Debugging Error Message of VS2005
Microsoft Visual Studio
The following module was built either with optimizations enabled or without debug information:
C:\Documents and Settings\Peter Peter\Local Settings\Application Data\assembly\dl3\GK36Y4X8.1TR\K1JO6NOP.P99\bc8980d3\f0e49e63_711dc601\MyResources.dll
To debug this module, change its project build configuration to Debug mode. To suppress this message, disable the 'Warn if no user code on launch' debugger option.
OK
I didn't do anything but this error message come out from VS2005, I followed the "suggested" solution and of course, it doesn't work. Who know the reason of this strange message?
Thanks,
Do you know where 'MyResources.dll' is coming from?
MyResources.dll is actually another class library project in my solution.
I'm having the same issue, i've checked the project properties and its all set for debugging but I still get this issue. Did you find a resolution to the problem? Can you give me any more information about how your assembly is being built and deployed? For instance, from the error message, it looks like MyResources is being deployed to a local GAC.
Hello, I have the same problem.
I created a new configuration (Debug_MR) for my solution and used the option to copy settings from an existing configuration (Debug).
I can go to any configuration of any the 68 projects in my solution, they all show (Debug and Trace constant ON) but I can not debug anypProject unless I change back to "Debug" Configuration". When using the 'Debug_MR' configuration, I get exactly the same error messsge.
What do I do wrong ?
Marc
Hi there,
I compared the output generated when building with configuration "Debug" with the output generated using a custom made configuration.
Even if 'Debug' and 'Trace' constants are enabled in the custom configuration, the Build-Process is started without the "/debug+" Option. If this one is missing, you can not debug your project.
You can enabled it again if you select the 'Advanced Option" in the Build-Tab of the Configuration-Dialog and then select "Debug-Info" full.
Unfortunately, this setting is not copied across when copying configurations.
Marc
I got the same problem and now I have solved it.
That's because project files in your dictionary "/bin" is *.dll.
VS2005 needs *.pdb and *.dll.
You can solved it like this.
web project--property--referance
add referance--project
add you projects of other layer.
I too had a similar problem after installing Visual Studio.NET 2005 and converting a ASP.NET 1.1.4322 project to ASP.NET 2.0.50727 version Web Application Project.
First, I ensured that my .csproj file had the correct definitions like this:
<DebugSymbols>true</DebugSymbols>
<DebugType>full</DebugType>
<DefineDebug>true</DefineDebug>
This still did not work, so after casting about for a while,
I went to the Main Menu in VS.NET 2005 where I selected:
Tools > Options > Debugging > General and unchecked the "Enable Just My Code (Managed only)" Checkbox.
This final action enabled debugging in this project.
Hope this helps
Hi hrjordan,
you post was most helpful and helped me solve a problem I had been having all day.
Although I like it when problems are resolved I like it even more when I understand why I fixed, can you explain why unchecking the "Enable Just My Code (Managed Only)" made my project debug again.
Wayne
Wayne,
Sorry, but I don't have the answer either.
I'm glad it worked for you.
Harry
Cheers Harry,
can anyone explain why this setting enables the debugging?
Wayne
This option does nothing but get rid of the warning...
Exactly, this option just gets rid of the message, you must have seen even when the message comes and you press 'OK' the application runs, so this option just removes the warning message. Doing this the problem is one cannot debug the application, if anyone can tell me how to debug the application after this message , then I am waiting eagerly for a reply.
I myself found the solution to this, in my case it was happening because I was trying to debug a project the path of which was not the same as the dll which I was using in my application solution. So, in order to debug an additional project in the mai project its dll path should be same as the path of the project to be debugged.
Hope this helps someone.
