Replies: 2 comments 11 replies
-
|
CsWinRT 3.0 doesn't use GeneratedComInterface, as it does not use .NET's source generated COM Wrappers. It uses its own COM Wrappers implementation. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Does that mean I won’t be able to use it to implement interfaces for COM
with NativeAOT?
…On Fri, 17 Apr 2026 at 5:45 pm, Minh Dang Binh ***@***.***> wrote:
CsWinRT 3.0 doesn't use GeneratedComInterface, as it does not use .NET's
source generated COM Wrappers. It uses its own COM Wrappers implementation.
—
Reply to this email directly, view it on GitHub
<#2394 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABBRBS3OP3HRTLCEZ5R2PT4WHOKNAVCNFSM6AAAAACX4RLIL6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMNRQGAYDGOI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
11 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
e.g. I have a csproj:
When I have a look at the type definitions coming from cswinrt they're missing the ComGeneratedInterface attribute - is there perhaps another flag I need to set?
Beta Was this translation helpful? Give feedback.
All reactions