Azure-docs: Best practice for creating "Run from package" ZIP missing

[timmkrause]

/p:DeployOnBuild=true /p:WebPublishMethod=Package /p:PackageAsSingleFile=true seems to build the packages like MSDeploy needs it:

This is not how the package should be structured for "Run from package" ZIP deployments.

I think it would make sense to add a section about how to create this package.

My assumption is that msbuild /t:Publish and zipping the output is the right way of achieving this.
Can somebody confirm this?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 4581be64-415a-804a-0a45-25b6976095c3
• Version Independent ID: 0cae0e82-c263-e2cf-ea54-a783291f5746
• Content: Zip push deployment for Azure Functions
• Content Source: articles/azure-functions/deployment-zip-push.md
• Service: azure-functions
• GitHub Login: @ggailey777
• Microsoft Alias: glenga

[KetanChawda-MSFT]

@timmkrause Thank you for posting your question. We will review and provide an update on this.

[KetanChawda-MSFT]

@timmkrause Document states that you have to create a .zip of the function app project folder.

When you are developing on a local computer, it's easy to create a .zip file of the function app project folder on your development computer.

Its just a simple zip of the existing function app project folder

Below are few more articles that you can refer to understand the Run-From-Package command:

https://github.com/Azure/app-service-announcements/issues/110
https://github.com/Azure/app-service-announcements/issues/84
https://docs.microsoft.com/en-us/azure/app-service/deploy-zip

[timmkrause]

I don't think that is a good idea. I should deploy a package where my .csproj and .cs files are included? What if Debug and Release folders are part of the package in a local scenario?

I will go with /t:Publish /p:PublishDir="$(Build.ArtifactStagingDirectory)/MyFunction" and zipping that folder within a build pipeline step. For me it feels like more control and a cleaner ZIP file.

[ggailey777]

@timmkrause you are correct that for a compiled project like C#, the "project root" folder is actually generated in the bin/release folder, and is documented here.

This article doesn't address the msbuild way to do this—assuming that customers are using Visual Studio or Core Tools for publishing, which does this correctly for you. We are working on a Azure DevOps deployment article that should cover this, but in the meantime, I have created an internal work item to track your suggested improvement to this article (1455913).

[ggailey777]

@KetanChawda-MSFT We can #please-close this comment, unless @timmkrause has any further suggestions to improve this article. Thanks Timm!

[timmkrause]

Sounds good, thanks! To me it would make sense to add these two links (maybe other scenarios as well?) to articles/azure-functions/deployment-zip-push.md so that users are aware of what to "Zip deploy".

[KetanChawda-MSFT]

@timmkrause We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.