Add capability of using hyperlinks in code to visual studio - by VanceMorrison

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


75
0
Sign in
to vote
ID 296795 Comments
Status Closed Workarounds
Type Suggestion Repros 19
Opened 9/5/2007 9:55:48 AM
Access Restriction Public

Description

Currently Visual Studio will turn strings that look like URLs into hyperlinks (eg http://www.codeplex.com/hyperAddin), however it would be even more useful if these hyperlinks to refer to other parts of the code base (using symbolic lookup) or can be easily defined by the user.  This allows you to create quick links to related code, or create an overview description that can then be linked to from many places in the code base.  

There is a prototype of this defined as a Visual Studio Addin at http://www.codeplex.com/hyperAddin.  This should be integrated into Visual Studio itself (and improved, like having spell checking, warnings on broken links, and intellisense when creating links). 

Please see the help for the hyperaddin for a complete feature overview.    

In addition to the hyperlinking feature, the addin also does word-wrapping in the comments.   It can fix up formatting when words are added or deleted (currently you have to invoke a 'Format' command to fix up a comment, but you could imagine doing it as you type).    This is a trivial feature, but a real time saver (because adding just a few words to the middle of a paragraph wrecks the word wrapping).  

Both of these features encorage commenting in a code base, which in general is a very good thing.   Please consider adding this in the next version.  
Sign in to post a comment.
Posted by cmartz on 10/30/2008 at 6:46 AM
Something like this would allow me to define a bookmark (or anchor) in my code and hyperlinking from Generic test case results straight to the code.
Posted by Microsoft on 4/18/2008 at 12:47 AM
Vance,

Thanks for taking the time to submit your suggestion! Your feedback is very valuable to us. During every release, we make sure to review all customer suggestions to help guide our decision making. After taking a look at the suggestions and priorities for this release, we’ve decided to invest heavily in improving our experience around understanding code, navigating through code, and test-driven development style of writing code. Unfortunately, given these priorities, we will not be addressing this suggestion for our next release to allow us to focus our investments.

Given this decision, I’m going to go ahead and resolve this suggestion as a Won’t Fix. Although we’re resolving this suggestion, please be assured that it has been recorded in our running list of feature suggestions that we use when planning for each release and that it will not be lost. If you have any questions or comments, feel free to either reactivate the bug or shoot me an email at djpark@microsoft.com.

Thanks,
DJ Park
Visual C#, Program Manager
Posted by Frank Robijn on 4/12/2008 at 1:55 PM
It would be great if this type of functionality is also available for the /// style comments in C#. So that either a <see cref=.../> becomes a hyperlink, or that code:Method is translated into a <see cref=""> when the documentation is generated.
Posted by dbl007 on 9/28/2007 at 7:00 AM
Great stuff!
Posted by kalyancs [msft] on 9/20/2007 at 4:19 AM
This makes a lot of sense for anyone working with an existing codebase. Developers will definitely appreciate this problem.
Hope this does not get "triaged out" after counting votes :).

I am sure if you put in resharper features here, there may not be enough votes but enough ppl buy resharper as vs lacks in the features that resharper fills in.

Posted by Microsoft on 9/6/2007 at 8:26 PM
Hi VanceMorrison,

Thanks for submitting this suggestion! I agree, this would definately be a very useful feature to have. Given where we are in the current product cycle, this isn't something we'll be able to do for Visual Studio 2008, but we'll definately consider this as we begin planning for our next release. If you have any questions or concerns, please feel free to contact me directly at djpark@microsoft.com. Keep the suggestions coming!

Thanks,
DJ Park
Visual C#, Program Manager