I have asked myself, and I replayed "why don't you ask the nice people of the nhusers group what they think?" :)
Can anyone state what are the pros and cons of referencing NH in your domain? On Apr 25, 11:53 pm, Gunnar Liljas <[email protected]> wrote: > You must ask yourself, is it really a problem that NHibernate is referenced? > It may be, but in most cases it's not, and trying to work around it is just > hours of work sacrificed on the altar of dogmatism. > > /G > > 2011/4/25 Matan Goldschmiedt <[email protected]> > > > > > > > > > Hi, > > > I'd like to use NHibernate.Search via Nuget, I thought I'd start by > > attributing my entities using the NHibernate.Search.Attributes > > namespace. Problem is that the NH Search package depends on NH which > > means that my domain class library would reference NHibernate. > > > Up until now I managed to avoid that since I figured that my domain > > shouldn't be aware of NHibernate at all, is it a lost fight, or am I > > better adding a manual reference only to NHibernate Spatial? > > > -- > > You received this message because you are subscribed to the Google Groups > > "nhusers" 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/nhusers?hl=en. -- Make sure to check out my blog at www.codecovered.net -- You received this message because you are subscribed to the Google Groups "nhusers" 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/nhusers?hl=en.
