Comments on: Proceed with Caution: Strongly Typed Resources Ahead

By: leppie

leppie — Mon, 22 Oct 2007 07:46:51 +0000

You are right too! I investigated a bit further. It seems the RuntimeResourceSet (internal class) does not perform any caching, while it’s base class ResourceSet, does cache, which is what you would expect.

Not sure if this a bug, perhaps

By: aaron

aaron — Sat, 20 Oct 2007 02:50:45 +0000

Thanks leppie

While what you say is true, your explanation still fails to explain why the following line of code (using my example above) asserts:
Debug.Assert(Properties.Resources.LockIcon == Properties.Resources.LockIcon);

The same references are not equal, therefore the same object is not being returned.

Maybe if the resx file contained the base-64 encoded bits of the image it might return the same instance, but look at the resx file for the particular resource – here’s mine for the example:

..\Resources\lock16.png;System.Drawing.Bitmap, System.Drawing, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a

The ResXFileRef is just a container that uses a TypeConverter to return the appropriate type it points to.

I don’t have enough time tonight to trace through exactly what’s going on in the ResourceManager (and below) to know what’s happening – it’ll be nice to get my hands on the source when they release it with .NET 3.5!

By: leppie

leppie — Fri, 19 Oct 2007 13:35:30 +0000

The information you are providing is incorrect. The ResourceManager contains a ResourceSet which in turn contains a Hashtable. The Hashtable is populated when a ResourceSet is created. When GetObject is called on the ResourceManager, the already created value will be retrieved from the ResourceSet’s Hashtable, and will NOT be recreated.

This can be clearly seen by looking at the classes in Reflector.

By: mike

mike — Thu, 18 Oct 2007 03:58:26 +0000

Yeah, I really thought those were static resources. That’s pretty bad and non-intuitive like you pointed out.