G
Guest
Hi
I am in a shop where developers are required to work off of a networ
share. This is so that code and other documentation is backed up nightly. This is outside the realm of Visual SourceSafe which we also use for code control. The network drive is used as the working folder. This is a configuration this shop has used for 6 years and I do not see it changing any time soon
So I am testing running an ASP.NET Web application with a Clas
assembly all on a shared drive
I have the solution working perfectly. However, I have run into
hiccup. In order to map IIS Virtual Dir to a network drive, you nee
to specify a username/password. When I use the username/password o
the person logged into XP for the Virtual Folder, then I can debug m
ASP.NET app with no problems. However, if I set the Virtual Folder t
connect as another ACL, then I get an error when debugging: Acces
Denied. If I log out of XP and then back in as that Virtual Folde
user, I can debug the ASP.NET application
Here is my configuration
Developer Workstation: X
File Server: Windows 200
CAS on XP has Full Trust of Windows 200
Two users: A &
Domain User
Administrators on both machines
IIS/ASP.NET on XP runs as A (through processModel machine.config
Impersonation is off
Virtual Folder 'Connects As' either A or B (ideally B
- using \\server\share. I tried mapping the drive and then using th
drive name but I receive 'The system cannot find the path specified
from IIS MMC
To Recap
1) - Logged into XP =
- processModel =
- Virtual Folder =
A can debug ASP.NET application
2) - Logged into XP =
- processModel =
- Virtual Folder =
B can debug ASP.NET application
3) - Logged into XP =
- processModel =
- Virtual Folder =
A CANNOT debug ASP.NET application: Access Denie
4) - Logged into XP =
- processModel =
- Virtual Folder =
B CANNOT debug ASP.NET application: Access Denie
The reason we want to have Virtual Folder connect as B is because
will be a generic username/password with special access to the Fil
Server. A will be any of the developer ACLs
This is to prevent administration with a couple 100 developer
changing 1000s of local virtual folders each time their password
change
I am in a shop where developers are required to work off of a networ
share. This is so that code and other documentation is backed up nightly. This is outside the realm of Visual SourceSafe which we also use for code control. The network drive is used as the working folder. This is a configuration this shop has used for 6 years and I do not see it changing any time soon
So I am testing running an ASP.NET Web application with a Clas
assembly all on a shared drive
I have the solution working perfectly. However, I have run into
hiccup. In order to map IIS Virtual Dir to a network drive, you nee
to specify a username/password. When I use the username/password o
the person logged into XP for the Virtual Folder, then I can debug m
ASP.NET app with no problems. However, if I set the Virtual Folder t
connect as another ACL, then I get an error when debugging: Acces
Denied. If I log out of XP and then back in as that Virtual Folde
user, I can debug the ASP.NET application
Here is my configuration
Developer Workstation: X
File Server: Windows 200
CAS on XP has Full Trust of Windows 200
Two users: A &
Domain User
Administrators on both machines
IIS/ASP.NET on XP runs as A (through processModel machine.config
Impersonation is off
Virtual Folder 'Connects As' either A or B (ideally B
- using \\server\share. I tried mapping the drive and then using th
drive name but I receive 'The system cannot find the path specified
from IIS MMC
To Recap
1) - Logged into XP =
- processModel =
- Virtual Folder =
A can debug ASP.NET application
2) - Logged into XP =
- processModel =
- Virtual Folder =
B can debug ASP.NET application
3) - Logged into XP =
- processModel =
- Virtual Folder =
A CANNOT debug ASP.NET application: Access Denie
4) - Logged into XP =
- processModel =
- Virtual Folder =
B CANNOT debug ASP.NET application: Access Denie
The reason we want to have Virtual Folder connect as B is because
will be a generic username/password with special access to the Fil
Server. A will be any of the developer ACLs
This is to prevent administration with a couple 100 developer
changing 1000s of local virtual folders each time their password
change