try/catch delay at first exception

There is always going to be some overhead with using exceptions over HResults (ie returning an error from your function, which is the way it works in C). This is why you should use custom exceptions sparingly, and really put some thought as to if and where you throw them. If it is possible to avoid them you should, but used correctly they are, of course, extremely powerful. (oh, and by the way, dont use HResults in .NET) Regards KevinT

Actually, there still is a slight delay when first throwing the exception, but, compared with the delay caused when executing within the IDE, it is imperceptible: - from within the IDE an average of 450 milliseconds at first run -direct execution returned an avarage of 18 milliseconds at first run, but as I said, this amount of time is imperceptible. I guess these figures depend on the type of the exception thrown and of the platform, so these figures are only relevant to see the rough ratio between the two.

Thanks, KevinT, you were right! Best of luck, ldragos

This behaviour is often simply because you are running the app from the designer and there is a lot of debug functionality that the designer loads to allow you to interrogate/deal with the exception. Try running your app directly from the .exe and the chances are you will see that the delay has gone... Regards KevinT

It is depend with the What code are you have in ur App. example, If you are trying to open the SQL Server Connection. If the Server is not Avilbale then it will search the Path and try the Server name all the possible Network path. Finally it throw the error. From the next time it will execute faster. Bcs it already Know the Path of the Server. Same that will be happend in some other code also. So its only depand on your Code. Pls explaine the Code what you had in try {} block. -Manivannan