# Installation > Install ShellUI via CLI or NuGet package Source: https://shellui.dev/docs/v0.4/installation ShellUI 0.4 offers a **hybrid workflow** with two installation methods. Choose the approach that fits your project. These pages cover 0.4.0, the current stable release, which `dotnet tool install` and `dotnet add package` install by default. For 0.3, see the [v0.3 docs](https://shellui.dev/docs/v0.3/installation.md). ## Prerequisites - **.NET 8 SDK or later** to run the CLI; your Blazor project can target **.NET 8, 9 or 10** with the CLI or the NuGet package - **Node.js** (optional — only needed if using npm for Tailwind) - A **Blazor project** (Server, WebAssembly, Hybrid, or Interactive Server) --- ## Installation Methods - [CLI Installation (Recommended)](https://shellui.dev/docs/v0.4/installation/cli.md): Copy components directly into your project for full ownership and customization. Automatic Tailwind setup, MSBuild integration, and component management. - [NuGet Package](https://shellui.dev/docs/v0.4/installation/nuget.md): Traditional package install for quick prototyping. Pre-compiled components with manual Tailwind CSS setup. --- ## CLI vs NuGet — Which to Choose? | Aspect | CLI Tool | NuGet Package | |--------|----------|---------------| | **Install command** | `shellui add button card` | `dotnet add package ShellUI.Components` | | **Components** | Source copied to your project | Pre-compiled, referenced as package | | **Customization** | Full source code access — edit anything | Override via CSS, limited code changes | | **Tailwind setup** | Automatic via `shellui init` | Manual setup required | | **Bundle size** | Only components you add | All components included | | **Updates** | `shellui update`, then `shellui migrate` | Bump package version | | **Best for** | Production apps, full customization | Prototyping, quick starts | > **Pick one per project.** The package and the CLI define the same component names, so using both makes those names ambiguous (`shellui doctor` warns about it). Start with the package if you like, and move to the CLI when you need to change a component's source. --- ## Quick Start The fastest way to get started with ShellUI: ```bash # 1. Install the CLI tool dotnet tool install -g ShellUI.CLI # 2. Initialize in your Blazor project cd your-blazor-project shellui init # 3. Add components shellui add button input card dialog # 4. Run your app dotnet run ``` `shellui init` also offers to set up a [dashboard layout](https://shellui.dev/docs/v0.4/dashboard.md); pass `--dashboard 02` to choose one without the prompt. That's it — `shellui init` handles Tailwind CSS setup, Bootstrap cleanup, folder creation, and MSBuild integration automatically. [View full CLI guide](https://shellui.dev/docs/v0.4/installation/cli.md) | [View full NuGet guide](https://shellui.dev/docs/v0.4/installation/nuget.md) --- ## Project Types ShellUI works with all Blazor hosting models: **Blazor Server** ```bash dotnet new blazorserver -n MyApp cd MyApp shellui init shellui add button card input dotnet run ``` **Blazor WebAssembly** ```bash dotnet new blazorwasm -n MyApp cd MyApp shellui init shellui add button card input dotnet run ``` **Blazor Hybrid** Works with MAUI, WPF, and WinForms Blazor Hybrid apps. ```bash dotnet new maui-blazor -n MyApp cd MyApp shellui init shellui add button card input dotnet run ``` **Interactive Server** Supports Blazor's Interactive Server rendering mode. ```bash dotnet new blazor -n MyApp cd MyApp shellui init shellui add button card input dotnet run ``` --- ## Verification After installation, verify everything is working: 1. **Build** your project: `dotnet build` 2. **Check** that `wwwroot/app.css` was generated 3. **Run** the project: `dotnet run` ### Quick Test ```razor @page "/test" @using YourProject.Components.UI