Creating a new project and opting for localization causes the wizard to throw

Progress® Telerik® UI for Blazor Feedback Portal

Create an account Log In

Back to Feed

Request a Feature Report a Bug

Completed

Last Updated: 14 Jul 2022 09:46 by ADMIN

Release 3.5.0

Czeshirecat

Created on: 24 Jun 2022 06:38

Category: UI for Blazor

Type: Bug Report

Creating a new project and opting for localization causes the wizard to throw

Hi. VS 2022 version 17.2.4, C#, Windows 11

I thought I'd have a look at blazor and selected the Telerik version in the new projects window and ran through the wizard.

I selected the dashboard look, .net 6, teleric UI for blazor 3.4.0 (Dev) and to enable localization, which is what I assume to be the cause of the following error message. There were no other hints and as I've never tried blazor or telerik for blazor I don't know if there's anything missing from the solution. If I ran another wizard without localization there was no error.

An error occurred while running the wizard.

Error executing custom action Telerik.Blazor.VSX.Actions.CopyBlazorLocalizationResourcesAction: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
   at System.ThrowHelper.ThrowKeyNotFoundException()
   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
   at Telerik.Blazor.VSX.Actions.CopyBlazorLocalizationResourcesAction.Execute(WizardContext wizardContext, IPropertyDataDictionary arguments, IProjectWrap project)
   at Telerik.VSX.WizardEngine.ActionManager.ExecActions()

1 comment

ADMIN

Radko

Posted on: 30 Jun 2022 14:11

Hi Claire,

Thank you for reporting - I can confirm it is the wizard itself causing the issue, rather than something on your part. The error itself stems from the fact an older version of the localization resources is copied to the output folder. As an author of this bug report, you are automatically subscribed to receive notifications on its status updates. Also, I have updated your Telerik Points as a gesture of gratitude.

A workaround, for the time being, is to manually replace the files in the newly created project with the ones from the Telerik UI for Blazor installation folder. You can find more details in regards to where these are located here: How Localization Works in the Telerik Components.

Lastly, I hope you do not mind I have updated the title of this item to more accurately describe the issue, making it easier for other people to discover.

Regards, Radko Stanev Progress Telerik

The Premier Dev Conference is back!

Coming to you live from Progress360 in-person or on your own time, DevReach for all. Register Today.