Adding support for VS2026

[andysterland]

Description

Adding 18 to the valid set of VS version numbers. No new tests were added, consistent with the change to add 17. In general it looks like the tasks relies on distinguishing being between versions of VS < 16 or later, with the logic for >= 16 versions being the same - and the behavior for 18.0 is the same

Issue

---

Package Name

msbuildhelpers

---

Risk Assessment (Low / Medium / High)

Low

Unit Tests Added or Updated

• [ x] Manual tests performed

---

Additional Testing Performed

---

Documentation Changes Required (Yes / No)

No

Dependencies

None

Checklist

• Related issue linked (if applicable)
• Package version was bumped — see versioning guide
• Verified the package behaves as expected
• CLA signed (if applicable) — see Contributor License Agreement

---

[ToreDemant]

Should this fallback solution also be extended with 2026?

azure-pipelines-tasks-common-packages/common-npm-packages/packaging-common/nuget/NuGetToolGetter.ts

Line 154 in 6a37f0e

const msbuild2022Path = 'C:/Program Files/Microsoft Visual Studio/2022/Enterprise/MSBuild/Current/Bin/msbuild.exe';