Skip to content

Commit 74a2221

Browse files
adegeogewarren
adegeo
and
gewarren
authored
Clarify the publishing articles by removing "deploy" where appropriate and merge similar info (#47079)
* Temp * Temp * final updates * Minor * Rename and rewrite * Redirect, TOC, links * Temp * Almost final draft of rewriting the publishing intro article. * Reset copilot * Extra descriptions * Move cli parameters to include * move table * Change header to bold * Fix bugs * Add info about FDD lookups * Remove my temp code * Fix indentation * Add container * Handle what acro I can... * Fix cross links to publishing * Redirect deploy/publish articles * Fix other links * Remove sample code no longer unsed * More bookmark changes * fix redirect * Fix links; link to tutorials * Fix that link that snuck through! * ugh * Apply suggestions from code review Co-authored-by: Genevieve Warren <24882762+gewarren@users.noreply.github.com> --------- Co-authored-by: Genevieve Warren <24882762+gewarren@users.noreply.github.com>
1 parent e122129 commit 74a2221

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

43 files changed

+507
-746
lines changed

‎.openpublishing.redirection.core.json

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -386,6 +386,14 @@
386386
"source_path_from_root": "/docs/core/deploying/applications.md",
387387
"redirect_url": "/dotnet/core/deploying/index"
388388
},
389+
{
390+
"source_path_from_root": "/docs/core/deploying/deploy-with-cli.md",
391+
"redirect_url": "/dotnet/core/deploying/index"
392+
},
393+
{
394+
"source_path_from_root": "/docs/core/deploying/deploy-with-vs.md",
395+
"redirect_url": "/dotnet/core/deploying/index"
396+
},
389397
{
390398
"source_path_from_root": "/docs/core/deploying/fixing-warnings.md",
391399
"redirect_url": "/dotnet/core/deploying/trimming/fixing-warnings",

‎docs/architecture/microservices/multi-container-microservice-net-applications/multi-container-applications-docker-compose.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -457,7 +457,7 @@ The .NET team provides some basic variants in [dotnet/](https://hub.docker.com/r
457457
- **sdk**: for development and build scenarios
458458
- **aspnet**: for ASP.NET production scenarios
459459
- **runtime**: for .NET production scenarios
460-
- **runtime-deps**: for production scenarios of [self-contained applications](../../../core/deploying/index.md#publish-self-contained)
460+
- **runtime-deps**: for production scenarios of [self-contained applications](../../../core/deploying/index.md#self-contained-deployment)
461461

462462
For faster startup, runtime images also automatically set aspnetcore\_urls to port 80 and use Ngen to create a native image cache of assemblies.
463463

‎docs/core/compatibility/sdk/6.0/apphost-generated-for-macos.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ ms.date: 07/13/2021
55
---
66
# Generate apphost for macOS
77

8-
When building on macOS, the .NET SDK now [produces an executable](../../../deploying/index.md#produce-an-executable) for app projects.
8+
When building on macOS, the .NET SDK now produces an executable for app projects.
99

1010
Since .NET Core 3.0, the .NET SDK has created an executable for app projects when building on non-macOS operating systems. However, it did not create an executable on macOS since we weren't signing this binary. That resulted in an app that was recognized as dangerous by the OS, which made it hard for the user to run it. The .NET 6 SDK can sign the app executable, so it now produces the executable by default.
1111

‎docs/core/compatibility/sdk/8.0/arch-option.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ ms.date: 10/05/2023
55
---
66
# --arch option doesn't imply self-contained
77

8-
Up until now, the `--arch` option for `dotnet` CLI commands such as [dotnet publish](../../../tools/dotnet-publish.md) implied that the app was [self-contained](../../../deploying/index.md#publish-self-contained). The behavior of the `--arch` option has now been changed to match that of the `--runtime` option, and it no longer implies that an app is self-contained.
8+
Up until now, the `--arch` option for `dotnet` CLI commands such as [dotnet publish](../../../tools/dotnet-publish.md) implied that the app was [self-contained](../../../deploying/index.md#self-contained-deployment). The behavior of the `--arch` option has now been changed to match that of the `--runtime` option, and it no longer implies that an app is self-contained.
99

1010
## Previous behavior
1111

‎docs/core/compatibility/sdk/8.0/runtimespecific-app-default.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ ms.date: 06/05/2023
55
---
66
# Runtime-specific apps no longer self-contained
77

8-
Runtime-specific apps, or .NET apps with a `RuntimeIdentifier`, are no longer [self-contained](../../../deploying/index.md#publish-self-contained) by default. Instead, they are [framework-dependent](../../../deploying/index.md#publish-framework-dependent) by default.
8+
Runtime-specific apps, or .NET apps with a `RuntimeIdentifier`, are no longer [self-contained](../../../deploying/index.md#self-contained-deployment) by default. Instead, they are [framework-dependent](../../../deploying/index.md#framework-dependent-deployment) by default.
99

1010
This is a breaking change in the following situations:
1111

‎docs/core/deploying/deploy-with-cli.md

Lines changed: 0 additions & 175 deletions
This file was deleted.

0 commit comments

Comments
 (0)