I just pulled down the package via NuGet and noticed it's looking for NHibernate.Core v3.0.0.2001 (alpha 1) rather than 3.0.0.4000 (GA). Little glitch, but I've no idea how you're getting 2.x.
It *is *pulling the latest and greatest (v 1.1 build #694) down of FNH though... :) I don't see the .nuspec file in the repo, so assuming that's handled externally... :( --- David R. Longnecker blog: http://blog.drlongnecker.com twitter: dlongnecker On Thu, Dec 9, 2010 at 12:32 PM, Stacey Thornton < [email protected]> wrote: > I am going to seem like the retard here, but here goes. > > I downloaded Fluent NHibernate using Visual Studio's new NuGet > utility. Now, on the newest release, it claims to use "NHibernate Core > 3.XXX". However the NHibernate.dll it downloads shows a version of > 2.0.57xxx. > > Do I need to download NHibernate.dll 3.0+ and replace it in my > project, and it will work? or do I need to go through some hoops to > get Nhibernate 3.0 working for me? Can someone clarify this? > > On Dec 8, 5:21 am, Chris Magee <[email protected]> wrote: > > As long as Fluent NHibernate comes with NHibernate and its clearly noted > as > > being version NH 3.0 then I think that's enough. > > > > After downloading people, that are 'in the know', can replace the > NHibernate > > files with 3.X.Y if needed. > > > > Also, if it FNH defaults to Castle and removes the hurdle of when you > would > > choose linfu over castle, it makes things even easier to get started for > a > > newcomer. > > > > On Wed, Dec 8, 2010 at 11:12 AM, James Gregory <[email protected] > >wrote: > > > > > > > > > > > > > > > > > This is the first I've heard of anyone being confused by our version > > > numbers... > > > > > In my opinion this is an education issue, not something that should be > > > solved by altering our version numbers. We're an independent project > and our > > > release cycles are not tied to NH. > > > > > FNH 1.0 was compatible with 1.2 and 2.1 of NHibernate, 1.1 compatible > with > > > 2.1, 1.2 compatible with 2.1 and 3.0, and 2.0 will be compatible with > 3.0 > > > upwards; I don't see an easy way to indicate that in our version > numbers > > > without compromising our ability to version independently from > NHibernate > > > *and* maintain the intention of version numbers (major number changes > > > indicate breaking changes, minor indicates fixes but binary > compatibility). > > > > > It should be made clearer on the website when you're downloading FNH > what > > > version of NHibernate it's compatible with. > > > > > -- > > > You received this message because you are subscribed to the Google > Groups > > > "Fluent NHibernate" group. > > > To post to this group, send email to > [email protected]. > > > To unsubscribe from this group, send email to > > > [email protected]<fluent-nhibernate%[email protected]><fluent-nhibernate%2Bunsubscr > [email protected]> > > > . > > > For more options, visit this group at > > >http://groups.google.com/group/fluent-nhibernate?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Fluent NHibernate" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<fluent-nhibernate%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/fluent-nhibernate?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Fluent NHibernate" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/fluent-nhibernate?hl=en.
