AncientTiger
Programmer
I'm working on a new project and it has the potential of going out to different offices. The trouble is that our tech folks don't coordinate well with what I'm doing, and have several times in the past come in, did an upgrade, and royally jacked up my apps dependency files (incorrect registration errors, changed directories, you name it).
I was wondering if there's a way that I could gather up all the dependency files (dll's, ocx's, tlb's, etc) and put them into a subdirectory along with my .exe, then in turn have the .exe self-register them from that directory at runtime.
Also, could this possibly interfere with other programs on the target machine? For example, if the comdlg32.dll file is used by my app and is located in the apps folder, and other programs uses the version in the system32 folder, would my app registering it just cause two entries, or would it overwrite the existing registry entry, thus potentially jacking up their stuff?
------------------------------------
![[yinyang]](/data/assets/smilies/yinyang.gif "[yinyang] [yinyang]")
Over 20 years of programming, and still learning every day!
I was wondering if there's a way that I could gather up all the dependency files (dll's, ocx's, tlb's, etc) and put them into a subdirectory along with my .exe, then in turn have the .exe self-register them from that directory at runtime.
Also, could this possibly interfere with other programs on the target machine? For example, if the comdlg32.dll file is used by my app and is located in the apps folder, and other programs uses the version in the system32 folder, would my app registering it just cause two entries, or would it overwrite the existing registry entry, thus potentially jacking up their stuff?
------------------------------------
Over 20 years of programming, and still learning every day! 
