Open jonathanpeppers opened 2 years ago
/cc @dsplaisted @wli3
I'd suggest solving this with #21741. We are already going to need to group multiple library packs into the same MSI, so I think we should support doing the same thing with other types of workload packs.
We can also add more flexibility to runtime packs if we need to, but if the only issue here is that it's a bunch of different MSIs, then I would just solve it by bundling the multiple packs into the same MSI.
Is your feature request related to a problem? Please describe.
Currently the
maui
workload has a lot of packs:All of these come via
UseMaui=true
, but you can select different sets of them withUseMauiEssentials=true
orUseMauiCore=true
.What I would like to do, is collapse these into:
And just put all the platforms in one pack for each. The packs are small in size, because they are mostly managed code.
I attempted this here: https://github.com/dotnet/maui/pull/2743
But what happens for the
data/RuntimeList.xml
file:Is you end up with errors like:
So it just seems like alll assemblies are added.
Is there a way to put all the platforms in one pack?
Describe the solution you'd like
@Profile
would be respected for Runtime packs? It's not clear to me if it's being respected for targeting/Ref packs, but those don't give an error.If we could do this, it would eliminate 24
.msi
's installed when runningdotnet workload install maui
in an Admin location. I think it might be a significant performance win, sincemsiexec
can only install one at a time?