Asking for the moon...

[Merrion]

You know how there's that [ a p i ] tag on the other forum that takes you to the relevant API declaration in AllApi.net...what are the chances of an [ m s d n ] tag here that takes you to the class definition in MSDN.

 

e.g.

 

You need to look at [msdn]IEnumerator[/msdn]

 

becomes

 

You need to look at IEnumerator

[divil]

There is an [m s h e l p] tag which does something similar given the complete url of a local help page from the vs.net or framework sdk documentation.

 

Derek kindly made it for us, so perhaps he could clarify exactly how it works.

[Derek Stone]

Wow. I did something "kindly" for once. What a change...

 

You can use the [mshelp] tag like such:

 

[mshelp]ms-help://MS.VSCC/MS.MSDNVS/cpref/html/frlrfSystemExceptionClassTopic.htm[mshelp]

[mshelp=ms-help://MS.VSCC/MS.MSDNVS/cpref/html/frlrfSystemExceptionClassTopic.htm]Exception class[/mshelp]

 

... which would generate the following:

 

[mshelp]ms-help://MS.VSCC/MS.MSDNVS/cpref/html/frlrfSystemExceptionClassTopic.htm[/mshelp]

[mshelp=ms-help://MS.VSCC/MS.MSDNVS/cpref/html/frlrfSystemExceptionClassTopic.htm]Exception class[/mshelp]

 

The tags take a http://ms-help:// URI as input, which is easily retrieved from a local installation of the .NET Framework SDK or MSDN.

 

As for what you're asking for? That would be rather tricky to accomplish, since mapping one word to its associated MSDN topic would be very tricky.

 

With that said we could generate a working redirect script over time that could be added to. I can start one on EliteVB if you wish. Either that or we could work on a more user-friendly version of MSDN, hosted and updated by us. This of course would require community support, since we're all busy people.

[Derek Stone]

Alright. I have an ASP.NET page running on our server which translates a fully-qualified class name or a namespace into its associated reference document on MSDN. This utility is limited, since it will not except a class that isn't fully qualified. For example, the utility will accept "System.Environment" but not "Environment". I don't see this as much of a problem, although I will work on a solution to allow for short class names.

 

If an administrator could create a vB Tag for this utility it would be great. The utility is located at the following URI:

http://www.elitevb.com/tools/msdn7itr/

 

It can be used like so:

http://www.elitevb.com/tools/msdn7itr/?item=System.IO

http://www.elitevb.com/tools/msdn7itr/?item=System.Environment

 

As Merrion suggested, I think [msdn] would be an appropriate name for the tag.

[Banjo]

Ask and you shall receive.

 

I've done both methods:

 

[msdn]System.IO[/msdn] = [msdn]System.IO[/msdn]

[msdn=System.IO]Find info on System.IO here[/msdn] = [msdn=System.IO]Find info on System.IO here[/msdn]

[Robby]

It works great but shouldn't it open a browser? (instead of using the current window)

[Derek Stone]

It really is improper to open a new window everytime a link is clicked. The user always has the option to open the link in a new window (by pressing shift or by right-clicking on the link). This is one part of vBulletin that I don't care for.

[Robby]

Derek, this is true, but when a link directs a user away from the original site, isn't it better to open a new browser.

[Banjo]

Its probably better for sites aimed at novice users who may find themselves getting lost. However, for programmers, who by definition should be relatively advanced, it is just annoying to have the choice taken away.

[Derek Stone]

VBulletin opens internal links in new windows, which there is no reason for it to be doing. This is unacceptable, and you won't find too many people to argue against that. Of course vBulletin also opens external links in new windows, which is slightly justified, if not still a huge annoyance. I wouldn't bring it up if only external links opened in new browsers, but personally I find the lack of the control that a user should have... well, just that-- lacking.

[Robby]

You're right it is better to be given a choice, but I find myself (on this site) always opening links in a new window. Especially when reading threads, I'll open 5, 10 at one time.

[quwiltw]

***drifting back on topic....

I couldn't get it to work with System.Diagnostics.Process, I edited out the Process class and it works. Maybe a bug?

 

http://www.xtremedotnettalk.com/showthread.php?s=&postid=363411#post363411

[Derek Stone]

I'm guessing you included parenthesis after the namespace and class. This is not handled as of yet. For the time being enter parenthesis after the [msdn] tag.

[edit]The utility doesn't support methods yet anyway. Only namespaces and classes.[/edit]

Edited April 27, 2003 by Derek Stone

[quwiltw]

Actually, I tried it all. System.Diagnostics.Process doesn't work either even without the method on there.

[Derek Stone]

[msdn=System.Diagnostics.Process]Process Class[/msdn]

[msdn]System.Diagnostics.Process[/msdn]

[edit]The above do not work, as you have stated. I'll look for the problem as soon as possible. Thanks for letting me know.[/edit]

[edit]The problem is now fixed. Thanks again.[/edit]

Edited April 28, 2003 by Derek Stone