dotnet / dotnet/aspnetcore

Utilize .NET SDK workloads infrastructure to generate runtime pack msis for Visual Studio

Open
#46,427 13 comments 0 reactions 0 assignees View on GitHub
area-infrastructure task
Dominant language
C#
Stars
38.4k
Forks
10.9k
Avg merge
2d 10h
Merged PRs (30d)
281

Description

### Is there an existing issue for this?

- [X] I have searched the existing issues

### Is your feature request related to a problem? Please describe the problem.

Today customers targeting self-contained applications download the runtime packs at build time. This prevents offline scenarios with Visual Studio. This also impacts internal customers that install pre-release builds.

### Describe the solution you'd like

Expand the existing runtime pack infrastructure used in the runtime repo today to the aspnet and windows desktop runtime packs.

- Do similar authoring to what exists in the runtime repo
- https://github.com/dotnet/runtime/blob/78f5a9839ac7d49a3cfaa6f4015a90b1cc846fa1/src/mono/nuget/Microsoft.NET.Workload.Mono.Toolchain.Manifest/WorkloadManifest.json.in#L131
- provide better descriptions than what is in the runtime repo
- Update the VS setupauthoring (see mail thread for link to existing authoring) to add the runtime pack as an optional component
- Add the baseline manifest into the installer repo
- https://github.com/dotnet/installer/blob/main/src/redist/targets/BundledManifests.targets

Drawbacks are that this could impact servicing codeflow in the future. The recommendation is to only produce these for windows versions that VS ships on (the idea being we still download for cross-compiling but for the RID that matches the OS, we can provide that to VS).

See email or ask marcpop for more details

### Additional context

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.