Skip to content

Conversation

@florelis
Copy link
Member

@florelis florelis commented Nov 14, 2025

The solution does not build in VS 2026 because it defaults to using the v140 toolset (VS 2015), which is no longer supported.
This PR adds the configuration to use the latest toolset v145 in VS 2026 (v18), and removes the options for v140 (VS 2015) and v141 (VS 2017). I'm also setting this in the Directory.Build.props and removing the configuration from the individual projects.

Microsoft Reviewers: Open in CodeFlow

JohnMcPMS
JohnMcPMS previously approved these changes Nov 15, 2025
Copy link
Member

@JohnMcPMS JohnMcPMS left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm quite impressed that this is all it took. Maybe we are standards compliant at the moment.

@florelis florelis merged commit ac226ee into microsoft:master Nov 17, 2025
5 of 9 checks passed
@florelis florelis deleted the retarget branch November 17, 2025 19:24
@florelis florelis mentioned this pull request Nov 25, 2025
florelis added a commit that referenced this pull request Dec 1, 2025
Follow-up to #5882 to fix some issues I saw when building with VS2026.

* Add back the setting for `ReleaseStatic` configuration that I deleted
by accident. (The build error without this says that a the binary needs
an entrypoint. So I'm assuming that without the `ConfigurationType` it
assumes application instead of library.)
* Added a missing include to a header.
* Moved a template definition to be after the definition for a type it
references.
* Suppressed a warning from WIL code.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants