|
|
 |
| Visual Studio 2005 For discussing Visual Studio 2005. Please post code questions about a specific language (C#, VB, ASP.NET, etc) in the correct language forum instead. |
Welcome to the p2p.wrox.com Forums.
You are currently viewing the Visual Studio 2005 section of the Wrox p2p Programmer to Programmer discussion community. This is a community of more than 40,000 computer programmers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining our free Wrox p2p community you can post your own programming questions and respond to other programmers’ questions. Registered users also don't have to see the ads that are displayed to guests. Registration is fast, simple and absolutely free so please, join today!
Join today and post to win prizes! Post more to increase your chances of being Wrox’s top poster of the month.
|
 |

March 29th, 2006, 10:30 AM
|
|
Friend of Wrox
|
|
Join Date: Jun 2003
Location: Denver, CO, USA.
Posts: 342
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
Can't Debug Windows App?
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?
__________________
PLEASE READ THIS BEFORE RESPONDING: If you have nothing to offer except a lecture on the superiority of Javascript, do not waste your time or mine. I am in an all IE world where I can use VBScript to my heart's content. I choose to use VBScript over Javascript because Javascript is horrendously frustrating to me due to inconsistencies in naming standards and and unnecessary case sensitivity. I would rather not receive assistance than have to read one more sanctimonious lecture about what an idiot I am for using VBScript, OK???
|

March 29th, 2006, 05:19 PM
|
|
Friend of Wrox
|
|
Join Date: Jun 2003
Location: Denver, CO, USA.
Posts: 342
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
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?!?!?
|

January 19th, 2007, 06:10 PM
|
|
Registered User
|
|
Join Date: Jan 2007
Location: , , .
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
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.
|

January 29th, 2007, 05:53 PM
|
|
Registered User
|
|
Join Date: Jul 2004
Location: , , .
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
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?
|

January 30th, 2007, 09:53 AM
|
 |
Friend of Wrox
Points: 16,368, Level: 55 |
|
|
Join Date: Aug 2003
Location: Clifton Park, New York, USA.
Posts: 5,394
Thanks: 0
Thanked 2 Times in 2 Posts
|
|
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
|

November 30th, 2007, 05:20 PM
|
|
Registered User
|
|
Join Date: Nov 2007
Location: , TX, USA.
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
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.
|
| Thread Tools |
Search this Thread |
|
|
|
| Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
|
 |