Hello!

The behavior that you are seeing is by design. The localization approach used by .NET Applications follows a hub-and-spoke model where there hub is the main assembly and the spokes are satellite assemblies containing localized strings. The naming of the satellite assemblies is based on .NET culture names.

This model applies to the resx files as well -- the default strings are in the main resx file and the localized strings are in culture-specific .resx files with the culture name appended to the file name of the main resx file.

Because all resources will be accessed through a ResourceManager instance, there is only a need for a single code file that corresponds to the main resx file.

In your example, you would have a Localize.resx with Localize.Designer.cs nested underneath it and you could create Localize.en.resx for the 'en' culture if it is not your default culture.

For more information, see https://msdn.microsoft.com/en-us/library/sb6a8618(v=vs.100).aspx.

Best regards,

Svet Bonev

Visual Studio Client Tools

Thank you for your feedback! We have determined that this issue is not a bug. Please see https://msdn.microsoft.com/en-us/library/sb6a8618(v=vs.110).aspx for additional information.