GitXplorerGitXplorer
d

maket

public
42 stars
3 forks
2 issues

Commits

List of commits on branch master.
Verified
abba5c3ebe0bb9c452d75938db0b6e580c1c5855

Update README.md

ddavkean committed 5 years ago
Verified
15aa02627b2c876e0dd133fdcc70492696618aff

Update README.md

ddavkean committed 7 years ago
Verified
07db7729ff2fe97c96f015d3962bd71595635a60

Clarified

ddavkean committed 7 years ago
Verified
59fb1395fbef3280dc93444417195451e51d89cf

Updated samples

ddavkean committed 7 years ago
Verified
6b96e187e161e5f8c2ad1e372ab89ccac6c6f836

Initial readme

ddavkean committed 7 years ago
Unverified
818db46ffa31ea88575424c875bb25b996887be4

Initial commit.

ddavkean committed 7 years ago

README

The README file for this repository.

maket

This repository shows an example of controlling NuGet package versions at the repository level, while at the same time ensuring that projects only opt into packages that they want.

Packages are opt'd in as normal via a <PackageReference> in each project just without a version:

  <ItemGroup>
    <PackageReference Include="Newtonsoft.Json" />
  </ItemGroup>

Package versions across the repository (or solution) are then controlled by the <PackageReference Update=""/> constructs (new for MSBuild 15) inside of Directory.Build.targets:

  <ItemGroup>
    <PackageReference Update="Newtonsoft.Json" Version="10.0.1"/>
    <PackageReference Update="EntityFramework" Version="6.1.2"/>  
  </ItemGroup>

This says, "if a project has Newtonsoft.Json or EntityFramework in their list of packages, update them to this version".

You can read more information about Directory.Build.props/Directory.Build.targets in Customize your build.