Skip to content

Commit 21ea0bd

Browse files
ghogenmerriemcgaw
andauthored
Apply suggestions from code review
Co-authored-by: Merrie McGaw <[email protected]>
1 parent 74f8ca3 commit 21ea0bd

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

docs/msbuild/errors/msb3176.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -31,15 +31,15 @@ This article describes the MSB3176 error code.
3131
<!-- :::editable-content name="postOutputDescription"::: -->
3232
## Description
3333

34-
This error refers to minimum required version property you specified for the ClickOnce manifest. See [Choose a ClickOnce update strategy - make updates required](../../deployment/choosing-a-clickonce-update-strategy.md#make-updates-required).
34+
This error refers to the minimum required version property you specified for the ClickOnce manifest. See [Choose a ClickOnce update strategy - make updates required](../../deployment/choosing-a-clickonce-update-strategy.md#make-updates-required).
3535

3636
This error occurs when the version you specified as the minimum required version is greater than the current version you're building.
3737

3838
## Resolution
3939

4040
Check the minimum required version property and change it so that it is less than or equal to the current version. If a user has a version below this version, they are required to update at least to the minimum required version. The minimum version requirement is optional. If you don't want to require a minimum version, you can turn off this setting.
4141

42-
For .NET Core or .NET 5 and later apps, in the Visual Studio **Publish** tool, you can change the minimum required version setting by choosing the **Update settings** link on the **Settings** screen.
42+
For .NET applications, in the Visual Studio **Publish** tool, you can change the minimum required version setting by choosing the **Update settings** link on the **Settings** screen.
4343

4444
:::image type="content" source="./media/msb3176/update-settings.png" alt-text="Screenshot showing the Application Settings screen in Visual Studio, reached from the Update Settings link on the Settings page in the Publish wizard." :::
4545

docs/msbuild/errors/msb3321.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ In order to use a certificate with a private key in a `.pfx` file, it needs to b
4141

4242
If you are building on a machine without Visual Studio installed, such as when setting up a build server, add the Authenticode certificate and private key to the Windows [Trusted Publishers Certificate Store](/windows-hardware/drivers/install/trusted-publishers-certificate-store). You can use [certmgr](/windows-hardware/drivers/devtest/certmgr) to add a certificate to the system store. Once added, it is available to MSBuild when trying to sign an assembly until the certificate expires or is removed.
4343

44-
You can also use *dotnet-mage.exe* or *mage.exe* (Manifest Assembly Generation) to generate and sign ClickOnce manifests. See [Manually deploy a ClickOnce application](../../deployment/walkthrough-manually-deploying-a-clickonce-application.md).
44+
You can also use *dotnet-mage.exe* for .NET projects, or *mage.exe* (Manifest Assembly Generation) for .NET Framework projects to generate and sign ClickOnce manifests. See [Manually deploy a ClickOnce application](../../deployment/walkthrough-manually-deploying-a-clickonce-application.md).
4545

4646
<!-- :::editable-content-end::: -->
4747
<!-- :::ErrorDefinitionDescription-end::: -->

0 commit comments

Comments
 (0)