Re: [WiX-users] ListView table?
Bob Arnson wrote: Guillaume Girard wrote: Unfortunately, the ListView table is not created in the final MSI file. Shouldn't it be? WiX doesn't create tables unless they're needed. You can use the EnsureTable element to make sure an empty table is created. It makes sense, thank you. I got confused by the ListBox table appearing despite the fact that it's empty and I can't find any EnsureTable for it in the code. But now everything is working. Thank you, Guillaume. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] ICE 03 Error in FizeSize Column on File Table
You can use multiple cabs by specifying multiple Media tags, each one having a different ID. You can then put files in whichever cab by setting [EMAIL PROTECTED] to the relevant id number. I think you can also set [EMAIL PROTECTED], but I'm not sure off the top of my head. Rob Magus wrote: Is there a max size limitation outside of cab files? I have a file that is around 2.06 GB and I am getting this error. When I install it installs fine, but this error will not Fly with microsoft. Is there a way to chop up a file into multiple cabs then let the installer reintegrate the pieces back together? - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] File Chooser Dialog
Hi, I can't find any support in Wix (or rather, in MSI) for building a file chooser dialog. In particular, I'm missing a file list control. Am I just being confused? If this is indeed not supported by Wix/MSI, how would you go building one? I thought of having a custom action filling in a list view, but I'm a little doubtful about re-writing the whole logic behind a file chooser dialog. Would it be possible to use a dialog from another UI in a custom action? Regards, Guillaume Girard. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] File Chooser Dialog
Hi Guillaume,...
The MSI does not support the File browse dialog.
You should check the CFileDialog class in MFC
http://msdn2.microsoft.com/en-us/dk77e5e7(VS.80).aspx
Here is a snippet of the code I was using for the same purpose:
extern C UINT __stdcall CAOpenFileDialog(MSIHANDLE hInstall)
{
CFileDialog dlg;
if(dlg.DoModal() == IDOK)
{
// do something
}
return ERROR_SUCCESS;
}
Regards
Stefan
Guillaume Girard wrote:
Hi,
I can't find any support in Wix (or rather, in MSI) for building a file
chooser dialog. In particular, I'm missing a file list control. Am I
just being confused?
If this is indeed not supported by Wix/MSI, how would you go building
one? I thought of having a custom action filling in a list view, but I'm
a little doubtful about re-writing the whole logic behind a file chooser
dialog. Would it be possible to use a dialog from another UI in a custom
action?
Regards,
Guillaume Girard.
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Stefan Pavlik | [EMAIL PROTECTED]
Whitestein Technologies | www.whitestein.com
Panenska 28 | SK-81103 Bratislava | Slovak Republic
Tel +421(2)5930-0735 | Fax +421(2)5443-5512
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] File Chooser Dialog
It is the C++ CustomAction Type 1 (CA in Dll).
I didn't mention it but I think you have realised that.
Stefan
Stefan Pavlik wrote:
Hi Guillaume,...
The MSI does not support the File browse dialog.
You should check the CFileDialog class in MFC
http://msdn2.microsoft.com/en-us/dk77e5e7(VS.80).aspx
Here is a snippet of the code I was using for the same purpose:
extern C UINT __stdcall CAOpenFileDialog(MSIHANDLE hInstall)
{
CFileDialog dlg;
if(dlg.DoModal() == IDOK)
{
// do something
}
return ERROR_SUCCESS;
}
Regards
Stefan
Guillaume Girard wrote:
Hi,
I can't find any support in Wix (or rather, in MSI) for building a file
chooser dialog. In particular, I'm missing a file list control. Am I
just being confused?
If this is indeed not supported by Wix/MSI, how would you go building
one? I thought of having a custom action filling in a list view, but I'm
a little doubtful about re-writing the whole logic behind a file chooser
dialog. Would it be possible to use a dialog from another UI in a custom
action?
Regards,
Guillaume Girard.
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job
easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Stefan Pavlik | [EMAIL PROTECTED]
Whitestein Technologies | www.whitestein.com
Panenska 28 | SK-81103 Bratislava | Slovak Republic
Tel +421(2)5930-0735 | Fax +421(2)5443-5512
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Custom action executing boo script fails
Hi Nick, Try this: CustomAction Id=InstallScript Directory=[INSTALLSCRIPTINSTALLDIR] ExeCommand='[INSTALLSCRIPTINSTALLDIR]boo\booi.exe [INSTALLSCRIPTINSTALLDIR]install.dir.boo [WEBINSTALLDIR]. [INSTALLDIR]. [DIRECTORYNAME] [DATABASEPASSWORD]' / Add please tell me the sequence of this custom action. Thanks Traits 2007/2/13, nick hemsley [EMAIL PROTECTED]: I am having a problem calling an external boo script from wix. Here is the tag CustomAction Id=InstallScript Property=INSTALLSCRIPTRESULT ExeCommand='[INSTALLSCRIPTINSTALLDIR]boo\booi.exe [INSTALLSCRIPTINSTALLDIR]install.dir.boo [WEBINSTALLDIR]. [INSTALLDIR]. [DIRECTORYNAME] [DATABASEPASSWORD]' / If I paste the command text from the log into a command prompt it runs as expecte. The ExeCommand is quoted using single quotes (as I *think* i need to use double quotes for paths, i havent tested this though). Here is the relevant log section: Error 1721. There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor. Action: InstallScript, location: , command: C:\Program Files\PROGRAM\PROGRAMWebModuleV56\install-script\boo\booi.exe C:\Program Files\PROGRAM\PROGRAMWebModuleV56\install-script\install.dir.boo C:\Program Files\PROGRAM\PROGRAMWebModuleV56\. C:\Program Files\PROGRAM\. PROGRAM test MSI (s) (B4:6C) [19:31:47:268]: Product: AAA PROGRAM V5.6 Web Module -- Error 1721. There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor. Action: InstallScript, location: , command: C:\Program Files\PROGRAM\PROGRAMWebModuleV56\install-script\boo\booi.exe C:\Program Files\PROGRAM\PROGRAMWebModuleV56\install-script\install.dir.boo C:\Program Files\PROGRAM\PROGRAMWebModuleV56\. C:\Program Files\PROGRAM\. PROGRAM test Action ended 19:31:47: InstallScript. Return value 3. Action ended 19:31:47: INSTALL. Return value 3. Thanks for any help. Nick - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Reboot, when driver interface has been changed
Hi, I have following scenario: 1. A deferred InstallDeviceDriver custom action installs device drivers. The custom action checks if the driver interface has been changed? Then it writes a volatile key in the registry, which indicates that a reboot is necessary! CustomAction Id=InstallDeviceDriver FileKey=instw2k.exe ExeCommand=-p quot;[INSTALLDIR]quot; Impersonate=no Execute=deferred/ 2. In WiX a property DOREBOOT, contains the registry value of the volatile key value doreboot, if it is written in the registry? Property Id=DOREBOOT RegistrySearch Id=RebootVolatile Type=raw Root=HKLM Key=SOFTWARE\MyTest\volatilekey Name=doreboot/ /Property 3. The DOREBOOT property is used as ScheduleReboot action condition: InstallExecuteSequence Custom Action=InstallDeviceDriver After=InstallFiles NOT Installed OR UPGRADINGPRODUCTCODE /Custom ScheduleReboot Before=InstallFinalize DOREBOOT /ScheduleReboot /InstallExecuteSequence My questions are: - When is the RegistrySearch launched during installation? - Is it possible to schedule it happen just before ScheduleReboot, in my InstallExecuteSequence? - If this scenario is not possible in WiX? What would be a alternative way of doing this? Thanks in advance, Harry -- View this message in context: http://www.nabble.com/Reboot%2C-when-driver-interface-has-been-changed-tf3220275.html#a8943325 Sent from the wix-users mailing list archive at Nabble.com. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Specifying Backup location
Bob Arnson wrote: [...] MSI doesn't let you configure rollback storage except to disable it entirely. Can this be done from inside Wix? If so, how? Andre' - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Kernel Drivers
Has this issue been resolved with WiX v3 and DIFxApp? On 1/30/07, Rob Mensching [EMAIL PROTECTED] wrote: There is a bug open on WiX v3 about not quite integrating correctly with DIFxApp. *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *Levi Wilson *Sent:* Tuesday, January 30, 2007 5:27 AM *To:* Quinton Tormanen *Cc:* wix-users@lists.sourceforge.net *Subject:* Re: [WiX-users] Kernel Drivers Alright, I'm trying to give this DIFxApp a shot. I'm using Version 3 of WiX, and it will not allow me to put DriverXXX attributes in the component. Nor will it allow me to use the Driver/ element inside my component. I've been trying to go through the article found here ( http://msdn2.microsoft.com/en-gb/library/ms790289.aspx) but can't seem to get past this. Which version of WiX did you use when using DIFxApp? On 1/29/07, *Quinton Tormanen* [EMAIL PROTECTED] wrote: DIFxApp will install hardware drivers if you provide it with the .INF file(s) and the referenced files from the package. Whether a file system driver fits that bill is over my head, although it sounds a bit different. DIFxApp does the equivilant of SetupCopyOemInf and then some. It's job is to get the driver into the driver store. I know that hardware .INF files often include an AddService question, but it sounds like you'll need to wait for one of the big guns to reply to your request... --Quinton -- *From:* Levi Wilson [mailto:[EMAIL PROTECTED] *Sent:* Monday, January 29, 2007 1:26 PM *To:* Quinton Tormanen *Cc:* wix-users@lists.sourceforge.net *Subject:* Re: [WiX-users] Kernel Drivers I neglected to mention that this is not a hardware driver, it is a file system driver. In InstallShield parlance, I used to call _CreateNTService to install it. Is there an equivalent WiX element to achieve this since the ServiceInstall/ doesn't support the @Type=kernelDriver ? Is DIFxAppexactly what I need? Also, why does Windows Installer not support the kernelDriver type? On 1/29/07, *Quinton Tormanen* [EMAIL PROTECTED] wrote: I just added USB drivers to our application installer. The toolkit I used is DIFxApp, which integrates VERY well with WiX. They've even got an example for WiX. The website for DIFx Tools is www.microsoft.com/whdc/driver/install/difxtools.mspx . However, beware that that website doesn't have the latest. It has version 2.01, which doesn't support Vista. To get the newest version (2.1), grab the WDK for Vista. Once you've got DIFx Tools, look at the DIFxApp component and its WiX examples. They read through the Driver* attributes under the Component element, and you should be well on your way! You shouldn't need your own CA (the DIFxApp WiXLib includes its own CAs). Hope this helps! --Quinton -- *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *Levi Wilson *Sent:* Monday, January 29, 2007 7:29 AM *To:* wix-users@lists.sourceforge.net *Subject:* [WiX-users] Kernel Drivers What is the proper way to install a kernel mode driver? I noticed in the help file that the ServiceInstall/ tag says that Windows Installer does not currently support kernelDriver or systemDriver. Do I need to make an INF install and use a CA to perform a rundll32 on it? Any help would be greatly appreciated. Levi - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] ListView table?
Guillaume Girard wrote: I got confused by the ListBox table appearing despite the fact that it's empty and I can't find any EnsureTable for it in the code. It's required if you have just about any UI because the FilesInUse table is required and it has a required ListBox. -- sig://boB http://bobs.org - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Specifying Backup location
André Pönitz wrote: Can this be done from inside Wix? If so, how? See DisableRollback action and DISABLEROLLBACK property in the doc. -- sig://boB http://bobs.org - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Reboot, when driver interface has been changed
1. RegistrySearch is executed when the AppSearch action runs. The AppSearch action usually is one of the very first things executed. 2. I don't think AppSearch will be able to be scheduled deferred which means it won't work for what you are trying to do. 3. It is difficult to impossible to fully integrate a call out to an exe CustomAction into the installer transaction and messaging system. Instead, C/C++ DLLs should be used to read data from MSI tables and call the appropriate APIs in a way that handles install, uninstall, rollback, repair, upgrading and patching. If it isn't apparent, CustomActions that modify machine state take a lot of work to do correctly. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Harry Liljeström Sent: Tuesday, February 13, 2007 4:17 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Reboot, when driver interface has been changed Hi, I have following scenario: 1. A deferred InstallDeviceDriver custom action installs device drivers. The custom action checks if the driver interface has been changed? Then it writes a volatile key in the registry, which indicates that a reboot is necessary! CustomAction Id=InstallDeviceDriver FileKey=instw2k.exe ExeCommand=-p quot;[INSTALLDIR]quot; Impersonate=no Execute=deferred/ 2. In WiX a property DOREBOOT, contains the registry value of the volatile key value doreboot, if it is written in the registry? Property Id=DOREBOOT RegistrySearch Id=RebootVolatile Type=raw Root=HKLM Key=SOFTWARE\MyTest\volatilekey Name=doreboot/ /Property 3. The DOREBOOT property is used as ScheduleReboot action condition: InstallExecuteSequence Custom Action=InstallDeviceDriver After=InstallFiles NOT Installed OR UPGRADINGPRODUCTCODE /Custom ScheduleReboot Before=InstallFinalize DOREBOOT /ScheduleReboot /InstallExecuteSequence My questions are: - When is the RegistrySearch launched during installation? - Is it possible to schedule it happen just before ScheduleReboot, in my InstallExecuteSequence? - If this scenario is not possible in WiX? What would be a alternative way of doing this? Thanks in advance, Harry -- View this message in context: http://www.nabble.com/Reboot%2C-when-driver-interface-has-been-changed-tf3220275.html#a8943325 Sent from the wix-users mailing list archive at Nabble.com. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] adding non-default extension
You probably can't use the standard WiX elements because those will cause your Component to take ownership of the .sln extension (as you note, not something you want to do). Instead, you'll probably have to write a number of targeted registry keys. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Simon Dahlbacka Sent: Monday, February 12, 2007 2:47 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] adding non-default extension I'm trying to add an Extension to an existing file type (.sln if that matters) I've tried with the following snippet... Component Id=FooComponent Guid=PUT-GUID-HERE File Name=Foo.exe Id=FooExe Source=!(wix.SourceDir)Foo.exe/ Extension ContentType=text\plain Id=sln Verb Id=Foo Command=Do foo TargetFile=FooExe Argument='%1'/ /Extension /Component The problem with this is that this becomes the *default* action, which obviously is not what I want for the .sln type, how do I do so that it does *not* become the default action? regards, Simon ps. ALLUSERS=1 or not does not seem to have any effect on this behavior.. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to use the registry to detect if a product is installed
Or better yet, just use the upgrade logic in the Windows Installer... unless of
course you're trying to detect a non-Windows Installer package. In that case,
then you really should use the mechanism the previous product suggests to
detect it. If it is really to go walk around in the ARP registry keys, then I
don't see anything wrong in the syntax... are you sure the registry key exists?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Harvey Werner
Sent: Monday, February 12, 2007 2:09 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to use the registry to detect if a product is installed
I would like to use the Windows registry (and not the file system) to
detect if a package is already installed.
I was thinking of using something like this, but can't seem to get it to
work. I most likely have the logic wrong in CDATA.
Property Id=PACKAGE_INSTALLED
RegistrySearch
Id=REG_FOUND
Root=HKLM
Key=SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{--
--}
Name=ProductVersion
Type=raw
Win64=no /
/Property
Condition
Message=Package X is installed. Please uninstall it before
trying again.
![CDATA[(NOT PACKAGE_INSTALLED) OR REMOVE]]
/Condition
Any advice is appreciated.
--
Harvey Werner
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to use the registry to detect if a productis installed
Yes, the package is pre-installed and the GUID is correct under the
Uninstall key.
-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 13, 2007 9:05 AM
To: Harvey Werner; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to use the registry to detect if
a productis installed
Or better yet, just use the upgrade logic in the Windows
Installer... unless of course you're trying to detect a
non-Windows Installer package. In that case, then you really
should use the mechanism the previous product suggests to
detect it. If it is really to go walk around in the ARP
registry keys, then I don't see anything wrong in the
syntax... are you sure the registry key exists?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Harvey Werner
Sent: Monday, February 12, 2007 2:09 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to use the registry to detect if a
product is installed
I would like to use the Windows registry (and not the file system) to
detect if a package is already installed.
I was thinking of using something like this, but can't seem
to get it to
work. I most likely have the logic wrong in CDATA.
Property Id=PACKAGE_INSTALLED
RegistrySearch
Id=REG_FOUND
Root=HKLM
Key=SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{
--
--}
Name=ProductVersion
Type=raw
Win64=no /
/Property
Condition
Message=Package X is installed. Please uninstall it before
trying again.
![CDATA[(NOT PACKAGE_INSTALLED) OR REMOVE]]
/Condition
Any advice is appreciated.
--
Harvey Werner
--
---
Using Tomcat but need to do more? Need to support web
services, security?
Get stuff done quickly with pre-integrated technology to make
your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on
Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057;
dat=121642
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to use the registry to detect if a productisinstalled
ComponentSearch element.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wilson, Phil
Sent: Tuesday, February 13, 2007 9:19 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to use the registry to detect if a
productisinstalled
I don't know the Wix for an appsearch for a component guid, sorry.
Phil Wilson
-Original Message-
From: Harvey Werner [mailto:[EMAIL PROTECTED]
Sent: Monday, February 12, 2007 3:34 PM
To: Wilson, Phil; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] How to use the registry to detect if a
productisinstalled
I have never used AppSearch before and the WiX docs are very vague on
it.
Can you give me an example of how it's used?
Harvey Werner
-Original Message-
From: Wilson, Phil [mailto:[EMAIL PROTECTED]
Sent: Monday, February 12, 2007 2:43 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to use the registry to detect if a
productisinstalled
There isn't a data item called ProductVersion under those those
registry keys.
Why not use a component guid in an AppSearch instead?
Phil Wilson
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Harvey
Werner
Sent: Monday, February 12, 2007 2:09 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to use the registry to detect if a product
isinstalled
I would like to use the Windows registry (and not the file system) to
detect if a package is already installed.
I was thinking of using something like this, but can't seem to get it
to work. I most likely have the logic wrong in CDATA.
Property Id=PACKAGE_INSTALLED
RegistrySearch
Id=REG_FOUND
Root=HKLM
Key=SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{
--
--}
Name=ProductVersion
Type=raw
Win64=no /
/Property
Condition
Message=Package X is installed. Please uninstall it before
trying again.
![CDATA[(NOT PACKAGE_INSTALLED) OR REMOVE]]
/Condition
Any advice is appreciated.
--
Harvey Werner
--
--
-
Using Tomcat but need to do more? Need to support web services,
security?
Get stuff done quickly with pre-integrated technology to make your job
easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057;
dat=121642
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] ?Bug? in linker
No, .wixlibs are designed to be portable. There was actually a bug a long time ago that absolute paths were preserved in the .wixlib. Thus the .wixlibs were looking for the server CustomAction files in the location we built them on the build server. That's obviously bad. What should actually be happening is that files referenced by the .wixlib should be relative to the location of the .wixlib (wherever that might be). That way you can move around the .wixlibs and their referenced files together (the way we used to move sca.wixlib, scasched.dll and scaexec.dll together). From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cullen Waters Sent: Tuesday, February 13, 2007 10:05 AM To: WiX-users@lists.sourceforge.net Subject: [WiX-users] ?Bug? in linker In my application, we have several wixlibs that we use to wrap functionality for Custom Actions. Recently, we changed the way we were building these slightly, and it broke our build. Previously, we were relying on a particular environment variable to be set, in order for the build to work. This environment variable was the full path to the root of our source control tree, and is different on each machine. We've been moving to Votive, and in doing so, have been removing the dependency on environment variables from our wix source (so we can build in VS). I changed the paths of the files to relative paths. Candle compiled the wixobj file fine, and lit created the wixlib that I expected. When I try to link an MSI that uses this wixlib, though, I get an error that a file with a relative path couldn't be found. I went to the directory where the wixlib was compiled and linked from, and pasted in the path that couldn't be found. It was there, just as expected. Eventually, I realized that light seemed to be resolving the path from the directory where the MSI was linking from, not the directory where the wxs file for the wixlib resided. This seemed strange, since light has the directory of the source file. I think this is a bug, and I think that Lit should be changed to resolve all relative paths to absolute paths when it builds the wixlib file. What do others think? Cullen Waters SDET Office Live +1 425 706 6809 x 66809 - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] ?Bug? in linker
That's not the behavior I'm seeing. I saved the wixlib files, so you can see the paths that are in there. The wixlib and the file it references are both built to the same directory, but the wixlib contains the path from the .wxs source file to the binary reference. Since we build to a 'Target' directory, that path is invalid when the wixlib is compiled. From: Rob Mensching Sent: Tuesday, February 13, 2007 10:26 AM To: Cullen Waters; WiX-users@lists.sourceforge.net Subject: RE: [WiX-users] ?Bug? in linker No, .wixlibs are designed to be portable. There was actually a bug a long time ago that absolute paths were preserved in the .wixlib. Thus the .wixlibs were looking for the server CustomAction files in the location we built them on the build server. That's obviously bad. What should actually be happening is that files referenced by the .wixlib should be relative to the location of the .wixlib (wherever that might be). That way you can move around the .wixlibs and their referenced files together (the way we used to move sca.wixlib, scasched.dll and scaexec.dll together). From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cullen Waters Sent: Tuesday, February 13, 2007 10:05 AM To: WiX-users@lists.sourceforge.net Subject: [WiX-users] ?Bug? in linker In my application, we have several wixlibs that we use to wrap functionality for Custom Actions. Recently, we changed the way we were building these slightly, and it broke our build. Previously, we were relying on a particular environment variable to be set, in order for the build to work. This environment variable was the full path to the root of our source control tree, and is different on each machine. We've been moving to Votive, and in doing so, have been removing the dependency on environment variables from our wix source (so we can build in VS). I changed the paths of the files to relative paths. Candle compiled the wixobj file fine, and lit created the wixlib that I expected. When I try to link an MSI that uses this wixlib, though, I get an error that a file with a relative path couldn't be found. I went to the directory where the wixlib was compiled and linked from, and pasted in the path that couldn't be found. It was there, just as expected. Eventually, I realized that light seemed to be resolving the path from the directory where the MSI was linking from, not the directory where the wxs file for the wixlib resided. This seemed strange, since light has the directory of the source file. I think this is a bug, and I think that Lit should be changed to resolve all relative paths to absolute paths when it builds the wixlib file. What do others think? Cullen Waters SDET Office Live +1 425 706 6809 x 66809 - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] ?Bug? in linker
That sounds like the bug I remember. Maybe it hasn't been fixed yet. I have not been in to the WiX v3 Binder in a long time... focused on finishing WiX v2. From: Cullen Waters Sent: Tuesday, February 13, 2007 10:28 AM To: Rob Mensching; WiX-users@lists.sourceforge.net Subject: RE: [WiX-users] ?Bug? in linker That's not the behavior I'm seeing. I saved the wixlib files, so you can see the paths that are in there. The wixlib and the file it references are both built to the same directory, but the wixlib contains the path from the .wxs source file to the binary reference. Since we build to a 'Target' directory, that path is invalid when the wixlib is compiled. From: Rob Mensching Sent: Tuesday, February 13, 2007 10:26 AM To: Cullen Waters; WiX-users@lists.sourceforge.net Subject: RE: [WiX-users] ?Bug? in linker No, .wixlibs are designed to be portable. There was actually a bug a long time ago that absolute paths were preserved in the .wixlib. Thus the .wixlibs were looking for the server CustomAction files in the location we built them on the build server. That's obviously bad. What should actually be happening is that files referenced by the .wixlib should be relative to the location of the .wixlib (wherever that might be). That way you can move around the .wixlibs and their referenced files together (the way we used to move sca.wixlib, scasched.dll and scaexec.dll together). From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cullen Waters Sent: Tuesday, February 13, 2007 10:05 AM To: WiX-users@lists.sourceforge.net Subject: [WiX-users] ?Bug? in linker In my application, we have several wixlibs that we use to wrap functionality for Custom Actions. Recently, we changed the way we were building these slightly, and it broke our build. Previously, we were relying on a particular environment variable to be set, in order for the build to work. This environment variable was the full path to the root of our source control tree, and is different on each machine. We've been moving to Votive, and in doing so, have been removing the dependency on environment variables from our wix source (so we can build in VS). I changed the paths of the files to relative paths. Candle compiled the wixobj file fine, and lit created the wixlib that I expected. When I try to link an MSI that uses this wixlib, though, I get an error that a file with a relative path couldn't be found. I went to the directory where the wixlib was compiled and linked from, and pasted in the path that couldn't be found. It was there, just as expected. Eventually, I realized that light seemed to be resolving the path from the directory where the MSI was linking from, not the directory where the wxs file for the wixlib resided. This seemed strange, since light has the directory of the source file. I think this is a bug, and I think that Lit should be changed to resolve all relative paths to absolute paths when it builds the wixlib file. What do others think? Cullen Waters SDET Office Live +1 425 706 6809 x 66809 - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] ?Bug? in linker
We've found a workaround for now, so it's not a critical issue for us, but something that probably should be fixed. From: Rob Mensching Sent: Tuesday, February 13, 2007 10:37 AM To: Cullen Waters; WiX-users@lists.sourceforge.net Subject: RE: [WiX-users] ?Bug? in linker That sounds like the bug I remember. Maybe it hasn't been fixed yet. I have not been in to the WiX v3 Binder in a long time... focused on finishing WiX v2. From: Cullen Waters Sent: Tuesday, February 13, 2007 10:28 AM To: Rob Mensching; WiX-users@lists.sourceforge.net Subject: RE: [WiX-users] ?Bug? in linker That's not the behavior I'm seeing. I saved the wixlib files, so you can see the paths that are in there. The wixlib and the file it references are both built to the same directory, but the wixlib contains the path from the .wxs source file to the binary reference. Since we build to a 'Target' directory, that path is invalid when the wixlib is compiled. From: Rob Mensching Sent: Tuesday, February 13, 2007 10:26 AM To: Cullen Waters; WiX-users@lists.sourceforge.net Subject: RE: [WiX-users] ?Bug? in linker No, .wixlibs are designed to be portable. There was actually a bug a long time ago that absolute paths were preserved in the .wixlib. Thus the .wixlibs were looking for the server CustomAction files in the location we built them on the build server. That's obviously bad. What should actually be happening is that files referenced by the .wixlib should be relative to the location of the .wixlib (wherever that might be). That way you can move around the .wixlibs and their referenced files together (the way we used to move sca.wixlib, scasched.dll and scaexec.dll together). From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cullen Waters Sent: Tuesday, February 13, 2007 10:05 AM To: WiX-users@lists.sourceforge.net Subject: [WiX-users] ?Bug? in linker In my application, we have several wixlibs that we use to wrap functionality for Custom Actions. Recently, we changed the way we were building these slightly, and it broke our build. Previously, we were relying on a particular environment variable to be set, in order for the build to work. This environment variable was the full path to the root of our source control tree, and is different on each machine. We've been moving to Votive, and in doing so, have been removing the dependency on environment variables from our wix source (so we can build in VS). I changed the paths of the files to relative paths. Candle compiled the wixobj file fine, and lit created the wixlib that I expected. When I try to link an MSI that uses this wixlib, though, I get an error that a file with a relative path couldn't be found. I went to the directory where the wixlib was compiled and linked from, and pasted in the path that couldn't be found. It was there, just as expected. Eventually, I realized that light seemed to be resolving the path from the directory where the MSI was linking from, not the directory where the wxs file for the wixlib resided. This seemed strange, since light has the directory of the source file. I think this is a bug, and I think that Lit should be changed to resolve all relative paths to absolute paths when it builds the wixlib file. What do others think? Cullen Waters SDET Office Live +1 425 706 6809 x 66809 - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Question about logging from a WIX install
That actually does help, and what I have learned is that case sensitivity is the issue here. If, on my install, I have mydomainname=domain\account (and provided I make the change that Rob suggested below), I will see the command line. But if I have it MYDOMAINNAME=domain\account, the value will be appropriately hidden. Why is WIX so inconsistent about case sensitivity? In my example above, the wrong case screws up whether or not MYDOMAINNAME is hidden or not. But passing in lowercase certainly does work internally (the value for the variable is set properly). That seems wrong. Andy From: Rob Mensching Sent: Monday, February 12, 2007 3:06 PM To: Andy Ness; wix-users@lists.sourceforge.net Subject: RE: Question about logging from a WIX install My only guess would be to do something like: Property Id=MYDOMAINPASSWORD Hidden=yes / That may or may not work for command-line properties. From: Andy Ness Sent: Monday, February 12, 2007 10:25 AM To: wix-users@lists.sourceforge.net; Rob Mensching; Justin Rockwood Subject: Question about logging from a WIX install I have an MSI file created via WIX. In there, I install some services. For these services, I need a domain account name and password. This information is passed in to my MSI via the command line of MSIEXEC (egg. msiexec /qn /I MyInstall.msi /L*vx c:\install.log MYDOMAINNAME=domain\account MYDOMAINPASSWORD=MyPassword). In the log file, I want to hide instances of the password. I have found I can do that by making sure the property is hidden, and by using the HideTarget='Yes' tag on my CustomAction (when I look in the install.log file at the point where the custom action is being run, the password is correctly hidden). The problem is, very much near the top of my install.log file is the full command line. It says Command Line: MYDOMAINNAME=domain\account MYDOMAINPASSWORD=MyPassword. Well, this somewhat defeats the purpose of trying to hide this information. Does anyone have any suggestions on how the command line can be truly hidden in the log files? Thanks, Andy - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Error 1604
Thanks Fredrik. That was I need and it works now. From: Fredrik Grohn [mailto:[EMAIL PROTECTED] Sent: Saturday, February 10, 2007 1:35 AM To: Leila Lali (Excell Data Corporation); wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Error 1604 Are you using WCAUtil form your custom action? If you do, there is a call WcaErrorMessage(), it has a prinf like syntax so it should be easy to use. Your option is to call MsiProcessMessage() directly (see MSDN for appropriate values for the eMessageType parameter). The values for the placeholders goes in the hRecord parameter, again see MSDN for details. Is the work you need to do to determine the installation state of the product in question very complex? Other ways look at the LaunchCondition and AppSearch tables respectively, you might be able to get away without having to write a custom action. Fredrik From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Leila Lali (Excell Data Corporation) Sent: Saturday, February 10, 2007 2:19 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Error 1604 Hi, I need to show error 1604 for a custom action, this error is : The product '[2]' is already installed, and has prevented the installation of this product. But the value of [2] is nothing in error dialog. I didn't find any sample or doc for how to use these kind of errors. Does anybody knows any doc about using these errors? Thanks Leila - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Question about logging from a WIX install
It's not Wix as much as it is that Windows Installer property names are case-sensitive (one of the reasons being that all uppercase means that it's a public property). Phil Wilson From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andy Ness Sent: Tuesday, February 13, 2007 11:04 AM To: Rob Mensching; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Question about logging from a WIX install That actually does help, and what I have learned is that case sensitivity is the issue here. If, on my install, I have mydomainname=domain\account (and provided I make the change that Rob suggested below), I will see the command line. But if I have it MYDOMAINNAME=domain\account, the value will be appropriately hidden. Why is WIX so inconsistent about case sensitivity? In my example above, the wrong case screws up whether or not MYDOMAINNAME is hidden or not. But passing in lowercase certainly does work internally (the value for the variable is set properly). That seems wrong. Andy From: Rob Mensching Sent: Monday, February 12, 2007 3:06 PM To: Andy Ness; wix-users@lists.sourceforge.net Subject: RE: Question about logging from a WIX install My only guess would be to do something like: Property Id=MYDOMAINPASSWORD Hidden=yes / That may or may not work for command-line properties. From: Andy Ness Sent: Monday, February 12, 2007 10:25 AM To: wix-users@lists.sourceforge.net; Rob Mensching; Justin Rockwood Subject: Question about logging from a WIX install I have an MSI file created via WIX. In there, I install some services. For these services, I need a domain account name and password. This information is passed in to my MSI via the command line of MSIEXEC (egg. msiexec /qn /I MyInstall.msi /L*vx c:\install.log MYDOMAINNAME=domain\account MYDOMAINPASSWORD=MyPassword). In the log file, I want to hide instances of the password. I have found I can do that by making sure the property is hidden, and by using the HideTarget='Yes' tag on my CustomAction (when I look in the install.log file at the point where the custom action is being run, the password is correctly hidden). The problem is, very much near the top of my install.log file is the full command line. It says Command Line: MYDOMAINNAME=domain\account MYDOMAINPASSWORD=MyPassword. Well, this somewhat defeats the purpose of trying to hide this information. Does anyone have any suggestions on how the command line can be truly hidden in the log files? Thanks, Andy - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] ?Bug? in linker
Totally agree. Can you make sure abug is open to track the issue. From: Cullen Waters Sent: Tuesday, February 13, 2007 10:43 AM To: Rob Mensching; WiX-users@lists.sourceforge.net Subject: RE: [WiX-users] ?Bug? in linker We've found a workaround for now, so it's not a critical issue for us, but something that probably should be fixed. From: Rob Mensching Sent: Tuesday, February 13, 2007 10:37 AM To: Cullen Waters; WiX-users@lists.sourceforge.net Subject: RE: [WiX-users] ?Bug? in linker That sounds like the bug I remember. Maybe it hasn't been fixed yet. I have not been in to the WiX v3 Binder in a long time... focused on finishing WiX v2. From: Cullen Waters Sent: Tuesday, February 13, 2007 10:28 AM To: Rob Mensching; WiX-users@lists.sourceforge.net Subject: RE: [WiX-users] ?Bug? in linker That's not the behavior I'm seeing. I saved the wixlib files, so you can see the paths that are in there. The wixlib and the file it references are both built to the same directory, but the wixlib contains the path from the .wxs source file to the binary reference. Since we build to a 'Target' directory, that path is invalid when the wixlib is compiled. From: Rob Mensching Sent: Tuesday, February 13, 2007 10:26 AM To: Cullen Waters; WiX-users@lists.sourceforge.net Subject: RE: [WiX-users] ?Bug? in linker No, .wixlibs are designed to be portable. There was actually a bug a long time ago that absolute paths were preserved in the .wixlib. Thus the .wixlibs were looking for the server CustomAction files in the location we built them on the build server. That's obviously bad. What should actually be happening is that files referenced by the .wixlib should be relative to the location of the .wixlib (wherever that might be). That way you can move around the .wixlibs and their referenced files together (the way we used to move sca.wixlib, scasched.dll and scaexec.dll together). From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cullen Waters Sent: Tuesday, February 13, 2007 10:05 AM To: WiX-users@lists.sourceforge.net Subject: [WiX-users] ?Bug? in linker In my application, we have several wixlibs that we use to wrap functionality for Custom Actions. Recently, we changed the way we were building these slightly, and it broke our build. Previously, we were relying on a particular environment variable to be set, in order for the build to work. This environment variable was the full path to the root of our source control tree, and is different on each machine. We've been moving to Votive, and in doing so, have been removing the dependency on environment variables from our wix source (so we can build in VS). I changed the paths of the files to relative paths. Candle compiled the wixobj file fine, and lit created the wixlib that I expected. When I try to link an MSI that uses this wixlib, though, I get an error that a file with a relative path couldn't be found. I went to the directory where the wixlib was compiled and linked from, and pasted in the path that couldn't be found. It was there, just as expected. Eventually, I realized that light seemed to be resolving the path from the directory where the MSI was linking from, not the directory where the wxs file for the wixlib resided. This seemed strange, since light has the directory of the source file. I think this is a bug, and I think that Lit should be changed to resolve all relative paths to absolute paths when it builds the wixlib file. What do others think? Cullen Waters SDET Office Live +1 425 706 6809 x 66809 - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] adding non-default extension
ok, thanks for that... Just in case that someone else happens to need to do the same thing: Component Id=DependencyVisualizerComponent Guid=PUT-GUID-HERE File Name=DependencyVisualizer.exe Id=DependencyVisualizerExe Source=!(wix.SourceDir)DependencyVisualizer.exe/ RegistryKey Action=createAndRemoveOnUninstall Root=HKCR Key=VisualStudio.Launcher.sln\Shell\Visualize RegistryValue Action=write Value=Visualize Dependencies Type=string / RegistryKey Action=createAndRemoveOnUninstall Key=Command RegistryValue Action=write Type=string Value=quot;[#DependencyVisualizerExe]quot; quot;%1quot;/ /RegistryKey /RegistryKey !-- This is how it should be done, if it would have worked.. RobMen @ 13.2 -07: You probably can't use the standard WiX elements because those will cause your Component to take ownership of the .sln extension (as you note, not something you want to do). Instead, you'll probably have to write a number of targeted registry keys. Extension ContentType=text\plain Id=sln Verb Id=Visualize Command=Visualize dependencies TargetFile=DependencyVisualizerExe Argument='%1'/ /Extension -- /Component On 2/13/07, Rob Mensching [EMAIL PROTECTED] wrote: You probably can't use the standard WiX elements because those will cause your Component to take ownership of the .sln extension (as you note, not something you want to do). Instead, you'll probably have to write a number of targeted registry keys. *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *Simon Dahlbacka *Sent:* Monday, February 12, 2007 2:47 PM *To:* wix-users@lists.sourceforge.net *Subject:* [WiX-users] adding non-default extension I'm trying to add an Extension to an existing file type (.sln if that matters) I've tried with the following snippet... Component Id=FooComponent Guid=PUT-GUID-HERE File Name=Foo.exe Id=FooExe Source=!(wix.SourceDir)Foo.exe/ Extension ContentType=text\plain Id=sln Verb Id=Foo Command=Do foo TargetFile=FooExe Argument='%1'/ /Extension /Component The problem with this is that this becomes the *default* action, which obviously is not what I want for the .sln type, how do I do so that it does *not* become the default action? regards, Simon ps. ALLUSERS=1 or not does not seem to have any effect on this behavior.. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Delete a virtual directory
Is there a command to delete a virtual directory if it exists? - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Com registration using tallow
Hi, I have a question about using wix to author an installer package. I am trying to register a com interop, from all of the reading I have done I understand that I shouldn't use AssemblyRegisterComInterop=yes and I shouldn't call a custom action that uses regsvr32. So what I SHOULD do if I understand correctly, is use tallow.exe to extract the specific registration and then include that in my wix xml file. However, I am having some problems using tallow. I have tried: tallow -c myAssembly.dll, but I get a Failed to load Assembly, System.BadImageFormatException. I have also tried: tallow -s myAssembly.dll to try to get the registry keys but I then get a Failed to SelfReg error. (which is strange because I can manually use regsvr32 to register it on this same machine). I have also tried tallow - reg myRegFile.rgs, but I then just get an empty wix fragment, which is strange because the rgs file is not empty. Any advice as to what I'm doing wrong, or where I should go from here would be greatly appreciated, Thanks! Lindsay Harris - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Windows Forms App
I don't know if this issue is WIX related, or something completely random. I had developed an app that was deployed using Xcopy via a batch file. Recently my PM decided to port it to WIX because of my newly gained WIX powers. Anyway, this app has a bunch of .dll files and a Windows Forms app that references a couple of these .dll files. There are no problems with the installer and everything installs just fine. But as soon as I try and launch the .exe file (the Windows Form), it crashes. The Windows Forms app has no problems, whatsoever, if deployed via Xcopy. I am not sure if how I have laid out my Components (the Name attribute for backward compatiblity, etc.) in the WIX file is screwing up somehow... This is a .NET 2.0 app being deployed on W2K3 server. I haven't tried installing it on XP. Thanks in advance, folks! - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Bootstrapper
Hi All, I know this topic has been of much discussion and I have looked through all of the previous mailings but am still unable to produce what I need. All I want is a bootstrapper that is similar to InstallShield to perform minor upgrades. I need to: 1. Ensure prerequisites are present and if not then install (.NET 2.0, Windows Installer 3.1) 2. Get the product code of the package. 3. Check if the product code is already installed. 4. If it isn't, launch the install normally. 5. If it is and the package code is the same, launch maintenance mode. 6. If the package code is different, launch the install in reinstall mode. Preferably I would like to display a splash screen while the bootstrapper fires up msiexec. Almost all the requirements are handled very nicely by the Visual Studio 2005 GenerateBootstrapper task and is the preferred solution, however it does not handle requirement 6. Changing the product code would resolve this, but then I need to mess with my msi and schedule RemoveExistingProducts near the end of the install to maintain settings in files like the web.config, as far as I know. Is this the recommended action? It is direction I'm leaning towards. The other option using the Bootstrapper at http://sourceforge.net/tracker/?group_id=105970atid=654188 and modifying it with msistuff.exe setup.exe /o INSTALLUPD /d mymsi.msi /b mymsi.msi /v 200 /n My Product. Using this requirements 1 and 5 aren't satisfied. Another option I have read is to use the GenerateBootstrapper task to launch a C# UI and check everything with that. But this sounds like a lot of unnecessary work and I don't know how to go about this. Also with either bootstrapper option I have tried the Visual Styles of my installer are gone. This is a minor issue except that the ComboBox drop down list do not show (you have to use the up and down keys to go through the options). Has anyone else experienced this? Thanks, -Matthew Rowan - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Custom action executing boo script fails
Thanks alot, That did the trick, however the Directory attrib expects a property id of an existing Directory, so no need for the []: CustomAction Id=InstallScript Directory=INSTALLSCRIPTINSTALLDIR ExeCommand='[INSTALLSCRIPTINSTALLDIR]boo\booi.exe [INSTALLSCRIPTINSTALLDIR]install.dir.boo [WEBINSTALLDIR]. [INSTALLDIR]. [DIRECTORYNAME] [DATABASEPASSWORD]' / Cheers - Nick On 2/13/07, Traits Zhang [EMAIL PROTECTED] wrote: Hi Nick, Try this: CustomAction Id=InstallScript Directory=[INSTALLSCRIPTINSTALLDIR] ExeCommand='[INSTALLSCRIPTINSTALLDIR]boo\booi.exe [INSTALLSCRIPTINSTALLDIR]install.dir.boo [WEBINSTALLDIR]. [INSTALLDIR]. [DIRECTORYNAME] [DATABASEPASSWORD]' / Add please tell me the sequence of this custom action. Thanks Traits 2007/2/13, nick hemsley [EMAIL PROTECTED]: I am having a problem calling an external boo script from wix. Here is the tag CustomAction Id=InstallScript Property=INSTALLSCRIPTRESULT ExeCommand='[INSTALLSCRIPTINSTALLDIR]boo\booi.exe [INSTALLSCRIPTINSTALLDIR]install.dir.boo [WEBINSTALLDIR]. [INSTALLDIR]. [DIRECTORYNAME] [DATABASEPASSWORD]' / If I paste the command text from the log into a command prompt it runs as expecte. The ExeCommand is quoted using single quotes (as I *think* i need to use double quotes for paths, i havent tested this though). Here is the relevant log section: Error 1721. There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor. Action: InstallScript, location: , command: C:\Program Files\PROGRAM\PROGRAMWebModuleV56\install-script\boo\booi.exe C:\Program Files\PROGRAM\PROGRAMWebModuleV56\install-script\install.dir.boo C:\Program Files\PROGRAM\PROGRAMWebModuleV56\. C:\Program Files\PROGRAM\. PROGRAM test MSI (s) (B4:6C) [19:31:47:268]: Product: AAA PROGRAM V5.6 Web Module -- Error 1721. There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor. Action: InstallScript, location: , command: C:\Program Files\PROGRAM\PROGRAMWebModuleV56\install-script\boo\booi.exe C:\Program Files\PROGRAM\PROGRAMWebModuleV56\install-script\install.dir.boo C:\Program Files\PROGRAM\PROGRAMWebModuleV56\. C:\Program Files\PROGRAM\. PROGRAM test Action ended 19:31:47: InstallScript. Return value 3. Action ended 19:31:47: INSTALL. Return value 3. Thanks for any help. Nick - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Windows Forms App
On 2/14/07, Dhaval Patel [EMAIL PROTECTED] wrote: I don't know if this issue is WIX related, or something completely random. I had developed an app that was deployed using Xcopy via a batch file. Recently my PM decided to port it to WIX because of my newly gained WIX powers. Anyway, this app has a bunch of .dll files and a Windows Forms app that references a couple of these .dll files. There are no problems with the installer and everything installs just fine. But as soon as I try and launch the .exe file (the Windows Form), it crashes. The Windows Forms app has no problems, whatsoever, if deployed via Xcopy. I am not sure if how I have laid out my Components (the Name attribute for backward compatiblity, etc.) in the WIX file is screwing up somehow... This is a .NET 2.0 app being deployed on W2K3 server. I haven't tried installing it on XP. Thanks in advance, folks! How does the application crash? The exception should give you some clues to track down the problem. Although since it works when you copy the files a possible cause could be that one or more of the files are missing or were installed in the wrong location. /Johan - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
