msbuild - Visual Studio Online continuous deployment to Azure Website with publish profile -



msbuild - Visual Studio Online continuous deployment to Azure Website with publish profile -

i using visual studio online deploy project continuously after ci build pass. have utilize publish profile build production web.config transform deployed website using production db instead of dev db. have followed scott hanselman's blog post add together msbuild arguments in ci build definition. arguments this:

/p:deployonbuild=true /p:publishprofile=[publish profile name] /p:allowuntrustedcertificate=true /p:username=[credentials obtained azure website portal] /p:password=[from portal well]

it seems working, deployed website using production db now.

then noticed in ci build definition under deployment section, there 1 parameter called: path deployment settings. this article, says:

"the path .pubxml file website, relative root folder of repo. ignored cloud services."

which want. removed msbuild arguments, set path deployment settings select pubxml file in popup, , give try.

however, nice , simple way doesn't work @ all. if pointing same pubxml file, , both ways got greenish ci builds, later 1 seems still utilize default web.config not transformed 1 after deployment.

so curious if know difference between publishprofile in msbuild arguments , path deployment settings? using right way this?

i had same problem. found "path deployment settings" sets msbuild parameter "/p:publishprofilepath". can see in diagnostic log of build. i'm not sure publishprofilepath parameter though.

but got transforms working different way. in "build" section, set "configurations" utilize release configuration. publishing through vso build seems apply transform config.

msbuild azure-web-sites visual-studio-online continuous-deployment publish-profiles

Comments

Popular posts from this blog

formatting - SAS SQL Datepart function returning odd values -

c++ - Apple Mach-O Linker Error(Duplicate Symbols For Architecture armv7) -

php - Yii 2: Unable to find a class into the extension 'yii2-admin' -