I presented at ASPLive! and TechEd 2003 on Internationalizing ($g(i18n)) ASP.NET. I know that the story changes with Whidbey and changes dramatically post-Whidbey, but until then...what are the best practices for ASP.NET 1.1? DasBlog is a good example, as is (IMHO) the code I showed at the conferences. Each takes certain approaches for performance vs. ease of i18n vs. avoiding $g(code smell).
Some random thoughts, some questions, some rethorical, some I could use comments/thoughts on:
This and other questions burn...time to refactor...Now this looks like an interesting tool that makes ASP.NET localization more like WinForms localization. I'll check out the trial, but I suspect it will break down when faced with complex ASP.NET DataGrids (definitely non-trivial to localize).
Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. I am a failed stand-up comic, a cornrower, and a book author.
Disclaimer: The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.