Try Catch.

[Vipin Venugopal]

Do using of so many try-catch block in a project degrade the performance of Project. To be clearer do try catch consume more memory. Vipin

[XNork]

Yes, Try catch is expensive in memmory usage, especially if used frequently.

[_AK_]

Do you know some article which gives a bit details in this regard?

Best Regards, Apurva Kaushal

[Guffa]

Using a try-catch block is not expensive, but when an exception is raised, there is a performance hit. Use try-catch for anything that potentially can go wrong, but don't use it for normal program flow. If you for an example have a string that sometimes contains a number, it's better to check the contents of the string before converting it than to use a try-catch to handle the times when it doesn't contain a number.

--- b { font-weight: normal; }

[Vipin Venugopal]

Thank u so much for the information. Vipin

[XNork]

http://windowssdk.msdn.microsoft.com/en-us/library/5dws599a.aspx#CodingPractices[^]

[_AK_]

Thanks man.. :)

Best Regards, Apurva Kaushal

[Scott Dorman]

Using try/catch, try/finally, and try/catch/finally blocks are only expensive when an exception occurs. At that point, the runtime has to take a lot of steps to unwind all of the catch handlers to see who should respond to the exception. Exceptions should only be thrown when something goes wrong, not to help control program flow. If you use them to try and control program flow, then it gets expensive (not to mention it's just bad practice). Incidentally, if you have any using blocks using (MemoryStream stream = new MemoryStream()) { // do some work here } you are implicitly using a try/finally block. The C# compiler will automatically turn this into MemoryStream stream = new MemoryStream(); try { // do some work here } finally { if (stream != null) { ((IDisposable)stream).Dispose(); } }

[Scott Dorman]

Guffa wrote:

If you for an example have a string that sometimes contains a number, it's better to check the contents of the string before converting it than to use a try-catch to handle the times when it doesn't contain a number.

In these cases, you should really look at the TryParse methods. .NET 1.1 only had a few of these, but they have been expanded in .NET 2.0 to be included in more of the basic data types.