Tabs Studio v2.0.1 released – fixed tabs reordering when entering the debug mode in Visual Studio 2010.
May 7, 2010
April 20, 2010
Missing stdole.dll with a custom Visual Studio 2010 installation
If you perform a custom Visual Studio 2010 installation selecting only C++ development tools on a clean Windows 7 x64 machine, running Tabs Studio v2.0 generates “System.IO.FileNotFoundException: Could not load file or assembly ‘stdole, Version=7.0.3300.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’ or one of its dependencies. The system cannot find the file specified.”
A workaround is to manually install stdole.dll in the GAC. For example, running the following single line command from an elevated command prompt:
"C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin\gacutil.exe" -i "C:\Program Files (x86)\Common Files\microsoft shared\MSEnv\PublicAssemblies\stdole.dll"
Another workaround is to add Visual C# development tools in the Visual Studio 2010 installer:
April 18, 2010
Tabs Studio v2.0 is released
Tabs Studio v2.0.0 public is released – comparing to v1.9.5 added a yellow tone to the selected unfocused tab background in VS 2010.
April 15, 2010
Tabs Studio v1.9.5 is released
Tabs Studio v1.9.5 is released:
- Added the Tabs Studio toolbar to VS 2010.
- Added the “Show tabs in a separate window” option to VS 2010.
- Added close file buttons.
- Changed selected tab colors to match the default VS 2010 theme.
- Removed the XP quick style option in VS 2010.
- Removed the fixed expiration date for VS 2010.
- Fixed the rare unhandled exception when creating the Tabs Studio toolbar.
April 13, 2010
Visual Studio 2010 RTM
Yesterday Visual Studio 2010 was released:
I don’t see any changes in default VS tabs behavior comparing to RC. I’ve tested Tabs Studio v1.9.0 with VS Professional, Premium and Ultimate 2010 RTM editions and everything worked just fine.
April 12, 2010
Close file buttons
I’ve added the close file button to each extension. It should be particularly useful in SSMS where you more often need to close a file rather than a whole tab:
In the default style these buttons are collapsed, but you can use all usual properties in a custom style to make them visible. For example, the following style makes close file buttons visible on the selected tab and hides the close tab button in a tab when it contains more than a one extension:
<Style TargetType="TabsStudio:TabExtensionCloseButton" BasedOn="{StaticResource DefaultTabExtensionCloseButton}">
<Style.Triggers>
<Trigger Property="IsTabSelected" Value="True">
<Setter Property="Visibility" Value="Visible"/>
</Trigger>
</Style.Triggers>
</Style>
<Style TargetType="TabsStudio:CloseTabButton" BasedOn="{StaticResource DefaultCloseTabButtonStyle}">
<Style.Triggers>
<Trigger Property="IsMultiExtensions" Value="True">
<Setter Property="Visibility" Value="Collapsed"/>
</Trigger>
</Style.Triggers>
</Style>
March 17, 2010
Tabs Studio v1.9.1 is released
Tabs Studio v1.9.1 is released – added support for Debugging and Executing tab states in SQL Server Management Studio, added ReadOnly tab title text cleanup in SSMS.
March 15, 2010
Special tab titles in SSMS
SQL Server Management Studio adds the [ReadOnly] prefix to the window title for read only scripts. It also adds Debugging… and Executing… suffixes when SQL scripts are debugged and executed:
I’ve added additional processing for such titles that removes excessive text and adds appropriate status icons:
March 5, 2010
Tabs Studio v1.9.0 is released
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.







