Shared DLL Concept
Hi Guys,
I am aware of the DLL hell problem,just wanted to seek some help.In one of my applications a.dll is there which is getting delivered under C:\ProgramFiles\Appfolder.The same a.dll with the exact version is present under System32.The application is a set up capture so as a result of which in registry information shareddll information is pointed towards C:\ProgramFiles\Appfolder\a.dll.
Do we need to increase the refernce count for this?My gut feeling is this theres no need to increase tthe dll count as this is not delivered to any shared location such as commonfiles,system or system32.
kindly give your views?
Can this a.dll be used by others Apps?if yes...how?
cheers!
I am aware of the DLL hell problem,just wanted to seek some help.In one of my applications a.dll is there which is getting delivered under C:\ProgramFiles\Appfolder.The same a.dll with the exact version is present under System32.The application is a set up capture so as a result of which in registry information shareddll information is pointed towards C:\ProgramFiles\Appfolder\a.dll.
Do we need to increase the refernce count for this?My gut feeling is this theres no need to increase tthe dll count as this is not delivered to any shared location such as commonfiles,system or system32.
kindly give your views?
Can this a.dll be used by others Apps?if yes...how?
cheers!
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
ajchak
15 years ago
No theres no requirment of dll registration.Kindly note the dlls are not listed in Self Reg Table too.
i think their registration information has been captured under the registries.
i think their registration information has been captured under the registries.
Posted by:
MSIPackager
15 years ago
You are posting confusing information!
Do you know how the system32 copy is getting there? If it's part of the OS or base build and it's never likely to be removed then I'd take the one out of your package (along with all the registration info) and test.
Assuming the one in system32 is already registered your app should use that quite happily.
Regards,
Rob.
Do you know how the system32 copy is getting there? If it's part of the OS or base build and it's never likely to be removed then I'd take the one out of your package (along with all the registration info) and test.
Assuming the one in system32 is already registered your app should use that quite happily.
Regards,
Rob.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.