Update to latest Nuget Packages for WAS/WinUI #1762
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
|
Oh and also I had to update your projects references to the latest SkiaSharpView nuget to make the QA machine happy as well. |
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.
I found an interesting bug, which I don't think is your fault or mine, but instead is a Microsoft Bug.
tldr; Microsoft pushed out an update in November to Windows 11 machines, that causes our app to crash unless all graphic drawing project libraries are upgraded to use the latest
AppSDK,BuildTools, andImplementaionLibrary, if multiple libraries are attempting to simultaneously draw graphic.We had upgraded to the latest WAS / WinUI build packages for our C# WinUI project.
We are using LiveCharts2 in the Windows implementation of MyRadar (www.myradar.com, if you want to see the project that it is being used on).
Part of the MyRadar system is our own in-house C++ Graphic Engine that draws the weather and CONUS maps. It was built against
"Microsoft.WindowsAppSDK.1.5.240627000"
"Microsoft.Windows.SDK.BuildTools.10.0.26100.1742"
"Microsoft.Windows.ImplementationLibrary.1.0.240122.1"
And of course your current nuget packages in the
devbranch are"Microsoft.WindowsAppSDK.1.5.240627000"
"Microsoft.Windows.SDK.BuildTools.10.0.26100.1742"
"Microsoft.Windows.ImplementationLibrary.1.0.240122.1"
So each of the various components were using slightly different versions of the dependent libraries and on all our our Dev machine and most of our QA team's machines this was no issue...
BUT
We had received a report from customer that they were experiencing a crash of MyRadar anytime they tried to view a page that had a LiveCharts2 chart on it. And, as luck would have it, we finally had one of our QA machines start reproducing the crash.
It took me while but I was able to definitively prove that on some machines (but not all) the 2024-12 Cumulative Update for Windows 11 Version 23H2 causes an error of multiple libraires are attempting to do "Drawing" on the Main UI Thread in the same Application process at the same time, IF they have differing
WAS,BuildTools, orImplementationLibraryversionsSo, I have taken your Dev Branch (as of last Friday afternoon) and upgraded it to use the latest versions of those libraries.
AND it appears that the culprit is the 23
H2update (as opposed to the 24H2update) that causes the error.