Welcome to mirror list, hosted at ThFree Co, Russian Federation.

github.com/mono/corefx.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDavis Goodin <dagood@microsoft.com>2016-10-11 21:29:37 +0300
committerDavis Goodin <dagood@microsoft.com>2016-10-12 19:48:35 +0300
commitdd2bfa20c59548676b02bf3d4bbd29bb9eba5f8b (patch)
treed388f1c4d13205c571e5aaa39ca4f264cc6396de /Documentation
parentbe874f8337f2b2e6ff72fa02ae337a00755e085e (diff)
Move NuGet dependency documentation to buildtools.
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/README.md2
-rw-r--r--Documentation/project-docs/project-nuget-dependencies.md35
2 files changed, 2 insertions, 35 deletions
diff --git a/Documentation/README.md b/Documentation/README.md
index 5fd2da332d..93eb6a2316 100644
--- a/Documentation/README.md
+++ b/Documentation/README.md
@@ -31,7 +31,7 @@ Project Docs
- [Strong Name Signing](project-docs/strong-name-signing.md)
- [Public Signing](project-docs/public-signing.md)
- [Repo Organization](project-docs/repo-organization.md)
-- [Project NuGet Dependencies](project-docs/project-nuget-dependencies.md)
+- [Project NuGet Dependencies](https://github.com/dotnet/buildtools/blob/master/Documentation/project-nuget-dependencies.md)
Coding Guidelines
=================
diff --git a/Documentation/project-docs/project-nuget-dependencies.md b/Documentation/project-docs/project-nuget-dependencies.md
index 844ed6bce4..a1e66402d2 100644
--- a/Documentation/project-docs/project-nuget-dependencies.md
+++ b/Documentation/project-docs/project-nuget-dependencies.md
@@ -1,37 +1,4 @@
Project NuGet Dependencies
==========================
-In CoreFX, dependencies on NuGet packages are stored in `project.json` files. `project.lock.json` files shouldn't be checked in to this repository.
-
-A dependency must be for a specific version of a package: no floating (\*) dependencies are used. This ensures builds are repeatable. CoreFX also has some rules for certain groups of packages that need to stay in sync: for example, all prerelease `System.*` packages must use the same prerelease version. These rules are validated during a build step, so a local build or continuous integration will catch any mistakes.
-
-As a historical note, `project.json` files in CoreFX previously had floating dependencies and `project.lock.json` files were checked in to lock the version for repeatable package restore. This was changed during pull request [#4894](https://github.com/dotnet/corefx/pull/4894).
-
-Dependency version validation
------------------------------
-
-The dependencies in each CoreFX project.json file are validated by a few rules in `dependencies.props` to ensure package versions across the repository stay in sync.
-
-Errors you can expect from failed dependency version validation are like the following:
-
- C:\git\corefx\Tools\VersionTools.targets(47,5): error : Dependency verification errors detected. To automatically fix based on dependency rules, run the msbuild target 'UpdateDependencies' [C:\git\corefx\build.proj]
- C:\git\corefx\Tools\VersionTools.targets(47,5): error : Dependencies invalid: In 'C:\git\corefx\src\Common\test-runtime\project.json', 'Microsoft.DotNet.BuildTools.TestSuite 1.0.0-prerelease-00704-04' must be '1.0.0-prerelease-00704-05' (Microsoft.DotNet.BuildTools.TestSuite) [C:\git\corefx\build.proj]
- C:\git\corefx\Tools\VersionTools.targets(47,5): error : Dependencies invalid: In 'C:\git\corefx\src\Common\tests\project.json', 'Microsoft.xunit.netcore.extensions 1.0.0-prerelease-00704-04' must be '1.0.0-prerelease-00704-05' (Microsoft.xunit.netcore.extensions) [C:\git\corefx\build.proj]
-
-To fix these, you can manually modify the `project.json` files mentioned or automatically fix them using the `UpdateDependencies` target described in the next section.
-
-Upgrading a package dependency
-------------------------------
-
-To update a package that isn't validated by a rule, simply change the project.json file.
-
-To update a package that is validated, follow these steps:
-
-1. Edit the versions repo commit hashes in `(CoreFx|CoreClr|External)CurrentRef` and `StaticDependency` versions in `dependencies.props` in the CoreFX root.
-2. Run the dependency update target in the repository root using this command:
-
- build-managed.cmd -- /t:UpdateDependencies
-
-3. Commit the automated updates in an independent commit, isolating them from other changes. This makes pull requests easier to review.
-
-The `UpdateDependencies` target looks through all dependencies, using the validation rules to update any invalid versions. On `/verbosity:Normal` or higher, it logs which files were changed.
+Documentation moved to [Project NuGet Dependencies](https://github.com/dotnet/buildtools/blob/master/Documentation/project-nuget-dependencies.md).