You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
ID: e0842844-005f-5004-022d-fce7a82daff8
Version Independent ID: 88ddeba8-3b31-95f4-26b2-4a12a7313b47
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.
The text was updated successfully, but these errors were encountered: