Can't Debug Windows App?

Ron Howerton · March 29th, 2006, 10:30 AM

I am converting an old 1.1 .NET Windows application to 2.0. When I try to build it, VS 2005 says:

The following module was built either with optimizations enabled or without debug information...

...To debug this module, change its project build configuration to Debug mode. blah blah blah...

I have set teh configuration to DEBUG. I also verified that Optimizations are not enabled. But I still get this message and debugging is disabled, which means I cannot insert breakpoints, etc. This is making debugging unnecessarily painful.

So what else do I have to do to be able to debug my code?

Ron Howerton · March 29th, 2006, 05:19 PM

I have resolved this problem, although I never could enable debugging in the converted project. Instead, I created a new project in 2005 and imported all my converted code modules. I had to go through the same thing to convert one of my web projects, so it was no surprise, but the inability to debug a converted project points to a serious deficiency in the conversion wizard.

Hello, Microsoft, are you listening?!?!?

sholliday · January 19th, 2007, 06:10 PM

Go to the project in question (the one in the error message).

Go to

Project Properties.
Build.
Find the "Advanced" button in the bottom right.
Click and it will open "Advanced Build Settings".
Under "Output" change "Defug Info" to "full".

The issue is that the .pdb files are being copied to the /debug/bin directory of the "start up" project or webpage.

DDB001 · January 29th, 2007, 05:53 PM

I have similar problem. I am using VS 2005. In the past the debugger worked ok. I created a new project, I can see that pdb file was generated but for some reason in Release folder. I could not add any Break point(F9 does not work), F5 does not work eather, I don't see debug menu at all. Could you please help me?

planoie · January 30th, 2007, 09:53 AM

I wouldn't expect a PDB file to show up in the release folder after a compile. But aside from that, it sounds like you are compiling in release mode which would cause problems. Check your build configuration and change it back to debug and you should then be able to launch with the debugger.

-Peter

sirpoon · November 30th, 2007, 05:20 PM

Take a look in your Windows\Assembly folder for a matching dll with MSIL in the Processor Architecture column. Apparently, items in this folder are not always flushed OR if you have added a Release version of one of your components to the GAC, the GAC one overrides the local one. Anyway, removing this and rebuilding the project worked for me.