This section provides information about deploying applications with the Syncfusion Blazor components.
You can get more information about deploying Blazor applications Here.
Note: We highly recommend to load the Syncfusion Blazor interop script in the application end for the production environment. Refer to this documentation for more details.
Note: You have to change the base path of the application. Refer to the MSDN for more details.
Solution Explorerand select
Folderoption and select the publishing target location.
Advanced...option below the target location.
Blazor Server Application, Deployment Mode is set to
Self-Contained. Because some dependencies are not loaded properly when we host the published folder.
Refer here for publishing the application to Azure App Service using Visual Studio.
Packing the application and its dependencies into a folder for deployment to a hosting system by using the
dotnet publish command.
For CLI deployment, run the following command from your root directory.
dotnet publish -c Release
For Blazor Server CLI deployment.
dotnet publish -c Release --self-contained true -r win-x86
Refer to the dotnet publish’s optional arguments.
Use the following command to specify the path for the output directory.
dotnet publish -c Release -o <output directory>
If the output directory not specified, it defaults to
./bin/[configuration]/[framework]/publish/for a framework-dependent deployment or
./bin/[configuration]/[framework]/[runtime]/publish/for a self-contained deployment.
If the path is relative, the output directory generated is relative to the project file location, not to the current working directory.
Also, refer to the MSDN reference here.
Now, you can host the published folder by using the IIS or Azure app service.