Thanks for the opinions. Yes, I'd thought of both of those options already. However my extension is to NHibernate behaviour, i.e. If this configuration setting = true then extend NHibernate so that it does not perform implicit dirty checking (as per the NH Add Ins process Fabio wrote) otherwise use the default behaviour of NH (something that would be nice in NH 3.0.0 tbh).
When you consider therefore that this is an explicit change to how NH works in our application framework, it makes sense to include that in the configuration of NH as that is where a developer will look. I could create a custom configuration block but, until now, we haven't needed one and IMO actually makes things *more* complicated, not less, to do so. So, thanks for the feedback but I guess the answer is actually "no, you can't" but it seems a shame that you cannot override the appriopriate methods in Configuration to do this. -- 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.
