Suppress auto-copying of language resource extensions

4 posts, 0 answers
  1. Carl
    Carl avatar
    195 posts
    Member since:
    Oct 2012

    Posted 25 Mar 2014 Link to this post

    How to configure the ASP.Net C# Razor project with UI for ASP.Net MVC in order to suppress and prevent the apparent automatic copying of all the different language resource extensions into the bin directory of the project???

    If all I want to use is the default culture/language "en-US", why is it necessary for all the other culture/languages to be copied into the bin directory?

    So how to turn off that automatic copying in Kendo.Mvc?
  2. Momchil
    Admin
    Momchil avatar
    58 posts

    Posted 27 Mar 2014 Link to this post

    Hello Carl,

    Copying localization resources to the output folder is a standard behavior for assemblies which support localization. When you create a Telerik UI for ASP.NET MVC VIsual Studio project there is by default four references to assemblies which support localization and copy such folders and these are:
    1. Kendo.Mvc
    2. Microsoft.Data.OData
    3. Microsoft.Data.Edm
    4. System.Spatial

    (The last three assemblies are part of Microsoft ASP.NET Web API OData package)
    If you really don't want these localization folders copied you can follow these steps to delete the localization resources folders for each referenced assembly:

    1. Get the path to the assembly by looking in the properties of the reference to this assembly in your project.
    2. Navigate to this path. You will see the assembly and many folders containing localization resources for each language.
    3. Delete these localization resources folders.
    When you do these steps for each of the four referenced assemblies there will be no more copying of the localization resources in the bin folder but your application will not support localization anymore.

    I hope this will help you.

    Regards,
    Momchil
    Telerik
     

    Build cross-platform mobile apps using Visual Studio and .NET. Register for the online webinar on 03/27/2014, 11:00AM US ET.. Seats are limited.

     
  3. UI for ASP.NET MVC is VS 2017 Ready
  4. Carl
    Carl avatar
    195 posts
    Member since:
    Oct 2012

    Posted 27 Mar 2014 in reply to Momchil Link to this post

    Thank you for instructions.  However, we should have control over this kind of thing without "jumping through hoops".

    The desired behavior is in fact "not supporting localization" and "no more copying of the localization resources to the bin folder".

    There should be a simple flag - boolean switch - to turn on or off copying of localization resources to the bin folder.

    Then we can use localization resources when we do or do not want in an easy manner controlled by a simple switch.
  5. Momchil
    Admin
    Momchil avatar
    58 posts

    Posted 28 Mar 2014 Link to this post

    Hi Carl,

    I understand your point and I agree that such an option could be useful but this is the current behavior of the Visual Studio with localized assemblies.

    Regards,
    Momchil
    Telerik
     

    Build cross-platform mobile apps using Visual Studio and .NET. Register for the online webinar on 03/27/2014, 11:00AM US ET.. Seats are limited.

     
Back to Top
UI for ASP.NET MVC is VS 2017 Ready