AddViteIntegration

NuGet: TechGems.ViteDotNet Extension methods

Registers the Vite.NET integration on the dependency-injection container. Call it once in Program.cs. Three overloads let you source the app directory name(s) from configuration or supply them directly.

Namespace

using ViteDotNet;

Overloads

AddViteIntegration(IConfiguration)

public static void AddViteIntegration(
    this IServiceCollection services,
    IConfiguration configuration)

Reads the app directory name(s) from the ViteDotNet configuration section — either a single string or an array of strings.

Program.cs

builder.Services.AddViteIntegration(builder.Configuration);

Parameter	Type	Description
configuration	IConfiguration	The app configuration; the ViteDotNet section is read from it.

AddViteIntegration(string)

public static void AddViteIntegration(
    this IServiceCollection services,
    string appDirectory)

Registers a single app directory directly, bypassing configuration.

Program.cs

builder.Services.AddViteIntegration("ReactApp");

Parameter	Type	Description
appDirectory	string	The directory name of the integrated Vite app (e.g. "ReactApp").

AddViteIntegration(IEnumerable<string>)

public static void AddViteIntegration(
    this IServiceCollection services,
    IEnumerable<string> appDirectories)

Registers one or more app directories directly.

Program.cs

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

Parameter	Type	Description
appDirectories	IEnumerable<string>	The directory names of the integrated Vite apps.

The ViteDotNet configuration section

The IConfiguration overload reads this section, accepting either form:

{ "ViteDotNet": "ReactApp" }

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

If the section is missing or empty, no directories are registered and the tag helpers will throw when used. See Backend Configuration.