Re: [WiX-users] Wix or MSI bug ?
I think it's my mistake. The property was also declared in directories. However, if I remove it, it's never assigned. Must be missing something in the installexecutesequence. Sorry to have made you loosing your time. Sent from my iPod touch Le 8 nov. 2011 à 18:58, "Wilson, Phil" a écrit : > Mmm, odd. I just did a standard AppSearch/FileSearch using only the MSI > tables and a search for msi.dll in the System folder does not return a > trailing slash on the end of the file name, using MSI 4.5. WiX doesn't get in > the middle of a standard file search does it? > > Phil Wilson > > > -Original Message- > From: Pally Sandher [mailto:pally.sand...@iesve.com] > Sent: Tuesday, November 08, 2011 2:19 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Wix or MSI bug ? > > Phil the bug is that the path returned by FileSearch is of the format > C:\Directory\Filename.ext\ > The trailing slash after the filename makes the path returned by FileSearch > all but useless unless you use a custom action to remove it first, in which > case you may as well just use a custom action to return the correct value in > the first place. > > Palbinder Sandher > Software Platform Engineer > 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: Wilson, Phil [mailto:phil.wil...@invensys.com] > Sent: 07 November 2011 17:58 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Wix or MSI bug ? > > And most Windows Installer paths end with a \ too, in the path properties. > > Phil Wilson > > > -Original Message- > From: Pally Sandher [mailto:pally.sand...@iesve.com] > Sent: Monday, November 07, 2011 6:45 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Wix or MSI bug ? > > Old bug with FileSearch which has been "closed" but never actually fixed as > far as I can see -> > http://sourceforge.net/tracker/?func=detail&atid=642714&aid=1648267&group_id=105970 > & > http://sourceforge.net/tracker/index.php?func=detail&aid=1273447&group_id=105970&atid=642714 > > Palbinder Sandher > Software Platform Engineer > 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: Nicolas Penin [mailto:n.pe...@happly.fr] > Sent: 07 November 2011 09:02 > To: General discussion for Windows Installer XML toolset. > Subject: [WiX-users] Wix or MSI bug ? > > Dear all, > > I believe this is a bug in wix 3.6, but not sure... > > If I do the following : > > Key="SOFTWARE\Microsoft\Microsoft SQL Server\100\Tools\ClientSetup" > Type="directory" Name="Path"> > > > > > I have the appropriate path, except it is terminating with a \ > > If I change the Type of RegistrySearch to file, the content of SQLCMDPATH is > 'C:\' > > Any idea ? > > Regards, > Nicolas Penin > > -- > RSA(R) Conference 2012 > Save $700 by Nov 18 > Register now > http://p.sf.net/sfu/rsa-sfdev2dev1 > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > -- > RSA(R) Conference 2012 > Save $700 by Nov 18 > Register now > http://p.sf.net/sfu/rsa-sfdev2dev1 > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > *** Confidentiality Notice: This e-mail, including any associated or attached > files, is intended solely for the individual or entity to which it is > addressed. This e-mail is confidential and may well also be legally > privileged. If you have received it in error, you are on notice of its > status. Please notify the sender immediately by reply e-mail and then delete > this message from your system. Please do not copy it or use it for any > purposes, or disclose its contents to any other person. This email comes from > a division of the Invensys Group, owned by Invensys plc, which is a company > registered in England and Wales with its registered office at 3rd Floor, 40 > Grosvenor Place, London, SW1X 7AW (Registered number 166023). For a list of > European legal entities within the Invensys Group, please go to > h
[WiX-users] Dereference Indirect Property within Condition
Hello, I have a generic dialog that uses an indirect property for a username and I would like to enable and disable the Next button depending on whether a username has been entered. MyDialog.wxs ... ... Product.wxs ... ... With this code the button is always enabled, I assume because I need to dereference the Dialog.Username property somehow in the Condition. Could someone explain how to do this? # Attention: The information contained in this message and or attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any system and destroy any copies. # -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Arabic RTL special character issues with MSI dialog.
Hi, One of the localized languages in my setup msi is Arabic. (An Arabic transform that is embedded in the Setup.msi) When a text string ends with a special character (For example: C:\Program Files\Company\) the special character gets moved to the beginning of the string for Arabic only. Any ideas how I can fix this? I should also mention that I have all the correct RTL bits set to True for the controls and the dialog. Another example: My product name that I display at the top of the setup Dialog is Web Adaptor (IIS). So in Arabic dialogs, this shows as )WebAdaptor(IIS Thanks! Uma- -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Per-Machine and Per-User installs on XP/Vista/7 in the same MSI
In WiX 3.5, I am trying to create an MSI that can do both per-machine (ALLUSERS=1) and per-user (ALLUSERS="") installs from the same MSI. In this case, I want the default behavior to be per-machine, unless the user takes explicit steps to install per-user. I read several forum posts (and some of the Microsoft documentation), but they are confusing, or not promising. I am hoping that some ingenious folks here can figure out how to do this! Here is the scenario: Using WixUI_Advanced When double-clicking on the MSI (i.e., msiexec /i path-to-msi.msi, without setting any properties explicitly): On Windows XP: if the user is an administrator (privileged), the default Install button installs per-machine. if the user is not an administrator (not privileged), the default Install button installs per-machine--which will fail. However, clicking the "Advanced" button allows the user to install per-user. On Windows Vista/Windows 7: if the user is an administrator (privileged), AND elevated, the default Install button installs per-machine. (The shield icon may or may not be visible.) if the user is an administrator (privileged), AND NOT elevated, the default Install button installs per-machine. (The shield icon should be visible.) if the user is not an administrator (not privileged), the default Install button installs per-machine--which will require the user to be prompted for an administrator's credentials. (The shield icon should be visible.) However, clicking the "Advanced" button allows the user to install per-user. In all cases, explicitly setting ALLUSERS="" or ALLUSERS=1 at the msiexec command-line will force per-user or per-machine installs. The closest we have gotten thus far is: (And various other supporting WiX elements.) In the configuration above: On Windows XP, the behavior is correct. On Windows Vista/Windows 7: *CORRECT*: if the user is an administrator (privileged), AND elevated, the default Install button installs per-machine. (The shield icon is NOT visible.) *INCORRECT*: if the user is an administrator (privileged), AND NOT elevated, the default Install button installs per-machine. The shield icon is visible. However, the package does NOT elevate. The error given is: "You do not have sufficient privileges to complete this installation for all users of the machine. Log on as administrator and then retry this installation." Error 1925. *INCORRECT*: if the user is not an administrator (not privileged), the default Install button installs per-machine. The shield icon is visible. However, the package does NOT elevate. Same error as above. Clicking the "Advanced" button allows the user to install per-user successfully, without elevation. In all cases, explicitly setting ALLUSERS="" at the command-line performs the intended behavior of forcing per-user installation. ALLUSERS=1 at the command-line has the intended behavior of forcing per-machine installation, but it does NOT force elevation--so per-machine fails on Vista and 7. So basically, is there some way through custom actions or otherwise, to cause an MSI built with InstallPrivileges="limited" to request elevation? Alternatively, is there a way to cause an MSI built with InstallPrivileges="elevated" to reconfigure itself so that it does not request elevation? Thanks all, Sean -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Use of the Options dialog in default burn bootstrapper UI
Using the default UI for the new Wix 3.6 Burn bootstrapper there is a Options button that allows users to select an installation directory. Questions about this I have are: a) How is this referenced from within a chained MSI? b) Can it be pre-set to a directory rather than blank? c) Can the button be hidden/disabled altogether? (Ideally without modifying the source) Thanks! -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] New installer uninstalling an old application
Thanks - you are quite right in that I should prompt first. In this particular situation the other app is one that has very limited internal distribution and I just wanted to make the transition as seamless as possible to our users. My original problem (of the item going into the upgrade table) was simply down to the fact I'd forgotten to put in an element in! Once I did that I could then either let MSI do the uninstall of it without asking or use a custom action or launch condition to show an error message (though an OK/Cancel dialog would be preferable) . On 8 November 2011 18:37, John Cooper wrote: > 1) detect the old application and set a property; > 2) Use that property in a Launch Condition. Stop the install if present > with a "Please remove the-old-product first"; else continue with the > install. > > Unconditionally removing a product without the user's intervention is not > friendly behavior. > > -- > John Merryweather Cooper > Jack Henry & Associates, Inc. > Build & Install Engineer - jXchange > Office: 913-341-3434 x791011 > jocoo...@jackhenry.com > > > > > -Original Message- > From: Aled Hughes [mailto:trestlemon...@gmail.com] > Sent: Tuesday, November 08, 2011 12:29 PM > To: General discussion for Windows Installer XML toolset. > Subject: [WiX-users] New installer uninstalling an old application > > As part of my installer I need to uninstall some other application which > is being superseded, prior to installing the new app. So into my .wxs file > I've added in: > > > > In the hope that the application will be removed. However, it appears not > to work. Looking at the generated MSI with Orca the Upgrade table only > contains the upgrade guid for this installer. The FindRelatedProducts > action is in the InstallExecuteSequence table. > This is with latest Wix 3.6. > > Any ideas on how I should do this? > > -- > RSA(R) Conference 2012 > Save $700 by Nov 18 > Register now > http://p.sf.net/sfu/rsa-sfdev2dev1 > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > NOTICE: This electronic mail message and any files transmitted with it are > intended > exclusively for the individual or entity to which it is addressed. The > message, > together with any attachment, may contain confidential and/or privileged > information. > Any unauthorized review, use, printing, saving, copying, disclosure or > distribution > is strictly prohibited. If you have received this message in error, please > immediately advise the sender by reply email and delete all copies. > > > > -- > RSA(R) Conference 2012 > Save $700 by Nov 18 > Register now > http://p.sf.net/sfu/rsa-sfdev2dev1 > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WiX 3.6 and System.ArgumentException ("illegal characters in path") during build
I'm using WiX 3.6.2221.0 and am having problems trying to build using msbuild.exe. Most of the time the build is failing with System.ArgumentException: light.exe : error LGHT0001: Illegal characters in path. [C:\cygwin\home\mymsi.wixproj] Exception Type: System.ArgumentException Stack Trace: at System.IO.Path.CheckInvalidPathChars(String path) at System.IO.Path.IsPathRooted(String path) at Microsoft.Tools.WindowsInstallerXml.BinderFileManager.ResolveFile(String source, String type, SourceLineNumberCollection sourceLineNumbers, BindStage bindStage) at Microsoft.Tools.WindowsInstallerXml.Binder.ResolveFields(TableCollection tables, Hashtable cabinets, ArrayList delayedFields) at Microsoft.Tools.WindowsInstallerXml.Binder.BindDatabase(Output output, String databaseFile) at Microsoft.Tools.WindowsInstallerXml.Binder.Bind(Output output, String file) at Microsoft.Tools.WindowsInstallerXml.Tools.Light.Run(String[] args) Has anyone else come across this and know what the problem might be? -- Bruce Cran -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] New installer uninstalling an old application
1) detect the old application and set a property; 2) Use that property in a Launch Condition. Stop the install if present with a "Please remove the-old-product first"; else continue with the install. Unconditionally removing a product without the user's intervention is not friendly behavior. -- John Merryweather Cooper Jack Henry & Associates, Inc. Build & Install Engineer - jXchange Office: 913-341-3434 x791011 jocoo...@jackhenry.com -Original Message- From: Aled Hughes [mailto:trestlemon...@gmail.com] Sent: Tuesday, November 08, 2011 12:29 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] New installer uninstalling an old application As part of my installer I need to uninstall some other application which is being superseded, prior to installing the new app. So into my .wxs file I've added in: In the hope that the application will be removed. However, it appears not to work. Looking at the generated MSI with Orca the Upgrade table only contains the upgrade guid for this installer. The FindRelatedProducts action is in the InstallExecuteSequence table. This is with latest Wix 3.6. Any ideas on how I should do this? -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] New installer uninstalling an old application
As part of my installer I need to uninstall some other application which is being superseded, prior to installing the new app. So into my .wxs file I've added in: In the hope that the application will be removed. However, it appears not to work. Looking at the generated MSI with Orca the Upgrade table only contains the upgrade guid for this installer. The FindRelatedProducts action is in the InstallExecuteSequence table. This is with latest Wix 3.6. Any ideas on how I should do this? -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix or MSI bug ?
Mmm, odd. I just did a standard AppSearch/FileSearch using only the MSI tables and a search for msi.dll in the System folder does not return a trailing slash on the end of the file name, using MSI 4.5. WiX doesn't get in the middle of a standard file search does it? Phil Wilson -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Tuesday, November 08, 2011 2:19 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Wix or MSI bug ? Phil the bug is that the path returned by FileSearch is of the format C:\Directory\Filename.ext\ The trailing slash after the filename makes the path returned by FileSearch all but useless unless you use a custom action to remove it first, in which case you may as well just use a custom action to return the correct value in the first place. Palbinder Sandher Software Platform Engineer 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: Wilson, Phil [mailto:phil.wil...@invensys.com] Sent: 07 November 2011 17:58 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Wix or MSI bug ? And most Windows Installer paths end with a \ too, in the path properties. Phil Wilson -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Monday, November 07, 2011 6:45 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Wix or MSI bug ? Old bug with FileSearch which has been "closed" but never actually fixed as far as I can see -> http://sourceforge.net/tracker/?func=detail&atid=642714&aid=1648267&group_id=105970 & http://sourceforge.net/tracker/index.php?func=detail&aid=1273447&group_id=105970&atid=642714 Palbinder Sandher Software Platform Engineer 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: Nicolas Penin [mailto:n.pe...@happly.fr] Sent: 07 November 2011 09:02 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Wix or MSI bug ? Dear all, I believe this is a bug in wix 3.6, but not sure... If I do the following : I have the appropriate path, except it is terminating with a \ If I change the Type of RegistrySearch to file, the content of SQLCMDPATH is 'C:\' Any idea ? Regards, Nicolas Penin -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023). For a list of European legal entities within the Invensys Group, please go to http://www.invensys.com/en/legal/default.aspx. You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail recept...@invensys.com. This e-mail and any attachments thereto may be subject to the terms of any agreements between Invensys (and/or its subsidiaries and affiliates) and the recipient (and/or its subsidiaries and affiliates). -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-u
Re: [WiX-users] Wix or MSI bug ?
I use this type of search in WiX 3.5 successfully but I have not tried to confirm its behavior in WiX 3.6. Edwin G. Castro Software Developer - Staff Digital Channels Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail > -Original Message- > From: Pally Sandher [mailto:pally.sand...@iesve.com] > Sent: Tuesday, November 08, 2011 2:19 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Wix or MSI bug ? > > Phil the bug is that the path returned by FileSearch is of the format > C:\Directory\Filename.ext\ The trailing slash after the filename makes the > path > returned by FileSearch all but useless unless you use a custom action to > remove > it first, in which case you may as well just use a custom action to return the > correct value in the first place. > > Palbinder Sandher > Software Platform Engineer > 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: Wilson, Phil [mailto:phil.wil...@invensys.com] > Sent: 07 November 2011 17:58 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Wix or MSI bug ? > > And most Windows Installer paths end with a \ too, in the path properties. > > Phil Wilson > > > -Original Message- > From: Pally Sandher [mailto:pally.sand...@iesve.com] > Sent: Monday, November 07, 2011 6:45 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Wix or MSI bug ? > > Old bug with FileSearch which has been "closed" but never actually fixed as > far > as I can see -> > http://sourceforge.net/tracker/?func=detail&atid=642714&aid=1648267&grou > p_id=105970 & > http://sourceforge.net/tracker/index.php?func=detail&aid=1273447&group_id= > 105970&atid=642714 > > Palbinder Sandher > Software Platform Engineer > 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: Nicolas Penin [mailto:n.pe...@happly.fr] > Sent: 07 November 2011 09:02 > To: General discussion for Windows Installer XML toolset. > Subject: [WiX-users] Wix or MSI bug ? > > Dear all, > > I believe this is a bug in wix 3.6, but not sure... > > If I do the following : > >Key="SOFTWARE\Microsoft\Microsoft SQL Server\100\Tools\ClientSetup" > Type="directory" Name="Path"> > > > > > I have the appropriate path, except it is terminating with a \ > > If I change the Type of RegistrySearch to file, the content of SQLCMDPATH is > 'C:\' > > Any idea ? > > Regards, > Nicolas Penin > > -- > RSA(R) Conference 2012 > Save $700 by Nov 18 > Register now > http://p.sf.net/sfu/rsa-sfdev2dev1 > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > -- > RSA(R) Conference 2012 > Save $700 by Nov 18 > Register now > http://p.sf.net/sfu/rsa-sfdev2dev1 > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > *** Confidentiality Notice: This e-mail, including any associated or attached > files, is intended solely for the individual or entity to which it is > addressed. This > e-mail is confidential and may well also be legally privileged. If you have > received it in error, you are on notice of its status. Please notify the > sender > immediately by reply e-mail and then delete this message from your system. > Please do not copy it or use it for any purposes, or disclose its contents to > any > other person. This email comes from a division of the Invensys Group, owned by > Invensys plc, which is a company registered in England and Wales with its > registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW > (Registered number 166023). For a list of European legal entities within the > Invensys Group, please go to http://www.invensys.com/en/legal/default.aspx. > > You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail > recept...@invensys.com. This e-mail and any attachments thereto may be > subject to the terms of any agreements between Invensys (and/or its > subsidiaries and affiliates) and the recipient (and/or
Re: [WiX-users] Patch with a simple file change
Bob Arnson-6 wrote: > > In addition to admin images, you can use Melt.exe to build an image you > can use without -ax. > I thought Melt only http://wix.sourceforge.net/manual-wix3/AllTools.htm dealt with merge modules (.msm). Special use, maybe? - John -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-with-a-simple-file-change-tp6956231p6975065.html Sent from the wix-users mailing list archive at Nabble.com. -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Fragments and Patch generation
MSDN section on major upgrades http://msdn.microsoft.com/en-us/library/windows/desktop/aa369786%28v=vs.85%29 .aspx Wix help file How to Guides -> Product upgrades -> Implement a major upgrade in your installer Wix Tutorial http://wix.tramontana.co.hu/tutorial/upgrades-and-modularization Alex Shevchuk's series on Wix http://blogs.technet.com/b/alexshev/archive/2008/02/15/from-msi-to-wix-part-8 -major-upgrade.aspx Bob's blog http://www.joyofsetup.com/2008/12/30/paying-for-upgrades/ There are many more sources of information including this mailing list and blogs of some of the people who contribute to it. It's important to understand the MSI concepts in the MSDN to start with though. -Original Message- From: Justin Hull [mailto:justin.h...@assetpoint.com] Sent: 08 November 2011 16:38 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Fragments and Patch generation You have a number of options depending on what your constraints are. The easiest upgrade type to write is a major upgrade with an early scheduling of RemoveExistingProducts. It's much more tolerant of mistakes. Could you point me in the right direction for this? I have both Phil Wilson's Windows Installer book and the Wix developer guide, but the section on upgrades is what I'm stuck on. To get past this point in my project is what I am looking for so we can revamp the whole process going forward (I inherited this project). We may look at one file per component, but this is not feasible for this install/upgrade. - --- Moving to 1 file per component is another option. That way, the keypath of each component is the file that changes. You can't do this if you've already released because of the rules in what you can do in an upgrade. If you must keep using 1 component per directory then always bump the version number of the component's keypath of the component when changing anything in the component. I believe that's what you meant by changing the initial file in the basedata folder. You would have to do that for each component (and therefore directory) that changes. Adding keypath=yes isn't going to help because its already implicitly set to the default. Also you must not change a component keypath, once set. -Original Message- From: justin hull [mailto:justin.h...@assetpoint.com] Sent: 08 November 2011 16:13 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Fragments and Patch generation Thanks for the input. It got me looking in different directions. I found this link which is interesting for it both advocates the need to break MS rules on one file per component while stating it is the preferred method (sigh). http://makemsi-manual.dennisbareis.com/component_keypath.htm In looking at my wxi files, these are build via paraffin and with the amount of files involved I had paraffin group the files under directory components. Given what you said, could I solve this by just changing the initial file in the basedata folder? Would I have to do that for each sub directory? Would adding keypath='yes' work instead? I will try these options with the remaining wisps of hair I still have on my head. I did see that the base component does not have keypath yet does allow updates of files. My other plan will be to manually integrate the fragment files into the main project (not what I want to do in the future) to see if that will work. Justin Hull [cid:image003.jpg@01CC9E07.564C9180] Office: 864-679-3500 (3413) From: Peter Shirtcliffe [via Windows Installer XML (WiX) toolset] [mailto:ml-node+s687559n6974692...@n2.nabble.com] Sent: Tuesday, November 08, 2011 10:24 AM To: Justin Hull Subject: Re: Fragments and Patch generation I did a quick diff of the 2 wxs files. The changes appear to be in a component whose keypath doesn't change. I think, by default, in Wix v3+ the first file/registry key in a component is taken to be the keypath unless one is specified explicitly. Unless the component's keypath changes, the component won't be reinstalled. This is one reason 1 file per component is recommended - you don't need to bump the version of unchanged files to get your changed files updated. -Original Message- From: justin hull [mailto:[hidden email]] Sent: 08 November 2011 14:01 To: [hidden email] Subject: Re: [WiX-users] Fragments and Patch generation That makes sense. The files are large so I will upload them. Original base install http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n6974348/T abWareXiTools8200.wxs TabWareXiTools8200.wxs project for full install for patch (upgrade) http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n6974348/T abWareXiTools8201.wxs TabWareXiTools8201.wxs Patch project 8200 > 8201 http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n6974348/P atch.wxs Patch.wxs Database fra
Re: [WiX-users] Fragments and Patch generation
You have a number of options depending on what your constraints are.
The easiest upgrade type to write is a major upgrade with an early scheduling
of RemoveExistingProducts. It's much more tolerant of mistakes.
Could you point me in the right direction for this? I have both Phil Wilson's
Windows Installer book and the Wix developer guide, but the section on upgrades
is what I'm stuck on. To get past this point in my project is what I am
looking for so we can revamp the whole process going forward (I inherited this
project).
We may look at one file per component, but this is not feasible for this
install/upgrade.
Moving to 1 file per component is another option. That way, the keypath of
each component is the file that changes. You can't do this if you've already
released because of the rules in what you can do in an upgrade.
If you must keep using 1 component per directory then always bump the version
number of the component's keypath of the component when changing anything in
the component. I believe that's what you meant by changing the initial file
in the basedata folder. You would have to do that for each component (and
therefore directory) that changes. Adding keypath=yes isn't going to help
because its already implicitly set to the default. Also you must not change a
component keypath, once set.
-Original Message-
From: justin hull [mailto:justin.h...@assetpoint.com]
Sent: 08 November 2011 16:13
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Fragments and Patch generation
Thanks for the input. It got me looking in different directions. I found
this link which is interesting for it both advocates the need to break MS
rules on one file per component while stating it is the preferred method
(sigh).
http://makemsi-manual.dennisbareis.com/component_keypath.htm
In looking at my wxi files, these are build via paraffin and with the amount
of files involved I had paraffin group the files under directory components.
Given what you said, could I solve this by just changing the initial file in
the basedata folder? Would I have to do that for each sub directory? Would
adding keypath='yes' work instead? I will try these options with the
remaining wisps of hair I still have on my head.
I did see that the base component does not have keypath yet does allow
updates of files.
My other plan will be to manually integrate the fragment files into the main
project (not what I want to do in the future) to see if that will work.
Justin Hull
[cid:image003.jpg@01CC9E07.564C9180]
Office: 864-679-3500 (3413)
From: Peter Shirtcliffe [via Windows Installer XML (WiX) toolset]
[mailto:ml-node+s687559n6974692...@n2.nabble.com]
Sent: Tuesday, November 08, 2011 10:24 AM
To: Justin Hull
Subject: Re: Fragments and Patch generation
I did a quick diff of the 2 wxs files. The changes appear to be in a
component whose keypath doesn't change. I think, by default, in Wix v3+ the
first file/registry key in a component is taken to be the keypath unless one
is specified explicitly.
Unless the component's keypath changes, the component won't be reinstalled.
This is one reason 1 file per component is recommended - you don't need to
bump the version of unchanged files to get your changed files updated.
-Original Message-
From: justin hull [mailto:[hidden
email]]
Sent: 08 November 2011 14:01
To: [hidden email]
Subject: Re: [WiX-users] Fragments and Patch generation
That makes sense. The files are large so I will upload them.
Original base install
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n6974348/T
abWareXiTools8200.wxs
TabWareXiTools8200.wxs
project for full install for patch (upgrade)
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n6974348/T
abWareXiTools8201.wxs
TabWareXiTools8201.wxs
Patch project 8200 > 8201
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n6974348/P
atch.wxs
Patch.wxs
Database fragment
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n6974348/d
atabasefiles.wxi
databasefiles.wxi
The wixmst differences file is over 2mg so I wont upload it all, but what is
happening is that I am getting the files in the main directory updated, but
I am not getting the files in the sub folders like Database
\Tabware
{Files here are updated}
\Databases
\BaseData
{These fiels are not even touched}
An example is this one database file. I find it in the diff file in various
locations, but it does not update even when I "force" an update:
...
-file_twdatabase_11comp_twdatabase_0
zzwinact.txt14686651248
...
-file_twdatabase_11dir_DATABASE_basedata_11c:\8.2.0.x\Pro
01\DATABASE\basedata\zzwinact.txt-100
...
The database files are added to the proejct via the fragment. This is why I
am wondering if the fragment, built by paraffin, is not being recogn
Re: [WiX-users] Fragments and Patch generation
You have a number of options depending on what your constraints are.
The easiest upgrade type to write is a major upgrade with an early scheduling
of RemoveExistingProducts. It's much more tolerant of mistakes.
Moving to 1 file per component is another option. That way, the keypath of
each component is the file that changes. You can't do this if you've already
released because of the rules in what you can do in an upgrade.
If you must keep using 1 component per directory then always bump the version
number of the component's keypath of the component when changing anything in
the component. I believe that's what you meant by changing the initial file
in the basedata folder. You would have to do that for each component (and
therefore directory) that changes. Adding keypath=yes isn't going to help
because its already implicitly set to the default. Also you must not change a
component keypath, once set.
-Original Message-
From: justin hull [mailto:justin.h...@assetpoint.com]
Sent: 08 November 2011 16:13
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Fragments and Patch generation
Thanks for the input. It got me looking in different directions. I found
this link which is interesting for it both advocates the need to break MS
rules on one file per component while stating it is the preferred method
(sigh).
http://makemsi-manual.dennisbareis.com/component_keypath.htm
In looking at my wxi files, these are build via paraffin and with the amount
of files involved I had paraffin group the files under directory components.
Given what you said, could I solve this by just changing the initial file in
the basedata folder? Would I have to do that for each sub directory? Would
adding keypath='yes' work instead? I will try these options with the
remaining wisps of hair I still have on my head.
I did see that the base component does not have keypath yet does allow
updates of files.
My other plan will be to manually integrate the fragment files into the main
project (not what I want to do in the future) to see if that will work.
Justin Hull
[cid:image003.jpg@01CC9E07.564C9180]
Office: 864-679-3500 (3413)
From: Peter Shirtcliffe [via Windows Installer XML (WiX) toolset]
[mailto:ml-node+s687559n6974692...@n2.nabble.com]
Sent: Tuesday, November 08, 2011 10:24 AM
To: Justin Hull
Subject: Re: Fragments and Patch generation
I did a quick diff of the 2 wxs files. The changes appear to be in a
component whose keypath doesn't change. I think, by default, in Wix v3+ the
first file/registry key in a component is taken to be the keypath unless one
is specified explicitly.
Unless the component's keypath changes, the component won't be reinstalled.
This is one reason 1 file per component is recommended - you don't need to
bump the version of unchanged files to get your changed files updated.
-Original Message-
From: justin hull [mailto:[hidden
email]]
Sent: 08 November 2011 14:01
To: [hidden email]
Subject: Re: [WiX-users] Fragments and Patch generation
That makes sense. The files are large so I will upload them.
Original base install
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n6974348/T
abWareXiTools8200.wxs
TabWareXiTools8200.wxs
project for full install for patch (upgrade)
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n6974348/T
abWareXiTools8201.wxs
TabWareXiTools8201.wxs
Patch project 8200 > 8201
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n6974348/P
atch.wxs
Patch.wxs
Database fragment
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n6974348/d
atabasefiles.wxi
databasefiles.wxi
The wixmst differences file is over 2mg so I wont upload it all, but what is
happening is that I am getting the files in the main directory updated, but
I am not getting the files in the sub folders like Database
\Tabware
{Files here are updated}
\Databases
\BaseData
{These fiels are not even touched}
An example is this one database file. I find it in the diff file in various
locations, but it does not update even when I "force" an update:
...
-file_twdatabase_11comp_twdatabase_0
zzwinact.txt14686651248
...
-file_twdatabase_11dir_DATABASE_basedata_11c:\8.2.0.x\Pro
01\DATABASE\basedata\zzwinact.txt-100
...
The database files are added to the proejct via the fragment. This is why I
am wondering if the fragment, built by paraffin, is not being recognized in
the pyro process.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Fragments-and-P
atch-generation-tp6972320p6974348.html
Sent from the wix-users mailing list archive at Nabble.com.
-
-
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
___
WiX-users mailing list
[hidden email]
https://lists.sourc
Re: [WiX-users] Fragments and Patch generation
Thanks for the input. It got me looking in different directions. I found this
link which is interesting for it both advocates the need to break MS rules on
one file per component while stating it is the preferred method (sigh).
http://makemsi-manual.dennisbareis.com/component_keypath.htm
In looking at my wxi files, these are build via paraffin and with the amount of
files involved I had paraffin group the files under directory components.
Given what you said, could I solve this by just changing the initial file in
the basedata folder? Would I have to do that for each sub directory? Would
adding keypath='yes' work instead? I will try these options with the remaining
wisps of hair I still have on my head.
I did see that the base component does not have keypath yet does allow updates
of files.
My other plan will be to manually integrate the fragment files into the main
project (not what I want to do in the future) to see if that will work.
Justin Hull
[cid:image003.jpg@01CC9E07.564C9180]
Office: 864-679-3500 (3413)
From: Peter Shirtcliffe [via Windows Installer XML (WiX) toolset]
[mailto:ml-node+s687559n6974692...@n2.nabble.com]
Sent: Tuesday, November 08, 2011 10:24 AM
To: Justin Hull
Subject: Re: Fragments and Patch generation
I did a quick diff of the 2 wxs files. The changes appear to be in a
component whose keypath doesn't change. I think, by default, in Wix v3+ the
first file/registry key in a component is taken to be the keypath unless one
is specified explicitly.
Unless the component's keypath changes, the component won't be reinstalled.
This is one reason 1 file per component is recommended - you don't need to
bump the version of unchanged files to get your changed files updated.
-Original Message-
From: justin hull [mailto:[hidden
email]]
Sent: 08 November 2011 14:01
To: [hidden email]
Subject: Re: [WiX-users] Fragments and Patch generation
That makes sense. The files are large so I will upload them.
Original base install
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n6974348/T
abWareXiTools8200.wxs
TabWareXiTools8200.wxs
project for full install for patch (upgrade)
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n6974348/T
abWareXiTools8201.wxs
TabWareXiTools8201.wxs
Patch project 8200 > 8201
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n6974348/P
atch.wxs
Patch.wxs
Database fragment
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n6974348/d
atabasefiles.wxi
databasefiles.wxi
The wixmst differences file is over 2mg so I wont upload it all, but what is
happening is that I am getting the files in the main directory updated, but
I am not getting the files in the sub folders like Database
\Tabware
{Files here are updated}
\Databases
\BaseData
{These fiels are not even touched}
An example is this one database file. I find it in the diff file in various
locations, but it does not update even when I "force" an update:
...
-file_twdatabase_11comp_twdatabase_0
zzwinact.txt14686651248
...
-file_twdatabase_11dir_DATABASE_basedata_11c:\8.2.0.x\Pro
01\DATABASE\basedata\zzwinact.txt-100
...
The database files are added to the proejct via the fragment. This is why I
am wondering if the fragment, built by paraffin, is not being recognized in
the pyro process.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Fragments-and-P
atch-generation-tp6972320p6974348.html
Sent from the wix-users mailing list archive at Nabble.com.
-
-
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
___
WiX-users mailing list
[hidden email]
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.
--
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
___
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
If you reply to this email, your message will be added to the discussion below:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Fragments-and-Patch-generation-tp6972320p6974692.html
To unsubscribe from Fragments and Patch generation, click
here
Re: [WiX-users] Burn - what's the difference between InstallConditionand DetectCondition?
For the first part, I can say yes. I have not tested yet the second assumption, but I hope it works as you (and I) expect it. Regards, Nicolas Penin -Message d'origine- De : Aled Hughes [mailto:trestlemon...@gmail.com] Envoyé : mardi 8 novembre 2011 16:56 À : General discussion for Windows Installer XML toolset. Objet : Re: [WiX-users] Burn - what's the difference between InstallConditionand DetectCondition? Am I right in deducing that InstallCondition, if specified, will override DetectCondition? So if InstallCondition=False, the package will not get installed regardless of DetectCondition. Likewise, if InstallCondition=True, the package is always installed regardless of DetectCondition. or is is that if InstallCondition=True then package is installed only if DetectCondtion=False? On 8 November 2011 15:30, Nicolas Penin wrote: > The DetectCondition helps you know whether the package is installed or not. > The InstallCondition allows you to choose to install a package even if > the DetectCondition is true, or to choose not to install a package if > the DetectCondition is False. > > I use it because I have to install SqlExpress in a specific case > (depending on my UI), the detect condition helps me to know whether it > is already installed, and the install condition has to be true (my > specific > case) to allow the installation of SQLExpress. > > Does it make sense ? > > Regards, > Nicolas Penin > > > -Message d'origine- > De : Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Envoyé : mardi 8 > novembre 2011 16:26 À : General discussion for Windows Installer XML > toolset. > Objet : Re: [WiX-users] Burn - what's the difference between > InstallConditionand DetectCondition? > > I've not looked at Burn but I would guess you could install something > under a wider variety of conditions that it just being already present > or not. For instance you might want to install a package based on OS > or language or on the presence of other products. > > -Original Message- > From: Aled Hughes [mailto:trestlemon...@gmail.com] > Sent: 08 November 2011 15:22 > To: General discussion for Windows Installer XML toolset. > Subject: [WiX-users] Burn - what's the difference between > InstallConditionand DetectCondition? > > With burn, what is the difference between the DetectCondition and > InstallCondition on the element? I noticed that the > NetFx4.wxs file in the WiX sources uses DetectCondition to seemingly > prevent installation of .Net4 if it is already installed - but isn't > InstallCondition the same? > > -- > --- > - > RSA(R) Conference 2012 > Save $700 by Nov 18 > Register now > http://p.sf.net/sfu/rsa-sfdev2dev1 > ___ > 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. > > > > -- > > RSA(R) Conference 2012 > Save $700 by Nov 18 > Register now > http://p.sf.net/sfu/rsa-sfdev2dev1 > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > -- > > RSA(R) Conference 2012 > Save $700 by Nov 18 > Register now > http://p.sf.net/sfu/rsa-sfdev2dev1 > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn - what's the difference between InstallConditionand DetectCondition?
Am I right in deducing that InstallCondition, if specified, will override DetectCondition? So if InstallCondition=False, the package will not get installed regardless of DetectCondition. Likewise, if InstallCondition=True, the package is always installed regardless of DetectCondition. or is is that if InstallCondition=True then package is installed only if DetectCondtion=False? On 8 November 2011 15:30, Nicolas Penin wrote: > The DetectCondition helps you know whether the package is installed or not. > The InstallCondition allows you to choose to install a package even if the > DetectCondition is true, or to choose not to install a package if the > DetectCondition is False. > > I use it because I have to install SqlExpress in a specific case > (depending on my UI), the detect condition helps me to know whether it is > already installed, and the install condition has to be true (my specific > case) to allow the installation of SQLExpress. > > Does it make sense ? > > Regards, > Nicolas Penin > > > -Message d'origine- > De : Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] > Envoyé : mardi 8 novembre 2011 16:26 > À : General discussion for Windows Installer XML toolset. > Objet : Re: [WiX-users] Burn - what's the difference between > InstallConditionand DetectCondition? > > I've not looked at Burn but I would guess you could install something > under a wider variety of conditions that it just being already present or > not. For instance you might want to install a package based on OS or > language or on the presence of other products. > > -Original Message- > From: Aled Hughes [mailto:trestlemon...@gmail.com] > Sent: 08 November 2011 15:22 > To: General discussion for Windows Installer XML toolset. > Subject: [WiX-users] Burn - what's the difference between > InstallConditionand DetectCondition? > > With burn, what is the difference between the DetectCondition and > InstallCondition on the element? I noticed that the NetFx4.wxs > file in the WiX sources uses DetectCondition to seemingly prevent > installation of .Net4 if it is already installed - but isn't > InstallCondition the same? > > - > - > RSA(R) Conference 2012 > Save $700 by Nov 18 > Register now > http://p.sf.net/sfu/rsa-sfdev2dev1 > ___ > 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. > > > > -- > RSA(R) Conference 2012 > Save $700 by Nov 18 > Register now > http://p.sf.net/sfu/rsa-sfdev2dev1 > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > -- > RSA(R) Conference 2012 > Save $700 by Nov 18 > Register now > http://p.sf.net/sfu/rsa-sfdev2dev1 > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn - what's the difference between InstallConditionand DetectCondition?
The DetectCondition helps you know whether the package is installed or not. The InstallCondition allows you to choose to install a package even if the DetectCondition is true, or to choose not to install a package if the DetectCondition is False. I use it because I have to install SqlExpress in a specific case (depending on my UI), the detect condition helps me to know whether it is already installed, and the install condition has to be true (my specific case) to allow the installation of SQLExpress. Does it make sense ? Regards, Nicolas Penin -Message d'origine- De : Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Envoyé : mardi 8 novembre 2011 16:26 À : General discussion for Windows Installer XML toolset. Objet : Re: [WiX-users] Burn - what's the difference between InstallConditionand DetectCondition? I've not looked at Burn but I would guess you could install something under a wider variety of conditions that it just being already present or not. For instance you might want to install a package based on OS or language or on the presence of other products. -Original Message- From: Aled Hughes [mailto:trestlemon...@gmail.com] Sent: 08 November 2011 15:22 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Burn - what's the difference between InstallConditionand DetectCondition? With burn, what is the difference between the DetectCondition and InstallCondition on the element? I noticed that the NetFx4.wxs file in the WiX sources uses DetectCondition to seemingly prevent installation of .Net4 if it is already installed - but isn't InstallCondition the same? - - RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ 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. -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn - what's the difference between InstallConditionand DetectCondition?
I've not looked at Burn but I would guess you could install something under a wider variety of conditions that it just being already present or not. For instance you might want to install a package based on OS or language or on the presence of other products. -Original Message- From: Aled Hughes [mailto:trestlemon...@gmail.com] Sent: 08 November 2011 15:22 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Burn - what's the difference between InstallConditionand DetectCondition? With burn, what is the difference between the DetectCondition and InstallCondition on the element? I noticed that the NetFx4.wxs file in the WiX sources uses DetectCondition to seemingly prevent installation of .Net4 if it is already installed - but isn't InstallCondition the same? - - RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ 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. -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Fragments and Patch generation
I did a quick diff of the 2 wxs files. The changes appear to be in a
component whose keypath doesn't change. I think, by default, in Wix v3+ the
first file/registry key in a component is taken to be the keypath unless one
is specified explicitly.
Unless the component's keypath changes, the component won't be reinstalled.
This is one reason 1 file per component is recommended - you don't need to
bump the version of unchanged files to get your changed files updated.
-Original Message-
From: justin hull [mailto:justin.h...@assetpoint.com]
Sent: 08 November 2011 14:01
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Fragments and Patch generation
That makes sense. The files are large so I will upload them.
Original base install
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n6974348/T
abWareXiTools8200.wxs
TabWareXiTools8200.wxs
project for full install for patch (upgrade)
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n6974348/T
abWareXiTools8201.wxs
TabWareXiTools8201.wxs
Patch project 8200 > 8201
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n6974348/P
atch.wxs
Patch.wxs
Database fragment
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n6974348/d
atabasefiles.wxi
databasefiles.wxi
The wixmst differences file is over 2mg so I wont upload it all, but what is
happening is that I am getting the files in the main directory updated, but
I am not getting the files in the sub folders like Database
\Tabware
{Files here are updated}
\Databases
\BaseData
{These fiels are not even touched}
An example is this one database file. I find it in the diff file in various
locations, but it does not update even when I "force" an update:
...
-file_twdatabase_11comp_twdatabase_0
zzwinact.txt14686651248
...
-file_twdatabase_11dir_DATABASE_basedata_11c:\8.2.0.x\Pro
01\DATABASE\basedata\zzwinact.txt-100
...
The database files are added to the proejct via the fragment. This is why I
am wondering if the fragment, built by paraffin, is not being recognized in
the pyro process.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Fragments-and-P
atch-generation-tp6972320p6974348.html
Sent from the wix-users mailing list archive at Nabble.com.
-
-
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
___
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.
--
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Burn - what's the difference between InstallCondition and DetectCondition?
With burn, what is the difference between the DetectCondition and InstallCondition on the element? I noticed that the NetFx4.wxs file in the WiX sources uses DetectCondition to seemingly prevent installation of .Net4 if it is already installed - but isn't InstallCondition the same? -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Fragments and Patch generation
That makes sense. The files are large so I will upload them.
Original base install
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n6974348/TabWareXiTools8200.wxs
TabWareXiTools8200.wxs
project for full install for patch (upgrade)
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n6974348/TabWareXiTools8201.wxs
TabWareXiTools8201.wxs
Patch project 8200 > 8201
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n6974348/Patch.wxs
Patch.wxs
Database fragment
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n6974348/databasefiles.wxi
databasefiles.wxi
The wixmst differences file is over 2mg so I wont upload it all, but what is
happening is that I am getting the files in the main directory updated, but
I am not getting the files in the sub folders like Database
\Tabware
{Files here are updated}
\Databases
\BaseData
{These fiels are not even touched}
An example is this one database file. I find it in the diff file in various
locations, but it does not update even when I "force" an update:
...
-file_twdatabase_11comp_twdatabase_0zzwinact.txt14686651248
...
-file_twdatabase_11dir_DATABASE_basedata_11c:\8.2.0.x\Pro01\DATABASE\basedata\zzwinact.txt-100
...
The database files are added to the proejct via the fragment. This is why I
am wondering if the fragment, built by paraffin, is not being recognized in
the pyro process.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Fragments-and-Patch-generation-tp6972320p6974348.html
Sent from the wix-users mailing list archive at Nabble.com.
--
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Advanced Wix based installer
Here is the source file... cleaned up a bit REMOVED REST OF THE FILE ID LINES INSTALLLOCATION="" NOT Installed 2 1 1 2 2 -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Advanced-Wix-based-installer-tp6973595p6974241.html Sent from the wix-users mailing list archive at Nabble.com. -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Strange behavior with wix 3.6 (wwansvc, VirtualBox)
Finally, here's what happend: The MSI contains a RegistryKey which references another RegistryKey by id ( Key="[OtherKey]\SubKey" ). By I removed the id attribute from the other RegistryKey. So the references property does not exist. I assume it expanded to "SOFTWARE\Microsoft\WwanSvc\Profiles". Not sure why, though. Regards Michael Am 08.11.2011 12:06, schrieb Michael Stoll: > Just tried uninstalling from control panel, without bootstrapper. Same > problem. > > Here's the complete log: > > Error 1402. Could not open key: > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WwanSvc\Profiles. System error > 5. Verify that you have sufficient access to that key, or contact your > support personnel. > === Logging stopped: 08.11.2011 12:00:49 === > 1: 1101 2: C:\Config.Msi\2fcfc1.rbs 3: 3 > 1: 1712 > > Regards Michael > > Am 08.11.2011 09:10, schrieb Michael Stoll: >> Hi, >> >> I've noticed a strange behavior using burn. And I have no idea, how to >> analyse it. Here's what happend: >> >> Wix-Version: 3.6.2221 >> Test-Environment: Windows 7 Professional x64 running inside of >> VirtualBox 4.1.4 with Additions. >> Installation-Package: Burn with 2 msi-packages (created with wix) and >> some prerequisite exe packages >> >> I intended to test the installation package on the virtual test >> platform. So I copied the package to the VM, installed it, found a >> missing component and tried to uninstall. During uninstall an error >> occured (Permission denied on >> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\WwanSvc). The log >> file of one msi package contains a similar message. >> The first strange thing is, that the msi package does not contain this >> registry key in the Registry table. >> Then I rebooted the VM. But the system does not boot any more. After >> "Windows is starting" there's only a black screen, even when booting in >> safe mode. >> >> I looking forward to any helpful advise. >> >> Regards >> Michael >> >> >> -- >> RSA(R) Conference 2012 >> Save $700 by Nov 18 >> Register now >> http://p.sf.net/sfu/rsa-sfdev2dev1 >> ___ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> > > -- > RSA(R) Conference 2012 > Save $700 by Nov 18 > Register now > http://p.sf.net/sfu/rsa-sfdev2dev1 > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Deploying Web Services
I am tasked with writing an installer to deploy some (.NET) web services on IIS. Typically the deployment will involve some/all of the following: During install selecting: . The App pool (test that the AppPool the user chooses is compatible with the service/application being installed) . The website to use - IIS can host more than one website . The virtual application and the URL that the service will be accessible by. . Various changes to XML config files that are installed o Connection strings for the service to connect to a database (we allow multiple connection strings) o Some general application settings (output directory for results of the service, location of some other installed products on the machine, etc.) . Enabling the distributed transaction coordinator The web service is a pretty complicated and this list of requirements will undoubtedly grow. I can generate a web deployment package which automates some of this stuff (and, till now, have been doing the rest manually, e.g., in IIS). My question is related to creating a Wix installer for this stuff - should I start from scratch and implement all the steps natively in Wix, or should I create the web deployment package and install it by implementing a custom action that calls the web deploy application, then do any additional stuff in Wix. If anyone can point me to information about how best to accomplish this, it will be much appreciated. Thanks sanjay -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Dependencies between components
Thanks, I think this will fit when i get this working. I tried: But when I then only select the Symbols it still installs only the Symbols ComponentGroup. Any idea whats wrong? greetings Steffen 2011/11/8 Michael Stoll > AFAIK you cannot do that with ComponentGroups. > > If you like a flat structure you can do something like this: > > > > ... > > > > > > This will install the "Binaries"-Feature when Debug or Binaries is > selected. It's like a dependency of "Debug" to "Binaries". > > Regards Michael > > Am 08.11.2011 12:39, schrieb Steffen Henne: > > That perhaps explains the strange behavior of the DependencyExtension :D > > > > Any possibibilty then to set one ComponentGroup as optional? > > I'm thinking about having an ComponentGroup with Binaries and one with > the > > Program Debug Databases. Then the Debug dbs will be kind of addition to > the > > Binaries. > > > > Any other way except from defining the Debug dbs as Subfeature of the > > Binaries like > > > > > > > > > > > > > > > greetings Steffen > > > > 2011/11/8 Michael Stoll > > > >> AFAIK the DependencyExtension is about dependencies between installer > >> packages. > >> > >> I'm solving component dependencies with groups. Like this: > >> > >> ... > >> ... > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> So I'm only referencing groups in the feature and thus can add any > >> dependency like any other component to that group. > >> > >> > >> Regards Michael > >> > >> > >> Am 08.11.2011 10:49, schrieb Steffen Henne: > >>> Thanks for your answer. I actually think it's not necessary but we want > >> to > >>> try it out for the scenario the guy who creates our big main wxs file > has > >>> no idea about the dependencies between all the projects and we can > define > >>> them somerwhere else. > >>> > >>> I just found the DependencyExtension and tried to use it. Looks like > >> this: > >>> in Feature A: > >>> > >>> > >>> > >>> > >>> > >>> in Feature B: > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> So B should be dependent of A right? > >>> now if i build the installer and select only Feature B it says as > >> expected > >>> some dependencies are missing. > >>> but if i now select feature A and B the same message pops up although > all > >>> dependencies are actually fulfilled. > >>> > >>> Any idea whats going wrong? > >>> > >>> > >>> 2011/11/5 Blair Murri > >>> > If two components must be always be installed/removed together, I > don't > see why they can't be in all the same features. > If one of the components depends on another but the dependency is not > mutual, you could make a hidden feature that also contains the > dependent > component and use a custom action to enable that feature based on the > depending component's action state. > -Blair > > > Date: Fri, 4 Nov 2011 13:10:57 +0100 > > From: steffen@googlemail.com > > To: wix-users@lists.sourceforge.net > > Subject: [WiX-users] Dependencies between components > > > > Hi, > > > > I would like to define that one component can't be installed without > >> the > > other, without them being in the same feature. Is there any > possibility > to > > define dependencies between components or component groups? > > > > or ist there any other approach to realise such a dependency? > > > > thanks in advance > > > > Steffen > > > >> > -- > > RSA(R) Conference 2012 > > Save $700 by Nov 18 > > Register now > > http://p.sf.net/sfu/rsa-sfdev2dev1 > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > >> > -- > RSA(R) Conference 2012 > Save $700 by Nov 18 > Register now > http://p.sf.net/sfu/rsa-sfdev2dev1 > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > >> > -- > >>> RSA(R) Conference 2012 > >>> Save $700 by Nov 18 > >>> Register now > >>> http://p.sf.net/sfu/rsa-sfdev2dev1 > >>> ___ > >>> WiX-users mailing list > >>> WiX-users@lists.sourceforge.net > >>> https://lists.sourceforge.net/lists/listinfo/wix-users > >>> > >> > >> > >> > -- > >> RSA(R) Conference 2012 > >> Save $700 by Nov 18 > >> Register now > >> http://p.sf.net/sfu/rsa-sfdev2dev1 > >> ___
[WiX-users] wix
wix If you are looking for financial independence look no further http://.todayl0newsi.com -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Dependencies between components
AFAIK you cannot do that with ComponentGroups. If you like a flat structure you can do something like this: ... This will install the "Binaries"-Feature when Debug or Binaries is selected. It's like a dependency of "Debug" to "Binaries". Regards Michael Am 08.11.2011 12:39, schrieb Steffen Henne: > That perhaps explains the strange behavior of the DependencyExtension :D > > Any possibibilty then to set one ComponentGroup as optional? > I'm thinking about having an ComponentGroup with Binaries and one with the > Program Debug Databases. Then the Debug dbs will be kind of addition to the > Binaries. > > Any other way except from defining the Debug dbs as Subfeature of the > Binaries like > > > > > > > greetings Steffen > > 2011/11/8 Michael Stoll > >> AFAIK the DependencyExtension is about dependencies between installer >> packages. >> >> I'm solving component dependencies with groups. Like this: >> >> ... >> ... >> >> >> >> >> >> >> >> >> >> >> So I'm only referencing groups in the feature and thus can add any >> dependency like any other component to that group. >> >> >> Regards Michael >> >> >> Am 08.11.2011 10:49, schrieb Steffen Henne: >>> Thanks for your answer. I actually think it's not necessary but we want >> to >>> try it out for the scenario the guy who creates our big main wxs file has >>> no idea about the dependencies between all the projects and we can define >>> them somerwhere else. >>> >>> I just found the DependencyExtension and tried to use it. Looks like >> this: >>> in Feature A: >>> >>> >>> >>> >>> >>> in Feature B: >>> >>> >>> >>> >>> >>> >>> >>> So B should be dependent of A right? >>> now if i build the installer and select only Feature B it says as >> expected >>> some dependencies are missing. >>> but if i now select feature A and B the same message pops up although all >>> dependencies are actually fulfilled. >>> >>> Any idea whats going wrong? >>> >>> >>> 2011/11/5 Blair Murri >>> If two components must be always be installed/removed together, I don't see why they can't be in all the same features. If one of the components depends on another but the dependency is not mutual, you could make a hidden feature that also contains the dependent component and use a custom action to enable that feature based on the depending component's action state. -Blair > Date: Fri, 4 Nov 2011 13:10:57 +0100 > From: steffen@googlemail.com > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] Dependencies between components > > Hi, > > I would like to define that one component can't be installed without >> the > other, without them being in the same feature. Is there any possibility to > define dependencies between components or component groups? > > or ist there any other approach to realise such a dependency? > > thanks in advance > > Steffen > >> -- > RSA(R) Conference 2012 > Save $700 by Nov 18 > Register now > http://p.sf.net/sfu/rsa-sfdev2dev1 > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users >> -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users >> -- >>> RSA(R) Conference 2012 >>> Save $700 by Nov 18 >>> Register now >>> http://p.sf.net/sfu/rsa-sfdev2dev1 >>> ___ >>> WiX-users mailing list >>> WiX-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/wix-users >>> >> >> >> -- >> RSA(R) Conference 2012 >> Save $700 by Nov 18 >> Register now >> http://p.sf.net/sfu/rsa-sfdev2dev1 >> ___ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> > -- > RSA(R) Conference 2012 > Save $700 by Nov 18 > Register now > http://p.sf.net/sfu/rsa-sfdev2dev1 > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- RSA(R) Confer
Re: [WiX-users] Dependencies between components
That perhaps explains the strange behavior of the DependencyExtension :D Any possibibilty then to set one ComponentGroup as optional? I'm thinking about having an ComponentGroup with Binaries and one with the Program Debug Databases. Then the Debug dbs will be kind of addition to the Binaries. Any other way except from defining the Debug dbs as Subfeature of the Binaries like greetings Steffen 2011/11/8 Michael Stoll > AFAIK the DependencyExtension is about dependencies between installer > packages. > > I'm solving component dependencies with groups. Like this: > > ... > ... > > > > > > > > > > > So I'm only referencing groups in the feature and thus can add any > dependency like any other component to that group. > > > Regards Michael > > > Am 08.11.2011 10:49, schrieb Steffen Henne: > > Thanks for your answer. I actually think it's not necessary but we want > to > > try it out for the scenario the guy who creates our big main wxs file has > > no idea about the dependencies between all the projects and we can define > > them somerwhere else. > > > > I just found the DependencyExtension and tried to use it. Looks like > this: > > > > in Feature A: > > > > > > > > > > > > in Feature B: > > > > > > > > > > > > > > > > So B should be dependent of A right? > > now if i build the installer and select only Feature B it says as > expected > > some dependencies are missing. > > but if i now select feature A and B the same message pops up although all > > dependencies are actually fulfilled. > > > > Any idea whats going wrong? > > > > > > 2011/11/5 Blair Murri > > > >> If two components must be always be installed/removed together, I don't > >> see why they can't be in all the same features. > >> If one of the components depends on another but the dependency is not > >> mutual, you could make a hidden feature that also contains the dependent > >> component and use a custom action to enable that feature based on the > >> depending component's action state. > >> -Blair > >> > >>> Date: Fri, 4 Nov 2011 13:10:57 +0100 > >>> From: steffen@googlemail.com > >>> To: wix-users@lists.sourceforge.net > >>> Subject: [WiX-users] Dependencies between components > >>> > >>> Hi, > >>> > >>> I would like to define that one component can't be installed without > the > >>> other, without them being in the same feature. Is there any possibility > >> to > >>> define dependencies between components or component groups? > >>> > >>> or ist there any other approach to realise such a dependency? > >>> > >>> thanks in advance > >>> > >>> Steffen > >>> > >> > -- > >>> RSA(R) Conference 2012 > >>> Save $700 by Nov 18 > >>> Register now > >>> http://p.sf.net/sfu/rsa-sfdev2dev1 > >>> ___ > >>> WiX-users mailing list > >>> WiX-users@lists.sourceforge.net > >>> https://lists.sourceforge.net/lists/listinfo/wix-users > >> > >> > -- > >> RSA(R) Conference 2012 > >> Save $700 by Nov 18 > >> Register now > >> http://p.sf.net/sfu/rsa-sfdev2dev1 > >> ___ > >> WiX-users mailing list > >> WiX-users@lists.sourceforge.net > >> https://lists.sourceforge.net/lists/listinfo/wix-users > >> > > > -- > > RSA(R) Conference 2012 > > Save $700 by Nov 18 > > Register now > > http://p.sf.net/sfu/rsa-sfdev2dev1 > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > > -- > RSA(R) Conference 2012 > Save $700 by Nov 18 > Register now > http://p.sf.net/sfu/rsa-sfdev2dev1 > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Strange behavior with wix 3.6 (wwansvc, VirtualBox)
Just tried uninstalling from control panel, without bootstrapper. Same problem. Here's the complete log: Error 1402. Could not open key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WwanSvc\Profiles. System error 5. Verify that you have sufficient access to that key, or contact your support personnel. === Logging stopped: 08.11.2011 12:00:49 === 1: 1101 2: C:\Config.Msi\2fcfc1.rbs 3: 3 1: 1712 Regards Michael Am 08.11.2011 09:10, schrieb Michael Stoll: > Hi, > > I've noticed a strange behavior using burn. And I have no idea, how to > analyse it. Here's what happend: > > Wix-Version: 3.6.2221 > Test-Environment: Windows 7 Professional x64 running inside of > VirtualBox 4.1.4 with Additions. > Installation-Package: Burn with 2 msi-packages (created with wix) and > some prerequisite exe packages > > I intended to test the installation package on the virtual test > platform. So I copied the package to the VM, installed it, found a > missing component and tried to uninstall. During uninstall an error > occured (Permission denied on > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\WwanSvc). The log > file of one msi package contains a similar message. > The first strange thing is, that the msi package does not contain this > registry key in the Registry table. > Then I rebooted the VM. But the system does not boot any more. After > "Windows is starting" there's only a black screen, even when booting in > safe mode. > > I looking forward to any helpful advise. > > Regards > Michael > > > -- > RSA(R) Conference 2012 > Save $700 by Nov 18 > Register now > http://p.sf.net/sfu/rsa-sfdev2dev1 > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Windows Installer 5.0 SDK Download Location
One thing to keep in mind is that if you're targeting Windows Installer 5.0 it's only available on Windows 7 & Server 2008 R2. 4.5 is the latest available redistributable for earlier Windows versions. Palbinder Sandher Software Platform Engineer 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: Jamie Hankins [mailto:jamie.hank...@qsm.com] Sent: 07 November 2011 18:47 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Windows Installer 5.0 SDK Download Location Okay, I see that the platform SDK installs it in the bin directory. Since there's nothing in the installer UI that specifically mentions the Installer SDK, I didn't think it was there. I'm sorry for the OT message. Jamie From: Jamie Hankins Sent: Monday, 07 November, 2011 13:16 To: 'wix-users@lists.sourceforge.net' Subject: Windows Installer 5.0 SDK Download Location I'm sorry this is off-topic, but I'm having a hard time finding a download location for the latest Windows Installer SDK. All of the links on Microsoft.com are wrong. There is a lot of info, but no actual download location. Can anyone give me a link or at least an explanation of why this isn't findable? Thanks, Jamie -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Dependencies between components
AFAIK the DependencyExtension is about dependencies between installer packages. I'm solving component dependencies with groups. Like this: ... ... So I'm only referencing groups in the feature and thus can add any dependency like any other component to that group. Regards Michael Am 08.11.2011 10:49, schrieb Steffen Henne: > Thanks for your answer. I actually think it's not necessary but we want to > try it out for the scenario the guy who creates our big main wxs file has > no idea about the dependencies between all the projects and we can define > them somerwhere else. > > I just found the DependencyExtension and tried to use it. Looks like this: > > in Feature A: > > > > > > in Feature B: > > > > > > > > So B should be dependent of A right? > now if i build the installer and select only Feature B it says as expected > some dependencies are missing. > but if i now select feature A and B the same message pops up although all > dependencies are actually fulfilled. > > Any idea whats going wrong? > > > 2011/11/5 Blair Murri > >> If two components must be always be installed/removed together, I don't >> see why they can't be in all the same features. >> If one of the components depends on another but the dependency is not >> mutual, you could make a hidden feature that also contains the dependent >> component and use a custom action to enable that feature based on the >> depending component's action state. >> -Blair >> >>> Date: Fri, 4 Nov 2011 13:10:57 +0100 >>> From: steffen@googlemail.com >>> To: wix-users@lists.sourceforge.net >>> Subject: [WiX-users] Dependencies between components >>> >>> Hi, >>> >>> I would like to define that one component can't be installed without the >>> other, without them being in the same feature. Is there any possibility >> to >>> define dependencies between components or component groups? >>> >>> or ist there any other approach to realise such a dependency? >>> >>> thanks in advance >>> >>> Steffen >>> >> -- >>> RSA(R) Conference 2012 >>> Save $700 by Nov 18 >>> Register now >>> http://p.sf.net/sfu/rsa-sfdev2dev1 >>> ___ >>> WiX-users mailing list >>> WiX-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/wix-users >> >> -- >> RSA(R) Conference 2012 >> Save $700 by Nov 18 >> Register now >> http://p.sf.net/sfu/rsa-sfdev2dev1 >> ___ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> > -- > RSA(R) Conference 2012 > Save $700 by Nov 18 > Register now > http://p.sf.net/sfu/rsa-sfdev2dev1 > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix or MSI bug ?
Phil the bug is that the path returned by FileSearch is of the format C:\Directory\Filename.ext\ The trailing slash after the filename makes the path returned by FileSearch all but useless unless you use a custom action to remove it first, in which case you may as well just use a custom action to return the correct value in the first place. Palbinder Sandher Software Platform Engineer 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: Wilson, Phil [mailto:phil.wil...@invensys.com] Sent: 07 November 2011 17:58 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Wix or MSI bug ? And most Windows Installer paths end with a \ too, in the path properties. Phil Wilson -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Monday, November 07, 2011 6:45 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Wix or MSI bug ? Old bug with FileSearch which has been "closed" but never actually fixed as far as I can see -> http://sourceforge.net/tracker/?func=detail&atid=642714&aid=1648267&group_id=105970 & http://sourceforge.net/tracker/index.php?func=detail&aid=1273447&group_id=105970&atid=642714 Palbinder Sandher Software Platform Engineer 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: Nicolas Penin [mailto:n.pe...@happly.fr] Sent: 07 November 2011 09:02 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Wix or MSI bug ? Dear all, I believe this is a bug in wix 3.6, but not sure... If I do the following : I have the appropriate path, except it is terminating with a \ If I change the Type of RegistrySearch to file, the content of SQLCMDPATH is 'C:\' Any idea ? Regards, Nicolas Penin -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023). For a list of European legal entities within the Invensys Group, please go to http://www.invensys.com/en/legal/default.aspx. You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail recept...@invensys.com. This e-mail and any attachments thereto may be subject to the terms of any agreements between Invensys (and/or its subsidiaries and affiliates) and the recipient (and/or its subsidiaries and affiliates). -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Dependencies between components
Thanks for your answer. I actually think it's not necessary but we want to try it out for the scenario the guy who creates our big main wxs file has no idea about the dependencies between all the projects and we can define them somerwhere else. I just found the DependencyExtension and tried to use it. Looks like this: in Feature A: in Feature B: So B should be dependent of A right? now if i build the installer and select only Feature B it says as expected some dependencies are missing. but if i now select feature A and B the same message pops up although all dependencies are actually fulfilled. Any idea whats going wrong? 2011/11/5 Blair Murri > > If two components must be always be installed/removed together, I don't > see why they can't be in all the same features. > If one of the components depends on another but the dependency is not > mutual, you could make a hidden feature that also contains the dependent > component and use a custom action to enable that feature based on the > depending component's action state. > -Blair > > > Date: Fri, 4 Nov 2011 13:10:57 +0100 > > From: steffen@googlemail.com > > To: wix-users@lists.sourceforge.net > > Subject: [WiX-users] Dependencies between components > > > > Hi, > > > > I would like to define that one component can't be installed without the > > other, without them being in the same feature. Is there any possibility > to > > define dependencies between components or component groups? > > > > or ist there any other approach to realise such a dependency? > > > > thanks in advance > > > > Steffen > > > -- > > RSA(R) Conference 2012 > > Save $700 by Nov 18 > > Register now > > http://p.sf.net/sfu/rsa-sfdev2dev1 > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > -- > RSA(R) Conference 2012 > Save $700 by Nov 18 > Register now > http://p.sf.net/sfu/rsa-sfdev2dev1 > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Fragments and Patch generation
There's not enough information there. Can you post the original and updated source code ? Possibly the patch wxs too. -Original Message- From: justin hull [mailto:justin.h...@assetpoint.com] Sent: 07 November 2011 22:19 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Fragments and Patch generation I am trying to create a "patch" install (.msp). It has been a learning struggle, but I got to the point where the msp install updates some files (if I use an 'a' flag on reinstallmode). However, in the original wix project I use paraffin to create a fragment for a database update component. While that works for the full install, the files that are from the fragment are not updated when I run the msp. I use pyro to create the diff.wixmst file and I see the database files in there. I get no errors when I create the msp, but the log file for the update shows that no database files are updated. Is there something about fragments and patchs taht I am missing? I can try to manually build the component in the main project, but this is a multi-folder, many file structure that I would prefer to not do by hand. Any help would be greatly appreciated for I have been at this for a few days. I'll be happy to provide any information requested. Thanks -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Fragments-and-P atch-generation-tp6972320p6972320.html Sent from the wix-users mailing list archive at Nabble.com. - - RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ 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. -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Advanced Wix based installer
Hi, It's hard to answer without your wxs, but for the WixUI_Mode, I would say you need to make a PropertyRef instead a Property. -Message d'origine- De : Neville Lewis [mailto:neville.le...@gmail.com] Envoyé : mardi 8 novembre 2011 10:10 À : wix-users@lists.sourceforge.net Objet : [WiX-users] Advanced Wix based installer Hello everyone, I need to create a multi-language installer for a windows application. I need help in creating an installer using WiX, which does the following during installation: 1. Prompt user for language selection. 2. Proceed with installation in selected language. 3. Skip the license agreement window. 4. Prompt to install for self or all users on the pc. 5. Prompt for feature list to install. 6. Prompt for folder to install into with default folder already displayed. Creates a folder if it doesn't already exist. 7. Install application binaries in selected language to selected path. 8. Run a custom application immediately after clicking finish. even one step before finish would do. 9. While un-installing, the language should be the language it was installed in. Of the list above I have only managed to get point 3 & 5 to work, with point 6 partially; the default folder is not what I want it to be. It goes by default to program files. I seem to be running into these types of errors very often when building the project in Visual studio 2008: "The primary key '..' is duplicated in table 'ControlEvent' " "The primary key 'WixUI_Mode' is duplicated in table 'Property'. " This error below I get when I change the location settings on the pc and I attempt to run the .msi file. "Error applying transforms. Verify that the specified transforms paths are valid." Any sample script for getting the points I have not been able to accomplish as mentioned above? Also some tips on what to do when I run into the transforms errors on a generated MSI file. What changes do I need to make? What is the cause of the problem? Thanks for your time. -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Advanced Wix based installer
Hello everyone, I need to create a multi-language installer for a windows application. I need help in creating an installer using WiX, which does the following during installation: 1. Prompt user for language selection. 2. Proceed with installation in selected language. 3. Skip the license agreement window. 4. Prompt to install for self or all users on the pc. 5. Prompt for feature list to install. 6. Prompt for folder to install into with default folder already displayed. Creates a folder if it doesn't already exist. 7. Install application binaries in selected language to selected path. 8. Run a custom application immediately after clicking finish. even one step before finish would do. 9. While un-installing, the language should be the language it was installed in. Of the list above I have only managed to get point 3 & 5 to work, with point 6 partially; the default folder is not what I want it to be. It goes by default to program files. I seem to be running into these types of errors very often when building the project in Visual studio 2008: "The primary key '..' is duplicated in table 'ControlEvent' " "The primary key 'WixUI_Mode' is duplicated in table 'Property'. " This error below I get when I change the location settings on the pc and I attempt to run the .msi file. "Error applying transforms. Verify that the specified transforms paths are valid." Any sample script for getting the points I have not been able to accomplish as mentioned above? Also some tips on what to do when I run into the transforms errors on a generated MSI file. What changes do I need to make? What is the cause of the problem? Thanks for your time. -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Strange behavior with wix 3.6 (wwansvc, VirtualBox)
Hi, I've noticed a strange behavior using burn. And I have no idea, how to analyse it. Here's what happend: Wix-Version: 3.6.2221 Test-Environment: Windows 7 Professional x64 running inside of VirtualBox 4.1.4 with Additions. Installation-Package: Burn with 2 msi-packages (created with wix) and some prerequisite exe packages I intended to test the installation package on the virtual test platform. So I copied the package to the VM, installed it, found a missing component and tried to uninstall. During uninstall an error occured (Permission denied on HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\WwanSvc). The log file of one msi package contains a similar message. The first strange thing is, that the msi package does not contain this registry key in the Registry table. Then I rebooted the VM. But the system does not boot any more. After "Windows is starting" there's only a black screen, even when booting in safe mode. I looking forward to any helpful advise. Regards Michael -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
