I realise this is a diversion, and not an answer to your question (although I think mookid has got that covered). You should really evaluate whether interfaces on your domain entities are actually providing anything of worth; it’s rare to find a situation where you actually need to do this. For example: How is relying … Read more
You can do something like: config.Mappings(m => { m.FluentMappings.ExportTo(“…file path here…”); m.HbmMappings.ExportTo(“…file path here…”); m.AutoMappings.ExportTo(“…file path here…”); { ); I don’t like it myself. If I find some better way (if such exists at all) I’ll update the answer. See http://blog.jagregory.com/2009/02/03/fluent-nhibernate-configuring-your-application/ Or if broken, see this instead https://github.com/jagregory/fluent-nhibernate/wiki/Database-configuration
Use collection interfaces instead of concrete collections, so NHibernate can inject it with its own collection implementation. In this case, use IList<int> instead of List<int>
Yes its a common problem, you are using the Column “EndDate” twice in your mapping definition (for both Company and PrimaryListing) and that is not allowed. One of them has to go, or have an additional EndDate column (one for each association) check this too nHibernate 2.0 – mapping a composite-id *and* many-to-one relationship causes … Read more
Just few hints, summarizing the most suitable standards I found out when working with NHibernate. 1) If there is a bi-directional reference in persitence (DB column), express it in C# code bi-directional as well. Other words, if a child has reference to parent, parent should have reference to child. public class Employee { … public … Read more
The inverse attribute must not be set to true … You use the inverse attribute to specify the ‘owner’ of the association. (An association can have only one owner, so one end has to be set to inverse, the other has to be set to ‘non inverse’). (Owner: inverse=false; Non-owner: inverse=true) In a one-to-many association, … Read more