actions/setup-msbuild
1
0
Fork 0
mirror of https://github.com/microsoft/setup-msbuild.git synced 2026-03-15 05:32:14 +07:00
Code Issues Packages Projects Releases Wiki Activity

fix: move to node24

Browse Source
This commit is contained in:
Tim Heuer
2026-03-12 10:55:15 -07:00
parent 767f00a3f0
commit c77b6bc497
6 changed files with 3210 additions and 3201 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
README.md
View File

@@ -9,7 +9,7 @@ This action will help discover where the `MSBuild` tool is and automatically add
```yml
- name: Add msbuild to PATH
uses: microsoft/setup-msbuild@v2
uses: microsoft/setup-msbuild@v3
- name: Build app for release
run: msbuild src\YourProjectFile.csproj -t:rebuild -verbosity:diag -property:Configuration=Release
@@ -29,7 +29,7 @@ You may have a situation where your Actions runner has multiple versions of Visu
```yml
- name: Add msbuild to PATH
uses: microsoft/setup-msbuild@v2
uses: microsoft/setup-msbuild@v3
with:
vs-version: '[16.4,16.5)'
```
@@ -42,7 +42,7 @@ If you need your Actions runner to target a pre-release version of Visual Studio
```yml
- name: Add msbuild to PATH
uses: microsoft/setup-msbuild@v2
uses: microsoft/setup-msbuild@v3
with:
vs-prerelease: true
```
@@ -53,7 +53,7 @@ By default the action will use the x86 architecture for MSBuild, but it is possi
```yml
- name: Add msbuild to PATH
uses: microsoft/setup-msbuild@v2
uses: microsoft/setup-msbuild@v3
with:
msbuild-architecture: x64
```
@@ -64,7 +64,7 @@ This makes use of the vswhere tool which is a tool delivered by Microsoft to hel
```yml
- name: Add msbuild to PATH
uses: microsoft/setup-msbuild@v2
uses: microsoft/setup-msbuild@v3
with:
vswhere-path: 'C:\path\to\your\tools\'
```