My company also uses NuGet exclusively. I use this because its easy and we have several company-specific packages which we host internally. NuGet handles all the dependencies and upgrades when I start a new project.
On a separate note: I'm taking a stab at a migrations feature for nhibernate which will likely make heavy use of the powershell/visual studio integration features exposed through the package manager console for NuGet. All that will clearly live in a separate assembly and likely a separate NuGet Package entirely. On Friday, August 1, 2014 11:36:44 AM UTC-4, Patrick Earl wrote: > > In another thread we were talking about the possibility of having > different types of releases, which made me wonder how people use NHibernate > nowdays. I know for our company we're totally on NuGet. So it would be > helpful to get a general feeling for how and why people do things certain > ways. > > 1. Do you use NuGet or manual DLL references (or other?) when you consume > NHibernate? > 2. Would you prefer to use a different method but you feel that something > is blocking you? > 3. For what reasons do you use that particular type of consumption? > -- --- You received this message because you are subscribed to the Google Groups "nhibernate-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to nhibernate-development+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
