In my modules I use a form of Image Localization and I thought I'd bring it up as a possible future enhancements.

Basically, I use an ASPX page called ImageResource.aspx and that expects a single QueryString item called img. Then it takes the value of "img" attaches .Url to the end and localizes it using a Resource File in my module's App_LocalResources called Images.ascx.resx (The ASCX makes it show up in the Language Editor). Images.ascx.resx contains a bunch of keys of the form [ImageKey].Url = [ImagePath] so for example: Edit.Url = ~/images/edit.gif.

Once this path is retrieved, ImageResource.aspx strips out the '[L]' added by DNN 4.3 if necessary and uses Reponse.WriteFile and Server.MapPath to dump the image file out. That seems to work great for my modules except that because ImageResource.aspx is in my module folder, getting the Url can be annoying (don't like putting /DesktopModules/MyModule/ImageResource.aspx, so I use Control.ResolveUrl("ImageResource.aspx"), which adds complexity). However, a core Image Resource system would be able to fix that issue.

I think that this would be a great idea for Core integration. There could be an HttpHandler that handles [ImageKey].image.ashx and then dumps out the image with that Key using a global Images resource file to resolve the Urls. Perhaps functionality could be included to allow for module-specific Image resource files too.

Just thought I'd throw the idea out there, I have working code for my ImageResource.aspx if anyone wants it (but its not a very complicated task)

---

Andrew Nurse
DotNetNuke Core Team Member and Reports Module Project Lead
Microsoft Certified Professional Developer