<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Getting MSDN help urls for .NET BCL types and Members</title><link>http://blogs.msdn.com/monad/archive/2005/12/28/507903.aspx</link><description>Often when playing with .Net objects in Monad, I need to use MSDN class library reference to learn how to use a particular type and its members. Now, I have my bookmarks and favorite search engine but I always thought it would be cool if get-member cmdlet</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Getting MSDN help urls for .NET BCL types and Members</title><link>http://blogs.msdn.com/monad/archive/2005/12/28/507903.aspx#508341</link><pubDate>Sat, 31 Dec 2005 05:24:35 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:508341</guid><dc:creator>DontBotherMeWithSpam</dc:creator><description>I have thought creating a similar function which will retrieve MSDN2 link(but not through modifying command member definition).  But will MSDN2 always have the same naming scheme later on?  That was what I have been afraid of... but not that it matters much :)</description></item><item><title>re: Getting MSDN help urls for .NET BCL types and Members</title><link>http://blogs.msdn.com/monad/archive/2005/12/28/507903.aspx#508347</link><pubDate>Sat, 31 Dec 2005 07:06:10 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:508347</guid><dc:creator>Monad Team</dc:creator><description>You could also register a ScriptMethod MSDN in a TYPES.MSHXML file to show the documentation in a viewer:&lt;br&gt;&lt;br&gt;    &amp;lt;Type&amp;gt;&lt;br&gt;        &amp;lt;Name&amp;gt;System.Object&amp;lt;/Name&amp;gt;&lt;br&gt;        &amp;lt;Members&amp;gt;&lt;br&gt;            &amp;lt;ScriptMethod&amp;gt;&lt;br&gt;                &amp;lt;Name&amp;gt;MSDN&amp;lt;/Name&amp;gt;&lt;br&gt;                &amp;lt;Script&amp;gt;&lt;br&gt;if ($global:MSDNViewer -eq $null)&lt;br&gt;{   $global:MSDNViewer = new-object -ComObject InternetExplorer.Application&lt;br&gt;}&lt;br&gt;$global:MSDNViewer.Navigate2(&amp;quot;&lt;a rel="nofollow" target="_new" href="http://msdn2.microsoft.com/library/&amp;quot;"&gt;http://msdn2.microsoft.com/library/&amp;quot;&lt;/a&gt; + $this.GetType().FullName + &amp;quot;.ASPX&amp;quot;)&lt;br&gt;$global:MSDNViewer.Visible = $TRUE&lt;br&gt;		&amp;lt;/Script&amp;gt;&lt;br&gt;            &amp;lt;/ScriptMethod&amp;gt;&lt;br&gt;        &amp;lt;/Members&amp;gt;&lt;br&gt;    &amp;lt;/Type&amp;gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;Then you could do something like:&lt;br&gt;[Appdomain]::CurrentDomain.MSDN()&lt;br&gt;&lt;br&gt;Jeffrey P. Snover [MSFT]&lt;br&gt;</description></item><item><title>re: Getting MSDN help urls for .NET BCL types and Members</title><link>http://blogs.msdn.com/monad/archive/2005/12/28/507903.aspx#508363</link><pubDate>Sat, 31 Dec 2005 11:48:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:508363</guid><dc:creator>kfarmer</dc:creator><description>Now if only MSDN would provide a way for vendors to register base URLs for strong-named assemblies, this could be extended to non-MS types...</description></item><item><title>re: Getting MSDN help urls for .NET BCL types and Members</title><link>http://blogs.msdn.com/monad/archive/2005/12/28/507903.aspx#508386</link><pubDate>Sat, 31 Dec 2005 20:36:06 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:508386</guid><dc:creator>Monad Team</dc:creator><description>&amp;gt; Now if only MSDN would provide a way for vendors to register base &lt;br&gt;&amp;gt; URLs for strong-named assemblies, this could be extended to &lt;br&gt;&amp;gt; non-MS types&lt;br&gt;&lt;br&gt;Right.  In lieu of that happening, the scriptMethod could do a one time load of some metadata which mapped REGEXs against the full typename to URL-maker strings (think:  $URLMAKER -f $this.GetType().FullName )  where $URLMAKER for MSDN would be:&lt;br&gt;&amp;quot;&lt;a rel="nofollow" target="_new" href="http://msdn2.microsoft.com/library/"&gt;http://msdn2.microsoft.com/library/&lt;/a&gt;{0}.ASPX&amp;quot; &lt;br&gt;&lt;br&gt;Jeffrey P. Snover [MSFT]</description></item><item><title>re: Getting MSDN help urls for .NET BCL types and Members</title><link>http://blogs.msdn.com/monad/archive/2005/12/28/507903.aspx#508389</link><pubDate>Sat, 31 Dec 2005 21:07:25 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:508389</guid><dc:creator>kfarmer</dc:creator><description>Yup.. and if there were some standard web service contract for retrieving the information, we wouldn't need to launch in a browser -- we could merely format the information as appropriate to the display.&lt;br&gt;&lt;br&gt;</description></item><item><title>Loving Mush - I mean Monad</title><link>http://blogs.msdn.com/monad/archive/2005/12/28/507903.aspx#558755</link><pubDate>Thu, 23 Mar 2006 11:47:12 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:558755</guid><dc:creator>ComputerZen.com - Scott Hanselman</dc:creator><description /></item></channel></rss>