"unable to attach to the process" when debugging in VS.2003

Question

Hello,

I have both Visual Studio 2003 and Visual Studio 2005 installed on my workstation. I have some big projects that are not transitioned from 2003 to 2005 yet and I have to debug thier code now.

But after I installed VS.2005 "Attach to a process" feature stopped working in VS.2003. When I try to attach to a process that has .Net 1.1 assemby running it always gives me an error "unable to attach to the process" with no further explanation.

Re-registering mscordbi.dll didn't help:

regsvr32 C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscordbi.dll

Any iseas how I can fix 2003 so I can continue working in it?

Thanks, Vladimir

Answer 1

Does the process have the 1.1 or 2.0 version of mscorwks.dll (you can check with listdlls from www.sysinternals.com)

Answer 2

By default apps will run against the later framework if it is installed.  This will cause the error you are seeing in VS 2003.  To force your apps to run against framework v 1.1 add the following to their config files

   <startup>

      <supportedRuntime version="v1.1.4322" />

   </startup>

hth
Bill

Answer 3

I'm using VS2003, but have .Net framework v2.0 installed. These are incompatible - I can't attach to a process to debug CLR code when the app has invoke .Net v2.0. Such was the case writing my BHO for IE. However, the message was frustratingly vague: "Cannot attach to process"
I defined a .config file for IE and required .Net v1.1, and now I can debug my BHO code!

Thanks for the notes

Answer 4

I have the same problems but since we only have Class Libraries (no exes) that are called from VB6/COM it is not possible to add a specific config file for the "application".

Are there other solutions to this problem?

BR

Anders

Answer 5

 

This is what I did to solve that problem. Basiclly I went to the IIS settings , and I change the project's ASP.net configuration back to 1.1 for the the 1.1 project. When I attached the debug process ,  I had two asp.net_wp.exe for me to choose. If it is asp.net 1.1 then I choose the 1.1 exe, if it is 2.0 then I choose the 2.0 exe. I do not know if this could apply to your case.

Answer 6

 

This was a gr8 help friend.

Answer 7

I had the same "unable to attach to the process" issue in a remote debugging setup, with my Visual Studio.Net trying to debug an 1.1 ASP.Net application on a remote W2003 x86; I thought it had to do with a security issue, but just switching the remote IIS from the ASP.Net 2.0 runtime to 1.1 did the trick

Answer 8

Thanq. This did the trick.