|
.net
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
2.0 causes 1.1 debugging to fail?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 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. Show quote "GaryDean" <GaryDean@newsgroups.nospam> wrote in message news:ugeqIWOCGHA.228@TK2MSFTNGP12.phx.gbl... >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 > > >  |
|||||||||||||||||||||||
Other interesting topics