Ramblings from the Creator of WilsonDotNet.com
Nice! Congrats on the new release.
Ah, you made my day by fixing the exception handling! That was a big pain when debuging. :)
I'm new to your mapper... "Better Exception Handling, No longer Catching and Eating Exceptions" The fact that you were ever eating exceptions makes me a little scared to use this in my applications... and to fix it in v3.1 makes me even more worried. I would put that into "bug fixes" rather than "improvements".
AJ: Its hard to disagree with that in general, but there was one exceptional case. Basically, people often have object A related 1-n to object B and object B related n-1 to object A. For the default lazy-loading scenario this works fine, but when someone turns off lazy-loading then this was a scenario where an infinite set of relations could become a huge problem! Since my mapper does not require a base class, its not easy to deal with some situations like that, so I found a way to cause an exception -- and I ate it on purpose since that was my intent. Unfortunately there was opportunity for other exceptions to get ate in the process. Anyhow, this is now fixed (not an easy thing to do), but while it was less than idea before, it was there for a reason and didn't exactly make the mapper unstable as you are maybe suspecting -- it was very stable.