Thanks for the link. Those bugs you mentioned should be entirely gone for 1.0 :)
On Sun, Aug 2, 2009 at 8:33 PM, Mikael Henriksson <[email protected]>wrote: > I just read a nice post from Alex James on the Entity Framework team. I > might be mistaken but I feel Fluent has a couple of bugs like this in the > configuration. When I try to use ColumnName on a property it completely > kills all other configuration. I found a workaround with manipulating the > order of things etc but Alex still has a good point. > http://blogs.msdn.com/alexj/archive/2009/08/01/another-c-trick-fluents-inheritance-and-extension-methods.aspx > > It is however using .NET 3.5. Not sure if you are on fluent so it might not > be for you. Good reading though. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
