C#/WinRT docs: fix stale content, typos, and code errors

- index.md: Remove 'preview of authoring' (authoring is GA); remove
  '(Preview)' from Embedded support heading; fix 'Github' → 'GitHub';
  update ms.date
- authoring.md: fix 'Github' → 'GitHub'; update ms.date
- agile-objects.md: add missing semicolon in code example; update ms.date
- net-mappings-of-winrt-types.md: fix self-referential NOTE (now links
  to UWP mappings page); fix malformed Matrix3D table row (spurious
  opening parenthesis); update ms.date
- create-windows-runtime-component-cswinrt.md: update VS prereq to
  '2022 or later'; remove pinned C#/WinRT version 1.4.1 (use latest);
  update ms.date
- net-projection-from-cppwinrt-component.md: update two .NET 6.0 LTS
  references to .NET 8.0 LTS (.NET 6 support ended Nov 2024); update
  ms.date
- create-winrt-component-winui-cswinrt.md: fix 'Github' → 'GitHub'
  (×3); add 'or later' to .NET 6.0 SDK prereq; update ms.date

Co-authored-by: Copilot <[email protected]>

Author: GrantMeStrength

hub/apps/develop/platform/csharp-winrt/agile-objects.md

@@ -1,7 +1,7 @@
 ---
 description:  An agile object is one that can be accessed from any thread. C#/WinRT provides support for agile references if you need to marshal a non-agile object across apartments in a safe way.
 title: Agile objects with C#/WinRT
-ms.date: 11/17/2020
+ms.date: 04/13/2026
 ms.topic: article
 ms.localizationpriority: medium
 ---
@@ -40,6 +40,6 @@ You can now pass `agileReference` to a thread in a different apartment, and use
 
 ```csharp
 await Task.Run(() => {
-        Windows.UI.Popups.PopupMenu nonAgileObjAgain = agileReference.Get()
+        Windows.UI.Popups.PopupMenu nonAgileObjAgain = agileReference.Get();
     });
 ```

hub/apps/develop/platform/csharp-winrt/authoring.md

@@ -1,7 +1,7 @@
 ---
 title: Author Windows Runtime components with C#/WinRT
 description: Overview of authoring Windows Runtime Components with C#/WinRT 
-ms.date: 03/15/2022
+ms.date: 04/13/2026
 ms.topic: article
 ms.localizationpriority: medium
 ---
@@ -15,7 +15,7 @@ The C#/WinRT NuGet package provides support for authoring your own Windows Runti
 
 For a walkthrough showing how to author a Windows Runtime component with .NET 6, and how to consume it from a C++/WinRT console application, see [Walkthrough: Create a C#/WinRT component and consume it from C++/WinRT](./create-windows-runtime-component-cswinrt.md).
 
-For more details, and to search for or file any issues, refer to the [C#/WinRT Github repo](https://github.com/microsoft/CsWinRT) and [Authoring C#/WinRT Components](https://github.com/microsoft/CsWinRT/blob/master/docs/authoring.md).
+For more details, and to search for or file any issues, refer to the [C#/WinRT GitHub repo](https://github.com/microsoft/CsWinRT) and [Authoring C#/WinRT Components](https://github.com/microsoft/CsWinRT/blob/master/docs/authoring.md).
 
 ## Declaring types in Windows Runtime components
 

hub/apps/develop/platform/csharp-winrt/create-windows-runtime-component-cswinrt.md

@@ -1,12 +1,7 @@
 ---
 title: Walkthrough—Create a C#/WinRT component, and consume it from C++/WinRT
 description: Author a Windows Runtime component with C#/WinRT, and consume it from a native application.
-ms.date: 03/15/2022
-ms.topic: article
-ms.localizationpriority: medium
----
-
-# Walkthrough—Create a C#/WinRT component, and consume it from C++/WinRT
+ms.date: 04/13/2026, and consume it from C++/WinRT
 
 C#/WinRT enables developers using .NET to author their own Windows Runtime components in C# using a class library project. Authored components can be consumed in native desktop applications as a package reference or as a project reference with a few modifications.
 
@@ -18,7 +13,7 @@ For a walkthrough on authoring WinUI 3 controls with C#/WinRT specifically for u
 
 This walkthrough requires the following tools and components:
 
-- [Visual Studio 2022](/visualstudio/releases/2022/release-notes)
+- [Visual Studio 2022 or later](/visualstudio/releases/2022/release-notes)
 - [.NET 6.0 SDK](https://dotnet.microsoft.com/download/dotnet) or later
 - [C++/WinRT VSIX](https://marketplace.visualstudio.com/items?itemName=CppWinRTTeam.cppwinrt101804264) for C++/WinRT project templates
 
@@ -41,7 +36,7 @@ Begin by creating a new project in Visual Studio. Select the **Class Library** p
 
     a. In Solution Explorer, right click on the project node and select **Manage NuGet Packages**.
 
-    b. Search for the **Microsoft.Windows.CsWinRT** NuGet package and install the latest version. This walkthrough uses C#/WinRT version 1.4.1.
+    b. Search for the **Microsoft.Windows.CsWinRT** NuGet package and install the latest version.
 
 3. Add a new `PropertyGroup` element that sets the `CsWinRTComponent` property. This specifies that your project is a Windows Runtime component so that a `.winmd` file is generated when you build the project.
 

hub/apps/develop/platform/csharp-winrt/create-winrt-component-winui-cswinrt.md

@@ -1,12 +1,7 @@
 ---
 title: Walkthrough—Create a C# component with WinUI controls, and consume it from a C++/WinRT app that uses the Windows App SDK
 description: Author a Windows Runtime component with C#/WinRT with WinUI controls, and consume it from any Windows App SDK app.
-ms.date: 03/15/2022
-ms.topic: article
-ms.localizationpriority: medium
----
-
-# Walkthrough—Create a C# component with WinUI 3 controls, and consume it from a C++/WinRT app that uses the Windows App SDK
+ms.date: 04/13/2026, and consume it from a C++/WinRT app that uses the Windows App SDK
 
 C#/WinRT provides support for authoring Windows Runtime components, including WinUI custom types and custom controls. These components can be consumed from either C# or C++/WinRT applications that use the Windows App SDK. We recommend using C#/WinRT v1.6.4 or later to author runtime components with NuGet packaging support.
 
@@ -19,7 +14,7 @@ This walkthrough demonstrates how to author a C# component with a custom WinUI c
 This walkthrough requires the following tools and components:
 
 - [Visual Studio 2026](/visualstudio/releases/2026/release-notes)
-- [.NET 6.0 SDK](https://dotnet.microsoft.com/download/dotnet/6.0)
+- [.NET 6.0 SDK](https://dotnet.microsoft.com/download/dotnet/6.0) or later
 - [Windows App SDK VSIX](../../../windows-app-sdk/downloads.md) (1.1 from the stable channel)
 
 ## Author your C#/WinRT component using the Windows App SDK
@@ -104,7 +99,7 @@ This walkthrough requires the following tools and components:
 1. You can now build the **WinUIComponentCs** project to generate a `.winmd` file for the component. 
 
  > [!NOTE]
- > You can also package the component as a NuGet package for end app consumers to reference. For more details, see [Authoring C#/WinRT components](https://github.com/microsoft/CsWinRT/blob/master/docs/authoring.md) on the C#/WinRT Github repo.
+ > You can also package the component as a NuGet package for end app consumers to reference. For more details, see [Authoring C#/WinRT components](https://github.com/microsoft/CsWinRT/blob/master/docs/authoring.md) on the C#/WinRT GitHub repo.
 
 ## Reference the component from a Windows App SDK C++/WinRT app
 
@@ -177,8 +172,8 @@ Consumption from packaged apps that use a separate **Windows Application Packagi
 
 ## Known issues
 
-- Consuming a C# component as a project reference requires `PublishReadyToRun` to be set to `False`. See [Github Issue #1151](https://github.com/microsoft/CsWinRT/issues/1151) for more details.
-- Consuming a C# component built for `AnyCPU` from C++ is supported only from `x86` applications currently. `x64` and `Arm64` apps result in a runtime error similar to: *%1 is not a valid Win32 application.* See [Github Issue #1151](https://github.com/microsoft/CsWinRT/issues/1093) for more details.
+- Consuming a C# component as a project reference requires `PublishReadyToRun` to be set to `False`. See [GitHub Issue #1151](https://github.com/microsoft/CsWinRT/issues/1151) for more details.
+- Consuming a C# component built for `AnyCPU` from C++ is supported only from `x86` applications currently. `x64` and `Arm64` apps result in a runtime error similar to: *%1 is not a valid Win32 application.* See [GitHub Issue #1151](https://github.com/microsoft/CsWinRT/issues/1093) for more details.
 
 ## Related topics
 

hub/apps/develop/platform/csharp-winrt/index.md

@@ -1,7 +1,7 @@
 ---
 description: C#/WinRT is a tool set that provides WinRT projection support for C# code.
 title: C#/WinRT
-ms.date: 05/19/2020
+ms.date: 04/13/2026
 ms.topic: article
 keywords: windows 10, uwp, standard, c#, winrt, cswinrt, projection
 ms.localizationpriority: medium
@@ -13,7 +13,7 @@ C#/WinRT is a NuGet-packaged toolkit that provides Windows Runtime (WinRT) proje
 
 C#/WinRT currently provides support for consuming WinRT APIs through the use of [Target Framework Monikers](../../../desktop/modernize/desktop-to-uwp-enhance.md) (TFMs) in .NET. Setting the TFM with a specific Windows SDK version adds references to the Windows SDK projection and runtime assemblies generated by C#/WinRT.
 
-The [C#/WinRT NuGet package](https://www.nuget.org/packages/Microsoft.Windows.CsWinRT/) enables you to [create](#generate-and-distribute-an-interop-assembly) and [reference](#reference-an-interop-assembly) your own WinRT interop assemblies for .NET consumers. The latest C#/WinRT version also includes a [preview of authoring](create-windows-runtime-component-cswinrt.md) WinRT types in C#.
+The [C#/WinRT NuGet package](https://www.nuget.org/packages/Microsoft.Windows.CsWinRT/) enables you to [create](#generate-and-distribute-an-interop-assembly) and [reference](#reference-an-interop-assembly) your own WinRT interop assemblies for .NET consumers. The latest C#/WinRT version also supports [authoring](create-windows-runtime-component-cswinrt.md) WinRT types in C#.
 
 For additional information, see the [C#/WinRT GitHub repo](https://aka.ms/cswinrt/repo).
 
@@ -29,7 +29,7 @@ Finally, C#/WinRT is a general toolkit and is intended to support other scenario
 
 ## What's new
 
-The latest C#/WinRT releases can be found on our [release notes](https://github.com/microsoft/CsWinRT/releases) page in the Github repo.
+The latest C#/WinRT releases can be found on our [release notes](https://github.com/microsoft/CsWinRT/releases) page in the GitHub repo.
 
 ## Usage
 
@@ -47,7 +47,7 @@ Typically, C#/WinRT interop assemblies are referenced by application projects. B
 
 If you distribute a third-party WinRT component without an official interop assembly, an application project may follow the procedure for [generating an interop assembly](#generate-and-distribute-an-interop-assembly) to generate its own private projection sources. We don't recommend this approach, because it can produce conflicting projections of the same type within a process. NuGet packaging, following the [Semantic Versioning](https://semver.org) scheme, is designed to prevent this. An official third-party interop assembly is preferred.
 
-### Embedded support for WinRT types (Preview) 
+### Embedded support for WinRT types 
 
 Starting with C#/WinRT version 1.4.1, support is included for embedding Windows SDK projection and runtime sources for both .NET and .NET Standard 2.0 into your library or app's output. This is useful in cases where usage of Windows SDK types is self-contained. Embedded support removes dependencies on WinRT.Runtime.dll and Microsoft.Windows.SDK.NET.dll which reduces the library or app output size. It also allows library developers to provide downlevel support and removes the need for multi-targeting.
 

hub/apps/develop/platform/csharp-winrt/net-mappings-of-winrt-types.md

@@ -1,7 +1,7 @@
 ---
 title: .NET mappings of WinRT types in C#/WinRT
 description: The following table lists the mappings that C#/WinRT makes between Windows Runtime types and .NET types.
-ms.date: 04/19/2020
+ms.date: 04/13/2026
 ms.topic: article
 keywords: windows 10, uwp
 ms.localizationpriority: medium
@@ -18,7 +18,7 @@ The C#/WinRT custom type mappings are categorized by types in the Windows SDK or
 - **WinRT types that map to .NET types with the same name and namespace.** These custom mappings are generally for performance or enhancement reasons, and are implemented directly in C#. Most of the types that have the same namespace name and type name in WinRT and .NET are structures (or types associated with structures, such as enumerations). In WinRT, structures have no members other than fields, and require helper types, which .NET hides. The .NET versions of these structures have properties and methods that provide the functionality of the hidden helper types (for example, **Windows.UI.Color**).
 
 > [!NOTE]
-> For a list of mappings between WinRT and .NET types in the context of UWP apps, see [.NET mappings of WinRT types in UWP](/windows/apps/develop/platform/csharp-winrt/net-mappings-of-winrt-types).
+> For a list of mappings between WinRT and .NET types in the context of UWP apps, see [.NET mappings of Windows Runtime types](/windows/uwp/winrt-components/net-framework-mappings-of-windows-runtime-types).
 
 ## Mappings for WinRT types in the Windows SDK
 
@@ -99,4 +99,4 @@ The C#/WinRT custom type mappings are categorized by types in the Windows SDK or
 | KeyTime | Microsoft.UI.Xaml.Media.Animation | 
 | RepeatBehavior | Microsoft.UI.Xaml.Media.Animation | 
 | RepeatBehaviorType | Microsoft.UI.Xaml.Media.Animation | 
-| Matrix3D |(Microsoft.UI.Xaml.Media.Media3D |
+| Matrix3D | Microsoft.UI.Xaml.Media.Media3D |

hub/apps/develop/platform/csharp-winrt/net-projection-from-cppwinrt-component.md

@@ -1,7 +1,7 @@
 ---
 title: Generate a C# projection from a C++/WinRT component, distribute as a NuGet for .NET apps
 description: In this topic, we walk through using [C#/WinRT](/windows/uwp/csharp-winrt/) to generate a C# .NET projection (or interop) assembly from a C++/WinRT Windows Runtime component, and distribute it as a NuGet package for .NET applications.
-ms.date: 03/23/2023
+ms.date: 04/13/2026
 ms.topic: how-to
 keywords: windows 10, c#, winrt, cswinrt, projection
 ms.localizationpriority: medium
@@ -73,7 +73,7 @@ First, with the **CppWinRTComponentProjectionSample** solution still open in Vis
     1. In **Solution Explorer**, right-click your solution node and click **Add** > **New Project**. 
     2. In the **Add a new project** dialog box, type **Class Library** in the search box. Choose **C#** from the language list, and then choose **Windows** from the platform list. Choose the C# project template that's called simply **Class Library** (with no prefixes nor suffixes), and click **Next**.
     3. Name the new project *SimpleMathProjection*. The location should already be set to the same `\CsWinRT\src\Samples\NetProjectionSample` folder that the **SimpleMathComponent** folder is in; but confirm that. Then click **Next**.
-    4. On the **Additional information** page, select **.NET 6.0 (Long-term support)**, and then choose **Create**.
+    4. On the **Additional information** page, select **.NET 8.0 (Long-term support)**, and then choose **Create**.
 
 2. Delete the stub **Class1.cs** file from the project.
 
@@ -235,7 +235,7 @@ To consume **SimpleMathComponent** from a .NET project, you can simply add to a
     1. In a new instance of Visual Studio, select **File** > **New** > **Project**.
     2. In the **Create a new project** dialog box, search for the **Console App** project template. Choose the C# project template that's called simply **Console App** (with no prefixes nor suffixes), and click **Next**. If you're using Visual Studio 2019, then the project template is **Console Application**.
     3. Name the new project **SampleConsoleApp**, set its location to the same `\CsWinRT\src\Samples\NetProjectionSample` folder that the **SimpleMathComponent** and **SimpleMathProjection** folders are in, and click **Next**.
-    4. On the **Additional information** page, select **.NET 6.0 (Long-term support)**, and then choose **Create**.
+    4. On the **Additional information** page, select **.NET 8.0 (Long-term support)**, and then choose **Create**.
 
 2. In **Solution Explorer**, double-click the **SampleConsoleApp** node to open the **SampleConsoleApp.csproj** project file, and edit the `TargetFramework` and `Platform` properties so that they look as shown in the following listing. Add the `Platform` element if it's not there.