Deploy with VS needs a major rewrite

[adegeo]

Type of issue

Outdated article

Description

Splitting this off from #41489 @richlander

First, the article is talking about deploying, but this really is publishing. Second, the entire deploy vs publish story is a mess here. There is another article about publishing with the CLI, that needs an update too. Third, both articles are named deploy* as well as the parent folder, this probably should change to publish*.

We need to refocus this area on publishing and create a new article about common deployment scenarios.

How do I deploy to:

• Azure Functions
• Containers
• Archive (Zip for example) to be downloaded and run
• Storefronts?
• Other?

Another issue that was discussing some related info is #17757

Related issue: #53183 make sure to call out that the same self-contained option should be used on build if publish --no-build is used so you don't get a mixed framework-dependent self-contained output.

Page URL

https://learn.microsoft.com/en-us/dotnet/core/deploying/?tabs=vs156

Content source URL

https://github.com/dotnet/docs/blob/main/docs/core/deploying/index.md

Document Version Independent Id

559262e6-f27b-e581-255f-0967b006a922

Platform Id

4eecb109-a22d-e57a-2de4-e07a215b94ae

Article author

@adegeo

Metadata

• ID: 50511188-600e-18f6-6d92-c93b135d3db6
• PlatformId: 4eecb109-a22d-e57a-2de4-e07a215b94ae
• Service: dotnet-fundamentals

Related Issues

---

Associated WorkItem - 486554