OK, I know it's a perenial question but here goes:

I have a number of classes (in fact data object classes) that are used by a number of applications. Some of those applications are straight forward .EXE on a WINNT network, some use DCOM accross a WAN. Shortly some will need to be used in an ASP web page.

I want to split these classes out from the .EXE files so that I can maintain them seperately.

Should I ;
a) make them into COM objects in a .DLL
b) distribute the compiled .VCX files (code removed)
c) forget it .EXE is the fastest and best

a) makes me worried about overheads and also the WAN application uses a "controller" object to create and return objects (saves registering lots of COM objects and also handles all IP validation and system status). Don't see a DCOM object creating COM objects local as being an ideal!

b) makes me worry about decompilation and does'nt seem 21st century! Also I end up with VCX & VCT files, not neat.

c) I don't like because small changes require a new .EXE

As you can see I can argue AGAINST each option! anyone like to join in my internal struggle?


Gary Williams