Visual Studio Publish Files
In Visual Studio I am trying to publish an asp.net website to a remote server
I go to Build - Publish website and insert the url http://217.xxx.xxx.x
In the past I have used WS_FTP which requires a username and the password for the site.
However this does not seem to be required in the Visual Studio
If I use the url http://217.xxx.xxx.x then after precompling I get a final error message
The Web server does not appear to have FrontPage Server Extensions installed.
FP extension are installed on this domain
I tried http://217.xxx.xxx.x/domainname.co.uk but still receive the same message.
Can anyone please say what I need to place in the url box to allow me to upload the files to the domain
Thanks
John
I go to Build - Publish website and insert the url http://217.xxx.xxx.x
In the past I have used WS_FTP which requires a username and the password for the site.
However this does not seem to be required in the Visual Studio
If I use the url http://217.xxx.xxx.x then after precompling I get a final error message
The Web server does not appear to have FrontPage Server Extensions installed.
FP extension are installed on this domain
I tried http://217.xxx.xxx.x/domainname.co.uk but still receive the same message.
Can anyone please say what I need to place in the url box to allow me to upload the files to the domain
Thanks
John
ASKER
Thanks for the tutorial but my server is with Fasthosts who have a different method of handling FP extensions ie through a Matrix control.
I found this on the FH website
--------------------------
As the .NET Framework account shares a server with other accounts, you are unable to create an additional IIS application on our Windows servers. To publish a .NET website, you should use FTP software to upload the necessary files.
Visual Studio has a Copy Project option, which requires FrontPage Extensions to be installed on the domain name. This option will not work because FrontPage Extensions require administrator permissions that are not suitable for shared servers. If you have installed FrontPage Extensions, you should uninstall them through the control panel, before FTPing your files.
If you want to upload .NET assembly files (compiled DLL's), you will need to create a directory within htdocs called bin and upload your .DLL files to this directory.
--------------------------
I have uploaded the domain with ftp and its working but very slow to open initially.
Perhaps I have to Build the site locally and then upload with ftp.
I am not familiar with the asp.net Build process but seem to remember reading that once a site was Built you could not loger edit that site. I doubt this is correct but wonder if you can enlighten me further
Regards
John
I found this on the FH website
--------------------------
As the .NET Framework account shares a server with other accounts, you are unable to create an additional IIS application on our Windows servers. To publish a .NET website, you should use FTP software to upload the necessary files.
Visual Studio has a Copy Project option, which requires FrontPage Extensions to be installed on the domain name. This option will not work because FrontPage Extensions require administrator permissions that are not suitable for shared servers. If you have installed FrontPage Extensions, you should uninstall them through the control panel, before FTPing your files.
If you want to upload .NET assembly files (compiled DLL's), you will need to create a directory within htdocs called bin and upload your .DLL files to this directory.
--------------------------
I have uploaded the domain with ftp and its working but very slow to open initially.
Perhaps I have to Build the site locally and then upload with ftp.
I am not familiar with the asp.net Build process but seem to remember reading that once a site was Built you could not loger edit that site. I doubt this is correct but wonder if you can enlighten me further
Regards
John
What type of project did you build? A website project, or a web application?
If it is a website project, nothing is precompiled and the JIT will compile each page into its own .dll at runtime, which is why it's slow initially.
The web application pre-compiles everything into a single .dll file and doesn't need to do that.
The advantage of the web site is you can change a single page and not worry about a thing. But if you make changes to the code (not the aspx) you have to recompile and upload the .dll.
If it is a website project, nothing is precompiled and the JIT will compile each page into its own .dll at runtime, which is why it's slow initially.
The web application pre-compiles everything into a single .dll file and doesn't need to do that.
The advantage of the web site is you can change a single page and not worry about a thing. But if you make changes to the code (not the aspx) you have to recompile and upload the .dll.
ASKER
Sorry ApexCo
I got a bit lost here
Its definitely a website, in this instance its a shopping cart.
However often to open the home page can take a minute which is unacceptable.
I was told that I should publish via VS Build - Publish Website but there seems to be no place in the MS Publish Web Site routine to stipulate the user or password as one would find in sat ws-ftp
Any more ideas please?
Thanks
John
I got a bit lost here
Its definitely a website, in this instance its a shopping cart.
However often to open the home page can take a minute which is unacceptable.
I was told that I should publish via VS Build - Publish Website but there seems to be no place in the MS Publish Web Site routine to stipulate the user or password as one would find in sat ws-ftp
Any more ideas please?
Thanks
John
Np.
If you open the wizard for a new project, you will see a bunch of different things. The one you really want is "ASP.NET Web Application"
If you choose this one, it will pre-compile everything when you build your project. If you don't choose that one, the web server has to recompile on the fly when the page is requested. Make sense now?
So your insane loading time is partly due (most likely anyway) to using a regular "ASP.NET Web Site".
Also, in VS2008 (what version are you on), there is indeed a place to put in the user/pass for the FTP site. Screenshot attached for you to see.
If you open the wizard for a new project, you will see a bunch of different things. The one you really want is "ASP.NET Web Application"
If you choose this one, it will pre-compile everything when you build your project. If you don't choose that one, the web server has to recompile on the fly when the page is requested. Make sense now?
So your insane loading time is partly due (most likely anyway) to using a regular "ASP.NET Web Site".
Also, in VS2008 (what version are you on), there is indeed a place to put in the user/pass for the FTP site. Screenshot attached for you to see.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I am on version 9.0.21022.8RTM
If I go to Build - Publish website I get this, different to yours?
Publish.jpg
If I go to Build - Publish website I get this, different to yours?
Publish.jpg
Click the ellipses on the right of the box with http:? in it.
I know, it's completely retarded, but that's how the did it.... :)
I know, it's completely retarded, but that's how the did it.... :)
ASKER
Thanks so much for the help
I eventually have it working although there looks to be some other problems there and I will no doubt be asking some other questions!
However you answered the question I posed.
Thanks again
John
I eventually have it working although there looks to be some other problems there and I will no doubt be asking some other questions!
However you answered the question I posed.
Thanks again
John
Welcome, and happy to help :)
ASKER
Out of interest I uploaded twice via VS Build Publish Website but found all of the files were not uploaded.
I then published to a local folder on my PC and uploaded with ws-ftp.
The site now works but somewhat slower tha expected
Regards
John
I then published to a local folder on my PC and uploaded with ws-ftp.
The site now works but somewhat slower tha expected
Regards
John
Not sure if you have access to the box, but here is a nice tutorial on how to set it up so you can publish.
http://www.visualwin.com/FPSE/