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

HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsLanguage PacksLanguage PacksLocalization for custom modules .. strange VS behaviorLocalization for custom modules .. strange VS behavior
Previous
 
Next
New Post
4/10/2007 10:22 AM
 
Hi,

Sorry if I'm asking this in the wrong forum, but I am completely stumped over a particular VS2005 behavior and I thought someone else might have run into it.

I've developed a simple custom control, DesktopModules/Test/Test.ascx, that simply displays a label. This label would of course be suitable for localization, and thus, I've clicked on "generate local resource", which creates an App_LocalResources/Test.ascx.resx file.

Now, as soon as I hit "build page" on Test.ascx, VS reports a validation/build error: "Object reference not set to an instance of an object". It points to the first line in the ascx file, but there's really nothing there to complain about. If I delete the *.resx file(s), it builds fine. Add the resx file again, boom, error. In fact, all I have to do is create a directory called App_LocalResources in that subdirectory for it to go boom.

I managed to create a standalone website, with a custom control in a subfolder, containing localization files, by first of all moving the App_LocalResources folder into the root, then hitting Build Website, then moving them back again into the subfolder, hitting Build Website again, and then I can hit "Build Page" fine, even again and again. But when I try the same stuff within the DNN project, it goes boom again.

Why? Why, oh why? Is this a bug within Visual Studio? Am I doing something wrong? I get the same thing on another guy's machine, and he's running XP, not Vista as I am. We've both got the latest service packs for Visual Studio.

Why? ("Why, Mr. Anderson? Why do you do it? Why get up? Why keep fighting? Do you even know? Why do you persist?")

Thankful for any help,
Matt
 
New Post
8/4/2007 7:22 AM
 

Hey,

Did you get to the bottom of this?  I seem to be experiencing the same phenomenon.....

Thanks,

Olly

 
New Post
8/4/2007 11:19 AM
 

     The dnn localization is implemented since asp.net 1.1, It is very similar as asp.net 2.0 localizaion implementation but have  diffrence. Please see DotNetNuke Localization.pdf  for detail . you can find this file in DotNetNuke_4.4.1_Docs.zip


Over 20 + professional dnn modules for News Article, Store, Video Gallery, Photo Gallery, Ultra Flash Player,YouTube Video, Image Slide show, Skin Chameleon and much more from DnnModule.com
 
New Post
8/5/2007 11:46 AM
 
Olly,

Nope, never did. Since asking, I've washed my hands of any custom DNN development, hired a consultant to work out the messy details instead, and am now happily working with php again.

Regards,
Mats Gefvert
 
New Post
8/6/2007 1:34 AM
 

I suggest also to check out the tutorials from Michael Washington at dotnetnuke.adefwebserver.com, AFAIR at least one demonstrates, how to utilize resource files.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsLanguage PacksLanguage PacksLocalization for custom modules .. strange VS behaviorLocalization for custom modules .. strange VS behavior


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