creating new project in VS.NET

  • Thread starter Thread starter Sam Carleton
  • Start date Start date
S

Sam Carleton

I am trying to figure out how to get VS.Net and IIS6 to work
together... I am working in domain nowhere.local. I have a W2K3
server named server1.nowhere.local that is running IIS6. I want it
to host a web site named jws.nowhere.local. Within II6 of server1,
I created a new web site as to allow one to serf to
jws.nowhere.local and see the simply default.htm doc. Then I have
shared that directories root such that the path to the default file
is: \\server1\jws$\default.html

Then when I try to create a new ASP.NET Web Application:

http://jws.nowhere.local/calendar

With a file share path of:

\\server1\jws$\calendar

-------------- I get this error --------------

The default Web access mode for this project is set to file share,
but the project folder at 'http://jws.nowhere.local/calendar' cannot
be opned with the path '\\server1\jws$\calendar'. The error
returned was:

Unable to create Web project 'calendar'. The file path
'\\server1\jws$\calendar' does not correspond to the URL
'http://jws.nowhere.local/calendar'. the two need to map to the
same server location

-------------- error --------------

The file path and the URL do point to the same location. What do I
need to do to get this setup correctly?

Sam
 
Sam Carleton said:
I am trying to figure out how to get VS.Net and IIS6 to work
together... I am working in domain nowhere.local. I have a W2K3
server named server1.nowhere.local that is running IIS6. I want it
to host a web site named jws.nowhere.local. Within II6 of server1,
I created a new web site as to allow one to serf to
jws.nowhere.local and see the simply default.htm doc. Then I have
shared that directories root such that the path to the default file
is: \\server1\jws$\default.html

Then when I try to create a new ASP.NET Web Application:

http://jws.nowhere.local/calendar

With a file share path of:

\\server1\jws$\calendar

-------------- I get this error --------------

The default Web access mode for this project is set to file share,
but the project folder at 'http://jws.nowhere.local/calendar' cannot
be opned with the path '\\server1\jws$\calendar'. The error
returned was:

Unable to create Web project 'calendar'. The file path
'\\server1\jws$\calendar' does not correspond to the URL
'http://jws.nowhere.local/calendar'. the two need to map to the
same server location

-------------- error --------------

The file path and the URL do point to the same location. What do I
need to do to get this setup correctly?

In general, VS.NET wants to create web projects at
http://localhost/webproject. It's not very good with anyplace else.
 
That's not really correct...

Now back to Sam's question -- Sam, since you mention this is IIS6 you're
dealing with... I also guess you might be using VS 2002... in which case,
you will need to ensure that .tmp extension is allowed in IIS.

VS places a file with .tmp extension in that file share, and then makes an
HTTP request for that same name using that URL shown in the error. If it
does not receive the same file, it throws the error you're seeing.

..tmp extension is prohibited in IIS6 by default, so you'll have to enable it
first.

PS. VS 2003 uses .htm extension, hence you would not run into this problem.
If you're using 2003, then you'd probably need to double-check that the
locations do really match.
 
Strange I have projects in all sorts of places and VSNet has absolutely no
problems at all managing them.
 
This is the information I got from Microsoft when fighting this battle. I'm
only repeating it.
 
How do you make .tmp extension allowed in IIS? Mapping?

I just did some digging around and discovered that all you have to
do is add .tmp to the MIME types of the server. In other words,
open up properties on the server, click on the MIME Types... button
and add .tmp.

Sam
 
This one sucks :) It's actually a bug in VS... you DO have permissions --
you can confirm that by adding another type of file to the project (say an
xml file.. or something like that.. whatever's available on the menu)

I think there was a fix for it... you can call into support to request it
(no charge of course).

Optionally, you can use FrontPage Server Extensions instead -- they don't
exhibit this particular problem.
 
Back
Top