Re: [WiX-users] The cancel installation string
Hello Brian, The CancelDlgText is used on the CancelDlg. When removing the product using the Maintenance Mode it will show the CancelDlg as you described. This is probably also the reason why the ActionText on the progress dialog for most installations is just "The installer is performing the requested actions". :-) If the users removes the product using Control panel, no Cancel dialog/confirmation is shown. A trick to change the text could be using a property instead of the word "installation". E.g "Are you sure you want to cancel [ProductName] [INSTALLERACTION]". Define the INSTALLERACTION property with "installation" as default value. Then add a SetProperty custom action to set the INSTALLERACTION property to "uninstallation" if the "REMOVE" property is set (= uninstalling). Additionally you may set it to "reinstallation" if REINSTALL is set. Best regards, Sebastian Brand sebast...@instyler.com Geisenfelder Str. 53a 85053 Ingolstadt, Germany EU VAT ID: DE219712370 Phone: +49 841 4544567 www.instyler.com - Instyler Setup: Create WiX-based MSI installations, elegantly. www.traveladdin.com - Travel Add-in for Outlook: Add travel and return times to your calendar. www.sebastianbrand.com - blogging about software development, deployment and productivity. > -Original Message- > From: little.forest [mailto:little.for...@ymail.com] > Sent: Tuesday, January 12, 2010 23:04 > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] The cancel installation string > > Our QA complains this: > > Reinstall the same build, then choose the "Remove". During "Remove", hit > the "Cancel" button. The dialog box shows "Are you sure you want to cancel > ProductX installation?" which our QA think it should be some like "Are you > sure you want to cancel ProductX removing?". Is there a way to satisfy our > QA? > > I searched the language file and found: > Are you sure you want to cancel [ProductName] > installation? > > > I doubt if we could change it as I thought the string CancelDlgText is used > everywhere? Any ideas? > > Many thanks! > /Brian > > > > > __ > > Be smarter than spam. See how smart SpamGuard is at giving junk email the > boot with the All-new Yahoo! Mail. Click on Options in Mail and switch to > New Mail today or register for free at http://mail.yahoo.ca > -- > This SF.Net email is sponsored by the Verizon Developer Community Take > advantage of Verizon's best-in-class app development support A > streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] vc80 and vc71 merge modules
Hi Igor , Have u found a work around for this.. As i wish to do the same i.e re distribute msvcr71.dll and msvcr80.dll using merge modules. Could u give me the link to download the correct version of these msm's? Igor Likhotkin wrote: > > > Hello! > > Has anyone tried to distribute VC80 and VC71 DLLs with merge modules? I > got a bunch of warnings when I added VC80 merge module to my project, but > the project built successfully and everything was installed. Some of my > DLLs did not get registered because I was not distributing VC71. I added > VC71 merge modules to my project, and it stopped building: > > Warning 1 The InstallExecuteSequence table contains an action > 'SxsInstallCA' which cannot be merged from the merge module 'C:\Program > Files\Common Files\Merge Modules\Microsoft_VC80_CRT_x86.msm'. This action > is likely colliding with an action in the database that is being created. > The colliding action may have been authored in the database or merged in > from another merge module. If this is a standard action, it is likely > colliding due to a difference in the condition for the action in the > database and merge module. If this is a custom action, it should only be > declared in the database or one merge module. C:\Documents and > Settings\ilikhot\My Documents\Visual Studio > 2005\Projects\VDSPInstallation\VDSPInstallation\_merge_modules.wxi 4 1 > VDSPInstallation > Warning 9 ICE03: String overflow (greater than length permitted in > column); Table: Component, Column: KeyPath, Key(s): > downlevel_manifest.8.0.50727.762.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E > light.exe 0 1 VDSPInstallation > > Warning 69 ICE25: Possible dependency failure as we do not find > atl.policy.66332652_9c28_58b1_ff1f_c8b3b9a1e...@0 v in ModuleSignature > table light.exe 0 1 VDSPInstallation > Warning 146 ICE39: The File > 'ansi_atl80.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E' is explicitly marked > compressed, but the Summary Information Stream already specifies that the > whole install is compressed. This might not be the behavior you want. > light.exe 0 1 VDSPInstallation > Warning 281 ICE82: This action > SystemFolder.66332652_9C28_58B1_FF1F_C8B3B9A1E18E has duplicate sequence > number 5 in the table AdminExecuteSequence light.exe 0 1 VDSPInstallation > Warning 306 ICE83: The keypath for Global Win32 SXS Assembly > (Component_=uplevel.66332652_9C28_58B1_FF1F_C8B3B9A1E18E) SHOULD NOT be > it's manifest file for assemblies other than Win32 Policy assemblies > light.exe 0 1 VDSPInstallation > Error 141 ICE32: Possible Mis-Aligned Foreign Keys C:\Documents and > Settings\ilikhot\Local Settings\Temp\bae7v7y1\VDSPInstallation.msi 0 1 > VDSPInstallation > > What do I do? Do I have bad versions of these MSM files? Where can I get > proper MSMs for distributing VC80 and VC71? > > Please help. > > Thanks. > > -igor. > _ > Windows Live Hotmail is giving away Zunes. Enter for your chance to win. > http://www.windowslive-hotmail.com/ZuneADay/?locale=en-US&ocid=TXT_TAGLM_Mobile_Zune_V3 > - > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ > ___ > 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/vc80-and-vc71-merge-modules-tp709448p4323136.html Sent from the wix-users mailing list archive at Nabble.com. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Windows System Folder
What versions are the two files? This is a standard VB6 custom control, I must admit I have never heard of an update to this to support more comm ports, is it an official Microsoft release? The "correct" way to install MSCOMM32.OCX is via the Microsoft supplied merge module, mscomm32.msm, this installs v6.0.81.69 - which version are you installing? Neil -Original Message- From: Daniel Hughes [mailto:daniel.hug...@tait.co.nz] Sent: 12 January 2010 22:53 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Windows System Folder one of the files is MSCOMM32.OCX, this is for handling com ports. We have a customer who uses a different version of this that provides the ability to access more com ports. There version is new both in time stamp and in version. However our installer replaces it, pissing said customer off. Why?It is my understanding that Windows Installer only knows the two files are the same if the component GUID matches, ie having the same name is not enough. The customer in question did not install the file he copied it into the required location. Even if he did install it with as part of some other installer it would have been installed with a different GUID and so windows installer would not know it was the same thing and that it should apply its version rules. Is my understanding wrong? and if so please explain why our installer is replacing our customers (newer) assembly. Rob Mensching wrote: > Can you provide more information about these files that are getting > replaced? The Windows Installer its rules for File Version checks > (documented in the MSI SDK) and they are consistent. You'd have to use a > custom action to install files (a huge no-no) to install files differently. > > The whole design sounds very suspicious right now but more details may > better explain what is going on and provide suggestions. > > On Mon, Jan 11, 2010 at 5:06 PM, Daniel Hughes wrote: > > >> We are moving one of products from a old Install shield installer to a >> WiX installer. >> >> The old Installer installs a bunch of assemblies to the System32 folder. >> These assemblies are not produced by us but a required dependencies of >> our software. Install Shield has a replace if older type option so it >> checks the assemblies version and only installs if the existing assembly >> is older then the one being installed. >> >> When we moved to WiX there was no such option. Each assembly gets a >> component GUID and install shield just goes along and replaces any >> existing assemblies even if they are newer. This is causing problems as >> some of our customers are running software which relies on functionary >> only available in newer versions. >> >> I have heard that a way to get the correct component GUID so windows >> installer doesn't do bad things is to find official Merge Modules. These >> have proved to be hard to find and if the assembles have been copied or >> installed to Windows32 by some other method it will not work. >> >> How do I make sure I don't replace new versions of assemblies which we >> don't produce and don't control. >> >> Cheers, >> Daniel >> >> === >> This email, including any attachments, is only for the intended >> addressee. It is subject to copyright, is confidential and may be >> the subject of legal or other privilege, none of which is waived or >> lost by reason of this transmission. >> If the receiver is not the intended addressee, please accept our >> apologies, notify us by return, delete all copies and perform no >> other act on the email. >> Unfortunately, we cannot warrant that the email has not been >> altered or corrupted during transmission. >> === >> >> >> >> -- >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and >> easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> ___ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> >> >> > > > === This email, including any attachments, is only for the intended addressee. It is subject to copyright, is confidential and may be the subject of legal or other privilege, none of which is waived or lost by reason of this transmission. If the receiver is not the intended addressee, please accept our apologies, notify us by return, delete all copies and perform no other act on the email. Unfortunately, we cannot warrant that the email has not been altered or
[WiX-users] ServiceInstall query
Hi, I have updated the wix file (.wxs file) with current user id (Account) and password in section and am able to install the msi file with my login credentials few days back. But now as my login credentials are changed (i.e. password changed). So I updated the wix file accordingly i.e. changed the Password in section. With this change I am unable to install the msi. Error shown in Event Viewer was : "Logon failure: unknown user name or bad password." But actually the user name and password are correct. Is there any other issue which preventing me to install with new credentials? Thanks, Rama Krishna Duddu -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Windows System Folder
and something else to check is that InstallShield sometimes uses a thing called version lying. It's called "lying" because the File table in the MSI file gets a version of 65535.65535 etc so it always replaces any existing file on the system. If you managed to transfer something like this into your WiX build you will replace that file. You'd need to look at the file table in your MSI file to see what version of mscomm32.ocx is in there. Phil Wilson -Original Message- From: Blair [mailto:os...@live.com] Sent: Tuesday, January 12, 2010 3:34 PM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Windows System Folder >From a debug-verbose installation log, what is the value of the REINSTALLMODE property? -Original Message- From: Daniel Hughes [mailto:daniel.hug...@tait.co.nz] Sent: Tuesday, January 12, 2010 2:53 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Windows System Folder one of the files is MSCOMM32.OCX, this is for handling com ports. We have a customer who uses a different version of this that provides the ability to access more com ports. There version is new both in time stamp and in version. However our installer replaces it, pissing said customer off. Why?It is my understanding that Windows Installer only knows the two files are the same if the component GUID matches, ie having the same name is not enough. The customer in question did not install the file he copied it into the required location. Even if he did install it with as part of some other installer it would have been installed with a different GUID and so windows installer would not know it was the same thing and that it should apply its version rules. Is my understanding wrong? and if so please explain why our installer is replacing our customers (newer) assembly. Rob Mensching wrote: > Can you provide more information about these files that are getting > replaced? The Windows Installer its rules for File Version checks > (documented in the MSI SDK) and they are consistent. You'd have to use a > custom action to install files (a huge no-no) to install files differently. > > The whole design sounds very suspicious right now but more details may > better explain what is going on and provide suggestions. > > On Mon, Jan 11, 2010 at 5:06 PM, Daniel Hughes wrote: > > >> We are moving one of products from a old Install shield installer to a >> WiX installer. >> >> The old Installer installs a bunch of assemblies to the System32 folder. >> These assemblies are not produced by us but a required dependencies of >> our software. Install Shield has a replace if older type option so it >> checks the assemblies version and only installs if the existing assembly >> is older then the one being installed. >> >> When we moved to WiX there was no such option. Each assembly gets a >> component GUID and install shield just goes along and replaces any >> existing assemblies even if they are newer. This is causing problems as >> some of our customers are running software which relies on functionary >> only available in newer versions. >> >> I have heard that a way to get the correct component GUID so windows >> installer doesn't do bad things is to find official Merge Modules. These >> have proved to be hard to find and if the assembles have been copied or >> installed to Windows32 by some other method it will not work. >> >> How do I make sure I don't replace new versions of assemblies which we >> don't produce and don't control. >> >> Cheers, >> Daniel >> >> === >> This email, including any attachments, is only for the intended >> addressee. It is subject to copyright, is confidential and may be >> the subject of legal or other privilege, none of which is waived or >> lost by reason of this transmission. >> If the receiver is not the intended addressee, please accept our >> apologies, notify us by return, delete all copies and perform no >> other act on the email. >> Unfortunately, we cannot warrant that the email has not been >> altered or corrupted during transmission. >> === >> >> >> >> -- >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and >> easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> ___ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> >> >> > > > === This email, including any attachment
Re: [WiX-users] The cancel installation string
You could try copying the source to the CancelDlg, update it to select the text to show based on the REMOVE property. -Original Message- From: little.forest [mailto:little.for...@ymail.com] Sent: Tuesday, January 12, 2010 2:53 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] The cancel installation string By the way, I could change it to be "Are you sure you want to cancel?" to ignore the installation/remove operation. But if you have a better idea, please let me know. Thanks. From: little.forest To: wix-users@lists.sourceforge.net Sent: Tue, January 12, 2010 2:04:07 PM Subject: The cancel installation string Our QA complains this: Reinstall the same build, then choose the "Remove". During "Remove", hit the "Cancel" button. The dialog box shows "Are you sure you want to cancel ProductX installation?" which our QA think it should be some like "Are you sure you want to cancel ProductX removing?". Is there a way to satisfy our QA? I searched the language file and found: Are you sure you want to cancel [ProductName] installation? I doubt if we could change it as I thought the string CancelDlgText is used everywhere? Any ideas? Many thanks! /Brian Looking for the perfect gift?Give the gift of Flickr! __ The new Internet ExplorerR 8 - Faster, safer, easier. Optimized for Yahoo! Get it Now for Free! at http://downloads.yahoo.com/ca/internetexplorer/ -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Windows System Folder
>From a debug-verbose installation log, what is the value of the REINSTALLMODE property? -Original Message- From: Daniel Hughes [mailto:daniel.hug...@tait.co.nz] Sent: Tuesday, January 12, 2010 2:53 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Windows System Folder one of the files is MSCOMM32.OCX, this is for handling com ports. We have a customer who uses a different version of this that provides the ability to access more com ports. There version is new both in time stamp and in version. However our installer replaces it, pissing said customer off. Why?It is my understanding that Windows Installer only knows the two files are the same if the component GUID matches, ie having the same name is not enough. The customer in question did not install the file he copied it into the required location. Even if he did install it with as part of some other installer it would have been installed with a different GUID and so windows installer would not know it was the same thing and that it should apply its version rules. Is my understanding wrong? and if so please explain why our installer is replacing our customers (newer) assembly. Rob Mensching wrote: > Can you provide more information about these files that are getting > replaced? The Windows Installer its rules for File Version checks > (documented in the MSI SDK) and they are consistent. You'd have to use a > custom action to install files (a huge no-no) to install files differently. > > The whole design sounds very suspicious right now but more details may > better explain what is going on and provide suggestions. > > On Mon, Jan 11, 2010 at 5:06 PM, Daniel Hughes wrote: > > >> We are moving one of products from a old Install shield installer to a >> WiX installer. >> >> The old Installer installs a bunch of assemblies to the System32 folder. >> These assemblies are not produced by us but a required dependencies of >> our software. Install Shield has a replace if older type option so it >> checks the assemblies version and only installs if the existing assembly >> is older then the one being installed. >> >> When we moved to WiX there was no such option. Each assembly gets a >> component GUID and install shield just goes along and replaces any >> existing assemblies even if they are newer. This is causing problems as >> some of our customers are running software which relies on functionary >> only available in newer versions. >> >> I have heard that a way to get the correct component GUID so windows >> installer doesn't do bad things is to find official Merge Modules. These >> have proved to be hard to find and if the assembles have been copied or >> installed to Windows32 by some other method it will not work. >> >> How do I make sure I don't replace new versions of assemblies which we >> don't produce and don't control. >> >> Cheers, >> Daniel >> >> === >> This email, including any attachments, is only for the intended >> addressee. It is subject to copyright, is confidential and may be >> the subject of legal or other privilege, none of which is waived or >> lost by reason of this transmission. >> If the receiver is not the intended addressee, please accept our >> apologies, notify us by return, delete all copies and perform no >> other act on the email. >> Unfortunately, we cannot warrant that the email has not been >> altered or corrupted during transmission. >> === >> >> >> >> -- >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and >> easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> ___ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> >> >> > > > === This email, including any attachments, is only for the intended addressee. It is subject to copyright, is confidential and may be the subject of legal or other privilege, none of which is waived or lost by reason of this transmission. If the receiver is not the intended addressee, please accept our apologies, notify us by return, delete all copies and perform no other act on the email. Unfortunately, we cannot warrant that the email has not been altered or corrupted during transmission. === -- This SF.Net email is sponsored by the Verizon Developer Community Take a
Re: [WiX-users] The cancel installation string
By the way, I could change it to be "Are you sure you want to cancel?" to ignore the installation/remove operation. But if you have a better idea, please let me know. Thanks. From: little.forest To: wix-users@lists.sourceforge.net Sent: Tue, January 12, 2010 2:04:07 PM Subject: The cancel installation string Our QA complains this: Reinstall the same build, then choose the "Remove". During "Remove", hit the "Cancel" button. The dialog box shows "Are you sure you want to cancel ProductX installation?" which our QA think it should be some like "Are you sure you want to cancel ProductX removing?". Is there a way to satisfy our QA? I searched the language file and found: Are you sure you want to cancel [ProductName] installation? I doubt if we could change it as I thought the string CancelDlgText is used everywhere? Any ideas? Many thanks! /Brian Looking for the perfect gift?Give the gift of Flickr! __ The new Internet Explorer® 8 - Faster, safer, easier. Optimized for Yahoo! Get it Now for Free! at http://downloads.yahoo.com/ca/internetexplorer/ -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Windows System Folder
one of the files is MSCOMM32.OCX, this is for handling com ports. We have a customer who uses a different version of this that provides the ability to access more com ports. There version is new both in time stamp and in version. However our installer replaces it, pissing said customer off. Why?It is my understanding that Windows Installer only knows the two files are the same if the component GUID matches, ie having the same name is not enough. The customer in question did not install the file he copied it into the required location. Even if he did install it with as part of some other installer it would have been installed with a different GUID and so windows installer would not know it was the same thing and that it should apply its version rules. Is my understanding wrong? and if so please explain why our installer is replacing our customers (newer) assembly. Rob Mensching wrote: > Can you provide more information about these files that are getting > replaced? The Windows Installer its rules for File Version checks > (documented in the MSI SDK) and they are consistent. You'd have to use a > custom action to install files (a huge no-no) to install files differently. > > The whole design sounds very suspicious right now but more details may > better explain what is going on and provide suggestions. > > On Mon, Jan 11, 2010 at 5:06 PM, Daniel Hughes > wrote: > > >> We are moving one of products from a old Install shield installer to a >> WiX installer. >> >> The old Installer installs a bunch of assemblies to the System32 folder. >> These assemblies are not produced by us but a required dependencies of >> our software. Install Shield has a replace if older type option so it >> checks the assemblies version and only installs if the existing assembly >> is older then the one being installed. >> >> When we moved to WiX there was no such option. Each assembly gets a >> component GUID and install shield just goes along and replaces any >> existing assemblies even if they are newer. This is causing problems as >> some of our customers are running software which relies on functionary >> only available in newer versions. >> >> I have heard that a way to get the correct component GUID so windows >> installer doesn't do bad things is to find official Merge Modules. These >> have proved to be hard to find and if the assembles have been copied or >> installed to Windows32 by some other method it will not work. >> >> How do I make sure I don't replace new versions of assemblies which we >> don't produce and don't control. >> >> Cheers, >> Daniel >> >> === >> This email, including any attachments, is only for the intended >> addressee. It is subject to copyright, is confidential and may be >> the subject of legal or other privilege, none of which is waived or >> lost by reason of this transmission. >> If the receiver is not the intended addressee, please accept our >> apologies, notify us by return, delete all copies and perform no >> other act on the email. >> Unfortunately, we cannot warrant that the email has not been >> altered or corrupted during transmission. >> === >> >> >> >> -- >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and >> easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> ___ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> >> >> > > > === This email, including any attachments, is only for the intended addressee. It is subject to copyright, is confidential and may be the subject of legal or other privilege, none of which is waived or lost by reason of this transmission. If the receiver is not the intended addressee, please accept our apologies, notify us by return, delete all copies and perform no other act on the email. Unfortunately, we cannot warrant that the email has not been altered or corrupted during transmission. === -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-us
Re: [WiX-users] Making a Requirements Dialog
pmdarrow wrote: > > Hi all. I'd like to display a dialog after the feature customization > dialog that gives the user feedback if the requirements for installing > their selected features are fulfilled. For instance, if the user only > selected the database feature, SQL Server is the only requirement. But if > they select the ASP.NET app, IIS is a requirement as well. Is there any > easy way to write the dialog for this? The only thing I can think of doing > is writing a dialog for each combination of selected features (e.g. > OnlyDBDlg.wxs for just the DB, DB+IISDlg.wxs for DB and IIS, etc.) and > having a bunch of conditions on the next button of the customize dialog > for showing each of them. Any ideas? > I am doing a something similar. I'm using the SelectionTree control to let users select which features to install but have some feature-specific system requirements. I really wish you could disable features but still show them in the SelectionTree control, that would be my ideal solution but it is not possible. What I have settled on is using the new functionality to publish a DoAction event from the SelectionTree control. This is only available on Windows 2003 and newer, so Vista, Win7 and 2008 too. However, for the product I'm working on I only need to support newer OSes so I can use the new functionality. I wrote a custom action that updates a property that I use on a text control on the same dialog. Whenever a user selects a feature the text control gets updated with what the feature-specific requirements are for that feature. Then on the Next button I run a custom action that verifies everything and if they are trying to install a feature without all of its necessary prerequisites I throw up a dialog with an informative error and keep that on that dialog until their feature selections are valid to continue. The only catch I ran into was that using a DTF custom action on the SelectionTree control published DoAction was too slow. Because the DTF has to extract the native DLL, then extract the baked in .NET assembly and load it up just to call your code, it caused noticeable lag on the dialog whenever you selected a different feature or changed a feature's state. I ended up rewriting that custom action in C++ and it sped things up greatly. My Next button custom action is still in DTF as the slight delay does not stand out as much on the dialog transitions. Hope that helps, Mike -- View this message in context: http://n2.nabble.com/Making-a-Requirements-Dialog-tp4292721p4295065.html Sent from the wix-users mailing list archive at Nabble.com. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] The cancel installation string
Our QA complains this: Reinstall the same build, then choose the "Remove". During "Remove", hit the "Cancel" button. The dialog box shows "Are you sure you want to cancel ProductX installation?" which our QA think it should be some like "Are you sure you want to cancel ProductX removing?". Is there a way to satisfy our QA? I searched the language file and found: Are you sure you want to cancel [ProductName] installation? I doubt if we could change it as I thought the string CancelDlgText is used everywhere? Any ideas? Many thanks! /Brian __ Be smarter than spam. See how smart SpamGuard is at giving junk email the boot with the All-new Yahoo! Mail. Click on Options in Mail and switch to New Mail today or register for free at http://mail.yahoo.ca -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installation of msi with user credentials
Please search the forum history on Source Forge for an email titled: and question This might help you out a bit... Brian Rogers "Intelligence removes complexity." - Me http://blogs.msdn.com/icumove <-- NEW On Tue, Jan 12, 2010 at 10:31 AM, Rama Krishna Duddu (Infosys Technologies Ltd) wrote: > Hi > > I would like to install a msi file with my user credentials from command > line. Can you please help me with command and procedure to meet this > purpose. > > Thanks, > Rama Krishna Duddu > > > -- > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and > easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Installation of msi with user credentials
Hi I would like to install a msi file with my user credentials from command line. Can you please help me with command and procedure to meet this purpose. Thanks, Rama Krishna Duddu -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] How to set property Directory browsing for IIS virtual directory?
Hi All, I need to set property Directory browsing for IIS virtual directory. As I understand Wix doesn't support this property. Is there any solution for this? -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Making a Requirements Dialog
Hi all. I'd like to display a dialog after the feature customization dialog that gives the user feedback if the requirements for installing their selected features are fulfilled. For instance, if the user only selected the database feature, SQL Server is the only requirement. But if they select the ASP.NET app, IIS is a requirement as well. Is there any easy way to write the dialog for this? The only thing I can think of doing is writing a dialog for each combination of selected features (e.g. OnlyDBDlg.wxs for just the DB, DB+IISDlg.wxs for DB and IIS, etc.) and having a bunch of conditions on the next button of the customize dialog for showing each of them. Any ideas? -- View this message in context: http://n2.nabble.com/Making-a-Requirements-Dialog-tp4292721p4292721.html Sent from the wix-users mailing list archive at Nabble.com. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] short name of the default windows installer directory and the status of burn
Thanks for the clarification, I thought the shortname was always used. So in real life it's probably "WINDOW~1.5" on most machines ( try DIR /X ) But you can't be sure... Short file name generation might even be disabled. Best regards, Sebastian Brand sebast...@instyler.com Geisenfelder Str. 53a 85053 Ingolstadt, Germany EU VAT ID: DE219712370 Phone: +49 841 4544567 www.instyler.com - Instyler Setup: Create WiX-based MSI installations, elegantly. www.traveladdin.com - Travel Add-in for Outlook: Add travel and return times to your calendar. www.sebastianbrand.com - blogging about software development, deployment and productivity. > -Original Message- > From: Bob Arnson [mailto:b...@joyofsetup.com] > Sent: Tuesday, January 12, 2010 12:46 > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] short name of the default windows installer > directory and the status of burn > > On 1/11/2010 11:50 AM, Sebastian Brand (Instyler Software) wrote: > > The short name is generated randomly during the build of WiX installation. > > In my Wix3.5 install it's "nzj-aqro" (in Program Files folder) > > > > 1. It's not random: it's a stable hash, generated from the path information so > it doesn't change. > 2. MSI uses the provided short names for directories and files only if the > system doesn't support long file names. Otherwise, the file system > generates the short name. So for Sean, the answer is: "impossible to say, > because it varies on every system." That's why MSI provides the [#fileid], > [!fileid] and [$componentid] Formatted string substitutions. > > -- > sig://boB > http://joyofsetup.com/ > > > -- > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Automatic MSI rename???
You could wrap the MSI up in a self-extracting archive which unpacks to a known location. This also avoids the problem of the MSI file being renamed by the downloader. You shouldnt rename an MSI file. -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: 12 January 2010 14:07 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Automatic MSI rename??? Sounds like the user is downloading your MSI from a web page using Internet Explorer & clicking "Run" rather than "Save" in the download prompt. The MSI is being run from the users Temporary Internet Files & when the time comes for them to install the later version, the old MSI simply doesn't exist as it has been purged from the Temporary Internet Files during the period between the original installation & the update. No ideas how you would fix it though unless you get the user to download the old MSI to a location on their machine & then manually change the registry entry to point at that location before they attempt to run your new MSI. The only real fix is educating users that the Run button in the Internet Explorer download prompt should never be used for MSI's. Good Luck. 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: Tobi Ha [mailto:tob...@gmx.net] Sent: 12 January 2010 12:42 To: wix-users@lists.sourceforge.net; wix-users@lists.sourceforge.net Subject: [WiX-users] Automatic MSI rename??? Hi, I have a question concerning the following topic: In our company we create a msi file for a component/product ,e.g. xyz.msi. The product may only exist in one, the newest version, on the customers machine, therfore we use Major upgrades to replace any older version during installation. For each product version the same name of the msi, i.e. xyz.msi is used. This msi works on the most machines, but on some machines we get an error which points out that a xyz[1].msi cannot be found. Inside the registry instead of xyz.msi a named item xyz[1].msi can be found, but of cause our software does not rename the file. Does somebody know, which automatism changes the file name of an msi i.e. by appending indexes? Or is this an error within the MSI? Best regards, Tobias -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Uninstalling after a minor upgrade
Uninstalling after a minor upgrade Hi I have noticed that after applying a minor upgrade (1.0.1) the uninstall will be executed with using the older version of the installation package (1.0.0) and not with the new package (1.0.1). How to uninstall using version 1.0.1 ? This is what I done: I have a version 1.0.0 msi package. After installing version 1.0.0 I applied version 1.0.1 package, by doing a minor upgrade: msiexec /i Package.msi REINSTALL=ALL REINSTALLMODE=vomus All went well - my custom actions from version 1.0.1 were executed Then I uninstalled the package from Add/Remove Programs, but the package uninstalled was 1.0.0 package, so any custom actions that I have in package 1.0.1 were not executed. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Automatic MSI rename???
Sounds like the user is downloading your MSI from a web page using Internet Explorer & clicking "Run" rather than "Save" in the download prompt. The MSI is being run from the users Temporary Internet Files & when the time comes for them to install the later version, the old MSI simply doesn't exist as it has been purged from the Temporary Internet Files during the period between the original installation & the update. No ideas how you would fix it though unless you get the user to download the old MSI to a location on their machine & then manually change the registry entry to point at that location before they attempt to run your new MSI. The only real fix is educating users that the Run button in the Internet Explorer download prompt should never be used for MSI's. Good Luck. 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: Tobi Ha [mailto:tob...@gmx.net] Sent: 12 January 2010 12:42 To: wix-users@lists.sourceforge.net; wix-users@lists.sourceforge.net Subject: [WiX-users] Automatic MSI rename??? Hi, I have a question concerning the following topic: In our company we create a msi file for a component/product ,e.g. xyz.msi. The product may only exist in one, the newest version, on the customers machine, therfore we use Major upgrades to replace any older version during installation. For each product version the same name of the msi, i.e. xyz.msi is used. This msi works on the most machines, but on some machines we get an error which points out that a xyz[1].msi cannot be found. Inside the registry instead of xyz.msi a named item xyz[1].msi can be found, but of cause our software does not rename the file. Does somebody know, which automatism changes the file name of an msi i.e. by appending indexes? Or is this an error within the MSI? Best regards, Tobias -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Uninstalling after a minor upgrade
Hi I have noticed that after applying a minor upgrade (1.0.1) the uninstall will be executed with using the older version of the installation package (1.0.0) and not with the new package (1.0.1). How to uninstall using version 1.0.1 ? This is what I done: I have a version 1.0.0 msi package. After installing version 1.0.0 I applied version 1.0.1 package, by doing a minor upgrade: msiexec /i Package.msi REINSTALL=ALL REINSTALLMODE=vomus All went well - my custom actions from version 1.0.1 were executed Then I uninstalled the package from Add/Remove Programs, but the package uninstalled was 1.0.0 package, so any custom actions that I have in package 1.0.1 were not executed. -- View this message in context: http://n2.nabble.com/Uninstalling-after-a-minor-upgrade-tp4291466p4291466.html Sent from the wix-users mailing list archive at Nabble.com. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Automatic MSI rename???
Hi, I have a question concerning the following topic: In our company we create a msi file for a component/product ,e.g. xyz.msi. The product may only exist in one, the newest version, on the customers machine, therfore we use Major upgrades to replace any older version during installation. For each product version the same name of the msi, i.e. xyz.msi is used. This msi works on the most machines, but on some machines we get an error which points out that a xyz[1].msi cannot be found. Inside the registry instead of xyz.msi a named item xyz[1].msi can be found, but of cause our software does not rename the file. Does somebody know, which automatism changes the file name of an msi i.e. by appending indexes? Or is this an error within the MSI? Best regards, Tobias -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Disable repair and admin setup...
On 1/8/2010 12:53 PM, Wilson, Phil wrote: > It's like saying you don't support FilesInUse dialogs, requests for the > original install source, reboots at the end of the install and other things > that Windows will do whether you want to support them or not. > That's key: You can't disable or prevent repair; you can only cancel it once it's been invoked. I support a product that has a custom action like that and I had an IT manager of a well-known company ready to prevent the deployment of 30,000+ seats because: 1. We had a component-rules violation from a beta-to-beta upgrade. 2. The violation triggered a repair from an unadvertised shortcut via a COM registration. The reason we don't want to support repair? 1. Because the many custom actions we have might not support it. 2. Because nobody wants to take the time to verify whether the custom actions support it. 3. Because nobody in management cares about it -- until sales are lost because of it. -- sig://boB http://joyofsetup.com/ -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Added ErrorLog Dialog at end of Install...
On 1/7/2010 12:17 PM, Dominique Louis wrote: >What would be the best way to add a custom ErrorLog Dialog that is > only displayed if an error occurs during installation and it would > appear right at the end of the installation in that case. See InstallUISequence/Show/@OnExit for the different ways you can schedule 'exit' dialogs. -- sig://boB http://joyofsetup.com/ -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] short name of the default windows installer directory and the status of burn
On 1/11/2010 11:50 AM, Sebastian Brand (Instyler Software) wrote: > The short name is generated randomly during the build of WiX installation. > In my Wix3.5 install it's "nzj-aqro" (in Program Files folder) > 1. It's not random: it's a stable hash, generated from the path information so it doesn't change. 2. MSI uses the provided short names for directories and files only if the system doesn't support long file names. Otherwise, the file system generates the short name. So for Sean, the answer is: "impossible to say, because it varies on every system." That's why MSI provides the [#fileid], [!fileid] and [$componentid] Formatted string substitutions. -- sig://boB http://joyofsetup.com/ -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
