You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: common-features/icons.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,6 +35,8 @@ The Telerik Blazor components use built-in icons with the help of two NuGet pack
35
35
*`Telerik.FontIcons` - defines the `FontIcon``enum` for easier usage of built-in **font** icons
36
36
*`Telerik.SvgIcons` - defines the `ISvgIcon` interface and the `SvgIcon` static class for built-in **SVG** icons
37
37
38
+
>tip Unlike the `Telerik.UI.for.Blazor` package, the icon packages are available from the `nuget.org` source. Keep this in mind when using [`packageSourceMapping`](https://learn.microsoft.com/en-us/nuget/consume-packages/package-source-mapping).
39
+
38
40
To use the icons, import one or both namespaces, for example in `_Imports.razor`:
The error `Unable to find package` can imply the following:
70
+
71
+
* If the error occurs for the `Telerik.UI.for.Blazor` package, the [Telerik NuGet source]({%slug installation/nuget%}) may not be added or enabled. The possible causes are:
72
+
* Missing configuration in the `NuGet.Config` file (or Visual Studio).
73
+
* The correct `NuGet.Config` file is not used. This is common in Docker scenarios and the solution is to copy the `NuGet.Config` file explicitly during build. See the forum thread about [private NuGet feeds in Docker](https://www.telerik.com/forums/can-the-telerik-blazor-and-asp-net-tools-be-used-in-a-docker-container) and [some DevOps examples](https://github.com/LanceMcCarthy/DevOpsExamples)).
74
+
* If the error occurs for the [icon packages (`Telerik.FontIcons` and `Telerik.SvgIcons`)]({%slug general-information/font-icons%}), the NuGet client is not using `nuget.org` as a NuGet source. The possible causes are:
75
+
* The NuGet source is disabled.
76
+
* The [`packageSourceMapping`](https://learn.microsoft.com/en-us/nuget/consume-packages/package-source-mapping) forces the NuGet client to search for the icon packages in the `nuget.telerik.com` source. However, the icon packages are published on `nuget.org`.
77
+
78
+
66
79
## See Also
67
80
68
81
*[Setup of the Telerik Online Private NuGet Feed]({%slug installation/nuget%})
0 commit comments