Please Stop Reorganizing MSDN
Oh look, another Google search result that leads to an MSDN page that’s gone missing (the 2nd link on the results page, at least as of right now).
This happens far too often. There’s really no excuse for Microsoft not realizing by now that search engines index their site, and that users use search engines to find developer content far more than they use MSDN.
How about some search engine friendly URLs? For example, the link above is:
http://msdn2.microsoft.com/en-us/library/ms123402.aspx
Basically a meaningless string.
This is the page that should have been hit by that link (I think):
http://msdn2.microsoft.com/en-us/library/aa965225(VS.85).aspx
Another meaningless string.
How about something like…
http://msdn2.microsoft.com/en-us/win32/windows2000/system/memory/about/memory_performance_information
This has a version number in the URL. I can tell from the URL that it’s for a win32 function and that the documentation is relevant to Windows 2000. With a URL like this:
http://msdn2.microsoft.com/en-us/win32/vista/sdk/apiref/CreateProcess
This URL would even let me Google for Vista specific documentation, and tell if I found it because it’s right there in the URL.
Sun did a great job of this with Java. Even though the documentation is way old:
http://java.sun.com/j2se/1.3/docs/api/java/io/PrintStream.html
This link still works, and I can tell by reading it what I’m going to get.
February 4th, 2008 at 1:52 am
“This URL would even let me Google for Vista specific documentation”
Isn’t this what MS wants, to NOT empower Google? But force you to use their site, or Live.com
February 12th, 2008 at 4:44 am
How about this site? I am not sure if this site is reorganized or not, but the links to dottext articles on http://www.stevex.org are now redirected to blog.stevex.net. Example article http://www.stevex.org/dottext/articles/158.aspx ( as in my favourites)
Thanks
E Screw
February 19th, 2008 at 7:41 am
Guilty as charged. I tried to migrate all the content over when I switched from .Text to WordPress, but I neglected to set up forwards for the old URLs.
My only defense is that this is a personal blog and I don’t have any IT staff I can assign to making it work. But that’s a lame excuse.