huahaofeng
/
aspnetcore
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
aspnetcore/eng/tools/BaselineGenerator
History
Doug Bunting 17ea650638
Add `--update` option to BaselineGenerator (#9956) 
- aspnet/AspNetCore-Internal#1649
- remove `$(StartArguments}` from project; conflicts with `--update`
- support v3 source _automatically_ when not using `--update`
  - use NuGet's V3 source by default
- update README.md

nits:
- `--source` -> `--package-source` due to conflict with a `dotnet` argument
- address Markdown lint warnings in README.md
- grab a couple of improvements from 'release/2.2'
  - never exit silently
  - remove `first` special case
 		2019-05-06 15:04:15 -07:00
..
BaselineGenerator.csproj Add `--update` option to BaselineGenerator (#9956) 2019-05-06 15:04:15 -07:00
Program.cs Add `--update` option to BaselineGenerator (#9956) 2019-05-06 15:04:15 -07:00
README.md Add `--update` option to BaselineGenerator (#9956) 2019-05-06 15:04:15 -07:00

README.md

BaselineGenerator

This tool is used to generate an MSBuild file which sets the "baseline" against which servicing updates are built.

Usage

Add --package-source {source} to the commands below if the packages of interest are not all hosted on NuGet.org.

Auto-update

  1. Run dotnet run --update in this project folder.
  2. Run dotnet run in this project.

Manual update

  1. Add to the Baseline.xml a list of package ID's and their latest released versions. The source of this information can typically be found in the build.xml file generated during ProdCon builds. See https://github.com/dotnet/versions/blob/master/build-info/dotnet/product/cli/release/2.1.6/build.xml for example. Update the version at the top of baseline.xml to match prior release (even if no packages changed in the prior release).
  2. Run dotnet run on this project.