From 3923ec06fe892c5814fddc9ca039e894df631388 Mon Sep 17 00:00:00 2001 From: Kevin B Date: Sat, 2 Mar 2024 13:46:18 -0800 Subject: [PATCH] Removing culture specific Microsoft links --- docs/contributing/compiling.mdx | 4 ++-- docs/distributing/github-actions.mdx | 2 +- docs/packaging/rid.mdx | 2 +- docs/packaging/signing.mdx | 4 ++-- 4 files changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/contributing/compiling.mdx b/docs/contributing/compiling.mdx index 57285ab..4a4879d 100644 --- a/docs/contributing/compiling.mdx +++ b/docs/contributing/compiling.mdx @@ -10,8 +10,8 @@ It is made up of: In order to test the project, you need to build the Rust binaries before compiling dotnet. ### Prerequisites - - [.NET 6 SDK](https://dotnet.microsoft.com/en-us/download/dotnet/6.0) - - [.NET 8 SDK](https://dotnet.microsoft.com/en-us/download/dotnet/8.0) + - [.NET 6 SDK](https://dotnet.microsoft.com/download/dotnet/6.0) + - [.NET 8 SDK](https://dotnet.microsoft.com/download/dotnet/8.0) - [Rust / Cargo](https://www.rust-lang.org/tools/install) - `dotnet tool install -g dotnet-coverage` - `dotnet tool install -g nbgv` diff --git a/docs/distributing/github-actions.mdx b/docs/distributing/github-actions.mdx index 4bc8403..e37207a 100644 --- a/docs/distributing/github-actions.mdx +++ b/docs/distributing/github-actions.mdx @@ -70,7 +70,7 @@ You can publish without the self-contained flag if using Velopack to install suc configuration to `Release` mode, `-o` to set the output directory to `publish`, `-r` to set the runtime to `win-x64` for distributing on 64-bit Windows, and `--self-contained` to publish the .NET runtime with the application. Adapt this command to your needs. You can learn more about -`dotnet publish` in the [Microsoft Documentation](https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-publish). +`dotnet publish` in the [Microsoft Documentation](https://learn.microsoft.com/dotnet/core/tools/dotnet-publish). ```yml - name: Publish Application diff --git a/docs/packaging/rid.mdx b/docs/packaging/rid.mdx index 8461664..34af36d 100644 --- a/docs/packaging/rid.mdx +++ b/docs/packaging/rid.mdx @@ -19,4 +19,4 @@ On MacOS, the RID (min version and arch) is just stored as metadata in the `.pkg #### Also read - [Windows 10 version history](https://en.wikipedia.org/wiki/Windows_10_version_history) - [Windows 11 version history](https://en.wikipedia.org/wiki/Windows_11_version_history) -- [.NET RID Catalog](https://learn.microsoft.com/en-us/dotnet/core/rid-catalog) +- [.NET RID Catalog](https://learn.microsoft.com/dotnet/core/rid-catalog) diff --git a/docs/packaging/signing.mdx b/docs/packaging/signing.mdx index 3e75519..69481d4 100644 --- a/docs/packaging/signing.mdx +++ b/docs/packaging/signing.mdx @@ -13,7 +13,7 @@ Here is the general rule of thumb for Windows Defender/Smart Screen warnings: - You sign your code with an EV certificate. People never get warnings. ### Acquiring a code signing certificate -First, you need to acquire a code-signing certificate from a reputable brand. Microsoft lists the following trusted issuers [in their documentation](https://learn.microsoft.com/en-us/windows-hardware/drivers/dashboard/code-signing-cert-manage): +First, you need to acquire a code-signing certificate from a reputable brand. Microsoft lists the following trusted issuers [in their documentation](https://learn.microsoft.com/windows-hardware/drivers/dashboard/code-signing-cert-manage): - [Certum](https://shop.certum.eu/data-safety/code-signing-certificates/certum-ev-code-sigining.html) - [SSL.com](https://www.ssl.com/certificates/ev-code-signing/) @@ -50,7 +50,7 @@ Then now with `--signParams` it would be: vpk pack ... --signParams "/td sha256 /fd sha256 /f yourCert.pfx /tr http://timestamp.comodoca.com" ``` -If you are new to using `signtool.exe`, you can check the [command line reference here](https://learn.microsoft.com/en-us/dotnet/framework/tools/signtool-exe). I recommend getting signing working on a single binary first, using `signtool.exe`, before trying to get things working with the Velopack CLI. +If you are new to using `signtool.exe`, you can check the [command line reference here](https://learn.microsoft.com/dotnet/framework/tools/signtool-exe). I recommend getting signing working on a single binary first, using `signtool.exe`, before trying to get things working with the Velopack CLI. If you are using a USB / HSM and have the following signing error `Error: SignerSign() failed." (-2147023673/0x800704c7)`, this means that you are missing a password / unlock token. This can be added to your signing command with the `/csp /k` parameters. [[Read more]](https://stackoverflow.com/questions/17927895/automate-extended-validation-ev-code-signing-with-safenet-etoken/54439759#54439759)