Richard
Fri Sep 02 23:54:04 CDT 2005
Hi David,
I was working on other details so I postponed addressing this question until
this evening (actually, early Sat. morning. I found your reply, but I
can't figure out what thread it's on. So, I'm going to reissue this
question, which will be more sophisticated since I'll reflect my new
understanding base on what you've told me.
The Subject will be: "How to set up privileges for VS.NET developers?"
Thanks for the help you've already provided. But I don't know how to
implement it, which will be reflected in my new post.
Best wishes,
Richard
"David Wang [Msft]" <someone@online.microsoft.com> wrote in message
news:uE0onb5qFHA.248@TK2MSFTNGP14.phx.gbl...
> When using the fileshare mode of project deployment (FPSE is the other
> supported option), you need to have the user in the "VS Developers" group
> as
> well as make sure \\server\wwwroot$ is accessible.
>
> What happens is that Visual Studio, behind the scenes, will use the
> wwwroot$
> share to move data around to/from the web server, and since the wwwroot$
> share is ACL'd for access by "VS Developers" group, as soon as you are in
> that group and ports for UNC shares are open on your firewall, it should
> work.
>
> Fileshare mode of project deployment actually has little to do with IIS.
> The
> main thing ASP.Net needs is a defined application in IIS that maps the
> /MyVirtualProj URL to some physical path on the server, usually
> underneath
> the same directory structure that wwwroot$ exposes -- thus the two work in
> tandem to all you to deploy, debug, and run an ASP.Net application with
> VS.Net.
>
> I'm not certain what K:\ maps to, but if you are using the fileshare
> deployment model, you should not need a K:\ mapping.
>
> --
> //David
> IIS
>
http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> //
> "Richard Lionheart" <NoOne@Nowhere.net> wrote in message
> news:eUXWxh4qFHA.3080@TK2MSFTNGP15.phx.gbl...
> Hi All,
>
> Is there on-line documentation for the permissions available in IIS for a
> Virtual Directory's Local Path? Specifically I want documentation in
> relation to developing Web Forms using Visual Studio .Net.
>
> I'm developing my first (small) .Net WebForm app by following Jeff
> Prosise's
> "Programming Microsoft .Net" (2002 edition) guidance on page 220. I
> created
> a virtual directory without incident. But when I took the next step to
> create
> a Web App Proj, I ran into an access problem. I got a "Web Access
> Failed"
> dialog saying:
>
> =======================
> The default Web access mode for this project is set to file share, but
> the
> project folder at
http://localhost/MyVirtualProj cannot be opened with the
> path "K:\_Projects\WebForms\MyWebProj". The error returned was:
>
> Unable to created Web project "MyVirtualProj". The UNC share
> "K:\_Projects\WebForms\MyWebProj" does not exist or you do not have
> access.
> ========================
>
> I got around it by accessing my virtual directory's properties in IIS and
> gave the Local Path all the permissions I could. That did the job. But
> I'd
> like to know what the most appropriate permissions are for various
> contexts.
>
> Thanks in advance,
> Richard
>
>
>
>