Howard Kapustein

Ping. Any update?

> No updates as of yet, sorry. > > @DrusTheAxe Do you or the WindowsAppSDK team have cycles to help contribute the Nuget creation automation? That would certainly help move...

@MikeHillberg @BenJKuhn @Scottj1s is a Single File App (PublishSingleFile = true) a problem for WinAppSDK or a N/A and this is a WinUI issue? If the latter please transfer it...

Please run the following command and share the results: ``` powershell -c "$(get-appxpackage *micro*win*apprun*).packagefullname" ``` The description and callstack sounds like WindowsAppSDK issue [#2592](https://github.com/microsoft/WindowsAppSDK/issues/2592) -- if the Bootstrap API doesn't...

SUGGESTION: Drop 'C++/WinRT' BEFORE: `WindowsAppSDK, WinAppSDK, WinUI, XAML, C++, C++/WinRT` = 54 chars AFTER: `WindowsAppSDK, WinAppSDK, WinUI, XAML, C++` = 43 chars That aligns better with the C# VSIX tags...

Do the tags need whitespace or just comma separator? `WindowsAppSDK, WinAppSDK, WinUI, XAML, C++` is it equally valid to say `WindowsAppSDK,WinAppSDK,WinUI,XAML,C++` ?

Those interested in CMake (or other build systems) please check out https://github.com/microsoft/WindowsAppSDK/discussions/1891#discussioncomment-1881153

You're right, this is an appmodel issue not WinUI. `Package.PublisherDisplayName` not always available is one of the pain points we've incrementally (though not always completely) improved over the years. Expanding...

That's an interesting idea. What sorts of data are you thinking of? Do you have specific scenarios in mind? AppxManifest.xml supports package-scope as well as application-scope extensions as a general...

Yes, I can see how a 'packageExtension' would be very helpful for your scenario. This warrants its own issue. Would you be so kind as to post a new Issue/Proposal?...