-
Notifications
You must be signed in to change notification settings - Fork 111
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
Visual Studio 2022 #541
Comments
Bumping this after discovering that VS2019 can no longer be downloaded (without an account paying $$ to MS). Currently unable to build Micro-Manager on a fresh Windows system. |
See also: micro-manager/micro-manager#2062 |
The nightly build has now been switched to a new Windows image containing VS2022 (with VS2019 build tools). (It only took 2 and a half days to get that working!) This has been tested and will apply starting with the next nightly build. This means that we are now almost ready to switch the projects to use the VS2022 toolset, but I suggest that we wait until a time when we don't have any major pull requests pending (or at least none that add, remove, or rename projects), because touching all the project files can complicate merging. We'll also need to update the VC redistributable that we ship with our installer. |
(I don't think the VS2019 build tools installable with VS2022 are going away any time soon; VS2019 EOL is still a few years ahead.) |
Updating the projects is likely trivial; most of the work will be in updating the build worker VM images.
The text was updated successfully, but these errors were encountered: