Mar6
My Issues With Microsoft’s MSDN
- posted by: Ryan
- no comments
- post a comment
Yesterday I needed to reference the syntax for getting the string representation of a .NET DateTime object in a specific format. Google and MSDN (Microsoft Developer Network)’s own search brought me to this page. This page and the next few I found on the topic where less then helpful. These pages highlight two issues I have with MSDN’s documentation.
First, while MSDN’s documentation is excellent and thorough as an encyclopedic work, it fails as a quick reference. It’s often hard to find the nugget of info you need, especially if you are in a hurry. For example – on the page I reference above – instead of providing some simple examples demonstrating the concept – you need to scroll through about 80 lines of code. I’m happy to do that, but I’d appreciate some quick examples at the top for when I’m in a hurry. It would make my life a little easier.
Second, the default .NET version that MSDN shows documentation for is the latest .NET version, 3.5. I respect Microsoft’s desire to push and promote the latest version of its framework, but not taking developers to the most common – and the version of documentation they are most likely looking for – does not seem the best strategy, or even a good strategy. It’s annoying because it requires extra clicks and effort to get to the version of info you are actually looking for. It’s double annoying because .NET 3.5 is still a new technology and not yet widely adopted; 2.0 seems to the de facto standard.
I think that MSDN will get better in time, especially with the feedback system that was implemented sometime ago. Microsoft seems more open to input these days and I hope the .NET community can encourage MSDN to evolve.


Looks like today at the 
Google’s blog hosted a pretty 








