Bring VS Code Themes To Visual Studio 2022!
We want developers to have the flexibility to personalize their Visual Studio IDE to fit their individual preferences, and themes are an important component for achieving this goal. We’ve been testing out a Theme Converter that helps theme authors convert their Visual Studio Code themes to work in VS. Last week, we shared a collection of new community themes created using this tool. Today, we’d like to share with you a bit more detail about this converter tool, and how you can convert your own theme as well!
Using this tool, you can now convert any VS Code theme for use in Visual Studio 2022! This gives you access to a new range of themes inside the Visual Studio family, and if you use both Visual Studio and Visual Studio Code, you now have the extra flexibility to use the same theme for both platforms.
If you’re a VS Code theme author, you can now easily share your theme with a new range of users by packaging and uploading your theme to the Marketplace as well!
Using the Theme Converter tool
The Theme Converter tool converts color tokens from a VS Code theme and applies them to Visual Studio. We’ve made efforts to ensure that even theme elements that are undefined will still be usable, through a fallback logic, which improves the appearance of the theme. Converted themes are most compatible with Visual Studio 2022 Preview 3 and above.
The converted themes look their best with C# and C++ repos, and other languages may use the fallback colors if they are not available in the theme.
Try the Theme Converter now!
You can give the theme converter a try by downloading from the GithHub repository. It’s a tool that converts all the tokens you’ve specified. You now have access to a wide range of themes in the Visual Studio family and can match your Visual Studio and Visual Studio Code themes.
If there are elements that don’t work well, you are welcome to share feedback with us by creating an issue in the GitHub repo or create a Pull Request with the changes you’d like to see. Please let us know what you think!
>>> Read the Full Story at Visual Studio Blog