Man, this thing is dense.
I was able to get a very snazzy sample up and running with Castle.Windsor in under an hour, but it'll take quite a bit of time to get the same demo working with ObjectBuilder. Admittedly, the PAG team states that it wasn't designed for prime time (yet), but what I would be interested in is seeing Microsoft integrate some open source projects into their own OSS projects. Why reinvent the wheel?
From my brief review of ObjectBuilder, it seems like it requires way too much work to use at this point. It uses a mixture of configuration and compile time attributes to make the magic happen. Why not have the option of doing it all in the configuration file? It seems to require a lot of custom code to utilize ObjectBuilder whereas the Windsor container requires almost no custom code for wiring; it can be done in one line of code.
On a tangent, I found out that contrary to lack of activity on NDoc, a 2.0 version is in the works and has been mostly underground due to the fact that it's, from what I gather, a complete rewrite. I tracked down a post by Kevin Downs, the project leader for NDoc over at Fabrice Marguerie's blog dated 2/23/2006:
Originally I had planned to do a simple upgrade of NDoc 1.3, but this
proved almost impossible. NDoc2 is, to all intents and purposes, a
complete rewrite (a huge undertaking) and has taken far longer than I
originally anticipated due to illness. I was forced to 'go dark' on
this development because I was getting some fairly offensive emails
*demanding* a new release, and I could not give a firm time-line due to
the above mentioned illness.
So if you're interested in being a tester, track down Kevin and get on the mailing list.