RE: WinSVN: Sources of Material

(BTW, forgiveness in advance if my postings are coming out ill-formatted. I'm working on switching mail clients (again) and hopefully will have this resolved by mid-week).

> The one thing I'm concerned about here (besides licencing problems, but
> I see you're keeping on top of that) is avoiding the DLL explosion you
> usually get with Windows programs.
>
> The question here is: How many different DLLs will we have to install
> (and maintain) for a Windows GUI client?
>
> We want to avoid DLL versioning problems at all costs. I'd even lean
> towards static linking, at least for the client, where the libraries are
> relatively small.

I'd be happy to static link in the client library to the COM client, barring technical reasons which make that impractical. So managing versioning of our own code will be fairly easy.

However, DLL explosion is a factor of Windows development, not of VB. VB adds one or two runtime DLLs. Everything else (COM libraries, C/C++ runtimes, etc.) will be the same as if you were building it in C++.

I have no desire to have any more DLLs in here than needed -- after all, it only makes it more difficult for me to write the setup program.

I'll try to get an initial count and post it soonish.

Mark Murphy
mmurphy@collab.net
Received on Sat Oct 21 14:36:16 2006