Welcome to the Blazor feedback portal. We’re happy you’re here! If you have feedback on how to improve the Blazor, we’d love to hear it!

  • Check out the features or bugs others have reported and vote on your favorites. Feedback will be prioritized based on popularity.
  • If you have feedback that’s not listed yet, submit your own.

Thanks for joining our community and helping improve Syncfusion products!

3
Votes

Hi,

I have just spent quite a lot more time that I'd like to admit to tracking down the cause of the following error.

InvalidOperationException: Cannot provide a value for property 'Localizer' on type 'Syncfusion.Blazor.Inputs.SfTextBox'. There is no registered service of type 'Syncfusion.Blazor.ISyncfusionStringLocalizer'.

I was working on a fairly complex project that mixes both Server and WASM components and I added an SfTextBox to a page and started to get this error.  

In the end, the problem turned out to be that I had forgotten to 

include builder.Services.AddSyncfusionBlazor(); in my Program.cs file.

I checked a few of the Input controls (including NumericTextBox) and they threw the same error.

However, I tried a number of other unrelated controls, and they had a much clearer error such as the following for a Button control:

InvalidOperationException: Cannot provide a value for property 'SyncfusionService' on type 'Syncfusion.Blazor.Buttons.SfButton'. There is no registered service of type 'Syncfusion.Blazor.SyncfusionBlazorService'.

While just a silly mistake on my part, it might help someone else in a similar situation if the error of 

There is no registered service of type 'Syncfusion.Blazor.SyncfusionBlazorService' was standardised for all controls if 
AddSyncfusionBlazor() is omitted.