Upgrading Syncfusion® Blazor NuGet packages to a latest version
29 Nov 20243 minutes to read
Every three months, Syncfusion® releases new volumes with interesting new features. For this volume, there will be weekly NuGet releases and a service pack. Syncfusion® Blazor NuGet packages are released on a weekly basis to address critical issue fixes.
From any Syncfusion® Blazor NuGet version you have installed; you can update to our most recent version.
Upgrade NuGet packages through Package Manager UI
The NuGet Package Manager UI in Visual Studio allows you to easily install, uninstall, and update NuGet packages in applications and solutions. You can find and upgrade the Syncfusion® Blazor NuGet packages to the most recent version or to specific version in the Blazor solution or application and this process is easy with the steps below:
-
Right-click on the Blazor application or solution in the Solution Explorer tab, and choose Manage NuGet Packages…
As an alternative, after opening the Blazor application in Visual Studio, go to the Tools menu and after hovering NuGet Package Manager, select Manage NuGet Packages for Solution…
-
The Manage NuGet Packages window will open. Navigate to the Updates tab, then search for the Syncfusion® Blazor NuGet packages using a term like “Syncfusion” and select the appropriate Syncfusion® Blazor NuGet package for your application.
NOTE
The nuget.org package source is selected by default in the Package source drop-down. If your Visual Studio does not have nuget.org configured, follow the instructions in the Microsoft documents to set up the nuget.org feed URL.
-
By default, the package selected with latest version. You can select the required version and click the Update button and accept the license terms. The package will be upgraded to selected version in your Blazor application.
You can choose the multiple NuGet packages by selecting the checkbox like below and click the Update button to update the multiple Syncfusion® NuGet packages in your application.
Upgrade NuGet packages through Dotnet (.NET) CLI
There is no distinct command for the update procedure in the Dotnet CLI. Unless you specify the package version, Dotnet CLI installs the latest version of the Syncfusion® Blazor NuGet packages when you use the dotnet add package command.
To specify a version, add the -v parameter:
dotnet add package Syncfusion.Blazor.Grid -v 19.2.0.44.
Upgrade NuGet packages through Package Manager Console
The Package Manager Console saves NuGet packages upgrade time since you don’t have to search for the package you want to update, and you can just type the command to update the appropriate Syncfusion® Blazor NuGet package. Follow the steps below to upgrade the installed Syncfusion® NuGet packages using the Package Manager Console in your Blazor application.
-
To show the Package Manager Console, open your Blazor application in Visual Studio and navigate to Tools in the Visual Studio menu and after hovering NuGet Package Manager, select Package Manager Console.
-
The Package Manager Console will be shown at the bottom of the screen. You can install the Syncfusion® Blazor NuGet packages by enter the following NuGet update commands.
Update specified Syncfusion® Blazor NuGet package
The below command will update the Syncfusion® Blazor NuGet package in the default Blazor application
Update-Package <Package Name>
For example: Update-Package Syncfusion.Blazor.Grid
Update specified Syncfusion® Blazor NuGet package in specified Blazor application
The below command will update the Syncfusion® Blazor NuGet package in the given Blazor application alone
Update-Package <Package Name> -ProjectName <Project Name>
For example: Update-Package Syncfusion.Blazor.Grid -ProjectName BlazorApplication
-
By default, the package will be installed with latest version. You can give the required version with the -Version term like below to install the Syncfusion® Blazor NuGet packages in the appropriate version.
Update-Package Syncfusion.Blazor.Grid -Version 19.2.0.44
-
The NuGet package manager will update the Syncfusion® Blazor NuGet package as well as the dependencies it has.