Handling 3rd party packages. NuGet vs Paket

[persn]

Currently we're using NuGet to manage 3rd party dependencies into our C# modules. However there is a new hip and happening tool on the sphere that is called Paket which is supposed to be more simple, flexible and all that.

I don't have the time to research it any time soon but this issue will be left as a reminder for anyone who wants to dive in and investigate new technology we can use.

[persn]

I stayed up late to take a look at Paket, and I have to say it's a pretty nifty little tool.

What I like about it:

1. It's super simple, efficient and works flawlessly.
2. All packets are handled globally by repo, instead of individually by each project module. This means that the if the repo has multiple projects that references the same NuGet package, they will always use the same version of the software. This also means that we don't have to micro manage NuGet updates and hope every module will work with the update.
3. It's not just for NuGet, making it much more flexible. It can also download GitHub projects, files by HTTP, and even files on Gist.

I think this will make our lives much easier in the long run so I think we should just implement Paket into Hero6.

[persn]

Paket is implemented into the private prototype. It'll be included when the source code is uploaded.