From 3b62da358150b2d45f351b1f1967098f4b4fc56a Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Fri, 24 Jul 2026 21:39:58 +0000 Subject: [PATCH 1/3] Initial plan From 07a2b43413f0ee7ccac79c0520ae4c41d4a2e79c Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Fri, 24 Jul 2026 21:42:00 +0000 Subject: [PATCH 2/3] Add dscom note to COM exposure article --- docs/core/native-interop/expose-components-to-com.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/core/native-interop/expose-components-to-com.md b/docs/core/native-interop/expose-components-to-com.md index 7d9e0d2cb75e8..54eb7407ea1ed 100644 --- a/docs/core/native-interop/expose-components-to-com.md +++ b/docs/core/native-interop/expose-components-to-com.md @@ -2,6 +2,7 @@ title: "Exposing .NET Core components to COM" description: "This tutorial shows you how to expose a class to COM from .NET Core. You generate a COM server and a side-by-side server manifest for Registry-Free COM." ms.date: 07/12/2019 +ai-usage: ai-assisted helpviewer_keywords: - "exposing .NET Core components to COM" - "interoperation with unmanaged code, exposing .NET Core components" @@ -128,3 +129,5 @@ There is a fully functional [COM server sample](https://github.com/dotnet/sample Exposing COM components from [C++/CLI projects](/cpp/dotnet/dotnet-programming-with-cpp-cli-visual-cpp) via the [EnableComHosting property](../project-sdk/msbuild-props.md#enablecomhosting) is not supported. Additionally, loading both .NET Framework and .NET Core into the same process does have diagnostic limitations. The primary limitation is the debugging of managed components as it is not possible to debug both .NET Framework and .NET Core at the same time. In addition, the two runtime instances don't share managed assemblies. This means that it isn't possible to share actual .NET types across the two runtimes and instead all interactions must be restricted to the exposed COM interface contracts. + +For scenarios where you need command-line COM tools similar to tools that .NET Framework provided, see the community project [`dscom`](https://github.com/dspace-group/dscom). This project isn't a Microsoft tool, so support comes from the project maintainers. From 4b57dc31cdec1e7b1751536ba75af8f7ce2988dc Mon Sep 17 00:00:00 2001 From: "Andy (Steve) De George" <67293991+adegeo@users.noreply.github.com> Date: Fri, 24 Jul 2026 15:29:06 -0700 Subject: [PATCH 3/3] Apply suggestion from @adegeo --- docs/core/native-interop/expose-components-to-com.md | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/core/native-interop/expose-components-to-com.md b/docs/core/native-interop/expose-components-to-com.md index 54eb7407ea1ed..76e99dc703239 100644 --- a/docs/core/native-interop/expose-components-to-com.md +++ b/docs/core/native-interop/expose-components-to-com.md @@ -2,7 +2,6 @@ title: "Exposing .NET Core components to COM" description: "This tutorial shows you how to expose a class to COM from .NET Core. You generate a COM server and a side-by-side server manifest for Registry-Free COM." ms.date: 07/12/2019 -ai-usage: ai-assisted helpviewer_keywords: - "exposing .NET Core components to COM" - "interoperation with unmanaged code, exposing .NET Core components"