Skip to content

Commit

Permalink
docs: use unlikely example versions in nuget package script (#7448)
Browse files Browse the repository at this point in the history
* Update doc

* Change last digit
  • Loading branch information
marcelwgn authored Sep 4, 2020
1 parent 5330759 commit 5ba992a
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions doc/building.md
Original file line number Diff line number Diff line change
Expand Up @@ -67,12 +67,12 @@ To update the version of a given package, use the following snippet

where:
- `$PackageName` is the name of the package, e.g. Microsoft.UI.Xaml
- `$OldVersionNumber` is the version number currently used, e.g. 2.5.0-prerelease.200609001
- `$NewVersionNumber` is the version number you want to migrate to, e.g. 2.4.200117003-prerelease
- `$OldVersionNumber` is the version number currently used, e.g. 2.4.0-prerelease.200506002
- `$NewVersionNumber` is the version number you want to migrate to, e.g. 2.5.0-prerelease.200812002

Example usage:

`git grep -z -l Microsoft.UI.Xaml | xargs -0 sed -i -e 's/2.5.0-prerelease.200609001/2.4.200117003-prerelease/g'`
`git grep -z -l Microsoft.UI.Xaml | xargs -0 sed -i -e 's/2.4.0-prerelease.200506002/2.5.0-prerelease.200812002/g'`

## Using .nupkg files instead of downloaded Nuget packages
If you want to use .nupkg files instead of the downloaded Nuget package, you can do this with the following steps:
Expand Down

0 comments on commit 5ba992a

Please sign in to comment.