Logo 
Search:

Asp.net Forum

Ask Question   UnAnswered
Home » Forum » Asp.net       RSS Feeds

Opening a Web Application (remote server)

  Asked By: Howard    Date: Apr 03    Category: Asp.net    Views: 1115
  

we are moving to VB.NET and ASP.NET. Overall I am very pleased with
both, and have made some nice ASP.NET applications using the localserver
with IIS on my machine. However I want to something very simple (I
assume) which is to create an ASP.NET application on a remote server
running IIS and the .NET framework.

I know this sounds like the ultimate newby question, but clearly I am
missing something very very simple!

I start a new ASP.NET Web Application project and specify the location
'http://161.#.##.##/crews/WebApplication1' (or)
'http://$$$.wku.edu/crews/WebApplication1'. Both result in the same
error message shown below:
--------------------------------------------------------------------

"The default Web access mode for this project is set to file share, but
the project folder at 'http://161.#.##.##/crews/WebApplication1' cannot
be opened with the path '\\$$$.wku.edu\wwwroot$\crews\WebApplication1'.
The error returned was:

Unable to create Web project 'crews/WebApplication1'. The UNC share
'\\$$$.wku.edu\wwwroot$\crews\WebApplication1' does not exist or
you do not have access.

What would you like to do?
(*) Retry using a different file share path
( ) Try to open the project with FrontPage Server Extensions

--------------------------------------------------------------------

I have two basic questions. First, why can I not create a project on a
remote server? (I do have access the 'crews' account using FTP and host
some course web pages from that account.)

Second, if it did work, when would it authenticate that I have
permission to access the server? (I assume that a valid connection
would respond with a password verification dialog, right?)

Thanks in advance for helping out an instructor who wants to teach new
technologies to his students

Share: 

 

5 Answers Found

 
Answer #1    Answered By: Vid Fischer     Answered On: Apr 03

With some messing around I could make this work on my setup, but I found
it much easier to develop locally and use the handy little "Copy
Project" button to send my project to the production machine. It also
gives you the option to only copy files needed to run, so you don't
clutter up the production environment with all of VS's extra files.

 
Answer #2    Answered By: Daniel Costa     Answered On: Apr 03

Your server  needs to have either Frontpage Extensions installed, or you
network access to a shared folder which houses your web  stuff. The server
admins need to either give you author privledges on a web (frontpage), or
network privledges to a share on the webserver.

 
Answer #3    Answered By: Grace Ellis     Answered On: Apr 03

We had this problem when starting our projects too. I believe VS.net
attempts to connect to the project via FrontPage extentions first (which is
why it tried http://161.#.##.##/crews/WebApplication1
<http://161.#.##.##/crews/WebApplication1> first) then it'll try to access
the project via network shares (which is why it then tried to access it via
the UNC path \\$$$.wku.edu\wwwroot$\crews\WebApplication1'
<file://\\$$$.wku.edu\wwwroot$\crews\WebApplication1'> ) For some reason
VS.net added the $ at the end of the wwwroot share name - so when we removed
the $ it worked for us... so try connecting to
\\$$$.wku.edu\wwwroot\crews\WebApplication1
<file://\\$$$.wku.edu\wwwroot\crews\WebApplication1> (notice - no $ after
wwwroot). If that doesn't work -- see if you can access
\\$$$.wku.edu\wwwroot$\crews\ <file://\\$$$.wku.edu\wwwroot$\crews\> from
your windows explorer. If not, then it could be a permissions problem...

 
Answer #4    Answered By: Alisha Johnson     Answered On: Apr 03

FYI, the $ on the end of the share name means that the share is
hidden, which is recommend in an environment where you don't want
certian users to see your shares.

 
Answer #5    Answered By: Varick Fischer     Answered On: Apr 03

The reason VS.Net adds that dollar symbol on is because a share name
followed by a $ indicates a hidden share. That is, a share which exists, but
won't show up in network neighborhood. By default, windows creates wwwroot$
when you install IIS.

 
Didn't find what you were looking for? Find more on Opening a Web Application (remote server) Or get search suggestion and latest updates.




Tagged: