How does Paket stack up against NuGet 3's project.json?

I notice that the Paket website/documentaton doesn’t make any mention of project.jsonProject.json Intro, which for NuGet’s purposes basically replaces package.config (in participating projects), with a few differences:

1. First and foremost, project.json does not bake in transitive dependencies; instead, these are resolved during package restore and written into a lockfile. (This should sound familiar.)
2. With project.json, NuGet does not modify project files during package “install” or restore (Except if project.json is the project file, like for ASP.NET 5, though reportedly NuGet is not actually used for ASP.NET 5?) Instead, the build system is supposed to pick up references from the lockfile, project.lock.json.
3. Install/Uninstall scripts are unsupported and ignored by design. (Also familiar.)
4. Content transforms are unsupported and ignored by design. (Presumably, whether or not this sounds familiar, Paket behaves the same way.)
5. Content files aren’t supported either, but in this case that’s not by design, it’s because they haven’t decided on a design for how this should work with project.json yet.

And that’s just the things that NuGet 3 doesn’t do anymore with project.json; there are also some new features, too.

It would be nice if you’d talk about the extent to which the advantages that you mention Paket has over packages.config also apply to project.json, whether any new advantages have cropped up, and (god forbid!) any advantages project.json might have at the moment.

Docs

The NuGet documentation includes these pages about project.json:

• Project.json Intro, or NuGet 3.0, .NET and project.json
• Project.json Format, or Project.json Usage
• Project.json Dependency, or Dependency Resolution in NuGet v3 / project.json

[edblackburn]

I have a C# .NET service. It uses paket, which I have been very, very happy with. I just googled paket CoreClr to investigate what is required to port my service to CoreClr and I have to say this thread is thoroughly depressing and aggressive in tone.

This thread is a massive, massive turn off to CoreClr and to .NET OSS / ecosystem in general. I really hope this is a temporary blip and not a mask slipping.

Frankly it’s embarrasing to read.

[forki]

no comment