Forum Discussion
Solved
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 ...
- Hello, 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!
Tim Mangan, TIMOTHY_MANGAN, John Vintzel, Bogdan Mitrache - UR all great pros, if somebody could just point me in the right direction, I would be very glad. Thank you.
It looks like quite an ordinary task, but I read all the docs and dozens of posts on the internet and didn't find a good solution for it, I think I'm losing something obvious.
As I understood, with dependencies I can point to shared "framework" packages only, but I don't have one. With install actions or with PSF I will need to bundle the Dotnet installer with me, or download it from the MS site and run it with /quiet (because install-dotnet.ps1 intended only for CI machines), all of that looks far from an optimal solution. The best solution from bad ones I see is to use self-contained publish, but it's not the best too.
It looks like quite an ordinary task, but I read all the docs and dozens of posts on the internet and didn't find a good solution for it, I think I'm losing something obvious.
As I understood, with dependencies I can point to shared "framework" packages only, but I don't have one. With install actions or with PSF I will need to bundle the Dotnet installer with me, or download it from the MS site and run it with /quiet (because install-dotnet.ps1 intended only for CI machines), all of that looks far from an optimal solution. The best solution from bad ones I see is to use self-contained publish, but it's not the best too.