Peter Jaworski wrote:
>
> Oh, that is a good news, but COM+ are used when for example I would like
> to
> use VB6 COMs from .net applications, does it true?
>
Hi Peter,
not really. Com+ is a transactional hosting container it can be used either
by legacy (VB6) COM components or by .Net Enter
>
> I see, seems I was on the wrong direction. Sorry, but then I could not
> help
> you further.
>
Anyway thank you.
>
> If your question on VB6 Com support based on discussion regarding
> ComplusExtension
> http://www.nabble.com/WixComPlusExtension-in-Wix-v3-td14923013.html
> then I could state t
Peter Jaworski wrote:
>
> 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.
>
I see, seems I was on
Peter Jaworski wrote:
>
> After build and installation of such setup (where has been used WXS file
> produced by tallow) COMs are not registered.
>
> 1)What should I do to make COMs registering?
>
SelfRegCost="1" is required to perform MSI SelfReg
(1 is ok for registry entries it is used f
I have used following tallow invocation (from WiX2.0.5805.0):
tallow -nologo -1 -d Libs -gg > Libs1.wxs
adding -s switch causes error for directory, but I do not want to
invoke it for every file separately.
Regards,
Peter Jaworski
-
Hello,
I have approximately over 300 VB6 COMs that should be registered.
I have tried previously, when using WiXv3, use heat to scan directory with
components and produce output WXS file.
Because there is currently no support for VB6 COMs in WiXv3 I have moved to
WiXv2 and instead I have used tallo
6 matches
Mail list logo
