Hi Leszek,
Using FPSE is an optional work around for this issue. I have another
solution for your reference.
We can follow the following steps to create the project on the
virtual/remote Web site.
Once the virtual Web site is created,
1) Share the physical folder pointed by the virtual Web root.
2) Provide permissions to VS Developers Group to that folder and make sure
the user on the client is one of the members of this group on the server.
3) In an intranet situation, add the virtual web site name/address to hosts
file on both client and server machine.
From the client,
1) Open Visual Studio.NET.
2) Go to Tools/Options/Projects/Web Settings and on the right hand side
panel, select "Connection Settings" or you can also open IE and go to
Tools/Internet Options/Connections.
3) Click on LAN settings and if you are using proxy, then uncheck all the
options under "Automatic configuration" section. ("Automatically detect
settings" and "Use Automatic configuration Script")
4) Check both options in "Proxy Server" section ("Use Proxy server for your
LAN .." and "Bypass proxy server for local addresses") and provide the
details of the proxy server.
5) Click on the "Advanced" button in Proxy Server section and in the "Proxy
Server" dialog box, add the host header name to the list that says "Do not
use proxy server for addresses beginning with the following" and click Ok.
6) Start creating a new project in VS.NET
8) In the New Project dialog box, provide the location as
http://virtualWebsitename/projectname
9) When you get the Web Access Failed dialog box, provide the proper share
for the virtual web site that you are going to create project in. e.g.
\\<machinename>\sharenameforvirtualwebsite\projectname
10) Now the project should get created under the specified share on the web
server.
I hope it helps.
Best regards,
Jacob Yang
Microsoft Online Partner Support
Get Secure! ¨C
www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.