31bd4d4b1d
- mostly duplicates #25217 - update `BaselineGenerator` to produce baselines useful in 6.0 (too) - update Baseline.Designer.props using new generator (matching 3.1.7 release) - always suppress references expressed only in `*.nuspec` files - needed even in servicing builds - restore warning and errors about removed references (new for 5.0) - adjust exclusions to handle `@(_ProjectReferenceByAssemblyName)` removal nit: do not generate empty `<ItemGroup />` elements * Correct `@(SuppressBaselineReference)` items - remove out-of-date `@(SuppressBaselineReference)` items - either 3.1.7 baselines we're using don't include reference or still using package - fix some comments and `Condition` attributes to make remainder easy to find - add missing `@(SuppressBaselineReference)` items |
||
|---|---|---|
| .. | ||
| BaselineGenerator.csproj | ||
| Program.cs | ||
| README.md | ||
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
Run dotnet run --update in this project folder. This will attempt to find the latest patch version of packages and
update the baseline file.
Manual update
- 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 file://vsufile/patches/sign/NET/CORE_BUILDS/3.0.X/3.0.0/preview5/3.0.100-preview5-011568/manifest.txt for example. Update the version at the top of baseline.xml to match prior release (even if no packages changed in the prior release).
- Run
dotnet runon this project.