Skip to Content
New release 12 available 🎉
ObfuscatorMSBuild TaskCustomizing IntelliSense

Customizing IntelliSense

The MSBuild Babel task attributes are defined in the schema file Babel.Build.xsd, shipped next to Babel.Build.dll in the MSBuild folder of the babel_net* zip packages. Registering this schema with your editor gives you completion and inline documentation for the Babel task and its attributes while editing project files, which makes build scripts that use the Babel task easier to write and maintain.

Visual Studio

Visual Studio keeps its MSBuild schemas in the Xml\Schemas\1033 folder under the installation directory.

Find your schema folder

VersionSchema folder
Visual Studio 2026C:\Program Files\Microsoft Visual Studio\18\<edition>\Xml\Schemas\1033
Visual Studio 2022C:\Program Files\Microsoft Visual Studio\2022\<edition>\Xml\Schemas\1033
Visual Studio 2019C:\Program Files (x86)\Microsoft Visual Studio\2019\<edition>\Xml\Schemas\1033

Where <edition> is Community, Professional or Enterprise. Note that Visual Studio 2026 names its folder after the major version number (18) rather than the year, and that Visual Studio 2019 lives under Program Files (x86). If you installed Visual Studio to a custom location, use the Xml\Schemas\1033 folder under that path instead.

Copy the schema file

Copy Babel.Build.xsd into the folder that matches your version and edition.

Add the Babel include

Open Microsoft.Build.xsd in the same folder and add the Babel include right after the existing include of the MSBuild common types:

<xs:include schemaLocation="MSBuild\Microsoft.Build.CommonTypes.xsd"/>
<!-- Import of the Babel Build XSD definition -->
<xs:include schemaLocation="Babel.Build.xsd"/>

Restart Visual Studio

Restart Visual Studio for the change to take effect. Editing files under Program Files requires administrator rights, and a Visual Studio update can replace Microsoft.Build.xsd: if completion for the Babel task stops working after an update, re-apply the include.

Other Editors

Babel.Build.xsd targets the MSBuild namespace (http://schemas.microsoft.com/developer/msbuild/2003) and includes MSBuild\Microsoft.Build.Core.xsd, so it is designed to sit next to the MSBuild schema set and be pulled in from Microsoft.Build.xsd exactly as shown above. Editors other than Visual Studio do not read the Visual Studio schema folder, but they can be pointed at a schema set you assemble yourself:

  1. Create a folder containing Microsoft.Build.xsd and its MSBuild\ subfolder. Copy them from a Visual Studio installation, or take them from the MSBuild repository . Place Babel.Build.xsd next to Microsoft.Build.xsd and add the include line shown above.
  2. Because the schema declares a target namespace, the project file must declare the MSBuild namespace on its root element for the association to apply. MSBuild accepts the namespace on SDK-style projects too:
<Project Sdk="Microsoft.NET.Sdk" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">

Visual Studio Code

With the XML extension by Red Hat  installed, associate your project files with the schema set in settings.json:

"xml.fileAssociations": [
  { "pattern": "**/*.csproj",  "systemId": "C:/Schemas/MSBuild/Microsoft.Build.xsd" },
  { "pattern": "**/*.props",   "systemId": "C:/Schemas/MSBuild/Microsoft.Build.xsd" },
  { "pattern": "**/*.targets", "systemId": "C:/Schemas/MSBuild/Microsoft.Build.xsd" }
]

Replace C:/Schemas/MSBuild/ with the folder created in step 1.

JetBrains Rider

Go to Settings | Languages & Frameworks | Schemas and DTDs, click Add to open the Map External Resource dialog, enter http://schemas.microsoft.com/developer/msbuild/2003 as the URI and select your Microsoft.Build.xsd as the location. Rider then validates and completes project files that declare that namespace against the mapped schema, Babel task included.

Last updated on