Chris
Tue Mar 27 18:41:43 CDT 2007
I've run into exactly the same problem, and there are a few ways to work
around it. The underlying problem is, as you point out, that the generator
marks everything as internal.
These easiest way for me to work around this is was to have the attribute:
[assembly:
InternalsVisibleTo("Coversant.SoapBox.Services.Translation,PublicKey=0024...")]
present in my resource assembly. I was able to do this, as I know exactly
what assemblies are going to need access to the resource files. Doing this
allowed me to have a
"Coversant.SoapBox.xxx.Common" assembly that has all of my resources. The
other assemblies then use these resources as if they were public. It works
just fine.
The only tricky part was getting the public key signature right - I used
ildasm for that. If you're not strong naming your assemblies, then I would
imagine you can skip that step.
--
Chris Mullins, MCSD.NET, MCPD:Enterprise, Microsoft C# MVP
http://www.coversant.com/blogs/cmullins
"Alexander Kolev" <AlexanderKolev@discussions.microsoft.com> wrote:
>I create a class library. Then I add default resource file to support
> globalization and add strings. I want to use these resource strings
> outside
> of this assembly, but I see that the generator makes all strings as
> internal
> static properties.
> Is there any way to make them public, so I can use them from another
> assembly?
>
>