I've been asking for help on getting NDoc working with .NET 2.0 recently. I was lucky enough and Kevin Downs, the developer of NDoc sent me an alpha version of the next NDoc release that was good enough for generating Mvp.Xml API documentation. And that unexpected problem made me realize that NDoc reached such level that we all take this tool as granted, like part of .NET SDK or Visual Studio. While NDoc is actually a free open-source tool developed by enthusiasts! NDoc is so awesome and pervasive that Microsoft even doesn't bother to provide any alternative solutions. Java has javadoc and doclets, while Microsoft provides no tool for generating code documentation and indeed - why, don't you have NDoc? That's an interesting open-source phenomena.
But the cruel fact is that developing such a tool as NDoc for no money is a tough challenge. In .NET 2.0 Microsoft introduced huge amount of changes in both CLR/BCL and SDK docs NDoc has to adapt to, while NDoc project is very low on contributors and donations and Kevin Downs, the guy who writes NDoc has been recovering from some major health problems recently. That actually looked like NDoc project is dead, but it's not! Kevin is working on the next version and it already works as you can see here.
But my point is that we absolutely have to support NDoc project. NDoc saved Microsoft lots of money, while Kevin Downs even has no MSDN subscription and Visual Studio 2005! What a shame... Come on, Microsoft, show some love to NDoc and .NET community! And NDoc users, especially the ones using NDoc in commercial stuff - please support NDoc, donate some money to the project or directly to Kevin Downs.
Recent Comments