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
When I look at the PDBs that are downloaded from Microsoft's symbol server, they look like they're stripped, with no reference to any file name information inside them (it even places them in a "stripped" folder).
I tried clearing the cache, hoping the symbols had gotten updated since I last downloaded symbols, but that didn't help.
On that note, it would be great if you could now switch over to use source linking, so that we don't actually need to clone the repo, but source code will automatically get downloaded from the correct commit.
Describe the bug
I'm trying to follow the steps described here: https://github.com/microsoft/microsoft-ui-xaml/tree/winui3/release/1.4-stable#debugging-winui-3
to debug the latest v1.4.2 with the source code you released.
However I'm not able to get this to work:
When I look at the PDBs that are downloaded from Microsoft's symbol server, they look like they're stripped, with no reference to any file name information inside them (it even places them in a "stripped" folder).
I tried clearing the cache, hoping the symbols had gotten updated since I last downloaded symbols, but that didn't help.
On that note, it would be great if you could now switch over to use source linking, so that we don't actually need to clone the repo, but source code will automatically get downloaded from the correct commit.
Steps to reproduce the bug
Follow the steps described here: https://github.com/microsoft/microsoft-ui-xaml/tree/winui3/release/1.4-stable#debugging-winui-3
I used Visual Studios solution properties to add the source code path, since this was only vaguely described with a link in the readme:
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: