| |
|
|
|
|
|
|
|
|
|
 |  | |
| | |
| | |
| | |
 | | |
|
|
|
| Localization for custom modules .. strange VS behavior |
|
|
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 |
|
|
|
| |
|
|
| Re: Localization for custom modules .. strange VS behavior |
|
|
Hey,
Did you get to the bottom of this? I seem to be experiencing the same phenomenon.....
Thanks,
Olly |
|
|
|
| |
|
|
| Re: Localization for custom modules .. strange VS behavior |
|
|
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 |
|
|
|
| |
|
|
| Re: Localization for custom modules .. strange VS behavior |
|
|
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
|
|
|
|
| |
|
|
| Re: Localization for custom modules .. strange VS behavior |
|
|
|
|
| |
| | |
| | |
| | |
|  |
| |
|
|
|
These Discussion Forums are dedicated to the discussion of the DotNetNuke Web Application Framework.
For the benefit of the community and to protect the integrity of the project, 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 DotNetNuke.
2. Discussion or promotion of DotNetNuke product releases under a different brand name are strictly prohibited.
3. No Flaming or Trolling.
4. No Profanity, Racism, or Prejudice.
5. Site Moderators have the final word on approving/removing a thread or post or comment.
6. English language posting only, please.
|
| |
|
|
|
|
|
|
|
|