-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Utilize .NET SDK workloads infrastructure to generate runtime pack msis for Visual Studio #3415
Comments
aspnet version is here. I'd recommend coordinating to do both at the same time. There's a monday sync on workloads if someone wants to come learn more. |
+1 to making this happen. It would be useful for internal test pipelines that run using local machine accounts to be able to have these packages downloaded by the VS installer. Bonus points if you maintain two components; one for 6.0 and one for 7.0. |
We will have to find an owner here to drive this. |
@merriemcgaw This comes up most months as feedback from VS and moreso near the end of the release. Might be nice to explore this for 9 if there is capacity. |
That sounds quite interesting. @pchaurasia14 as FYI too. |
Is there an existing issue for this?
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.
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
The text was updated successfully, but these errors were encountered: