I've got it!

From: M. (anonymous_at_discussions.microsoft.com)
Date: 03/14/04

Date: Sun, 14 Mar 2004 11:25:04 -0800


I found, that you must create a binary resource with
resgen, before you can create satellite assembly from it.
Altough this will create something like satellite

al /t:lib /embed:Form1.sk-
SK.resx /out:MyApplication.resources.dll

this is not a valid sat. assmbly. and application will
not recognize it.

As first, you must generate binary resource file with
resgen. The
form: "ApplicationName.ResourceName.resources" is

resgen Form1.sk-SK.resX MyApplication.Form1.sk-

As second, you must embed it to sat. assembly.
The /culture switch is important.

al /t:lib /culture:en-US /embed:MyApplication.Form1.sk-
Sk.resources /out:MyApplication.resources.dll

This sat. assmbly works as expected. Yeah!

Thanks goes to ildasm... :-)


>-----Original Message-----
>I've question about resources. I've found this in MSDN:
>"When you are finished creating .resources files with
>Resgen.exe, use the Assembly Linker (Al.exe) to either
>embed the resources in a runtime binary executable or
>compile them into satellite assemblies."
>I think, that resgen isn't required. I can do this:
>al /embed:Form1.resx /out:Form1Res.dll
>and I have resource-only assembly. Right? So when I get
>question, like what is the most effective method to
>create resource-only assembly, can I skip generating
>binary resource by resgen?
>P.S. I just get similair question on my MeasureUP. The
>explanation tells this:
>"A .resources file is a binary representation of the
>human readable resource file and is generated by the
>Resource File Generator (Resgen.exe) utility. It can
>be embedded into a satellite assembly and distributed
>with the application."