-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[dotnet-sdk-9.0.100-preview.7.24352.8] WPF apps launch failed with System.Windows.Markup.XamlParseException #9354
Comments
@harshit7962 Thanks for looking into the two bugs regarding WPF app launch. Could you please let us know if there are any updates? There are totally 35 apps affected in our AppCompat Lab, it may affect more users in real world. Thanks. |
We have a fix ready, we are going though final stages of testing. The fix would be merged in a couple of hours. |
Great. Thanks @harshit7962 for your update. We will verify it when we get the build. |
@Junjun-zhao we have merged the fix to this as of 19 July (Friday). The changes in PR #5610 caused these applications to fail and the fix was followed up by the change #9393. |
Hi @harshit7962, we have verified with build# dotnet-sdk-9.0.100-preview.7.24374.17, this issue has been fixed for the affected apps. |
@Junjun-zhao - Can we close this issue? |
Yes, please go ahead. |
I am using the operating system 9.0.100-preview.7.24407.12, Windows 11, and this issue still exists, causing all of my WPF applications to fail to start |
@wf-soft Could you please share the stack trace? Besides, if you could share a github project or demo to reproduce this issue, that will help developer team to look into the issue. |
@Junjun-zhao I'm seeing crash on my WPF apps too and I'm a bit surprised to get them even if I target With SDK 8, it's using PresentationFramework.dll 8.0.8 and it's working fine. Did something also changed in the SDK? In the way the .xaml resources are being processed? |
Hi @jairbubbles, Could you please try if the workarounds work for you? #9582 (comment) |
@Junjun-zhao No problem with RC1 now. |
Description
When run the 3rd party application with the latest .NET 9 build "dotnet-sdk-9.0.100-preview.7.24352.8", it failed to launch System.Windows.Markup.XamlParseException.
Reproduction Steps
App Repro steps
Expected behavior
Launch successfully.
Actual behavior
Launch failed.
Event Viewer Log:
Regression?
Yes
Verify Scenarios:
1). Windows 10 21H2 AMD64 + dotnet-sdk-9.0.100-preview.6.24328.19: Pass
2). Windows 10 21H2 AMD64 + dotnet-sdk-9.0.100-preview.7.24352.8: Fail
3). Windows 10 21H2 AMD64 + dotnet-sdk-9.0.100-preview.7.24353.17: Fail
Known Workarounds
No response
Impact
No response
Configuration
Application Name: MahAppsMetro,RSBase,BitbendazLinker,TodoSync,JL,WUView,MyMoneyNet,YoutubePlaylistDownloaderCore,VidCoderCore,GenshinLyreMidiPlayer,RadeonSoftwareSlimmer
,ImageSort,HuoHuan,Delfinovin,PicView,OpenNetMeter,HandyControl,,FlowLauncher,ME3TweaksModManager,ScreenToGifNetcore,OnlyM,OnlyT,WolvenKit,ADBExplorer
OS: Windows 10 21H2
CPU: X64
.NET Build Number: dotnet-sdk-9.0.100-preview.7.24352.8
App, Source and repro machine Info checking at https://devdiv.visualstudio.com/DevDiv/_workitems/edit/2114797
Github Link:
https://github.com/MahApps/MahApps.Metro
https://github.com/MoneyTools/MyMoney.Net
Other information
Debug Repro steps:
1.Open "C:\ReproAppSource\MahApps.Metro\src\MahApps.Metro.sln" with Visual Studio.
2. Build the solution.
3. Update \bin\Debug\net6.0-windows\MahApps.Metro.Demo.runtimeconfig.json to run against with dotnet-sdk-9.0.100-preview.7.24352.8:
Select net6.0-windows option before run it in Visual Studio because this app is multiple platforms targeted.
Press F5 to start the app.
Expected Result:
App launch successful in Visual Studio.
Actual Result:
App launch failed with exception thrown in Visual Studio.
Findings:
Some apps, like repro app mentioned in the repro steps, if we replace the DynamicResource to StaticResource in xaml file, the issue will go.
And we found this issue and #9353 are all related to load resource in WPF app.
@dotnet-actwx-bot @dotnet/compat
The text was updated successfully, but these errors were encountered: