CSLA 4 is now available through NuGet, the package installer for .NET products.
This is thanks to Johann Hough (jaans) - thank you Johann!
The following packages are available:
I noticed that there was a training session on NuGet amonst the free training from PluralSight for ASP.NET MVC3.
The particular NuGet session isn't focuessed on ASP.NET MVC 3 per se, but rather generically and thus to my mind, offers an excellent opportunity to get up to speed with NuGet. It aims to give fundamentals about learning how to use and leverage NuGet (esepecially with CSLA *hint* *hint* *nudge* *nudge*). The CSLA 4.1 NuGet Packages are already on the official gallery (have been for some time) and are aware of dependencies on other CSLA packages (e.g. Core).
It works a treat and I'm certain that for many NuGet will solve some long standing frustrations with package management and versioning. Usefull to point out that NuGet can be used with your own in-house "package gallery" - grat if you would like to standardise what's available to your teams. There's plenty information about it out there and I would highly recommend you watch the free plural sight training while it's still available.
I believe it's only free until 18 Marh 2011 - so hurry!!
Link to the free ASP.NET MVC 3 Training : http://www.asp.net/mvc/pluralsight
Direct link to the NuGet traning : http://www.pluralsight-training.net/microsoft/players/PSODPlayer.aspx?author=scott-allen&name=mvc3-nuget&mode=live&clip=0&course=aspdotnet-mvc3
Could you please include the documentation XML files in all the packages? Currently it only exists in the CSLA Core package with the "sl3-wp" project type.
Thanks jaans! Releasing these through Nuget as it makes my life allot easier working on varied machines.
Thanks Nick for the suggestion.
I see Rocky has logged the request for us.
We have a new way of building our NuGet packages with CSLA 4.2 and we explicitly now include the .XML and resource satellite assemblies - this work has been completed some time back, but I'll double check it.
It may be that the .xml files is not being placed in the bin drop folder for NuGet to pick up.
Great, I really miss the summaries for Intellisense when I'm coding.
FYI: for the PDBs, you may want to check out this article from David Ebbo http://blog.davidebbo.com/2011/04/easy-way-to-publish-nuget-packages-with.html
Copyright (c) Marimer LLC