We’re not using the call-stack based approach for the reasons you state.

With respect to performance 1.2 should be on par with 1.1 – There have been few, if any, changes to performance critical sections of the code. Additionally, the additional lazy loading features in 1.2 offer more potential performance improvements to the application developer.

Cheers,

Andrew.

I’m interested in the implementation that you’ve used to support the Tidier Property Setters. I’ve used another ORM (XPO) that supported the same short-hand syntax but they have recommended against using this approach as they ran into problems with their algorithm that analysed the call stack to find the property being used “because the .NET 2 compiler employs improved mechanisms of inlining method calls.” See http://community.devexpress.com/blogs/xpo/archive/2007/02/01/701.aspx for the details.

Are you aware of such issues and will your implementation avoid these kinds of pitfalls? Also is the 1.2 version just as performant as the 1.1 version?

Thanks
Carel