@@ -8,7 +8,7 @@ This action will help discover where the `MSBuild` tool is and automatically add
88
99``` yml
1010- name : Add msbuild to PATH
11- uses : microsoft/setup-msbuild@v1.1
11+ uses : microsoft/setup-msbuild@v2
1212
1313- name : Build app for release
1414 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
2828
2929` ` ` yml
3030- name: Add msbuild to PATH
31- uses: microsoft/setup-msbuild@v1.1
31+ uses: microsoft/setup-msbuild@v2
3232 with:
3333 vs-version: '[16.4,16.5)'
3434` ` `
@@ -41,7 +41,7 @@ If you need your Actions runner to target a pre-release version of Visual Studio
4141
4242` ` ` yml
4343- name: Add msbuild to PATH
44- uses: microsoft/setup-msbuild@v1.1
44+ uses: microsoft/setup-msbuild@v2
4545 with:
4646 vs-prerelease: true
4747` ` `
@@ -52,7 +52,7 @@ By default the action will use the x86 architecture for MSBuild, but it is possi
5252
5353` ` ` yml
5454- name: Add msbuild to PATH
55- uses: microsoft/setup-msbuild@v1.1
55+ uses: microsoft/setup-msbuild@v2
5656 with:
5757 msbuild-architecture: x64
5858` ` `
@@ -63,7 +63,7 @@ This makes use of the vswhere tool which is a tool delivered by Microsoft to hel
6363
6464` ` ` yml
6565- name: Add msbuild to PATH
66- uses: microsoft/setup-msbuild@v1.1
66+ uses: microsoft/setup-msbuild@v2
6767 with:
6868 vswhere-path: 'C:\p ath\t o\y our\t ools\'
6969` ` `
0 commit comments