actions
Visual Studio 2022 to 17.14
Tool name
Visual Studio
Tool license
https://visualstudio.microsoft.com/license-terms/vs2022-ga-proenterprise
Add or update?
- [ ] Add
- [x] Update
Desired version
17.14
Approximate size
No response
Brief description of tool
Visual Studio 17.14 was released two weeks ago. I'm opening this issue to have something easily trackable for when it gets added to the runner images.
Xref #11591
URL for tool's homepage
https://learn.microsoft.com/en-us/visualstudio/releases/2022/release-notes
Provide a basic test case to validate the tool's functionality.
Compile some C/C++ programs
Platforms where you need the tool
- [x] Azure DevOps
- [ ] GitHub Actions
Runner images where you need the tool
- [ ] Ubuntu 22.04
- [ ] Ubuntu 24.04
- [ ] macOS 13
- [ ] macOS 13 Arm64
- [ ] macOS 14
- [ ] macOS 14 Arm64
- [ ] macOS 15
- [ ] macOS 15 Arm64
- [ ] Windows Server 2019
- [x] Windows Server 2022
- [x] Windows Server 2025
Can this tool be installed during the build?
Tool installation time in runtime
No response
Are you willing to submit a PR?
No response
Hi @h-vetinari , Thank you for bringing this issue to our attention. We will look into this issue and will update you after investigating.
@RaviAkshintala @akilesh-amaran This is killing my team right now! Because of the older version, we're hitting this:
(CoreCompile target) ->
CSC : error CS9057: The analyzer assembly 'C:\Program Files\dotnet\sdk\9.0.300\Sdks\Microsoft.NET.Sdk\codestyle\cs\Microsoft.CodeAnalysis.CodeStyle.dll' references version '4.14.0.0' of the compiler, which is newer than the currently running version '4.13.0.0'.
Hey @jamiehankins, I'm in the same boat as you. Microsoft never provided a way to choose the MSVC version in the image, so whenever it (or some other parts of the toolchain) changes, stuff breaks.
The only reason I've opened this issue is to get some advance notice so I can respond more quickly to the breakage that will happen on our side. I don't have that luxury, but you might want to consider using clang-cl as a (binary compatible) MSVC replacement. 🤷
@h-vetinari sorry, I meant to tag the other person.
Unfortunately, changing to another compiler isn't an option.
Unfortunately, changing to another compiler isn't an option.
It's always an option if the pain becomes big enough to outweigh whatever benefits remain, and I think the ecosystem will get to that point eventually. In my case it would affect switching 10'000s of artefacts that would need to switch compilers, so not a small operation. But longterm, I can imagine it happening nevertheless.
How can I get the installChannel ID to add to the toolset.json and test Visual Studio 17.14 on my side? I don’t know where to find this information.
Unfortunately, changing to another compiler isn't an option.
It's always an option if the pain becomes big enough to outweigh whatever benefits remain...
It's a C# .NET 9 project. Believe me, it's not an option. 🙃
Anyhow, I found the magic sauce I needed. There's a preprocessor define that tells it to use the SDK compiler instead of the VS compiler, so I'm good.
So I guess in a way, I took your advice, just not exactly the way you meant. 🙂
Hi all, Visual Studio 17.14 has been updated in the Windows Server 2022 and 2025 images. We are closing this issue, Thanks.
