About

I'm Mike Pope. I live in the Seattle area. I've been a technical writer and editor for over 30 years. I'm interested in software, language, music, movies, books, motorcycles, travel, and ... well, lots of stuff.

Read more ...

Blog Search


(Supports AND)

Google Ads

Feed

Subscribe to the RSS feed for this blog.

See this post for info on full versus truncated feeds.

Quote

A writer is somebody for whom writing is more difficult than it is for other people.

— Thomas Mann



Navigation





<September 2018>
SMTWTFS
2627282930311
2345678
9101112131415
16171819202122
23242526272829
30123456

Categories

  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  

Contact

Email me

Blog Statistics

Dates
First entry - 6/27/2003
Most recent entry - 9/21/2018

Totals
Posts - 2522
Comments - 2582
Hits - 2,081,219

Averages
Entries/day - 0.45
Comments/entry - 1.02
Hits/day - 374

Updated every 30 minutes. Last: 8:38 PM Pacific


  09:58 AM

The advantage of MSDN is that it consolidates all the developer documentation from Microsoft into a single library -- if it's a released developer product, you'll find (should find?) the docs for it there. Awesome.

The problem, however, is that MSDN can be ... hmmm, how to phrase this? ... a teeny bit unwieldy. Like, you know the docs you're looking for are there ... somewhere. And there are the occasional, you know, surprises. Did you know, for example, that all the ASP.NET 2.0 docs are not in www.msdn.com but actually in www.msdn2.com? This isn't so much a problem if you use, uh, certain search strategies to get at the docs, but let's face it, there are two libraries.

Welp, the MSDN folks are on the job. They posted a note recently on their home page advising readers about the existing of that whole 'nuther library. But more to the point, as they say, "In the coming months, the documentation hosted in both libraries will be consolidated into a single MSDN Library." Yay for that.

Managing a site as large as MSDN is quite a challenge, no doubt about it. We see it from both ends, as content providers to that site and, like everyone else, as users, so we're maybe even more eager than ordinary folks to see these improvements. :-)

PS Don't forget the MSDN Devwiki!

[categories]   ,

[2] |