Skip to content

Commit

Permalink
Update project reference protocol doc
Browse files Browse the repository at this point in the history
  • Loading branch information
dsplaisted committed Nov 18, 2021
1 parent a169ace commit 32755de
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion documentation/ProjectReference-Protocol.md
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,7 @@ If implementing a project with an “outer” (determine what properties to pass
* It returns an item with the following metadata:
* `TargetFrameworks` indicating what TargetFrameworks are available in the project
* `TargetFrameworkMonikers` and `TargetPlatformMonikers` indicating what framework / platform the `TargetFrameworks` map to. This is to support implicitly setting the target platform version (for example inferring that `net5.0-windows` means the same as `net5.0-windows7.0`) as well as treating the `TargetFramework` values [as aliases](https://github.com/NuGet/Home/issues/5154)
* Boolean metadata for `HasSingleTargetFramework` and `IsRidAgnostic`.
* Boolean metadata for `HasSingleTargetFramework` and `AcceptsRuntimeIdentifier`.
* `Platforms` indicating what platforms are available for the project to build as, and boolean metadata `IsVcxOrNativeProj` (used for [SetPlatform Negotiation](#setplatform-negotiation))
* The `GetReferenceNearestTargetFrameworkTask` (provided by NuGet) is responsible for selecting the best matching `TargetFramework` of the referenced project
* This target is _optional_. If not present, the reference will be built with no additional properties.
Expand Down

0 comments on commit 32755de

Please sign in to comment.