-
Notifications
You must be signed in to change notification settings - Fork 107
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
Allow dropping native host for NativeAOT WinRT components #1395
Conversation
@@ -1,258 +1,342 @@ | |||
using Microsoft.CodeAnalysis; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note: I normalized whitespaces in this file, review with whitespace diff off.
The actual changes are just a few lines of code being added.
4d5281b
to
38098bf
Compare
fa62a4c
to
f02bf33
Compare
…ot-winrt-exports-authoringtestfixes2
…-authoringtestfixes2 Fix test issues discovered from enabling AOT for authoring scenarios
Just to note in the PR, there is one remaining authoring test failure for AOT (AuthoringTest.CustomTypes). That would be addressed in a separate PR. |
We will still need the generated See: https://github.com/hez2010/WinRTServer/blob/master/WinRTServer/InternalModule.cs |
Closes #1387
Overview
This PR adds a new
CsWinRTAotExportsEnabled
MSBuild property that can be set in authoring scenarios (and is automatically set ifPublishAot
is already set). This triggers the generator to emit the native exports for WinRT .dll-s directly into the same binary, with the correct logic, and also skips adding all references and copying all files related to the native host infrastructure.Keeping as a draft as I'm not entirely sure how to set up unit tests for this just yet 😅