WinRT Server fixes #40
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We ran into two problems trying to use WinRT server in .NET9. I'm not sure what changed/broke this but it seems obvious what's wrong:
I was able to reproduce the problem by publishing the test package and running the C++ app -- the background WinRT server crashes calling GetTrustLevel on what it thinks is an IActivationFactory but is actually an IUnknown. And once that is fixed (1), then the IActivationFactory QI in ActivateInstance failed. With these fixes, the NAOT compiled version succeeds.