Add support for Visual Studio 2026 #1763
Open
+13
−5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request adds support for Visual Studio 2026. Previously, users were forced to use Visual Studio 2022, but this PR now allows users to optionally use the latest version of Visual Studio 2026 instead.
This PR adds an additional
createallprojectsscript to generate the solution for the use in Visual Studio 2026 calledcreateallprojects-vs2026.bat.Thankfully, Visual Studio 2026 offers backward compatibility with Visual Studio 2022 so that VS2022 projects can be seamlessly upgraded to Visual Studio 2026. But there is one caveat with this when it comes to the Source Engine. The source engine uses MSVC version 143 to build the project, which is not supported in Visual Studio 2026. This dissuades people (such as me) from installing the component, which ends up resulting in this happening every time you regenerate the solution:
To resolve this, projects generated for Visual Studio 2026 will use MSVC v145 instead. Thankfully, the change in platform toolkit versions doesn't appear to cause any issues while building, but if you are experiencing compilation issues directly after upgrading, I suggest that you clean the solution and then rebuild it. If that doesn't work, please let me know in the comments.
Additionally, Visual Studio 2022 support was retained as to avoid forcing users to upgrade. Some users may be unable or unwilling to upgrade, whether it being their device not being able to run it, or because of certain features that VS2026 support (such as copilot).
The README has also been updated to accommodate for the added support of VS2026 & lists down the required components.