CODEWITHSUNDEEP
c#asp.netvisual-studio-2010
Julien
Julien

Reputation: 282

remote debugging asp.net

I have a server running my web app through IIS. I have visual studio locally, I am attaching to the remote w3wp.exe process with no issues, but my breakpoints are not being hit because my symbols are not loaded.

What am I missing?

What am i missing?

Update: Should I be debugging Native or Managed? When I do Native, the Modules window shows a ton of windows dll's that all fail to open the PDB. Should I be concerned? I do not see my dll in the list. When I use Managed, the modules window is completely empty.

Upvotes: 4

Views: 2188

Answers (2)

Julien
Julien

Reputation: 282

Found the issue. When I was attaching to the process via the Visual Studio gui, the w3wp.exe process was listed as x86 instead of Managed 4.0. I recreated my app's site in IIS and the process went back to being listed as Managed, which allowed the symbols to be loaded.

Upvotes: 3

bobek
bobek

Reputation: 8020

Make sure that you built your project in debug mode. Also, make sure you have sufficient rights for your remote server.

Upvotes: 0

Related Questions