ProgressBar and ProgressRing controls are not working in SDK 1.1 preview 3

Describe the bug

If I include ProgressBar or ProgressRing control on the Window, the app simple does not load. And also the error is not meaningful.

I used the simple XAML: <ProgressBar Width="130" Value="0" />

Error:

Unhandled exception at 0x5BE8BAC9 (Microsoft.ui.xaml.dll) in App3.exe: 0xC000027B: An application-internal exception has occurred (parameters: 0x122D8960, 0x00000002).

Steps to reproduce the bug

1. Create a new Blank App in WinUI 3 C# with SDK 1.1 Preview 3.
2. Add a ProgressRing or ProgressBar control on the MainWindow.
3. Run the app

Expected behavior

The app should start normally when ProgressBar or ProgressRing control is added.

Screenshots

Can’t add screenshot as the app is not starting.

NuGet package version

WinUI 3 - Windows App SDK 1.1 Preview 3: 1.1.0-preview3

Windows app type

• UWP
• Win32

Device form factor

Desktop

Windows version

Windows 11 (21H2): Build 22000

Additional context

No response

[gabbybilka]

This issue was fixed and released in Windows App SDK 1.1.3 - check out the release notes and NuGet to try it out 🎉

[kmahone]

@hassaanmasood thanks for reporting this issue. The problem is understood and I have a fix available internally.

This issue is hit whenever a ProgressRing, ProgressBar (or a few other controls) are created when Microsoft.Windows.SDK.NET.dll is not already loaded into the process. So it is possible to work-around this issue by forcing Microsoft.Windows.SDK.NET.dll to be loaded before your page/wndow loads. I was able to do this by adding a line of code to my window’s ctor:

        public MainWindow()
        {
            var coreDispatcher = this.Dispatcher;
            this.InitializeComponent();
        }

Even though this line of code doesn’t really do anything, it does have the effect of getting Microsoft.Windows.SDK.NET.dll loaded into the process and so you no longer hit a problem with ProgressRing or ProgressBar. It doesn’t have to be this specific line of code, anything that forces the dll to load should suffice.