Skip to content
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.

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

Clarifications about exposing "Any CPU" assemblies to 32-bit COM clients needed #21173

Closed
Dmitry-Me opened this issue Oct 21, 2020 · 1 comment · Fixed by #22531
Closed

Clarifications about exposing "Any CPU" assemblies to 32-bit COM clients needed #21173

Dmitry-Me opened this issue Oct 21, 2020 · 1 comment · Fixed by #22531
Labels
doc-enhancement Improve the current content [org][type][category] Pri2

Comments

@Dmitry-Me
Copy link

This page https://docs.microsoft.com/en-us/dotnet/core/native-interop/expose-components-to-com explains how to expose a .NET Core assembly to COM. It looks very similar to how .NET Framework assemblies are exposed. However there's a major difference: dotnet/runtime#32493

With .NET Framework "Any CPU" assembly can be consumed by both 32-bit and 64-bit clients. With .NET Core "Any CPU" assemblies are accompanied with 64-bit .comhost.dll and so they can only be consumed by 64-bit clients. This is a breaking change and totally unexpected. Would be nice to have it documented.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

@tdykstra
Copy link
Contributor

@Dmitry-Me Thanks for reporting that. @jkoritzinsky Please verify the wording of the note as added in #22531

@tdykstra tdykstra added the doc-enhancement Improve the current content [org][type][category] label Jan 28, 2021
@dotnet-bot dotnet-bot removed the ⌚ Not Triaged Not triaged label Jan 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc-enhancement Improve the current content [org][type][category] Pri2
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants