So my current project is a DLL that will basicly be a conduit between 2 different systems.
Without knowing anything about your situation, static linking might be an option. Often times, folks use a DLL where they could use a library instead. If your EXEs are always released in a "matched set", static linking isn't a bad way to go. It'll use extra disk space and a bit of memory when both apps are open at the same time, but this should only be an issue with older machines and/or _extremely_ large apps.
I'll second Bill's recommendation. Dependencies are a major pain and complicate distribution and installation. Steer clear unless you're going to be using that library in a large number of programs that will all be running at once.
If you have registration code in your exes, I dont see why you couldn't include it in your DLL as well. I mean if your custom exes are the only one using the DLL, they could make a call like InitDLL() which takes a the same registration key as your exes uses.
Bill & Clay: A DLL is the only way to go in this situation unfortunatly...
Fog Creek Home