Admin install for optional workloads

[marcpopMSFT]

• [x] VS (no new feature needed) -- PM needs to sign off on IPA
• [x] Don’t put workloads into ARP
• [x] Investigate the best way to trigger IPA for missing optional workloads
• [x] Finalizer to clean up standalone installs
• [x] Package caching for MSI (source location, compatible with VS package cache relocation)
• [x] Sign verification
• [x] Rollback
• [x] Manifest update
• [ ] (stand alone installer)Exe/msi. Convert CLI command to msi command. Muti-targeted library.
• [x] Update, especially when crossing stream (VS and standalone installer)
• [x] Error experience when standalone installer missing optional workloads
• [ ] Retries when other installs slip through. This would cause an error when 2 MSIS are running, e.g. you install a workload, but then at same time install/uninstall/repair another application, etc. We mitigate that today by turning off Windows Update Agent. If you’re 90% into a workload and hit this error, we would rollback, but if the other install is still running, rollback would fail as well.
• [ ] Blocking if the machine has pending reboots.
• [ ] Dealing with locked files that require reboots to complete installs. I’m not worried about this just yet, and it’s mostly to round out the installer.

other than IPA all preview 6

[marcpopMSFT]

@joeloff We had a review of this with the project system team. One item to investigate are around how In-product Acquisition will work with this. Presumably we return a list of individual component IDs and project system will trigger IPA for that but we need to confirm that VS setup supports that as that's different than how project system triggers IPA today (today they do it on project load for specific project type GUIDS).

Another was finding out how Codespaces will work wrt IPA if they components are not pre-configured on the Codespaces server.

Separately, we do need to investigate the project system experience for Xamarin projects but we can take that offline.

[joeloff]

Yup, IPA in CodeSpaces might be tricky. The idea with CodeSpaces generally is that everything you need is already installed. I'll need to check with VS folks how they handle optional workloads, because it will likely need to perform a machine wide install to modify VS setup.

The idea I originally had was to add the classifiers to the workloads for .NET Core. It's possible to express something like "when you open a .csproj that contains a property named X and its value is 17 then install something". I've done something similar using a project type GUID + component (without needing project system changes), so I was going along this route.

I'm hopeful to have a proof of concept ready soon

[marcpopMSFT]

I added a couple of checkboxes above to track these two issues. For the second in particular, the project system team is very interested to know what work they may or may not have as for them, the existing way they trigger IPA is based on project type and so won't work for optional workloads as is.

[wli3]

@marcpopMSFT note (stand alone installer)Exe/msi. Convert CLI command to msi command. Muti-targeted library. is now committed after today's meeting. Since Blazor desktop would want this.

[marcpopMSFT]

Completed all planned work and we have separate issues tracking any additional work here.