Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / Debugging / March 2005

Tip: Looking for answers? Try searching our database.

Unable to debug after installing VS2005

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Dale - 14 Aug 2004 13:07 GMT
I am unable to debug (F5) Visual Studio 2003 projects after installing Visual
Studio 2005 Beta. Everything worked fine before. The projects run perfectly
if I start without debugging (Ctrl+F5). The projects that I am trying to
debug are all located on my local machine. The VS 2005 debugger works great.
This is the error message that I am getting:

---------------------------
Microsoft Development Environment
---------------------------
Error while trying to run project: Unable to start debugging on the web
server.

Click Help for more information.
---------------------------
OK   Help  

Here is the output:

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

When I try to manually attach to the process, this is the error I get:

---------------------------
Microsoft Development Environment
---------------------------
Unable to attach to the process.
---------------------------
OK  
---------------------------

I have already tried repairing the IIS mapping, as described here:
http://support.microsoft.com/default.aspx?scid=kb;en-us;306005

I really don’t want to start re-installing applications if I don’t have to.
Any suggestions would be greatly appreciated.

Thanks,

Dale
"Gary Chang" - 17 Aug 2004 07:01 GMT
Hi Dale,

Installing the Visual Studio 2005 Beta would configure IIS to use the v2.0
.NET Framework, it would cause that Visual Studio.NET 2003 cannot debug
against the new version.

Do you have tried the following resolution to configured IIS using the v1.1
.NET Framework again::

Open a command prompt and navigated to the 2.0 .NET Framework folder:
C:\Windows\Microsoft.NET\Framework\v2.0.*

Then run the following command to remove the 2.0 mappings from IIS:
ASPNET_RegIIS.exe -u

After this we navigated to the 1.1 .NET Framework folder:
C:\Windows\Microsoft.NET\Framework\v1.1.4322

Run the following command to configure IIS to use the 1.1 .NET Framework
ASPNET_RegIIS -i

Wish it helps!

Best regards,

Gary Chang
Microsoft Online Partner Support

Signature

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
michael clark - 18 Mar 2005 00:27 GMT
this solution worked great for me. thanks

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2012 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.