-
Notifications
You must be signed in to change notification settings - Fork 25.1k
Description
after the various examples of dotnet publish command usage, there is a small section which is very confusing
_In the preceding examples:
dotnet publish and dotnet build support Kudu APIs to publish to Azure from any platform. Visual Studio publish supports the Kudu APIs, but it's supported by WebSDK for cross-platform publish to Azure.
Don't pass DeployOnBuild to the dotnet publish command._
For example - it states don't pass deployonbuild - then why is are examples of it shown?
the sentence about visual studio and websdk and kudu is very confusing - "but it's supported by webSDK..." - what is supported by webSDK - what is webSDK.
there should also be examples on what to pass to the p:PublishProfile parameter - is it a relative path to a pubxml file, or is it absolute, do we include the pubxml extension etc.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
- ID: 684d1f55-3d8b-9ba6-ee65-e8f84c2b4244
- Version Independent ID: 2db330b4-e830-715f-0a15-e406f85e1d3b
- Content: Visual Studio publish profiles (.pubxml) for ASP.NET Core app deployment
- Content Source: aspnetcore/host-and-deploy/visual-studio-publish-profiles.md
- Product: aspnet-core
- Technology: aspnetcore-hostdeploy
- GitHub Login: @Rick-Anderson
- Microsoft Alias: riande