Forum Discussion
levyas
May 20, 2021Brass Contributor
MSIX: How to achieve automatic install of .net 5 required for my application?
Hi! I wrote a WPF program using .NET 5, packed it into the MSIX bundle (Release, x86 and x64) as a framework-dependent package. Everything seems fine, but there is one very annoying thing: on the ...
- May 24, 2021Hello, if it's an application based on .NET Core / .NET 5 (as I seem to understand from the description), the suggested and best way to distribuite via MSIX is to use the self-deployment approach. Thanks to MSIX features like differential updates and single disk instance, you don't have to worry too much about the increased size, since the runtime will be downloaded only at the first install.
Otherwise, if you don't like self-deployment, you will need to use a script to pre-install the runtime. You can leverage some of the available script we release for CI/CD purposes here: https://docs.microsoft.com/en-us/dotnet/core/tools/dotnet-install-script
I hope it helps!
Telemak68
Jun 09, 2021Copper Contributor
Thanks for your considerations, Matteo. As you can see, this seems to be a common deployment scenario, and in many cases a system-wide deployment of .NET prerequisites may be the only plausible option. BTW, the popular MsixHero tool also utilizes the .NET system-wide deployment model instead of rather problematic self-contained option, and adding support for .NET distribution would significantly simplify its deployment. I would appreciate if you could submit to the MSIX team the request to add at least .NET and Asp.NET packages to the subset of supported libraries, this would be indeed very helpful. Thank you very much in advance!
Jun 09, 2021
To state the obvious, if Microsoft wants to encourage developers to move to these technologies, there must be a better way to handle the dependencies outside of those suggested here. The same reasons for wanting the components outlined by Matteo that are supported as package dependencies apply to .Net 5, and Microsoft should add a solution. The package dependency route seems the most obvious to me, but I'm guessing there are technical reasons this hasn't been (yet).
- Matteo PaganiJun 09, 2021
Microsoft
Sure, feel free to send me a mail at name.surname [at] microsoft.com - Telemak68Jun 09, 2021Copper ContributorMany thanks, Matteo, much appreciated!
I think the requested extension will be very beneficial for ISVs.
BTW, I have a question about your recommendations in Chapter 4 of your MSIX Succinctly book (https://www.syncfusion.com/succinctly-free-ebooks/msix-succinctly/the-package-support-framework) Would it be possible to clarify with you some issues in this regard? - Matteo PaganiJun 09, 2021
Microsoft
Thanks for the feedback Timothy and Valery. I'll make sure to convey it to the MSIX team, to see if they can start a conversation with the .NET team on this topic.