tom baxter

Hello Clive,

Thank you for the response.

I attached the files to the original posting but I suspect you did not seem
them because you viewed the messages using a web client. I have attached the
files again.

As I mentioned, this is a satellite DLL but it is not specific to any
culture. It is a satellite DLL to be used regardless of the current culture.
I am not sure it is possible to use a satellite DLL independent of culture.
I would certainly hope so.

Also, recall that I created this DLL entirely outside of Visual Studio using
C# code to create the .resources file and then using al.exe to create the
DLL. I describe this in my original posting.

Below is the manifest from the DLL. The ".msresource" line is *not* prefixed
with the namespace. Perhaps this is the problem. I will continue to
investigate.


// Metadata version: v2.0.50727
..assembly ADO_1.Resources
{
.hash algorithm 0x00008004
.ver 0:0:0:0
}
..mresource public MyAppResources.resources
{
// Offset: 0x00000000 Length: 0x0000012E
}
..module ADO_1.Resources.dll
// MVID: {80AD39C8-E47D-4D5F-8132-3577D02A47D4}
..imagebase 0x00400000
..file alignment 0x00000200
..stackreserve 0x00100000
..subsystem 0x0003 // WINDOWS_CUI
..corflags 0x00000001 // ILONLY
// Image base: 0x01030000