huahaofeng
/
aspnetcore
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
aspnetcore/eng/tools/BaselineGenerator
History
Nate McMaster 41ce223c1c
Replace Internal.AspNetCore.Sdk with Microsoft.DotNet.Arcade.Sdk (#10674) 
* Update build.cmd to install .NET Core into $repoRoot/.dotnet instead of $repoRoot/.dotnet/x64
* Move restore sources from build/sources.props into eng/Versions.props (following arcade conventions)
* Remove usages of RuntimeFrameworkVersion in tests and build
* Update Blazor VSIX to use Arcade VSIX tools
* Rename Common.Tests to IIS.Common.TestLib and make it a test asset
* Remove custom versions props for ANCM installer code
* Remove duplicate references to xunit and remove usages of IsTestProject
* Remove duplicate references to Internal.AspNetCore.Analyzers
* Import Arcade.Sdk props and targets and remove custom versioning props
* Remove references to Internal.AspNetCore.Sdk
* Rename PackageLicenseType => PackageLicenseExpression
* Remove dependency on tasks in Internal.AspNetCore.Sdk, add ref to Internal.AspNetCore.BuildTasks as a temporary workaround
* Use Arcade's nuspec support
* Rename SignalR.Client.FunctionalTests to SignalR.Client.FunctionalTestApp
* Fixes for changes to property evaluation order
* Update BaseLineGenerator to netcoreapp3.0
* React to changes in evaluation order in RPM files and quirks in using <Exec> instead of <Run>
* Update Microsoft.Extensions.ApiDescription.Server to react to changes in Arcade packaging
* Workaround aspnet/AspNetCore#11009
 		2019-06-07 17:19:41 -07:00
..
BaselineGenerator.csproj Replace Internal.AspNetCore.Sdk with Microsoft.DotNet.Arcade.Sdk (#10674) 2019-06-07 17:19:41 -07:00
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

  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 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).
  2. Run dotnet run on this project.