Re: [WiX-users] Failed to create web application. (-2147024809)
I'm pretty sure Octopus (being someone who has not actually used it) has an option to enable MSI logging. You received the generic "installation failed" error result. You will need to look at the MSI logging to determine the reason for the error. The "Failed to create web application" message has an error code of 0x80070057="The parameter is incorrect." It would be useful to know of the differences between the 2003 server targeted by Octopus and the one you tested directly, especially as regards any already existing web applications/contents of those applications in IIS. -Original Message- From: Sandeep Kumar Bushnam (Wipro Ltd.) [mailto:v-san...@microsoft.com] Sent: Tuesday, September 15, 2009 10:57 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Failed to create web application. (-2147024809) Hi Team, My MSI creates a virtual directory under a default website and creates a new web application under existing App pool(this case DefaultAppPool). Which is working fine on windows 2003 OS. When I install the same MSI using Microsoft Octopus from Win7 onto windows 2003 server the installer throws below error. [ERROR] ROMDVWEBV01 : Installers\ROMBSCallBack\ROMBSCallBack.msi: Failed to create web application. (-2147024809 /Root/ROMBSCALLBACK ) [ERROR] ROMDVWEBV01 : Installers\ROMBSCallBack\ROMBSCallBack.msi: Error Code 1603: Fatal error during installation. (Exception from HRESULT: 0x80070643) [ERROR] Error occurred. Waiting for all active server executors to finish current task Any help is highly appreciated. Thanks, Sandeep. -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] launching page localization
The list server generally strips attachments. Before Windows Installer has finished parsing the MSI database file to determine what language it is in, it uses the user/system locale to show the first messages. One of the core wix-team members blogged about that (it seems like it was 3-4 years ago?) describing the process (I forget which one and I would have to research it to provide the link). Once it gets going, does it show the messages in the correct language? Or does it continue with the "wrong" language? -Original Message- From: Lian Jiang [mailto:lji...@microsoft.com] Sent: Tuesday, September 15, 2009 1:00 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] launching page localization Hi, I localized all strings used in my installer UI. The installer is a MUI based msi which means the same MSI can work on different locale machines and shows the strings in the corresponding locale. All dialogs works fine except that the launching page (the verify first dialog showing something like "installation starts ...") shows strings incorrectly. For example, I saw it shows other language when running on an en-us machine and it shows English when running on other locales machine. The launching page shown in en-us locale machine is attached. Thanks for any clue. Thanks Lian -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditional installed based on REG_MULTI_SZ value
I had never really thought about bootstrapping WI v4.5 with Installer. Does WiX 3.0 support Windows Installer 4.5 Or alternatively how can I check if v4.5 is installed so I can throw up an conditional message. Dominique. -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: 15 September 2009 16:03 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Conditional installed based on REG_MULTI_SZ value In that case are you bootstrapping the Windows Installer 4.5 redistributable before your installer runs so all your users/customers will be able to successfully install your product or are you also testing it on 3.1 & 4.0 to make sure they don't have problems? According to the docs (http://wix.sourceforge.net/manual-wix3/read_a_registry_entry.htm) before LaunchConditions should be fine but I would double check a verbose log just to make sure your RegistrySearch is populating the SQLSERVER Property before your CustomAction attempts to parse it. Palbinder Sandher Software Deployment & IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the ** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Dominique Louis [mailto:dominique.lo...@amxeurope.com] Sent: 15 September 2009 14:53 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Conditional installed based on REG_MULTI_SZ value I'm using v4.5.6001.22159 if that is any help to anyone. Is putting my CustomAction before LaunchConditions the best place to run my vbs, or would there be another more appropriate place? Dominique. -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: 15 September 2009 10:23 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Conditional installed based on REG_MULTI_SZ value No but you could attribute it to a bug in whichever version of Windows Installer you're using to test the MSI (v3.1 or v4.0 whether you're on XP/2k3 or Vista/2k8 respectively I'm guessing). People on this list really need to learn the difference between WiX & Windows Installer. They are *not* the same thing & should never be used interchangeably as if far too often the case. You'll have to write your own Custom Action to parse the registry value before you compare it as far as I know. Would be nice if there was some sort of Standard Custom Action in WiX for manipulating regex but then there's already plenty of features which existed in WiX v2.0 which we have to live without in WiX v3.0 so I wouldn't hold my breath. Palbinder Sandher Software Deployment & IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the ** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Dominique Louis [mailto:dominique.lo...@amxeurope.com] Sent: 15 September 2009 09:42 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Conditional installed based on REG_MULTI_SZ value Hi Blair, Can we attribute this to a bug in WiX 3.0 then? If I need to write a work around, does WiX provide any parsing capabilities, or should I look at using VBScript or similar to get this working? Dominique. -Original Message- From: Blair [mailto:os...@live.com] Sent: 14 September 2009 17:34 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Conditional installed based on REG_MULTI_SZ value In my tests using a simple installation package, it would appear that the conditional comparison routines for strings stop looking through the string at the first NUL character. Since REG_MULTI_SZ strings start with a NUL, then terminate each value with an additional NUL (remember that the conditional is evaluated AFTER the string is parsed replacing all "[whatever]" property references) means that the conditional syntax can't "see" any values after the first [~] value (which would include all values retrieved using RegistrySearch involving REG_MULTI_SZ strings. You can check for presence of the property, however. (If the property were truly empty, it would be removed). To see what I am talking about, compare these three lines from my log: AppSearch: Property: MYMULTIVALUE, Signature: MyMultiValue MSI (c) (38:98) [09:26:38:902]: PROPERTY CHANGE: Adding MYMULTIVALUE property. Its value is ''. Property(C): MYMULTIVALUE = [~]SysClass.Dll,StorageCoInstaller[~]WmiProp.dll,WmiPropCoInstaller[~] Those are the only references to that property in the entire debug verbose log. You would need some custom action to parse or o
Re: [WiX-users] (no subject)
That means Windows Installer is "thinking". We get it with patches when you click on the Next button on WelcomeDlg as at that point the Windows Installer is inventorying the product's currently installed components & keypaths etc. Not sure what would cause it with an MSI, possibly a large number of things like RegistrySearch, FileSearch or if you're using the major upgrade functionality and you currently have an older product installed which has a large number of files/components/etc. Nothing to be worried about, just Windows Installer doing it's job properly & you should just click the return button rather than cancelling & restarting as it'll likely be no faster. Palbinder Sandher Software Deployment & IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the ** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Alex Ivanoff [mailto:alex.ivan...@shavlik.com] Sent: 15 September 2009 17:04 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] (no subject) >From time to time I am getting the following dialog during install that never disappears and prevents installation from continuing: Please wait while installer finishes determining your disk space requirements. If I cancel the install and then restart it again most likely it will work. What may be going on? Alex -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to check db2 installation on the machine in WIX
Hi Ranganatha, Thanks for example. Checking the DB2 installation on target machine is wokring now. Best Regards Adnan Ranganatha H C wrote: > > Hi, > > One way would be to add Registry serach and assign the registry serach > result to a property. Later you can use the property based on its value to > check whether DB2 installed on the target machine or not. > > e.g To check IIS is installed or not > > > > > > > > Id='IISCheck' > > Type='raw' > > Root='HKLM' > > Key='SYSTEM\CurrentControlSet\Services\W3SVC\Parameters' > > Name='MajorVersion' /> > > > > > > Installed OR (IIS6SPLEVEL >= "#6" AND NOT Installed) > > > Hope this helps... > > On Thu, Sep 10, 2009 at 4:51 AM, Blair wrote: > >> Searching IBM's web site I found a list of ProductCodes you could search >> for >> for DB2 v8.(whatever it was, I didn't save the link since that version is >> post-support) but for DB2 v9 I didn't find any such list. >> >> Your best bet is to query either IBM or DB2 users as to how to >> programmatically check db2 installations (hopefully there is a way >> without >> running any exe). Once you know that, we can help you with the syntax >> needed >> to implement it in WiX. >> >> -Original Message- >> From: danimian [mailto:miand...@gmail.com] >> Sent: Wednesday, September 09, 2009 3:12 PM >> To: wix-users@lists.sourceforge.net >> Subject: [WiX-users] How to check db2 installation on the machine in WIX >> >> >> Hi, >> I am using WIX to create MSI package for installation. Checking the >> Operating System and .NETFRAMEWORK 3.5 is working properly. >> I want to check whether DB2 is installed on the machine or not. >> How it is possible? I am using Visual Studio 8. >> Please help me in this regard. >> Thanks in advance >> Adnan >> -- >> View this message in context: >> >> http://n2.nabble.com/How-to-check-db2-installation-on-the-machine-in-WIX-tp3 >> 614998p3614998.html >> Sent from the wix-users mailing list archive at Nabble.com. >> >> >> >> -- >> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 >> 30-Day >> trial. Simplify your report design, integration and deployment - and >> focus >> on >> what you do best, core application coding. Discover what's new with >> Crystal Reports now. http://p.sf.net/sfu/bobj-july >> ___ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> >> >> >> -- >> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 >> 30-Day >> trial. Simplify your report design, integration and deployment - and >> focus >> on >> what you do best, core application coding. Discover what's new with >> Crystal Reports now. http://p.sf.net/sfu/bobj-july >> ___ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> > > > > -- > Regards/Ranga > -- > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 > 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- View this message in context: http://n2.nabble.com/How-to-check-db2-installation-on-the-machine-in-WIX-tp3614998p3655149.html Sent from the wix-users mailing list archive at Nabble.com. -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] launching page localization
Actually, I've found that the language of this initial dialog depends on the languages that your MSI publishes in its summary information stream. In WiX, this corresponds to the value of the "Languages" attribute of the "Package" element. For example, if the value of this attribute is "1033" then the text will always display in English, even on non-English systems. If you want the text to display in the system language, you can set the value of the attribute to "0" (language neutral). Mike -Original Message- From: DE?K JAHN, G?bor [mailto:d...@tramontana.co.hu] Sent: 15 September 2009 21:22 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] launching page localization On Tue, 15 Sep 2009 19:59:35 +, Lian Jiang wrote: Lian, You probably mean the very first small message about the installation launching. This is displayed by the Windows Installer, not your installer. So, no matter how fully you have localized yours, this message will display in the actual Windows system language your installer is running on. Bye, Gábor --- DEÃK JAHN, Gábor -- Budapest, Hungary E-mail: d...@tramontana.co.hu -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditional installed based on REG_MULTI_SZ value
Windows Installer doesn't support running multiple installations concurrently as it's a transaction based system. Not sure how burn works as I've not upgraded to WiX v3.5 yet but dotnetinstaller (http://dotnetinstaller.codeplex.com/) is a pretty easily configurable bootstrapper for this type of thing. Other bootstrappers are available & other people on the list may have other recommendations. You should be setting the InstallerVersion attribute on your Product Element to the *minimum* version of Windows Installer your package requires to install successfully. I use 301 (aka Windows Installer 3.1) since as of SP3 for XP it's the latest version supported by all the operating systems we support (2k3 & XP64/2k364 have 3.1 as of their SP2). You can use as low as 200 but even 300 is supported by XP SP2 & Windows 2000 SP4 AFAIK. See also the VersionMSI Property http://msdn.microsoft.com/en-us/library/aa372493.aspx if you really want to use a bootstrapper & LaunchConditions. To be quite honest, if you don't need any of the new features in Windows Installer 4.5 I don't see why you (and more importantly your users/customers) wouldn't be better off authoring your MSI for 3.1. If only Windows Updates pushed out the Windows Installer 4.5 redistributable to XP & above as it did 3.1 I wouldn't even have to bring this up. Palbinder Sandher Software Deployment & IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the ** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Dominique Louis [mailto:dominique.lo...@amxeurope.com] Sent: 16 September 2009 09:46 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Conditional installed based on REG_MULTI_SZ value I had never really thought about bootstrapping WI v4.5 with Installer. Does WiX 3.0 support Windows Installer 4.5 Or alternatively how can I check if v4.5 is installed so I can throw up an conditional message. Dominique. -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: 15 September 2009 16:03 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Conditional installed based on REG_MULTI_SZ value In that case are you bootstrapping the Windows Installer 4.5 redistributable before your installer runs so all your users/customers will be able to successfully install your product or are you also testing it on 3.1 & 4.0 to make sure they don't have problems? According to the docs (http://wix.sourceforge.net/manual-wix3/read_a_registry_entry.htm) before LaunchConditions should be fine but I would double check a verbose log just to make sure your RegistrySearch is populating the SQLSERVER Property before your CustomAction attempts to parse it. Palbinder Sandher Software Deployment & IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the ** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Dominique Louis [mailto:dominique.lo...@amxeurope.com] Sent: 15 September 2009 14:53 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Conditional installed based on REG_MULTI_SZ value I'm using v4.5.6001.22159 if that is any help to anyone. Is putting my CustomAction before LaunchConditions the best place to run my vbs, or would there be another more appropriate place? Dominique. -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: 15 September 2009 10:23 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Conditional installed based on REG_MULTI_SZ value No but you could attribute it to a bug in whichever version of Windows Installer you're using to test the MSI (v3.1 or v4.0 whether you're on XP/2k3 or Vista/2k8 respectively I'm guessing). People on this list really need to learn the difference between WiX & Windows Installer. They are *not* the same thing & should never be used interchangeably as if far too often the case. You'll have to write your own Custom Action to parse the registry value before you compare it as far as I know. Would be nice if there was some sort of Standard Custom Action in WiX for manipulating regex but then there's already plenty of features which existed in WiX v2.0 which we have to live without in WiX v3.0 so I wouldn't hold my breath. Palbinder Sandher Software Deployment & IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the ** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 R
[WiX-users] launching page localization
On Wed, 16 Sep 2009 10:07:55 +0100, Michael Bednarek wrote: Mike, > value of this attribute is "1033" then the text will always display > in English, even on non-English systems. If you want the text to > display in the system language, you can set the value of the > attribute to "0" (language neutral). Interesting. If others could confirm that this is so across various Windows versions and Windows Installer versions, I'd add it to the tutorial. I only have English opsystems so I can't try this one myself... Bye, Gábor --- DEÃK JAHN, Gábor -- Budapest, Hungary E-mail: d...@tramontana.co.hu -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] How to Build / Check a localhost connection with db2 odbc
Hi, i have written the following code in wix to build a localhost db2 odbc driver connection. .msi is running without any problem. First question is about the written code, is it right to build the connection? or missing something? Second question how can i check whether the connection was successfull or not? here is code: Please explain, I am new to wix. Best Regards Adnan -- View this message in context: http://n2.nabble.com/How-to-Build-Check-a-localhost-connection-with-db2-odbc-tp3655921p3655921.html Sent from the wix-users mailing list archive at Nabble.com. -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditional installed based on REG_MULTI_SZ value
They did push MSI 4.5 in Vista SP2, and Win7 has MSI 5, which includes everything in 4.5. But there are not any planned future service packs for XP that I know of... -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Wednesday, September 16, 2009 2:51 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Conditional installed based on REG_MULTI_SZ value Windows Installer doesn't support running multiple installations concurrently as it's a transaction based system. Not sure how burn works as I've not upgraded to WiX v3.5 yet but dotnetinstaller (http://dotnetinstaller.codeplex.com/) is a pretty easily configurable bootstrapper for this type of thing. Other bootstrappers are available & other people on the list may have other recommendations. You should be setting the InstallerVersion attribute on your Product Element to the *minimum* version of Windows Installer your package requires to install successfully. I use 301 (aka Windows Installer 3.1) since as of SP3 for XP it's the latest version supported by all the operating systems we support (2k3 & XP64/2k364 have 3.1 as of their SP2). You can use as low as 200 but even 300 is supported by XP SP2 & Windows 2000 SP4 AFAIK. See also the VersionMSI Property http://msdn.microsoft.com/en-us/library/aa372493.aspx if you really want to use a bootstrapper & LaunchConditions. To be quite honest, if you don't need any of the new features in Windows Installer 4.5 I don't see why you (and more importantly your users/customers) wouldn't be better off authoring your MSI for 3.1. If only Windows Updates pushed out the Windows Installer 4.5 redistributable to XP & above as it did 3.1 I wouldn't even have to bring this up. Palbinder Sandher Software Deployment & IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the ** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Dominique Louis [mailto:dominique.lo...@amxeurope.com] Sent: 16 September 2009 09:46 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Conditional installed based on REG_MULTI_SZ value I had never really thought about bootstrapping WI v4.5 with Installer. Does WiX 3.0 support Windows Installer 4.5 Or alternatively how can I check if v4.5 is installed so I can throw up an conditional message. Dominique. -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: 15 September 2009 16:03 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Conditional installed based on REG_MULTI_SZ value In that case are you bootstrapping the Windows Installer 4.5 redistributable before your installer runs so all your users/customers will be able to successfully install your product or are you also testing it on 3.1 & 4.0 to make sure they don't have problems? According to the docs (http://wix.sourceforge.net/manual-wix3/read_a_registry_entry.htm) before LaunchConditions should be fine but I would double check a verbose log just to make sure your RegistrySearch is populating the SQLSERVER Property before your CustomAction attempts to parse it. Palbinder Sandher Software Deployment & IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the ** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Dominique Louis [mailto:dominique.lo...@amxeurope.com] Sent: 15 September 2009 14:53 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Conditional installed based on REG_MULTI_SZ value I'm using v4.5.6001.22159 if that is any help to anyone. Is putting my CustomAction before LaunchConditions the best place to run my vbs, or would there be another more appropriate place? Dominique. -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: 15 September 2009 10:23 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Conditional installed based on REG_MULTI_SZ value No but you could attribute it to a bug in whichever version of Windows Installer you're using to test the MSI (v3.1 or v4.0 whether you're on XP/2k3 or Vista/2k8 respectively I'm guessing). People on this list really need to learn the difference between WiX & Windows Installer. They are *not* the same thing & should never be used interchangeably as if far too often the case. You'll have to write your own Custom Action to parse the registry value before you compare it as far as I know. Would be nice if there was some sort of Standard Custom Actio
Re: [WiX-users] launching page localization
This is the blog entry I was referring to last night: http://blogs.msdn.com/heaths/archive/2006/10/25/how-windows-installer-uses-l anguages.aspx. You will notice he refers to two places where language is identified in the MSI files, and where each of those two settings takes effect. -Original Message- From: DEÃK JAHN, Gábor [mailto:d...@tramontana.co.hu] Sent: Wednesday, September 16, 2009 5:45 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] launching page localization On Wed, 16 Sep 2009 10:07:55 +0100, Michael Bednarek wrote: Mike, > value of this attribute is "1033" then the text will always display > in English, even on non-English systems. If you want the text to > display in the system language, you can set the value of the > attribute to "0" (language neutral). Interesting. If others could confirm that this is so across various Windows versions and Windows Installer versions, I'd add it to the tutorial. I only have English opsystems so I can't try this one myself... Bye, Gábor --- DEÃK JAHN, Gábor -- Budapest, Hungary E-mail: d...@tramontana.co.hu -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] launching page localization
Hi Gábor, Our product's installer originally suffered from the same problem as Lian - that the dialog text displayed in English on all systems. While researching the problem, I stumbled across the blog post that Blair mentions below, and that's what lead me to experiment with the summary information stream. We now use "0" in our product installer and have tested this successfully on English, Spanish, French, German and Japanese, on Windows 2003 and Windows 2008. We did get one report of the "Cancel" button on the dialog still being displayed in English on a Japanese system, even though the rest of the text in the dialog was Japanese. I haven't bothered to investigate that one yet... Hope this helps, Mike -Original Message- From: Blair [mailto:os...@live.com] Sent: 16 September 2009 16:18 To: d...@tramontana.co.hu; 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] launching page localization This is the blog entry I was referring to last night: http://blogs.msdn.com/heaths/archive/2006/10/25/how-windows-installer-uses-l anguages.aspx. You will notice he refers to two places where language is identified in the MSI files, and where each of those two settings takes effect. -Original Message- From: DEÃK JAHN, Gábor [mailto:d...@tramontana.co.hu] Sent: Wednesday, September 16, 2009 5:45 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] launching page localization On Wed, 16 Sep 2009 10:07:55 +0100, Michael Bednarek wrote: Mike, > value of this attribute is "1033" then the text will always display > in English, even on non-English systems. If you want the text to > display in the system language, you can set the value of the > attribute to "0" (language neutral). Interesting. If others could confirm that this is so across various Windows versions and Windows Installer versions, I'd add it to the tutorial. I only have English opsystems so I can't try this one myself... Bye, Gábor --- DEÃK JAHN, Gábor -- Budapest, Hungary E-mail: d...@tramontana.co.hu -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] (no subject)
Pally, I, like Alex, have seen the same thing and recently too. As I recall, I waited several minutes for an installer to "think" before I got bored and cancelled it. I just put it down to Windows being "awkward" as when I restarted the installer, the thinking time was either non-existent or just a couple of seconds and everything then went fine. Unfortunately at the time, I didn't think to note it as a problem as it eventually installed correctly. I am not even sure what it was I was installing! Chris -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Wednesday, September 16, 2009 05:18 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] (no subject) That means Windows Installer is "thinking". We get it with patches when you click on the Next button on WelcomeDlg as at that point the Windows Installer is inventorying the product's currently installed components & keypaths etc. Not sure what would cause it with an MSI, possibly a large number of things like RegistrySearch, FileSearch or if you're using the major upgrade functionality and you currently have an older product installed which has a large number of files/components/etc. Nothing to be worried about, just Windows Installer doing it's job properly & you should just click the return button rather than cancelling & restarting as it'll likely be no faster. Palbinder Sandher Software Deployment & IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the ** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Alex Ivanoff [mailto:alex.ivan...@shavlik.com] Sent: 15 September 2009 17:04 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] (no subject) >From time to time I am getting the following dialog during install that never disappears and prevents installation from continuing: Please wait while installer finishes determining your disk space requirements. If I cancel the install and then restart it again most likely it will work. What may be going on? Alex -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] launching page localization
Some practical considerations: Both the Module and the Product elements contain a required @Language attribute. If the Package element's @Language attribute is missing, the parent's Language value will be used instead. Since Heath suggests always making sure both language values are the same, to prevent inconsistent values (once the package is opened), that would suggest that you place the language you built the package with in the Product/Module's @Language and that you don't supply the Package's @Language attribute (unless building a merge module and you truly support more than one language with that one MSM, a rarity). Unless you really donÂt have any text in your installer (also a rarity) you will usually want a specific language that matches your .wxl file as your language (otherwise the system-supplied text will be in the system's language and your text will be in whatever you used, such as English). You can use any localized string or any binder variable (e.g. "!(loc.LCID)" or "!(bind.fileLanguage.File1)") where you supply the correct value (for the loc var, make sure that the 1033 is translated in each .wxl it appears). You will need to supply this, since the WiX-provided translations in the UI extension don't include this string. It is always assumed that the user understands the language of the system they are running AND the language of the MSIs that they run. It is up to you to enforce the latter via the way you provide the packages, and to assume the former. -Original Message- From: Michael Bednarek [mailto:michael.bedna...@eu.citrix.com] Sent: Wednesday, September 16, 2009 8:24 AM To: General discussion for Windows Installer XML toolset.; d...@tramontana.co.hu Subject: Re: [WiX-users] launching page localization Hi Gábor, Our product's installer originally suffered from the same problem as Lian - that the dialog text displayed in English on all systems. While researching the problem, I stumbled across the blog post that Blair mentions below, and that's what lead me to experiment with the summary information stream. We now use "0" in our product installer and have tested this successfully on English, Spanish, French, German and Japanese, on Windows 2003 and Windows 2008. We did get one report of the "Cancel" button on the dialog still being displayed in English on a Japanese system, even though the rest of the text in the dialog was Japanese. I haven't bothered to investigate that one yet... Hope this helps, Mike -Original Message- From: Blair [mailto:os...@live.com] Sent: 16 September 2009 16:18 To: d...@tramontana.co.hu; 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] launching page localization This is the blog entry I was referring to last night: http://blogs.msdn.com/heaths/archive/2006/10/25/how-windows-installer-uses-l anguages.aspx. You will notice he refers to two places where language is identified in the MSI files, and where each of those two settings takes effect. -Original Message- From: DEÃK JAHN, Gábor [mailto:d...@tramontana.co.hu] Sent: Wednesday, September 16, 2009 5:45 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] launching page localization On Wed, 16 Sep 2009 10:07:55 +0100, Michael Bednarek wrote: Mike, > value of this attribute is "1033" then the text will always display > in English, even on non-English systems. If you want the text to > display in the system language, you can set the value of the > attribute to "0" (language neutral). Interesting. If others could confirm that this is so across various Windows versions and Windows Installer versions, I'd add it to the tutorial. I only have English opsystems so I can't try this one myself... Bye, Gábor --- DEÃK JAHN, Gábor -- Budapest, Hungary E-mail: d...@tramontana.co.hu -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/
Re: [WiX-users] (no subject)
Chris gave it several minutes, I let it sit overnight. So there is a problem. -Original Message- From: Chris Lord [mailto:chris.l...@atterotech.com] Sent: Wednesday, September 16, 2009 10:46 To: wix-users Subject: Re: [WiX-users] (no subject) Pally, I, like Alex, have seen the same thing and recently too. As I recall, I waited several minutes for an installer to "think" before I got bored and cancelled it. I just put it down to Windows being "awkward" as when I restarted the installer, the thinking time was either non-existent or just a couple of seconds and everything then went fine. Unfortunately at the time, I didn't think to note it as a problem as it eventually installed correctly. I am not even sure what it was I was installing! Chris -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Wednesday, September 16, 2009 05:18 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] (no subject) That means Windows Installer is "thinking". We get it with patches when you click on the Next button on WelcomeDlg as at that point the Windows Installer is inventorying the product's currently installed components & keypaths etc. Not sure what would cause it with an MSI, possibly a large number of things like RegistrySearch, FileSearch or if you're using the major upgrade functionality and you currently have an older product installed which has a large number of files/components/etc. Nothing to be worried about, just Windows Installer doing it's job properly & you should just click the return button rather than cancelling & restarting as it'll likely be no faster. Palbinder Sandher Software Deployment & IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the ** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Alex Ivanoff [mailto:alex.ivan...@shavlik.com] Sent: 15 September 2009 17:04 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] (no subject) >From time to time I am getting the following dialog during install that never disappears and prevents installation from continuing: Please wait while installer finishes determining your disk space requirements. If I cancel the install and then restart it again most likely it will work. What may be going on? Alex -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] (no subject)
This is off-the-cuff, but is it possibly related to generating the "System Restore Point"? I have seen that take a "long" time before. Did either Alex or Chris happen to obtain a log? -Original Message- From: Alex Ivanoff [mailto:alex.ivan...@shavlik.com] Sent: Wednesday, September 16, 2009 9:12 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] (no subject) Chris gave it several minutes, I let it sit overnight. So there is a problem. -Original Message- From: Chris Lord [mailto:chris.l...@atterotech.com] Sent: Wednesday, September 16, 2009 10:46 To: wix-users Subject: Re: [WiX-users] (no subject) Pally, I, like Alex, have seen the same thing and recently too. As I recall, I waited several minutes for an installer to "think" before I got bored and cancelled it. I just put it down to Windows being "awkward" as when I restarted the installer, the thinking time was either non-existent or just a couple of seconds and everything then went fine. Unfortunately at the time, I didn't think to note it as a problem as it eventually installed correctly. I am not even sure what it was I was installing! Chris -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Wednesday, September 16, 2009 05:18 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] (no subject) That means Windows Installer is "thinking". We get it with patches when you click on the Next button on WelcomeDlg as at that point the Windows Installer is inventorying the product's currently installed components & keypaths etc. Not sure what would cause it with an MSI, possibly a large number of things like RegistrySearch, FileSearch or if you're using the major upgrade functionality and you currently have an older product installed which has a large number of files/components/etc. Nothing to be worried about, just Windows Installer doing it's job properly & you should just click the return button rather than cancelling & restarting as it'll likely be no faster. Palbinder Sandher Software Deployment & IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the ** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Alex Ivanoff [mailto:alex.ivan...@shavlik.com] Sent: 15 September 2009 17:04 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] (no subject) >From time to time I am getting the following dialog during install that never disappears and prevents installation from continuing: Please wait while installer finishes determining your disk space requirements. If I cancel the install and then restart it again most likely it will work. What may be going on? Alex -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November
[WiX-users] Creating or Updating an Xml Element
I want to update my machine.config to create the element in system.web if and only if it does not already exist. Then I want to update the retail attribute to be set to "true" no matter whether or not the element existed before the install began. Here is my WiX snippet: The problem is that it creates another element every time the install begins. How can I fix this issue? I also tried adding a delete at the beginning of this component. Even if this worked it would not be ideal because it would eliminate any other attributes of the element that may already have been set. Here is my snippet with the delete: In this case, the delete seems to be ignored and I get the same result: multiple elements in my machine config. Any ideas? Thanks. - Phil -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] (no subject)
Blair, I didnt get one. If I see it happen again, I most surely will. As I said previously, I am not sure what it was I was installing or for that matter what OS (though the choice is either XP or Vista). Its also entirely possible the application I was installing was not my own WiX-generated installer but another piece of software entirelyI wish I'd paid more attention now when it happened! It certainly seems to be one of those frustratingly difficult to track down, only happens once in a while things. Chris -Original Message- From: Blair [mailto:os...@live.com] Sent: Wednesday, September 16, 2009 12:24 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] (no subject) This is off-the-cuff, but is it possibly related to generating the "System Restore Point"? I have seen that take a "long" time before. Did either Alex or Chris happen to obtain a log? -Original Message- From: Alex Ivanoff [mailto:alex.ivan...@shavlik.com] Sent: Wednesday, September 16, 2009 9:12 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] (no subject) Chris gave it several minutes, I let it sit overnight. So there is a problem. -Original Message- From: Chris Lord [mailto:chris.l...@atterotech.com] Sent: Wednesday, September 16, 2009 10:46 To: wix-users Subject: Re: [WiX-users] (no subject) Pally, I, like Alex, have seen the same thing and recently too. As I recall, I waited several minutes for an installer to "think" before I got bored and cancelled it. I just put it down to Windows being "awkward" as when I restarted the installer, the thinking time was either non-existent or just a couple of seconds and everything then went fine. Unfortunately at the time, I didn't think to note it as a problem as it eventually installed correctly. I am not even sure what it was I was installing! Chris -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Wednesday, September 16, 2009 05:18 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] (no subject) That means Windows Installer is "thinking". We get it with patches when you click on the Next button on WelcomeDlg as at that point the Windows Installer is inventorying the product's currently installed components & keypaths etc. Not sure what would cause it with an MSI, possibly a large number of things like RegistrySearch, FileSearch or if you're using the major upgrade functionality and you currently have an older product installed which has a large number of files/components/etc. Nothing to be worried about, just Windows Installer doing it's job properly & you should just click the return button rather than cancelling & restarting as it'll likely be no faster. Palbinder Sandher Software Deployment & IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the ** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Alex Ivanoff [mailto:alex.ivan...@shavlik.com] Sent: 15 September 2009 17:04 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] (no subject) >From time to time I am getting the following dialog during install that never disappears and prevents installation from continuing: Please wait while installer finishes determining your disk space requirements. If I cancel the install and then restart it again most likely it will work. What may be going on? Alex -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Come build with us! The BlackBerry® Developer Conference in SF, CA
Re: [WiX-users] (no subject)
I've seen some comments suggesting that file costing gets slower when the current TARGETDIR is populated, and if that's the case it presumably makes the costing calculations more complex The same might be true if other target folders are populated (and that's more speculation). Nevertheless, taking all night seems excessive. Installs often set the default TARGETDIR before costing, but I doubt that's a requirement because the user can change it later in a UI based install. It might be worth experimenting to see if it makes any difference to leave it unset until after costing when TARGETDIR already contains many files. Phil Wilson -Original Message- From: Chris Lord [mailto:chris.l...@atterotech.com] Sent: Wednesday, September 16, 2009 11:36 AM To: wix-users Subject: Re: [WiX-users] (no subject) Blair, I didnt get one. If I see it happen again, I most surely will. As I said previously, I am not sure what it was I was installing or for that matter what OS (though the choice is either XP or Vista). Its also entirely possible the application I was installing was not my own WiX-generated installer but another piece of software entirelyI wish I'd paid more attention now when it happened! It certainly seems to be one of those frustratingly difficult to track down, only happens once in a while things. Chris -Original Message- From: Blair [mailto:os...@live.com] Sent: Wednesday, September 16, 2009 12:24 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] (no subject) This is off-the-cuff, but is it possibly related to generating the "System Restore Point"? I have seen that take a "long" time before. Did either Alex or Chris happen to obtain a log? -Original Message- From: Alex Ivanoff [mailto:alex.ivan...@shavlik.com] Sent: Wednesday, September 16, 2009 9:12 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] (no subject) Chris gave it several minutes, I let it sit overnight. So there is a problem. -Original Message- From: Chris Lord [mailto:chris.l...@atterotech.com] Sent: Wednesday, September 16, 2009 10:46 To: wix-users Subject: Re: [WiX-users] (no subject) Pally, I, like Alex, have seen the same thing and recently too. As I recall, I waited several minutes for an installer to "think" before I got bored and cancelled it. I just put it down to Windows being "awkward" as when I restarted the installer, the thinking time was either non-existent or just a couple of seconds and everything then went fine. Unfortunately at the time, I didn't think to note it as a problem as it eventually installed correctly. I am not even sure what it was I was installing! Chris -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Wednesday, September 16, 2009 05:18 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] (no subject) That means Windows Installer is "thinking". We get it with patches when you click on the Next button on WelcomeDlg as at that point the Windows Installer is inventorying the product's currently installed components & keypaths etc. Not sure what would cause it with an MSI, possibly a large number of things like RegistrySearch, FileSearch or if you're using the major upgrade functionality and you currently have an older product installed which has a large number of files/components/etc. Nothing to be worried about, just Windows Installer doing it's job properly & you should just click the return button rather than cancelling & restarting as it'll likely be no faster. Palbinder Sandher Software Deployment & IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the ** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Alex Ivanoff [mailto:alex.ivan...@shavlik.com] Sent: 15 September 2009 17:04 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] (no subject) >From time to time I am getting the following dialog during install that never disappears and prevents installation from continuing: Please wait while installer finishes determining your disk space requirements. If I cancel the install and then restart it again most likely it will work. What may be going on? Alex -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___
[WiX-users] Localized strings not in Wix Extensions
I'll preface this by saying that I'm not very experienced using Wix so I may be doing something wrong. I'm attempting to use the FirewallExtension. When I build in English it succeeds. However, when I build using other languages it fails. I get the following error: C:\delivery\Dev\wix30_public\src\ext\FirewallExtension\wixlib\FirewallExtension.wxs(19) : error LGHT0102 : The localization variable !(loc.WixSchedFirewallExceptionsInstall) is unknown. Please ensure the variable is defined. After a little bit of digging around I found that the string WixSchedFirewallExceptionsInstall and about 5 or 6 others are only defined in English. So, when my build attempts to build other languages the strings are not defined and it fails. To work around this I've added the English strings to all my localized files so the string ID is defined for each language. I don't particularly like that so I figured I'd ask if there are any plans on getting strings in the Wix Extensions localized. I noticed that other extensions also only have English strings defined, so this doesn't just apply to the FirewallExtension. I would assume there are plans to localize these strings since they are set up to be, but the way it is right now makes the extension unusable without doing what I did for projects that build in languages other than English. Unless, of course, I'm doing something wrong and it's possible to not include/use the UI and strings defined for the extension, but I don't think there is. Chris -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Localized strings not in Wix Extensions
Quick stroll through the RTM source dump reveals the following: 7 extensions have localized strings: ComPlus Firewall IIS MSMQ SQL UI Util 5 of those extensions have only en-US strings included: ComPlus Firewall IIS MSMQ SQL Util also has de-DE (but only those two languages), and UI has a total of 12 languages, including en-US and de-DE. Gábor's localization project only extends the localization for the UI extension (including the action and error tables) but does not include any strings from the other 6 extensions. (It is not his fault, he was looking at just the UI extension, which is the only one really called out in wix.chm and the only one with more than two languages localized in the RTM). Those are 143 strings that are NOT in the UI extension (a lot less than the approx 400-500 strings that ARE in the UI extension) but still a fair number. Supplemental .WXL files added to light's (and lit's) commandline can contain strings not used in the extensions that are actually used without adding any bloat to the final product (since strings not referenced are ignored and never incorporated) so if we could get 143 strings localized into 11 languages + whatever additional languages Gábor has outside of the 12 that currently ship would be a great boon to the community. While I am fluent in Spanish I am not a native speaker, and I would prefer a native speaker in localization activities for the target languages (the translation quality tends to be much higher), but if Gábor (or anyone else) is willing to manage an additional set of strings (12 of them already have a translation into German) I'm willing to send the "initial" set of language files with English placeholders to get the process started. The latest source dump of 3.5 has the same number of WXL files, so I assume that it doesn't have any additional languages translated at this point (although there are a small number of additional strings). -Blair -Original Message- From: Capaci, Chris [mailto:christopher.cap...@hp.com] Sent: Wednesday, September 16, 2009 12:08 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Localized strings not in Wix Extensions I'll preface this by saying that I'm not very experienced using Wix so I may be doing something wrong. I'm attempting to use the FirewallExtension. When I build in English it succeeds. However, when I build using other languages it fails. I get the following error: C:\delivery\Dev\wix30_public\src\ext\FirewallExtension\wixlib\FirewallExtens ion.wxs(19) : error LGHT0102 : The localization variable !(loc.WixSchedFirewallExceptionsInstall) is unknown. Please ensure the variable is defined. After a little bit of digging around I found that the string WixSchedFirewallExceptionsInstall and about 5 or 6 others are only defined in English. So, when my build attempts to build other languages the strings are not defined and it fails. To work around this I've added the English strings to all my localized files so the string ID is defined for each language. I don't particularly like that so I figured I'd ask if there are any plans on getting strings in the Wix Extensions localized. I noticed that other extensions also only have English strings defined, so this doesn't just apply to the FirewallExtension. I would assume there are plans to localize these strings since they are set up to be, but the way it is right now makes the extension unusable without doing what I did for projects that build in languages other than English. Unless, of course, I'm doing something wrong and it's possible to not include/use the UI and strings defined for the extension, but I don't think there is. Chris -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Migrating from Wix v1 to Wix v3
Hi, Have you migrated from Wix v1 to Wix v3? What are the risks? What are the areas to focus? Is there any tool to migrate Wix v1 to Wix v3? Will WixCop help in anyway? Could you please give me a general idea? Thanks, Walaja -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
