Back in the old days...
...and when NuGet showed up, it made referencing a breeze.
But then, there was a new problem...
designed to work well with NuGet packages and also enables referencing files directly from Git repositories or any HTTP resource. It enables precise and predictable control over what packages the projects within your application reference.
How PAKET does it?
NuGet does not support SemVer-compatible (v2.0.0) prerelease numbers with dot notation, as in 1.0.1-build.23. You can use a form like 1.0.1-build23 but this is always considered a pre-release version.
in PreRelease Semantic Versioning
Plan to implement SemVer 2.0.0 support
1:
|
|
paket.dependencies (in solution root)
1: 2: 3: 4: 5: 6: 7: 8: 9: 10: 11: 12: 13: 14: 15: 16: 17: 18: 19: 20: |
|
paket.lock (generated from paket install)
1: 2: 3: 4: 5: 6: 7: 8: 9: |
|
paket.references (in each project folder)
1: 2: |
|
paket.template replaces the need for .nuspec file
1: 2: 3: 4: 5: 6: 7: 8: |
|
There's also a VS extension - Paket.VisualStudio