Re: [WiX-users] Upgrade InstallShield package
fiordean dacian wrote: 1. When double click on my new msi, it detects there is a previous product installed (there is a PREVFOUND property set I provided within the Upgrade sequence of my WiX code), but there is no message saying Another version of ... like I get when I do an upgrade with two msi files I generated with WiX but have different versions. It just goes like a normal install, even if some components are upgraded. What I'd expect is getting an error when double click (Another version...), but when launched with REINSTALL=ALL REINSTALLMODE=vomus it should work. The REINSTALL/REINSTALLMODE behavior you describe is a minor upgrade. The Upgrade/UpgradeVersion schema is used to declare a major upgrade, which removes the previous product version as part of installing the newer. Which do you want? -- 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] ForceReboot
Aaron Shurts wrote: Why not set the REBOOT property to 'Always'? ForceReboot is bad to use in some scenarios and could end up making some of your users angry. True, but it's occasionally unavoidable for some drivers. -- 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] Adding User Interface to Setup Project in Visual Studio
Afshin Sepehri wrote: light.exe -out SampleWixUI.msi SampleWixUI.wixobj /path/\wixui.wixlib -loc /path/\WixUI_en-us.wxl That command line is for WiX v2. In v3, you just need to add a reference to WixUIExtension.dll. -- 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] UPdating label field through spawn dialog
hariom wrote: this point. Now if users wants to customize some settings, we are providing options through spawn dialog. Whatever the changes they make in spawn dialog based on the I have to update the text of label-text filed which in parent dialog. You can try setting the text control's Property attribute to the property being used but there's no guarantee in the MSI doc that doing so will trigger an update. It's a limitation of the MSI UI support. -- 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] Adding User Interface to Setup Project in Visual Studio
On 6/12/07, Bob Arnson [EMAIL PROTECTED] wrote: Afshin Sepehri wrote: light.exe -out SampleWixUI.msi SampleWixUI.wixobj *path*\wixui.wixlib -loc *path*\WixUI_en-us.wxl That command line is for WiX v2. In v3, you just need to add a reference to WixUIExtension.dll. and specify Cultures -- 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 - 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] Upgrade InstallShield package
Hi Bob, I just reviewed the REINSTALL/REINSTALLMODE which indeed is used for minor upgrades. My fault... Thanks for the help, Dacian - Original Message From: Bob Arnson [EMAIL PROTECTED] To: fiordean dacian [EMAIL PROTECTED] Cc: wix-users@lists.sourceforge.net Sent: Tuesday, June 12, 2007 8:06:26 AM Subject: Re: [WiX-users] Upgrade InstallShield package fiordean dacian wrote: 1. When double click on my new msi, it detects there is a previous product installed (there is a PREVFOUND property set I provided within the Upgrade sequence of my WiX code), but there is no message saying Another version of ... like I get when I do an upgrade with two msi files I generated with WiX but have different versions. It just goes like a normal install, even if some components are upgraded. What I'd expect is getting an error when double click (Another version...), but when launched with REINSTALL=ALL REINSTALLMODE=vomus it should work. The REINSTALL/REINSTALLMODE behavior you describe is a minor upgrade. The Upgrade/UpgradeVersion schema is used to declare a major upgrade, which removes the previous product version as part of installing the newer. Which do you want? -- sig://boB http://joyofsetup.com/ Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Now (it's updated for today's economy) at Yahoo! Games. http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow - 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] Future of Votive?
Is there a way of specifying the -b switch when building from Visual Studio? Assuming you mean using Votive, it doesn't appear to be exposed through the project property pages. But you can edit the .wixproj file outside VS and add a LinkerBaseInputPaths property to be a semi-colon-delimited list of paths. Would adding this to the light property page be the kind of thing that patches would be welcome for? Regards, John - 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] Adding User Interface to Setup Project in Visual Studio
I am trying to use Votive and Visual Studio to build my WiX Steup project, but to be able to add User Interface, I need to add parameters to light. For example: light.exe -out SampleWixUI.msi SampleWixUI.wixobj path\wixui.wixlib -loc path\WixUI_en-us.wxl However, the light settings in project file in VS does not let me add any new parameter. Does anybody know how I can build my setup project with VS? Ashin, I don't think you can add the reference to WixUIExtension.dll from within Votive, so you need to modify the wixproj manually and add an item like this: ItemGroup WixExtension Include=$(WixDir)\bin\WixUIExtension.dll / /ItemGroup I've defined an environment variable called WixDir to make my file portable rather than put in an absolute path, but there might be a better way. Regards, John - 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] Centrally postition error dialogs
Is there a way to ensure that the error dialogs spawned are positioned centrally with respect to the parent dialog? Thanks and regards, Saraswathy - 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] Adding User Interface to Setup Project in Visual Studio
I'm new to WiX myself and just ran into this one yesterday. I presume you are using VS2005 and WiX 3.0? The instructions at http://wix.sourceforge.net/manual-wix2/WixUI_dialog_library.htm to add a *.wixlib and *.wxl file to the Light command line do not apply to WiX 3.0, nor do they work with the VS IDE. Instead, use the VS solution explorer to add a reference to WixUIExtension.dll, which you'll find in WiX's install directory. Then you do still need to identify the localization culture. On the Linker tab (Light Settings) of the solution's property pane, specify 'en-US' (or whatever) as the Culture. 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] Upgrade InstallShield package
Hi,
I ran into some extra problems with my InstallShield upgrade. Looking with Orca
throughout the Component table on the IS msi installation file, I saw some of
the components don't have a KeyPath set (the KeyPath column is empty). The WiX
source for my new version of the product has KeyPath set on the component
containing the same file, like below:
Component Id=Component1 Guid={GUID1}
File Id=File1 Name=File1.exe Source=...
Shortcut Id=ScFile1 Name=File1 Description=.. .../
/File
!-- just a fix for ICE43 --
Registry Id=... Root=HKCU Key=... KeyPath=yes Action=write/
/Component
Component Id=Component2 Guid={GUID2}
File Id=File2 Name=File2.exe Source=... SelfReg=1 KeyPath=yes/
/Component
Now the problem is IS component I want to upgrade contained, when the setup was
built, both File1 and File2, without a KeyPath. What I tried is I used new
GUIDs for both Component1 and Component2 in my new WiX source. What I was
expecting is:
1. File1.exe and File2.exe from the IS deployement gets removed (the Component
containing them isn't present in my new installation).
2. File1.exe and File2.exe from my new setup are deployed as they are new
components to be installed by the upgrade.
At the end of the day, none File1.exe or File2.exe are present in the
installation folder.
Am I doing something wrong here?
Dacian
- Original Message
From: Wilson, Phil [EMAIL PROTECTED]
To: wix-users@lists.sourceforge.net
Sent: Monday, June 11, 2007 11:33:04 PM
Subject: Re: [WiX-users] Upgrade InstallShield package
1. Is because this is a major upgrade and your new
product has a different ProductCode guid.
2. Is probably because you've set OnlyDetect if I
recall the syntax correctly.
Phil Wilson
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of fiordean
dacian
Sent: Monday, June 11, 2007 8:14 AM
To:
wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Upgrade
InstallShield package
Hi,
I located and opened with Orca the
cached msi file under Windows\Installer. The UpgradeCode is, of course,
different compared with the one I was using (displayed by IS UI). Now it looks
like some upgrade is done (files are replaced and on uninstall they are removed
from the system).
I have two questions though related to the upgrade
process:
1. When double click on my new msi, it detects there is a
previous product installed (there is a PREVFOUND property set I provided within
the Upgrade sequence of my WiX code), but there is no message saying Another
version of ... like I get when I do an upgrade with two msi files I generated
with WiX but have different versions. It just goes like a normal install, even
if some components are upgraded. What I'd expect is getting an error when
double
click (Another version...), but when launched with REINSTALL=ALL
REINSTALLMODE=vomus it should work.
2. At the end of the installation, I
have two entries within Add/Remove Programs list: one with the previous name
for
the product and under it the new name for the product. There is just the Remove
button for the previous product version (by design) and clicking on it just
removes the entry from the Add/Remove list (without an installation or
whatever). What I'd expect is no entry for the previous version in the
list.
Any ideas why?
Thx,
Dacian
-
Original Message
From: Wilson, Phil
[EMAIL PROTECTED]
To:
wix-users@lists.sourceforge.net
Sent: Friday, June 8, 2007 8:36:03
PM
Subject: Re: [WiX-users] Upgrade InstallShield package
If you can locate the cached MSI file in
Windows\installer, opening it with Orca will show the UpgradeCode in the
Property table. That might help see if you're on the right track.
Versions are also another reason why a major upgrade won't detect an older one.
Phil Wilson
From: fiordean dacian
[mailto:[EMAIL PROTECTED]
Sent: Friday, June 08, 2007 10:00
AM
To: Wilson, Phil;
wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Upgrade
InstallShield package
Hi
Phil,
Looking through IS log I see ALLUSERS with a value of
1.
Running your script displays Context 4, so there is a per-machine
install done by IS. I have ALLUSERS set to 1 in my WiX source, but there is no
detection for the product IS created.
A strange thing I saw running your
script: the product GUID displayed by your script next to the product name I'm
interested is something like
this:
{B607D95A-A73C-444B-87BA-B4E9DBAC4DEE}
while the product
code displayed by IS within its UI
is:
{F1872E85-C933-44D4-8B88-85D68DD9B103}
which makes me think
the UpgradeCode on which I base my Upgrade element to detect the
previous version installed out there is wrong (I take it from the same IS UI
which displays the wrong product code above). I don't see a property for
retrieving the UpgradeCode within the WindowsInstaller automation interface in
order to check if the UpgradeCode IS
Re: [WiX-users] Future of Votive?
John Hall wrote: Would adding this to the light property page be the kind of thing that patches would be welcome for? I won't speak for Justin but in general, patches are pretty much always welcome.g -- 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] Where and why does this tallow Warning message come from?
Steven Chin wrote: /WixI18N Runtime Warning: Missing ICU data file detected while processing $(MWE_INSTALL)/bin/$(MWE_ARCH). Hint: Check for a misconfigured environment or installation. I don't see where this is generated in the source code and some of the message uses our environment parameters. How and why is this message being generated, what other warning messages might pop up and should I be worried about these warning messages that I am going to delete? Thanks. It doesn't come from Tallow, AFAIK. Kinda weird... -- 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] Upgrade InstallShield package
fiordean dacian wrote: Now the problem is IS component I want to upgrade contained, when the setup was built, both File1 and File2, without a KeyPath. What I tried is I used new GUIDs for both Component1 and Component2 in my new WiX source. What I was expecting is: 1. File1.exe and File2.exe from the IS deployement gets removed (the Component containing them isn't present in my new installation). 2. File1.exe and File2.exe from my new setup are deployed as they are new components to be installed by the upgrade. Check a verbose log. The InstallValidate action logs the install state, request, and action state of each feature and component. -- 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
[WiX-users] Where and why does this tallow Warning message come from?
When I run tallow -s on COM server files to create registry entries I get a warning at the end of the file after the XML such as: /WixI18N Runtime Warning: Missing ICU data file detected while processing $(MWE_INSTALL)/bin/$(MWE_ARCH). Hint: Check for a misconfigured environment or installation. I don't see where this is generated in the source code and some of the message uses our environment parameters. How and why is this message being generated, what other warning messages might pop up and should I be worried about these warning messages that I am going to delete? Thanks. - 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] Upgrade InstallShield package
If you're really doing a major upgrade, this sounds like maybe you have
RemoveExistingProducts after InstallFinalize. Immediately after
InstallInitialize is better if you expect a major upgrade to behave like
an uninstall of the old product followed by an install of the new.
Phil Wilson
From: fiordean dacian [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 12, 2007 7:09 AM
To: Wilson, Phil; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Upgrade InstallShield package
Hi,
I ran into some extra problems with my InstallShield upgrade. Looking
with Orca throughout the Component table on the IS msi installation
file, I saw some of the components don't have a KeyPath set (the KeyPath
column is empty). The WiX source for my new version of the product has
KeyPath set on the component containing the same file, like below:
Component Id=Component1 Guid={GUID1}
File Id=File1 Name=File1.exe Source=...
Shortcut Id=ScFile1 Name=File1 Description=.. .../
/File
!-- just a fix for ICE43 --
Registry Id=... Root=HKCU Key=... KeyPath=yes
Action=write/
/Component
Component Id=Component2 Guid={GUID2}
File Id=File2 Name=File2.exe Source=... SelfReg=1
KeyPath=yes/
/Component
Now the problem is IS component I want to upgrade contained, when the
setup was built, both File1 and File2, without a KeyPath. What I tried
is I used new GUIDs for both Component1 and Component2 in my new WiX
source. What I was expecting is:
1. File1.exe and File2.exe from the IS deployement gets removed (the
Component containing them isn't present in my new installation).
2. File1.exe and File2.exe from my new setup are deployed as they are
new components to be installed by the upgrade.
At the end of the day, none File1.exe or File2.exe are present in the
installation folder.
Am I doing something wrong here?
Dacian
- Original Message
From: Wilson, Phil [EMAIL PROTECTED]
To: wix-users@lists.sourceforge.net
Sent: Monday, June 11, 2007 11:33:04 PM
Subject: Re: [WiX-users] Upgrade InstallShield package
1. Is because this is a major upgrade and your new product has a
different ProductCode guid.
2. Is probably because you've set OnlyDetect if I recall the syntax
correctly.
Phil Wilson
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of fiordean
dacian
Sent: Monday, June 11, 2007 8:14 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Upgrade InstallShield package
Hi,
I located and opened with Orca the cached msi file under
Windows\Installer. The UpgradeCode is, of course, different compared
with the one I was using (displayed by IS UI). Now it looks like some
upgrade is done (files are replaced and on uninstall they are removed
from the system).
I have two questions though related to the upgrade process:
1. When double click on my new msi, it detects there is a previous
product installed (there is a PREVFOUND property set I provided within
the Upgrade sequence of my WiX code), but there is no message saying
Another version of ... like I get when I do an upgrade with two msi
files I generated with WiX but have different versions. It just goes
like a normal install, even if some components are upgraded. What I'd
expect is getting an error when double click (Another version...), but
when launched with REINSTALL=ALL REINSTALLMODE=vomus it should work.
2. At the end of the installation, I have two entries within Add/Remove
Programs list: one with the previous name for the product and under it
the new name for the product. There is just the Remove button for the
previous product version (by design) and clicking on it just removes the
entry from the Add/Remove list (without an installation or whatever).
What I'd expect is no entry for the previous version in the list.
Any ideas why?
Thx,
Dacian
- Original Message
From: Wilson, Phil [EMAIL PROTECTED]
To: wix-users@lists.sourceforge.net
Sent: Friday, June 8, 2007 8:36:03 PM
Subject: Re: [WiX-users] Upgrade InstallShield package
If you can locate the cached MSI file in Windows\installer, opening it
with Orca will show the UpgradeCode in the Property table. That might
help see if you're on the right track. Versions are also another reason
why a major upgrade won't detect an older one.
Phil Wilson
From: fiordean dacian [mailto:[EMAIL PROTECTED]
Sent: Friday, June 08, 2007 10:00 AM
To: Wilson, Phil; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Upgrade InstallShield package
Hi Phil,
Looking through IS log I see ALLUSERS with a value of 1.
Running your script displays Context 4, so there is a per-machine
install done by IS. I have ALLUSERS set to 1 in my WiX source, but there
is no detection for the product IS created.
A strange thing I saw running your script: the product GUID displayed by
your script next to the product name I'm interested is something like
[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:
Class Id={D5DE8D20-5BB8-11D1-A1E3-00A0C90F2731}
Context=InprocServer32 Description=VBPropertyBag
ThreadingModel=apartment /
2) Error CNDL0047: The TypeLib element is non-advertised and therefore
requires a parent File element. This is referring to the following
element:
TypeLib Id={000204EF---C000-0046} Description=Visual
Basic For Applications Language=9 MajorVersion=6 MinorVersion=0
3) another one like (2), referring to:
TypeLib Id={EA544A21-C82D-11D1-A3E4-00A0C90AEA82} Description=Visual
Basic runtime objects and procedures Hidden=yes Language=9
MajorVersion=6 MinorVersion=0
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] Clear out directory before install?
Why doesn't RemoveFile work? Did you set On=install? -Brian Simoneau -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matthew Janulewicz Sent: Tuesday, June 12, 2007 1:08 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Clear out directory before install? I realize this is a certifiable Bad Thing(tm), but it's a situation I haven't much control over. Here's what's going on. Deployment crew deploys website or application .msi's to one set of our production servers. Instead of using the .msi's on all our redundant servers, they xcopy it over to multiple other servers. Next month, deployment crew does the same thing except that they start on a different server, one of the xcopy servers. So the new .msi does not overwrite anything on that server. Then they xcopy it to the original server and regress everything back to where it was last month. Everyone spends half a day trying to figure it out before anyone asks CM about the installers. Problem is then discovered in about 10 seconds. CM gets blamed for having bad installers. I've suggested they 'use the installers correctly' but apparently this is too difficult. There is no 'extra stuff' in any of the directories, so if I could wipe them out completely before the .msi starts InstallFile ... it would solve this 'problem'. Essentially I'm looking for a way to delete items that are not in the file table in an installer prior to installing. I've tried RemoveFile ... / but it doesn't seem to work in the way I would like it to. Or else I'm not doing it right. Any ideas? -- Matthew Janulewicz SCM Engineer Green Dot Corporation [EMAIL PROTECTED] (626) 775-3857 - 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] Adding User Interface to Setup Project in Visual Studio
both I and Cheyne, Mark A - DNR have already replied that you also need to specify Cultures, re-read the post from Mark for detailed instructions. On 6/12/07, Afshin Sepehri [EMAIL PROTECTED] wrote: When I add a reference to WixUIExtension.dll, I get so many errors such as: The localization variable !(loc.WixUIOK) is unknown. Please ensure the variable is defined. Any idea? Afshin *From:* Bob Arnson [mailto:[EMAIL PROTECTED] *Sent:* Monday, June 11, 2007 11:12 PM *To:* Afshin Sepehri *Cc:* wix-users@lists.sourceforge.net *Subject:* Re: [WiX-users] Adding User Interface to Setup Project in Visual Studio Afshin Sepehri wrote: light.exe -out SampleWixUI.msi SampleWixUI.wixobj *path*\wixui.wixlib -loc *path*\WixUI_en-us.wxl That command line is for WiX v2. In v3, you just need to add a reference to WixUIExtension.dll. -- 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 - 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] Adding User Interface to Setup Project in Visual Studio
Add -cultures:en-us (or your supported language of choice) to the light command line as well. - Brett _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Afshin Sepehri Sent: Tuesday, June 12, 2007 1:40 PM To: Bob Arnson Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Adding User Interface to Setup Project in Visual Studio When I add a reference to WixUIExtension.dll, I get so many errors such as: The localization variable !(loc.WixUIOK) is unknown. Please ensure the variable is defined. Any idea? Afshin From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: Monday, June 11, 2007 11:12 PM To: Afshin Sepehri Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Adding User Interface to Setup Project in Visual Studio Afshin Sepehri wrote: light.exe -out SampleWixUI.msi SampleWixUI.wixobj path\wixui.wixlib -loc path\WixUI_en-us.wxl That command line is for WiX v2. In v3, you just need to add a reference to WixUIExtension.dll. -- 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] Adding User Interface to Setup Project in Visual Studio
Sorry, but I missed that part from your email and I did not receive any email from Cheyne, Mark A - DNR. I added the culture and it worked. Thanks, Afshin From: Simon Dahlbacka [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 12, 2007 11:47 AM To: Afshin Sepehri Cc: Bob Arnson; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Adding User Interface to Setup Project in Visual Studio both I and Cheyne, Mark A - DNR have already replied that you also need to specify Cultures, re-read the post from Mark for detailed instructions. On 6/12/07, Afshin Sepehri [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] wrote: When I add a reference to WixUIExtension.dll, I get so many errors such as: The localization variable !(loc.WixUIOK) is unknown. Please ensure the variable is defined. Any idea? Afshin From: Bob Arnson [mailto: [EMAIL PROTECTED]mailto:[EMAIL PROTECTED]] Sent: Monday, June 11, 2007 11:12 PM To: Afshin Sepehri Cc: wix-users@lists.sourceforge.netmailto:wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Adding User Interface to Setup Project in Visual Studio Afshin Sepehri wrote: light.exe -out SampleWixUI.msi SampleWixUI.wixobj path\wixui.wixlib -loc path\WixUI_en-us.wxl That command line is for WiX v2. In v3, you just need to add a reference to WixUIExtension.dll. -- 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.netmailto:WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - 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] If File Assembly='.net' ... /, Assembly added but file not installed?
Using WiX v3.0.2813, If I set the Assembly attribute on a File element to '.net', like this: File Id='Some_DLL' Name='Some.DLL' KeyPath='yes' Assembly='.net' / The assembly gets gac'd, but the actual file does not get installed. Is this the expected behavior? Julie Campbell [EMAIL PROTECTED] _ Scanned by IBM Email Security Management Services powered by MessageLabs. For more information please visit http://www.ers.ibm.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
[WiX-users] VB6 runtime merge modules problem
Hope I'm not wearing out my welcome on this list with all my queries in the last few days... As I understand, a VB6 program is at a minimum dependent on the following files that constitute the VB6 runtime: 1. msvbvm60.dll 2. oleaut32.dll 3. olepro32.dll 4. comcat.dll 5. asycfilt.dll 6. stdole2.tlb (For reference, see http://support.microsoft.com/default.aspx?scid=kb;en-us;290887 and http://nsis.sourceforge.net/Docs/AppendixB.html#B.4) I found a package of *.msm files for VB6 at the Visual Studio 6 SP6 download page: http://msdn2.microsoft.com/en-us/vstudio/aa718364.aspx. They are all dated 3/12/2004. First question - which *.msm files are necessary to get all 6 of the above DLLs? There is not a clear mapping of filenames in all cases. I think I need comcat.msm, oleaut32.msm, and msvbvm60.msm, do I need others? Second question - I get reams of build errors when I try to merge these, for example in my *.wxs file I have: Merge Id=42ABC845-26F9-42ED-BBC9-D1B77F961242 Language=1033 SourceFile=./msm/msvbvm60.msm DiskId=1 / Inside a Directory element, and then later in my Feature element I include a MergeRef, for example MergeRef Id=42ABC845-26F9-42ED-BBC9-D1B77F961242/ Which leads to a bunch of errors like: Error LGHT0204: ICE03: Table: Registry Column: Registry Missing specifications in _Validation Table (or Old Database) Can anyone elaborate? Do I have bad versions of the *.msm files, or should I not be using WiX 3.0? 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-3aec65edd50bdisplaylang=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:
Class Id={D5DE8D20-5BB8-11D1-A1E3-00A0C90F2731}
Context=InprocServer32 Description=VBPropertyBag
ThreadingModel=apartment /
2) Error CNDL0047: The TypeLib element is non-advertised and therefore
requires a parent File element. This is referring to the following
element:
TypeLib Id={000204EF---C000-0046} Description=Visual
Basic For Applications Language=9 MajorVersion=6 MinorVersion=0
3) another one like (2), referring to:
TypeLib Id={EA544A21-C82D-11D1-A3E4-00A0C90AEA82} Description=Visual
Basic runtime objects and procedures Hidden=yes Language=9
MajorVersion=6 MinorVersion=0
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] VB6 runtime merge modules problem
That's funny I was just looking at exactly the same thing, here is what I found: oleaut32.msm - installs olepro32.dll, stdole2.tlb, asycfilt.dll and oleaut32.dll msvbvm60.msm - installs msvbvm60.dll comcat.msm - installs comcat.dll Hope this helps. If you need to find out what the other merge modules install try using Orca from the platform sdk. 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 20:46 To: wix-users@lists.sourceforge.net Subject: [WiX-users] VB6 runtime merge modules problem Hope I'm not wearing out my welcome on this list with all my queries in the last few days... As I understand, a VB6 program is at a minimum dependent on the following files that constitute the VB6 runtime: 1. msvbvm60.dll 2. oleaut32.dll 3. olepro32.dll 4. comcat.dll 5. asycfilt.dll 6. stdole2.tlb (For reference, see http://support.microsoft.com/default.aspx?scid=kb;en-us;290887 and http://nsis.sourceforge.net/Docs/AppendixB.html#B.4) I found a package of *.msm files for VB6 at the Visual Studio 6 SP6 download page: http://msdn2.microsoft.com/en-us/vstudio/aa718364.aspx. They are all dated 3/12/2004. First question - which *.msm files are necessary to get all 6 of the above DLLs? There is not a clear mapping of filenames in all cases. I think I need comcat.msm, oleaut32.msm, and msvbvm60.msm, do I need others? Second question - I get reams of build errors when I try to merge these, for example in my *.wxs file I have: Merge Id=42ABC845-26F9-42ED-BBC9-D1B77F961242 Language=1033 SourceFile=./msm/msvbvm60.msm DiskId=1 / Inside a Directory element, and then later in my Feature element I include a MergeRef, for example MergeRef Id=42ABC845-26F9-42ED-BBC9-D1B77F961242/ Which leads to a bunch of errors like: Error LGHT0204: ICE03: Table: Registry Column: Registry Missing specifications in _Validation Table (or Old Database) Can anyone elaborate? Do I have bad versions of the *.msm files, or should I not be using WiX 3.0? 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-3aec65edd50bdisplaylang=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:
Class Id={D5DE8D20-5BB8-11D1-A1E3-00A0C90F2731}
Context=InprocServer32 Description=VBPropertyBag
ThreadingModel=apartment /
2) Error CNDL0047: The TypeLib element is non-advertised and
therefore requires a parent File element. This is referring to the
following element:
TypeLib Id={000204EF---C000-0046}
Description=Visual Basic For Applications Language=9
MajorVersion=6 MinorVersion=0
3) another one like (2), referring to:
TypeLib Id={EA544A21-C82D-11D1-A3E4-00A0C90AEA82}
Description=Visual Basic runtime objects and procedures Hidden=yes
Language=9 MajorVersion=6 MinorVersion=0
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] How to correct ICE19 and ICE50 errors in .MSI package
Hi I am trying to test my .MSI with ORCA and I am getting the following error messages: ICE19: Shortcut 'startmenuTeamsDesigner10Uni' advertises component:' Component24': This component cannot be advertised because the keypath type disallowed AND ICE50:Component 24 has an advertised shortcut,but the keypath cannot be found. My shortcut has the follwing code in wix file: File Id=file934 Name=teams.exe src=C:\luntbuild\work\TEAMS-10.0\teams\release\program\teams-unicode\teams.exe Vital=yes Shortcut Id=startmenuTeamsDesigner10Uni Directory=ProgramMenuFolder Name=Teams10 LongName=Teams Designer 10.0 WorkingDirectory=TEAMSDIR Icon=teams.exe IconIndex=0 Advertise=yes/ Shortcut Id=desktopTeams10Uni Directory=DesktopFolder Name=Teams10 LongName=Teams Designer 10.0 WorkingDirectory=TEAMSDIR Icon=teams.exe IconIndex=0 Advertise=yes/ /File If I donot advertise them I am getting these error messages: ICE43:Component 'Component24' has non-advertised shortcuts. It should use a registry key under HKCU as its KeyPath. I donot want to create path under HKCU as I need to create under HKLM. Any solutions for this. Please help. Thanks in advance. Regards Venkatesh - 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-3aec65edd50bdisplaylang=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:
Class Id={D5DE8D20-5BB8-11D1-A1E3-00A0C90F2731}
Context=InprocServer32 Description=VBPropertyBag
ThreadingModel=apartment /
2) Error CNDL0047: The TypeLib element is non-advertised and
therefore requires a parent File element. This is referring to the
following element:
TypeLib Id={000204EF---C000-0046}
Description=Visual Basic For Applications Language=9
MajorVersion=6 MinorVersion=0
3) another one like (2), referring to:
TypeLib Id={EA544A21-C82D-11D1-A3E4-00A0C90AEA82}
Description=Visual Basic runtime objects and procedures Hidden=yes
Language=9 MajorVersion=6 MinorVersion=0
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] How to correct ICE19 and ICE50 errors in .MSI package
Also my Icon has the follwoing definition: Icon Id=teams.exe SourceFile=C:\luntbuild\work\TEAMS-10.0\teams\release\program\teams-unicode\teams.exe / Venkatesh -Original Message- From: Venkatesh Malepati Sent: Tuesday, June 12, 2007 5:13 PM To: 'wix-users@lists.sourceforge.net' Subject: How to correct ICE19 and ICE50 errors in .MSI package Hi I am trying to test my .MSI with ORCA and I am getting the following error messages: ICE19: Shortcut 'startmenuTeamsDesigner10Uni' advertises component:' Component24': This component cannot be advertised because the keypath type disallowed AND ICE50:Component 24 has an advertised shortcut,but the keypath cannot be found. My shortcut has the follwing code in wix file: File Id=file934 Name=teams.exe src=C:\luntbuild\work\TEAMS-10.0\teams\release\program\teams-unicode\teams.exe Vital=yes Shortcut Id=startmenuTeamsDesigner10Uni Directory=ProgramMenuFolder Name=Teams10 LongName=Teams Designer 10.0 WorkingDirectory=TEAMSDIR Icon=teams.exe IconIndex=0 Advertise=yes/ Shortcut Id=desktopTeams10Uni Directory=DesktopFolder Name=Teams10 LongName=Teams Designer 10.0 WorkingDirectory=TEAMSDIR Icon=teams.exe IconIndex=0 Advertise=yes/ /File If I donot advertise them I am getting these error messages: ICE43:Component 'Component24' has non-advertised shortcuts. It should use a registry key under HKCU as its KeyPath. I donot want to create path under HKCU as I need to create under HKLM. Any solutions for this. Please help. Thanks in advance. Regards Venkatesh - 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] VB6 runtime merge modules problem SOLUTION
Neil was right on. First of all, if I'd installed orca.exe first, I could have answered my first question by examining the guts of the MSMs. Not the easiest tool to get ahold of, but I found a guy who linked it to his blog: http://blogs.msdn.com/astebner/archive/2004/07/12/180792.aspx As for my second question- why I got the build errors when merging the MS-provided MSMs, Neil was also right on in his reply to my other post: http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg09448.htm l. I added the same 6 EnsureTable elements to my Package element, no more build problems when I merge the VB6 runtime MSMs. Yay! Thanks, Neil. From: Neil Sleightholm [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 12, 2007 4:13 PM To: Cheyne, Mark A - DNR; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] VB6 runtime merge modules problem That's funny I was just looking at exactly the same thing, here is what I found: oleaut32.msm - installs olepro32.dll, stdole2.tlb, asycfilt.dll and oleaut32.dll msvbvm60.msm - installs msvbvm60.dll comcat.msm - installs comcat.dll Hope this helps. If you need to find out what the other merge modules install try using Orca from the platform sdk. 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 20:46 To: wix-users@lists.sourceforge.net Subject: [WiX-users] VB6 runtime merge modules problem Hope I'm not wearing out my welcome on this list with all my queries in the last few days... As I understand, a VB6 program is at a minimum dependent on the following files that constitute the VB6 runtime: 1. msvbvm60.dll 2. oleaut32.dll 3. olepro32.dll 4. comcat.dll 5. asycfilt.dll 6. stdole2.tlb (For reference, see http://support.microsoft.com/default.aspx?scid=kb;en-us;290887 and http://nsis.sourceforge.net/Docs/AppendixB.html#B.4) I found a package of *.msm files for VB6 at the Visual Studio 6 SP6 download page: http://msdn2.microsoft.com/en-us/vstudio/aa718364.aspx. They are all dated 3/12/2004. First question - which *.msm files are necessary to get all 6 of the above DLLs? There is not a clear mapping of filenames in all cases. I think I need comcat.msm, oleaut32.msm, and msvbvm60.msm, do I need others? Second question - I get reams of build errors when I try to merge these, for example in my *.wxs file I have: Merge Id=42ABC845-26F9-42ED-BBC9-D1B77F961242 Language=1033 SourceFile=./msm/msvbvm60.msm DiskId=1 / Inside a Directory element, and then later in my Feature element I include a MergeRef, for example MergeRef Id=42ABC845-26F9-42ED-BBC9-D1B77F961242/ Which leads to a bunch of errors like: Error LGHT0204: ICE03: Table: Registry Column: Registry Missing specifications in _Validation Table (or Old Database) Can anyone elaborate? Do I have bad versions of the *.msm files, or should I not be using WiX 3.0? 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?
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 FRAGMENT 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:
EnsureTable Id=Registry /
EnsureTable Id=Class /
EnsureTable Id=ProgId /
EnsureTable Id=Extension /
EnsureTable Id=MIME /
EnsureTable Id=Verb /
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-3aec65edd50bdisplaylang=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:
Class Id={D5DE8D20-5BB8-11D1-A1E3-00A0C90F2731}
Context=InprocServer32 Description=VBPropertyBag
ThreadingModel=apartment /
2) Error CNDL0047: The TypeLib element is non-advertised
and therefore requires a parent File element. This is referring to the
following element:
TypeLib Id={000204EF---C000-0046}
Description=Visual Basic For Applications Language=9
MajorVersion=6 MinorVersion=0
3) another one like (2), referring to:
TypeLib Id={EA544A21-C82D-11D1-A3E4-00A0C90AEA82}
Description=Visual Basic runtime objects and procedures Hidden=yes
Language=9 MajorVersion=6 MinorVersion=0
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] Question about VS property sheets
Hi, sorry if I missed that somewhere, but I couldn't find references to it anywhere. Is it possible to use the variables (macros in the sense of either environment variables or plain) defined in VS property sheets? This is a highly useful feature of VS and it would make it possible for WiX to use for example paths that are declared in the .vsprops file. Any comments on that? Thanks in advance, -- Oliver Schneider Researcher / Developer FRISK Software International Thverholti 18 IS-105 Reykjavik Iceland +354 540 7400 http://www.f-prot.com | http://forum.f-prot.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 FRAGMENT 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:
EnsureTable Id=Registry /
EnsureTable Id=Class /
EnsureTable Id=ProgId /
EnsureTable Id=Extension /
EnsureTable Id=MIME /
EnsureTable Id=Verb /
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-3aec65edd50bdisplaylang=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:
Class Id={D5DE8D20-5BB8-11D1-A1E3-00A0C90F2731}
Context=InprocServer32 Description=VBPropertyBag
[WiX-users] Wix - Prevent XMLFile updates on Repair option
Hi, I am stuck with few issues and trying to find a solution for it. Please do let me know few pointers if you are aware of their solution. I am developing an installer for my application using WIX (ver 2.0.5325). I am deploying XML files that I modify while installation based on the user input. I am successfull able to install and update the XML files using XMLFile tag. The following are my questions: 1. Typically when you do a repair only the files that are missing or corrupt are deployed which happens to me as well. But even for the existing file XMLFile statement is executed and my files are updated on Repair. The XMLFile tag does not accept any Condition text as the content model is empty. Is there a way out for this? 2. I have noticed that If I have installed my application on a different drive say D:\Program files than the default C:\Program files, in the Repair mode the INSTALLDIR still shows C:\Program files. (I found this when I logged the entries). Hence when in repair mode the installer tries to update the XML files it throws an exception as the path is incorrect in this case. Surprisingly even in this case it rightly replaces all the missing files in D:\program files. I am not sure how it does that:). 3. Is there a way by which I can have the default value of PathEdit control (associated with Browse button) as blank? Thanks in advance for any pointers. Regards. Bhavesh Goradia -- View this message in context: http://www.nabble.com/Wix---Prevent-XMLFile-updates-on-Repair-option-tf3911179.html#a11089460 Sent from the wix-users mailing list archive at Nabble.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
[WiX-users] How to use the output of Heat?
Hi, I am trying to use Heat to auto generate the list of my files to install. However, I do not know how to use the Heat's output file. There are several Fragments, DirectoryRefs, and Components. How can I include this file in my existing project? Do I need to use a set of ComponentRef to refer to all the components one by one? Isn't it possible to add the entire structure with a single reference. Please help. Thanks, Afshin - 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] How to use the output of Heat?
Hi, You can use tallow to add the entire structure. Bhavesh Afshin Sepehri wrote: Hi, I am trying to use Heat to auto generate the list of my files to install. However, I do not know how to use the Heat's output file. There are several Fragments, DirectoryRefs, and Components. How can I include this file in my existing project? Do I need to use a set of ComponentRef to refer to all the components one by one? Isn't it possible to add the entire structure with a single reference. Please help. Thanks, Afshin - 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 -- View this message in context: http://www.nabble.com/How-to-use-the-output-of-Heat--tf3911224.html#a11090133 Sent from the wix-users mailing list archive at Nabble.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
[WiX-users] Having PathEdit control blank associated to Browse Dialog
http://www.nabble.com/file/p11091564/Tool_Setup.jpg Hi, I have just started with Wix and have the following questions. In a dialog I have an optional field for which I have the property linked to the Browse dialog. Currently I am not able to leave this blank as peroperties cannot be left blank and have a default value. Clicking on browse button opens a browse dailog where the user can select the path to the build root. How do I? 1. Have the PathEdit control blank? 2. When the user selects the path it should populate in the PathEdit field 3. A way for the user to RESET already selected value to blank. Any help in this regard will be greatly appreciated. Thanks in advance for the help Regards. Bhavesh -- View this message in context: http://www.nabble.com/Having-PathEdit-control-blank-associated-to-Browse-Dialog-tf3912120.html#a11091564 Sent from the wix-users mailing list archive at Nabble.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] If File Assembly='.net' ... /, Assembly added but file not installed?
Julie Campbell wrote: The assembly gets gac'd, but the actual file does not get installed. Is this the expected behavior? If a file is marked for the GAC, it goes there only. MSI doesn't install the file, then run gacutil or equivalent -- it uses Fusion interfaces directly to install to the GAC. -- 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] How to correct ICE19 and ICE50 errors in .MSI package
Venkatesh Malepati wrote: ICE19: Shortcut 'startmenuTeamsDesigner10Uni' advertises component:' Component24': This component cannot be advertised because the keypath type disallowed AND ICE50:Component 24 has an advertised shortcut,but the keypath cannot be found. My shortcut has the follwing code in wix file: File Id=file934 Name=teams.exe src=C:\luntbuild\work\TEAMS-10.0\teams\release\program\teams-unicode\teams.exe Vital=yes What does your Component element look like? Components with shortcuts should have a single file so there's no confusion about what resource is the component's key path. -- 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?
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] How to use the output of Heat?
Afshin Sepehri wrote: I am trying to use Heat to auto generate the list of my files to install. However, I do not know how to use the Heat's output file. There are several Fragments, DirectoryRefs, and Components. How can I include this file in my existing project? Do I need to use a set of ComponentRef to refer to all the components one by one? Isn't it possible to add the entire structure with a single reference. Please help. Heat is not designed to be used in an automated build process. To see how to use fragments, check out the WiX setup source in src/Setup/*.wxs. -- 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] MinorUpdateTargetRTM problem using Wix v2.0.5002
Nick Nieslanik wrote: When I try to build the MSP with msimsp.exe after creating the PCP including MinorUpdateTargetRTM, I get the following error: ERROR: Patch Metadata property: 'MinorUpdateTargetRTM' is not a generic MSI property. You need to use MsiMsp 3.1 or later -- older versions don't know what to do with it. -- 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] Wix - Prevent XMLFile updates on Repair option
BhaveshG wrote: 1. Typically when you do a repair only the files that are missing or corrupt are deployed which happens to me as well. But even for the existing file XMLFile statement is executed and my files are updated on Repair. The XMLFile tag does not accept any Condition text as the content model is empty. Is there a way out for this? Check out the XmlConfig element. It offers additional control for repair and uninstall. 2. I have noticed that If I have installed my application on a different drive say D:\Program files than the default C:\Program files, in the Repair mode the INSTALLDIR still shows C:\Program files. (I found this when I logged the entries). Hence when in repair mode the installer tries to update the XML files it throws an exception as the path is incorrect in this case. Surprisingly even in this case it rightly replaces all the missing files in D:\program files. I am not sure how it does that:). If you explicitly rely on properties (or directories, which are turned into properties) then you must persist that data and load it during maintenance mode. The easiest way is to write them to the registry and use RegistrySearch to load them. (MSI knows where it installed each component but doesn't store other random data.) 3. Is there a way by which I can have the default value of PathEdit control (associated with Browse button) as blank? No. Each directory has a default value. -- 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] Having PathEdit control blank associated to Browse Dialog
BhaveshG wrote: 1. Have the PathEdit control blank? 2. When the user selects the path it should populate in the PathEdit field 3. A way for the user to RESET already selected value to blank. See my reply to your other message: In short, no; directories must have a default value, starting with the TARGETDIR root. -- 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] Wix - Prevent XMLFile updates on Repair option
Thanks for your reply. I cannot use XmlConfig as I need to update value for the XML elements and XmlConfig I guess only has create and delete options. The other option which I thought and used while repair was to set the condition for the component by having transitive to yes and then checking for Installed but that does not seem to work. Bhavesh Bob Arnson-6 wrote: BhaveshG wrote: 1. Typically when you do a repair only the files that are missing or corrupt are deployed which happens to me as well. But even for the existing file XMLFile statement is executed and my files are updated on Repair. The XMLFile tag does not accept any Condition text as the content model is empty. Is there a way out for this? Check out the XmlConfig element. It offers additional control for repair and uninstall. 2. I have noticed that If I have installed my application on a different drive say D:\Program files than the default C:\Program files, in the Repair mode the INSTALLDIR still shows C:\Program files. (I found this when I logged the entries). Hence when in repair mode the installer tries to update the XML files it throws an exception as the path is incorrect in this case. Surprisingly even in this case it rightly replaces all the missing files in D:\program files. I am not sure how it does that:). If you explicitly rely on properties (or directories, which are turned into properties) then you must persist that data and load it during maintenance mode. The easiest way is to write them to the registry and use RegistrySearch to load them. (MSI knows where it installed each component but doesn't store other random data.) 3. Is there a way by which I can have the default value of PathEdit control (associated with Browse button) as blank? No. Each directory has a default value. -- 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 -- View this message in context: http://www.nabble.com/Wix---Prevent-XMLFile-updates-on-Repair-option-tf3911179.html#a11092731 Sent from the wix-users mailing list archive at Nabble.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] Having PathEdit control blank associated to Browse Dialog
Thanks. You're right the directory needs to have a default value so that it can have a root to start with. But I think there has to be a way of having an Edit or PathEdit control to have a blank entry at the same time associating with a property. Bhavesh Bob Arnson-6 wrote: BhaveshG wrote: 1. Have the PathEdit control blank? 2. When the user selects the path it should populate in the PathEdit field 3. A way for the user to RESET already selected value to blank. See my reply to your other message: In short, no; directories must have a default value, starting with the TARGETDIR root. -- 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 -- View this message in context: http://www.nabble.com/Having-PathEdit-control-blank-associated-to-Browse-Dialog-tf3912120.html#a11092746 Sent from the wix-users mailing list archive at Nabble.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
