On Nov 24, 4:58 am, Paul Batum <[email protected]> wrote: > Interesting that the namespaces were the issue. I have no idea why this > would be the case. If I find the time, I might try to reproduce it, because > really this sounds like a bug to me.
Yes, it certainly seems like a bug. > In general most people (including myself) put their mapping classes and > conventions in a seperate assembly to the domain objects themselves. We do > this because we like to minimise the dependencies our domain assembly has. I understand. But I think there are also some advantages to allowing the mapping classes to be intermixed with the domain classes in the same namespace and file. For me, at least, it makes the code easier to understand. Also, now that I have basic functionality working, I expect to be making a lot of additions to my domain classes, and I'm problably more likely to remember to update the mapping class when it's in the same file. -Tom -- 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.
