Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output

> I am curious, does your installation package, once installed, work > correctly? > > Thanks, > > Brian Rogers > "Intelligence removes complexity." - Me > http://icumove.spaces.live.com > > > On Wed, May 13, 2009 at 8:30 AM, Roy Abou Assaly > wro

Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output

.0.5308: WiX file produced 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=detail&a

Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output

me know if I can 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. Tha

Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output

ave to stick with 3.0.4923 as 3.0.5224 has a break that I can't work around. If anything is unclear, let me know. Thanks again, Roy Neil Sleightholm wrote: > > I am not sure I understand what you are asking, could you explain? > > Neil > > -Original Message

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 t

Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output

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 i

Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output

d 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 the XML that heat > generates in order to ensure certain shortcuts are added and changes a few > other thing

Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output

gt; command lines you are using? > > Neil > > -----Original Message- > From: Roy Abou Assaly > [mailto:royass...@...<http://n2.nabble.com/user/SendEmail.jtp?type=node&node=2686897&i=0>] > > Sent: 23 April 2009 22:18 > To: > wix-us...@...<http://n2

Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output

gt; Please file a bug. > > Thanks, > > Brian Rogers > "Intelligence removes complexity." - Me > http://icumove.spaces.live.com > > > On Thu, Apr 23, 2009 at 1:31 PM, Roy Abou Assaly > wrote: > >> >> Hi, >> >> In 3.0.4923, I

[WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output

Hi, In 3.0.4923, I used to get the following output (note how the Interface element is *outside* of the File element): In 3.0.5217, the heat output i

Re: [WiX-users] Registring CDO.dll - Heat ouput same as before, but Light now giving error

We got an error: 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

Re: [WiX-users] Registring CDO.dll - Heat ouput same as before, but Light now giving error

tput of the > harvest 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://

[WiX-users] Registring CDO.dll - Heat ouput same as before, but Light now giving error

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 one

Re: [WiX-users] Heat missing some RegistryValue elements (Programmable) from VB6 code?

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, Ro

Re: [WiX-users] Heat missing some RegistryValue elements (Programmable) from VB6 code?

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\XMLEditor>heat dir . -v -sfrag -gg -svb6 -out foo.xml Microsoft (R) Windows Installer Xml Toolset Harvester version 3.0.5210.0 Copyright (C) Microsoft Corporat

Re: [WiX-users] Heat missing some RegistryValue elements (Programmable) from VB6 code?

Hey Roy, If you are still able to reproduce this please file a bug in heat and upload the DLL. I would recommend that the DLL ONLY contain required information to reproduce the issue IF possible. Thanks, Brian Thanks for the all the help Brian and Neil. I've submitted the bug: https://sou

Re: [WiX-users] Heat missing some RegistryValue elements (Programmable) from VB6 code?

tp://n2.nabble.com/user/SendEmail.jtp?type=node&node=2571127&i=1>> > > > > > > From: Roy Abou Assaly > [mailto:royass...@...<http://n2.nabble.com/user/SendEmail.jtp?type=node&node=2571127&i=2>] > > Sent: Wed

Re: [WiX-users] Heat missing some RegistryValue elements (Programmable) from VB6 code?

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. If you are not already you may also want to try the -svb6 option with Heat as that will remove the VB6 runtime properties that are not required (see help file). Neil Hi

Re: [WiX-users] Heat missing some RegistryValue elements (Programmable) from VB6 code?

t; > -Original Message----- > From: Roy Abou Assaly > [mailto:royass...@...<http://n2.nabble.com/user/SendEmail.jtp?type=node&node=2559601&i=0>] > > Sent: 30 March 2009 21:02 > To: > wix-us...@...<http://n2.nabble.com/user/SendEmail.jtp?type=node&node=2559601

[WiX-users] Heat missing some RegistryValue elements (Programmable) from VB6 code?

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: This key existed in our December build, and now, in many mor

Re: [WiX-users] Writing a Value for RegistryValue element of Type Binary

Roy Abou Assaly wrote: > > > > Roy Abou Assaly wrote: >> >> >> >> Bob Arnson-6 wrote: >>> >>> Roy Abou Assaly wrote: >>>>> Value="00 01" gives: >>>>> >>>>

Re: [WiX-users] Writing a Value for RegistryValue element of Type Binary

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 >>> val

Re: [WiX-users] Writing a Value for RegistryValue element of Type Binary

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. >> V

Re: [WiX-users] Writing a Value for RegistryValue element of Type Binary

On Tue, Feb 24, 2009 at 1:46 PM, Bob Arnson-6 (via Nabble) < ml-user+58260-683222...@n2.nabble.com > wrote: > Roy Abou Assaly wrote: > > > > > > But I keep getting the error: > > > > error LGHT0204 : ICE70: The value '#x01,00' is an i

[WiX-users] Writing a Value for RegistryValue element of Type Binary

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 Regist

Re: [WiX-users] COM Plus Applications and Major Upgrade

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

Re: [WiX-users] COM Plus Applications and Major Upgrade

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 > > > _

Re: [WiX-users] ClickThrough 3.0.4805.0 throws exception when selectiong Isolated Apps

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: http://n2.nabble.com/ClickThrough-3.0.4805.0-throws-exception-when-selecti

[WiX-users] ClickThrough 3.0.4805.0 throws exception when selectiong Isolated Apps

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 sele

[WiX-users] Uninstalling or Installing while an exe of the product is running errors

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\system32>msiexec /i "\\isdist01z\prism\Vista\Build_10.61.0\MSI\Prism.msi" /q /l* "C:\Prog ramDa

Re: [WiX-users] Creating COM+ components using Wix 3.0

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 sho

Re: [WiX-users] Creating COM+ components using Wix 3.0

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

[WiX-users] Creating COM+ components using Wix 3.0

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 gr

Re: [WiX-users] WiX build 3.0.4207 - missing mergmod.dll

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.ne

Re: [WiX-users] WiX build 3.0.4207 - missing mergmod.dll

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 t

[WiX-users] WiX build 3.0.4207 - missing mergmod.dll

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 found.

Re: [WiX-users] Vista registry virtualization

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

Re: [WiX-users] WiX v3: COM on Vista. I have some success, but worried about heat's erroneous output

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

Re: [WiX-users] WiX v3: COM on Vista. I have some success, but worried about heat's erroneous output

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

Re: [WiX-users] WiX v3: COM on Vista. I have some success, but worried about heat's erroneous output.

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&#x

[WiX-users] WiX v3: COM on Vista. I have some success, but worried about heat's erroneous output.

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

Re: [WiX-users] Full Uninstall and Reinstall of Features

Bob Arnson-6 wrote: > > Roy Abou Assaly wrote: >> in order to install f3. By default f1 is installed if ADDLOCAL is >> omitted. >> That's good. However, let's say that I want to install f3 after f1 is >> installed on my computer. What's happeni

[WiX-users] Full Uninstall and Reinstall of Features

Hi, I've been using WiX v2 on XP for a while and I'm moving to WiX v3 on Windows Vista. I have the following setup: Product: Px Components: c1 c2 c3 Features: f1 (c1,c2) - level 1 f2 (c1,c3) - level 2 f3 (c3) - level 3 At the command line, I use: $msiexec /i px.msi /qn ADDLOCAL=f3 in orde

Re: [WiX-users] nant task and WiX

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 task after I've built my project. To clarify, I use WiX v2: Lerudjo

Re: [WiX-users] UCS-2 Little Endian encoding of MSI Log file problem.

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 >

[WiX-users] UCS-2 Little Endian encoding of MSI Log file problem.

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

Re: [WiX-users] Launching program after installation completes gives occassional error. (Roy Abou Assaly)

rs] Launching program after installation > completes gives occassional error. (Roy Abou Assaly) > To: wix-users@lists.sourceforge.net > Roy: > > I'm not sure what is going on here, but if the MSI dialog is reappearing > after the product is installed, it seems that things are not

Re: [WiX-users] Launching program after installation completes gives occassional error. (Roy Abou Assaly)

> 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 &

[WiX-users] Launching program after installation completen give occassional error.

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 chronolog