Tabs Studio v1.9.0 public is released – comparing to v1.8.5: fixed inability to display identical extensions in a tab group, removed unnecessary access to Visual Studio documents on tabs update.
Reminder for those upgrading from v1.8.0: previous versions of Navigator, Saver and Sorter add-ins don’t work with Tabs Studio v1.8.3 and greater. Here are the updated versions: Navigator v1.0.1, Saver v1.0.1, Sorter v1.0.2.
Tabs Studio v1.8.5 is released – fixed the Remove path from tab name option for SSMS broken in v1.8.2, changed installer to leave disabled Tabs Studio state in SSMS on upgrade, fixed 2 pixels tabs overflow over a code window in SSMS, fixed occasional 1 pixel dark line under the tabs.
I’ve prepared two tab context menu translations for German and Spanish localized Visual Studio editions:

Localized context menu in German Visual Studio 2008
Feel free to correct my translation and update it with other languages. To add a new language just copy an existing
.resx and provide translated string values:

Localizer project
Download
Localizer v1.0.0
I’ve added two additional tabs layouts – Wrap and Stack:

Tabs layout option
Standard layout is the way it worked before:

Standard layout
Wrap layout retains original tab width and doesn’t try to distribute tabs between rows evenly:

Wrap layout
Stack layout places tabs in a single vertical stack and should be useful when having a separate tabs window on a side of a code window:

Stack layout
The
System.Windows.Controls.Panel TabPanel2 property was added to the
TabsStudioExt.Tabs class replacing the
System.Windows.Controls.Primitives.TabPanel TabPanel property.
TabPanel is still present to prevent add-ins that use it from crashing at startup, but always returns an empty panel. I’ve updated
Navigator,
Saver and
Sorter add-ins to use the new
TabPanel2 property.
Tabs Studio v1.8.2 is released:
- Added the Group titles ignoring case differences option.
- Added Title grouping regex processing to single titles.
- Changed default Title grouping regex and remove path transform to support a path with back slashes.
- Separated remove path transforms for VS and SSMS internally.
- Improved the first Tabs window reliability to save and restore its position.
- Fixed rare code window shift when using tabs in a separate window.
- Fixed Open Corresponding File error to open .h files on non-English VS editions by removing workaround to open Windows Forms .h files from .h [Design].
- Fixed the incorrect package name in the Visual Studio 2010 About window for the Tabs Studio 2010 Helper extension.
Since the beginning, Tabs Studio didn’t group e.g. WebDataService.cs and WebdataService.svc because of the case difference. It was my conscious decision to indicate an inconsistence and prompt a developer to fix it. But now I think there is no harm to provide an option and give you full control of this behavior:

Group titles ignoring case differences option
This week Visual Studio 2010 Release Candidate was released:

Visual Studio 2010 Ultimate RC
I don’t see any changes in default tab behavior comparing to
Beta 2 in this release. I’ve tested Tabs Studio v1.8.0 with Professional, Premium and Ultimate 2010 RC editions and everything worked as good as in Beta 2. Interestingly, the
Load per user extensions when running as administrator VS option is now on by default.
Visual Studio has a special project type – Database Project. Tab names in such project include a path with back slashes:

A Visual Studio database project
To support back slashes I’ve changed the default
Title grouping regex to
(?<Name>(.*[/\\])?.+?)(?<Ext>\..+) and I’ve changed the default remove path transform to
^(.*[/\\\\])?(.*)$. With these changes selecting the
Remove path from tab name option successfully removes paths:

Paths removed
It would be nice to remove trailing
Project1 as well.
(?<Name>(.*[/\\])?.+?)(?<Ext>\..+) \(Project1\) helps, but only for grouped titles like
Script1. I’ve made additional changes in Tabs Studio and now single titles are affected by
Title grouping regex too:

Project1 removed
For more advanced title customization there is
TitleTransform available in add-ins.
Decorator add-in v1.0.0 was found guilty in disrupting Visual Studio operations, even causing a crash. It too often looked for a project associated with a window, particularly disrupting when the window was already closed.
I’ve added a dictionary to store a project for a tab. Now the project is searched in Visual Studio only once when the tab is created. You may also notice in source code how I use tab.TabItem for tab identity – this is because TabsStudioExt.Tab objects are created at will and only WPF controls and DTE objects are stable enough for identity purposes.
Download Decorator v1.0.1.