I am using NServiceBus with NHibernate. My shop is primarily a VB.NET shop so projects are VB. I am using NServiceBus sagas which essentially maps a sagadata class to a database. I have updateSchema set so that the table is created/modified with changes to the sagadata.
I have one solution which uses NServciceBus.NHibernate 3.3.8 and NHibernate 3.3.1.4000 and only maps the properties of my sagadata class as columns in the related db table. This is what I expect. I have another solution which uses NServciceBus.NHibernate 5.0.0 and NHibernate 4.0.1.4000 and maps the properties of my sagadata class as columns in the related db as well as the backing fields for those columns. So if I have one property on my class (Name) I get two db columns (Name and _Name). If I create the same sagadata class in C# using the same NServciceBus.NHibernate 5.0.0 and NHibernate 4.0.1.4000, I do not get the extra columns for the backing field(_Name). Is this a change in NHibernate or potentially the way NServiceBus is creating the mapping? Is there a setting to prevent the backing fields from being mapped? I am not using mapping files. It looks like NServiceBus creates a mapping and compiles it 'on the fly'. Thanks in advance for any assistance. -- You received this message because you are subscribed to the Google Groups "nhusers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/nhusers. For more options, visit https://groups.google.com/d/optout.
