How can I delete existing files when deploying an ASP.Net 5 Web App to Azure

Question

I've got a web application in ASP.Net 5 with the source in VS Team Services. Using the Team Services build system, I'd like to deploy it directly to Azure for Continuous Deployment.

I've followed the steps here: https://msdn.microsoft.com/Library/vs/alm/Build/azure/deploy-aspnet5

However, when the website is deployed, only the new files are added and existing ones are overridden. Any deleted files are not removed. This means that extra controllers that were removed during refactoring (for example) still hang around.

Is there a way to force the deployment to wipe out any existing deployed website before putting the new one in place?

I've already run into an issue where the site is unable to deploy due to files being locked. I fixed this by wrapping the publish command in commands to start/stop the site:

Stop-AzureWebsite -Name $websiteName

. $publishScript -publishProperties $publishProperties  -packOutput $packOutput

Start-AzureWebsite -Name $websiteName

In theory I could instead remove and create the website, but that seems a bit heavy handed...

Did you ever figure out how to do this? I have the exact same problem as you. — Dave New, Sep 17 '15 at 06:00
Bruno's answer below (which I've now accepted) seemed to do the trick. The parameter name still doesn't make much sense to me. — Alasdair Ross, Sep 19 '15 at 17:46

score 6 · Answer 1 · answered Aug 19 '15 at 07:54

6

Another option, using the publish profile:

answered Aug 19 '15 at 07:54

ZGFubnk

500
4
13

score 4 · Accepted Answer · edited May 23 '17 at 12:08

4

Add this to your MSBuild parameters:

/p:SkipExtraFilesOnServer=False

Additional parameters here:

Valid Parameters for MSDeploy via MSBuild

edited May 23 '17 at 12:08

Community

1
1

answered Aug 18 '15 at 18:58

Bruno Faria

5,219
3
24
27

How can I delete existing files when deploying an ASP.Net 5 Web App to Azure

2 Answers2

Linked