The smallest deployment unit that exist in .NET is an assembly, but when you create an assembly (*.dll, *.exe), this makes them like small islands to comunicate them you need to use things like .NET Remoting to be able to let them talk, but the use of such power solution will make sense only if you are talking about processes(running in the back) or executable applications because either a private or public dll can be used in many applications at the same time with no problems. Hope this help

No problem, I trust thats what you where looking for?

I see where is the ouput directory, but not the obj directory, in project settings. It is a C# project not a C++ project. The project settings are different.

Thank you, I'll see this. Freg

thank you

We are calling it the InitInstance of the application. Then all the dialogs / views are set up with the correct strings. If you want to change the language at runtime, you have to call this language first and then "refresh" all your views / menus whatever. (Set the item texts with the new strings from the resource table) (But this whole process depends on the structure of the program) More information on SetThreadLocal http://msdn.microsoft.com/library/default.asp?url=/library/en-us/intl/nls\_52lh.asp Regarding your exact question: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/intl/nls\_7qck.asp All the label says is that this stuff contains chemicals "... known to the State of California to cause cancer in rats and low-income test subjects." Roger Wright http://www.codeproject.com/lounge.asp?select=965687&exp=5&fr=1#xx965687xx