satellite-assembly

VB.NET/C# Globalization: Prevent creation of culture-specific satellite assemblies (resources)

Hello, is there a possibility to prevent the creation of all the folders with the resources.dll files and just embed every globalization culture right into the compiled exe file? ...

How to access resources from an external assembly.

I want to create a vb.net project that I will use to only hold image and string resources that I will need in multiple projects. What I can't figure out is how do I access these resources using code from other projects. ...

How do I reference a font resource in a satellite assembly?

I have a localised WPF application and I need to embed a font for each locale. I have a font added into my project and it's Build Action is set to Resource. If I remove the <UICulture>en-US</UICulture> from my .csproj (which eliminates the creation of the satellite assemblies) the font is compiled as a resource into the project assembl...

Can you static link satellite assemblies?

I don't know enough about satelite assemblies to understand their construction, I'm curious if it's possible to statically link them all into a single dll and get the same functionality as if they weren't statically linked from: ResourceManager.GetString("SomeStringIdentifier", CultureInfo.GetCulture(someCultureThatYouHaveResourcesFor))...

Removing the default language in an assembly and moving it to a satellite assembly

Hi everyone, I have a .Net 3.5 application written mostly in C# that uses .resx files to store internationalization data for several different languages, consisting of strings, control sizes and positions, etc. What I'm trying to figure out is this: it is possible to compile my application in such a way that the default culture data...

Can I use a satellite resource assembly for one language in the OS for another language simply by changing the name of the folder the dll appears in?

If I compile a .NET satellite assembly with localised resources, does the assembly itself know which language it is for, or is this implied in the folder in which it appears? If I decide to create a localised assembly where all strings are enclosed by '@' symbols for testing if all of my app is localised and then install that on an EN-G...