Code Block End Tagger

New options are now available for Code Block End Tagger

Use double-click to navigate

Previously, single-click on the tagger would take you to the beginning of a tagged code block.
This can now be changed to use double-click instead.

Show icon only

You can now configure Code Block End Tagger to display icons only during normal usage and have a header displayed only when mouse is over the icon.

Solution Explorer – Install PFX Files

Code Signing Certificates (PFX files) can now be easily installed directly from Solution Explorer:

Bug Fixes:

• Slow performance when loading C++ files
• Code Block End Tagger compatibility issue with Productivity Power Tools
• Other minor fixes

Other

VSCommands will now use Visual Studio version as first part of its own version (3.9.0.0 became 10.3.9.0).

This is to avoid confusions in the near future when VSCommands 11 will be released.

• Fixed – VSCommands is stealing focus [see details]
• Fixed – VS crashing when using Ctrl+Shift+X to switch to a different keyboard layout [see details]

• Fix – Performance when editing css files
• Fix – Performance when using Locate in Solution with big solutions (>500 projects)
• Fix – Memory Leak when opening solution
• Fix – Memory Leak when using Locate in Solution
• Fix – Code Block End Tagger – only first line will now be shown for multiline statements [bug report]
• Other minor fixes

• Fixed – File Structure – navigation to regions and abstract methods does not work properly
• Fixed – File Structure – navigation to end of code element (when Ctrl is pressed) does not always work
• Fixed – File Structure – tooltip displays wrong comments for some elements
• Fixed – File Structure – comments for method parameters and permissions not always displayed properly
• Fixed – File Structure – clear contents after file has been closed
• Fixed – File Structure – when navigating always put target element in center
• Fixed – Create Code Contract – contract for abstract class is not longer private
• Fixed – Code Block End Tagger – when navigating always put target element in center
• Code Block End Tagger – experimental support for Razor files added
• Code Block End Tagger – support for regions added
• Other minor fixes

Code Block Tagger (pro)

VSCommands will now add a tagger at the end of each code block:

Clicking on the tagger will take you to the beginning of the code block.

By default tagger will only show when beginning of the code block is not currently visible. This behaviour can be changed from Tools | VSCommands | Options | Text Editor | Common

Text color can be changed from Tools | Options | Environment | Fonts and Colors | VSCommands.CodeBlockTagger.Foreground

File Structure – Razor, ASPX, HTML, JavaScript

File Structure Window (Tools | VSCommands | File Structure) now supports Razor, Aspx, HTML and JavaScript files:

JavaScript embedded inside Razor, ASPX or HTML files is supported as well:

Color Highlighting – Color Picker

Clicking on a color in a code editor will now show a color picker popup where you can select a value to be used in place of the old color:

Debug As Different User – Web Projects Support

Debug As Different User now supports Web Projects debugged on local IIS Server:

Organize Namespace Imports

You can now easily sort namespace imports (C# and VB) on a project level, or from context menu of a code editor:

Copy Document Content

This command copies the content of selected document to the clipboard without opening the document.

It is available from context menu only when CTRL key is press. This behaviour can be changed from Tools | VSCommands | Options | Features.

Don’t forget to suggest new features and vote for existing ideas at vscommands.com/community
Follow @vscommands on Twitter or rate us in Visual Studio Gallery!

• Prevent Accidental Drag & Drop in Solution Explorer – fixed issue which prevented it from working in some scenarios
• Group Items – fixed issue which prevented it from working in some scenarios
• File Structure – added experimental support for MVC3 Razor, ASP.NET and HTML files
• General stability improvements
• Other minor fixes

• Performance improvements (UI and background processing)
• Fixed issue where on some machines Insert Guid, Prevent Accidental Drag & Drop and Group Items didn’t work at all.
• File Structure – fixed issue where some elements were duplicated on first load
• File Structure – added experimental support for Java Script and SQL files
• Copy/Paste reference – fixed issue where in some circumstances Paste didn’t populate HintPath properly

• Bug Fix – Unable to save settings, ‘Save’ button not visible when text size set to more than 100% in Windows settings [support topic] – FIXED
• Bug Fix – Incompatibility issue with other plugins caused by Microsoft.Practices.ServiceLocation.dll – FIXED
• Bug Fix – File Structure Window temporarily goes blank when editing C# and VB files – FIXED
• Bug Fix – Locate In Solution doesn’t always work with files inside Solution Folders [support topic] – FIXED
• File Structure Window performance improvement – previously File Structure Window (a WPF control) has been hosted inside ElementHost inside WinForms Tool Pane exposed by Visual Studio.
  This caused serious performance problems and has now been rewritten to show WPF content directly.
  This change improves performance of all other Tool Pane windows exposed by VSCommands.
• Other minor fixes

Don’t forget to suggest new features and vote for existing ideas at vscommands.com/community
Follow @vscommands on Twitter or rate us in Visual Studio Gallery!

File Structure Window improvements

Hovering over item in the File Structure window will now display comments associated with that element: (C# and VB):

For XML elements tooltip will display attributes of that element:

File Structure Window – Custom comments support (PRO)

VSCommands PRO can now display custom comments (such as todo, note, hack and strong comment [//+]) inside File Structure Window:

This feature can drastically improve navigation in large code blocks.

For example, you can use strong comments //+ to mark certain points inside a method:

and quickly navigate between them using File Structure window:

Friendly Solution Name – Environment Variables support

You can now use {env:xxx} placeholder to insert environment variables inside Friendly Solution name:

Other changes:

• Reload All Projects will now remember Startup Project settings and re-apply them once reloading has finished (support topic)
• File Structure – Performance improvements – it will now only refresh when VS has been idle for > 5s (when file processing on edits is enabled)
• File Structure – VB.Net regions are now recognized properly
• File Structure – filxed issue where classes with constructors were collapsed on every edit
• C# and VB files are not longer processed using VS CodeModel to improve performance and solve issues with vb files. (support topic)
• File Structure – navigating to element which is inside collapsed outlining will now expand this outlining to make sure that element is visible (support topic)
• File Structure – expand button added
• Build Startup Projects command will no longer block UI when there is only one startup project to build (support topic)
• VSCommands diagnostic messages will now be logged to Activity Log when Visual Studio is started with /Log argument
• Processing of C++ files is disabled by default – It uses VS CodeModel which turned out to be source of problems on some machines. You can still enable it from Tools|VSCommands|Options|Text Editor| C++ if it works for you well. It will be replaced with another approach in the near future.

File Structure  – CSS files support

CSS files are now supported by File Structure Window (Tools | VSCommands | File Structure)

File processing settings can be configured from Tools | VSCommands |Options | Text Editor | CSS Files

Currently supported file types:

• C# (.cs)
• VB.Net (.vb)
• C++ (.cpp, .h)
• Xml (.xml + any xml based file format)
• Xaml (.xaml)
• Config files (.config, .clientconfig)
• CSS (.css)

Support for SQL, JavaScript and Razor files is under development so stay tuned!

File Structure – Code Regions support

File Structure window will now display code regions as defined in your code:

(C#)

Code Regions are not limited to C# and VB.NET and you can use them with other file types too!

In CSS files use /* #region region_name */ and /* #endregion */ comments:

(CSS)

In Xml/Xaml/Config files use <!—#region region_name –> and <!—#endregion –> comments:

(XAML)

(.CONFIG)

File Structure – Collapse/Expand Siblings

You can now hold CTRL while collapsing/expanding node in File Structure to collapse/expand all its siblings

WinQual

VSCommands is now integrated with Microsoft WinQual which means that if it ever causes your Visual Studio to crash and you choose to report the problem then we’re going to get detailed crash details!
You’ll also get notification as soon as the fix is ready.

Other Changes:

• Assembly Info window can now be closed using ENTER or ESC keys
• Friendly Solution Name – will revert back to default name when branch name regex fails and the error will be logged in vscommands output window
• Fixed bug where Xml Key Attributes were no longer showing
• Fixed – bug where some output window colors were not read properly from the settings
• Fixed – bug which created phantom data in File Structure window and could cause VS to crash
• VSCommands will now no longer auto update when Microsoft Productivity Power Tools are installed

Don’t forget to suggest new features and vote for existing ideas at vscommands.com/community
Follow @vscommands on Twitter or rate us in Visual Studio Gallery!