"Creating Custom Cultures in the .NET Framework 2.0" MSDN Webcast Available For Download

If you missed Tuesday’s "Creating Custom Cultures in the .NET Framework 2.0" MSDN Webcast you can now download it here. The source code mentioned in the webcast can be downloaded here. Chapter 11 of .NET Internationalization, Creating Custom Cultures, can be downloaded here.

Enjoy.

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Posted by: Guy Smith-Ferrier
Posted on: Friday, July 14, 2006 at 1:00 AM
Categories: Events
Actions: E-mail | Kick it! | DZone it! | del.icio.us
Post Information: Permalink | Comments (4) | Post RSSRSS comment feed

Related posts

Comments

Dennis Parks

Saturday, July 15, 2006 2:00 AM

Dennis Parks

Guy:
I just read your culture article, and I want to try it out for myself.
I have a problem (I think).
You first say not to use the AJAX Web Site Project because it can’t access an assembly, but when I fire up VS 2005 SP1, I don’t have an "ASP.NET AJAX Enabled Web Application" in my project templates for FILE | NEW | PROJECT.

I do have however ASP.NET AJAX Control Project, and the regular ASP.NET Web Application.

When I do FILE | NEW | NEW WEB SITE:
I have the ASP.NET AJAX-Enabled Web Site.

I’m not sure what to do?
Can you email me the solution?
Thanks Much!
Dennis Parks, Beaverton Oregon

Guy Smith-Ferrier

Saturday, July 15, 2006 2:00 AM

Guy Smith-Ferrier

Patrick,

(Apologies for the delay - I have been away).

Yes, your scenario is entirely possible. The custom culture approach is certainly a good approach for allowing the customer to override the default resources. (Obviously you must make sure that the de-DE-custom culture has a parent of de-DE).

The harder issue to resolve is the integration of the resources into the application. As you intend to use custom cultures it is safe to assume that you are using the .NET Framework 2.0. However, an important issue is whether the application is an ASP.NET or Windows Forms app. If it is an ASP.NET 2.0 application then the problem is not a big one because ASP.NET recognizes changes to .resx files and reloads the application. If your application is a Windows Forms application you must rebuild the satellite assemblies. http://www.dotneti18n.com" target="new">Chapter 14, The Translator goes into both scenarios in depth.

Guy

Patrik

Saturday, July 15, 2006 2:00 AM

Patrik

Hi Guy

I read your sample chapter. Good stuff and easy to read!

I’d like to implement the following scenario: we deliver resources to the customer. But the customer translates or changes the resources, too. I should have this fallback: If there is a customer translation: use it. If not: the application should use our own translation. It sounds to me like e perfect use for CustomCulture. How would you implement this? Idea: the customer compiles his resources as de-DE-custom (or de-custom). We compile our resources as de-DE (or de) thus the fallback will work. What do you think? Do you have another approach?

Can’t wait to read the other chapters!
Thanks, Patrik

Guy Smith-Ferrier

Saturday, July 15, 2006 2:00 AM

guy[at]guysmithferrier[dot]com

Dennis,

Hopefully the answer I sent by email clears this one up.

Guy