Re: can't debug ASP.NET app after upgrading to VS.NET 2003
From: Brian K. Williams (williamsb_at_millenia.com)
Date: 02/20/04
- Next message: Tim Mulholland: "Re: Custom IIdentity class - how to set it?"
- Previous message: Elizabeth Newman [MS]: "RE: Error crystal websetup 9 install"
- In reply to: SXL: "can't debug ASP.NET app after upgrading to VS.NET 2003"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 20 Feb 2004 12:56:26 -0800
Have you set the Debugging Flags on IIS?
Enable ASP server-side & client-side script debugging.
If you have the debugging flags set you can try uninstalling IIS then
install the .Net Framework then re-install IIS.
Brian K. Williams
Reaction Labs
"SXL" <anonymous@discussions.microsoft.com> wrote in message
news:E42141CC-7FBB-4DE5-9458-438ECF7D32F0@microsoft.com...
> I just upgraded my VS.NET 2002 to VS.NET 2003.
>
> I converted an old ASP.NET web application (a C# project), which was
created in VS.NET 2002, to VS.NET 2003. Everything seems to go smoothly,
but I can't debug anymore!? The message is:
> "Error while trying to run project: Unable to start debugging.
> ASP debugging is disabled because the ASP process is running as a user
that does not have debug permissions."
>
> The environment I have is:
> - Windows 2000 (can't be changed because of company policy)
> - IIS 5.0 as web server, which is on the same machine as VS.NET at this
point.
>
> I've checked all the places I can think of, such as :
> - Enable ASP.NET Debugging in my VS.NET project property.
> - Directory Security in IIS web property
> - Debug programs in Local Security Policy
>
> Any idea?
>
> Thanks in advanced,
> SXL
- Next message: Tim Mulholland: "Re: Custom IIdentity class - how to set it?"
- Previous message: Elizabeth Newman [MS]: "RE: Error crystal websetup 9 install"
- In reply to: SXL: "can't debug ASP.NET app after upgrading to VS.NET 2003"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
