actions/setup-msbuild
1
0
Fork 0
mirror of https://github.com/microsoft/setup-msbuild.git synced 2024-09-19 22:30:05 +07:00
Code Issues Packages Projects Releases Wiki Activity

Updated docs [skip ci]

Browse Source
This commit is contained in:
Tim Heuer 2021-11-01 20:07:20 -07:00
parent e48d8c6605
commit c4a66a0e8a
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -7,7 +7,7 @@ You know how handy that 'Visual Studio Developer Command Prompt' is on your loca
```yml ```yml
- name: Add msbuild to PATH - name: Add msbuild to PATH
uses: microsoft/setup-msbuild@v1.0.3 uses: microsoft/setup-msbuild@v1.1
``` ```
## Specifying specific versions of Visual Studio ## Specifying specific versions of Visual Studio
@ -15,7 +15,7 @@ You may have a situation where your Actions runner has multiple versions of Visu
```yml ```yml
- name: Add msbuild to PATH - name: Add msbuild to PATH
uses: microsoft/setup-msbuild@v1.0.3 uses: microsoft/setup-msbuild@v1.1
with: with:
vs-version: '[16.4,16.5)' vs-version: '[16.4,16.5)'
``` ```
@ -27,7 +27,7 @@ This makes use of the vswhere tool which is a tool delivered by Microsoft to hel
```yml ```yml
- name: Add msbuild to PATH - name: Add msbuild to PATH
uses: microsoft/setup-msbuild@v1.0.3 uses: microsoft/setup-msbuild@v1.1
with: with:
vswhere-path: 'C:\path\to\your\tools\' vswhere-path: 'C:\path\to\your\tools\'
``` ```

2
building-release.md
View File

@ -7,7 +7,7 @@ This is a quick document to walk through the process of building and releasing.
- Build the branch/package - Build the branch/package
- `npm install` - `npm install`
- `npm run build` - `npm run build`
- `npm run package` - `npm run pack`
- Prune the dependencies to only production - Prune the dependencies to only production
- `npm prune --production` - `npm prune --production`
- Uncomment `node_modules` in `.gitignore` **for this branch only** - Uncomment `node_modules` in `.gitignore` **for this branch only**