I had problems with the 3.2 version. The access="field" and access="nosetter.camelcase" options, were raising am exception (don't remember the type) because I didn't have a public or protected set defined in my property.
But it's ok on version 3.1 On Jun 16, 8:33 am, Dwarrel <[email protected]> wrote: > Additional information, when changing to NH 3.0 then the same problem > does NOT occur (only changed the NH binaries, nothing else). Anyone > have any idea where I should be looking to get this resolved? So > project runs fine under .Net 3.5/4.0 with NH 2.1 and NH 3.0 but fails > compiling the hbm mapping files when moving to NH 3.1 -- You received this message because you are subscribed to the Google Groups "nhusers" 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/nhusers?hl=en.
