Skip to content

Commit 44a0dba

Browse files
jjanuszkiewiczzivkan
authored andcommitted
fix formatting in Package-References-in-Project-Files.md (NuGet#1182)
Fix formatting/typo in the first paragraph.
1 parent 75ad83a commit 44a0dba

File tree

1 file changed

+1
-7
lines changed

1 file changed

+1
-7
lines changed

docs/consume-packages/Package-References-in-Project-Files.md

Lines changed: 1 addition & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -9,13 +9,7 @@ ms.topic: conceptual
99

1010
# Package references (PackageReference) in project files
1111

12-
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.
13-
14-
15-
16-
17-
18-
fig` files (including package sources) are still applied as explained in [Configuring NuGet Behavior](configuring-nuget-behavior.md).
12+
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).
1913

2014
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).)
2115

0 commit comments

Comments
 (0)