Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Language and In...Language and In...Custom server control RESX file locationCustom server control RESX file location
Previous
 
Next
New Post
3/3/2008 2:21 PM
 

I am nearing completion on my image editing and upload custom server control and am wondering where best to place the localization (resx) file.  As this is a custom server control (no .ascx file) rather than a usercontrol and since I anticipate it will be used in any number of modules by multiple developers I cannot find in the localization documentation nor in forum searches the best practices for placement of the resx file.  In testing, I have simply placed it in the App_LocalResources folder of my test module's folder.

Several choices for location come to mind. Please advise your recommendations:

  1. Add the localization keys and values to the SharedResources.resx located in the site's App_GlobalResources folder. This is where many of the framework control's localization values are kept. I feel, however that this file (as well as GlobalResources.resx in the same folder) should be reserved for use by core controls only.
  2. Add the localization file (WESNet_ImageEditorControl.resx) to the App_GlobalResources folder.  This would be my #2 choice, but I need to know if the App_GlobalResources folder should be reserved for core localization only.
  3. Add the localization file to the site's controls/App_LocalResources folder. Most of the core usercontrols place their localization files in this folder. This would be my #1 choice, but I am concerned if this folder should be reserved for core control localization only.
  4. Add the localization file to a new sub-folder in the site's Resources folder.  Although this would seem a good choice I don't see any other localization files there.

Since I can code the server control to reference the localization file from just about anywhere, let's hear your suggestions. BTW, when ready, the control source and demo/test module will be released as an open source project on Forge/CodePlex.


Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
3/4/2008 10:39 AM
 

Bill,

I am not sure that there really is a "standard" for this.  I personally like keeping the files inside the App_LocalResources folder for my specific module....but it really depends on the specific implementation.

I would caution against placing files in areas where the core puts files, just as an overall best practice.  In my opinion anyway.


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Language and In...Language and In...Custom server control RESX file locationCustom server control RESX file location


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out