Windows App SDK 1.6.0 (1.6.240829007)

[duncanmacmichael]

Windows App SDK 1.6.0 (1.6.240829007)

WinAppSDK 1.6.0 is the latest stable version of WinAppSDK providing new features and improvements to the platform.

New features include:

• Native AOT support
• Decoupled WebView2 versioning
• New Package Deployment APIs
• Improved TabView tear-out

Additional updates include:

• New wrapping mode for PipsPager
• More customization options for RatingControl

To see everything that's new and changed, see the full Windows App SDK 1.6 release notes.

See the WinAppSDK 1.6 milestone and WinUI 3 in WinAppSDK 1.6 milestone for a list of issues addressed in this release.

Try it out

• Download the 1.6.240829007 NuGet package to use WinAppSDK 1.6 in your app.
• Download and update the WinUI Gallery to see the WinUI 3 updates firsthand.

Getting Started

To get started using Windows App SDK to develop Windows apps, check out the following documentation:

• Install developer tools .
• Create a WinUI 3 app.
• Continue your development journey.

---

This discussion was created from the release Windows App SDK 1.6.0 (1.6.240829007).

[ynkdir]

Is Microsoft.WindowsAppRuntime.Bootstrap.dll removed from installer?

[ynkdir]

Thank you for reply.

I was using system installed bootstrap dll in "C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.*" by LoadLibrary so that I can distribute my library without bundling the dll.
It seems like I have to bundle bootstrap dll.

[DarranRowe]

That library isn't the a "system installed bootstrap dll". That is one of the core Windows App SDK libraries, and it is still part of the package.

But as stated, it is not where the exports for the bootstrap API are.

This is the list of exports from that library, and while the Windows App Runtime dynamic dependency API is exported from it, the bootstrapper isn't. I would have to double check the exports, but I don't think the bootstrapper API has ever been exported from it. The important thing is that both MddBootstrapInitialize and MddBootstrapInitialize2 are both documented to be exported from Microsoft.WindowsAppRuntime.Bootstrap.dll. This unfortunately means that if the exports were previously in Microsoft.WindowsAppRuntime.dll, it was an undocumented implementation detail and this can change.

[ynkdir]

What I wanted to say is that WindowsAppSDK 1.5 runtime package has Microsoft.WindowsAppRuntime.Bootstrap.dll in the installed directory.

"C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.5_5001.214.1843.0_x64__8wekyb3d8bb\Microsoft.WindowsAppRuntime.Bootstrap.dll"

And I can call MddBootstrapInitialize() in the dll.

But WindowsAppSDK 1.6 runtime package doesn't have Microsoft.WindowsAppRuntime.Bootstrap.dll in the installed directory.

I don't complain to it. I just wanted to confirm that this is intented.

[DarranRowe]

Well, there is documentation hinting that Microsoft.WindowsAppRuntime.Bootstrap.dll being part of the Windows App Runtime package is a mistake.

In the "Use the Windows App SDK runtime for apps packaged with external location or unpackaged" documentation, the section named "Using the bootstrapper API" states:

"That library is a small DLL that you must distribute with your app; it's not part of the framework package itself."

So the fact that it was found as part of the framework package is, by this documentation, a mistake.

[ynkdir]

I understand. Thank you.

[Slion]

When updating a brand new project from Template Studio from 1.4 to 1.6 it wants net8 which is using the new RuntimeIndentifiers like win-x64 instead of ̀ win10-x64` but even after fixing those the template Core DLL would still not compile complaining about RID. Not sure if that's because of dependency or something. I'll stick to net7 and v1.5 for now.

[ghost1372]

did you change rid in pubxml files?

[Slion]

Not sure what those are, so probably not 😁 Ok found them… I'll give it a try then. Should have done a search for win10- really 🫣

[Slion]

Ok so I could go one step further but then it seems quite a few NuGet dependencies are not yet available for net8 so I'll definitely stick to v1.5 for now.

[Diegorro98]

In the release notes, at New APIs, the following new APIs are mentioned:

Microsoft.Windows.Storage

    ApplicationData
    ApplicationDataContainer
    ApplicationDataContract
    ApplicationDataCreateDisposition
    ApplicationDataLocality

I have been using Windows.Storage API for all my WASDK projects and I would like to know which are the differences or the reasons to bring this new API, because if it has advantages, it might be interesting to use the new one. Or maybe it is just a renaming...

[ghost1372]

There are some new API that can be used in unpackaged app but not released yet
#4057

Here you can see its changes and benefits

https://github.com/microsoft/WindowsAppSDK/blob/main/specs/applicationdata/ApplicationData.md

[duwenlong2]

I found during my search that App sdk 1.6 seems to support AOT compilation for WinUI3. Since I couldn't find the sample program, I tried following the documentation process but didn't experience AOT compilation of WinUI3. Can you provide an example of this? Or can you give me some help? A C # empty WinUI3 project was created with the following configuration:

Refer to the following two documents:
https://learn.microsoft.com/zh-cn/windows/apps/windows-app-sdk/stable-channel#version-16

https://learn.microsoft.com/zh-cn/dotnet/core/deploying/native-aot/?tabs=windows%2Cnet9plus#publish-native-aot-using-the-cli

[manodasanW]

Did you create a MSIX package for your app? The publishing step is when AOT compilation happens.