Originally Posted by
michaeld
The descriptor.Resource is pretty obfuscated by the time it reaches GetUrl which means that the programmer needs to deconstruct it after you already constructed it (expensive).
The ideal would be that instead of obfuscating the resource name, instead have the parts as members of ResourceDescriptor so the user can construct it their-self.
Yes, it would be nice to have more control here. Thank you for the suggestion. We will try to do something.
Originally Posted by
michaeld
Also, I wasn't able to set ResourcesStrategyType="MyNamespace.RMStrategy" inside the ResourceManager of the as?x resource. I had to instead do it in the codebehind as
ResourceManager1.ResourcesStrategyType = typeof( MyNamespace.ExtjsCDNAlwaysStrategy );
We committed the fix. Now you can set up it via markup. However, please note that it expects the assembly-qualified name of the Type.
I.e., if the assembly is not signed, this should work.
ResourcesStrategyType="MyNamespace.RMStrategy, AssemblyName"
If signed, then:
"MyNamespace.ExtjsCDNAlwaysStrategy, AssemblyName, Version=1.0.0.0, Culture=neutral, PublicKeyToken=..."
Please also note that you can set up it on the Web.config level:
<extnet resourcesStrategyType="MyNamespace.ExtjsCDNAlwaysStrategy, AssemblyName" />
or in the Application global object.
Originally Posted by
michaeld
You're welcome to add this ResourceStrategy to your library if you'd like to give this and other controls to customers. Of course you'll have to maintain the extjs version in the path.
Thank you for the suggestion. At the moment we would prefer not to commit it leaving it under a developer's control.