Re: [WiX-users] Heat and vb6 dll?
That list matches the areas I remove, I'm afraid the only way to be sure
is to remove them then test on a clean machine - I recommend using a VM
for this, if you don't already, so you can keep rolling it back. Another
approach is too look at the output from a non-VB6 COM component and only
leave in the bits it has, if my memory serves me right you should only
need one or more progids that point at classids and the classid may
point at a typelib entry - somewhere in the mix there can also be an
appid entry.
I hope this helps.
Neil
From: Cheyne, Mark A - DNR [mailto:[EMAIL PROTECTED]
Sent: 13 June 2007 22:05
To: Neil Sleightholm; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Heat and vb6 dll?
I had a hunch about that, just a bit timid with the knife.
What do you think the definition of 'unnecessary' is?
If I were to guess, I'd hack out , ,
elements that refer to things not defined in my DLL itself. For example,
in my heat-generated *.wxs I see a element for VBPropertyBag, a
for msvbvm60.dll, two elements for a
helpdir in system32, a for VBA, and a for Visual
Basic runtime objects and procedures.
Thanks, Mark
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Neil
Sleightholm
Sent: Wednesday, June 13, 2007 3:51 PM
To: Cheyne, Mark A - DNR; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Heat and vb6 dll?
In my experience I have found you need to remove the detritus
that Microsoft feels the need to include during the self registration of
VB6 COM DLLs. So basically I use heat/tallow as a guide to save time,
then hack out all the unnecessary items.
Neil
From: Cheyne, Mark A - DNR [mailto:[EMAIL PROTECTED]
Sent: 12 June 2007 23:45
To: Neil Sleightholm; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Heat and vb6 dll?
As Neil's reply is actually a solution to my other post:
http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg09440.htm
l
I thought I'd restate _this_ problem, which remains unsolved.
The problem here is that I run heat.exe on a VB6 DLL that I
authored, as a way to generate a *.wxs file containing a with
all the COM registration muck I need to install and register that DLL.
The problem is that the output *.wxs contains errors that prevent me
from building. See my enumeration of errors 1, 2, 3 at the bottom of
this thread.
Any thoughts? These errors refer to a class and typelibs that
are part of VB6 itself, not my DLL, and yet heat.exe emits (erroneous,
incomplete?) metadata about them when I point it at my DLL.
Thanks, all - I'm almost there! Mark
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat and vb6 dll?
I had a hunch about that, just a bit timid with the knife.
What do you think the definition of 'unnecessary' is?
If I were to guess, I'd hack out , ,
elements that refer to things not defined in my DLL itself. For example,
in my heat-generated *.wxs I see a element for VBPropertyBag, a
for msvbvm60.dll, two elements for a
helpdir in system32, a for VBA, and a for Visual
Basic runtime objects and procedures.
Thanks, Mark
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Neil
Sleightholm
Sent: Wednesday, June 13, 2007 3:51 PM
To: Cheyne, Mark A - DNR; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Heat and vb6 dll?
In my experience I have found you need to remove the detritus
that Microsoft feels the need to include during the self registration of
VB6 COM DLLs. So basically I use heat/tallow as a guide to save time,
then hack out all the unnecessary items.
Neil
From: Cheyne, Mark A - DNR [mailto:[EMAIL PROTECTED]
Sent: 12 June 2007 23:45
To: Neil Sleightholm; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Heat and vb6 dll?
As Neil's reply is actually a solution to my other post:
http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg09440.htm
l
I thought I'd restate _this_ problem, which remains unsolved.
The problem here is that I run heat.exe on a VB6 DLL that I
authored, as a way to generate a *.wxs file containing a with
all the COM registration muck I need to install and register that DLL.
The problem is that the output *.wxs contains errors that prevent me
from building. See my enumeration of errors 1, 2, 3 at the bottom of
this thread.
Any thoughts? These errors refer to a class and typelibs that
are part of VB6 itself, not my DLL, and yet heat.exe emits (erroneous,
incomplete?) metadata about them when I point it at my DLL.
Thanks, all - I'm almost there! Mark
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat and vb6 dll?
In my experience I have found you need to remove the detritus that Microsoft feels the need to include during the self registration of VB6 COM DLLs. So basically I use heat/tallow as a guide to save time, then hack out all the unnecessary items. Neil From: Cheyne, Mark A - DNR [mailto:[EMAIL PROTECTED] Sent: 12 June 2007 23:45 To: Neil Sleightholm; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Heat and vb6 dll? As Neil's reply is actually a solution to my other post: http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg09440.htm l I thought I'd restate _this_ problem, which remains unsolved. The problem here is that I run heat.exe on a VB6 DLL that I authored, as a way to generate a *.wxs file containing a with all the COM registration muck I need to install and register that DLL. The problem is that the output *.wxs contains errors that prevent me from building. See my enumeration of errors 1, 2, 3 at the bottom of this thread. Any thoughts? These errors refer to a class and typelibs that are part of VB6 itself, not my DLL, and yet heat.exe emits (erroneous, incomplete?) metadata about them when I point it at my DLL. Thanks, all - I'm almost there! Mark - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat and vb6 dll?
D'oh! I had forgotten about the "EnsureTable" fix (referenced in earlier messages). All but one of my VB installations had been updated to use that. Naturally, the one I looked at before sending the previous message was the one that wasn't (but contains assorted comments about building without validation). Put it down to too much blood in the caffeine stream this morning! :-) Regards, Richard From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Foster, Richard - PAL Sent: Wednesday, June 13, 2007 8:29 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Heat and vb6 dll? [Trimmed to only include ill advised comment] Personally, for the few VB6 projects I have under WiX, I make the inclusion of the merge modules conditional build and validate (run smoke) without them, then build again including them but turn off the validation. Yup, it's ugly. Yup, I don't want to turn off validation. Sometimes you just have to do what you can. * C O N F I D E N T I A L I T Y N O T I C E * --- The content of this e-mail is intended solely for the use of the individual or entity to whom it is addressed. If you have received this communication in error, be aware that forwarding it, copying it, or in any way disclosing its content to any other person, is strictly prohibited. Peek Traffic Corporation is neither liable for the contents, nor for the proper, complete and timely transmission of (the information contained in) this communication. If you have received this communication in error, please notify the author by replying to this e-mail immediately and delete the material from any computer. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat and vb6 dll?
Sadly (and Rob M has commented on this several times) the VB Team seem to feel that generating "correct" merge modules is not a priority. (For them, perhaps it's not, but for those of us who live in the real world where VB6 applications are still very much in use it does make things challenging.) Personally, for the few VB6 projects I have under WiX, I make the inclusion of the merge modules conditional build and validate (run smoke) without them, then build again including them but turn off the validation. Yup, it's ugly. Yup, I don't want to turn off validation. Sometimes you just have to do what you can. Regards, Richard From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cheyne, Mark A - DNR Sent: Tuesday, June 12, 2007 5:13 PM To: Neil Sleightholm; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Heat and vb6 dll? yes, that is precisely the source of the merge modules I describe in my original post. thanks. since that post, I have tried running smoke.exe on a few of those merge modules, which results in all the errors I am seeing in my build. I take that to mean that the modules are somehow 'bad'. Can anyone explain why? * C O N F I D E N T I A L I T Y N O T I C E * --- The content of this e-mail is intended solely for the use of the individual or entity to whom it is addressed. If you have received this communication in error, be aware that forwarding it, copying it, or in any way disclosing its content to any other person, is strictly prohibited. Peek Traffic Corporation is neither liable for the contents, nor for the proper, complete and timely transmission of (the information contained in) this communication. If you have received this communication in error, please notify the author by replying to this e-mail immediately and delete the material from any computer. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat and vb6 dll?
Wilson, Phil wrote: Well the issue is basically that registration of VB6 Dlls requires the VB6 runtime to be installed on the system. That means you need the VB6 runtime on your dev machine where you're running Heat. Heat is calling DllRegisterServer, which is calling into the VB6 runtime. That much seems obvious, so if you already have the VB6 runtime on the dev system then something else is going on (a possibility might be that Heat is confused by seeing registration entries that have a server other than your Dll). The problem is that some DLLs unnecessarily rewrite their (or parent/dependent DLLs') COM registration information. Heat just records what the DLLs' self-reg code actually did, so it can't differentiate between "good" self-reg and "bad" self-reg. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat and vb6 dll?
Well the issue is basically that registration of VB6 Dlls requires the
VB6 runtime to be installed on the system. That means you need the VB6
runtime on your dev machine where you're running Heat. Heat is calling
DllRegisterServer, which is calling into the VB6 runtime. That much
seems obvious, so if you already have the VB6 runtime on the dev system
then something else is going on (a possibility might be that Heat is
confused by seeing registration entries that have a server other than
your Dll).
The VB6 merge modules etc that consitute the VB6 runtime support are
included in your setup for the Dll to work, where the assumption is that
your VB6 code won't run until after the install because of the "random"
order in which files are installed.
Phil Wilson
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Cheyne,
Mark A - DNR
Sent: Tuesday, June 12, 2007 3:45 PM
To: Neil Sleightholm; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Heat and vb6 dll?
As Neil's reply is actually a solution to my other post:
http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg09440.htm
l
I thought I'd restate _this_ problem, which remains unsolved.
The problem here is that I run heat.exe on a VB6 DLL that I authored, as
a way to generate a *.wxs file containing a with all the COM
registration muck I need to install and register that DLL. The problem
is that the output *.wxs contains errors that prevent me from building.
See my enumeration of errors 1, 2, 3 at the bottom of this thread.
Any thoughts? These errors refer to a class and typelibs that are part
of VB6 itself, not my DLL, and yet heat.exe emits (erroneous,
incomplete?) metadata about them when I point it at my DLL.
Thanks, all - I'm almost there! Mark
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 12, 2007 4:29 PM
To: Cheyne, Mark A - DNR; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Heat and vb6 dll?
It looks like this has come up before:
http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg01619.htm
l
I found I needed to add:
Neil
From: Neil Sleightholm
Sent: 12 June 2007 22:19
To: 'Cheyne, Mark A - DNR'; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Heat and vb6 dll?
I can't help but I see exactly the same errors. As a work around
I am ignoring the ICE03 errors but I am not sure this is a good move.
Hopefully someone else will enlighten us.
Neil
From: Cheyne, Mark A - DNR [mailto:[EMAIL PROTECTED]
Sent: 12 June 2007 22:13
To: Neil Sleightholm; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Heat and vb6 dll?
yes, that is precisely the source of the merge modules I
describe in my original post. thanks.
since that post, I have tried running smoke.exe on a few of
those merge modules, which results in all the errors I am seeing in my
build. I take that to mean that the modules are somehow 'bad'. Can
anyone explain why?
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 12, 2007 4:03 PM
To: Cheyne, Mark A - DNR;
wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Heat and vb6 dll?
It might be easier to use the VB6 merge modules from
Microsoft:
http://www.microsoft.com/downloads/details.aspx?familyid=f9d19334-61ec-4
8cf-bb4e-3aec65edd50b&displaylang=en.
Neil
Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED]
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Cheyne,
Mark A - DNR
Sent: 12 June 2007 17:40
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Heat and vb6 dll?
I ran heat.exe on a COM dll created in VB6, to
automagically get a fragment of all the stuff necessary to register my
DLL on installation. When I try to build the project, I get 3 errors on
the output *.wxs that heat.exe gave me:
1) Error CNDL0010: The Class/@Server attribute was not
found; it is required. This is referring to the following element:
2) Error CNDL0047: The TypeLib element is non-advertised
and therefore requires a parent File element. This is referring to the
following element:
Re: [WiX-users] Heat and vb6 dll?
As Neil's reply is actually a solution to my other post:
http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg09440.htm
l
I thought I'd restate _this_ problem, which remains unsolved.
The problem here is that I run heat.exe on a VB6 DLL that I authored, as
a way to generate a *.wxs file containing a with all the COM
registration muck I need to install and register that DLL. The problem
is that the output *.wxs contains errors that prevent me from building.
See my enumeration of errors 1, 2, 3 at the bottom of this thread.
Any thoughts? These errors refer to a class and typelibs that are part
of VB6 itself, not my DLL, and yet heat.exe emits (erroneous,
incomplete?) metadata about them when I point it at my DLL.
Thanks, all - I'm almost there! Mark
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 12, 2007 4:29 PM
To: Cheyne, Mark A - DNR; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Heat and vb6 dll?
It looks like this has come up before:
http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg01619.htm
l
I found I needed to add:
Neil
From: Neil Sleightholm
Sent: 12 June 2007 22:19
To: 'Cheyne, Mark A - DNR'; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Heat and vb6 dll?
I can't help but I see exactly the same errors. As a work around
I am ignoring the ICE03 errors but I am not sure this is a good move.
Hopefully someone else will enlighten us.
Neil
From: Cheyne, Mark A - DNR [mailto:[EMAIL PROTECTED]
Sent: 12 June 2007 22:13
To: Neil Sleightholm; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Heat and vb6 dll?
yes, that is precisely the source of the merge modules I
describe in my original post. thanks.
since that post, I have tried running smoke.exe on a few of
those merge modules, which results in all the errors I am seeing in my
build. I take that to mean that the modules are somehow 'bad'. Can
anyone explain why?
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 12, 2007 4:03 PM
To: Cheyne, Mark A - DNR;
wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Heat and vb6 dll?
It might be easier to use the VB6 merge modules from
Microsoft:
http://www.microsoft.com/downloads/details.aspx?familyid=f9d19334-61ec-4
8cf-bb4e-3aec65edd50b&displaylang=en.
Neil
Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED]
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Cheyne,
Mark A - DNR
Sent: 12 June 2007 17:40
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Heat and vb6 dll?
I ran heat.exe on a COM dll created in VB6, to
automagically get a fragment of all the stuff necessary to register my
DLL on installation. When I try to build the project, I get 3 errors on
the output *.wxs that heat.exe gave me:
1) Error CNDL0010: The Class/@Server attribute was not
found; it is required. This is referring to the following element:
2) Error CNDL0047: The TypeLib element is non-advertised
and therefore requires a parent File element. This is referring to the
following element:
3) another one like (2), referring to:
Can anyone elaborate? Am I missing something?
Thanks, Mark
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat and vb6 dll?
It looks like this has come up before:
http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg01619.htm
l
I found I needed to add:
Neil
From: Neil Sleightholm
Sent: 12 June 2007 22:19
To: 'Cheyne, Mark A - DNR'; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Heat and vb6 dll?
I can't help but I see exactly the same errors. As a work around I am
ignoring the ICE03 errors but I am not sure this is a good move.
Hopefully someone else will enlighten us.
Neil
From: Cheyne, Mark A - DNR [mailto:[EMAIL PROTECTED]
Sent: 12 June 2007 22:13
To: Neil Sleightholm; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Heat and vb6 dll?
yes, that is precisely the source of the merge modules I describe in my
original post. thanks.
since that post, I have tried running smoke.exe on a few of those merge
modules, which results in all the errors I am seeing in my build. I take
that to mean that the modules are somehow 'bad'. Can anyone explain why?
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 12, 2007 4:03 PM
To: Cheyne, Mark A - DNR; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Heat and vb6 dll?
It might be easier to use the VB6 merge modules from Microsoft:
http://www.microsoft.com/downloads/details.aspx?familyid=f9d19334-61ec-4
8cf-bb4e-3aec65edd50b&displaylang=en.
Neil
Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED]
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Cheyne,
Mark A - DNR
Sent: 12 June 2007 17:40
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Heat and vb6 dll?
I ran heat.exe on a COM dll created in VB6, to automagically get
a fragment of all the stuff necessary to register my DLL on
installation. When I try to build the project, I get 3 errors on the
output *.wxs that heat.exe gave me:
1) Error CNDL0010: The Class/@Server attribute was not found; it
is required. This is referring to the following element:
2) Error CNDL0047: The TypeLib element is non-advertised and
therefore requires a parent File element. This is referring to the
following element:
3) another one like (2), referring to:
Can anyone elaborate? Am I missing something?
Thanks, Mark
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat and vb6 dll?
I can't help but I see exactly the same errors. As a work around I am
ignoring the ICE03 errors but I am not sure this is a good move.
Hopefully someone else will enlighten us.
Neil
From: Cheyne, Mark A - DNR [mailto:[EMAIL PROTECTED]
Sent: 12 June 2007 22:13
To: Neil Sleightholm; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Heat and vb6 dll?
yes, that is precisely the source of the merge modules I describe in my
original post. thanks.
since that post, I have tried running smoke.exe on a few of those merge
modules, which results in all the errors I am seeing in my build. I take
that to mean that the modules are somehow 'bad'. Can anyone explain why?
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 12, 2007 4:03 PM
To: Cheyne, Mark A - DNR; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Heat and vb6 dll?
It might be easier to use the VB6 merge modules from Microsoft:
http://www.microsoft.com/downloads/details.aspx?familyid=f9d19334-61ec-4
8cf-bb4e-3aec65edd50b&displaylang=en.
Neil
Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED]
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Cheyne,
Mark A - DNR
Sent: 12 June 2007 17:40
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Heat and vb6 dll?
I ran heat.exe on a COM dll created in VB6, to automagically get
a fragment of all the stuff necessary to register my DLL on
installation. When I try to build the project, I get 3 errors on the
output *.wxs that heat.exe gave me:
1) Error CNDL0010: The Class/@Server attribute was not found; it
is required. This is referring to the following element:
2) Error CNDL0047: The TypeLib element is non-advertised and
therefore requires a parent File element. This is referring to the
following element:
3) another one like (2), referring to:
Can anyone elaborate? Am I missing something?
Thanks, Mark
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat and vb6 dll?
yes, that is precisely the source of the merge modules I describe in my
original post. thanks.
since that post, I have tried running smoke.exe on a few of those merge
modules, which results in all the errors I am seeing in my build. I take
that to mean that the modules are somehow 'bad'. Can anyone explain why?
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 12, 2007 4:03 PM
To: Cheyne, Mark A - DNR; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Heat and vb6 dll?
It might be easier to use the VB6 merge modules from Microsoft:
http://www.microsoft.com/downloads/details.aspx?familyid=f9d19334-61ec-4
8cf-bb4e-3aec65edd50b&displaylang=en.
Neil
Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Cheyne,
Mark A - DNR
Sent: 12 June 2007 17:40
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Heat and vb6 dll?
I ran heat.exe on a COM dll created in VB6, to automagically get
a fragment of all the stuff necessary to register my DLL on
installation. When I try to build the project, I get 3 errors on the
output *.wxs that heat.exe gave me:
1) Error CNDL0010: The Class/@Server attribute was not found; it
is required. This is referring to the following element:
2) Error CNDL0047: The TypeLib element is non-advertised and
therefore requires a parent File element. This is referring to the
following element:
3) another one like (2), referring to:
Can anyone elaborate? Am I missing something?
Thanks, Mark
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat and vb6 dll?
It might be easier to use the VB6 merge modules from Microsoft: http://www.microsoft.com/downloads/details.aspx?familyid=f9d19334-61ec-4 8cf-bb4e-3aec65edd50b&displaylang=en. Neil Neil Sleightholm X2 Systems Limited [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cheyne, Mark A - DNR Sent: 12 June 2007 17:40 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Heat and vb6 dll? I ran heat.exe on a COM dll created in VB6, to automagically get a fragment of all the stuff necessary to register my DLL on installation. When I try to build the project, I get 3 errors on the output *.wxs that heat.exe gave me: 1) Error CNDL0010: The Class/@Server attribute was not found; it is required. This is referring to the following element: 2) Error CNDL0047: The TypeLib element is non-advertised and therefore requires a parent File element. This is referring to the following element: 3) another one like (2), referring to: Can anyone elaborate? Am I missing something? Thanks, Mark - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Heat and vb6 dll?
I ran heat.exe on a COM dll created in VB6, to automagically get a fragment of all the stuff necessary to register my DLL on installation. When I try to build the project, I get 3 errors on the output *.wxs that heat.exe gave me: 1) Error CNDL0010: The Class/@Server attribute was not found; it is required. This is referring to the following element: 2) Error CNDL0047: The TypeLib element is non-advertised and therefore requires a parent File element. This is referring to the following element: 3) another one like (2), referring to: Can anyone elaborate? Am I missing something? Thanks, Mark - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
