I’m in a quandry over whether to spend time setting up a common dll file for my program package. I thought using DLL’s as “Best Pratice” or “Best of Breed”. The following statement from an expert started me to thinking about this.
“If you don’twant to register DLLs, don’t use them. Nothing says you have to. Make sure there are specific reasons you are creating DLLs. Mainly speed or to apply a 3-tier architecture especially if your DLL is going to reside on the server and is separating the UI from direct access to the data source. Also creating a DLL is not the same as a COM object. COM objects (that just happen to be compiled to DLL) have specific entry and exit points as well as using interfaces. There is a lot more to creatingCOM than just compiling a DLL.”
My requirements are to:
– Provide access to about 100 functions from various programs
– Run no more than 4 of the programs at the same time
– Keep task sizes under 500K (This can be done w/o Dll)
– Make the programs understandable when I look at them a year from now
– Speed is not a problem
– Following program best practices. (Sometimes we have too many choices … and sometimes not)
Could someone comment on whether I need to bother with creating a DLL or not?