Add tokens for Visual Studio 2026 support

[SamStrife]

I've added the tokens to make the theme display properly in Visual Studio 2026.

I don't think it's perfect but it is good enough to keep people happy before I can find the time to really fine tune the little bits that need finishing.

I've kept a lot of comments in the file, but feel free to remove those if you don't want them.

[sgoudham]

I'll hopefully try this out and review this PR soon.

The artifact is generated on build: https://github.com/catppuccin/visual-studio/actions/runs/20333838942/artifacts/4910534228 so it would be nice to get some feedback from others as well!

[niklashog]

Installed and visually it looks awesome.

Only issue so far is the new toasters when debugging in VS2026 are dark text on dark background.

[mszubart]

Installed and visually it looks awesome.

Only issue so far is the new toasters when debugging in VS2026 are dark text on dark background.

It really looks great.
By "toasters" did you mean a message like this?:

(theme used in picture: Mocca) Maybe the text is kind of too bright and the contrast is too low but really I'm nitpicking right now.

Frankly, I haven't found anything particularly bad or unusable with this package installed for a few days. However, I primarily work in C++ and C#.

[jtlehtinen]

Maybe @niklashog was referring to inline values and inline return values, which don't have enough contrast difference. Mocha theme in the attached image.

[niklashog]

Maybe @niklashog was referring to inline values and inline return values, which don't have enough contrast difference. Mocha theme in the attached image.

Yes. These are the fields I was refering to as toasters.

[SamStrife]

I'm increasingly frustrated that Microsoft seemingly haven't published the full list of new tokens required for a theme. Their migration guide boasts that they've reduced the numbers so much and how much easier is to theme things, but I cannot for the life of me find a comprehensive list of all the names no matter how much I look.

I'm having to cross reference other themes that have been ported to 2026 to find out what these are but I'm not sure what the name for these specific messages are.

As soon as I have a little time, I'll have a play and see about fixing these.

[jtlehtinen]

The inline values get their color values from the following color tokens:

<!-- Border -->
<Color Name="PageSideBarExpanderSeparator">
  <Background Type="CT_RAW" Source="FFFF0000" />
</Color>

<!-- Background -->
<Color Name="ComboBoxPopupBackgroundEnd">
  <Background Type="CT_RAW" Source="FF00FF00" />
</Color>

<!-- Foreground -->
<Color Name="ScrollBarThumbPressedBackground">
  <Background Type="CT_RAW" Source="FF0000FF" />
</Color>

Source: Created a theme with Visual Studio Color Theme Designer 2022 (which claims to support VS2026) and modified each color token to have a unique color value to identify what is what. Maybe there are new tokens and these are fallbacks since they seem contextually mismatched.

[djflan]

Not sure if this matters or not, but when I was working in this project, I pinned the VSIX Color Compiler to 17.0.31709.430. There is likely a newer version of this. This should be present in the csproj file:

<!-- Dan Flanigan's note: for whatever reason, any version of vsix color compiler other than 17.0.31709.430 results in build errors -->
    <PackageReference Include="Microsoft.VisualStudio.VsixColorCompiler">
      <Version>[17.0.31709.430]</Version>
    </PackageReference>

You can remove the package restriction by removing the square brackets around the version.

[SamStrife]

Hello all, sorry I've been quiet the past couple of weeks, I've been busy with work and had little time to look into this theme further 😔.

So I've had another look today and just pushed an update which updates the status bar at the bottom and the backgrounds in the controls at the top of the editor to no longer use the default light/dark theme and instead use the Catppuccin colors.

There are 2 major things I still am unable to find the correct token names for:

• The inline hints mentioned above. I've tried adding the tokens @jtlehtinen referenced but cannot seem to get them to work.
• The diagnostic panel still uses the default theme color, rather than the Catppuccin "Mantle" color that I want it to.

I have scoured the internet to try and find answers but am not able to find any. I am still incredibly frustrated with Microsoft that they've updated all these tokens and put no documentation out there explaining what they actually are.

I've looked at other themes out there and, interestingly, some of the bigger ones (e.g. One Dark Pro 2026) also appear to suffer from this exact same problem.

I'm going to try and find someone to reach out to; be it a member of the Visual Studio team or an author of a theme that doesn't seem to suffer from this problem. That's about all I can do at this moment in time, I'm afraid.

[vakisddot]

@SamStrife goated, thanks G 🙌

[pikausp]

@SamStrife hey Sam, have you had any success here? Your work is very much appreciated

[SamStrife]

@SamStrife hey Sam, have you had any success here? Your work is very much appreciated

I have not had any success, unfortunately. I've just opened this ticket on the Visual Studio Developer Community Forums so hopefully someone can provide an answer for me

[jtlehtinen]

The color keys that I mentioned earlier work at least on my installation. I have been rocking it since then and now on Visual Studio 18.4.1. No problems.

[SamStrife]

The color keys that I mentioned earlier work at least on my installation. I have been rocking it since then and now on Visual Studio 18.4.1. No problems.

OK, I need to apologise, I could have sworn I tried these the first time you mentioned them and they didn't work but I've tried again and things are looking as they should. I do maintain they are very, very silly names for those colours though 😅

Pushing the changes now and then I'm pretty sure this can be folded into the main branch for all to benefit from.

@sgoudham it's up to you now to make sure you're happy and then merge into the main branch

[tayopi]

Nice work @SamStrife! Your work is very much apprecieated.

Help us @sgoudham! You're our only hope!

[J-eno]

Just learned of Catppuccin 30 minutes ago, but unfortunately ran into this issue in Visual Studio 2026.

@SamStrife this change works like a charm, thanks!