When we write a program, we describe step-by-step what the computer must do (at least in imperative programming; in the functional programming things look a bit different) and in most of the cases we rely that the program will execute normally. Indeed, most of the time, programs are following this normal pattern, but there are some exceptions. Let’s say we want to read a file and display its contents on the screen. Let’s assume the file is located on a remote server and during the process of reading it, the connection goes down. The file then will be only partially loaded. The program will not be able to execute normally and show file’s contents on the screen. In this case, we have an exception from the normal (and correct) program execution and this exception must be reported to the user and/or the administrator.
Exception handling is a mechanism, which allows exceptions to be thrown and caught. This mechanism is provided internally by the CLR (Common Language Runtime). Parts of the exception handling infrastructure are the language constructs in C# for throwing and catching exceptions. CLR takes care to propagate each exception to the code that can handle it.
Note : "myTextFile.txt" file store "YourProjectLocation(ConsoleApplication) ⇁ bin ⇁ Debug ⇁ myTextFile.txt "
Note : Here we change "myTextFile.txt" strings so, here output is deferent then "Example 1"
Friend's some reason we need some long time for next update, Sorry For Long Time, see you soon.
We make a Collaboration with HackIsOn YouTube Channel So, Please Subscribe Their Channel and keep supporting