Closed Junjun-zhao closed 2 months ago
@harshit7962 We have verified this issue with build dotnet-sdk-9.0.100-preview.7.24374.17, it has been fixed. But for Text-Grab, there is an new issue and we file a new bug [9.0.100-preview.7.24375.12] Text-Grab launch failed with exception System.Windows.Markup.XamlParseException at System.Windows.DependencyObject.EvaluateExpression . Could you please help look into it? Thanks.
Will follow the reported failure in respective thread. Closing this issue as of now.
Thank you @Junjun-zhao for reporting and keeping a close eye on this.
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 with exception: 'Value cannot be null. (Parameter 'key')'.
Reproduction Steps
App Repro steps:
Expected behavior
Launch successfully.
Actual behavior
Launch failed. Open Event Viewer, we can see below detailed stack trace message:
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: wpfui, Open-SD-WebUI-Launcher, Text-Grab OS: Windows 10 21H2 CPU: X64 .NET Build Number: dotnet-sdk-9.0.100-preview.7.24352.8 App or App installer checking at: https://devdiv.visualstudio.com/DevDiv/_workitems/edit/2114834 Github Link: https://github.com/lepoco/wpfui https://github.com/Ray-Source-X/Open-SD-WebUI-Launcher https://github.com/TheJoeFin/Text-Grab
Dotnet Info:
Other information
Debug Repro steps: 1.Open "C:\ReproAppSource\wpfui\Wpf.Ui.sln" with Visual Studio.
Expected Result: App launch successful in Visual Studio.
Actual Result: App launch failed with exception thrown in Visual Studio.
Findings: 1.The issue occurs when loading resource xaml file. In below repro app, we tried remove all content in Light.xaml file and only keep below 1 StaticResource, the problem still occurs.
@dotnet-actwx-bot @dotnet/compat