dotnet · adegeo · Dec 27, 2022 · Dec 23, 2022
@@ -26,7 +26,7 @@ Typically, applications need to support some or all of the following scenarios:
 
 In each of these scenarios, the exposed functionality needs to be secured against unauthorized use. At a minimum, this typically requires authenticating the user or principal making a request for a resource. This authentication may use one of several common protocols such as SAML2p, WS-Fed, or OpenID Connect. Communicating with APIs typically uses the OAuth2 protocol and its support for security tokens. Separating these critical cross-cutting security concerns and their implementation details from the applications themselves ensures consistency and improves security and maintainability. Outsourcing these concerns to a dedicated product like IdentityServer helps the requirement for every application to solve these problems itself.
 
-IdentityServer provides middleware that runs within an ASP.NET Core application and adds support for OpenID Connect and OAuth2 (see [supported specifications](https://docs.identityserver.io/en/latest/intro/specs.html)). Organizations would create their own ASP.NET Core app using IdentityServer middleware to act as the STS for all of their token-based security protocols. The IdentityServer middleware exposes endpoints to support standard functionality, including:
+IdentityServer provides middleware that runs within an ASP.NET Core application and adds support for OpenID Connect and OAuth2 (see [supported specifications](https://docs.duendesoftware.com/identityserver/v6/overview/specs/)). Organizations would create their own ASP.NET Core app using IdentityServer middleware to act as the STS for all of their token-based security protocols. The IdentityServer middleware exposes endpoints to support standard functionality, including:
 
 - Authorize (authenticate the end user)
 - Token (request a token programmatically)
@@ -97,13 +97,13 @@ public class Startup
 
 ## JavaScript clients
 
-Many cloud-native applications use server-side APIs and rich client single page applications (SPAs) on the front end. IdentityServer ships a [JavaScript client](https://docs.identityserver.io/en/latest/quickstarts/4_javascript_client.html) (`oidc-client.js`) via NPM that can be added to SPAs to enable them to use IdentityServer for sign in, sign out, and token-based authentication of web APIs.
+Many cloud-native applications use server-side APIs and rich client single page applications (SPAs) on the front end. IdentityServer ships a [JavaScript client](https://docs.duendesoftware.com/identityserver/v6/quickstarts/js_clients/) (`oidc-client.js`) via NPM that can be added to SPAs to enable them to use IdentityServer for sign in, sign out, and token-based authentication of web APIs.
 
 ## References
 
-- [IdentityServer documentation](https://docs.identityserver.io/en/latest/)
+- [IdentityServer documentation](https://docs.duendesoftware.com/identityserver/v6/)
 - [Application types](/azure/active-directory/develop/app-types)
-- [JavaScript OIDC client](https://docs.identityserver.io/en/latest/quickstarts/4_javascript_client.html)
+- [JavaScript OIDC client](https://docs.duendesoftware.com/identityserver/v6/quickstarts/js_clients/)
 
 >[!div class="step-by-step"]
 >[Previous](azure-active-directory.md)

@@ -360,9 +360,6 @@ The reference app uses [MediatR](https://github.com/jbogard/MediatR) to propagat
 - **Jimmy Bogard. Strengthening your domain: Domain Events** \
   <https://lostechies.com/jimmybogard/2010/04/08/strengthening-your-domain-domain-events/>
 
-- **Tony Truong. Domain Events Pattern Example** \
-  <https://www.tonytruong.net/domain-events-pattern-example/>
-
 - **Udi Dahan. How to create fully encapsulated Domain Models** \
   <https://udidahan.com/2008/02/29/how-to-create-fully-encapsulated-domain-models/>
 

@@ -103,9 +103,6 @@ items:
       tocHref: /dotnet/framework/
       topicHref: /dotnet/framework/index
       items:
-      - name: Add-ins and extensibility
-        tocHref: /dotnet/framework/add-ins/
-        topicHref: /dotnet/framework/add-ins/index
       - name: Additional APIs
         tocHref: /dotnet/framework/additional-apis/
         topicHref: /dotnet/framework/additional-apis/index
@@ -445,7 +442,7 @@ items:
           topicHref: /dotnet/csharp/language-reference/proposals/csharp-7.0/index
         - name: C# 7.1 feature specifications
           tocHref: /dotnet/csharp/language-reference/proposals/csharp-7.1/
-          topicHref: /dotnet/csharp/language-reference/proposals/csharp-7.1/index
+          topicHref: /dotnet/csharp/language-reference/proposals/csharp-7.1/infer-tuple-names
         - name: C# 7.2 feature specifications
           tocHref: /dotnet/csharp/language-reference/proposals/csharp-7.2/
           topicHref: /dotnet/csharp/language-reference/proposals/csharp-7.2/index

@@ -5,13 +5,13 @@ ms.date: 02/15/2022
 ---
 # Globalization APIs use ICU libraries on Windows 10
 
-.NET 5 and later versions use [International Components for Unicode (ICU)](http://site.icu-project.org/home) libraries for globalization functionality when running on Windows 10 May 2019 Update or later.
+.NET 5 and later versions use [International Components for Unicode (ICU)](https://icu.unicode.org/) libraries for globalization functionality when running on Windows 10 May 2019 Update or later.
 
 ## Change description
 
 In .NET Core 1.0 - 3.1 and .NET Framework 4 and later, .NET libraries use [National Language Support (NLS)](/windows/win32/intl/national-language-support) APIs for globalization functionality on Windows. For example, NLS functions were used to compare strings, get culture information, and perform string casing in the appropriate culture.
 
-Starting in .NET 5, if an app is running on Windows 10 May 2019 Update or later, .NET libraries use [ICU](http://site.icu-project.org/home) globalization APIs, by default.
+Starting in .NET 5, if an app is running on Windows 10 May 2019 Update or later, .NET libraries use [ICU](https://icu.unicode.org/) globalization APIs, by default.
 
 > [!NOTE]
 > Windows 10 May 2019 Update and later versions ship with the ICU native library. If the .NET runtime can't load ICU, it uses NLS instead.

@@ -5,15 +5,15 @@ ms.date: 09/01/2022
 ---
 # Globalization APIs use ICU libraries on Windows Server
 
-.NET 7 and later versions use [International Components for Unicode (ICU)](http://site.icu-project.org/home) libraries for globalization functionality when running on Windows Server 2019 or later. (Non-server Windows versions have already been [using ICU since .NET 5](../5.0/icu-globalization-api.md).)
+.NET 7 and later versions use [International Components for Unicode (ICU)](https://icu.unicode.org/) libraries for globalization functionality when running on Windows Server 2019 or later. (Non-server Windows versions have already been [using ICU since .NET 5](../5.0/icu-globalization-api.md).)
 
 ## Previous behavior
 
 In .NET 5 and .NET 6, the .NET libraries used [National Language Support (NLS)](/windows/win32/intl/national-language-support) APIs for globalization functionality on Windows Server 2019. For example, NLS functions were used to compare strings, get culture information, and perform string casing in the appropriate culture.
 
 ## New behavior
 
-Starting in .NET 7, if an app is running on Windows Server 2019 or later, .NET libraries use [ICU](http://site.icu-project.org/home) globalization APIs, by default. (Non-server Windows versions have already been [using ICU since .NET 5](../5.0/icu-globalization-api.md), so there is no change for these versions.)
+Starting in .NET 7, if an app is running on Windows Server 2019 or later, .NET libraries use [ICU](https://icu.unicode.org/) globalization APIs, by default. (Non-server Windows versions have already been [using ICU since .NET 5](../5.0/icu-globalization-api.md), so there is no change for these versions.)
 
 ## Behavioral differences
 

@@ -45,7 +45,7 @@ Discusses the first stage of creating a world-ready application, which involves
 
 [.NET globalization and ICU](globalization-icu.md)
 
-Describes how .NET globalization uses [International Components for Unicode (ICU)](http://site.icu-project.org/home).
+Describes how .NET globalization uses [International Components for Unicode (ICU)](https://icu.unicode.org/).
 
 [Localizability review](localizability-review.md)
 

@@ -14,7 +14,7 @@ helpviewer_keywords:
 
 # .NET globalization and ICU
 
-Before .NET 5, the .NET globalization APIs used different underlying libraries on different platforms. On Unix, the APIs used [International Components for Unicode (ICU)](http://site.icu-project.org/home), and on Windows, they used [National Language Support (NLS)](/windows/win32/intl/national-language-support). This resulted in some behavioral differences in a handful of globalization APIs when running applications on different platforms. Behavior differences were evident in these areas:
+Before .NET 5, the .NET globalization APIs used different underlying libraries on different platforms. On Unix, the APIs used [International Components for Unicode (ICU)](https://icu.unicode.org/), and on Windows, they used [National Language Support (NLS)](/windows/win32/intl/national-language-support). This resulted in some behavioral differences in a handful of globalization APIs when running applications on different platforms. Behavior differences were evident in these areas:
 
 - Cultures and culture data
 - String casing

@@ -217,7 +217,7 @@ For more information, see [Implement a custom logging provider in .NET](custom-l
 Here are some third-party logging frameworks that work with various .NET workloads:
 
 - [elmah.io](https://elmah.io) ([GitHub repo](https://github.com/elmahio/Elmah.Io.Extensions.Logging))
-- [Gelf](https://docs.graylog.org/en/2.3/pages/gelf.html) ([GitHub repo](https://github.com/mattwcole/gelf-extensions-logging))
+- [Gelf](https://go2docs.graylog.org/5-0/getting_in_log_data/ingest_gelf.html) ([GitHub repo](https://github.com/mattwcole/gelf-extensions-logging))
 - [JSNLog](http://jsnlog.com) ([GitHub repo](https://github.com/mperdeck/jsnlog))
 - [KissLog.net](https://kisslog.net) ([GitHub repo](https://github.com/catalingavan/KissLog-net))
 - [Log4Net](https://logging.apache.org/log4net) ([GitHub repo](https://github.com/apache/logging-log4net))

@@ -45,7 +45,7 @@ The features that have been implemented in C# versions after 6.0, including thos
  [C# 7.0 Specification Proposals](~/_csharplang/proposals/csharp-7.0/pattern-matching.md)  
  There are a number of new features implemented in C# 7.0. They include pattern matching, local functions, out variable declarations, throw expressions, binary literals, and digit separators. This folder contains the specifications for each of those features.
 
- [C# 7.1 Specification Proposals](~/_csharplang/proposals/csharp-7.1/target-typed-default.md)  
+ [C# 7.1 Specification Proposals](~/_csharplang/proposals/csharp-7.1/infer-tuple-names.md)  
  There are new features added in C# 7.1. The `default` expression can be used without a type in locations where the type can be inferred. Also, tuple member names can be inferred. Finally, pattern matching can be used with generics.
 
  [C# 7.2 Specification Proposals](~/_csharplang/proposals/csharp-7.2/readonly-ref.md)  
@@ -63,7 +63,7 @@ The features that have been implemented in C# versions after 6.0, including thos
 [C# 10 Specification Proposals](~/_csharplang/proposals/csharp-10.0/record-structs.md)\
 C# 10 is available with .NET 6. The features include record structs, parameterless struct constructors, global using directives, file-scoped namespaces, extended property patterns, improved interpolated strings, constant interpolated strings, lambda improvements, caller-argument expression, enhanced `#line` directives, generic attributes, improved definite assignment analysis, and `AsyncMethodBuilder` override.
 
-[C# 11 Specification Proposals](/_csharplang/proposals/csharp-11.0/static-abstracts-in-interfaces.md)\
+[C# 11 Specification Proposals](~/_csharplang/proposals/csharp-11.0/static-abstracts-in-interfaces.md)\
 C# 11 is available with .NET 7. The new features include static abstract members in interfaces, checked user-defined operators, unsigned right shift operator, relaxing shift operator, numeric `IntPtr`, raw string literals, interpolated string newline, UTF-8 string literals, pattern match span, list patterns, required members, auto-default struct, low-level struct improvements, extended `nameof` scope, and file local types.
 
 ## Related sections  

@@ -39,8 +39,6 @@ The following example shows the usage of the `default` literal:
 
 For more information, see the [Default value expressions](~/_csharpstandard/standard/expressions.md#11719-default-value-expressions) section of the [C# language specification](~/_csharpstandard/standard/README.md).
 
-For more information about the `default` literal, see the [feature proposal note](~/_csharplang/proposals/csharp-7.1/target-typed-default.md).
-
 ## See also
 
 - [C# reference](../index.md)

@@ -157,8 +157,8 @@ Simulates bank accounts, using ACID transactions to transfer random amounts betw
 :::image type="content" source="https://raw.githubusercontent.com/dotnet/samples/main/orleans/Blazor/BlazorServer/screenshot.jpeg" alt-text="Blazor Orleans sample app screen capture":::
 
 These two Blazor samples are based on the [Blazor introductory tutorials](https://dotnet.microsoft.com/learn/aspnet/blazor-tutorial/intro), adapted for use with Orleans.
-The [Blazor WebAssembly](https://github.com/dotnet/orleans/raw/main/samples/Blazor/BlazorWasm/#readme) sample uses the [Blazor WebAssembly hosting model](/aspnet/core/blazor/hosting-models#blazor-webassembly).
-The [Blazor Server](https://github.com/dotnet/orleans/raw/main/samples/Blazor/BlazorServer/#readme) sample uses the [Blazor Server hosting model](/aspnet/core/blazor/hosting-models#blazor-server).
+The [Blazor WebAssembly](https://github.com/dotnet/samples/tree/main/orleans/Blazor/BlazorWasm) sample uses the [Blazor WebAssembly hosting model](/aspnet/core/blazor/hosting-models#blazor-webassembly).
+The [Blazor Server](https://github.com/dotnet/samples/tree/main/orleans/Blazor/BlazorServer) sample uses the [Blazor Server hosting model](/aspnet/core/blazor/hosting-models#blazor-server).
 They include an interactive counter, a TODO list, and a Weather service.
 
 ### Blazor sample apps demonstrate
@@ -188,7 +188,7 @@ A *Hello, World!* application configured to use mutual [*Transport Layer Securit
 
 * How to configure mutual-TLS (mTLS) authentication for Orleans
 
-## [Visual Basic Hello World](/samples/dotnet/samples/orleans-vb-samplee)
+## [Visual Basic Hello World](/samples/dotnet/samples/orleans-vb-sample/)
 
 A *Hello, World!* application using Visual Basic.