Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Visual Studio 2010: why all the foreign language folders?

In the /bin/debug folder of my solution I've noticed a slew of what appear to be foreign language folders with names like "ar", "bg", "ca", "cs", "da"... all the way to "zh-Hant". The folders each have copies of these 4 DLLs:

  • System.ComponentModel.DataAnnotations.resources.dll
  • System.Windows.Controls.Data.Input.resources.dll
  • System.Windows.Controls.Data.resources.dll
  • System.Windows.Controls.resources.dll

The Silverlight application I'm developing doesn't have any internationalization support, so I can't figure out how these files and folders got there. All in all, it's almost 13 MB of files.

Worse yet, when I delete them, they are regenerated the next time I build the solution.

Any advice?

ETA:

Here's the list of DLLs referenced by the Silverlight project:

  • ESRI.ArcGIS.Client
  • ESRI.ArcGIS.Client.Toolkit
  • mscorlib
  • system
  • System.Core
  • System.Net
  • System.Runtime.Serialization
  • System.ServiceModel
  • System.Windows
  • System.Windows.Browser
  • System.Windows.Controls
  • System.Windows.Controls.Layout.Toolkit
  • System.Windows.Controls.Navigation
  • System.Windows.Interactivity
  • System.Xml
like image 330
Klay Avatar asked Oct 13 '10 17:10

Klay


2 Answers

I've noticed that some referenced assemblies tend to use localized resources for internationalization, for example Castle ActiveRecord. I just checked with a project I'm working on (that uses Castle ActiveRecord and ZedGraph - both of which have localized resources in separate assemblies), and after building, the language folders were recreated in my bin folder.

So imo, I believe you're referencing a similar assembly in your project that has localized resources, possibly the Silverlight assemblies or the ArcGIS assemblies (never worked with either).

like image 50
darkphoenix Avatar answered Sep 20 '22 01:09

darkphoenix


I have the exact same problem and I've managed to narrow it down. The problem lies with these two references:

  1. System.Windows.Control
  2. System.Windows.Control.Toolkit (Silverlight Toolkit 5)

By removing these two references, I've managed to remove the unnecessary foreign language DLLs.

If you cant afford to remove those 2 references or any other references, you can delete the foreign language dlls from silverlight installation directory eg. C:\Program Files (x86)\Microsoft SDKs\Silverlight\v5.0\Libraries\Client

like image 40
Syaiful Nizam Yahya Avatar answered Sep 22 '22 01:09

Syaiful Nizam Yahya