You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks a lot. Spent hours on that. Seems that "should be known" didn't work in my case. Wonder if there could be solution within the generated XAML startup code to check if that option is on and WriteLine a statement....
Describe the bug
VisualStudio 2022 tries to attach another debugger when
App.xaml.cs
tries to activate two Windows:Output:
The program '[26132] DebuggerCrash.exe' has exited with code 3221225477 (0xc0000005) 'Access violation'.
This happens (DebuggerCrash project) using
This does not happen (DebuggerNoCrash project) using
Both projects run without any issues if started WITHOUT debugging from VisualStudio 2022
Steps to reproduce the bug
Expected behavior
should open and continue debugging without any issues
Screenshots
No response
NuGet package version
WinUI 3 - Windows App SDK 1.4.2: 1.4.231008000
Windows version
Windows 11 (22H2): Build 22621
Additional context
No response
The text was updated successfully, but these errors were encountered: