Menu
I have a project that is working fine on my system. I can debug the project without problems. My development system is Win 7 (x64). When I deploy and/or publish this project to my test environment (Windows Server 2003 (x32)), I can no longer debug it. I keep getting an error that states "The following module was built either with optimizations enabled or without debug information." It is referring to one of the DLLs in my project that is from another project in the solution.
This application was originally created in VS 2005. I upgraded it to VS 2010 with no problems. I also felt that the original project needed to be re-factored, so I pulled all of the business and data layer logic and put it into a separate class library project within the solution. The web project also needed to be split up because the same code was running on two different server with different pages on both. However, there was shared presentation logic between the two web projects, so I created another class library project that was specifically for the presentation layer. After all of that, I now have 4 projects (2 class library projects and 2 web projects).
All of the web pages are working correctly, but it appears that I am having some issues with a web service (classic web service, not WCF) in one of the web projects. I am getting erroneous results and I am trying to step through it to find the problem. Please help! I have a pending deadline on this project.
894
You can attach the Visual Studio debugger to a running process on a local or remote computer. After the process is running, select Debug > Attach to Process or press Ctrl+Alt+p in Visual Studio, and use the Attach to Process dialog to attach the debugger to the process.
Set up the remote debugger. On the remote computer, find and start the Remote Debugger from the Start menu. If you don't have administrative permissions on the remote computer, right-click the Remote Debugger app and select Run as administrator. Otherwise, just start it normally.
For a VB project, you turn remote debugging off with these steps: 1) In Solution Explorer, right-click on the project name and choose "Properties" from the shortcut menu. 2) In the Project Properties page, click the Debug tab. 3) Under Start Options, clear the checkbox that says "Use Remote Machine."
You're building on a 64-bit system and deploying on a 32-bit system. This may be your problem.
Also, the account used while setting up remote debugger needs to have admin or power user privileges.
Third, can you debug any other assembly remotely? Try building a dummy console app and see if you can debug it remotely.
Also, once you attach a debugger, you can go to Debug > Windows > Modules > select your module and try to load the symbols manually. This may give you additional info as to why its not getting loaded.
147
Sounds like your pretty experienced with remote debugging but I posted three short blogs on my experiences last year that may help you. I was building on a 64 bit Win7 system and deploying to s 32 bit XP. First I had to upgrade my OS from Win 7 Home Ultimate to Pro. Secondly one of posts talks about the problems I had remote debugging the DEBUG build! I had to use a Release build and set some flags (detailed pic and info in the blog entry).
Remote Debugging a Release Build
General Remote Debugging advice (and screencast) from VS2008
Choosing the Right Version of Win 7 for remote debugging.
41
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
