Backend Configuration

The back end’s configuration has been reduced to a single thing: the directory name(s) of the integrated Vite app(s). Every other value the back end needs is read from the manifests the plugin emits into wwwroot.

The ViteDotNet section

Add the app folder name under the ViteDotNet key. It accepts either a single string or an array.

Single app

appsettings.Development.json

{
  "ViteDotNet": "ReactApp"
}

Multiple apps

appsettings.Development.json

{
  "ViteDotNet": [ "ReactApp", "SvelteApp" ]
}

The value(s) must match the SPA folder names — the same names the plugin derives from each app’s working directory, and the folders the manifests are written under in wwwroot.

Tip

With exactly one app configured, the tag helpers’ app-name attribute is optional. With more than one, app-name is required so the helper knows which app to render. See Multiple SPAs.

Registering the integration

Register the integration on the service collection in Program.cs. There are three overloads.

From configuration

Reads the app directory name(s) from the ViteDotNet configuration section:

Program.cs

builder.Services.AddViteIntegration(builder.Configuration);

A single directory in code

Bypasses configuration and registers one app directly:

Program.cs

builder.Services.AddViteIntegration("ReactApp");

Multiple directories in code

Program.cs

builder.Services.AddViteIntegration(new[] { "ReactApp", "SvelteApp" });

Registering the tag helpers

The tag helpers live in the ViteDotNet assembly. Register them in _ViewImports.cshtml (in the Pages folder for Razor Pages, or Views for MVC):

Pages/_ViewImports.cshtml

@addTagHelper *, Microsoft.AspNetCore.Mvc.TagHelpers
@addTagHelper *, ViteDotNet

This makes <dev-vite-scripts> and <prod-vite-scripts> available in your pages.

What you no longer configure

Compared with older versions, these values are no longer in your backend config — they come from the manifests instead:

• The entrypoint (src/main.tsx)
• The container element id (root)
• The dev-server port
• Whether the app is React

They live in vite.config.ts (the plugin’s arguments) and are emitted into the manifests at dev and build time. See How It Works and, if you’re upgrading, the Migrating from v0 guide.