How can I prevent hyper evolved versions of regular creatures from wiping out their cousins?

Twin primes whose sum is a cube

A reference to a well-known characterization of scattered compact spaces

How can saying a song's name be a copyright violation?

Why is it a bad idea to hire a hitman to eliminate most corrupt politicians?

Infinite Abelian subgroup of infinite non Abelian group example

Is it unprofessional to ask if a job posting on GlassDoor is real?

Intersection of two sorted vectors in C++

Why is the 'in' operator throwing an error with a string literal instead of logging false?

90's TV series where a boy goes to another dimension through portal near power lines

When a company launches a new product do they "come out" with a new product or do they "come up" with a new product?

Stopping power of mountain vs road bike

Combinations of multiple lists

Watching something be written to a file live with tail

Will google still index a page if I use a $_SESSION variable?

Why was the shrinking from 8″ made only to 5.25″ and not smaller (4″ or less)?

How to take photos in burst mode, without vibration?

Is "remove commented out code" correct English?

How can I fix/modify my tub/shower combo so the water comes out of the showerhead?

Can a rocket refuel on Mars from water?

How can I make my BBEG immortal short of making them a Lich or Vampire?

How to model explosives?

CEO ridiculed me with gay jokes and grabbed me and wouldn't let go - now getting pushed out of company

Facing a paradox: Earnshaw's theorem in one dimension

Can I install the Custom Document Well (vertical tabs) extension for Visual Studio 2019?

How do I turn off or adjust the clever tab completion in Ubuntu (Programmable Completion)Custom indentation mode with tabs for Emacsrotated vertical tabs for chrome or firefoxPinned tabs not lighting up when changed in chrome on Mac OSXHow to hide tab bar in chrome but still use tabs?No idea on how to Restore chrome tabs using user data files? Advice Much appreciatedChrome (67.0.3396.99) - new tab doesn't open at the end of tabsvisual studio code extensionHow to specify a different color for active tab in colored document?Getting Error while installing CPP Tools

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}

3

The Custom Document Well extension is only available for Visual Studio 2017. Is there a way to install it for Visual Studio 2019? Specifically, I only care about the vertical tabs feature.

As of the time of writing this question, the current version of Visual Studio 19 is 16.0.0 and the current version of the Custom Document Well extension is 15.06.

tabs extension visual-studio-2019

share|improve this question

asked 9 hours ago

Andrew KeetonAndrew Keeton

4422820

add a comment | 

3

The Custom Document Well extension is only available for Visual Studio 2017. Is there a way to install it for Visual Studio 2019? Specifically, I only care about the vertical tabs feature.

As of the time of writing this question, the current version of Visual Studio 19 is 16.0.0 and the current version of the Custom Document Well extension is 15.06.

tabs extension visual-studio-2019

share|improve this question

asked 9 hours ago

Andrew KeetonAndrew Keeton

4422820

add a comment | 

The Custom Document Well extension is only available for Visual Studio 2017. Is there a way to install it for Visual Studio 2019? Specifically, I only care about the vertical tabs feature.

As of the time of writing this question, the current version of Visual Studio 19 is 16.0.0 and the current version of the Custom Document Well extension is 15.06.

tabs extension visual-studio-2019

share|improve this question

asked 9 hours ago

Andrew KeetonAndrew Keeton

4422820

share|improve this question

asked 9 hours ago

Andrew KeetonAndrew Keeton

4422820

share|improve this question

asked 9 hours ago

Andrew KeetonAndrew Keeton

4422820

asked 9 hours ago

Andrew KeetonAndrew Keeton

4422820

asked 9 hours ago

Andrew KeetonAndrew Keeton

4422820

1 Answer
1

active

oldest

votes

3

1. Download CustomDocWell.vsix
   


2. Unzip the file, e.g. rename it to CustomDocWell.vsix.zip and extract the contents


3. Download the workaround extension.vsixmanifest (non-raw page)
   
   
   
   
   • The only change is that the upper bound of the InstallationTarget version has been removed
   
   
   
   


4. Replace the original extension.vsixmanifest with the workaround file


5. Download the workaround manifest.json (non-raw page)
   
   
   
   
   • The only change is the sha256 for extension.vsixmanifest has been recalculated
   
   
   
   


6. Replace the original manifest.json with the workaround file


7. 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 well as the other files and folders. The root of the zip file should not be a folder named CustomDocWell.
   
   
   
   


8. Rename to CustomDocWell.vsix
   


9. Run the VSIX file

If you don't get any errors you'll still get a warning when you open Visual Studio 2019:

The extension will still work; the Learn more link explains more.

The settings are under Tools > Options > Productivity Power Tools > Custom Document Well.

Errors

If you get an error it's likely that the sha256 of extension.vsixmanifest is incorrect. You can try calculating it on your own (PowerShell has Get-FileHash) and putting it in manifest.json.

share|improve this answer

answered 9 hours ago

Andrew KeetonAndrew Keeton

4422820

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  All this time, it was working but artificially blocked... WOW!
  
  – Yepeekai
  9 hours ago
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Not a deal breaker but: For color coded Regex, it works for the file name only, if you try to include folder structure in the expression, it is not detected ex: .*\Framework\.*.cs
  
  – Yepeekai
  9 hours ago
  

  
  
  
  

add a comment | 

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1421557%2fcan-i-install-the-custom-document-well-vertical-tabs-extension-for-visual-stud%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

3

1. Download CustomDocWell.vsix
   


2. Unzip the file, e.g. rename it to CustomDocWell.vsix.zip and extract the contents


3. Download the workaround extension.vsixmanifest (non-raw page)
   
   
   
   
   • The only change is that the upper bound of the InstallationTarget version has been removed
   
   
   
   


4. Replace the original extension.vsixmanifest with the workaround file


5. Download the workaround manifest.json (non-raw page)
   
   
   
   
   • The only change is the sha256 for extension.vsixmanifest has been recalculated
   
   
   
   


6. Replace the original manifest.json with the workaround file


7. 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 well as the other files and folders. The root of the zip file should not be a folder named CustomDocWell.
   
   
   
   


8. Rename to CustomDocWell.vsix
   


9. Run the VSIX file

If you don't get any errors you'll still get a warning when you open Visual Studio 2019:

The extension will still work; the Learn more link explains more.

The settings are under Tools > Options > Productivity Power Tools > Custom Document Well.

Errors

If you get an error it's likely that the sha256 of extension.vsixmanifest is incorrect. You can try calculating it on your own (PowerShell has Get-FileHash) and putting it in manifest.json.

share|improve this answer

answered 9 hours ago

Andrew KeetonAndrew Keeton

4422820

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  All this time, it was working but artificially blocked... WOW!
  
  – Yepeekai
  9 hours ago
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Not a deal breaker but: For color coded Regex, it works for the file name only, if you try to include folder structure in the expression, it is not detected ex: .*\Framework\.*.cs
  
  – Yepeekai
  9 hours ago
  

  
  
  
  

add a comment | 

3

1. Download CustomDocWell.vsix
   


2. Unzip the file, e.g. rename it to CustomDocWell.vsix.zip and extract the contents


3. Download the workaround extension.vsixmanifest (non-raw page)
   
   
   
   
   • The only change is that the upper bound of the InstallationTarget version has been removed
   
   
   
   


4. Replace the original extension.vsixmanifest with the workaround file


5. Download the workaround manifest.json (non-raw page)
   
   
   
   
   • The only change is the sha256 for extension.vsixmanifest has been recalculated
   
   
   
   


6. Replace the original manifest.json with the workaround file


7. 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 well as the other files and folders. The root of the zip file should not be a folder named CustomDocWell.
   
   
   
   


8. Rename to CustomDocWell.vsix
   


9. Run the VSIX file

If you don't get any errors you'll still get a warning when you open Visual Studio 2019:

The extension will still work; the Learn more link explains more.

The settings are under Tools > Options > Productivity Power Tools > Custom Document Well.

Errors

If you get an error it's likely that the sha256 of extension.vsixmanifest is incorrect. You can try calculating it on your own (PowerShell has Get-FileHash) and putting it in manifest.json.

share|improve this answer

answered 9 hours ago

Andrew KeetonAndrew Keeton

4422820

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  All this time, it was working but artificially blocked... WOW!
  
  – Yepeekai
  9 hours ago
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Not a deal breaker but: For color coded Regex, it works for the file name only, if you try to include folder structure in the expression, it is not detected ex: .*\Framework\.*.cs
  
  – Yepeekai
  9 hours ago
  

  
  
  
  

add a comment | 

1. Download CustomDocWell.vsix
   


2. Unzip the file, e.g. rename it to CustomDocWell.vsix.zip and extract the contents


3. Download the workaround extension.vsixmanifest (non-raw page)
   
   
   
   
   • The only change is that the upper bound of the InstallationTarget version has been removed
   
   
   
   


4. Replace the original extension.vsixmanifest with the workaround file


5. Download the workaround manifest.json (non-raw page)
   
   
   
   
   • The only change is the sha256 for extension.vsixmanifest has been recalculated
   
   
   
   


6. Replace the original manifest.json with the workaround file


7. 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 well as the other files and folders. The root of the zip file should not be a folder named CustomDocWell.
   
   
   
   


8. Rename to CustomDocWell.vsix
   


9. Run the VSIX file

If you don't get any errors you'll still get a warning when you open Visual Studio 2019:

The extension will still work; the Learn more link explains more.

The settings are under Tools > Options > Productivity Power Tools > Custom Document Well.

Errors

If you get an error it's likely that the sha256 of extension.vsixmanifest is incorrect. You can try calculating it on your own (PowerShell has Get-FileHash) and putting it in manifest.json.

share|improve this answer

answered 9 hours ago

Andrew KeetonAndrew Keeton

4422820

share|improve this answer

answered 9 hours ago

Andrew KeetonAndrew Keeton

4422820

answered 9 hours ago

Andrew KeetonAndrew Keeton

4422820

answered 9 hours ago

Andrew KeetonAndrew Keeton

4422820