Publish to Microsoft Azure Website using Web Deploy

 

Documentation is now available on GitHub >>

 

 

2bb6577c3be9919510b0b5e1b14c7debd3f0435cbfc839efbb3233353cd76a2a

Last edited May 6, 2015 at 8:07 AM by mousetraps, version 8

Comments

Jonas_S Jan 13, 2015 at 2:04 PM 
I believe there is a small glitch that causes deployment to azure websites to fail. Please check my blogpost if you experience issues. http://skylore.wordpress.com/2015/01/13/node-js-tools-for-visual-studio-deployment-hiccups/

pacific202 Nov 11, 2014 at 3:49 PM 
I had the exact same issue publishing, the issue has to do with long file names (>260 characters). I renamed my project to a shorter name, then moved my project dir out of C:\Users\[UserName]\Documents\Visual Studio 2013\Projects into c:\vsprojects. I was then able to sync perfectly.

johnhamm Sep 5, 2014 at 8:42 PM 
I created a new "Basic Microsoft Azure Express" application, and tried to publish it to my test Azure website. I get the following error:

"------ Publish started: Project: ExpressApp4, Configuration: Release Any CPU ------
Auto ConnectionString Transformed Web.config into obj\Release\CSAutoParameterize\transformed\Web.config.
Copying all files to temporary location below for package/publish:
obj\Release\Package\PackageTmp.

========== Build: 0 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========
========== Publish: 0 succeeded, 1 failed, 0 skipped =========="

I can publish individual files/folders, except for Web.config and Web.debug.config

I tried with both 1.0 beta 2, and the Aug 13, 2014 dev release. Both result in the same error.

jplane Apr 24, 2014 at 10:04 PM 
Do the settings in web.debug.config replace the need for a separate iisnode.yml file?