Fix build #52
Merged
Fix build #52
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
…rding to https://docs.microsoft.com/en-us/windows/apps/winui/winui2/getting-started and original Modernize page
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.
Handles build issues. Related to WinUI/Xaml Islands/WPF and UWP playing together.
The issue that has been holding us back the entire time started due to upgrading NuGet versions of WinUI.
The upgrade has been done in order to work with WinUI and Xaml Islands, that have stopped working and compiling in newer Visual Studio versions and .NET Core 3.1, and in order to renew our certificates.
Even after completely going over the instructions of using Xaml Islands and consuming WinUI into the app, we could not find any difference.
Eventually, after some (pretty long) time, Microsoft has released an update to their documentation that states the fixes that needed to be done in order to allow us building the app.
The issue was as follows -
Let's have a toast for anyone who stumbles upon this issue and somehow arrives here. If you do, have a good one. Sorry for the time you wasted on this. I know you wasted time on this ;)
Issue clarification -
https://docs.microsoft.com/en-us/windows/apps/desktop/modernize/host-custom-control-with-xaml-islands#resolve-cannot-find-a-resource-error-when-hosting-a-winui-control