Errors using localization

I created a Blazor project in Visual Studio 2019, using the "Syncfusion Blazor Template Studio" template.
I chose "Syncfusion Blazor Server App" and selected ".NET Core 3.1" for the version.
The template UI forces the selection of at least 1 control, so, I selected "DataGrid" - although, that control has nothing to do with my question. I used all the defaults for the grid.
I chose "Localization", then I created the Visual Studio project.
The template creates the project using Syncfusion.Blazor.dll v18.2.0.59, which won't compile, so, I updated to the latest version available, which was v18.3.0.42.
I commented the line that adds the license, since that really doesn't matter for this scenario:

I then added a breakpoint on the culture controller, to catch the error on the UI:

Then I built and started the application. I then chose a language from the culture picker:

That results in an error at runtime. Using Chrome tools, I checked for the error message and saw this:

No idea why this happens, or how to work around it. It seems to only happen with some languages, not with all.
I've included the project, in case that helps.
Any ideas?

Attachment: SyncfusionBlazorApp1_3fab6333.zip

4 Replies 1 reply marked as answer

RN Rahul Narayanasamy Syncfusion Team October 22, 2020 12:59 PM UTC

Hi Martin, 

Greetings from Syncfusion. 

Query: Errors using localization  

We have validated your query and checked the reported problem at our end. We could not reproduce the reported problem while changing the Locale in the dropdown with the provided sample itself. Find the below video link for your reference. 


If you are still facing the problem, then could you please share below details. it will be helpful to validate and provide a better solution. 

  • Video demonstration.
  • Visual studio configuration details.

Regards, 
Rahul 



UN Unknown October 22, 2020 05:16 PM UTC

Here are my visual studio details:



Attachment: myvideo_a706a26f.zip


RN Rahul Narayanasamy Syncfusion Team October 23, 2020 03:47 PM UTC

Hi Martin, 

Thanks for sharing the details. 

We have validated your query with the provided information. We have checked the reported problem in the below Visual Studio version. 

Microsoft Visual Studio Professional 2019 
Version 16.6.2 
 
Microsoft Visual Studio Professional 2019 Preview 
Version 16.8.0 Preview 3.1 

But we could not reproduce the problem at our end. Could you please ensure the reported problem at your end by upgrading the dotnet version to 5.0 or sdk version to 5.0.100-rc.1.20452.10.  

Also, we might suspect that the issue was from dotnet team and they mentioned that these issue will be included in RC2 update. Please find the below reference links for your reference. 


If you are still facing difficulties, please get back to us with the those details. 

regards, 
Rahul  


 


Marked as answer

UN Unknown October 23, 2020 06:02 PM UTC

I can verify that the issue still happens after installing SDK version 5.0.100-rc.2.20479.15 on my machine. I had SDK version 5.0.100-rc.1.20452.10 previously on my machine and the problem was there with that version as well.  

My version of Visual Studio is Community Edition 2019 version 16.7.6. Only thing I can think is maybe try to duplicate the issue on your end with that version of VS. 



Loader.
Up arrow icon