I needed to read this stuff right here. I have been developing happily on a custom-built CSLA-esque .NET platform for almost two years now, and I cannot begin t

I needed to read this stuff right here. I have been developing happily on a custom-built CSLA-esque .NET platform for almost two years now, and I cannot begin to explain to my OSS buddies what they should do to spin up a .NET project of their own. 1) It's not my job description or my problem domain at work. I'm paid to code the app, not spin up fresh instances of our app framework from scratch. We have maybe a dozen apps in various stages of progress, so it isn't like we need the whole team to know how to outfit a new instance of our app framework on a regular basis, but... 2) ...it's also amazing how difficult it is to even define what .NET is. It's hard to explain to colleagues what's going on behind the scenes when you can't always quite figure it out yourself. And I don't think of myself as simple-minded. I know that this stuff is a corollary to the inherent power/complexity factor that such a stack brings to the table, but MicroSoft could absolutely do a better job of providing clear and human-readable docs for people who are not already wizards.