Tabs Studio v3.7.1 released:
- Increased tabs font size selection up to 20pt for HiDPI screens.
- Fixed a rare exception on Visual Studio startup when PPT document well is installed.
Download link: Tabs Studio v3.7.1.
Tabs Studio v3.7.1 released:
Download link: Tabs Studio v3.7.1.
Tabs Studio v3.7.0 released:
Download link: Tabs Studio v3.7.0.
Tabs Studio v3.6.5 released:
Download link: Tabs Studio v3.6.5.
Tabs Studio v3.6.0 released:
Download link: Tabs Studio v3.6.0.
Tabs Studio v3.5.0 released:
Download link: Tabs Studio v3.5.0.
Visual Studio 2015 Community Technology Preview 5 is currently available for download:
Visual Studio 2015 CTP 5 splash screen
While I do not see any changes in default VS tabs behavior, VS 2015 stopped support for add-ins and that required substantial internal changes in Tabs Studio. Now, instead of VS Add-in Manager, Tabs Studio is presented in VS Extensions and Updates dialog. You can disable and uninstall it from there (though to uninstall all files it is still recommended to use Control Panel):
Tabs Studio in Visual Studio 2015 Extensions and Updates dialog
With the new implementation I removed the Connect word from Tabs Studio command names that you can assign to keyboard shortcuts:
Tabs Studio commands in Visual Studio 2015
Everything else in Tabs Studio should work as usual. Please let me know if it doesn’t 🙂
Tabs Studio in Visual Studio 2015 CTP 5
Download link: Tabs Studio v3.5.0.
Tabs Studio v3.2.0 released:
Download link: Tabs Studio v3.2.0.
Many automatically opened SQL tabs in SQL Server Management Studio have names like SQLQuery1.sql, SQLQuery2.sql etc:
SQLQuery tabs in SSMS 2012
To better distinguish such tabs I’ve created the SQLComment add-in that can add a comment from the query body to the tab name:
Tabs with comments in SSMS 2012
You can chose any comment format and configure SQLComment to extract it using a .NET regular expression. For example, the default regex
StoredProcedure \[dbo\]\.\[(?<M>\w+)\] extracts the procedure name (AddEvent) to the M named group from the following code:
USE [ReportServer] GO /****** Object: StoredProcedure [dbo].[AddEvent] Script Date: 3/11/2014 8:29:10 AM ******/ SET ANSI_NULLS ON GO SET QUOTED_IDENTIFIER ON GO
SQLComment options
To extract description from a comment like ––– provides details on investors you can use the regex ^––– (?<M>.+)$. To support several formats you can combine regexes with ‘|’ like ^––– (?<M>.+)$|StoredProcedure \[dbo\]\.\[(?<M>\w+)\]. You can use several separate M groups (line Name and Ext in standard tab grouping), the resulting string will be concatenated from all captures. Only tabs starting with SQLQueryNN.sql are considered for commenting.
Download link: SQLComment v1.0.0.
Update (March 20): Added commenting support for grouped tabs SQLComment v1.0.1.
Update (October 23): Added the “Set SQL comment…” tab context menu command for temporary comments. Added more customization for displaying comments. SQLComment v1.0.4.
Tabs Studio v3.1.5 released:
Download link: Tabs Studio v3.1.5.
I’ve added support for multiple captures of the Name and Ext groups in the Title grouping regex. For example,
(?<Name>.+?)-(?<Name>.+?)(?<Ext>\..+) will create the MainWindow name from the Main-Window.xaml tab. (?<Ext>Test)(?<Name>.+?)(?<Ext>\..+) will create the Test.xaml extension from the TestWindow.xaml. You can use as many separate Name and Ext groups as you need, the resulting string will be concatenated from all captures. It allows you to capture multiple parts of the original tab title as the name or extension. Technically I just switched to the built-in Group.Captures .NET regex feature.
Download link: Tabs Studio v3.1.5.
Update: Connell Watkins shared his use of multiple captures to group lots of similar files.