-
Notifications
You must be signed in to change notification settings - Fork 447
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.NET 6 support for Framework Packaging #7725
Comments
Any news on that issue? |
It's surely possible, considering .NET 5 UWP apps are already technically possible. Previews shouldn't be distributed via framework packages anyway so I wouldn't expect it soon. I mostly opened this issue hoping for a firm commitment for .NET 5, since I really don't want to wait for the next LTS (6.0) for a good distribution method. |
@terrajobst I see that this got raised in the Deployment and Servicing guidance issue, but it appears not to have made the cut for the proposed feature list for .NET 6.0? |
.NET 6 is the future of .NET development, and MSIX is the future of Windows app deployment. Please add support for Framework Packaging to allow creation of .NET 5 apps packaged with MSIX without redistributing .NET 6 with each app that depends on it.
Ideally, this will be followed up with a Visual Studio template referencing .NET 6 to use this framework package, along with the user's choice of UI framework (WinUI, WPF, WinForms, or blank/none).
Consider working with the Windows Store team to notify users when their framework package .NET runtime is out of date (assuming major releases are packaged separately).
Edit: Updated from 5 to 6, as my request remains the same but clearly the .NET 5 window has passed.
The text was updated successfully, but these errors were encountered: