Skip to content

Clarify non-Microsoft path for generating COM tooling artifacts in modern .NET COM docs #55013

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
adegeo merged 3 commits into from
Jul 24, 2026
+2 −0
Merged

Clarify non-Microsoft path for generating COM tooling artifacts in modern .NET COM docs #55013

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
3b62da3
Initial plan
Copilot Jul 24, 2026
07a2b43
Add dscom note to COM exposure article
Copilot Jul 24, 2026
4b57dc3
Apply suggestion from @adegeo
adegeo Jul 24, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/core/native-interop/expose-components-to-com.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -128,3 +128,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.
Loading