Thee are the full details of the exception: Exception thrown: 'NHibernate.MappingException' in NHibernate.dll The program '[3472] NHibernateTutorialX.vshost.exe' has exited with code -1073741819 (0xc0000005) 'Access violation'. Also. I putting this post out on the line as documentation. Once you know what I've posted then it is easy enough to of a construct to work within. The problem is there is regrettable lack in the maintenance of nHibernate and it's documentation therefore it is an extreme challenge to adopt. And, post adoption, it strangleholds most organizations into "if it isn't broken don't you dare fix it" mentality.
On Monday, February 29, 2016 at 4:28:35 PM UTC-5, Steve Lyle wrote: > > Is this a bug? > I can't imagine any purpose for this behavior. > Can you point me to sufficiently explicit documentation that enplanes this > requirement? > > I have a project in studio. > The assembly name in the project properties is XYZ. > Whatever value this project attribute has the executable will be named the > same. > The value of this attribute does not have to be the same as the project's > name. > > The value of this attribute has to be the same as the value of: > 1) the mapping<tag> assembly<attribute> in (app.config, web.config, > hibernate.cfg.xml, ... take your choice.) > 2) AND (as you might expect) the hibernate-mapping<tag> > assembly<attribute>. > If these three ducks are not in a row as compiled then at run time then > "an handled exception occured". > > Now here is the kicker: > If, in a application, I rename the executable file, and change noting else > ... it breaks the nHibernate configuration. > If I rename the file back ... it fixes nHibernate configuration. > If I rename the executable and reconfigure the nHibernate XML ... the > application remains broken. > This is true if I run the application in VStudio or from command line with > VStudio closed. > > Remember the project property is only applicable in when I run the > application in VStudio. > BUT the behavior even if I play with this in the command line. > So the application is getting compiled into the executable the value of > the Project property AND nHibernate somehow rely on this compiled value > when it the application executes nHibernate because the > confuration.configure() executes the executable that executed nHibernate. > > BTW ... and here is hte really stupid part ... the failure is: > Exception thrown: 'NHibernate.MappingException' in NHibernate.dll > The program '[3472] NHibernateTutorialX.vshost.exe' has exited with code > -1073741819 (0xc0000005) 'Access violation'. > *WTF? * > > Your Ideas? Bug? > > > > > -- 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 nhusers+unsubscr...@googlegroups.com. To post to this group, send email to nhusers@googlegroups.com. Visit this group at https://groups.google.com/group/nhusers. For more options, visit https://groups.google.com/d/optout.
