How to upload files from VS 2008?

I am trying to upload my files so that my site can become live.

I tried using VS 2008's Website | Copy Website | Connect | Remote Site, and entering my site's URL, but I get, "Unable to open the Web site '<my URL." The Web server does not appear to have FrontPage Server extensions installed."

So, I looked at the FAQs. There is one entitled, "How do I deploy a Visual Studio .NET web project from my local computer to your server?" with information specific to VS .NET 2002 and 2003. But there is this:

IMPORTANT NOTE: The following method applies to Visual Studio .NET 2002 and 2003. If you use Visual Studio .NET 2005, please see this Knowledge Base article.

When I click on the "this Knowledge Base article" link, I go to an Administrator Login screen. However, neither the Discountasp.net Username and password that I was provided with nor my customary username and password work.

So, can anybody tell me what I must do to upload my files?

 

OK, I figured it out--log into the Control Panel, go to IIS settings, and install FrontPage Extensions.


Thereafter, I was able to upload my files. How long does it take for the site to become visible, though? It's obviously not instantaneous--either that, or I did something wrong, as the discountasp.net page is still showing (index.htm).

 

In your Control Panel you can assign default pages.
This gives you two options for the index.htm

1. Remove it or replace it with your own.
2. Disable index.htm in the Control Panel as a default page then make sure your default page is enabled.

Hope that helped, if not let me know.
Salute,
Mark

 

In Visual Web Developer 2008 go to the Solution Explorer Window. (this will be on the right side of your computer screen)

Righ click at the top of the tree then select Add exsisting item from the menu. A new window of your compter strucure will popup. Highlight the files that you want to upload then press the add button

Mike

 

Hi,
I'd suggest you stick with the Copy Website feature in VS.
For both VS2005 and VS2008.

In both VS2005 and VS2008 creating a Website and a Web Application are not the same.
They both deploy diferently also.
Web site VS. Web Application:
http://www.codersbarn.com/post/2008/06/ASPNET-Web-Site-versus-Web-Application-Project.aspx

When you transfer files to your DASP server don't use a folder directive.
Just use your FTP or Alt FTP, your username and your ftp password.

Applications for folders exist for your site root, that is the default application pool.
You add more as needed, for ASP.NET or Classic ASP.
There are tons of reasons for adding additional applications for folders on your site...
However they are not required since you root exists. These can be added to it.

Even though the ASP.NET features work so well there are reasons to use the components DASP provides.
Something I like is the filtering, progress indicators, directives, etc.
I've used both here.
If I set it up so a user can upload a 3D file or image the ASP.NET features work fine.
But if I want the user to have the ability to upload a series of large compressed files I like to use the components.
Point is, DASP allows us to use what works best in our sites.
Salute,
Mark

 

I am using VS 2008 and just right click on the project name and choose "Publish...". On the screen that appears, press the "..." button to the right of the Target Location text box, choose FTP Site. I then configured the FTP settings and the site is published just fine.


One weird thing is that the site published and changes were visible instantly upon browsing to the site. The weird thing was that the published files did not appear in FileZilla till 5 minutes or so later.


Does anyone have any advice on whether this is the best way to publish? Is it better to enable FrontPage extensions? I read that it was possible to publish over SSL using this method, which would be cool to not be sending my password in clear text.


Why does the system automatically root your website in the /<username>/ folder? Why can't this folder be deleted? What can you do with the root folder above it?Is there some advantage to creating additional folders? I understand you can create additional folders and activate them as web applications. How would one access these additional applications via code or via the web?


Also, another random question: Why does DASP offer the ASPUpload component when it appears that the standard, built in <asp:FileUpload component seems to work just fine?


Thanks for any answers to the newbie questions. Glad to be a new customer!

 

Hi,
Are you on an IIS7 server here?
If so, check your FTP username, it's not the same as your account username.
I've attached an image of the settings I use for the IIS7 test server.
Salute,
Mark

Note: Notice that I'm also using the alternate FTP site rather than the ftp domain.
You can continue to do that but you have to do it at first, until your domain resolves.

 

Thanks Man! it worked!! It is aliveeee!!

 

Hello,


I just developed my first asp.net website using Visual Web Developer 2008 and my client needs the website to be "alive" asap, I am having trouble connecting to the ftp site. I tried COPY WEBSITE | CONNECT |FTP SITE and entered my Domain name in the "server" and the ftp username and ftp password, I tried checking and unchecking the passive mode.... I've tried pretty much everything..! Somebody help me please..


thanks

 

Congrats (Glad you got it working.)

 

I am still experiencing problem, I tried FireFTP and kept on getting 530. I am using alternative ftp host.


220-Microsoft FTP Service
220 DiscountASP.net FTP
USER 0081260|livesyncus0
331 Password required for 0081260|livesyncus0.
PASS (password not shown)
530 User cannot log in.
Unable to make a connection. Please try again.

 

Wow, thanks. For anyone else who stumbles on this thread - get your FTP username in the control panel under 'Account Info/Edit' link (top option on the left). I love simple answers to otherwise maddening problems.

 

any and all of my transfers from visual [studio|web] [pro|express] [2005|2008] to our ftp site hang indefinitely.

i can connect to the host via primary ftp, then it hangs ~ i hit escape to cancel and there's my directory (as if i'm connected). alt ftp the same. viewing any files from the server causes an indefinite hang in the app until i again hit escape.

i tried this on visual webdev 2005 express, vwebdev 2008ex, and, thinking it was express' fault, i went ahead and got vsp2k8. all same problems. i believe the passwords match ~ tried active/passive xfers.

anyone you can see anything i can't?

Post Edited (russ stranger) : 1/13/2009 5:34:53 AM GMT

 

...The only Tip I have, other than DASP Support, is try it with 'Copy Website' and making sure 'Use Passive mode' is not checked.
There are still some known issues with VS2005 and VS2008 and Passive mode.

If you want me to try connecting and publishing a test file PM me with the account details and I'll give it a shot for you.
Salute,
Mark

Technical Evangelist for DiscountASP.NET

http://www.iis7test.com/webcasts/
http://weblogs.asp.net/markwisecarver/
http://blogs.windowsclient.net/wisecarver/default.aspx

 

Mark -


Thanks very much for your reply. I finally figured it out. It's related to the way that VS 2008 handles the FTP credentials, I think. The trick is to embed your FTP username and password inside the ftp address.


Here is how I can successfully use theVS 2008 Build/Publish Web Site menu command to publish a web site to my DASP account in about 4 - 5 seconds:


1. Click Build/Publish Web Site


2. In the left panel of dialog, click on File System (rather than FTP)


3. For Target Location: ftp://myControlPanelUsername:[email protected]/


4. Then check the box Allow this precompiled site to be updatable.(I'm not sure this is necessary.)


5. Click OK.


This successfully published my small HelloWorld website in about 4 seconds.





Polybius

 

I'm having the same problem.


I just opened up a new account here at DASP (IIS 6). I'm using VS 2008. I have a tiny HelloWorld testwebsite that I'm trying to deploy to DASP. It hangs indefinitely whether I use "WebSite/Copy Website" or "Build/Publish Web Site".


It seems to me that there may be a settings problem at DASP.


I do know that I have another account here at DASP (.NET 2.0) that I've had for a couple of years. For that account, I use VS 2005 "Build/Publish Web Site" to deploy, and it works smoothly and very quickly, very easy.


But my new account (.NET 3.5) is proving to be another matter. It seems to me there may be a setting on the DASP server that needs adjustment. My HelloWorld is just a simple tiny website with 2 simple pages, that should take only1 or2 seconds to deploy, but instead it just hangs and hangs, and after maybe 5-10 minutes, maybe aone of the pagesgets created at the target location.


Any ideas anybody?


Polybius