When you plan to make your project multi-language and you are nearing its completion it is not smart to put those resource strings on a .resex files and edit right from your IDE. Why? Simply because it is not maintainable and hard to track changes whenever you add new entries. Also, your translators...

In few days I have to hire a Danes translator and I wanted it to be easy for her to encode[:) of course!] and be guided properly what to put in. Initially I thought a friendly naming on resource ids is sufficient, but I was wrong. It won't help her because different pages share the same resource strings...

When you are developing software product to be catered to diverse customers, it must be a standard to localized your software. With .NET this has never been easy, on .NET 2.0 its even easier with striongly typed resource files. But localizing application must be part of the architectture and should not...

Today, I have written a service to be deployed on a server to manage creation/tracking of orders and manage sending different emails to customers. I designed it to be multi-threaded and at first I want to use System.Threading.Timer but its complexity is not suited on a simple server process like my requirement...