Using .NET Exceptions for ASP.NET 2.0 Error Handling?

[Duncan P]

I have seen in multiple forum posts that using .NET Exceptions in server-side code can cause performance issues on the server. As of right now my site uses both exceptions and conditions/return statements to handle errors. I would like to be consistent and use .net exceptions, but I am afraid that if I switch (most) of the error handling to try/catch blocks that I will see a performance hit. Can anyone provide some insight as to the best methods for ASP.NET 2.0 error handling. Note:* I need detailed error handling, as my code is dealing with a large database as well as multiple remote servers.In response to youngboy:Thanks for the answer. The performance issue is actually from an msdn article located here:http://msdn2.microsoft.com/en-us/lib...49.aspxAnother article with the same viewpoint:http://www.realsoftwaredevelopment.c...s-to-impr.html