12 January, 2010

“Launch for User” exception?

It is at times really annoying to be an MS-developer!

For the life of me, I could not figure out the source of a “nice” exception I was presented with today numerous times. “A Launch for User” exception? Come on, what’s that ?

A lot of Googling lead me to a number of other dudes with the same problem. They all had something like “Debugger.Launch()” in their code, which I certainly did not have! Finally pressing the Launch Debugger dialog and opening the editor to debug the problem led me to the precise source of the problem. I too had forgotten that I indeed did have such statement (Debugger.Launch()) in my code hidden far inside the code. So – if you ever experience this strange dialog/exception; hunt for Debugger.Launch() statements in the code running.

Happy coding.

2 comments:

Vlad said...

Yeah, I couldn't believe it until I found out that some other dude introduced the Debugger.Launch() line in my source file.

Anonymous said...

Guess what, Debugger.Break() does that too.

InRiver: Not loading your extensions?

(You really need to in the loop to appreciate the issue this post addresses). Man, I've been fighting this problem for hours before I ...