Exception Managing in C#

It has been noticed almost never that a application operates correctly at its pretty very first attempt. Problems are pretty popular even though creating a application and are thought of as mistakes. The mistakes can be either compile time or operate time.
Compile time mistakes are typically syntax mistakes and are detected ahead of the execution of application. Missing semicolons, Mismatch of brackets, misspelling of key phrases and identifiers, bad references and poor assignments are popular compile time mistakes. Operate Time mistakes are occur throughout the execution of application. These mistakes do not let the successful execution of application and sometime sales opportunities to undesired benefits. In modern-day programming, operate time mistakes are also named exceptions. Divide by zero, invalid typecasting, invalid references, incapability to obtain a source are some of the operate time mistakes. Operate time mistakes are thought of a lot more dangerous as in contrast to compile time mistakes. These are typically due the invalid logic and almost never due to syntax.
C# gives a pretty economical process to cope with operate time mistakes (Exceptions). Any time C# compiler encounters operate time mistake, it makes an exception item and throws it. If exception is not caught and taken care of, the mistake message is shown and application terminates instantly. To continue the execution of application, even mistake has occurred the exception should be caught and taken care of correctly. In .Internet, exceptions are cases of the courses derived from Procedure.Exception.
Exception is handling is performed making use of- try….catch….finally syntax. We enclose the code in try out block, which is possible to elevate the exception, followed by capture block. The capture block catches the exception thrown and handles it. Each individual capture block has the code to cope with the exception correctly. At conclusion we compose the finally block- specifying the code that is always executed irrespective of no matter if or not the exception is thrown.
Try out



/////exception handling code


///the code to be executed finally no matter if exception occurred or not

A solitary try out block can have several capture blocks, every single handles the precise exception. But only one capture block is executed for each and every try out block, out of several capture blocks. When an exception is occurred, capture blocks are examined one by one till the correct is discovered, that can cope with the exception. If no certain capture block handles the exception, then only basic capture block is executed.