We've strived to do just that: keep our domain free of NHibernate -- and any other foreign dependencies. Gunnar is right, though: it took some effort on our part to design our code this way, and we exert a little extra effort every day to keep that purity.
What does it gain us? We don't anticipate switching away from NHibernate any time soon. But it does mean that our domain is easily unit testable, regardless of how test-friendly the various third party frameworks we rely upon are. On Apr 25, 4:20 pm, Matan Goldschmiedt <[email protected]> wrote: > ... > 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.
