If I just drop the ping part out of there and attempt to connect to C$ on a network client computer without testing via ping first, there is a 50/50 chance that it will be able to succeed. What is the best way to handle this scenario if the client is unavailable?
I was using ping to verify that the computer was on the network before attempting to open the C$ share. If I try to open the C$ share and the computer is not on the network, the application will fail without some way of dealing with the error.
Could you give me some sort of idea what I should research (keywords or classes perhaps) in order to catch the error on the fly? I am new to C# and haven't found very many reliable resources to learn/research the language.
In a C# 2008 and C# 2010 desktop applications that I am working on, I have the following questions to ask about adding features to the app.config file:
1. I would like to know how to add a reference to an executable that needs to run. I do not want to hard code the path, I would prefer to have the data path be dynamic.
2. I would like to add 2 entires to the app.config file where the location points to two different locations where output files are placed.
Thus can you tell me and/or point me to a reference that will show me how to make the coding changes to use and app.config file and what to add to the app.config file for my goals to be accomplished? (I basically would like to know what ‘tag(s)’ in the app.config I would need to place these new references.)
There is no technical problem or error in my project.
This question is about how improve my project to be more user friendly.
Let me explain about my project:
There are many tables in DB and I have created a CRUD Form for each table; There is Form that contains some buttons and every button opens a single CRUD Form.
Now imagine that user want to register an student and the user is very busy because of large number of students; so the user should open and close many of Form from the board just for entering a single student's information.
You know that in DB there is a table for each existence.
Person, PhoneType, Phone, Register, Class, Teacher, etc; and for each of them there is a CRUD Form. If one of them will cancel so I would cancel all of the insertion before the current Form.
Did you get what I mean?
In other word I should update all of them if the last Form's DialogResult equals DialogResult.OK and reject all changes if it is DialogResult.Cancel.
First the user will open and enter personal info about the first student in CustomerUI then he/she will close that. Now the entries will update at FormClosing by user's confirmation.
Second step the user is going to enter information about class registration. Now consider that the student doesn't want to register any more.
At thiss time there is a record in "Person" table in DB that is useless.
I'd implement a menu bar &/or a toolbar. So no matter where the user is in the app (unless in a modal form) they can add a student quickly by selecting the "Add Student..." menu item. I would also include a shortcut for the menu item. I would add all the common tasks a user needs in the menu bar.
Consider above statements.
after executing this command the content of
textBox1.Text will be 46.99 instead of 47;
I've solved this problem by some functions, but I want to see is there any tuning in C# 2010 that I missed it? thanks