installer
installer copied to clipboard
Please produce an "All runtimes" package
Simple request, probably not the right place to ask it, but it's the place I could find. Please add another "bundle" download that includes the core runtime, the desktop components and the asp.net components in a single package.
If you have an application like mine, which consists of desktop apps, windows services and websites, all of the runtimes are required. The error messages that appear if one does not install everything are not particularly helpful as they are overly generic and don't specifically name the runtime(s) that are missing.
Is this something to direct to you @NikolaMilosavljevic?
Is this something to direct to you @NikolaMilosavljevic?
I think this should go to the top-level repo, dotnet/installer. It consumes aspnetcore, runtime and windowsdesktop artifacts and is likely the best option for an 'all-runtimes' package.
cc @marcpopMSFT @joeloff
The hosting bundle would be the logical choice because it already supports configuration options, but the downside is that it carries all architectures and needs to be installed from the command line to select individual items.
@larudev are you looking for a single installer you can point your users to download when using your application?
This is more of a release team prioritization question as we'd be creating a new bundle for every architecture that installed all three but not the SDK. It's a moderate amount of work and would confuse our download page even more. CC @rbhanda @leecow @jamshedd
Perhaps we work on improving our acquisition story instead of investing in this but that's potentially a long way away.
I don't believe there's a strong signal in support of a single installer for the 3 runtimes. Most customers we work with use 1 or 2 of the runtimes - either .NET Core runtime, or .NET Core runtime + ASP.NET Core runtime, or .NET Core runtime + desktop runtime. Like Marc said this would create more confusion about the options on our download page so I am not going to jump into doing this just yet. If we see a larger share of customers start using all 3 runtimes then we can consider it.
Old issue triage: We have a separate customer development effort around acquisition ongoing by @ashnaga Will close this in favor of that more formal effort.