Sent from my iPhone

> On Apr 28, 2015, at 10:00 PM, wix-users-requ...@lists.sourceforge.net wrote:
> 
> 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: Reboot and ReallySuppress (Phil Wilson)
>   2. Re: Detect condition for a Burn Package ? (Marco Tognacci)
>   3. Re: Detect condition for a Burn Package ?
>      (keith.doug...@statcan.gc.ca)
>   4. Re: Reboot and ReallySuppress (Henri Hein)
>   5. Re: Detect condition for a Burn Package ? (Phill Hogland)
>   6. Unable to access HTTPS after installing ssl certificate    to
>      website (wixtester)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Tue, 28 Apr 2015 14:28:46 -0700
> From: Phil Wilson <phildgwil...@gmail.com>
> Subject: Re: [WiX-users] Reboot and ReallySuppress
> To: "General discussion about the WiX toolset."
>    <wix-users@lists.sourceforge.net>
> Message-ID:
>    <caczvprzyorwb2o9dxss_fklk89sdkxe6hsxgneyvfk-bga7...@mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
> 
> You should probably post a link to the entire log for others to see.
> For example, I don't know if you've looked at the possibility that a
> custom action is resetting the REBOOT property somewhere.
> ---------------
> Phil Wilson
> 
> 
>> On Tue, Apr 28, 2015 at 1:15 PM, Henri Hein <he...@thinair.com> wrote:
>> My message went out prematurely, but I think the question is clear enough.
>> Does anyone have any ideas why the reboot might be happening, and how I can
>> really suppress it?  There wasn't anything immediately obvious before the
>> last "Decrementing counter" log line.
>> 
>> Thanks,
>>  - Henri
>> 
>> 
>>> On Tue, Apr 28, 2015 at 1:13 PM, Henri Hein <he...@thinair.com> wrote:
>>> 
>>> 
>>> My installer keeps prompting for a reboot, and I am trying to find out
>>> why.  I set the Reboot property to 'ReallySuppress' with the following XML:
>>> 
>>> <Property Id="REBOOT" Value="ReallySuppress" />
>>> 
>>> I have run the installer with verbose log, trying to look for the clues
>>> listed on this helpful blog post:
>>> 
>>> 
>>> http://blogs.msdn.com/b/windows_installer_team/archive/2005/09/19/470980.aspx
>>> 
>>> However, none of the tips pointed me to a reason for the reboot.  I do not
>>> see "ReplacedInUseFiles" property set or Info 1603 or 1903 messages.  My
>>> installer does update an Explorer plugin, but the Restart Manager
>>> successfully shuts down Explorer.exe and updates the DLL.  I also run a
>>> custom action, but it's unclear if that triggers the reboot.
>>> 
>>> I see the following lines in the log file:
>>> 
>>> MSI (c) (F8:08) [18:33:11:278]: Incrementing counter to disable shutdown.
>>> Counter after increment: 0
>>> 
>>> MSI (c) (F8:E0) [18:34:33:767]: Disallowing shutdown.  Shutdown counter: 0
>>> MSI (s) (04:30) [18:34:48:408]: Incrementing counter to disable shutdown.
>>> Counter after increment: 0
>>> MSI (s) (04:30) [18:34:48:439]: Decrementing counter to disable shutdown.
>>> If counter >= 0, shutdown will be denied.  Counter after decrement: -1
>>> 
>>> These are not consecutive, just the lines related to the Shutdown property.
>> ------------------------------------------------------------------------------
>> One dashboard for servers and applications across Physical-Virtual-Cloud
>> Widest out-of-the-box monitoring support with 50+ applications
>> Performance metrics, stats and reports that give you Actionable Insights
>> Deep dive visibility with transaction tracing using APM Insight.
>> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
>> _______________________________________________
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Tue, 28 Apr 2015 23:47:56 +0200
> From: Marco Tognacci <mark...@live.it>
> Subject: Re: [WiX-users] Detect condition for a Burn Package ?
> To: WiX - users <wix-users@lists.sourceforge.net>
> Message-ID: <dub120-w5074225836737afb1e5edff8...@phx.gbl>
> Content-Type: text/plain; charset="iso-8859-1"
> 
> So at this moment, there isn't a way for doing this?
> 
> 
>> From: r...@firegiant.com
>> To: wix-users@lists.sourceforge.net
>> Date: Tue, 28 Apr 2015 21:18:56 +0000
>> Subject: Re: [WiX-users] Detect condition for a Burn Package ?
>> 
>> IIRC, there is a feature request open for that.
>> 
>> _____________________________________________________________
>> Short replies here. Complete answers over there: http://www.firegiant.com/
>> 
>> 
>> -----Original Message-----
>> From: Marco Tognacci [mailto:mark...@live.it] 
>> Sent: Tuesday, April 28, 2015 1:55 PM
>> To: WiX - users
>> Subject: [WiX-users] Detect condition for a Burn Package ?
>> 
>> I have a Burn package (setup1.exe) that have an UpgradeCode={GUID}I have 
>> used this exe package inside another Burn setup (setup2.exe), in this 
>> package I need to  get the DetectCondition for the firt package (setup1.exe) 
>> is there any way to get this condition?
>> <util:ProductSearch UpgradeCode="XXXXXXXX-XXXX-XXXX-XXXXXXXXXXXXXXXXX" 
>> Variable="Setup1_Installed" Result="state"/> I have tried this but it report 
>> Setup1_Installed = 2 as not installed even if it is really installed,I have 
>> read that this ProductSearch is only for the msi package, is right? 
>> I have search on the registry the UpgradeCode and it appear in the Uninstall 
>> section in a variable BundleUpgradeCode, But I don't know how to check it as 
>> it is under a GUID code that is auto genrated during setup of the setup1.exe 
>> Any way for doing this?Thanks
>> 
>> 
>> ------------------------------------------------------------------------------
>> One dashboard for servers and applications across Physical-Virtual-Cloud 
>> Widest out-of-the-box monitoring support with 50+ applications
>> Performance metrics, stats and reports that give you Actionable Insights
>> Deep dive visibility with transaction tracing using APM Insight.
>> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
>> _______________________________________________
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>                         
> 
> ------------------------------
> 
> Message: 3
> Date: Tue, 28 Apr 2015 18:04:14 -0400
> From: <keith.doug...@statcan.gc.ca>
> Subject: Re: [WiX-users] Detect condition for a Burn Package ?
> To: <wix-users@lists.sourceforge.net>
> Message-ID:
>    <101c22438f6f2d48bc37dc88b12c4fd5017cefa01...@f6stcemmba03.statcan.ca>
> Content-Type: text/plain; charset="iso-8859-1"
> 
> If I understand correctly this is what I asked about many moons ago. What I 
> was told at the time as a possibility - which we implemented - is that one 
> can "unbundle" and then parse the XML from one of the files:
> 
> Dim b As New Microsoft.Tools.WindowsInstallerXml.Unbinder
> Dim out As Microsoft.Tools.WindowsInstallerXml.Output = b.Unbind(fileName, 
> Microsoft.Tools.WindowsInstallerXml.OutputType.Bundle, scratchDirectory)
> uc = 
> ExeTools.GetUpgradeCodeByPath(String.Format(Globalization.CultureInfo.InvariantCulture(),
>  "{0}ux\BootStrapperApplicationData.xml", scratchDirectory))
> 
> where scratchdirectory is where you want to unbundle 
> and GetUpgradeCodeByPath is (error handling etc, omitted):
> 
>        Dim uc As String = String.Empty
>        Dim tempXml As New XmlDocument
>        tempXml.Load(applicationDataFile)
>        If tempXml.ChildNodes(1).Name = "BootstrapperApplicationData" Then
>            uc = 
> tempXml.ChildNodes(1).ChildNodes(0).Attributes("UpgradeCode").InnerText
>        End If
>        Return uc
> 
> Note that this is fairly slow and would probably be onerous if one had giant 
> bundles (ours are tens of megabytes at most).
> 
> I'm not sure how one would do this from a Burn bundle; might need custom.
> 
> 
> Keith Douglas
> Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
> Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6
> keith.doug...@statcan.gc.ca
> Telephone | T?l?phone 613-854-5589
> Facsimile | T?l?copieur 613-951-4674
> Government of Canada | Gouvernement du Canada 
> 
> 
> -----Original Message-----
> From: Marco Tognacci [mailto:mark...@live.it] 
> Sent: April-28-15 5:48 PM
> To: WiX - users
> Subject: Re: [WiX-users] Detect condition for a Burn Package ?
> 
> So at this moment, there isn't a way for doing this?
> 
> 
>> From: r...@firegiant.com
>> To: wix-users@lists.sourceforge.net
>> Date: Tue, 28 Apr 2015 21:18:56 +0000
>> Subject: Re: [WiX-users] Detect condition for a Burn Package ?
>> 
>> IIRC, there is a feature request open for that.
>> 
>> _____________________________________________________________
>> Short replies here. Complete answers over there: 
>> http://www.firegiant.com/
>> 
>> 
>> -----Original Message-----
>> From: Marco Tognacci [mailto:mark...@live.it]
>> Sent: Tuesday, April 28, 2015 1:55 PM
>> To: WiX - users
>> Subject: [WiX-users] Detect condition for a Burn Package ?
>> 
>> I have a Burn package (setup1.exe) that have an UpgradeCode={GUID}I have 
>> used this exe package inside another Burn setup (setup2.exe), in this 
>> package I need to  get the DetectCondition for the firt package (setup1.exe) 
>> is there any way to get this condition?
>> <util:ProductSearch UpgradeCode="XXXXXXXX-XXXX-XXXX-XXXXXXXXXXXXXXXXX" 
>> Variable="Setup1_Installed" Result="state"/> I have tried this but it report 
>> Setup1_Installed = 2 as not installed even if it is really installed,I have 
>> read that this ProductSearch is only for the msi package, is right? 
>> I have search on the registry the UpgradeCode and it appear in the 
>> Uninstall section in a variable BundleUpgradeCode, But I don't know 
>> how to check it as it is under a GUID code that is auto genrated 
>> during setup of the setup1.exe Any way for doing this?Thanks
>> 
>> 
>> ----------------------------------------------------------------------
>> -------- One dashboard for servers and applications across 
>> Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 
>> 50+ applications Performance metrics, stats and reports that give you 
>> Actionable Insights Deep dive visibility with transaction tracing 
>> using APM Insight.
>> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
>> _______________________________________________
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>                         
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud 
> Widest out-of-the-box monitoring support with 50+ applications Performance 
> metrics, stats and reports that give you Actionable Insights Deep dive 
> visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 
> 
> ------------------------------
> 
> Message: 4
> Date: Tue, 28 Apr 2015 15:26:15 -0700
> From: Henri Hein <he...@thinair.com>
> Subject: Re: [WiX-users] Reboot and ReallySuppress
> To: wix-users@lists.sourceforge.net
> Message-ID:
>    <cafxqxonjyg8lunl-thfjjwib6qm6edydrjvqwe+ebtwnrz3...@mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
> 
> Thanks, Phil.  Here's a link to the full log file:
> http://1drv.ms/1JyRdgH
> 
> I should have mentioned as well that this particular log was from an
> upgrade, though the problem happens on both upgrades and clean installs
> (installs where I uninstall first, reboot, then install).
> 
> Thanks,
>  - Henri
> 
> 
> ------------------------------
> 
> Message: 5
> Date: Tue, 28 Apr 2015 15:37:46 -0700 (MST)
> From: Phill Hogland <phogl...@rimage.com>
> Subject: Re: [WiX-users] Detect condition for a Burn Package ?
> To: wix-users@lists.sourceforge.net
> Message-ID: <1430260666016-7600132.p...@n2.nabble.com>
> Content-Type: text/plain; charset=us-ascii
> 
> With regard to using a Burn bundle in the chain of a Bundle, I did a little
> experimenting and I defined the RelatedBundle Action=Detect in the parent
> and Action=Addon or Update in the child.  I put logging code on the various
> RelatedBundle handlers in the mba but I did not need to do any
> implementation as Burn handled what I needed automaticly.  The
> ExePackage/@Protocol was set to "burn"
> 
> However with regard to finding the Bundle registration under the Windows
> Uninstall (ARP ) registry key, I posted some details in another thread on
> this issue.  I implemented a process well over a year ago that allows me (as
> a transition) to use wix bundles as child setups of a non-wix setup, which I
> am working on eliminating.  The auto-generated guid that you mentioned is
> the BundleID (or ProductID).  It is in the BootstrapperApplicationData.xml
> file.  There are examples out there for creating a class for a mba to read
> this xml file.  With a slight modification your mba can know it's BundleID. 
> I pass it down to one of my msi packages which saves it in the registry. 
> (As I recall I also had to explicitly define the ProviderKey to get the ARP
> registry key to not automatically change.  (Last time I indicated that
> detail someone said I was wrong.)  Anyway my non-wix setup knows the
> application deployed by the msi is installed, looks up the BundleId which
> installed it, and can then work out the pat to that bundle.exe and launch it
> to uninstall or repair.  Non-standard I know, and I am eager to not need to
> do this as I fully convert everything to wix.
> 
> 
> 
> --
> View this message in context: 
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Detect-condition-for-a-Burn-Package-tp7600124p7600132.html
> Sent from the wix-users mailing list archive at Nabble.com.
> 
> 
> 
> ------------------------------
> 
> Message: 6
> Date: Tue, 28 Apr 2015 18:59:54 -0700 (MST)
> From: wixtester <sangee...@hotmail.com>
> Subject: [WiX-users] Unable to access HTTPS after installing ssl
>    certificate    to website
> To: wix-users@lists.sourceforge.net
> Message-ID: <1430272794088-7600136.p...@n2.nabble.com>
> Content-Type: text/plain; charset=us-ascii
> 
> Hi,
> 
> I am unable to access my website with HTTPS. 
> After install, I see the SSL certificate is installed in the
> Personal\Certificates store and is also listed in the Server Certificates in
> IIS manager. But I don't see the certificate listed in the binding window
> that associates the port, ipaddress, header and ssl cert.
> 
> How can I get the certificate selected to the port binding using the code
> below ?
>    <Component Id="InstallWebsite" Guid="{GUID_VALUE}" KeyPath="yes"
> Win64="yes">
>        <iis:Certificate Id="PCert" BinaryKey="ProvCertPath" Name="ProvCert"
> PFXPassword="PASSWORD" Overwrite="yes" StoreLocation="localMachine"
> StoreName="personal" Request="no" />
>        <iis:WebSite Id="ProvisionIISWebsite"
> Description="$(var.IISWebSite)" Directory='IIS_WEBAPP' AutoStart='yes'
> StartOnInstall='yes'>
>          <iis:WebAddress Id="AllUnassigned" Port="[IISPORT]" Secure="yes"
> />
>          <iis:WebApplication Id="IISApplication"
> Name="[ProvisionIISWebsite]" 
> WebAppPool="IISWebsiteAppPool"></iis:WebApplication>
>          <iis:CertificateRef Id="PCert" />
>        </iis:WebSite>
>      </Component>
> 
> 
> Thanks!
> 
> 
> 
> --
> View this message in context: 
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Unable-to-access-HTTPS-after-installing-ssl-certificate-to-website-tp7600136.html
> Sent from the wix-users mailing list archive at Nabble.com.
> 
> 
> 
> ------------------------------
> 
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud 
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> 
> ------------------------------
> 
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 
> End of WiX-users Digest, Vol 107, Issue 43
> ******************************************

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to