2.0 causes 1.1 debugging to fail?

G

GaryDean

I have a 1.1 asp.net project that will no longer debug and I suspect that
the install of vs.net 2005 and framework 2.0 might be the cause. I can,
however, debug other projects. the message I get is:

Auto-attach to process '[3688] aspnet_wp.exe' on machine 'MACHINEX' failed.
Error code 0x8013134b.

The project will run without debugging.

The KB I found says this could happen with framework 1.0 but there is no
mention of 1.1.--


Regards,
Gary Blakely
 
G

GaryDean

Uh, never mind :)

That project was once a 2.0 project but I migrated back to 1.1 because the
conversion was corrupted. However IIS still had that name as a 2.0 app.
Once I changed it back to 1.1 it worked fine.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Debugging ASPNET 1.1 WebApp Running On IIS with Framework 2.0 2
conflict between asp.net 1.1 and asp.net 2.0 4
Debugging Problems 2
Can't debug 1.1 web app 5
Will ASP.NET 1.1 application work perfectly on .Net Framework 2.0 4
Migrate ASP.NET 1.1 application to 2.0 1
ASP.net 1.1 debugging on IIS with .net 2.0 5
specify Framework 1.1 when 1.1 & 2.0 Beta 1 are installed 6

Top