Workaround for UWP .Net native build#210
Closed
danielcaceresm wants to merge 1 commit into
Closed
Conversation
danielcaceresm
changed the title
Contributor
|
@andrew-boyarshin can we get this PR merged for next release please? |
Contributor
|
@andrew-boyarshin any ETA of when this PR wil get merged and new nuget will be released? This is blocker for wave engine guys using vortice windows |
Contributor
|
Thanks @danielcaceresm for pointing this out! I've merged a change similar to yours, but also I've gone through all other structs and checked there are no more autoproperties defined on them. Of course, you're welcome to open an issue if you spot any other .NET Native issues. |
This file contains hidden or 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
3 participants
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.
Build a project that references Vortice using UWP .Net Native throws the following exception:
This issue has been reported 3 years ago, but the only solution is to avoid the use of auto-properties....
You can reproduce the issue creating a new UWP project, adding the SharpGen.Runtime and adding the following line in the MainPage.xaml.cs: