Skip to content
Vite.NET

Vite.NET

Integrate Vite SPAs into ASP.NET Core Razor Pages and MVC. One build tool, shared authentication, and micro-frontends — without leaving .NET.
Overview Quick Start View on GitHub

Why Vite.NET

Section titled “Why Vite.NET”

Vite.NET bridges a Vite-powered front end (React, Svelte, Vue, Solid) and an ASP.NET Core back end. Your SPA lives inside your .NET app, so it inherits your authentication, your layouts, and your static-file pipeline — while Vite gives you a fast dev server, HMR, and optimized production bundles.

One build tool

Vite compiles your front end; ASP.NET Core serves it. No second server, no separate deployment.

Zero-duplication config

The Vite plugin emits manifests describing each app. The back end only needs the app’s folder name — everything else is generated.

Shared authentication

Because the SPA is served by your .NET app, it sits behind the same auth and cookies as the rest of your site.

Micro-frontends

Embed one SPA or many, each mounted into its own Razor page, all inside a single ASP.NET Core host.

What your Vite integration looks like

Section titled “What your Vite integration looks like”

An integration has three moving parts:

  1. A Vite plugin (vite-dotnet) added to your SPA’s vite.config.ts. It configures the build output and emits a small JSON manifest describing the app.
  2. A NuGet package (TechGems.ViteDotNet) registered in your ASP.NET Core app. It reads those manifests and exposes tag helpers.
  3. Two tag helpers — <dev-vite-scripts> and <prod-vite-scripts> — that render the correct <script>/<link> tags into a Razor page for development or production.

Continue to the Overview for the full picture, or jump straight to the Quick Start.