No, it shouldn't. Those attributes should be transformed in a API as we done in NHV and NHE (Envers).
On Mon, Apr 25, 2011 at 5:20 PM, Matan Goldschmiedt <[email protected]>wrote: > 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. > > -- Fabio Maulo -- 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.
