Monday, April 18, 2005

ASP.NET 2 and 1 Conflicts!!

After i loaded loaded VS.NET 2005 and tricked my firefox to act on iexplore.exe a strange error started popping up when trying to debug web applications from VS 2003! it said something like Auto-attach to process w3wp.exe failed... error code 0x8013134b.

Did a bit of googling and turns out - firefox has nothing to do with this! it's a conflict between VS 2003 and VS 2005! An ASP.NET 2.x and 1.x conflict to be more specific! A few sites seems to give you solutions but none seemed to work for me - (a combination of more than what one usergroup suggested did the trick however:) ) here's what allows you to get debug mode running in VS 2003...


  • Ensure that you register 1.x with iis again - go to command prompt of VS 2003 and type aspnet_regiis -i
  • change your default web site's asp.net version to 1.x - open properties in iis manager, select properties, go to asp.net tab and select 1.x as your version!
  • Just to be sure is registered 1.x again - (aspnet_regiis -i)
  • deployed a new project and hit F5 - and there it was!!! running as sweet as before!


So did the aspnet_regiis -i work fist time / second time? what happens to VS 2005 now if i try to run web applications there with debug mode...? For now, my apps in 2003 are running again and that's good enough... maybe i'll do a aspnet_regiis -i
from VS 2005 beta while playing around with Whidbey! and then choose ASP.NET v 2.x from iis :)

0 Comments:

Post a Comment

<< Home