microsoft / theme-converter-for-vs

CLI tool that allows you to convert your VS Code color theme to a VS 2022 color theme.

Theme Converter for Visual Studio

Theme Converter is a CLI tool which allows you to convert your VS Code theme to work in Visual Studio. It's a simple tool that maps the colors of a theme to Visual Studio. Themes can be packaged into VSIXs and uploaded to the Marketplace so that more people can use your theme! This allows developers who use Visual Studio, or use both VS Code and Visual Studio, to quickly get access to a wide range of fun and interesting themes!

Here's a quick overview on how the Theme Converter works:

Our community of authors have already converted a handful of VS Code themes to work in Visual Studio. Feel free to take a look here.

Prerequisites

1. VS Code
2. Visual Studio 2022
3. The following workloads can be installed via the Visual Studio installer:
   • .NET Desktop development
   • Visual Studio extension development

Instructions

Using the tool

1. Open command line in Admin mode.
2. Clone the repo
3. Go to <your_clone_path>\ThemeConverter\ThemeConverter and build the converter project with dotnet build ThemeConverter.csproj.
4. Go to <your_clone_path>\ThemeConverter\ThemeConverter\bin\Debug\net6.0.
5. Get the theme file with steps described in section Getting a theme's json file
6. Run ThemeConverter.exe -h to see the usage of the tool and use the tool according to your needs.

   • If you want to convert a theme and patch it to a target VS:

     • Run ThemeConverter.exe -i <path_to_theme_json> -t <target_vs_installation_path>
     • Example: ThemeConverter.exe -i "C:\myTheme\TestTheme.json" -t "C:\Program Files\Microsoft Visual Studio\2022\Community". This command will convert the TestTheme, patch the generated json to the target VS and launch the VS with the converted theme.
     • Note: the VS installation path can be found in your VS installer (the location field on the modify page).
     • Now you can see the your converted theme under Tools -> Themes! Enjoy!

   • If you just want to convert a theme and get the generated pkgdef:

     • Run ThemeConverter.exe -i <path_to_theme_json> -o <output_path>
     • Example: ThemeConverter.exe -i "C:\myTheme\TestTheme.json" -o "C:\myTheme\results". This command will convert the theme and the generated pkgdef will be C:\myTheme\results\TestTheme.pkgdef.

Getting a theme's json file

1. Open VS Code.
2. Install the desired color theme and switch to this theme in VS Code. Please note that this tool will not convert icon themes.
3. “Ctrl + Shift + P” and run “Developer: Generate Color Theme from current settings.”
4. In the generated JSON, uncomment all code. When you uncomment, please be careful about missing commas! Make sure the JSON is valid.
5. Save this as a “JSON” file for the conversion, using the theme's name as the file name. Please ensure that the file’s extension is .json. (The file shouldn’t be saved as a JSONC file.)
6. Note: Because some part of VS UI does not support customized alpha channel, we recommend reducing the usage of not fully opaque colors for better conversion result.

Creating a VSIX for the new theme

This section describes how you can create a VSIX with the converted theme for publishing and sharing.

1. In VS 2022, create a new "Empty VSIX Project."
2. Select the project node and open the "Add existing Item" window: Use "Shift + Alt + A" or right-click on the project node, select Add > Existing Item.
3. Set filter to All Files (.) and select the converted .pkgdef file(s) that you want to include in this VSIX.
4. Select the newly added pkgdef file in the Solution Explorer and open the Properties window. If the Properties window is not already open, navigate to the View menu at the top > Properties Window.

6. Set Copy to Output Directory to Copy always.
7. Set Include in VSIX to true.
8. Open the source.extension.vsixmanifest file, then select Assets, select New.
9. Set Type to Microsoft.VisualStudio.VsPackage, and Source to File on filesystem.
10. Select Browse and select the .pkgdef you added. Select OK.
11. Edit other fields in the vsixmanifest as desired (author, version, company, etc).
12. Build solution and you now have a vsix in the output folder! Your new theme is most compatible with Visual Studio 2022.

Removing a converted theme from VS

1. Open target VS and switch to some theme that will not be deleted (like Blue theme).
2. Go to <vs_install_dir>\Common7\IDE\CommonExtensions\Platform. e.g: C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\CommonExtensions\Platform and delete the pkgdef of the theme that the you want to remove (The name of the pkgdef will match the name of the theme).
3. Open Developer Command Prompt of the target VS and run devenv /updateConfiguration.
4. Launch VS again, and the themes should now be removed.

Support

How to file issues and get help

This project uses GitHub Issues to track bugs and feature requests. Please search the existing issues before filing new issues to avoid duplicates. For new issues, file your bug or feature request as a new Issue.

Microsoft Support Policy

Support for this project is limited to the resources listed above.

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.

theme-converter-for-vs's Issues

The icon is not clear when mouse hovering in Watch tab

Describe the bug
The icon is not clear when mouse hovering in Watch tab

Screenshots

To Reproduce
1.Create a console project
2.Set a breakpoint on Program.cs file
3.Debug this project
4.In debug mode, observe different debug windows

Environment (please complete the following information):

• Impacted Themes: Tomorrow Night Blue

⬆Close icon blink with mouse hover on NPD

Describe the bug
Close icon blink with mouse hover on NPD, making it hard to close.

🎈 Things that didnt work out on converting Deepdark Material Theme

Describe the bug
1- File Explorer colors are not the same
2- Almost everything(namespaces, variables, string values, comments) completely different color except the background
3- Current line highlighting is not the same

Screenshots
Visual Studio Code:

Visual Studio 2020 Preview 3.1

Test Explorer Wizard search box hover border not visible

The border is not visible in Test Explorer Wizard when hovering over the search box

1. Launch VS and create a new Unit test project
2. Open Test Explorer
3. Run all test
4. Hovering over the search box
5. Observe the search box border
   

Noted on themes: Eva Light and Eva Dark

🛑⬆️Breakpoints column headers unreadable

Name Labels font color are not clear in Breakpoints window

1.Create a console project
2.Set a breakpoint on Program.cs file
3.Debug this project
4.In debug mode, observe different debug windows

Noted on themes: Palenight, Shades of Purple, Winter is Coming(Dark Black - No Italics), Winter is Coming(Dark Blue - No Italics)

Task Center notification background is transparent

Task center notification is transparent

marketplace json was used: https://marketplace.visualstudio.com/items?itemName=nopjmp.fairyfloss

Noted on themes: fairyfloss

Those icons are not clear when mouse hovering in Test Explorer

Describe the bug
Those icons are not clear when mouse hovering in Test Explorer

Screenshots

To Reproduce
1.Create a new Unit Test Project
2.Click Test | Test Explorer
3.Observe the UI style in Test Explorer

Environment (please complete the following information):

• Impacted Themes: Abyss, Dark+, Kimbie Dark, Light+, Monokai Dimmed, Monokai, Quiet Light, Red, Solarized Dark, Solarized Light and Tomorrow Night Blue

Build warnings regarding references

VS 2022 Preview 3
.NET Desktop workload installed

Rebuild started...
Restored C:\Users\huvalo\source\repos\theme-converter-for-vs\ThemeConverter\ThemeConverter\ThemeConverter.csproj (in 10 ms).
1>------ Rebuild All started: Project: ThemeConverter, Configuration: Debug Any CPU ------
2>------ Rebuild All started: Project: ThemeTests, Configuration: Debug Any CPU ------
Restored C:\Users\huvalo\source\repos\theme-converter-for-vs\ThemeConverter\ThemeTests\ThemeTests.csproj (in 323 ms).
2>You are using a preview version of .NET. See: https://aka.ms/dotnet-core-preview
1>You are using a preview version of .NET. See: https://aka.ms/dotnet-core-preview
1>C:\Program Files\Microsoft Visual Studio\2022\Preview\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(2303,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "System". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.
1>C:\Program Files\Microsoft Visual Studio\2022\Preview\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(2303,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "System.Collections.ObjectModel". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.
1>C:\Program Files\Microsoft Visual Studio\2022\Preview\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(2303,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "System.Core". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.
1>C:\Program Files\Microsoft Visual Studio\2022\Preview\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(2303,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "System.Data". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.
1>C:\Program Files\Microsoft Visual Studio\2022\Preview\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(2303,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "System.Drawing". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.
1>C:\Program Files\Microsoft Visual Studio\2022\Preview\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(2303,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "System.IO". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.
1>C:\Program Files\Microsoft Visual Studio\2022\Preview\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(2303,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "System.Windows". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.
1>C:\Program Files\Microsoft Visual Studio\2022\Preview\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(2303,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "System.Windows.Media". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.
1>C:\Program Files\Microsoft Visual Studio\2022\Preview\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(2303,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "System.Xml". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.
1>C:\Program Files\Microsoft Visual Studio\2022\Preview\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(2303,5): warning MSB3243: No way to resolve conflict between "System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" and "System". Choosing "System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" arbitrarily.
1>C:\Program Files\Microsoft Visual Studio\2022\Preview\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(2303,5): warning MSB3243: No way to resolve conflict between "System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" and "System.Core". Choosing "System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" arbitrarily.
1>C:\Program Files\Microsoft Visual Studio\2022\Preview\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(2303,5): warning MSB3243: No way to resolve conflict between "System.Data, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" and "System.Data". Choosing "System.Data, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" arbitrarily.
1>C:\Program Files\Microsoft Visual Studio\2022\Preview\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(2303,5): warning MSB3243: No way to resolve conflict between "System.Drawing, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" and "System.Drawing". Choosing "System.Drawing, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" arbitrarily.
1>C:\Program Files\Microsoft Visual Studio\2022\Preview\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(2303,5): warning MSB3243: No way to resolve conflict between "System.IO, Version=5.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" and "System.IO". Choosing "System.IO, Version=5.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" arbitrarily.
1>C:\Program Files\Microsoft Visual Studio\2022\Preview\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(2303,5): warning MSB3243: No way to resolve conflict between "System.Windows, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" and "System.Windows". Choosing "System.Windows, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" arbitrarily.
1>C:\Program Files\Microsoft Visual Studio\2022\Preview\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(2303,5): warning MSB3243: No way to resolve conflict between "System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" and "System.Xml". Choosing "System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" arbitrarily.
1>ThemeConverter -> C:\Users\huvalo\source\repos\theme-converter-for-vs\ThemeConverter\ThemeConverter\bin\Debug\net5.0\ThemeConverter.dll
1>Done building project "ThemeConverter.csproj".
2>ThemeTests -> C:\Users\huvalo\source\repos\theme-converter-for-vs\ThemeConverter\ThemeTests\bin\Debug\net5.0-windows\ThemeTests.dll
========== Rebuild All: 2 succeeded, 0 failed, 0 skipped ==========

⬇️VB files font colors

Cannot clearly distinguish font colors in vb files. Colors do not match expected from VSC.

1. Launch VS and download the demo from https://github.com/kai-oswald/NightOwl-VS-Theme
2. Click "File" -> Open | Folder，selected the demo
3. Open the vb.vb file and observed that the font colors in Dev17's editor is not clearly distinguishable
   

Noted on themes: GitHub Light Default, Winter is Coming(Light - No Italics)

🛑⬇️Inconsistent color for "**" in MD file

Inconsistent color of "**" in md file

The classification tags for the "**" are different - front: operator, end: None

1. Launch VS and download the demo from https://github.com/kai-oswald/NightOwl-VS-Theme
2. Click "File" -> Open | Folder，selected the demo
3. Open the md.md file and observed that the color of "**" in Dev17's editor
   is not consistent

Noted on themes: All except for "Atom One Light", "One Dark Pro", "Panda"

"Enable/Delete all breakpoints matching current search criteria" icons are not clear when mouse hovering in Breakpoints tab

Describe the bug
"Enable/Delete all breakpoints matching current search criteria" icons are not clear when mouse hovering in Breakpoints tab

Screenshots

To Reproduce
Steps to reproduce the behavior:
1.Create a console project
2.Set a breakpoint on Program.cs file
3.Debug this project
4.In debug mode, observe different debug windows

Environment (please complete the following information):

• Impacted Themes: Abyss, Dark+, Kimbie Dark, Light+, Monokai Dimmed, Monokai, Quiet Light, Red, Solarized Dark, Solarized Light and Tomorrow Night Blue

Breakpoint window column labels unreadable when selected

Font colors are not clear when hitting with the mouse in the Breakpoints window

1. Launch VS and create a new console project
2. Open Program.cs and set a breakpoint
3. Start debugging
4. On Debug mode, observe the font color
   

Noted on themes: Vue

Improve command line interface

Hover on icons in ribbon bar is hard to see in solution explorer

Describe the bug
Hover on icons is hard to see in ribbon bar in solution explorer

Screenshots

To Reproduce
Steps to reproduce the behavior:
1.Launch VS and create a project
2. Go to Solution explorer
3. Hover on icons in ribbon bar
4.Observe

Environment (please complete the following information):

• Impacted Themes: Abyss, Dark+, Light+, Monokai, Solarized Dark, Solarized Light, Tomorrow Night Blue

Allow not passing in the path to VS

If path to VS is not specified, we won't attempt to copy to it and launch VS.

Alpha is not supported

Describe the bug
Alpha is not supported

Screenshots

To Reproduce
Convert any theme from Bearded Theme

Expected behavior
See VSCode screenshot

Environment (please complete the following information):

• Converter version: v0.0.2
• VS version: 17.0.0 Preview 3.1
• Theme used: Bearded Theme

Additional context
In order to manage all the variations of my themes, I use the transparency, that allows me to define a color, and that it works in all. I've used this : RGB Alpha with HEX](https://code.visualstudio.com/api/references/theme-color#color-formats)

Those icons are not clear when mouse hovering in Exception Settings tab

Describe the bug
Those icons are not clear when mouse hovering in Exception Settings tab

Screenshots

To Reproduce
1.Create a console project
2.Set a breakpoint on Program.cs file
3.Debug this project
4.In debug mode, observe different debug windows

Environment (please complete the following information):

• Impacted Themes: Abyss, Dark+, Kimbie Dark, Light+, Monokai Dimmed, Monokai, Quiet Light, Red, Solarized Dark, Solarized Light and Tomorrow Night Blue

Hover on Medium icons/small icons is hard to see in new item dialogue

Describe the bug
Hover on Medium icons/small icons is hard to see in new item dialogue

Screenshots

To Reproduce
Steps to reproduce the behavior:
1.Launch VS and create a project
2. Add a new item
3. Hover on Medium icons/small icons in new item dialogue
4.Observe

Environment (please complete the following information):

• Impacted Themes: Abyss, Dark+, Light+, Monokai, Solarized Dark, Solarized Light, Tomorrow Night Blue

Solution explorer search selected text is not readable

Describe the bug
Solution explorer search selected text is not readable for Eva light

Screenshots

Environment (please complete the following information):

• Converter version: v0.0.2
• VS version: 17.0.0 Preview 3
• Theme used: Eva light

Search bar is no border in solution explorer

Describe the bug
Search bar is no border in solution explorer

Screenshots

To Reproduce
Steps to reproduce the behavior:
1.Launch VS and create a project
2. Go to Solution explorer
3. Observe search bar

Environment (please complete the following information):

• Impacted Themes: Dark+

🛑Diagnostics radio button not themed

Diagnostics radio button

Noted on themes: Nord

"Clear All" and "Toggle Word Wrap" icons are not clear in Output tab

Describe the bug
"Clear All" and "Toggle Word Wrap" icons are not clear in Output tab

Screenshots

To Reproduce
1.Create a console project
2.Set a breakpoint on Program.cs file
3.Debug this project
4.In debug mode, observe different debug windows

Environment (please complete the following information):

• Impacted Themes: Abyss, Dark+, Kimbie Dark, Light+, Monokai Dimmed, Monokai, Quiet Light, Red, Solarized Dark, Solarized Light and Tomorrow Night Blue

The number font color is wrong in Text Explorer

Describe the bug
The number font color is wrong in Text Explorer

Screenshots

To Reproduce
1.Create a new Unit Test Project
2.Click Test | Test Explorer
3.Observe the UI style in Test Explorer

Environment (please complete the following information):

• Impacted Themes: Light+

Add an option to supply token mapping as an input

Suggestion

Current theme mappings sometimes don't make sense and are really hard to predict to tweak the theme. I basically modify the source JSON, then regenerate the theme, then try to work out what was affected, and then try to find a way to make things work.

For example in this screenshot titleBar.activeBackground is set to red and as you can see it affects many things. Some of which I don't want it to affect and some which it doesn't affect I want it to affect.

What could be done?
The ideal scenario for me would be to not modify the source JSON and instead to modify the mapping and supply it as an input. That way I could fine-tune the output and get something that would feel natural to VS and still true to the theme.

Environment (please complete the following information):

• Converter version: v0.0.2
• VS version: 17.0.0 Preview 3.1
• Theme used: ayu

Impact
This could tremendously speed up things and allow for things that are not possible with the auto conversion.

Fatal error running VsixColorCompiler.exe

There's an issue with the color compiler that is included in VS 2022 Preview 3 (it has already been fixed for upcoming Preview 4).

If you see this error:

Microsoft(R) Visual Studio(R) Vsix Color Compiler version 16.0.0.4.
(C) Microsoft Corporation. All rights reserved.
Could not load file or assembly 'Microsoft.VisualStudio.PkgDef, Version=16.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

System.ApplicationException: Fatal error running VsixColorCompiler.exe
   at ThemeConverter.Program.CompileTheme(String deployInstall) in C:\Users\huvalo\source\repos\theme-converter-for-vs\ThemeConverter\ThemeConverter\Program.cs:line 134
   at ThemeConverter.Program.Convert(String filePath, String pkgdefOutputPath, String deployInstall) in C:\Users\huvalo\source\repos\theme-converter-for-vs\ThemeConverter\ThemeConverter\Program.cs:line 107
   at ThemeConverter.Program.Main(String[] args) in C:\Users\huvalo\source\repos\theme-converter-for-vs\ThemeConverter\ThemeConverter\Program.cs:line 69

WORKAROUND

Open this file in a text editor like notepad as administrator

<vsinstalldir>\VSSDK\VisualStudioIntegration\Tools\Bin\VsixColorCompiler.exe.config

Change this line

<bindingRedirect oldVersion="2.0.0.0-99.99.99.99" newVersion="16.0.0.0" />

to

<bindingRedirect oldVersion="2.0.0.0-99.99.99.99" newVersion="17.0.0.0" />

The font is not clear when mouse focusing on search box in Watch tab

Describe the bug
The font is not clear when mouse focusing on search box in Watch tab

Screenshots

To Reproduce
1.Create a console project
2.Set a breakpoint on Program.cs file
3.Debug this project
4.In debug mode, observe different debug windows

Environment (please complete the following information):

• Impacted Themes: Tomorrow Night Blue

Changing themes takes 5 seconds

Changing themes through top-level theme menu or Tools Options takes up to 5 seconds and changes random dialog boxes first. Ideally, when the user changes themes, they would wait only a few moments, and the user would see a loading screen when the themes change. This would improve the experience of changing themes.

HTML/CSS/SCSS is not supported

Describe the bug
HTML/CSS/SCSS syntax colors aren't translated from VS Code theme.

Screenshots
Please include a screenshot of the bug.

To Reproduce
Convert the theme One Dark Pro.

Search control dropdown selected foreground is not readable

Describe the bug
search dropdown selected foreground not readable
Screenshots

Environment (please complete the following information):

• VS version: 17.0.0 Preview 3
• Theme used: Winter is Coming

Convertion of a JSON theme file failed, with a "file cannot be found" error.

Describe the bug
Convertion of a JSON theme file failed, with a "file cannot be found" error.

Screenshots

(Same error with PowerShell on Windows Terminal, or Developer PowerShell for VS 2022 Preview launched in administrator, or directly system PowerShell launched in administrator)

To Reproduce
Steps to reproduce the behavior:

1. Extract JSON theme file with the suggested method (in my case, Bearded Theme Monokai Metallian)
2. Follow the steps on project's README

Environment (please complete the following information):

• Converter version: v0.0.2
• VS version: 17.0.0 Preview 3.1
• Theme used: Bearded Theme

Additional context
The file :

The VS install folder :

I tried to :

• Change file name (remove all the characters except a-z)
• Change terminal (same error in bash)
• Change file location (in the desktop, directly in bin\Debug\netcoreapp3.1, in Documents)

If i use a folder instead of directly JSON file :

So i created myself a folder ImportedThemes in bin\Debug\netcoreapp3.1 and it say :

I move my theme.json file in the new ImportedThemes folder and :

(I guess the last part of the screenshots is not relevant, it looks more like a desperate trick, but hopefully it can be useful, we never know)

Solution explorer title is using a different color

Describe the bug
The "solution explorer" title appears pale purple instead of the white that the maintainers have chosen.

Screenshots

To Reproduce
Convert Dracula Official theme

Expected behavior
The "Solution Explorer" title should appear white.

Environment (please complete the following information):

• VS version: 17.0.0 Preview 4.0
• Theme used: Dracula Official

Line numbers are the wrong color

Describe the bug
For the Dracula theme, the line numbers appear blue instead of purple.

Screenshots

To Reproduce
Convert the Dracula Official theme.

Environment (please complete the following information):

• VS version: Version 17.0.0 Preview 4.0
• Theme used: Dracula Official

Status bar foreground color is wrong

Describe the bug
Status bar foreground color is wrong.

Screenshots

To Reproduce
Steps to reproduce the behavior:
Open a repo under source control and observe the status bar.

Environment (please complete the following information):

• Converter version: [e.g. v0.0.2]
• VS version: [e.g. 16.10.2, 17.0.0 Preview 3]
• Theme used: One Dark Pro and others

Additional context
Add any other context about the problem here.

The unit test fonts are not clear in Test Explorer

Describe the bug
The unit test fonts are not clear in Test Explorer

Screenshots

To Reproduce
1.Create a new Unit Test Project
2.Click Test | Test Explorer
3.Observe the UI style in Test Explorer

Environment (please complete the following information):

• Impacted Themes: Abyss, Dark+, Kimbie Dark, Light+, Monokai Dimmed, Monokai, Quiet Light, Red, Solarized Dark, Solarized Light and Tomorrow Night Blue

Selection as wrong color

Describe the bug
Selection as wrong color

Screenshots

To Reproduce
Convert any theme from Bearded Theme

Expected behavior
White with alpha (See VSCode screenshot)

Environment (please complete the following information):

• Converter version: v0.0.2
• VS version: 17.0.0 Preview 3.1
• Theme used: Bearded Theme

Additional context
Probably related to my previous issue : Apha issue

Active tool window title unreadable for "Quiet Light"

Describe the bug
Active window title, "Output", is white on light grey, practically invisible for "Quiet Light" VS Code theme.

Screenshots

⬇️Debug mode tool windows titles unreadable

The font color is not clear in Debug mode

Might be by design

1. Launch VS and create a new console project
2. Open Program.cs and set a breakpoint
3. Start debugging
4. On Debug mode, observe the font color

Noted on themes: Eva Light, Eva Dark and Vue

Scrollbars appear black

Describe the bug
In Eva Dark, the scrollbars appear black.

Screenshots

To Reproduce
Steps to reproduce the behavior:
Switch to the "Eva Dark" theme.

Expected behavior
The scrollbars should be a lighter grey to suit the theme.

Environment (please complete the following information):

• Converter version: n/a - used theme pack
• VS version: 17.0 Preview 4
• Theme used: Eva Dark

Additional context
Add any other context about the problem here.
Vue is also another theme that has this issue.

Dump view column header hover color is incorrect

Hover state in grid headers in dump view are rendered incorrectly

1. Open a memory dump
2. Debug managed memory
3. Navigate to some type
4. Hover the "Instance" column header in the table

Noted on themes: Ayu Mirage Bordered

User panel as wrong colors

Describe the bug
User panel as wrong colors

Screenshots
Visual Studio

Visual Studio Code

To Reproduce
Convert any theme from Bearded Theme

Expected behavior
See VSCode screenshot

Environment:

• Converter version: v0.0.2
• VS version: 17.0.0 Preview 3.1
• Theme used: Bearded Theme

Converted colors does not match

Describe the bug
Converted colors does not match, there is one less unit in the reds.

Screenshots

To Reproduce
Convert Bearded Theme Monokai Metallian from Bearded Theme

Expected behavior
See VSCode screenshot

Environment (please complete the following information):

• Converter version: v0.0.2
• VS version: 17.0.0 Preview 3.1
• Theme used: Bearded Theme Monokai Metallian

⬇️Locals window item row selected foreground color unreadable

Font color in Locals window is not clear

Is this by design? Not sure if the low contrast indicates selected state.

1.Create a console project
2.Set a breakpoint on Program.cs file
3.Debug this project
4.In debug mode, observe different debug windows

Noted on themes: Nord, Shades of Purple, Ayu Dark, Ayu Dark Bordered

Wrong borders color for tabs

Describe the bug
Wrong borders color for tabs

Screenshots
Visual Studio

Visual Studio Code

To Reproduce
Convert any theme from Bearded Theme

Expected behavior
See VSCode screenshot

Environment (please complete the following information):

• Converter version: v0.0.2
• VS version: 17.0.0 Preview 3.1
• Theme used: Bearded Theme

Additional context
It is very likely that this is due to the alpha format and that the conversion chooses the default top and bottom colors.
Probably related to my previous issue : Apha issue

🛑⬆️Breakpoint selected item foreground unreadable

Breakpoints and Program.cs fonts are not clear

1.Create a console project
2.Set a breakpoint on Program.cs file
3.Debug this project
4.In debug mode, observe different debug windows

Noted on themes: Atom One Light, GitHub Light, Nord

Sidebar links are low contrast

Describe the bug
The sidebar links on the Dracula theme appear pale purple instead of white, which would be more readable as it is an important link. The maintainers have chosen White as a readable accent color on a dark background.

Screenshots

To Reproduce
Convert the Dracula theme.

Expected behavior
The links should be white.

Environment (please complete the following information):

• VS version: Version 17.0.0 Preview 4.0
• Theme used: Dracula Official

"Show only pinned members" and "Find Next" icons are not clear when mouse hovering in Watch tab

Describe the bug
"Show only pinned members" and "Find Next" icons are not clear when mouse hovering in Watch tab

Screenshots

To Reproduce
1.Create a console project
2.Set a breakpoint on Program.cs file
3.Debug this project
4.In debug mode, observe different debug windows

Environment (please complete the following information):

• Impacted Themes: Abyss, Dark+, Kimbie Dark, Light+, Monokai Dimmed, Monokai, Quiet Light, Red, Solarized Dark, Solarized Light and Tomorrow Night Blue

Color is no differentiation between folder paths and file names

Describe the bug
Color is no differentiation between folder paths and file names

Screenshots
Please include a screenshot of the bug.

To Reproduce
Steps to reproduce the behavior:
1.Launch VS and create a asp project
2.Set tabs to left or right
3.Open some files and observe tabs

Environment (please complete the following information):

• Impacted Themes: Abyss, Dark+, Kimbie Dark, Light+, Monokai Dimmed, Monokai, Quiet Light, Red, Solarized Dark, Solarized Light, Tomorrow Night Blue

Search bar is no border in new item dialogue

Describe the bug
Search bar is no border in new item dialogue

Screenshots

To Reproduce
Steps to reproduce the behavior:
1.Launch VS and create a project
2. Add a new item under project
3. Observe search bar in new item dialogue

Environment (please complete the following information):

• Impacted Themes: Dark+

Two buttons are unviewable on Dark theme

Describe the bug
The Error List "Clear All Filters" and the Properties window "Categorized" button do not appear viewable a Dark theme.

Screenshots

To Reproduce
Convert One Dark Pro using latest conversion tool with integration.

Inconsistencies in tool window caption

These screenshots show the differences between active and inactive tool windows.

Inconsistencies compared to dark/light themes:

• the dithering texture is only visible when inactive, it should be in both active and inactive
• the pin buttons on the right are brighter when inactive than when active, that's the opposite of what would be expected