# NuGet Installation
> Step-by-step guide for installing ShellUI via NuGet package with manual Tailwind CSS setup
Source: https://shellui.dev/docs/v0.4/installation/nuget
The NuGet package provides pre-compiled ShellUI components as a traditional package reference. Unlike the CLI approach (which copies component source files into your project), NuGet gives you compiled components — ideal for quick prototyping, teams already using package-based workflows, or when you don't need to modify component internals.
## When to Use NuGet vs CLI
| Aspect | NuGet Package | CLI Tool |
|--------|--------------|----------|
| **Components** | Pre-compiled, referenced as package | Source copied to your project |
| **Customization** | Override via CSS, limited code changes | Full source code access |
| **Updates** | `dotnet add package` to bump version | `shellui update`, then `shellui migrate` |
| **Bundle size** | All components included | Only what you add |
| **Tailwind setup** | Manual (see below) | Automatic via `shellui init` |
| **Best for** | Prototyping, quick starts, package workflows | Customization, production apps |
> **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). To switch to the CLI later, remove the `ShellUI.Components` reference and run `shellui init` and `shellui add`.
The package targets .NET 8, 9 and 10.
---
## Step 1: Install the Package
```bash
dotnet add package ShellUI.Components
```
For chart components (optional):
```bash
dotnet add package Blazor-ApexCharts
```
---
## Step 2: Remove Bootstrap (New Projects)
New Blazor projects ship with Bootstrap. Since ShellUI uses Tailwind CSS, you should remove Bootstrap to avoid style conflicts.
**What to Delete**
Remove these files and folders from your project:
```
wwwroot/
├── lib/
│ └── bootstrap/ ← Delete entire folder
├── css/
│ ├── bootstrap*.css ← Delete
│ └── bootstrap*.min.css ← Delete
```
Also remove any Bootstrap `` or `