Re: Internationalization


"Pete Delgado" <Peter.Delgado@xxxxxxxxx> wrote in message
news:egRRcuLSIHA.5128@xxxxxxxxxxxxxxxxxxxxxxx

"Thomas Mooney" <tfm3@xxxxxxxxxxxxxxxxxxx> wrote in message
news:eNKjw7KSIHA.1208@xxxxxxxxxxxxxxxxxxxxxxx
Greetings,

I have an application that my client wants to internationalize. I've
read
Microsoft's Knowledgebase article on the topic:

http://support.microsoft.com/kb/198846/en-us

It states "use MFC library as a shared DLL." I have always preferred
"use
MFC in a Static Library."

Just out of curiosity, why do you prefer to do this? I can think of
several
valid reasons, but I wonder what your reasoning is.


I prefer to ship exactly what I have tested. The shared DLL approach
results in a situation where a problem could arise on a machine-by-machine
basis dependent on what the end user has installed. I have zero control
over that so I prefer to exercise control where I can. This may be less of
an issue today, but I've been doing this long enough to have painful
memories of DLL mismatches we referred to as DLL hell. Some traumas leave a
lasting impression. <g>

My 2¢

.

Relevant Pages

  • Re: A tricky one...
    ... This seems, that all of your information is in the shared dll you have, ... Client exe/dll: ... public bool Supports(Type objType) ... congratulations if you can understand my terrible English. ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: Returning an Enum From A Remote Service?
    ... I haven't really tried this but is your enum serializable?... ... the service to the client. ... I have defined the enum in a shared DLL ... Any pointers? ...
    (microsoft.public.dotnet.framework)
Loading