-
Run
analyzeto understand which projects and files will be affected. -
Use
--jsonto save the analysis report for later review or sharing. -
Run
migratewith--dry-runto preview all file changes. -
Re-run
migratewith--backupto apply changes and keep.bakcopies.
Blazorise 2.0 Migration CLI
The Blazorise Migrator is a command-line tool that helps you safely and predictably upgrade existing projects to Blazorise 2.0.
It analyzes your solution or project, reports the required changes, and can automatically apply them when you are ready. You stay in control at every step.
When should I use this?
Use the Blazorise Migrator when upgrading an existing application from Blazorise 1.x to 2.0.
- You are updating package references to Blazorise 2.0.
- Your project uses components, parameters, or APIs that changed in 2.0.
- You want a guided, reviewable upgrade process with minimal manual changes.
The migrator is not required for new projects created with Blazorise 2.0 templates.
Installation
dotnet tool install -g Blazorise.Migrator --prerelease
Verify installation
Confirm that the tool is available on your system path.blazorise-migrate --version
Recommended workflow
blazorise-migrate analyze --path C:\src\MyApp.sln blazorise-migrate analyze --json C:\temp\blazorise-report.json blazorise-migrate migrate --path C:\src\MyApp.sln --dry-run blazorise-migrate migrate --path C:\src\MyApp.sln --backup
Analyze
Inspect your solution
Analyze a solution or project to determine required Blazorise 2.0 migration changes.
The analyze command always runs in dry-run mode and never modifies files.
It reports all detected migration actions before any changes are applied.
If --path is omitted, the current directory is used.
You may specify a folder, .sln, .slnx, or .csproj.
blazorise-migrate analyze [--path <path>] [--json <file>] [--all-projects] [--verbose]
Migrate
Apply changes
Apply required Blazorise 2.0 migration changes to eligible projects.
The migrate command updates projects that reference Blazorise packages.
Use --dry-run to preview changes and --backup to preserve original files.
If --path is omitted, the current directory is used.
No files are modified unless the migrate command is executed without --dry-run.
blazorise-migrate migrate [--path <path>] [--dry-run] [--backup] [--all-projects] [--verbose]
Command options
Analyze options
| Name | Description | Type | Default |
|---|---|---|---|
--path <path> |
Path to a folder, |
string | current directory |
--json <file> |
Writes the analysis report to the specified file. |
string | none |
--all-projects |
Scan all projects under the path, even if they do not reference Blazorise packages. |
bool | false |
--verbose |
Output detailed diagnostics during analysis. |
bool | false |
Migrate options
| Name | Description | Type | Default |
|---|---|---|---|
--path <path> |
Path to a folder, |
string | current directory |
--dry-run |
Preview all changes without modifying files. |
bool | false |
--backup |
Create |
bool | false |
--all-projects |
Scan all projects under the path, regardless of Blazorise references. |
bool | false |
--verbose |
Output detailed diagnostics during migration. |
bool | false |
Global options
| Name | Description | Type |
|---|---|---|
--help |
Display command help information. |
flag |
--version |
Display the installed tool version. |
flag |