Re: ? Segregating a Dialog's Code (Particularly Resources)

I use this approach too when I have to, but I try to embed as many of the
language resources in my main applications DLLS so as to not have to have
extra ones. I just get annoyed when my application requires 30 5K DLLs.

You are right that they don't all have to be installed. For me it's more of
a maintenance issue. I'd still rather take the time to copy resources to my
project as needed rather than try to create a DLL with one or more dialogs
in it that I use a lot. Of course, I only have a few applications to
maintain. If I had to constantly change the same DLL in all of them I may
change my mind.

Tom

"Ajay Kalra" <ajaykalra@yahoo.com> wrote in message
news:2a018983-d694-4707-8372-6dda9edc755e@v42g2000yqv.googlegroups.com...
On Jan 31, 1:13 am, "Tom Serface" <t...@nospam.camaswood.com> wrote:

That is how we did it and it worked beautifully, We gave only specific
DLL to a particular group to translate. At installation time, only a
specific version of DLL was shipped. That is how its usually done.
This is a good thing IMO.

--
Ajay