Hi Quang,
Sorry for the delayed update.
We have checked your reported problem with Kestral and we are unable to reproduce it on our end. Meanwhile, we have proceeded with this issue for finding any possibilities to replicate this from our end. Based on that, we suspect that the environment is other than “Development”. So, static web assets are not loading properly. Also, we want to inform you that the reported issue is not with the Syncfusion library and it is the behavior of the ASP.NET Core Blazor platform itself. We can refer to the below GitHub issue for more details.
However, we can use the below configuration in a 'startup.cs' to deploy the application on the server/local.
| public void Configure(IApplicationBuilder app, IWebHostEnvironment env)
{
if (env.IsEnvironment("Local") || env.IsEnvironment("Production") || env.IsEnvironment("Staging"))
{
// For Deploying
#if (RELEASE)
app.UseStaticFiles(new StaticFileOptions
{
FileProvider = new PhysicalFileProvider(
Path.Combine(env.ContentRootPath, "wwwroot/_content/Syncfusion.Blazor/scripts")),
RequestPath = "/_content/Syncfusion.Blazor"
});
//For local
#else
app.UseStaticFiles(new StaticFileOptions
{
FileProvider = new PhysicalFileProvider(
@"C:\Users\{USER-NAME}\.nuget\packages\syncfusion.blazor\{VERSION}\staticwebassets"),
RequestPath = "/_content/Syncfusion.Blazor"
});
#endif }
//...other snippets...
}
|
We have also created a sample for your reference that you can find from the below link.
Please let us know if we misunderstood your query and you have any concerns about this.
Regards,
Muthukumar K
