Can you set VS2008 to break on an error inside a try-catch statement


One of the things I loved about VB6 is that you had the ability to tell the development environment to break on all errors regardless of what error handling you had set up. Is it possible to do the same thing in VS2008 so that the debugger will stop on any error even if it happens inside a try-catch statement?

The problem is particularly hard when you are processing a file with say 500 records and it is failing on one of them - who knows which one - You don't want to modify the code so that your for counter is initialized outside that for loop - that is sloppy long-term. You just want the debugger to know to stop because of some setting you put somewhere.


I discovered that checkbox everyone is talking about during debugging of a project at work once. I flipped it on and all of a sudden I'm getting all these exceptions thrown all over the place! Turned out the dev's on another team had been using Try-Catch as a mask for easily preventable conditions (but were too lazy to trap themselves). BAD!

By : Mike K

From MSDN :

The name and location of the application configuration file depend on the application's host, which can be one of the following:

Executable–hosted application.

The configuration file for an application hosted by the executable host is in the same directory as the application. The name of the configuration file is the name of the application with a .config extension. For example, an application called myApp.exe can be associated with a configuration file called myApp.exe.config.

And also

For client executables, the application configuration file resides in the same directory as the application's executable and has the same base name as the executable with a .config extension. For example, the configuration file for C:\Program Files\Myapp\Myapp.exe is C:\Program Files\Myapp\Myapp.exe.config.

By : mathieu

Dynamic map rendering speed is typically dominated by two factors: data access and label layout. Doing coordinate projection and typical 2D rendering happens about as fast as data can be read from an external source, e.g. shapefile or database. The trick is how much data are you loading to draw a map? And how long does it take to get it? Complicated DB queries may be causing inefficient queries. Querying data which is not indexed will cause slow downs. Even if you find data quickly, you need to be aware of how much you are loading. Does your data contain a very detailed single multi-part polygon for all of Canada's islands at high detail, but you are only rendering the US-Canada border in Wyoming?

This video can help you solving your question :)
By: admin