I have solution with 3 projects. Project one – Library. Project two – Service (asmx). Project three – Test. In my service I have two config transform: PRODUCTION and TEST. They are equals, but name of databases is different. My solution:
If I Debug Test with PRODUCTION.config then all right – my breakpoints is active. If I Debug Test with TEST.config then bad. I get this:
What could be the problem? Sorry for my English.
- Right mouse click your project
- Select Properties
- Select the Build tab
- Make sure Define DEBUG constant and Define TRACE constant are checked
- Click the Advanced button at the bottom of the Build tabpage
- Make sure that Debug Info: is set to full
- Click OK and save changes
- Clean solution and rebuild the project
Link to source Fixing “The breakpoint will not currently be hit. No symbols have been loaded for this document.”.
(step 6 generates the .pdb files, these are the debugging symbols)
I have sit up remote debugging on a Window 2003 server accessed through the Internet. I have VS 2008 SP1 installed on my XP dev box.
I launched the site on the remote server and attached to all the w3wp.exe processes on the remote server. I noticed that the .dll did not load the symbols file. When I try to load the corresponding .pdb file from my local machine, it says file does not match. I have “Require source files to exactly match the original version” unchecked. The assembly on the remote server is the same as the one on my dev box. The site and .dll was copied from dev boc to remote server and code hasn’t changed since. So I know .dll and .pdb files should match or at least I need to force the matching.
- How do I get the .pdb file to load? I know breakpoints won’t trigger unless symbols file is loaded. I noticed that the .pdb file does not exist in the “Temporary ASP.NET Files” folder on the remote server. The .dll does.
- What’s the proper sequence to start debugging remotely inside VS? (Remote set up is done and I can see remote processes). In VS, I have start page as the url of the remote site. I start without debugging and then attach to w3wp.exe(s) on the remote. Is this all?
Are you running a Web Site or a Web Application (is it a compiled project, that you deploy the DLL for, or a collection of aspx and aspx.cs files that you deploy)?
If it’s a Web Application, did you deploy a release build, or a debug build? You won’t be able to hit breakpoints when “debugging” a release build, as the code is fairly heavily optimised.
Have you got “debug=true” set in the web.config compilation section? If not, again, debugging is going to be difficult.
Finally, the steps I use when remote debugging are:
- Deploy latest debug build of files
- Request page on remote server to start/restart application
- Ensure that the VS Remote Debugging Monitor is up and running on the remote server
- In VS, go to Tools (or Debug) | Attach to Process…, ensure that the remote server is selected in the Qualifier, and select w3wp.exe for the correct app-pool, etc.
- Request page that will fire break point.
If the breakpoints are hollow (thin red circles rather than filled disks), I’ll often check the Stack window in VS to see what has and hasn’t been loaded.
I am having a very weird issue that I am unable to see
w3wp.exe anywhere in my system. I am learning ASP.NET using tutorials. In my computer
w3wp.exe process is not showing in the taskmanager. Please help, I got frustrated by searching it throughout the whole day. I have
Try refreshing or showing all processes – I believe it’s a checkbox option.
Then, refresh your browser and go for the attach to process option.
w3wp.exe will not appear until the first request has entered the pipeline. So if you browse to your site and then open your task manager, you will see the
The last couple of days I’ve been trying to figure out why a console application we use at work was throwing an error whilst trying to connect to oracle, we had some issues with Devart’s DotConnect for Oracle throwing the following error – ‘Error loading db connection’
Having tried a number of options it was suggested to me that I should try remote debugging, something that I had never actually done before, odd I know but I had never set this up so below are the steps I followed to get it working:-
- Download and install Remote Tools for Visual Studio 2012 Update 2 here – (Make sure to install the correct version x86 or x64).
- I then started the Remote Desktop Service making sure to ‘Run As Administrator’. An entry with the date and time and a description will be shown once we connect to the remote debugging service.
- In my case I wanted to debug a console application – so I ran the console application (on the remote server)
- Make sure to have your VS 2012 solution open, add some breakpoints to the code you’re looking to debug on the remote server – its important that the code on the remote server is exactly the same as the code which is open in VS 2012 – if not breakpoints wont be hit.
- Now go back to Visual Studio and from the debug menu select Attach to Process, on this screen I change the Qualifier to the name of the remote server and select the console application process from the list of running processes on the remote server.
- If you check back on the remote server it should say that you’ve connected to the remote debugger service.
- If all is setup correctly then your breakpoints will be hit and hopefully you can figure out why your code wasn’t working
- Turned out the licence file we had been using was empty and by debugging I was able to see a more detailed exception stack trace and information.
This is how I got it running fairly easily – if you run into any issues :- For more info on setting up remote debugging follow this link here.
Hope this helps someone out there.