Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p><em>WebDeploy</em> is definetly the <strong>right</strong> way to deploy web applications.</p> <p>Staring from <em>VS2010</em> targets for running web deploy in simple scenarious are "built-in" into the project files(and msbuild extension files on the PC). Starting from <em>VS2012</em> you can also use <em>Publish Profiles</em> feature which allows storing publish details in a simple file. E.g. you can run something like that:</p> <pre><code>msbuild MyProject.csproj /p:DeployOnBuild=true /p:PublishProfile=&lt;profile-name&gt; /p:Password=&lt;insert-password&gt; /p:VisualStudioVersion=11.0 </code></pre> <p>Which will build the app and publish it using the <code>profile-name</code> publish profile.</p> <ul> <li>Have a look at <a href="http://msdn.microsoft.com/en-us/library/dd465337.aspx" rel="noreferrer">this</a> article's <em>"Creating a Publish Profile"</em> section to know more about creating Publish profiles.</li> <li>Have a look at this <a href="http://sedodream.com/2013/01/06/CommandLineWebProjectPublishing.aspx" rel="noreferrer">post</a> by Sayed Ibrahim Hashimi for reference on publish automation with VS 2012. </li> <li>There's also a good <a href="http://www.troyhunt.com/2010/11/you-deploying-it-wrong-teamcity_11.html" rel="noreferrer">series of blog posts</a> on automating deployments with TeamCity by Troy Hunt (he uses vs2010, so this might be helpful if you are using VS2010)</li> </ul> <p>We were using bat files to run webdeploy commands directly when we were restricted to <em>.NET 3.5</em> and <em>VS2008</em> which didn't have project files web deploy integration.</p> <p>Hope it helps,</p> <p>Ivan</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload