Unclaimed project
Are you a maintainer of msvcup? Claim this project to take control of your public changelog and roadmap.
This releases a big change to how msvcup up works. Previously, msvcup would install its packages to the global C:\msvcup path. Now, the msvcup "install" subcommand takes a directory where it installs everything to. The lock file also gets written alongside this directory. This solves the problem that you can now have multiple instances of the toolchain which may be on the same high level "version", but actually have different contents based on what actually gets installed from Microsoft's manifest files. There are still some changes to make the process of upgrading more seamless, but, for now users can always clean their install directory and re-install if they ever run into issues. Also note that all network requests are cached so re-installing the same packages doesn't require any network access.
The bulk of these changes were done in: https://github.com/marler8997/msvcup/pull/14
Full Changelog: https://github.com/marler8997/msvcup/compare/v2026_02_07...v2026_02_21