http://blogs.law.harvard.edu/brandonhaynes/2008/10/29/a-second-look-enabling-aspnet-20-localization-in-a-dotnetnuke-application-2/ Observations about the intersection of technology, business, and intellectual property Wed, 21 Oct 2009 16:16:51 -0400 http://wordpress.org/?v=2.8.4 hourly 1 http://blogs.law.harvard.edu/brandonhaynes/2008/10/29/a-second-look-enabling-aspnet-20-localization-in-a-dotnetnuke-application-2/comment-page-1/#comment-1646 Brandon Haynes Wed, 17 Jun 2009 21:28:40 +0000 http://blogs.law.harvard.edu/brandonhaynes/?p=33#comment-1646 As I recall, this will be difficult to resolve without registering custom languages on the installation machine. I will take a look at extending functionality to cover this case. As I recall, this will be difficult to resolve without registering custom languages on the installation machine. I will take a look at extending functionality to cover this case.

]]> http://blogs.law.harvard.edu/brandonhaynes/2008/10/29/a-second-look-enabling-aspnet-20-localization-in-a-dotnetnuke-application-2/comment-page-1/#comment-1644 Walt Garfield Wed, 17 Jun 2009 18:31:41 +0000 http://blogs.law.harvard.edu/brandonhaynes/?p=33#comment-1644 For the most part this works well. The only gotcha I found when using with 5.0.1 is when a user makes changes to the base resx file which then has a Portal-0.resx prior to the .resx as user edits to the base resx file. Standard resourcekeys references work but not those referenced as meta:resourceykey. Do you see any way this can be resolved? For the most part this works well. The only gotcha I found when using with 5.0.1
is when a user makes changes to the base resx file which then has a Portal-0.resx prior to the .resx as user edits to the base resx file. Standard resourcekeys references work but not those referenced as meta:resourceykey. Do you see any way this can be resolved?

]]> http://blogs.law.harvard.edu/brandonhaynes/2008/10/29/a-second-look-enabling-aspnet-20-localization-in-a-dotnetnuke-application-2/comment-page-1/#comment-22 From the Desk of Brandon Haynes » Enabling ASP.NET 2.0 Localization in a DotNetNuke Application Wed, 29 Oct 2008 16:16:56 +0000 http://blogs.law.harvard.edu/brandonhaynes/?p=33#comment-22 [...] Editor’s note: This approach has been obsoleted in favor of the more straightforward, core-friendly ASP.NET 2.0 Localization approach outlined here. [...] [...] Editor’s note: This approach has been obsoleted in favor of the more straightforward, core-friendly ASP.NET 2.0 Localization approach outlined here. [...]

]]>