We are building a .NET 4.5 Web API application using the declarative pipelines syntax to issue bat commands calling msbuild /t:clean, build, and package on a Windows 10 slave VM. 

Package step creates a directory of publishable files at: ./obj/{config}/Package/PackageTmp

Final step of the pipeline uses the azureWebAppPublish plugin to publish this directory to Azure Web Site. Publish step reports successful, but when looking at the wwwroot/bin folder on the published site, some DLLs have a 0 byte file size. For example, in the build server's PackageTmp folder, A.Library.DLL has file size 1124 KB, but after deploying via the plugin, A.Library.DLL has file size 0 bytes in Azure.

Also noticed that the .azure-deploy GIT folder responsible for pushing the deploy files to Azure master contains some unstaged publish files after the pipeline has completed, one of which is the affected A.Library.DLL.

Azure Web App Publish Step:

azureWebAppPublish azureCredentialsId: params.azure_credential_id,					resourceGroup: params.resource_group, appName: params.service_name, sourceDirectory: "/obj/${params.build_mode}/Package/PackageTmp"

x