2016-03-01 13:42 GMT+00:00 Steve Lyle <[email protected]>: > Thee are the full details of the exception: > Exception thrown: 'NHibernate.MappingException' in NHibernate.dll >
No, it isn't. All exceptions contains a Message, a StackTrace, and any number of InnerExceptions recursively. The InnerExceptions will most often let us know the exact problem. As I understand it you have access to the source code? Then I think the most productive use of time would be to fix the program to actually tell us what is wrong by logging the complete exception info in any number of ways, instead of doing guesswork. If you don't already have log4net active, it can as simple as: log4net.Config.BasicConfigurator.Configure() ASSUMING that your program runs with access to standard output. Otherwise see e.g. http://nhibernate.info/doc/nhibernate-reference/session-configuration.html#configuration-logging and log4net xml configuration. Or you could just catch and print the exception information yourself (DON'T forget the InnerExceptions). /Oskar -- 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 https://groups.google.com/group/nhusers. For more options, visit https://groups.google.com/d/optout.
