<?xml-stylesheet type="text/css" href="http://www.mikepope.com/blog/rss/rssComments.css" ?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" >
  <channel>
    <title>More on MSDN - Comments</title>
    <link>http://www.mikepope.com/blog/AddComment.aspx?blogid=2015</link>
    <description />
    <copyright>Copyright 2003-2007 Mike Pope </copyright>
    <dc:language>en-US</dc:language>
    <pubDate>Tue, 12 Aug 2008 08:49:07 GMT</pubDate>
    <generator>mike pope's Web log</generator>
    <webMaster>mike@mikepope.com</webMaster>
        <item>
      <title>Comment by Dylan on "More on MSDN"</title>
      <link>http://www.dylanwolf.com/</link>
      <guid>http://www.mikepope.com/blog/AddComment.aspx?blogid=2015#2015_2104</guid>
      <description>(I should probably preface this post by saying I do a lot of SharePoint development right now, so my experience may be different.)&lt;br /&gt;&lt;br /&gt;I actually like MSDN's documentation on most things. Granted, I usually get there by typing in a class or method name through Google, but it's usually pretty complete. Its big weakness is that it doesn't always show useful examples for the more obscure SharePoint features, but it at least provides a basis that I can refer to when I look up the actual usage on the web on in books. I've only had to dig out .NET Reflector and figure out just what a particular method is doing once or twice.&lt;br /&gt;&lt;br /&gt;I'm not sure it would be as good if it was a wiki; the .NET classes might be well-documented, but somehow I doubt the less-used (like some SharePoint stuff and the class in the example) would get the same treatment. Now, if MSDN documentation included the official MS documentation &lt;em&gt;plus&lt;/em&gt; a wiki page (rather than just a comments thread), that might be more useful.</description>
      <dc:creator>Dylan</dc:creator>
      <pubDate>Tue, 12 Aug 2008 10:58:40 GMT</pubDate>
    </item>
    <item>
      <title>Comment by Jonathan Allen on "More on MSDN"</title>
      <link>http://www.infoq.com</link>
      <guid>http://www.mikepope.com/blog/AddComment.aspx?blogid=2015#2015_2105</guid>
      <description>I gave up on the wiki when I realized that with every version all my comments are lost. (Well not lost, but very well hidden from anyone looking at pages for the newer version.)</description>
      <dc:creator>Jonathan Allen</dc:creator>
      <pubDate>Tue, 12 Aug 2008 11:15:59 GMT</pubDate>
    </item>
    <item>
      <title>Comment by mike on "More on MSDN"</title>
      <link>http://www.mikepope.com/blog/</link>
      <guid>http://www.mikepope.com/blog/AddComment.aspx?blogid=2015#2015_2106</guid>
      <description>@Jonathan -- I'll forward your comment to the wiki team. Seems like a legitimate, um, disincentive to using the wiki, I agree.</description>
      <dc:creator>mike</dc:creator>
      <pubDate>Tue, 12 Aug 2008 12:13:23 GMT</pubDate>
    </item>
    <item>
      <title>Comment by Jonathan Allen on "More on MSDN"</title>
      <link>http://www.infoq.com</link>
      <guid>http://www.mikepope.com/blog/AddComment.aspx?blogid=2015#2015_2107</guid>
      <description>Thanks, that really means a lot to me.&lt;br /&gt;&lt;br /&gt;I actually complained about it months ago, but going through the &quot;proper channels&quot; often means the people who care never hear the message.</description>
      <dc:creator>Jonathan Allen</dc:creator>
      <pubDate>Tue, 12 Aug 2008 13:09:05 GMT</pubDate>
    </item>
    <item>
      <title>Comment by Larry W Jordan Jr on "More on MSDN"</title>
      <link>http://blogs.msdn.com/innovation/</link>
      <guid>http://www.mikepope.com/blog/AddComment.aspx?blogid=2015#2015_2108</guid>
      <description>Thanks for the comments and debate on MSDN. I want to address a number of things in the post and clear some things up.&lt;br /&gt;&lt;br /&gt;The Community Content that we enable for each article is more than offering just comments on the topic. It is designed to support embellishing the content with examples, pointers and other additions to improve the topic. We also enabled tagging through the same mechanism for discovery.  &lt;br /&gt;&lt;br /&gt;We have had a lot of prolific additions to the content from folks who add PowerShell and other scripts…&lt;br /&gt;&lt;a target='_blank' href='http://msdn.microsoft.com/en-us/library/system.decimal.aspx#CommunityContent'&gt;http://msdn.microsoft.com/en-us/library/system.decimal.aspx#CommunityContent&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;And helpers&lt;br /&gt;&lt;a target='_blank' href='http://msdn.microsoft.com/en-us/library/aa337083(SQL.90).aspx#CommunityContent'&gt;http://msdn.microsoft.com/en-us/library/aa337083(SQL.90).aspx#CommunityContent&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Just as an example of the diversity of the contributions. We allow edits and modifications, etc.&lt;br /&gt;&lt;br /&gt;Specific to the versioning issue is a little more complicated matrix and it is on our radar to enable it &amp;lt;g/&amp;gt; Versioning across releases for Community Content adds an additional dimension of features to the UX itself and also needs to provide for a way to bring forward Community Content and Annotations based on the user selecting that it applies to a specific version or all past/future versions. I am working with this currently with my team.&lt;br /&gt;&lt;br /&gt;Finally, the issue of being able to contribute articles to the library versus annotations only to existing topics is being developed right now. We are targeting the broader announcement of the features of this capability for the PDC and look forward to sharing more information on my blog as we get closer to the pilots.&lt;br /&gt;&lt;br /&gt;&lt;a target='_blank' href='http://blogs.msdn.com/innovation/'&gt;http://blogs.msdn.com/innovation/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Larry W Jordan Jr - Product Unit Manager for the MSDN and TechNet Infrastructure and Services Team</description>
      <dc:creator>Larry W Jordan Jr</dc:creator>
      <pubDate>Wed, 13 Aug 2008 09:31:54 GMT</pubDate>
    </item>
    <item>
      <title>Comment by Chris Slemp on "More on MSDN"</title>
      <link>http://blogs.msdn.com/cslemp</link>
      <guid>http://www.mikepope.com/blog/AddComment.aspx?blogid=2015#2015_2109</guid>
      <description>I'd like to chime in on the discoverability comments... I've just completed an informal evaluation with a dozen customers, who we asked to use MSDN Search for 12 days. We had only minor complaints and several converts as a result. In my experience talking to literally hundreds of customers about our search, those that are griping about it haven't tried it lately, or haven't noticed the new features we've added in recent months. Have a read of my post describing our recent study here. &lt;a target='_blank' href='http://blogs.msdn.com/cslemp/archive/2008/08/12/12-technical-pros-evaluate-msdn-technet-search-for-12-days.aspx'&gt;http://blogs.msdn.com/cslemp/archive/2008/08/12/12-technical-pros-evaluate-msdn-technet-search-for-12-days.aspx&lt;/a&gt; </description>
      <dc:creator>Chris Slemp</dc:creator>
      <pubDate>Thu, 14 Aug 2008 21:06:17 GMT</pubDate>
    </item>

  </channel>
</rss>

