I feel your pain, because I was there two months ago. After I got into it though, diving into the source code, which I do mostly by tracing through it in the debugger, really wasn't hard and I found to be a very effective way to learn. I am however developing in C# so there might be an advantage there.

You can get Louis Roeder's Reflector (http://www.aisto.com/roeder/dotnet/) and load the MM.Net dll's into in and decompile the methods to see a VB approximation of the source code in MM.Net. That may help as well.

IMO, I don't think you made a mistake with MM.Net. Even if it's not 100% right now long term it was the right call.

>I don't expect or want to chase around the source code. For one thing I'm not using C# and am having trouble following it. For another if I wanted to know every detail I would have just written everything myself. If thats the solution to this problem than I've made a huge mistake in using the framework. I talked a client into the idea of using a framework. That company paid for it so that they could develop in it after I've moved on. If I have to reverse that decision I’ll lose the client and be lucky if I don’t get sued!