> From: wix-users-requ...@lists.sourceforge.net
> Subject: WiX-users Digest, Vol 41, Issue 8
> To: wix-users@lists.sourceforge.net
> Date: Fri, 2 Oct 2009 17:55:54 +0000
>
> Send WiX-users mailing list submissions to
> wix-users@lists.sourceforge.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/wix-users
> or, via email, send a message with subject or body 'help' to
> wix-users-requ...@lists.sourceforge.net
>
> You can reach the person managing the list at
> wix-users-ow...@lists.sourceforge.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of WiX-users digest..."
>
>
> Today's Topics:
>
> 1. Re: CustomAction : Enumerating SQLServer Instancesacrossthe
> network using SQLDMO (Dominique Louis)
> 2. How to find the installed path for update
> (Jiang, Chunyan (GE Healthcare))
> 3. Re: How to find the installed path for update (Blair)
> 4. Re: Problem with storing checkbox state (Blair)
> 5. Re: Problem with storing checkbox state (Blair)
> 6. Re: How to find the installed path for update (Wilson, Phil)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 2 Oct 2009 14:22:42 +0100
> From: "Dominique Louis" <dominique.lo...@amxeurope.com>
> Subject: Re: [WiX-users] CustomAction : Enumerating SQLServer
> Instancesacrossthe network using SQLDMO
> To: "General discussion for Windows Installer XML toolset."
> <wix-users@lists.sourceforge.net>
> Message-ID:
> <488f6a8c5a9db84fbb082d732f1bbdef02196...@exchange01.amxuk.local>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi Thomas,
> Great to see the WiXRepo is up and running so quickly.
>
> I'm not sure how organized you can make things on codeplex, as I've
> never used it, but maybe CustomActions could be grouped per programming
> language. So a sub-dir for VB Script and another for C/C++ and C# etc.
>
> How can developers submit things to the project? Do you have to register
> to be able to be part of the project?
>
> A more portable solution to this SQLDMO code below would be to use SMO,
> as that is supported on SQLServer 2005 and 2008, but VB Script cannot
> call static methods, so it seems only a C/C+/C# etc solution would work
> for that.
>
> Dominique.
>
> -----Original Message-----
> From: Thomas Due [mailto:thomas....@scanvaegt.dk]
> Sent: 02 October 2009 06:47
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] CustomAction : Enumerating SQLServer
> Instancesacrossthe network using SQLDMO
>
> This would be perfect for http://wixrepo.codeplex.com/
>
> Also: Looks good, looking forward to playing around with it, although
> the company I work for, will have to support 2008 as well in the near
> future.
>
> /Thomas
>
> -----Original Message-----
> From: Dominique Louis [mailto:dominique.lo...@amxeurope.com]
> Sent: 1. oktober 2009 18:16
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] CustomAction : Enumerating SQLServer Instances
> acrossthe network using SQLDMO
>
> Hi all,
> I couldn't find all this code in one place so I thought this list
> might be a good place to archive it.
>
>
> Set sqlApp = CreateObject("SQLDMO.Application")
>
> If ( Err.Number <> 0 ) Then
> wscript.echo "SQLDMO.Application Not found. Error : " &
> Err.Number
> wscript.Quit -1
> End If
>
> Set sqlServer2 = CreateObject("SQLDMO.SQLServer2")
>
> If ( Err.Number <> 0 ) Then
> wscript.echo "SQLDMO.SQLServer2 Not found. Error : " &
> Err.Number
> wscript.Quit -1
> End If
>
> Set serverList = sqlApp.ListAvailableSQLServers
>
> numServers = serverList.Count
>
> Dim x, y
>
> For x = 1 To numServers
>
> Set instanceList = sqlServer2.ListInstalledInstances(
> serverList(x) )
>
> if Not ( instanceList is Nothing ) Then
>
> numInstances = instanceList.Count
>
> wscript.echo serverList(x)
> For y = 1 To numInstances
> wscript.echo " " & instanceList(y)
> Next
> End IF
> Next
>
> Set sqlServer2 = Nothing
> Set sqlApp = Nothing
>
>
> Note SQLDMO only works with SQLServer 2005 and below and is not
> installed by default on SQLServer 2008 onwards
>
>
> Hope this helps someone.
>
>
> DOMINIQUE LOUIS | IS DEVELOPER, AMX DIGITAL MEDIA GROUP
> AMX UK| 6TH FLOOR SALISBURY HOUSE,| LONDON WALL | LONDON | EC2M 5QQ
> www.amx.com
> AMX
>
> AMX UK
> Auster Road
> Clifton Moor
> York, North Yorkshire
> United Kingdom
> YO30 4GD
>
> +44 (0) 1904 343100 office
> +44 (0) 1904 343101 fax
>
> AMX South
> 6th Floor Salisbury House
> London Wall
> London
> United Kingdom
> EC2M 5QQ
>
> +44 (0) 2076 529450 office
> +44 (0) 8701 991661 fax
>
> AMX Belgium
> Boerenkrijglaan, 96a
> B-2260
> Westerlo
> Belgium
>
>
> + 32 (0) 1454 2763 office
> + 32 (0) 1454 2766 fax
>
> ######################################################################
> Attention:
> This e-mail message is privileged and confidential. If you are not the
> intended recipient please delete the message and notify the sender.
> Any views or opinions presented are solely those of the author.
>
> This email was scanned and cleared by NetIQ MailMarshal.
> ######################################################################
>
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 2 Oct 2009 15:25:54 +0200
> From: "Jiang, Chunyan (GE Healthcare)" <chunyan.ji...@ge.com>
> Subject: [WiX-users] How to find the installed path for update
> To: "General discussion for Windows Installer XML toolset."
> <wix-users@lists.sourceforge.net>
> Message-ID:
> <aac1d9c256968940b76a12c6e922f0ed239...@budmlvem08.e2k.ad.ge.com>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi Wix-users,
>
> I have developed a wix installer. It is an updatable installation
> package. For the path, I set the default path as
>
> <Directory Id="TARGETDIR" Name="SourceDir">
>
> <Directory Id="APPLICATIONFOLDER" Name="ViewPoint6">
>
>
>
> It will show "D:\ViewPoint6" as the default in InstallDirDlg.wxs:
>
> <Control Id="Folder" Type="PathEdit" X="20" Y="100" Width="320"
> Height="18" Property="WIXUI_INSTALLDIR" Indirect="yes" />
>
> <Property Id="WIXUI_INSTALLDIR" Value="APPLICATIONFOLDER" />
>
>
>
> However, if I installed the software in the other path, like
> d:\testinatll for the first time. When there is new version avalable, I
> want to update it. The InstallDirDlg still shows the path as
> "D:\ViewPoint6", instead of "d:\testinatll".
>
> How can I get the path for the update installation and set it to
> InstallDirDlg? Probably, I need to have to dialogs, one for new
> installation, defaut path is "D:\ViewPoint6", the other one is update
> dialog, the path should be set as installed path.
>
>
>
> Best regards
>
> Chunyan
>
>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 2 Oct 2009 06:49:31 -0700
> From: "Blair" <os...@live.com>
> Subject: Re: [WiX-users] How to find the installed path for update
> To: "'General discussion for Windows Installer XML toolset.'"
> <wix-users@lists.sourceforge.net>
> Message-ID: <bay122-ds3e8b8d952f363b272da68cd...@phx.gbl>
> Content-Type: text/plain; charset="us-ascii"
>
> What people often do is store APPLICATIONFOLDER to a registry value, and use
> a RegistrySearch to populate a secure property by the same name with it.
>
> <Property Id="APPLICATIONFOLDER" Secure="yes">
> <RegistrySearch Id="ApplicationFolderSearch" Type="raw" Root="..."
> Key="..." Name="InstallationPath"/>
> </Property>
>
> And inside of one of your components (or in a new component created for this
> purpose)
> <RegistryValue Id="ApplicationFolder" Root="..." Key="..."
> Name="InstallationPath" Type="string" Value="[APPLICATIONFOLDER]" />
>
> If the registry key/value doesn't exist, the current logic is used to
> calculate the path. If the value does exist, the current logic is ignored
> and that path shows up in the UI as well as gets used for installation.
>
> -----Original Message-----
> From: Jiang, Chunyan (GE Healthcare) [mailto:chunyan.ji...@ge.com]
> Sent: Friday, October 02, 2009 6:26 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] How to find the installed path for update
>
> Hi Wix-users,
>
> I have developed a wix installer. It is an updatable installation
> package. For the path, I set the default path as
>
> <Directory Id="TARGETDIR" Name="SourceDir">
>
> <Directory Id="APPLICATIONFOLDER" Name="ViewPoint6">
>
>
>
> It will show "D:\ViewPoint6" as the default in InstallDirDlg.wxs:
>
> <Control Id="Folder" Type="PathEdit" X="20" Y="100" Width="320"
> Height="18" Property="WIXUI_INSTALLDIR" Indirect="yes" />
>
> <Property Id="WIXUI_INSTALLDIR" Value="APPLICATIONFOLDER" />
>
>
>
> However, if I installed the software in the other path, like
> d:\testinatll for the first time. When there is new version avalable, I
> want to update it. The InstallDirDlg still shows the path as
> "D:\ViewPoint6", instead of "d:\testinatll".
>
> How can I get the path for the update installation and set it to
> InstallDirDlg? Probably, I need to have to dialogs, one for new
> installation, defaut path is "D:\ViewPoint6", the other one is update
> dialog, the path should be set as installed path.
>
>
>
> Best regards
>
> Chunyan
>
> ----------------------------------------------------------------------------
> --
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Fri, 2 Oct 2009 06:34:53 -0700
> From: "Blair" <os...@live.com>
> Subject: Re: [WiX-users] Problem with storing checkbox state
> To: "'General discussion for Windows Installer XML toolset.'"
> <wix-users@lists.sourceforge.net>
> Message-ID: <bay122-ds7c634417fe8cd6733e340cd...@phx.gbl>
> Content-Type: text/plain; charset="us-ascii"
>
> Remove the "<Property Id="ADDITIONAL_PARAMS" Secure="yes" Value="1" >" line.
>
> Add:
> <Property Id="ADDITIONAL_PARAMS" Secure="yes" />
> <CustomAction Id="SetADDITIONAL_PARAMS" Property="ADDITIONAL_PARAMS"
> Value="1" Execute="firstSequence" />
>
> <InstallUISequence>
> <Custom Action="SetADDITIONAL_PARAMS" Before="AppSearch">NOT
> Installed AND NOT OLDERVERSIONDETECTED</Custom>
> </InstallUISequence>
> <InstallExecuteSequence>
> <Custom Action="SetADDITIONAL_PARAMS" Before="AppSearch">NOT
> Installed AND NOT OLDERVERSIONDETECTED</Custom>
> </InstallExecuteSequence>
>
> What this will do is keep ADDITIONAL_PARAMS as a secure property, but it
> won't get a "default" value unless this is a new installation (or major
> upgrade). Change OLDERVERSIONDETECTED to be whatever you have in your
> Upgrade table for removing older versions.
>
> -----Original Message-----
> From: Igor Lemsky [mailto:igor.lem...@gmail.com]
> Sent: Friday, October 02, 2009 1:11 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] Problem with storing checkbox state
>
> In my installer I have checkbox "Add also addiotional parameters" with
> property ADDITIONAL_PARAMS. Its value "1" if checkbox is checked, and no
> value if unchecked.
> Worked perfectly, but there are problems. I store property to the registry,
> and use regsearch to restore it during upgrade or reinstall.
> <RegistryValue Id="ADDITIONAL_PARAMSstore" Root="HKLM"
> Key="Software\Company\Installation" Name="ADDITIONAL_PARAMS" Type="string"
> Value="[ADDITIONAL_PARAMS]" />
> .....
>
> <Property Id="ADDITIONAL_PARAMS" Secure="yes" Value="1" >
> <RegistrySearch Id="ADDITIONAL_PARAMS_RS" Type="raw" Root="HKLM"
> Key="Software\Company\Installation" Name="ADDITIONAL_PARAMS" />
> </Property>
>
> Problem if checkbox was unchecked during first installation. In registry we
> see key value of Software\Company\Installation\ADDITIONAL_PARAMS is null. It
> is ok: the property value in installer is also null and it is right.
> But during reinstall the checkbox become checked! Installer ignored that
> ADDITIONAL_PARAMS = null! May be it looks into registry, find no value and
> set default value from Property Value attribute?
> if I delete this attribute ( <Property Id="ADDITIONAL_PARAMS"
> Secure="yes">) then it correctly restored checkbox value (property value)
> from registry, but then during first install this checkbox become unchecked
> for default! But I need it to be checked for default. What can I do?
> ----------------------------------------------------------------------------
> --
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
>
> ------------------------------
>
> Message: 5
> Date: Fri, 2 Oct 2009 07:31:51 -0700
> From: "Blair" <os...@live.com>
> Subject: Re: [WiX-users] Problem with storing checkbox state
> To: "'General discussion for Windows Installer XML toolset.'"
> <wix-users@lists.sourceforge.net>
> Message-ID: <bay122-ds664bdbc5a8562b390363bcd...@phx.gbl>
> Content-Type: text/plain; charset="us-ascii"
>
> Amend that. Remove the Value="1" part, not replace the entire line.
>
> -----Original Message-----
> From: Blair [mailto:os...@live.com]
> Sent: Friday, October 02, 2009 6:35 AM
> To: 'General discussion for Windows Installer XML toolset.'
> Subject: Re: [WiX-users] Problem with storing checkbox state
>
> Remove the "<Property Id="ADDITIONAL_PARAMS" Secure="yes" Value="1" >" line.
>
> Add:
> <Property Id="ADDITIONAL_PARAMS" Secure="yes" />
> <CustomAction Id="SetADDITIONAL_PARAMS" Property="ADDITIONAL_PARAMS"
> Value="1" Execute="firstSequence" />
>
> <InstallUISequence>
> <Custom Action="SetADDITIONAL_PARAMS" Before="AppSearch">NOT
> Installed AND NOT OLDERVERSIONDETECTED</Custom>
> </InstallUISequence>
> <InstallExecuteSequence>
> <Custom Action="SetADDITIONAL_PARAMS" Before="AppSearch">NOT
> Installed AND NOT OLDERVERSIONDETECTED</Custom>
> </InstallExecuteSequence>
>
> What this will do is keep ADDITIONAL_PARAMS as a secure property, but it
> won't get a "default" value unless this is a new installation (or major
> upgrade). Change OLDERVERSIONDETECTED to be whatever you have in your
> Upgrade table for removing older versions.
>
> -----Original Message-----
> From: Igor Lemsky [mailto:igor.lem...@gmail.com]
> Sent: Friday, October 02, 2009 1:11 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] Problem with storing checkbox state
>
> In my installer I have checkbox "Add also addiotional parameters" with
> property ADDITIONAL_PARAMS. Its value "1" if checkbox is checked, and no
> value if unchecked.
> Worked perfectly, but there are problems. I store property to the registry,
> and use regsearch to restore it during upgrade or reinstall.
> <RegistryValue Id="ADDITIONAL_PARAMSstore" Root="HKLM"
> Key="Software\Company\Installation" Name="ADDITIONAL_PARAMS" Type="string"
> Value="[ADDITIONAL_PARAMS]" />
> .....
>
> <Property Id="ADDITIONAL_PARAMS" Secure="yes" Value="1" >
> <RegistrySearch Id="ADDITIONAL_PARAMS_RS" Type="raw" Root="HKLM"
> Key="Software\Company\Installation" Name="ADDITIONAL_PARAMS" />
> </Property>
>
> Problem if checkbox was unchecked during first installation. In registry we
> see key value of Software\Company\Installation\ADDITIONAL_PARAMS is null. It
> is ok: the property value in installer is also null and it is right.
> But during reinstall the checkbox become checked! Installer ignored that
> ADDITIONAL_PARAMS = null! May be it looks into registry, find no value and
> set default value from Property Value attribute?
> if I delete this attribute ( <Property Id="ADDITIONAL_PARAMS"
> Secure="yes">) then it correctly restored checkbox value (property value)
> from registry, but then during first install this checkbox become unchecked
> for default! But I need it to be checked for default. What can I do?
> ----------------------------------------------------------------------------
> --
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
> ----------------------------------------------------------------------------
> --
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
>
> ------------------------------
>
> Message: 6
> Date: Fri, 2 Oct 2009 09:40:11 -0700
> From: "Wilson, Phil" <phil.wil...@wonderware.com>
> Subject: Re: [WiX-users] How to find the installed path for update
> To: General discussion for Windows Installer XML toolset.
> <wix-users@lists.sourceforge.net>
> Message-ID:
> <5c889913ff236e4190093af280ab4ec40186a04...@wwlkfmail1.wonderware.com>
> Content-Type: text/plain; charset="us-ascii"
>
> If "updatable installation" is referring to the fact that you'll be doing a
> major upgrade with Upgrade elements, why do you need this? An upgrade is a
> new install that users can install to whatever path they want. It so happens
> that an upgrade can also remove prior versions, but it seems unusual to imply
> that an upgrade needs to go into exactly the same location as the previous
> product.
>
> Phil Wilson
>
> -----Original Message-----
> From: Jiang, Chunyan (GE Healthcare) [mailto:chunyan.ji...@ge.com]
> Sent: Friday, October 02, 2009 6:26 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] How to find the installed path for update
>
> Hi Wix-users,
>
> I have developed a wix installer. It is an updatable installation
> package. For the path, I set the default path as
>
> <Directory Id="TARGETDIR" Name="SourceDir">
>
> <Directory Id="APPLICATIONFOLDER" Name="ViewPoint6">
>
>
>
> It will show "D:\ViewPoint6" as the default in InstallDirDlg.wxs:
>
> <Control Id="Folder" Type="PathEdit" X="20" Y="100" Width="320"
> Height="18" Property="WIXUI_INSTALLDIR" Indirect="yes" />
>
> <Property Id="WIXUI_INSTALLDIR" Value="APPLICATIONFOLDER" />
>
>
>
> However, if I installed the software in the other path, like
> d:\testinatll for the first time. When there is new version avalable, I
> want to update it. The InstallDirDlg still shows the path as
> "D:\ViewPoint6", instead of "d:\testinatll".
>
> How can I get the path for the update installation and set it to
> InstallDirDlg? Probably, I need to have to dialogs, one for new
> installation, defaut path is "D:\ViewPoint6", the other one is update
> dialog, the path should be set as installed path.
>
>
>
> Best regards
>
> Chunyan
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
>
>
> ------------------------------
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
>
> ------------------------------
>
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
> End of WiX-users Digest, Vol 41, Issue 8
> ****************************************
_________________________________________________________________
Windows Live: Keep your friends up to date with what you do online.
http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_1:092010
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
