Newbe Dev Stack

Answer : Another solution is to create something like this <div class="row"> <div class="col-sm-3"> <ul class="nav nav-tabs nav-stacked nav-pills" role="tablist"> <li ng-class="{'active': view_tab == 'tab1'}"> <a class="btn-lg" ng-click="changeTab('tab1')" href="">My Tab 1</a> </li> <li ng-class="{'active': view_tab == 'tab2'}"> <a class="btn-lg" ng-click="changeTab('tab2')" href="">My Tab 2</a> </li> </ul> </div> <div class="col-sm-9"> <div class="tab-content"> <div class="tab-pane" ng-show="view_tab == 'tab1'"> This is tab 1 content </div> <div class="tab-p...

Answer : I'm not sure that you can apply ng-class to tabs like that. After trying and failing I decided to look at the bootstrap-ui source for tabs and made an interesting discovery related to the tab heading attribute. Apparently you can put html in the heading section if you place the tab-heading as a child to a tab element. Check out the tabheading directive in here. This is the example they show: <tabset> <tab> <tab-heading><b>HTML</b> in my titles?!</tab-heading> And some content, too! </tab> <tab> <tab-heading><i class="icon-heart"></i> Icon heading?!?</tab-heading> That's right. </tab> </tabset> In your case I think you might be able to do something like this to get the same effect: <tab ng-repeat="tab in tabs" active="tab.active"> <tab-heading>{{tab.title}} <span ng-show="tab.new">new<...

Answer : Update #2 Vertical tabs are out of preview and are now officially part of Visual Studio 2019 v16.4! Update #1 The new "Vertical Document Tabs" feature is part of Visual Studio 2019 version 16.4 Preview 2. There is also a dedicated blog post. Original answer Download CustomDocWell.vsix Unzip the file, e.g. rename it to CustomDocWell.vsix.zip and extract the contents Download the workaround extension.vsixmanifest (non-raw page) The only change is that the upper bound of the InstallationTarget version has been removed Replace the original extension.vsixmanifest with the workaround file Download the workaround manifest.json (non-raw page) The only change is the sha256 for extension.vsixmanifest has been recalculated Replace the original manifest.json with the workaround file Zip the contents into a new CustomDocWell.zip Important : Make sure the root of the zip file is at the level of extension.vsixmanifest and manifest.json , as ...