You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think some Visual Studio users may be interested in the minimal components needed to get Rust set up. I think those components can be installed by launching Visual Studio Installer and importing a .vsconfig file.
Hi, @cataggar, I'm just wondering whether this technique is definitely correct, and vetted. I ask because of the "I think those components can", and the query about whether or not VS Installer can take a url.
It takes a URL for the channel manifest and you can pass --add <component>, but a .vsconfig file is supported, yes. I designed it to be rooted in a repo (in hindsight, we should've spec'd/supported it more like a .gitignore file that can work at multiple levels) and we added support for it ~15.7.
# defaults to the Enterprise product for whatever channel you downloaded, but any could be selected instead.vs_enterprise.exe--installPath C:\DevStudio --add Microsoft.VisualStudio.Component.VC.Tools.x86.x64 -add Microsoft.VisualStudio.Component.VC.Redist.14.Latest
One thing to note is that while workload and component IDs aren't supposed to change, it has and will likely happen again. It's not often but, IIRC, these component IDs have been stable.
Thanks @heaths! I've committed a visual-cpp-build-tools.vsconfig to a repo with setup instructions. Thanks for the links @stevewhims. Hopefully, the docs can be updated when/if it gets vetted.
I think some Visual Studio users may be interested in the minimal components needed to get Rust set up. I think those components can be installed by launching Visual Studio Installer and importing a .vsconfig file.
In rust-lang/rustup#1462 (comment), I suggested creating a
visual-cpp-build-tools.vsconfig
with:Can the Visual Studio Installer take a URL? cc @heaths
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: