Regarding DLL registration queries...
Hi ,
I need to get my queries cleared , if any one could please clarify the good way to come out of these situations while packaging
1.) If 10 DLL/OCX are provided to package, do we need to use WiseComCapture mechanism for every DLL/OCX?
2.) During Wise Com Capture, except the path to be changed , Is there any thing else to be edited in the resultant registry file before importing it to the package.
3.) How can we be sure that the registry generated hasn't extracted any thing common with any Shell32 DLL or any other DLL? Because I sometimes have seen that there are many GUID(s) generated inthe registry files when we use wisecomcapture DLL?
4.) How reliable is the method of using Rescan Advertising on all the components of DLL/OCX as the Wise
uses wisecomcapture.exe every time when we use Rescan advertising?
Sorry, if the questions are too basic and should already been known but please reexplain and provide comments on each points.This will be really helpful for me ...[8|]
I need to get my queries cleared , if any one could please clarify the good way to come out of these situations while packaging
1.) If 10 DLL/OCX are provided to package, do we need to use WiseComCapture mechanism for every DLL/OCX?
2.) During Wise Com Capture, except the path to be changed , Is there any thing else to be edited in the resultant registry file before importing it to the package.
3.) How can we be sure that the registry generated hasn't extracted any thing common with any Shell32 DLL or any other DLL? Because I sometimes have seen that there are many GUID(s) generated inthe registry files when we use wisecomcapture DLL?
4.) How reliable is the method of using Rescan Advertising on all the components of DLL/OCX as the Wise
uses wisecomcapture.exe every time when we use Rescan advertising?
Sorry, if the questions are too basic and should already been known but please reexplain and provide comments on each points.This will be really helpful for me ...[8|]
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
anonymous_9363
13 years ago
1. Yes. Well, that is "Yes" for every DLL/OCX that contains COM information. That was the single-most important reason why I wrote a script to automate that exercise. And before you ask, no, I'm sorry, I'm no longer sending it to people.
2. No
3. Because WCC extracts COM information only from the DLL/OCX, not its dependents. If you think about it, it would be a pretty useless tool if it did that.
4. I never use it, so shan't comment.
Don't forget that there are useless developers afoot who still haven't learned to use the switch which tells the compiler to not create the DLLRegisterServer entry-point if it's not used. The JRE NPJAVAx.DLLs are a case in point. Wise identifies these as containing COM information (presumably it uses the presence of that entry-point to determine that), will try to extract COM information from them and fail, obviously.
2. No
3. Because WCC extracts COM information only from the DLL/OCX, not its dependents. If you think about it, it would be a pretty useless tool if it did that.
4. I never use it, so shan't comment.
Don't forget that there are useless developers afoot who still haven't learned to use the switch which tells the compiler to not create the DLLRegisterServer entry-point if it's not used. The JRE NPJAVAx.DLLs are a case in point. Wise identifies these as containing COM information (presumably it uses the presence of that entry-point to determine that), will try to extract COM information from them and fail, obviously.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
