.NET Zone is brought to you in partnership with:

I’ve been a Windows developer since 3.0 and caught the Visual Basic wave early with v1. I’ve released a “production” application in every version of VB since then (except VB for DOS). Focusing on enterprise, line-of-business development I’ve built Call Center Applications, Mortgage finance systems, Customer Relationship Management tools and more recently I’ve been in the Litigation Support/Electronic Data Discovery/Electronically Stored Information space. Greg is a DZone MVB and is not an employee of DZone and has posted 282 posts at DZone. You can read more from them at their website. View Full User Profile

Visual Studio Column Guides with Editor Guidelines Extension

09.04.2012
| 1897 views |
  • submit to reddit

Visual Studio Gallery - Editor Guidelines (VS2012)

Adds vertical column guides to the Visual Studio text editor. This version is for Visual Studio 2012

Note: This version is for Visual Studio 2012. For Visual Studio 2010, please go here. This version includes both the editor extension and the UI package in a single download.

"Editor Guidelines" is an editor extension for Visual Studio 2012 which adds vertical guidelines behind the text at user-specified column positions. This is useful if you are trying to tabulate columns of data or if you want to ensure that your lines don't go beyond a certain length.

Add a new guideline via the context (right-click) menu on the editor surface. You will see a "Guidelines" flyout with three commands:

  • Add Guideline
  • Remove Guideline
  • Guideline Color

When "Add Guideline" is selected, a vertical dashed line will be drawn at the same position as the caret (insertion point).

image..."

If you're running VS2012 and would like to get column guides, this extension is a quick and easy way... Just installed it on VS2012 RTM and seems to work fine.

(via Random, Happy Dev Thoughts - Visual Studio Plugin for Editor Guidelines: Recommended!)

Published at DZone with permission of Greg Duncan, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)