microsoft / microsoft/microsoft-ui-xaml
WASDK/WinUI source code loading during debugging in Visual Studio pops up Microsoft login window
- Dominant language
- C++
- Stars
- 8.4k
- Forks
- 942
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 105
Description
### Describe the bug
Whenever C++ source code files for Windows App SDK or WinUI are being loaded during debugging in Visual Studio, a Microsoft login window appears. It needs to be closed twice before the source code is actually loaded from GitHub.
I suspect this is the login for Microsoft employees, who have their credentials cached and therefore never see this. This issue impacts productivity of native debugging scenarios for Windows App SDK developers, as on every app start you will have to click away these two windows.
### Steps to reproduce the bug
1. Add a breakpoint in Windows App SDK/WinUI C++ code in Visual Studio (example: add function breakpoint to Microsoft.ui.xaml.dll!OnFailureEncountered)
2. Enable native debugging
3. Start debugging your app
4. During startup/applying the breakpoint, the source code is being loaded and the login window appears. It needs to be clicked away twice before the source code is loaded.
### Expected behavior
During startup/applying the breakpoint, the source code is being loaded without any login windows shown.
### Screenshots

### NuGet package version
Windows App SDK 1.6.1: 1.6.240923002
### Packaging type
Packaged (MSIX)
### Windows version
Windows 11 version 22H2 (22621, 2022 Update)
### IDE
Visual Studio 2022
### Additional context
_No response_
Contributor guide
Research direction
Reproduce the issue in Visual Studio 2022 using the listed Windows App SDK 1.6.1 environment, a native breakpoint, and the provided steps. Investigate the source-loading stage that displays the Microsoft login window; done means the C++ source loads from GitHub without either login prompt during debugging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100