Search
Closed
as Won't Fix Help for as Won't Fix

12
Sign in to vote
0
Sign in to vote
Sign in
to vote
Type: Suggestion
ID: 507891
Opened: 11/3/2009 8:19:00 AM
Access Restriction: Public
0
Workaround(s)
Visual Studio 2005 and 2008 contained an (not officially supported) feature that allows display of vertical guidelines in the (code) text editor. The feature is quite a hack, because a manual change in the Windows registry is needed. Visual Studio 2010 however, seems to completely miss this feature (see here: https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=484758).

Not only do I like this feature to be return in Visual Studio 2010, I like better support for it and it to be configurable on a project level (with VS2005 and VS2008 this is only possible on machine user level, because it is a HKEY_CURRENT_USER setting).

Many development teams use coding rules that state that a line of code must not exceed a certain amount of characters. Guidelines visualize this and help developers obey by these rules. This however is a problem when a single developer works on multiple projects with different rules about characters per line.

This problem can be solved by enabling guidelines to be specified on a per project basis.
Details (expand)

Version Currently Used

Visual Studio 2010 Beta 2

Operating System Currently Used

Windows Vista

Suggestion

Allow specifying guidelines on a per (C#) project basis.

Benefits

Faster Development
Other (please provides details below)

Other Benefits

Improved code quality.
      You can indicate your satisfaction with how Microsoft handled this issue by completing this quick 3 question survey. [Details]

 

File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 11/3/2009 at 10:26 PM
Thank you for your feedback, We are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Posted by Microsoft on 11/18/2009 at 6:37 PM
Hi .NET Junkie,

Thank you for logging this suggestion. We're unfortunately past the point of adding new features or making design changes for VS 2010, so I'm resolving this issue as Won't Fix for the current release. However, we are hoping to provide a guidelines extension for the VS 2010 editor, though there is no specific timeframe for this work. It's unlikely that we'll add this to project settings through extensibility, but I've added your suggestion to our list of ideas for to be revisited for a future version of Visual Studio.

Thanks for trying VS 2010 Beta2 and sending your feedback!

Brittany Behrens
Program Manager, VS Platform
http://blogs.msdn.com/visualstudio