File Registration Information Extraction
Hi all,
Does anyone know of any other Registry info extraction tools other than Tallow(Heat) from the WiX toolkit or Regasm /regfile. I was thinking of using a combination of both since RegAsm with /reg file will not extract type library interface information.
The reason I ask is that with Wise, I get files that aren't registered properly following install. I was hoping to maybe extract registration information pre build, create a .reg file and import into Wise with all of the information needed.
We recently purchased InstallShield 2010 and I can't get any registration information scanned from files at all. I currently have an incident logged with their Support on this. I can't imagine they don't have some type of scanning.
Anyway, if anyway has any information on this stuff or how to properly register .dlls and .ocxs so that I can rest at night, please let me know.
For now, our workaround is to run RegAsm Custom Actions, but these become a bear of sorts on Vista/Win 7.
Thanks for any info!
Does anyone know of any other Registry info extraction tools other than Tallow(Heat) from the WiX toolkit or Regasm /regfile. I was thinking of using a combination of both since RegAsm with /reg file will not extract type library interface information.
The reason I ask is that with Wise, I get files that aren't registered properly following install. I was hoping to maybe extract registration information pre build, create a .reg file and import into Wise with all of the information needed.
We recently purchased InstallShield 2010 and I can't get any registration information scanned from files at all. I currently have an incident logged with their Support on this. I can't imagine they don't have some type of scanning.
Anyway, if anyway has any information on this stuff or how to properly register .dlls and .ocxs so that I can rest at night, please let me know.
For now, our workaround is to run RegAsm Custom Actions, but these become a bear of sorts on Vista/Win 7.
Thanks for any info!
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
Jsaylor
14 years ago
Try using Wisecomcapture, you should have it lying around if you still have your Wise licenses. Usage is pretty simple, This comment seems to explain it adequately.
Posted by:
anonymous_9363
14 years ago
WCC won't extract registration information from .Net assemblies since, strictly speaking, they don't contain COM information. RegASM is NOT the same operation as RegSvr32.
If we're talking regular DLLs, if Wise isn't capturing the registration information, you have it set up incorrectly. Rather than repeat thread content, use AppDeploy's Search facility to look for WiseComCapture and you'll turn up the steps required.
The same applies for IS. From a brief flirtation, 2010 isn't that different to previous incarnations and should be set to extract COM information during capture. I seem to recall IS too has a stand-alone extractor, but don't quote me on that.
Both products should be set to use the advertising tables rather than the SelfReg table (or ISSelfReg in IS's case) or [shudder] RegSrv32/MSIExec /Y.
If we're talking regular DLLs, if Wise isn't capturing the registration information, you have it set up incorrectly. Rather than repeat thread content, use AppDeploy's Search facility to look for WiseComCapture and you'll turn up the steps required.
The same applies for IS. From a brief flirtation, 2010 isn't that different to previous incarnations and should be set to extract COM information during capture. I seem to recall IS too has a stand-alone extractor, but don't quote me on that.
Both products should be set to use the advertising tables rather than the SelfReg table (or ISSelfReg in IS's case) or [shudder] RegSrv32/MSIExec /Y.
Posted by:
dnmech
14 years ago
U can try to use Wisecomreg.exe. this is a also third party tool. You can extract the .dll information to a reg file and then u can import it.
Hope this helps.
Cheers!
Hope this helps.
Cheers!
Posted by:
spartacus
14 years ago
ORIGINAL: VBScab
I seem to recall IS too has a stand-alone extractor, but don't quote me on that.
That will be RegSpyUI.exe (installed to C:\Program Files\InstallShield\2010\Support by default)
Regards,
Spartacus
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
