fix vs2026 cant compile

[Redwarx008]

PR Details

My VS 2026 wouldn't compile no matter what I did because Windows Desktop couldn't find MSVC 143 (even though I had it installed). So I changed the target platform to 145, and everything worked fine. Since the project is already being compiled using VS2026, it's unnecessary for these projects to depend on 143.

Related Issue

Types of changes

• Docs change / refactoring / dependency upgrade
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• My change requires a change to the documentation.
• I have added tests to cover my changes.
• All new and existing tests passed.
• I have built and run the editor to try this change out.

[xen2]

Thanks!
I remember skipping that change at the time because I thought it would force us to bump our C++ redistributable to VS2026 (we would need to upgrade in prerequisite installer).
However, it seems that v145 is still backward compatible with VS 2019 C++ redist, so it looks safe to keep as is.

[Kryptos-FR]

Is v145 available in VS 2022 though? If not, it means we are now forcing the use of VS 2026 in order to build Stride. The doc would need update.

[VaclavElias]

Is v145 available in VS 2022 though? If not, it means we are now forcing the use of VS 2026 in order to build Stride. The doc would need update.

But you can build Stride 4.3 only with VS 2026?

[xen2]

I thought VS2026 was already a requirement since .NET 10.0 switch (Compiling .NET 10 with Visual Studio 2022 is generally not officially supported)
README.md was updated but I didn't check the doc in detail.

[VaclavElias]

Also, should this PR update also this?

stride/README.md

Lines 44 to 46 in d6c133c

	- **MSVC v143 - VS 2022 C++ x64/x86 build tools (Latest)** *(should be enabled by default)*
	- **MSVC v143 - VS 2022 C++ ARM64/ARM64EC build tools (Latest)** *(not enabled by default, click Individual components tab to select or search)*
	- **C++/CLI support for v143 build tools (Latest)** *(not enabled by default)*

Note, ideally, we need exact wordings e.g. MSVC v143 - VS 2022 C++ ARM64/ARM64EC build tools (Latest) as it is in the Visual Studio installer, so it is easy to find/filter. Obviously, the exact wordings is going to work only for EN and that is ok. Also, I believe they changed the wordings at least twice in the last 6 months 🤣 but we can just use the latest..

I can do a separate PR for stride-docs..