IonBlazor.Components
0.887.9
dotnet add package IonBlazor.Components --version 0.887.9
NuGet\Install-Package IonBlazor.Components -Version 0.887.9
<PackageReference Include="IonBlazor.Components" Version="0.887.9" />
<PackageVersion Include="IonBlazor.Components" Version="0.887.9" />
<PackageReference Include="IonBlazor.Components" />
paket add IonBlazor.Components --version 0.887.9
#r "nuget: IonBlazor.Components, 0.887.9"
#:package IonBlazor.Components@0.887.9
#addin nuget:?package=IonBlazor.Components&version=0.887.9
#tool nuget:?package=IonBlazor.Components&version=0.887.9
IonBlazor.Components
Razor / Blazor wrappers for Ionic Framework web components.
C# component types only. Does not include Ionic's JavaScript bundle, CSS, or icons. Use this package when you want to control how Ionic itself is loaded — typically a CDN reference, or in a MAUI Hybrid solution where only one project is allowed to ship the static assets.
For the all-in-one experience (wrappers + every static asset), install IonBlazor instead.
Install
dotnet add package IonBlazor.Components
Setup
You're responsible for loading Ionic's JS and CSS. Two common approaches:
Option 1 — Load Ionic from a CDN
In your host page (wwwroot/index.html, _Host.cshtml, or App.razor):
<script type="module" src="https://cdn.jsdelivr.net/npm/@ionic/core/dist/ionic/ionic.esm.js"></script>
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@ionic/core/css/core.css" />
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@ionic/core/css/ionic.bundle.css" />
Option 2 — Add the asset packages explicitly
dotnet add package IonBlazor.StaticAssets # JS interop modules (required)
dotnet add package IonBlazor.StaticAssets.Ionic # Ionic JS bundle + CSS
dotnet add package IonBlazor.StaticAssets.Ionic.Svg # Ionic SVG icons (optional)
Then point your host page at _content/IonBlazor/... — see the IonBlazor package README for the snippet.
Add the namespaces to _Imports.razor:
@using IonBlazor.Components
@using IonBlazor.Components.Abstractions
@using IonBlazor.Services
MAUI Hybrid
In a MAUI Hybrid solution with multiple Razor projects, only one project can ship the static assets — otherwise MAUI's packaging fails with a duplicate-static-asset error.
Pick one project to carry the assets (typically the MAUI host) and have it reference either:
- the bundle —
IonBlazor, or - the granular packages —
IonBlazor.StaticAssets+IonBlazor.StaticAssets.Ionic(+IonBlazor.StaticAssets.Ionic.Svgfor icons), plus this package for the wrappers.
Every other project in the solution references only IonBlazor.Components — no assets, just the C# types — so the wrappers stay available everywhere while the assets ship exactly once.
Supported frameworks
net8.0, net9.0, net10.0.
Links
License
MIT.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net8.0 is compatible. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 is compatible. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- Microsoft.AspNetCore.Components (>= 10.0.0)
- Microsoft.AspNetCore.Components.Web (>= 10.0.0)
-
net8.0
- Microsoft.AspNetCore.Components (>= 8.0.0 && < 9.0.0)
- Microsoft.AspNetCore.Components.Web (>= 8.0.0 && < 9.0.0)
-
net9.0
- Microsoft.AspNetCore.Components (>= 9.0.0)
- Microsoft.AspNetCore.Components.Web (>= 9.0.0)
NuGet packages (1)
Showing the top 1 NuGet packages that depend on IonBlazor.Components:
| Package | Downloads |
|---|---|
|
IonBlazor
IonBlazor bundle — includes all components and static assets. |
GitHub repositories
This package is not used by any popular GitHub repositories.