jcagle
17th July 2003 21:55 UTC
Install DLL directory?
During installation of your application, is it the norm to copy your dll to a specific directory (like C:\Windows\System???) and register it there...or do people typically just copy the dll into your "application directory" (like C:\Program Files\myapp) and register it there? Thanks in advance!!
Joel
17th July 2003 22:06 UTC
it's better to the System, it's the base dir where the apps
call the controls OCXs and DLLs...
But I think that
is OK that you can register it
from your $INSTDIR
Joost Verburg
17th July 2003 22:32 UTC
It depends on the DLL/OCX file. If it's a shared DLL file (like the VB/MFC run-time) you should put it in the System directory. DLL files for your application are usually stored in the application folder.
If you are worried about compatibility issues or backwards compatibility of a DLL file, it's better to keep your own copy.
jcagle
17th July 2003 22:57 UTC
This is NOT a shared DLL.
I was just not sure if people put their DLL's in the application folder or "hide" them in the system folder. I wasn't sure if there is a reason to not let your users see exactly what files your app is using or not. If the DLL is in your application folder, then they know what your app uses. If the DLL is in the system folder, then the user has no idea that your app uses it because they can't find it...easily. Is there any opinions on that???
Joost Verburg
17th July 2003 23:22 UTC
If the DLL is not shared, put it in your application folder.
I don't see why you should "hide" the files for the user. Any user who would want to know which files your application uses can easily check the dependencies. I also don't think there is any reason why the user should not know the filenames.