CODEWITHSUNDEEP
asp.netvisual-studio-2008remote-debugging
bzamfir
bzamfir

Reputation: 4886

Cannot debug asp.net application remotely - breakpoint doesn't get hit

I did this several time before, without any problem. But somehow, this time it simply doesn't work.

Systems:

Remote PC: VPS, Guest Win2008R2 x64 dual core (hosted on VMWare Server), VS 2008 remote debug x64 Sp1, application ASP.NET 2.0, isolated in own classic app pool. All updates applied. Host (if matters): AMD Phenom quad core

Develop PC - Win7 x64, VS 2008, all updates applied

I can connect to remote PC with Attach to Process. If I stop and start the app pool while "Attach to process" is open in VS, I can see the process and (apparently) I can attach to it. However, the breakpoint briefly get activated (red, filled) then immediately gets deactivated (red empty circle) and of course it doesn't stop the application.

I searched on google and found very few references. One suggested to copy the *.PDB in asp.net temporary files, and even if there there are lot of dirs with subdirs (one for each dll) I copied all PDB in temp folder with the dll. No success.

I'm running out of ideas. Does anyone feced similar issue? Any thoughts?

Thanks

Upvotes: 0

Views: 605

Answers (1)

user240141
user240141

Reputation:

You need pdb files for the same. Copy the actual pdb files of the dll from the development project. It will be inside the bin/debug/ directory of your original project (source code one not the deployed). Then copy the pdb file to remote directory where the dlls resides and then attach the debugger. Also for that , you need Remote Debugger.

Upvotes: 1

Related Questions