Paket: Package manager for .NET and Mono
fsprojects.github.io
Paket: Package manager for .NET and Mono
1–10 of 13 posts
Re: Paket: Package manager for .NET and Mono
#2The front page doesn't answer THE question, why would I use Paket instead of NuGet. Realistically in the .NET ecosystem, once Microsoft introduces a passable product (such as NuGet) the chances of any alternative to gain adoption are veeery swim.
Re: Paket: Package manager for .NET and Mono
#3The front page doesn't answer THE question, why would I use Paket instead of NuGet. Realistically in the .NET ecosystem, once Microsoft introduces a passable product (such as NuGet) the chances of any alternative to gain adoption are veeery swim.
See the faq : http://fsprojects.github.io/Paket/faq.html
Re: Paket: Package manager for .NET and Mono
#4If you want to add a killer feature to this, add better handling for non-referenced dependencies. By non-referenced I mean they don't exist as a project reference like a dll would. For example, if you're doing a web project and you depend on say angular. Angular isn't added as a project reference. Nuget/Visual Studio do all kinds of oddities to work around this. Unless there is already a solution to this that I don't know about (besides using two different package managers).
Re: Paket: Package manager for .NET and Mono
#5The front page doesn't answer THE question, why would I use Paket instead of NuGet. Realistically in the .NET ecosystem, once Microsoft introduces a passable product (such as NuGet) the chances of any alternative to gain adoption are veeery swim.
See the faq : http://fsprojects.github.io/Paket/faq.html
Sure, in these long, cold winter nights what else is one to do...
If you have any analytics, compare the number of visitors to the main and to faq pages ...
Re: Paket: Package manager for .NET and Mono
#6I hate to be a Negative Nancy, but wouldn't it be easier to Just Fix NuGet? I don't think that any of the problems being solved here are fundamentally incompatible with being fixed in NuGet (though I could be wrong).
Re: Paket: Package manager for .NET and Mono
#7The front page doesn't answer THE question, why would I use Paket instead of NuGet. Realistically in the .NET ecosystem, once Microsoft introduces a passable product (such as NuGet) the chances of any alternative to gain adoption are veeery swim.
See the faq : http://fsprojects.github.io/Paket/faq.html
Why not address these issues directly in nuget rather than building another layer on top?
Re: Paket: Package manager for .NET and Mono
#8How does this differ from asp.vnext's kpm?
Re: Paket: Package manager for .NET and Mono
#9One thing I wish NuGet would do - let me download packages directly from Github, like Bower and Grunt do. I do use Bower and Grunt with ASP.NET but usually mixed with some NuGet packages. It would be nice to have one system for all.
Re: Paket: Package manager for .NET and Mono
#10One thing I wish NuGet would do - let me download packages directly from Github, like Bower and Grunt do. I do use Bower and Grunt with ASP.NET but usually mixed with some NuGet packages. It would be nice to have one system for all.
Visual studio just added support for Bower and Grunt[1]. I'm thinking that might help us separate the ecosystem again -- nuget for server-side, bower/grunt for client-side.
[1] http://www.hanselman.com/blog/IntroducingGulpGruntBowerAndNp...