is 3794 lines, 601 KB
That's a great performance improvement!
Thanks again for all the help. Heat is definitely a rock solid tool.
Roy
Roy Abou Assaly wrote:
I have filed the following bug:
https://sourceforge.net/tracker/?func=detailatid=642714aid=2783049group_id=105970
and included
be of any help at all.
Roy Abou Assaly wrote:
Sorry. I'll explain the situation. I sort of cried wolf in the
beginning since I used an XSLT to massage my XML after Heat produced the
XML. At that point Candle wouldn't compile. That was my mistake as
confirmed by Brian and yourself. I
:
I am not sure I understand what you are asking, could you explain?
Neil
-Original Message-
From: Roy Abou Assaly [mailto:royass...@gmail.com]
Sent: 24 April 2009 16:02
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output
Can anyone run light 3.0.5217 on this to confirm this? The merge module
simple won't build and that Interface element is indeed needed.
Thanks again.
Roy Abou Assaly wrote:
Oh, and one more:
00020420---C000-0046
After that, I was able to build my merge module and link
Hi,
In 3.0.4923, I used to get the following output (note how the Interface
element is *outside* of the File element):
Component Id=DisplayFridayListUI.dll
Guid={C4773BDF-6383-423D-BB34-BBB961BFD6DF}
File Id=DisplayFridayListUI.dll
Name=DisplayFridayListUI.dll
Rogers
Intelligence removes complexity. - Me
http://icumove.spaces.live.com
On Thu, Apr 23, 2009 at 1:31 PM, Roy Abou Assaly
royass...@gmail.comwrote:
Hi,
In 3.0.4923, I used to get the following output (note how the Interface
element is *outside* of the File element
details of the
command lines you are using?
Neil
-Original Message-
From: Roy Abou Assaly
[mailto:royass...@...http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2686897i=0]
Sent: 23 April 2009 22:18
To:
wix-us...@...http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2686897i
-C000-0046
Which is slightly off. Me thinks I should also add this to the cleanup xslt
file.
You can copy paste it and try it out. I'm a bit stuck. Perhaps I've been
staring at this for too long.
Roy
Roy Abou Assaly wrote:
Both of you are correct. I have an XSLT that massage
though I remove those elements that I didn't fully understand.
Roy Abou Assaly wrote:
Still kind of stuck. I was able to generate the exact xml as Brian did.
Candle compiled fine, but light is complaining. I'm trying to generate a
merge module out of it. Getting this error:
[exec
:
Marshaler restriction: Excessively long string.
I will leave to the developers to update accordingly and then our plan is to
use the redistributable.
Thanks!
Roy
Roy Abou Assaly wrote:
Hi Brian,
I found this website http://www.cdolive.com/cdo7.htm which lead me to this
MS Collaboration Data
Hi,
I'm in the process of migrating more WiX files to the latest version of WiX.
I'm using 3.0.5217 and found this error that wasn't occurring in an older
version of WiX:
error LGHT0130 : The primary key 'regFB26914512AFF203D5986383999BD192' is
duplicated in table 'Registry'. Please remove
is basically not valid which is possible as COM is highly
customizable. Heat does not take into account all possible variations
because of those issues.
Thanks,
Brian Rogers
Intelligence removes complexity. - Me
http://icumove.spaces.live.com
On Mon, Apr 20, 2009 at 12:41 PM, Roy Abou
appreciate the detailed
information. When you see issues like this please feel free to file a bug
on
sourceforge.net/projects/wix.
Thanks,
Brian Rogers
Intelligence removes complexity. - Me
http://icumove.spaces.live.com
On Tue, Apr 14, 2009 at 8:15 AM, Roy Abou Assaly
royass...@...http://n2
Hi,
I was away for a week or else I would've replied sooner. I tested the
following using version 3.0.5210.0.
This works:
D:\lab\WiX\XMLEditorheat dir . -v -sfrag -gg -svb6 -out foo.xml
Microsoft (R) Windows Installer Xml Toolset Harvester version 3.0.5210.0
Copyright (C) Microsoft
I have just tried the latest version 3.0.5120.0 and the programmable
attribute on is set for your dll on the ClassId e.g.
Class Id={5A5DBDF3-10F1-43D1-AA51-CDE7EDFA0321}
Description=PRISMXMLEditor.XMLChunk Version=12.3 Programmable=yes
If you are not already you may also want to try the -svb6
/SendEmail.jtp?type=nodenode=2571127i=1
From: Roy Abou Assaly
[mailto:royass...@...http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2571127i=2]
Sent: Wed 01/04/2009 14:39
To:
wix-us...@...http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2571127i=3
Hi,
I'm running heat (WiX 3.0.4923.0) to harvest some DLLs. I don't have the
version that I was using before, but I know it was working before I had
upgraded sometime in the Fall.
I noticed that Programmable is being ommitted:
RegistryValue Root=HKCR
the problem?
Neil
-Original Message-
From: Roy Abou Assaly
[mailto:royass...@...http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2559601i=0]
Sent: 30 March 2009 21:02
To:
wix-us...@...http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2559601i=1
Subject: [WiX-users] Heat missing
Hi,
I have a registry key that is of type binary and has is a long series of
numbers. When I export it from regedit, it looks like this:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FooBar\Security]
Security=hex:01,00,14,80,90,...
I'm having trouble expressing this inside the
On Tue, Feb 24, 2009 at 1:46 PM, Bob Arnson-6 (via Nabble)
ml-user+58260-683222...@n2.nabble.comml-user%2b58260-683222...@n2.nabble.com
wrote:
Roy Abou Assaly wrote:
RegistryValue Type=binary Name=Security Value=01,00,... /
But I keep getting the error:
error LGHT0204 : ICE70
Bob Arnson-6 wrote:
Roy Abou Assaly wrote:
Value=00 01 gives:
error LGHT0204 : ICE70: The value '#x01 02' is an invalid hexadecimal
value
for registry entry regA16537AC885C7B5BB23019846BB931C1.
Value=00;01 gives:
error LGHT0204 :ICE70: The value '#x01;02' is an invalid
Roy Abou Assaly wrote:
Bob Arnson-6 wrote:
Roy Abou Assaly wrote:
Value=00 01 gives:
error LGHT0204 : ICE70: The value '#x01 02' is an invalid hexadecimal
value
for registry entry regA16537AC885C7B5BB23019846BB931C1.
Value=00;01 gives:
error LGHT0204 :ICE70: The value
Roy Abou Assaly wrote:
Roy Abou Assaly wrote:
Bob Arnson-6 wrote:
Roy Abou Assaly wrote:
Value=00 01 gives:
error LGHT0204 : ICE70: The value '#x01 02' is an invalid hexadecimal
value
for registry entry regA16537AC885C7B5BB23019846BB931C1.
Value=00;01 gives:
error
Neil Sleightholm wrote:
Where do you have RemoveExistingProducts scheduled? Have you tried it
after InstallValidate so that is removes everything before reinstalling.
Neil
Neil Sleightholm
X2 Systems Limited
n...@x2systems.com mailto:n...@x2systems.com
Don Benson wrote:
I also do Major upgrades *all* the time. We have a large COM, COM+,
VB6
application and I don't dare play games with COM+ registries as I value
my
time too much :P It's a requirement for us developers to move back and
forth along the versions and I want to force
Hi,
I'm using the WiX Beta Exit build 3.0.4805.0.
1. I start ClickThrough
2. I select Click Through for Office Addins (shouldn't it be ClickThrough
and Click Through? Typo?)
3. I get taken to the Build page with the 7 steps. Everything is good.
Now, when
1. I start ClickThrough
2. I
Rob Mensching-2 wrote:
ClickThrough has significant bugs that have all been punted to WiX v4
essentially rendering ClickThrough useless until then.
Thanks for the quick reply!
--
View this message in context:
Hi,
I was experimenting with an MSI packaged on Vista (WiX v 3.0.4207.0) and
installed on Vista with some situations trying to figure out the behaviour:
1. Install Prism.msi version 10.61
C:\Windows\system32msiexec /i
\\isdist01z\prism\Vista\Build_10.61.0\MSI\Prism.msi /q /l* C:\Prog
Fredrik Grohn-4 wrote:
There is a custom action library to do COM+ registration in WiX. For v2
see the PubCA schema:
http://wix.sourceforge.net/manual-wix2/pubca_xsd_index.htm
I am on the road, so I don't have an example ready to send, but if you
search the list archive there should be
Roy Abou Assaly wrote:
Hi,
Some background: I'm trying to replace a legacy builder tool. The old
builder tool compiled hundreds of vbp project files. Some ActiveX, some
Exes, some Com+. The compilation was successful in NAnt. I also have
created a WiX file that currently installs
Hi,
Some background: I'm trying to replace a legacy builder tool. The old
builder tool compiled hundreds of vbp project files. Some ActiveX, some
Exes, some Com+. The compilation was successful in NAnt. I also have
created a WiX file that currently installs the UI DLLs and Exe and it works
Hi,
I know I've seen a few blog posts about this and how it's been fixed in WiX
v3, but that you're working on it for v2, but it seems to back in build
3.0.4207. I get the following message:
light.exe : error LGHT0001 : Unable to load DLL 'mergemod.dll': The
specified module could not be
Lucky me. I found this post by Bob:
http://www.joyofsetup.com/2008/06/09/wix-v2-needs-fixed-mergemoddll-too/
So I downloaded the zip file for build 3.0.4207.0
(http://wix.sourceforge.net/releases/3.0.4207.0/) and took the mergmod.dll
from there and copied it. So it looks like the binaries in
Bob Arnson-6 wrote:
Roy Abou Assaly wrote:
Lucky me. I found this post by Bob:
http://www.joyofsetup.com/2008/06/09/wix-v2-needs-fixed-mergemoddll-too/
So I downloaded the zip file for build 3.0.4207.0
(http://wix.sourceforge.net/releases/3.0.4207.0/) and took the
mergmod.dll
from
Simon Topley wrote:
We have recently been having issues with our COM interface and the
finger was pointed at the installers as ever. It seems in vista being
logged in as an Administrator doesn't mean what it once did. Most
programs are run by default as a user, you have to right click and
John Hall-9 wrote:
I've been reading more about heat, vb6 and vista. I'm now
starting to get worried that there's a potential difference
between running Heat on Vista versus XP. And yes, you do
need to run as Admin, and elevated for Heat to actually
extract anything. Also, Should I
I basically have about 150 COM, ActiveX VB6 files. I ran heat to produce the
output and then modified them to produce 2 merge modules. I used heat to
avoid using the SelfRegCost attribute which as been frowned upon by many
here. I read Rob's blog about that :)
I ran into 2 warnings which were
Roy Abou Assaly wrote:
I basically have about 150 COM, ActiveX VB6 files. I ran heat to produce
the output and then modified them to produce 2 merge modules. I used heat
to avoid using the SelfRegCost attribute which as been frowned upon by
many here. I read Rob's blog about
I use NAnt to call in a similar fashion but add some more options since I'm
paranoid. I also have NAnt version my WiX file on the fly using the
XMLPoke task after I've built my project. To clarify, I use WiX v2:
!-- Create the MSI executable. We are using the WiX toolset to do
this.
When I install an msi, I am keeping a log like so:
c:\msiexec /i foo.msi /l* foo.log
The problems is that when I open foo.log, it turns out it's in UCS-2 Little
Endian encoding. Chaning the encoding in .NET is trivial, but we have a
legacy app that needs to append to the log file, and it's in
Solution:
Someone replied...the answer was to use the MultiByteToWideChar function to
convert from ANSI to UCS-2 before appending to the file.
Thanks!
Roy Abou Assaly wrote:
When I install an msi, I am keeping a log like so:
c:\msiexec /i foo.msi /l* foo.log
The problems
Date: Thu, 31 Aug 2006 10:32:18 -0400
From: Roy Abou Assaly [EMAIL PROTECTED]
Subject: [WiX-users] Launching program after installation completen
giveoccassional error.
I don't know if this is my fault or not. At the end of tte
installation, we have a checkbox which
I don't know if this is my fault or not. At the end of tte
installation, we have a checkbox which is by default on, such that
when the user clicks 'Finish', the program that he just installed,
launches. I *sometimes* get the following error in my Application
eventlog in the following
43 matches
Mail list logo
