B
Bob Day
Using VS 2003 and VB.net...
Does a build release react differently to an exception if it sees a debugger
(such as VS 2003) on the machine?
With a bad SQL connection string, the VS 2003 F5 debug and the debug build
handle it correctly - there error is correctly trapped and caught with an
try/catch.
With the same code in a build release, same error, I would expect it to
operate the same. But instead, a dialog box come up saying
Would I like to launch a degugger? and VS2003 is an option.
The problem is probably something else, but I though I would check.
Thanks!
Bob
Does a build release react differently to an exception if it sees a debugger
(such as VS 2003) on the machine?
With a bad SQL connection string, the VS 2003 F5 debug and the debug build
handle it correctly - there error is correctly trapped and caught with an
try/catch.
With the same code in a build release, same error, I would expect it to
operate the same. But instead, a dialog box come up saying
Would I like to launch a degugger? and VS2003 is an option.
The problem is probably something else, but I though I would check.
Thanks!
Bob