[Mono-winforms-list] Important ResourceManager notes

Rafael Teixeira monoman at gmail.com
Fri Jun 10 13:34:50 EDT 2005

I suggest to have our ResourceManager be smarter than MS's one, and
first search non-neutral resources in the main assembly and just try
the sattelite ones if not found. That way we are compatible with
VS.NET projects generated assembly-sets but can accomodate a basic set
of localizations in just one assembly, what would be nicer to compile
and package/distribute.

Or maybe the order should be reversed to allow for updated
localizations being distributed as sattellites and override the basic
internal set. Opinions are welcome.


On 6/10/05, Kornél Pál <kornelpal at hotmail.com> wrote:
> Hi,
> I am about post an extenive ResourceManager patch.
> I am still working on the test unit to make discover the correct behaviour
> of ResourceManager and prevent regressions.
> There were a lot of differences between Mono and .NET Framework
> implementation.
> The most important that will break Managed.Windows.Forms is that neutral
> resources has to be read from the main assembly any other resources has to
> be read from the appropriate satellite assembly.
> System.Windows.Forms.dll contains all the cultures of resources in the main
> assembly and only the neutral resources will be available in ResourceManager
> after the patch.
> Note that this change does not effect GetManifestResourceStream but it
> should not be used with localizable resources. (Managed.Windows.Forms is not
> using GetManifestResourceStream for localization)
> Kornél
> _______________________________________________
> Mono-winforms-list maillist  -  Mono-winforms-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-winforms-list

Rafael "Monoman" Teixeira
I'm trying to become a "Rosh Gadol" before my own eyes. 
See http://www.joelonsoftware.com/items/2004/12/06.html for enlightment.
It hurts!

More information about the Mono-winforms-list mailing list