actions/setup-msbuild
1
0
Fork 0
mirror of https://github.com/microsoft/setup-msbuild.git synced 2024-11-24 12:31:06 +07:00
Code Issues Packages Projects Releases Wiki Activity

Update README examples [skip ci]

Browse Source 
Update readme examples to use latest version major
This commit is contained in:
Tim Heuer 2024-01-31 22:46:42 -08:00 committed by GitHub
parent 6fb0222098
commit 31e0ba28c7
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
README.md
View File

@ -8,7 +8,7 @@ This action will help discover where the `MSBuild` tool is and automatically add
```yml
- name: Add msbuild to PATH
uses: microsoft/setup-msbuild@v1.1
uses: microsoft/setup-msbuild@v2
- name: Build app for release
run: msbuild src\YourProjectFile.csproj -t:rebuild -verbosity:diag -property:Configuration=Release
@ -28,7 +28,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@v1.1
uses: microsoft/setup-msbuild@v2
with:
vs-version: '[16.4,16.5)'
```
@ -41,7 +41,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@v1.1
uses: microsoft/setup-msbuild@v2
with:
vs-prerelease: true
```
@ -52,7 +52,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@v1.1
uses: microsoft/setup-msbuild@v2
with:
msbuild-architecture: x64
```
@ -63,7 +63,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@v1.1
uses: microsoft/setup-msbuild@v2
with:
vswhere-path: 'C:\path\to\your\tools\'
```