|
Home > Archive > IIS Server Security > February 2004 > how to debug ASP.NET with Win 2003 Server?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
how to debug ASP.NET with Win 2003 Server?
|
|
|
| Hi,
we use Visual Studio.Net, SQL Server and Windows 2003
Server.
It has always been no problem to debug ASP.NET applications
through IIS under Windows 2000, but now only works if we
give our developers admin rights on the server. The
developers work directly on the server through windows
terminal services.
Can someone tell me what the problem is?
Many thanks.
bodo
| |
| David Wang [Msft] 2004-02-26, 5:34 pm |
| Read VS.Net documentation. I've debugged ASP.Net apps on Windows Server
2003 without being an administrator.
The key challenge is whether the developr has privileges to attach onto the
worker process which is running ASP.Net code -- either put the developer
into "Debugger Users" group, or create individual AppPools using the dev's
identity.
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"bodo" <anonymous@discussions.microsoft.com> wrote in message
news:2a9f01c3fc9d$9de3e890$a301280a@phx.gbl...
Hi,
we use Visual Studio.Net, SQL Server and Windows 2003
Server.
It has always been no problem to debug ASP.NET applications
through IIS under Windows 2000, but now only works if we
give our developers admin rights on the server. The
developers work directly on the server through windows
terminal services.
Can someone tell me what the problem is?
Many thanks.
bodo
|
|
|
|
|