{"action":"created","issue":{"url":"https://api.github.com/repos/fsprojects/Paket/issues/1230","labels_url":"https://api.github.com/repos/fsprojects/Paket/issues/1230/labels{/name}","comments_url":"https://api.github.com/repos/fsprojects/Paket/issues/1230/comments","events_url":"https://api.github.com/repos/fsprojects/Paket/issues/1230/events","html_url":"https://github.com/fsprojects/Paket/issues/1230","id":117248722,"number":1230,"title":"How does Paket stack up against NuGet 3's project.json?","user":{"login":"SamB","id":13903,"avatar_url":"https://avatars.githubusercontent.com/u/13903?v=3","gravatar_id":"","url":"https://api.github.com/users/SamB","html_url":"https://github.com/SamB","followers_url":"https://api.github.com/users/SamB/followers","following_url":"https://api.github.com/users/SamB/following{/other_user}","gists_url":"https://api.github.com/users/SamB/gists{/gist_id}","starred_url":"https://api.github.com/users/SamB/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/SamB/subscriptions","organizations_url":"https://api.github.com/users/SamB/orgs","repos_url":"https://api.github.com/users/SamB/repos","events_url":"https://api.github.com/users/SamB/events{/privacy}","received_events_url":"https://api.github.com/users/SamB/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":32,"created_at":"2015-11-17T00:06:53Z","updated_at":"2015-11-18T13:07:47Z","closed_at":null,"body":"I notice that the Paket website/documentaton doesn't make any mention of `project.json`[Project.json Intro], which for NuGet's purposes basically replaces `package.config` (in participating projects), with a few differences:\r\n\r\n 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.)\r\n 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?)\r\n    Instead, the build system is supposed to pick up references from the lockfile, `project.lock.json`.\r\n 3. Install/Uninstall scripts are unsupported and ignored by design. (Also familiar.)\r\n 4. Content transforms are unsupported and ignored by design. (Presumably, whether or not this sounds familiar, Paket behaves the same way.)\r\n 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**.\r\n\r\nAnd that's just the things that NuGet 3 **doesn't** do anymore with `project.json`; there are also some new features, too.\r\n\r\nIt 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.\r\n\r\n## Docs\r\nThe NuGet documentation includes these pages about `project.json`:\r\n  * [Project.json Intro][], or *NuGet 3.0, .NET and project.json*\r\n  * [Project.json Format][], or *Project.json Usage*\r\n  * [Project.json Dependency][], or *Dependency Resolution in NuGet v3 / project.json*\r\n\r\n[Project.json Intro]: http://docs.nuget.org/consume/projectjson-intro\r\n[Project.json Format]: http://docs.nuget.org/consume/projectjson-format\r\n[Project.json Dependency]: http://docs.nuget.org/consume/projectjson-dependency"},"comment":{"url":"https://api.github.com/repos/fsprojects/Paket/issues/comments/157706743","html_url":"https://github.com/fsprojects/Paket/issues/1230#issuecomment-157706743","issue_url":"https://api.github.com/repos/fsprojects/Paket/issues/1230","id":157706743,"user":{"login":"robertmuehsig","id":756703,"avatar_url":"https://avatars.githubusercontent.com/u/756703?v=3","gravatar_id":"","url":"https://api.github.com/users/robertmuehsig","html_url":"https://github.com/robertmuehsig","followers_url":"https://api.github.com/users/robertmuehsig/followers","following_url":"https://api.github.com/users/robertmuehsig/following{/other_user}","gists_url":"https://api.github.com/users/robertmuehsig/gists{/gist_id}","starred_url":"https://api.github.com/users/robertmuehsig/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/robertmuehsig/subscriptions","organizations_url":"https://api.github.com/users/robertmuehsig/orgs","repos_url":"https://api.github.com/users/robertmuehsig/repos","events_url":"https://api.github.com/users/robertmuehsig/events{/privacy}","received_events_url":"https://api.github.com/users/robertmuehsig/received_events","type":"User","site_admin":false},"created_at":"2015-11-18T13:07:47Z","updated_at":"2015-11-18T13:07:47Z","body":"Maybe just keep in mind: project.json is not the only way of building libraries/dnx stuff. csproj stuff will stay, so keep calm."}}