Skip to content

Releases

Fili.VSCode2026 1.0.1

Choose a tag to compare

@github-actions github-actions released this 09 Nov 20:17
  • The themes now apply in VS Code's Agents window too. That window runs only extensions that declare
    support for it, and this one has code (the layout commands), so it was left out, and every theme,
    icon theme and product icon theme with it. The one-time offer of the layout is not shown there.
  • Covers VS Code 1.145. None of its ten new colours needs a value: the tab divider follows the tab
    border, which is already the tab well's colour (Visual Studio draws no line between tabs), the
    confetti colours follow themed keys, and the rest are VS Code's own brand colours.

Fili.VSCode2026 1.0.0

Choose a tag to compare

@github-actions github-actions released this 12 Oct 15:25

The first stable release: every theme Visual Studio 2026 ships, measured from Visual Studio itself
and verified against it in VS Code.

  • Avalonia AXAML takes Visual Studio's colours, measured from Visual Studio 2026 with the Avalonia extension: elements and the owner of an attached property (Grid in Grid.Row) in the type colour, attributes keyword blue, xmlns, x: directives, namespace prefixes and using: namespaces in the preprocessor grey, markup extensions such as {Binding} and {x:Null} in the method colour, and values, delimiters and entities plain. Both Extra Contrast editors follow Visual Studio's, and High Contrast stays monochrome. It needs Avalonia for VSCode: this extension now injects a small grammar into its AXAML grammar to tell those parts apart, with scopes other colour themes do not colour differently. Without it, .axaml stays XML.

Fili.VSCode2026 0.11.0

Choose a tag to compare

@github-actions github-actions released this 12 Oct 10:55
  • C and C++ take Visual Studio's C++ colours, from its own classifier: macros purple (#BEB7FF in Dark), parameters grey, member fields #DADADA, namespaces, globals and static members #C8C8C8, enumerators #B8D7A3, enums, structs and template parameters in the type colour, and all punctuation in the operator grey. String quotes and <…> around an include have their own delimiter colour, and an overloaded operator such as << is coloured in Light. With the C/C++ extension installed its semantic tokens complete the picture: macro uses, globals against locals, and overloaded operators.
  • F#: match, with and -> are keyword blue rather than control-flow purple, as in Visual Studio; =, |> and brackets are not coloured; modules are type-coloured and open System is no longer bold. With Ionide installed, union cases take the enum-member colour, int, decimal and DateTime the struct colour, a let mutable value is gold (#FFD21C) and printf format specifiers such as %s teal (#4EDCB0), all as Visual Studio draws them.
  • Python follows Visual Studio's colours: every keyword is blue, with no purple control flow; and, or, not, is and @ are operators; class and function names where they are defined are type-coloured; parameters, modules and f-string braces are plain, and escapes take the
    string colour. With Pylance, references to classes and functions stay plain, decorators and builtin types are type-coloured, and __init__, None and sum are keyword blue.
  • Extra Contrast follows Visual Studio's C++ overrides: types, parameters, overloaded operators, escapes and preprocessor directives (which C++ reads from a different item than C#, so #include is brighter there while C#'s #region is not). As in Visual Studio, new and delete, F#'s format specifiers and let mutable values keep their base colours under Extra Contrast. High Contrast stays monochrome.
  • Brackets: Apply Visual Studio 2026 Layout now also turns off VS Code's bracket-pair colouring. Visual Studio 2026 ships its own switched off, so brackets take the colour of the code around them; the theme keeps Visual Studio's three brace-pair colours for anyone who turns it back on. Remove Visual Studio 2026 Layout restores it.

Fili.VSCode2026 0.10.0

Choose a tag to compare

@github-actions github-actions released this 08 Oct 00:53
  • XML takes Visual Studio's colours, and so do MSBuild files (.csproj, .props) and XAML, which Visual Studio draws as XML. Attribute quotes and = are delimiter-coloured, and comment and CDATA delimiters too. CDATA content has its own colour (#E9D585 in Dark). Text between tags is Visual Studio's #C8C8C8 in Dark. Entity references such as &amp; take the attribute colour, and DOCTYPE declarations follow suit.
  • YAML takes Visual Studio's colours: keys, numbers and anchor names are keyword blue, while aliases and the | / > block markers stay plain.
  • Dockerfiles were measured too and already matched.

Fili.VSCode2026 0.9.0

Choose a tag to compare

@github-actions github-actions released this 07 Oct 21:49
  • JavaScript and TypeScript take Visual Studio's colours, measured from Visual Studio 2026 at a large font size. Unlike C#, Visual Studio colours every identifier that is not a type or a function as a variable, so properties, enum members and constants are now variable-coloured. Interfaces, enums, type parameters, primitive types such as string, and this used as a type take the type colour. A regular expression is one string colour, quantifiers and classes included. Template ${ } and JSDoc tags such as @param are keyword blue. JSDoc text is plain comment green, and new Error() colours Error as a type. These rules apply only to JavaScript and TypeScript; C# keeps its plain members.
  • Light's diff lines are #EBF1DD / #FFCCCC, the colours Visual Studio draws. The values in 0.7.0 were sampled on the line holding the caret, under the current-line highlight. Dark's diff lines were already right: they are drawn exactly as their tokens.
  • The README's theme grid shows all sixteen themes.

Fili.VSCode2026 0.8.0

Choose a tag to compare

@github-actions github-actions released this 05 Oct 19:33
  • Fili.VSCode2026 Dark (High Contrast), Visual Studio 2026's High Contrast theme under Windows' Aquatic contrast theme, as a VS Code high-contrast theme. Visual Studio's High Contrast names Windows system colours rather than colours; they are resolved through Aquatic, and the highlights no token gives were sampled from Visual Studio running in contrast mode. The editor is monochrome, as in Visual Studio, and VS Code's high-contrast borders are left on. There is no Light (High Contrast): Visual Studio keeps its Light theme under light contrast schemes.

Fili.VSCode2026 0.7.1

Choose a tag to compare

@github-actions github-actions released this 05 Oct 11:23
  • PowerShell takes Visual Studio's colours: foreach, if and param are keyword blue rather than control-flow purple, cmdlets and variables stay plain, and type literals such as [string] take Visual Studio's green. VB.NET's As and primitive types (Integer) are keyword blue, as in Visual Studio.
  • Dark takes the colours Visual Studio actually draws where they differ from its tokens: find matches are a soft #453B32 instead of #773800, and highlighted references, matched braces, snippet fields, indent guides and the selected caller frame follow suit.
  • References highlighted by text, not by the C# language server, are as strong as the others, as in Visual Studio; they were at 60%.
  • Light (Extra Contrast) uses its own diff-line colour again; 0.7.0 gave it Light's.
  • Verified in VS Code against Visual Studio: references, diff, terminal, Markdown, JSON, PowerShell and VB render the measured values.
  • The README's screenshots are retaken with the current theme, icons and terminal colours.

Fili.VSCode2026 0.7.0

Choose a tag to compare

@github-actions github-actions released this 04 Oct 20:24
  • Most of the colours that were chosen rather than taken from Visual Studio are now measured from a running Visual Studio 2026: in Light, highlighted references and matched braces, find matches, snippet fields, indent guides, the selected caller frame while debugging, the diff view's added and removed lines and words, and input borders. Inferred colours go from 20 to 5 in Light and from 7 to 6 in Dark; docs/PARITY.md lists the rest and why.
  • The integrated terminal uses Visual Studio 2026's own terminal colours in both themes, measured from its terminal. They replace the Windows Terminal "Campbell" scheme, which Visual Studio 2026 does not use.
  • Markdown headings take Visual Studio's class-name colour, and inline code its keyword blue, in both themes; they were keyword blue and string-coloured.

Fili.VSCode2026 0.6.0

Choose a tag to compare

@github-actions github-actions released this 03 Oct 19:57
  • Razor, SCSS, Less and SQL take Visual Studio's own colours: Razor transitions, directives, directive attributes and components (teal in Dark, purple in Light); SCSS and Less variables and SCSS mixins; SQL system functions and strings, including the Extra Contrast variants' values. HTML inside Razor files now gets the same colours as plain HTML when the Razor language server is running.
  • JSON property names in Dark are gold (#D7BA7D), as Visual Studio draws them; they were light blue.
  • HTML attribute names in Dark take Visual Studio's HTML colour (#9CDCFE) instead of its XML one.

Fili.VSCode2026 0.5.0

Choose a tag to compare

@github-actions github-actions released this 03 Oct 16:27
  • Fili.VSCode2026 Icons grows from 11 icons to 25. New: Razor (.razor, .cshtml), XAML and AXAML, MSBuild files (.props, .targets, Directory.Build.props and friends), .resx resources, SQL, HTML, CSS (with SCSS and Less), JavaScript, TypeScript, plain text and logs, Docker (Dockerfile, compose files, .dockerignore) and Git files (.gitignore, .gitattributes, .gitmodules). The Properties and wwwroot folders get Solution Explorer's wrench and globe badges.