Thank you for you advices.
> > 1)What should I do to make COMs registering?
> SelfRegCost="1" is required to perform MSI SelfReg
> <File Id="AttachW.ocx" LongName="AttachW.ocx" Name="ATTACHW.OCX"
> Source="Libs\AttachW.ocx" SelfRegCost="1" />
> (1 is ok for registry entries it is used for progress bar)
Yes, but my question idea was:
*How to* invoke tallow to *force* it scanning the directory with COMs
and *generating
for all* those COMs separate components, for each, in one fragment wxs file,
with registration information.
I do not want self registration.
> Basically adding the com registry information with separate wix registry
> entries is the preferred way and
> SelfReg should be avoided (search wix-users List for SelfReg)
> Heat could also produce the tallow layout when using -scom and/or -sreg
> parameters see
> http://www.wixwiki.com/index.php?title=Heat
Once more: Is VB6 COMs registration supported in WIXv3 for now?
Because a few weeks ago I was informed that not, because of some bug.
That is why I have moved backward to WiXv2, so* I have* to use that "ugly" *
tallow* instead of heat.
For now, I am writing tool that scans directory and invokes tallow for all
files from directory separately, then it modifies tallow's output (adds
feature node, removes warnings, and other things) files and creates merged
feature WXS file that contains references to features from those separate
fragments' files.
This will also allow me not to modify GUIDs for COMs components that are not
changed, when generating new setup.
Now it looks working registering some example files.
Once more, thank you for your suggestions.
Best regards,
Peter Jaworski
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
