VSCommands 3.6.9.0 Released!

admin | April 27, 2011 | 0 Comments

New in this release:

Silverlight breakpoints support (Lite)

Silverlight 5 Beta has been released earlier this month with plenty of great new features. One of the most anticipated changes is the ability to set breakpoints on bindings in xaml.

VSCommands Lite now provides a quick way to set breakpoints on all bindings and clear all breakpoints in xaml files.
As a bonus you can also set breakpoints on bindings with a condition that code execution will break only when binding has failed.

Debug Output Formatting (Pro)

Add custom rules to define how Debug Output text is formatted.

Just add a regular expression pattern and select format type (Verbatim, Information, Warning, Error, Strong, Weak)

Next time you debug your application Debug Output Window will format your messages.

You can add new patterns from Tools | VSCommands | Options | IDE Enhancements | Debug

and modify styling from Tools | Options | Environment | Fonts and Colors | VSCommands.DebugOutput.*

Friendly Solution Name – Global Setting (Lite)

VSCommands 3.6.8.0 was released with ability to set friendly name for solutions which is of great help when you work on different branches of the same project.

It can display branch name in Visual Studio window title bar

Solution Explorer

and when alt-tabbing between windows or when using peek feature of Windows 7

One of the most requested additions to this feature was the ability to have a global friendly name pattern which can be set once for all solutions.

This can be now achieved from Tools | VSCommands | Options | IDE Enhancements | Solution

This pattern will be stored in local windows registry instead of solution file and can be overridden by solution specific setting

Xaml Keywords highlighting (Pro)

Previous versions of VSCommands allowed marking of XAML specific constructs such as bindings or static and dynamic resources to make them easier to spot

New version extends this functionality by allowing you to apply custom format to xaml keywords.

By default they will be displayed using bold font

but you can change the format at any time from Tools | Options | Environment | Fonts and Colors where you will find three new items: VSCommands.Xaml.Binding, VSCommands.Xaml.DynamicResource and VSCommands.Xaml.StaticResource.

You now also have better control of which parts of this feature are enabled from Tools | VSCommands | Options | IDEEnhancements

Visual Studio Unhandled Exceptions (Lite)

Have you ever experienced a silent crash of Visual Studio where IDE just disappears without any warning?
It is extremely hard to find a source of such crash when you have several extensions and SDKs installed on your dev machine.
VSCommands Lite will now try to help in such situations by monitoring unhandled exceptions and providing additional system information to help you in reporting these problems to extension developers or Visual Studio dev team.

Once unhandled exception occurs you will be presented with a dialog box containing information about exception, installed extensions and local system setup.

Note that Visual Studio will exit after you close this dialog because starting from .Net 2.0 unhandled exceptions cause applications to terminate.
You can change this default behavior by adding legacyUnhandledExceptionPolicy to devenv.exe.config file as described on msdn.
This setting will make sure that Visual Studio doesn’t terminate so you can continue working, but it’s advised to immediately save your work and restart IDE anyway since it may be in unstable state.

Other Changes

Group Items – fixed bug introduced in previous version which prevented group items feature from working
Group Items – performance improvement – group items will now perform much quicker than before
Other minor fixes

We need your feedback!

Suggest new features and vote for existing ideas at vscommands.com/community
Follow @vscommands on Twitter or rate us in Visual Studio Gallery!

You can now get to our feedback forum directly from Visual Studio: