Tabs Studio v4.5.0 released:
- Added support for Visual Studio 2019 Preview 1.1.
- Added a new sorting rule type TabNameUntransformed (it ignores tab title transformations by other add-ins) and made it the default one in the Sorter add-in.
- Created the OrderKeeper add-in that remembers a tab position when it is closed and restores the position when the tab is reopened.
- Created the OpenDesigner add-in that adds a context menu command to open a corresponding [Design] view.
- Changed the PriorityGroup add-in to ignore tab title transformations by other add-ins.
- Changed the SuperName add-in to not add a project name to the PriorityGroup super group.
- Added support for solution folders and database projects to the Sync add-in.
- Removed the “Close All But Tool Windows” command from the context menu in VS 2017.
- Fixed the Sorter add-in to correctly tag the fist super group tab after the PriorityGroup super group.
- Fixed a Visual Studio hang when adding a tab to the priority group with Sorter and SuperName add-ins enabled.

Tabs Studio in Visual Studio 2019 Preview
Download link: Tabs Studio v4.5.0.
Dumb question but how do I install this OrderKeeper in SSMS?
Comment by Greg — January 25, 2019 @ 6:54 pm
OrderKeeper is included with Tabs Studio v4.5.0 installation. You can enable it in Tabs Studio Add-in Manager.
Comment by Sergey Vlasov — January 25, 2019 @ 10:15 pm
I have it enabled there under the “Startup” column but it doesn’t seem to keep the order of the tabs. I’m running SSMS 17.9.1 but I should mention I also use SSMSBoost to autosave the tab state on exit before I shutdown SSMS so perhaps that’s preventing OrderKeeper from working or perhaps OrderKeeper is designed to keep the the tab position only when the tab is manually closed and then reopened.
Comment by Greg — February 7, 2019 @ 12:06 am
Greg,
Please note that OrderKeeper works only within a session, it doesn’t remember order when you close and reopen SSMS. OrderKeeper also uses a document path to identify tabs, that may not work with temporary file names for SSMS scripts.
Comment by Sergey Vlasov — February 7, 2019 @ 10:56 am