dotnet build doesn't produce mountable ZIP file

[RyanHill-MSFT]

Steps to reproduce

See https://github.com/fnbk/world/blob/master/README.md. Originated from https://stackoverflow.com/questions/55786610/deploying-zip-file-to-azure-app-services-not-working

Expected behavior

A zip file containing the contents of wwwroot that could then be mountable by az webapp

Actual behavior

ZIP file is created with a folder structure that mimics the directory structure of the intended files. See illustration below.

Environment data

dotnet --info output:

.NET Core SDK (reflecting any global.json):
Version: 2.2.300-preview-010046
Commit: d6f4b3d

Runtime Environment:
OS Name: Windows
OS Version: 10.0.18886
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\2.2.300-preview-010046\

Host (useful for support):
Version: 2.2.4
Commit: f95848e524

[peterhuene]

@vijayrkn is this something the web sdk would own? Seems "web publish" related to me.

[EricHirst-BZ]

I've done workarounds to this in manual deployment scripts by parsing the parameters.xml file that shows up near the root of the archive. A kludge fix would be to have Azure itself do the same to find the content. Unfortunately, all the paths in that file are absolute (C:\MyRepository\foo\bar...) and specific as much to the build environment as to the .zip archive itself. If msbuild could simply add a new documented directory index value at the root of each archive, then I expect Azure could pick that up without any need to change the current archive structure.

I've added some more discussion on this to this Stack Overflow comment.