satellite-assembly

I want to override a string from a System.ComponentModel.DataAnnotations for an ASP.NET project. Do I need to make a satellite assembly, messing with custom build tasks, al.exe etc.? Even if yes, I couldn't find how to convert .resx to .resources to feed it to al.exe . And if no, where to put the .resx. and how to name it? UPD: To make it clear: I wanted to use a custom resource string instead of one from the default resource from the assembly. I didn't want to make changes in the every place that uses that string. After all, the resources exist just for overriding them. VoidDweller Phil Haack

We have an application whose structure when compiled looks something like this: Foo nb-NO Text.resources.dll sv-SE Text.resources.dll Bar.dll Foo.exe Text.dll Is it possible to use ILMerge on this? How would you do that? Tao I asked my own variant of this question and eventually got/implemented an answer: Single-assembly multi-language Windows Forms deployment (ILMerge and satellite assemblies / localization) - possible? Hope this helps. Disclaimer: I work for the company that makes Dotfuscator. There may be other alternatives out there that I am not aware of but I am pretty sure ILMerge does

I got the problem that I need to distribute a C# project as a single EXE file which is not an installer but the real program. It also needs to include a translation which currently resides in a subdirectory. Is it possible to embed it directly into the binary? binball Here it is the simplest solution which I saw in the Internet: How to embed your application’s dependent DLLs inside your EXE file also handy implementation of this solution: http://code.google.com/p/costura/wiki/HowItWorksEmbedTask The short answer is yes, there is a program called Assembly Linker (AL.exe) that will embed

What is a satellite assembly, and when should they be used? A definition from MSDN says something like this: "A .NET Framework assembly containing resources specific to a given language. Using satellite assemblies, you can place the resources for different languages in different assemblies, and the correct assembly is loaded into memory only if the user elects to view the application in that language." This means that you develop your application in a default language and add flexibility to react with change in the locale. Say, for example, you developed your application in an en-US locale.