Last Updated: 22 Mar 2024 07:02 by ADMIN
Created on: 18 Mar 2024 13:02
Category: UI for ASP.NET Core
Type: Feature Request
Suppress auto-copying of Language resource Folders

 When uncheck "Use localization" while create project the Localization resources are still auto copied while publish the project.

The resources are part of the telerik.ui.for.aspnet.core.yyyy.q.mmdd.nupkg and therefore are copied to the bin folder regardless of the  "Use localization" option. The "Use localization" option controls the availability only of the messages files.

This a feature request for providing another lightweight NuGet which does not contain the localization dlls that could be used for non-localized projects.


1 comment
Posted on: 22 Mar 2024 07:02

Hi Charles,

Generally,  the Telerik UI for ASP.NET Core uses satellite assemblies to support localization.  To modify what is used or included during publishing, a custom version of Kendo.Mvc.dll must be built in order to remove the existing folder structure.

However, my personal recommendation here would be to leverage the SatelliteResourceLanguages property. Which lets you specify which languages you want to preserve satellite resource assemblies for during build and publish.

As stated in the official Microsoft Documentation:

"By adding the SatelliteResourceLanguages property to your project file, only localized assemblies for the languages you specify will be included in the build and publish output."

This can be achieved via the ".csproj" file of the application. Here is an example:


This will ensure that only the specified languages will be supplemented with its satellite assembly counter-part:

And omit the one that are not explicitly specified:

Alternatively, you can also consider adding a single <SatelliteResourceLanguages> tag that holds the language codes separated by a semicolon (;). In order to prevent further XML pollution in terms of "csproj" file's proportions:


I hope this information proves helpful.

Kind Regards,
Progress Telerik

Stay tuned by visiting our public roadmap and feedback portal pages. If you're new to the Telerik family, be sure to check out our getting started resources, as well as the only REPL playground for creating, saving, running, and sharing server-side code.