DEPLOYING a visual studio 2005 project to my WEB SITE

I am having difficulty following the instructions in knowledge base article 10364 for deploying my 'web application project' authored with visual studio 2005 from my computer to my dicountasp,net web server.

I open my we application project in visual studio 2005. The the article asks to go to web site. What web site? I opened the project in Visual studio. There is no copy web site or copy tab or connect button. How do I go about deploying my project?

Chaarlie

 

1) Open your local Web site in VS 2005. (File System option)


2) From the main toolbar click on Website. (File, Edit, Build, Website...)


3) Click on Copy Web Site...


4) At the top click on Connect.


5) In the Open Web Site dialog click on FTP Site, left side.


From there enter the information for your DASP account.
Then click Open, at the bottom of that dialog.


You will now see your local site on the left and your remote site on the right.

 

THANKS,YOUR REPLY WAS MOST HELPFUL.

 

I created a web app using VWD2005 Express Edition adn uploaded my files onto this hosting server. I added a SQL database (and also paid to have that addon on my account) to my project which by default is stored in the App_Data folder which I of course also uploaded onto the server. However, when I test my app online (having tested it many times on my local machine successfully) I submit the form and the 'error.aspx' page I created pops up telling me the message that I had written on that page. Therefore apparently no conection was established and no entries were added to the db.
Any clues??? truly appreciate any help. Thx.

 

Hello Bruce... as a beginner developer, this sounds a little advanced to me so I've taken the liberty of posting my WEB.CONFIG code below so that you please point out what I have to do....
I'd appreciate it very much..
Thx.
Rod.





<!--
Note: As an alternative to hand editing this file you can use the
web admin tool to configure settings for your application. Use
the Website->Asp.Net Configuration option in Visual Studio.
A full list of settings and comments can be found in
machine.config.comments usually located in
\Windows\Microsoft.Net\Framework\v2.x\Config
-->
<configuration>
<appSettings/>
<connectionStrings>
<add name='commentsConnectionString1' connectionString='Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\comments.mdf;Integrated Security=True;User Instance=True'
providerName='System.Data.SqlClient' />
</connectionStrings>
<system.web>
<!--
Set compilation debug='true' to insert debugging
symbols into the compiled page. Because this
affects performance, set this value to true only
during development.
-->
<customErrors defaultRedirect='' />
<roleManager enabled='true' />
<compilation debug='true'/>
<!--
The <authentication> section enables configuration
of the security authentication mode used by
ASP.NET to identify an incoming user.
-->
<authentication mode='Forms' />
<!--
The <customErrors> section enables configuration
of what to do if/when an unhandled error occurs
during the execution of a request. Specifically,
it enables developers to configure html error pages
to be displayed in place of a error stack trace.

<customErrors mode='RemoteOnly' defaultRedirect='GenericErrorPage.htm'>
<error statusCode='403' redirect='NoAccess.htm' />
<error statusCode='404' redirect='FileNotFound.htm' />
</customErrors>
-->
</system.web>
<system.net>
<mailSettings>
<smtp from=''>
<network host='' password='' userName='' />
</smtp>
</mailSettings>
</system.net>
</configuration>

 

Hi Rod,
We can get you through this, will just take a few steps so don't worry.

Your web.config will work fine locally but not for your remote SQL Server.
To get your data connection refer to the connection string shown in your control panel SQL Server section.
If you can't figure it out don't worry just post it here but comment out the password then I'll write it up for you as needed.

For the KB articles related to this please look at this:
http://iis7testcom.web701.discountasp.net/membershipprovider/

As I catch up on things I'll keep making that easier to follow and more informative.
I'm here to help.
Salute,
Mark

 

If the website is large, I recommend publishing to a local directory then transferring the files to the server manually using a separate FTP client like FileZilla.

VS can be really slow to transfer the files compared to a dedicated FTP client. I think it has to do with the how many concurrent transfers it does.