From c1b4605b7b490716f6b908cbfd269d5338ede8c8 Mon Sep 17 00:00:00 2001 From: Excelan Date: Sun, 11 Nov 2018 16:31:32 +0200 Subject: [PATCH] Fixed typo --- .../Package-References-in-Project-Files.md | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/docs/consume-packages/Package-References-in-Project-Files.md b/docs/consume-packages/Package-References-in-Project-Files.md index c7ba01e47..258063b6b 100644 --- a/docs/consume-packages/Package-References-in-Project-Files.md +++ b/docs/consume-packages/Package-References-in-Project-Files.md @@ -9,13 +9,7 @@ ms.topic: conceptual # Package references (PackageReference) in project files -Package references, using the `PackageReference` node, manage NuGet dependencies directly within project files (as opposed to a separate `packages.config` file). Using PackageReference, as it's called, doesn't affect other aspects of NuGet; for example, settings in `NuGet. - - - - - -fig` files (including package sources) are still applied as explained in [Configuring NuGet Behavior](configuring-nuget-behavior.md). +Package references, using the `PackageReference` node, manage NuGet dependencies directly within project files (as opposed to a separate `packages.config` file). Using PackageReference, as it's called, doesn't affect other aspects of NuGet; for example, settings in `NuGet.Config` files (including package sources) are still applied as explained in [Configuring NuGet Behavior](configuring-nuget-behavior.md). With PackageReference, you can also use MSBuild conditions to choose package references per target framework, configuration, platform, or other groupings. It also allows for fine-grained control over dependencies and content flow. (See For more details [NuGet pack and restore as MSBuild targets](../reference/msbuild-targets.md).)