Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This completes the work started by @forki in #276.
As discussed in the other thread, this does not change anything about how Deedle is consumed (we still publish a NuGet package, with the same things as before).
However, this changes how we reference other packages. Rather than using NuGet directly, this uses it through Paket, but under the cover, it still gets the packages from NuGet.
The nice things about Paket (and why I would like to use it for Deedle are):
fsproj
files - when we update a reference, we just runpaket install
and that will update thefsproj
files (so no more messing with<HintPath>
elements by hand)packages
do not contain version number in the folder name (this means we do not have to modify*.fsx
files when we update a version of a referenced package).