Re: [WiX-users] util:RegistrySearch “Registry key not found” when using variable inside Win64=“$(var.Win64)”
Interesting, I was able to get it to work by simply removing the Win64 attribute altogether. I swear I tried this before and it didn't work... Just needed a nights sleep I guess. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/util-RegistrySearch-Registry-key-not-found-when-using-variable-inside-Win64-var-Win64-tp7593659p7593661.html Sent from the wix-users mailing list archive at Nabble.com. -- Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] util:RegistrySearch “Registry key not found” when using variable inside Win64=“$(var.Win64)”
http://stackoverflow.com/questions/22559113/utilregistrysearch-registry-key-not-found-when-using-variable-inside-win64 Am I doing something wrong? Thanks, -dirt -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/util-RegistrySearch-Registry-key-not-found-when-using-variable-inside-Win64-var-Win64-tp7593659.html Sent from the wix-users mailing list archive at Nabble.com. -- Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How do you bind a version number to a binary with an autogenerated wix component id?
I prefer this pre-build PowerShell script to auto-increment my build version. It gives greater control in how the version is incremented, when it is incremented (e.g. Release mode vs Debug mode) and which file(s) to actually update with the new version (e.g AssemblyInfo.cs and/or Variables.wxi). http://eldirte.blogspot.com/2013/10/visual-studio-pre-build-event-scripts.html Hope this helps. -dirt On 2013-10-23 17:28, victorwhiskey wrote: > Currently I'm using > > Version = !(bind.FileVersion.fil1241xxx) > > to bind the file version number to my MSI, where fil1241xx is a > component id I specified. How do I do it when it's generated per > build? > > Thanks! > > > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-do-you-bind-a-version-number-to-a-binary-with-an-autogenerated-wix-component-id-tp7589937.html > Sent from the wix-users mailing list archive at Nabble.com. > > -- > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the > most from > the latest Intel processors and coprocessors. See abstracts and > register > > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] [SPAM] Invalid package type
I was able to resolve this by changing WixBA.Plan(LaunchAction.UpdateReplace) to WixBA.Plan(LaunchAction.Install) per http://stackoverflow.com/questions/17676657/wix-burn-bootstrapper-majorupgrade On 2013-10-15 08:32, dirt wrote: > Well, it's back. My first upgrade test didn't have any Errors, now my > subsequent tests have the 'Invalid package type' error below. > > What causes this? > > Thanks, > -dirt > > On 2013-10-15 08:17, dirt wrote: >> I was able to resolve this by re-installing the new weekly build >> released last night (v3.8.1014.0). >> >> On 2013-10-14 18:11, dirt wrote: >>> I apparently made too many changes at once and now when I try to >>> install an updated version of the bootstrapper I get 'Invalid >>> package >>> type': >>> >>> = >>> [0FB4:0C24][2013-10-14T18:05:31]i199: Detect complete, result: 0x0 >>> [0FB4:0C24][2013-10-14T18:05:31]i200: Plan begin, 7 packages, >>> action: >>> UpdateReplace >>> [0FB4:0C24][2013-10-14T18:05:31]i000: [DEBUG-Progress] PlanBegin: >>> [0FB4:0C24][2013-10-14T18:05:31]e000: Error 0x8000: Invalid >>> package >>> type. >>> [0FB4:0C24][2013-10-14T18:05:31]e000: Error 0x8000: Failed to >>> plan >>> execute package. >>> [0FB4:0C24][2013-10-14T18:05:31]i000: [DEBUG-Progress] >>> PlanPackageComplete: >>> [0FB4:0C24][2013-10-14T18:05:31]e000: Error 0x8000: Failed to >>> process update package. >>> [0FB4:0C24][2013-10-14T18:05:31]e000: Error 0x8000: Failed to >>> plan >>> update. >>> [0FB4:0C24][2013-10-14T18:05:31]i000: [DEBUG-Install] PlanComplete: >>> [0FB4:0C24][2013-10-14T18:05:31]i000: [DEBUG-Model] ApplyAction: 0 >>> [0FB4:0C24][2013-10-14T18:05:31]i299: Plan complete, result: >>> 0x8000 >>> [0FB4:0C24][2013-10-14T18:05:31]i300: Apply begin >>> [0FB4:0C24][2013-10-14T18:05:31]i000: [DEBUG-Install] ApplyBegin: >>> [0FB4:0C24][2013-10-14T18:05:31]w380: Apply skipped, no planned >>> actions >>> [0FB4:0C24][2013-10-14T18:05:31]i000: [DEBUG-Install] ApplyComplete: >>> Result: 0 >>> [0FB4:0C24][2013-10-14T18:05:31]i000: [DEBUG-Install] ApplyComplete: >>> Display: Full >>> [0FB4:0C24][2013-10-14T18:05:31]i000: [DEBUG-Install] ApplyComplete: >>> PlannedAction: UpdateReplace >>> = >>> >>> Variables.wxs: >>> >>> >>> >>> >> "029B62E4-4AFE-4D74-837D-D0E79622BD97" >>> ?> >>> >>> Product.wxs: >>> >>>>> UpgradeCode="$(var.GUID_PRODUCTUPGRADE)" >>> Name="$(var.ProductName)" >>> Version="$(var.ProductVersion)" >>> Manufacturer="$(var.Manufacturer)" >>> Language="1033"> >>> >>> >> InstallScope="perMachine" InstallPrivileges="elevated" /> >>> >>> >>> >>> >>Schedule="afterInstallFinalize"/> >>> >>> >>>>>IncludeMinimum="no" >>>OnlyDetect="yes" >>>Language="1033" >>>Property="NEWERVERSIONDETECTED" /> >>>>>IncludeMinimum="yes" >>>Maximum="$(var.ProductVersion)" >>>OnlyDetect="no" >>>IncludeMaximum="no" >>>Language="1033" >>>Property="OLDERVERSIONBEINGUPGRADED" /> >>> >>> >>>>>Maximum="$(var.ProductVersion)" >>> Minimum="$(var.ProductVersion)" >>>IncludeMinimum="yes" IncludeMaximum="yes" >>> OnlyDetect="yes" /> >>> >>> >>> = >>> >>> Thanks, >>> -dirt >>> >>> >>> >>> >>> -- >>> View this message in context: >>> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Invalid-package-type-tp7589708.html >>> Sent from the wix-users mailing list archive at Nabble.com. >>> --
Re: [WiX-users] [SPAM] Invalid package type
Well, it's back. My first upgrade test didn't have any Errors, now my subsequent tests have the 'Invalid package type' error below. What causes this? Thanks, -dirt On 2013-10-15 08:17, dirt wrote: > I was able to resolve this by re-installing the new weekly build > released last night (v3.8.1014.0). > > On 2013-10-14 18:11, dirt wrote: >> I apparently made too many changes at once and now when I try to >> install an updated version of the bootstrapper I get 'Invalid package >> type': >> >> = >> [0FB4:0C24][2013-10-14T18:05:31]i199: Detect complete, result: 0x0 >> [0FB4:0C24][2013-10-14T18:05:31]i200: Plan begin, 7 packages, action: >> UpdateReplace >> [0FB4:0C24][2013-10-14T18:05:31]i000: [DEBUG-Progress] PlanBegin: >> [0FB4:0C24][2013-10-14T18:05:31]e000: Error 0x8000: Invalid >> package >> type. >> [0FB4:0C24][2013-10-14T18:05:31]e000: Error 0x8000: Failed to >> plan >> execute package. >> [0FB4:0C24][2013-10-14T18:05:31]i000: [DEBUG-Progress] >> PlanPackageComplete: >> [0FB4:0C24][2013-10-14T18:05:31]e000: Error 0x8000: Failed to >> process update package. >> [0FB4:0C24][2013-10-14T18:05:31]e000: Error 0x8000: Failed to >> plan >> update. >> [0FB4:0C24][2013-10-14T18:05:31]i000: [DEBUG-Install] PlanComplete: >> [0FB4:0C24][2013-10-14T18:05:31]i000: [DEBUG-Model] ApplyAction: 0 >> [0FB4:0C24][2013-10-14T18:05:31]i299: Plan complete, result: >> 0x8000 >> [0FB4:0C24][2013-10-14T18:05:31]i300: Apply begin >> [0FB4:0C24][2013-10-14T18:05:31]i000: [DEBUG-Install] ApplyBegin: >> [0FB4:0C24][2013-10-14T18:05:31]w380: Apply skipped, no planned >> actions >> [0FB4:0C24][2013-10-14T18:05:31]i000: [DEBUG-Install] ApplyComplete: >> Result: 0 >> [0FB4:0C24][2013-10-14T18:05:31]i000: [DEBUG-Install] ApplyComplete: >> Display: Full >> [0FB4:0C24][2013-10-14T18:05:31]i000: [DEBUG-Install] ApplyComplete: >> PlannedAction: UpdateReplace >> = >> >> Variables.wxs: >> >> >> >> > ?> >> >> Product.wxs: >> >>> UpgradeCode="$(var.GUID_PRODUCTUPGRADE)" >> Name="$(var.ProductName)" >> Version="$(var.ProductVersion)" >> Manufacturer="$(var.Manufacturer)" >> Language="1033"> >> >> > InstallScope="perMachine" InstallPrivileges="elevated" /> >> >> >> >> >Schedule="afterInstallFinalize"/> >> >> >>>IncludeMinimum="no" >>OnlyDetect="yes" >>Language="1033" >>Property="NEWERVERSIONDETECTED" /> >>>IncludeMinimum="yes" >>Maximum="$(var.ProductVersion)" >>OnlyDetect="no" >>IncludeMaximum="no" >>Language="1033" >>Property="OLDERVERSIONBEINGUPGRADED" /> >> >> >>>Maximum="$(var.ProductVersion)" >> Minimum="$(var.ProductVersion)" >>IncludeMinimum="yes" IncludeMaximum="yes" >> OnlyDetect="yes" /> >> >> >> = >> >> Thanks, >> -dirt >> >> >> >> >> -- >> View this message in context: >> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Invalid-package-type-tp7589708.html >> Sent from the wix-users mailing list archive at Nabble.com. >> -- >> October Webinars: Code for Performance >> Free Intel webinars can help you accelerate application performance. >> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the >> most from >> the latest Intel processors and coprocessors. See abstracts and >> register > >> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk >> ___ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users > > -- >
Re: [WiX-users] [SPAM] Invalid package type
I was able to resolve this by re-installing the new weekly build released last night (v3.8.1014.0). On 2013-10-14 18:11, dirt wrote: > I apparently made too many changes at once and now when I try to > install an updated version of the bootstrapper I get 'Invalid package > type': > > = > [0FB4:0C24][2013-10-14T18:05:31]i199: Detect complete, result: 0x0 > [0FB4:0C24][2013-10-14T18:05:31]i200: Plan begin, 7 packages, action: > UpdateReplace > [0FB4:0C24][2013-10-14T18:05:31]i000: [DEBUG-Progress] PlanBegin: > [0FB4:0C24][2013-10-14T18:05:31]e000: Error 0x8000: Invalid > package > type. > [0FB4:0C24][2013-10-14T18:05:31]e000: Error 0x8000: Failed to plan > execute package. > [0FB4:0C24][2013-10-14T18:05:31]i000: [DEBUG-Progress] > PlanPackageComplete: > [0FB4:0C24][2013-10-14T18:05:31]e000: Error 0x8000: Failed to > process update package. > [0FB4:0C24][2013-10-14T18:05:31]e000: Error 0x8000: Failed to plan > update. > [0FB4:0C24][2013-10-14T18:05:31]i000: [DEBUG-Install] PlanComplete: > [0FB4:0C24][2013-10-14T18:05:31]i000: [DEBUG-Model] ApplyAction: 0 > [0FB4:0C24][2013-10-14T18:05:31]i299: Plan complete, result: > 0x8000 > [0FB4:0C24][2013-10-14T18:05:31]i300: Apply begin > [0FB4:0C24][2013-10-14T18:05:31]i000: [DEBUG-Install] ApplyBegin: > [0FB4:0C24][2013-10-14T18:05:31]w380: Apply skipped, no planned > actions > [0FB4:0C24][2013-10-14T18:05:31]i000: [DEBUG-Install] ApplyComplete: > Result: 0 > [0FB4:0C24][2013-10-14T18:05:31]i000: [DEBUG-Install] ApplyComplete: > Display: Full > [0FB4:0C24][2013-10-14T18:05:31]i000: [DEBUG-Install] ApplyComplete: > PlannedAction: UpdateReplace > = > > Variables.wxs: > > > > ?> > > Product.wxs: > > UpgradeCode="$(var.GUID_PRODUCTUPGRADE)" > Name="$(var.ProductName)" > Version="$(var.ProductVersion)" > Manufacturer="$(var.Manufacturer)" > Language="1033"> > >InstallScope="perMachine" InstallPrivileges="elevated" /> > > > > Schedule="afterInstallFinalize"/> > > >IncludeMinimum="no" >OnlyDetect="yes" >Language="1033" >Property="NEWERVERSIONDETECTED" /> >IncludeMinimum="yes" >Maximum="$(var.ProductVersion)" >OnlyDetect="no" >IncludeMaximum="no" >Language="1033" >Property="OLDERVERSIONBEINGUPGRADED" /> > > >Maximum="$(var.ProductVersion)" > Minimum="$(var.ProductVersion)" >IncludeMinimum="yes" IncludeMaximum="yes" > OnlyDetect="yes" /> > > > = > > Thanks, > -dirt > > > > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Invalid-package-type-tp7589708.html > Sent from the wix-users mailing list archive at Nabble.com. > -- > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the > most from > the latest Intel processors and coprocessors. See abstracts and > register > > http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] [SPAM] Invalid package type
I apparently made too many changes at once and now when I try to install an updated version of the bootstrapper I get 'Invalid package type': = [0FB4:0C24][2013-10-14T18:05:31]i199: Detect complete, result: 0x0 [0FB4:0C24][2013-10-14T18:05:31]i200: Plan begin, 7 packages, action: UpdateReplace [0FB4:0C24][2013-10-14T18:05:31]i000: [DEBUG-Progress] PlanBegin: [0FB4:0C24][2013-10-14T18:05:31]e000: Error 0x8000: Invalid package type. [0FB4:0C24][2013-10-14T18:05:31]e000: Error 0x8000: Failed to plan execute package. [0FB4:0C24][2013-10-14T18:05:31]i000: [DEBUG-Progress] PlanPackageComplete: [0FB4:0C24][2013-10-14T18:05:31]e000: Error 0x8000: Failed to process update package. [0FB4:0C24][2013-10-14T18:05:31]e000: Error 0x8000: Failed to plan update. [0FB4:0C24][2013-10-14T18:05:31]i000: [DEBUG-Install] PlanComplete: [0FB4:0C24][2013-10-14T18:05:31]i000: [DEBUG-Model] ApplyAction: 0 [0FB4:0C24][2013-10-14T18:05:31]i299: Plan complete, result: 0x8000 [0FB4:0C24][2013-10-14T18:05:31]i300: Apply begin [0FB4:0C24][2013-10-14T18:05:31]i000: [DEBUG-Install] ApplyBegin: [0FB4:0C24][2013-10-14T18:05:31]w380: Apply skipped, no planned actions [0FB4:0C24][2013-10-14T18:05:31]i000: [DEBUG-Install] ApplyComplete: Result: 0 [0FB4:0C24][2013-10-14T18:05:31]i000: [DEBUG-Install] ApplyComplete: Display: Full [0FB4:0C24][2013-10-14T18:05:31]i000: [DEBUG-Install] ApplyComplete: PlannedAction: UpdateReplace = Variables.wxs: Product.wxs: = Thanks, -dirt -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Invalid-package-type-tp7589708.html Sent from the wix-users mailing list archive at Nabble.com. -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Upgrade confusion
Thank you for the missing link, I am now able to detect this as I
wanted.
I have a new problem though. When the upgraded/new version of
bootstrapper is invoked through the Update command, I am running into an
issue where the app is trying to see what version it is by using
Assembly/FileVersionInfo, but it is looking for its files in the wrong
place (C:\Users\x\AppData\Local\Package Cache\) as opposed to
(C:\ProgramData\Package Cache) and is causing a
System.IO.FileNotFoundException.
Can anyone explain why it can't find itself? I've tried toggling the
Cache="yes" property but nothing changes.
=Details=
v1.0.73 Installed. Exists: C:\ProgramData\Package
Cache\{971e0d36-1c42-4eca-a6ee-4804edcc83eb}\MyApp.exe
v1.0.73 Change, Update v1.0.74 Launched:
This gets created, but is empty: C:\Users\dirt\AppData\Local\Package
Cache\{971e0d36-1c42-4eca-a6ee-4804edcc83eb}
System.FileNotFoundException: C:\Users\dirt\AppData\Local\Package
Cache\{971e0d36-1c42-4eca-a6ee-4804edcc83eb}\MyApp.exe
=
Thanks,
-dirt
On 2013-10-14 10:35, Hoover, Jacob wrote:
> The engine is going to have "burn.related.upgrade" passed as a
> command line option, but as that is an internal burn parameter it
> won't get passed to your BA. The engine does set
> pCommand->relationType = BOOTSTRAPPER_RELATION_UPGRADE;
>
> Take a look at Command.Relation.
>
> -Original Message-
> From: dirt [mailto:d...@awoms.com]
> Sent: Monday, October 14, 2013 9:21 AM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Upgrade confusion
>
> When a bootstrapper v1.0.1 downloads and installs an update (v1.0.2)
> it logs "Automatically closing the window since update successful" and
> opens the v1.0.2 bootstrapper with this in the log at the top:
>
> "This bundle is being run by a related bundle as type 'Update'."
>
> From what I can tell in the logs, when the v1.0.2 is opened it is
> treated just like a normal run; the Action is "Install".
>
>
> Is there any built-in way to detect when a bootstrapper is ran as type
> 'Update'?
>
>
> The only way I see how to do this currently would be to store
> something
> in the registry at the shutdown of v1 that v2 reads to know that it
> should automatically continue to the Install portion.
>
> Thanks,
> -dirt
>
> On 2013-10-11 15:58, dirt wrote:
>> How am I to detect that the bootstrapper has been invoked via an
>> Update
>> and thus should suppress the UI and auto-invoke the Install sequence?
>>
>> I dont see anything when comparing the 1.0.1 and 1.0.2 logs to
>> indicate
>> that an Update could be detected. There is one line at the top of the
>> v1.0.2 log: i003: This bundle is being run by a related bundle as
>> type
>> 'Update'.
>>
>> But in DetectBegin the CustomBA.Model.Bootstrapper.Command.Action is
>> "Install", when I would expect it to be "UpdateReplace".
>>
>> =
>> Using Burn v3.8.1007.0.
>> PID is *.
>> Version Build is incremented on each build.
>> =
>>
>> v1.0.1 Installed
>> v1.0.1 Change launched from ARP, Update clicked, v1.0.2 downloaded
>> and
>> ExecutePackageComplete is success, v1.0.1 is exited automatically
>> v1.0.2 Is auto opened, but instead of detecting it is an update and
>> auto installing, it appears in the logs that the bootstrapper and
>> MyApp
>> are detected as Absent and it sits at the UI waiting for you to click
>> Install.
>>
>> Thanks,
>> -dirt
>>
>> On 2013-10-11 11:57, dirt wrote:
>>> Thank you for the clarification.
>>>
>>> I have made progress and here is an updated scenario, I am not sure
>>> why
>>> the update is not auto-installing but instead waiting for me to
>>> click
>>> Install (at step 2)
>>>
>>> =
>>> Product ID = *
>>> Product UpgradeCode = 029B...BD97
>>> Bootstrapper UpgradeCode = f031...56b3
>>> =
>>>
>>> 1) Install Bootstrapper v1.0.1
>>>
>>> 2) Run Add/Remove Programs > Change, Launches v1.0.1 UI, Click
>>> Update
>>>
>>> Update downloads, runs, appears to install and close the original UI
>>> (v1.0.1) and opens the new UI (v1.0.2)
>>>
>>> UI shows new version and shows as "Not Installed" with the Install
>>> option enabled.
>>>
>>> =
>>> This bundle is being run by a related bundle as type 'Update'.
>>> DetectBegin: Not Installed
>>> Detected package: MyApp,
Re: [WiX-users] Upgrade confusion
When a bootstrapper v1.0.1 downloads and installs an update (v1.0.2) it logs "Automatically closing the window since update successful" and opens the v1.0.2 bootstrapper with this in the log at the top: "This bundle is being run by a related bundle as type 'Update'." From what I can tell in the logs, when the v1.0.2 is opened it is treated just like a normal run; the Action is "Install". Is there any built-in way to detect when a bootstrapper is ran as type 'Update'? The only way I see how to do this currently would be to store something in the registry at the shutdown of v1 that v2 reads to know that it should automatically continue to the Install portion. Thanks, -dirt On 2013-10-11 15:58, dirt wrote: > How am I to detect that the bootstrapper has been invoked via an > Update > and thus should suppress the UI and auto-invoke the Install sequence? > > I dont see anything when comparing the 1.0.1 and 1.0.2 logs to > indicate > that an Update could be detected. There is one line at the top of the > v1.0.2 log: i003: This bundle is being run by a related bundle as type > 'Update'. > > But in DetectBegin the CustomBA.Model.Bootstrapper.Command.Action is > "Install", when I would expect it to be "UpdateReplace". > > = > Using Burn v3.8.1007.0. > PID is *. > Version Build is incremented on each build. > = > > v1.0.1 Installed > v1.0.1 Change launched from ARP, Update clicked, v1.0.2 downloaded and > ExecutePackageComplete is success, v1.0.1 is exited automatically > v1.0.2 Is auto opened, but instead of detecting it is an update and > auto installing, it appears in the logs that the bootstrapper and > MyApp > are detected as Absent and it sits at the UI waiting for you to click > Install. > > Thanks, > -dirt > > On 2013-10-11 11:57, dirt wrote: >> Thank you for the clarification. >> >> I have made progress and here is an updated scenario, I am not sure >> why >> the update is not auto-installing but instead waiting for me to click >> Install (at step 2) >> >> = >> Product ID = * >> Product UpgradeCode = 029B...BD97 >> Bootstrapper UpgradeCode = f031...56b3 >> = >> >> 1) Install Bootstrapper v1.0.1 >> >> 2) Run Add/Remove Programs > Change, Launches v1.0.1 UI, Click Update >> >> Update downloads, runs, appears to install and close the original UI >> (v1.0.1) and opens the new UI (v1.0.2) >> >> UI shows new version and shows as "Not Installed" with the Install >> option enabled. >> >> = >> This bundle is being run by a related bundle as type 'Update'. >> DetectBegin: Not Installed >> Detected package: MyApp, state: Absent >> DetectComplete: DetectedAbsent >> = >> >> ***a) Why does it not Auto Install? It is triggered by 'Update' yet >> waits for me to click Install.*** >> >> 3) Click Install: Installs MyApp >> >> v1.0.2 is installed successfully >> >> v1.0.1 ui is opened again automatically (this time appears to be >> hidden) >> >> 4) v1.0.2 UI shows as Complete. >> >> Add/Remove programs shows new v1.0.2 is installed. >> = >> >> Thanks, >> -dirt >> >> On 2013-10-10 19:08, Phill Hogland wrote: >>> For MajorUpgrade behavior you must change both the Product ID and >>> the >>> version. The UpgradeCode should remain unchanged. Also the version >>> of the >>> MSI must change in the first three quad-dots. The version of the >>> bundle can >>> be changed in any part of the version string. >>> >>> http://wixtoolset.org/documentation/manual/v3/howtos/updates/major_upgrade.html >>> >>> I would set the Id="*" and increment the Build portion of the >>> version >>> string >>> (Major.Minor.Build.Revision) to achieve what you are trying to do. >>> >>> >>> >>> -- >>> View this message in context: >>> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Upgrade-confusion-tp7589648p7589649.html >>> Sent from the wix-users mailing list archive at Nabble.com. >>> >>> -- >>> October Webinars: Code for Performance >>> Free Intel webinars can help you accelerate application performance. >>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the >>> most from >>> the latest
Re: [WiX-users] Upgrade confusion
How am I to detect that the bootstrapper has been invoked via an Update and thus should suppress the UI and auto-invoke the Install sequence? I dont see anything when comparing the 1.0.1 and 1.0.2 logs to indicate that an Update could be detected. There is one line at the top of the v1.0.2 log: i003: This bundle is being run by a related bundle as type 'Update'. But in DetectBegin the CustomBA.Model.Bootstrapper.Command.Action is "Install", when I would expect it to be "UpdateReplace". = Using Burn v3.8.1007.0. PID is *. Version Build is incremented on each build. = v1.0.1 Installed v1.0.1 Change launched from ARP, Update clicked, v1.0.2 downloaded and ExecutePackageComplete is success, v1.0.1 is exited automatically v1.0.2 Is auto opened, but instead of detecting it is an update and auto installing, it appears in the logs that the bootstrapper and MyApp are detected as Absent and it sits at the UI waiting for you to click Install. Thanks, -dirt On 2013-10-11 11:57, dirt wrote: > Thank you for the clarification. > > I have made progress and here is an updated scenario, I am not sure > why > the update is not auto-installing but instead waiting for me to click > Install (at step 2) > > = > Product ID = * > Product UpgradeCode = 029B...BD97 > Bootstrapper UpgradeCode = f031...56b3 > = > > 1) Install Bootstrapper v1.0.1 > > 2) Run Add/Remove Programs > Change, Launches v1.0.1 UI, Click Update > > Update downloads, runs, appears to install and close the original UI > (v1.0.1) and opens the new UI (v1.0.2) > > UI shows new version and shows as "Not Installed" with the Install > option enabled. > > = > This bundle is being run by a related bundle as type 'Update'. > DetectBegin: Not Installed > Detected package: MyApp, state: Absent > DetectComplete: DetectedAbsent > = > > ***a) Why does it not Auto Install? It is triggered by 'Update' yet > waits for me to click Install.*** > > 3) Click Install: Installs MyApp > > v1.0.2 is installed successfully > > v1.0.1 ui is opened again automatically (this time appears to be > hidden) > > 4) v1.0.2 UI shows as Complete. > > Add/Remove programs shows new v1.0.2 is installed. > = > > Thanks, > -dirt > > On 2013-10-10 19:08, Phill Hogland wrote: >> For MajorUpgrade behavior you must change both the Product ID and the >> version. The UpgradeCode should remain unchanged. Also the version >> of the >> MSI must change in the first three quad-dots. The version of the >> bundle can >> be changed in any part of the version string. >> >> http://wixtoolset.org/documentation/manual/v3/howtos/updates/major_upgrade.html >> >> I would set the Id="*" and increment the Build portion of the version >> string >> (Major.Minor.Build.Revision) to achieve what you are trying to do. >> >> >> >> -- >> View this message in context: >> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Upgrade-confusion-tp7589648p7589649.html >> Sent from the wix-users mailing list archive at Nabble.com. >> >> -- >> October Webinars: Code for Performance >> Free Intel webinars can help you accelerate application performance. >> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the >> most from >> the latest Intel processors and coprocessors. See abstracts and >> register > >> http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk >> ___ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users > > -- > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the > most from > the latest Intel processors and coprocessors. See abstracts and > register > > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] wixtoolset.org weekly builds downloads missing (404)
Hello. I worked as Sr. Sys Admin and CTO at a hosting company for over 5 years so I am lending my advice in regard to your hosting search. By no means do I mean this as an advertisement; I have no affiliation with anyone I am talking about. I left my last job and am now programming full time and much happier :) I have recently been hosting my personal projects at DigitalOcean.com and I would personally recommend them as they have been great thus far providing SSD cloud servers for as little as $5 a month. The SSD performance has shown to be double that of other non-ssd providers. I'm not sure what you are currently using or what capacity you need but it would be worth giving them a shot. I have also tried Rackspace.com and they are an ok 2nd, but are more expensive. Another one you may not have heard of is SoftLayer.com, they were just recently bought out by IBM. I would rank them 3rd. If you would like to try digitialocean I have a referral code :) Sorry if this is taken in any other way than my 2 cents. -dirt On 2013-10-11 13:23, Rob Mensching wrote: > The site was down for a bit this morning. > > FYI: We are investigating new hosting locations since our current > budget > hoster of 3 years has started having systematic issues. > > > On Fri, Oct 11, 2013 at 9:47 AM, Bruce Cran wrote: > >> On 10/11/2013 5:42 PM, Bruce Cran wrote: >>> None of the builds via wixtoolset.org are working. For example >>> trying >>> to download 3.8.1007 results in the broken link >>> http://wixtoolset.org/downloads/v3.8.1007.0/wix38.exe. >>> >> >> After refreshing each page it now works. >> >> -- >> Bruce Cran >> >> >> -- >> October Webinars: Code for Performance >> Free Intel webinars can help you accelerate application performance. >> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the >> most >> from >> the latest Intel processors and coprocessors. See abstracts and >> register > >> http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk >> ___ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> >> > -- > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the > most from > the latest Intel processors and coprocessors. See abstracts and > register > > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Upgrade confusion
Thank you for the clarification. I have made progress and here is an updated scenario, I am not sure why the update is not auto-installing but instead waiting for me to click Install (at step 2) = Product ID = * Product UpgradeCode = 029B...BD97 Bootstrapper UpgradeCode = f031...56b3 = 1) Install Bootstrapper v1.0.1 2) Run Add/Remove Programs > Change, Launches v1.0.1 UI, Click Update Update downloads, runs, appears to install and close the original UI (v1.0.1) and opens the new UI (v1.0.2) UI shows new version and shows as "Not Installed" with the Install option enabled. = This bundle is being run by a related bundle as type 'Update'. DetectBegin: Not Installed Detected package: MyApp, state: Absent DetectComplete: DetectedAbsent = ***a) Why does it not Auto Install? It is triggered by 'Update' yet waits for me to click Install.*** 3) Click Install: Installs MyApp v1.0.2 is installed successfully v1.0.1 ui is opened again automatically (this time appears to be hidden) 4) v1.0.2 UI shows as Complete. Add/Remove programs shows new v1.0.2 is installed. = Thanks, -dirt On 2013-10-10 19:08, Phill Hogland wrote: > For MajorUpgrade behavior you must change both the Product ID and the > version. The UpgradeCode should remain unchanged. Also the version > of the > MSI must change in the first three quad-dots. The version of the > bundle can > be changed in any part of the version string. > > http://wixtoolset.org/documentation/manual/v3/howtos/updates/major_upgrade.html > > I would set the Id="*" and increment the Build portion of the version > string > (Major.Minor.Build.Revision) to achieve what you are trying to do. > > > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Upgrade-confusion-tp7589648p7589649.html > Sent from the wix-users mailing list archive at Nabble.com. > > -- > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the > most from > the latest Intel processors and coprocessors. See abstracts and > register > > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Upgrade confusion
I need some clarification on how to process Upgrades for the bootstrapper. I am trying to use major upgrades (for 'simplicity') for each bootstrapper build to replace the existing version installed. Here's an example of what I'm experiencing: (Product ID and UpgradeCode are static, the Version (revision) is incremented on each build.) = [ID = 82e6e1be-f56e-40ad-98a5-0c010dd77b3] [UpgradeCode = 029B62E4-4AFE-4D74-837D-D0E79622BD97] Run v1.0.0.1; detects as Not Installed. Click Install. Installs successfully. Run v1.0.0.2; detects as Installed. Close. Run v1.0.0.1; Click Update; appears to Download and Install v1.0.0.2 according to Logs completes successfully. v1.0.0.2 opens after old closes; detects as Installed. Add/Remove Programs still shows v1.0.0.1... Files are still v1.0.0.1 = It's at this point I don't understand why a) if v1 logs show update successfull then exit why v2 doesnt appear to be installed and b) why v2 is opened after v1 exits - shouldn't the install be seamless? Thank you, -dirt -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn and ExePackage
If I understand correctly you are saying your problem is that your bootstrapper UI is starting a new instance at the end of your new exe installation? I believe this is caused by the bootstrapper trying to update itself, ie remove the older version as you just ran/installed a new version of the bootstrapper (providing the guid match and version has been incremented?) Otherwise, I would look in the log files in your %TEMP% folder to see what your exe installation is producing. -dirt On 2013-10-10 12:46, rw1017 wrote: > Hey all! > I'm trying to step through the code during bundle installation, but > seem to > be stuck. > > I have a package that is installing with an ExePackage. At the end of > a > successful execution(onExecutePackageComplete), it will create a new > instance of my bootstrapper UI(written in wpf/mvvmlight). > > I have other ExePackages that work normally without creating a new > instance > of the UI. > > Would anyone be able to point me in the right direction on how to > resolve > this one particular problem with the specific ExePackage? > > The ExePackage is a third party installer grabbed for ELO > Monitors(touchscreen monitors). > > The install command I use is "/iu /s" which tells it to silently > install. > > Another head scratcherit works fine when I run it on an x64 > machine, but > not on x86 machine. > > Thoughts? > > Thanks! > Richard > > > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-and-ExePackage-tp7589626.html > Sent from the wix-users mailing list archive at Nabble.com. > > -- > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the > most from > the latest Intel processors and coprocessors. See abstracts and > register > > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] UpdateEnabled not changing
I've stepped through my code using breakpoints but I fail to see why
the UpdateCommand does not seem to be enabled when this.UpdateEnabled ==
true.
UpdateViewModel sets State = Initializing
DetectUpdateBegin is fired setting State = Checking
this.RaisePropertyChanged(() => this.State); = Checking
this.RaisePropertyChanged(() => this.Title); = Checking
for updates
this.RaisePropertyChanged(() => this.CheckingEnabled); === True
this.RaisePropertyChanged(() => this.IsUpToDate); False
this.RaisePropertyChanged(() => this.UpdateEnabled); = False
DetectComplete is fired, State is still Checking so nothing is changed
worker_DoWork response is evaluated and update is found, sets State =
Available
this.RaisePropertyChanged(() => this.State); =
Available
this.RaisePropertyChanged(() => this.Title); = Newer
version available
this.RaisePropertyChanged(() => this.CheckingEnabled); === False
this.RaisePropertyChanged(() => this.IsUpToDate); False
this.RaisePropertyChanged(() => this.UpdateEnabled); = True
RootView shows "Update Available" and Wrench Icon, only the button
doesnt appear to be enabled (no mouseover effect) and clicking on it
does nothing.
I've compared my code to the example Setup\WixBA but don't see why this
isn't working correctly.
It seems to be something to do with the UpdateCommand not re-evaluating
the CanExecute method which is bound to a property that gets changed.
Only thing I really changed from example to mine is I am using Prism
for NotificationObject.
EDIT:
As I was writing this I tried something and got it to work, can anyone
tell me why the default isn't working but my changes below are working?
(Is it just because I am using Prism?)
=
public bool UpdateEnabled
{
get
{
//return this.UpdateCommand.CanExecute(this); // Orig:
Cant click update if update found...
return this.State == UpdateState.Available;
}
}
private ICommand updateCommand;
public ICommand UpdateCommand
{
get
{
if (this.updateCommand == null)
{
this.updateCommand = new DelegateCommand(
() => ConfirmUpdateRequest(),
//() => this.State == UpdateState.Available);
// Orig: Doesnt seem to be enabled once this.State ==
UpdateState.Available
() => !this.IsUpToDate);
}
return this.updateCommand;
}
}
=
--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to get the current directory of msi is running from?
I'm not sure if this applies here but I am using %~dp0 to get the current path in a cmd script used by the bootstrapper: More info: http://stackoverflow.com/questions/5034076/what-does-dp0-mean-and-how-does-it-work On 2013-10-09 11:49, Phil Wilson wrote: > And DATABASE is not a documented property - I wouldn't use it. > > Phil Wilson > > > On Wed, Oct 9, 2013 at 3:11 AM, Blair Murri wrote: > >> And you were already warned in your other posting of the same >> question >> about some of the issues you could run into. You haven't described >> what you >> are trying to accomplish, yet. >> >> Responding to our feedback will enable us to give you better answers. >> >>> Date: Wed, 9 Oct 2013 11:16:29 +0300 >>> From: fyodor...@gmail.com >>> To: wix-users@lists.sourceforge.net >>> Subject: Re: [WiX-users] How to get the current directory of msi is >> running from? >>> >>> Hi, >>> I never used such information during install but there are two >>> properties >>> that are set by MSI: >>> 1. OriginalDatabase - this is the .msi file you launched. >>> 2. DATABASE - the actual .msi file that is running >>> >>> -- >>> Regards, >>> Fyodor Koryazhkin.. >>> >> -- >>> October Webinars: Code for Performance >>> Free Intel webinars can help you accelerate application performance. >>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the >>> most >> from >>> the latest Intel processors and coprocessors. See abstracts and >>> register >>> >>> >> http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk >>> ___ >>> WiX-users mailing list >>> WiX-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/wix-users >> >> >> -- >> October Webinars: Code for Performance >> Free Intel webinars can help you accelerate application performance. >> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the >> most >> from >> the latest Intel processors and coprocessors. See abstracts and >> register > >> http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk >> ___ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> > -- > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the > most from > the latest Intel processors and coprocessors. See abstracts and > register > > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] [SPAM] Custom Bootstrapper Application Update Button
I am using the WiX Source\Setup\WixBA as a starting point for a custom
managed bootstrapper application.
I am trying to wrap my head around how the UpdateCommand works but I
don't even see the DetectUpdateBegin method get fired.
I see the DetectComplete method get fired but that just goes straight
to setting this.State = UpdateState.Current without checking for
updates.
What am I missing?
Ultimately I am trying to get the Bootstrapper to query a remote server
and download an updated version of itself instead of having to
distribute the updated bootstrapper.exe to the clients again.
=UpdateViewModel=
private void DetectUpdateBegin(object sender,
Microsoft.Tools.WindowsInstallerXml.Bootstrapper.DetectUpdateBeginEventArgs
e)
{
CustomBA.Model.LogMessage("[DEBUG-Update] DetectUpdateBegin: " +
e.UpdateLocation);
this.State = UpdateState.Checking;
this.worker.RunWorkerAsync(e.UpdateLocation);
}
private void DetectComplete(object sender,
Microsoft.Tools.WindowsInstallerXml.Bootstrapper.DetectCompleteEventArgs
e)
{
CustomBA.Model.LogMessage("[DEBUG-Update] DetectComplete: ");
// If we never started checking, assume we're up to date.
if (UpdateState.Initializing == this.State)
{
this.State = UpdateState.Current;
}
}
=
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Custom-Bootstrapper-Application-Update-Button-tp7589542.html
Sent from the wix-users mailing list archive at Nabble.com.
--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] [SPAM] Re: WiX Bootstrapper CustomAction Task.Wait instant Failure
Ok I was able to get the actual Exception by surrounding it with a try/catch (duh!) and the issue has nothing to do with WiX, I failed to run ParseClient.Initialize before trying to query Parse. /closed -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-Bootstrapper-CustomAction-Task-Wait-instant-Failure-tp7589448p7589452.html Sent from the wix-users mailing list archive at Nabble.com. -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] [SPAM] WiX Bootstrapper CustomAction Task.Wait instant Failure
Hello,
I have a CustomAction that checks a license key against a cloud
database. This uses an async method to wait for the response before
continuing.
When I test the methods below outside of the CustomAction, it works
fine; sends request, task waits for completion, returns results.
When I use the same methods in the CustomAction, I can see (using
debug) that as soon as the t.Wait() line is hit the Dialog instantly
goes to the "ended prematurely" page.
Is there something I am missing or are tasks - specifically waiting for
async tasks - not possible in CustomActions?
Thank you,
-Brock
=
[CustomAction]
public static ActionResult LicenseCheck(Session session)
{
#if DEBUG
System.Diagnostics.Debugger.Launch();
#endif
// Default Values
ReturnActionResult = ActionResult.Success;
session["PIDACCEPTED"] = "0";
string key = session["PIDKEY"].Replace("-", "");
IEnumerable results =
ParseCustom.StartQueryRequest("Store", "Key", key);
// Not making it past this point
...
public static class ParseCustom
{
public static IEnumerable StartQueryRequest(string
className, string key, string value)
{
Task> t = DoWorkAsync(className,
key, value);
t.Wait(); // Hitting this line in CustomAction causes
instant Failure, doesnt get past this line
return t.Result;
}
private static Task>
DoWorkAsync(string className, string key, string value)
{
return Task>.Factory.StartNew(()
=>
{
var x = AsyncTaskHelper(className, key, value);
return x.Result;
});
}
private static Task>
AsyncTaskHelper(string className, string key, string value)
{
return Task.Run(async () =>
{
IEnumerable ParseResults = await
AccessParseAsync(className, key, value);
return ParseResults;
});
}
private static async Task>
AccessParseAsync(string className, string key, string value)
{
ParseQuery query =
ParseObject.GetQuery(className).WhereEqualTo(key, value);
IEnumerable parseResults = await
query.FindAsync();
return parseResults;
}
}
...
TempLog:
MSI (c) (0C:BC) [09:24:13:569]: Doing action: LicenseCheckAction
Action 9:24:13: LicenseCheckAction.
Action start 9:24:13: LicenseCheckAction.
MSI (c) (0C:04) [09:24:13:591]: Invoking remote custom action. DLL:
C:\Users\dirt\AppData\Local\Temp\MSIFF5.tmp, Entrypoint: LicenseCheck
MSI (c) (0C:F0) [09:24:13:592]: Cloaking enabled.
MSI (c) (0C:F0) [09:24:13:592]: Attempting to enable all disabled
privileges before calling Install on Server
MSI (c) (0C:F0) [09:24:13:592]: Connected to service for CA
interface.
MSI (c) (0C!A4) [09:24:16:819]: PROPERTY CHANGE: Adding PIDACCEPTED
property. Its value is '0'.
Action ended 9:24:16: LicenseCheckAction. Return value 3.
DEBUG: Error 2896: Executing action LicenseCheckAction failed.
The installer has encountered an unexpected error installing this
package. This may indicate a problem with this package. The error code
is 2896. The arguments are: LicenseCheckAction, ,
Action ended 9:24:16: WelcomeDlg. Return value 3.
MSI (c) (0C:BC) [09:24:16:873]: Doing action: FatalError
Action 9:24:16: FatalError.
Action start 9:24:16: FatalError.
Action 9:24:16: FatalError. Dialog created
Action ended 9:32:02: FatalError. Return value 2.
Action ended 9:32:02: INSTALL. Return value 3.
MSI (c) (0C:BC) [09:32:02:489]: Destroying RemoteAPI object.
MSI (c) (0C:F0) [09:32:02:489]: Custom Action Manager thread
ending.
=
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-Bootstrapper-CustomAction-Task-Wait-instant-Failure-tp7589448.html
Sent from the wix-users mailing list archive at Nabble.com.
--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] [SPAM] Re: wixtoolset.org reporting 503 - service unavailable
Recycle the appPool! -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/wixtoolset-org-reporting-503-service-unavailable-tp7589445p7589446.html Sent from the wix-users mailing list archive at Nabble.com. -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] [SPAM] Re: Bootstrapper not detecting MsiPackage as Present when already installed
Oh I have Product Id="*"... whoops. I had that confused with UpgradeCode. http://stackoverflow.com/a/10331773/1992193 -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-not-detecting-MsiPackage-as-Present-when-already-installed-tp7589349p7589350.html Sent from the wix-users mailing list archive at Nabble.com. -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Automatically increment and synchronize version of product and bootstrapper
I was able to figure it out using DefineConstants in a BeforeBuild event to get the version of the project file and set it as a variable to be used in Bundle Version: Bundle.wxs: BuildVersion=%(AssemblyVersion.Version) -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Automatically-increment-and-synchronize-version-of-product-and-bootstrapper-tp7589213p7589219.html Sent from the wix-users mailing list archive at Nabble.com. -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Automatically increment and synchronize version of product and bootstrapper
So I figured out at least why the FileVersion.FileID isnt working as the FileID is declared in the 'Setup' project and this is the 'Bootstrapper' project. I still don't understand why *!(bind.packageVersion.MyApp)* results in *1.0.0.0* when the MyApp Project *AssemblyVersion *is set to *1.0.** -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Automatically-increment-and-synchronize-version-of-product-and-bootstrapper-tp7589213p7589215.html Sent from the wix-users mailing list archive at Nabble.com. -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] [SPAM] Error LGHT0094: Unresolved reference to symbol 'WixBootstrapperApplication:ManagedBootstrapperApplicationHost' in section 'Bundle:MyApp Bootstrapper'
Hello, Thank you for the quick reply! Can I not combine the WixBalExtensionExt and Custom/Managed BootstrapperApplication? Thanks, -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Error-LGHT0094-Unresolved-reference-to-symbol-WixBootstrapperApplication-ManagedBootstrapperApplicat-tp7589205p7589207.html Sent from the wix-users mailing list archive at Nabble.com. -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] [SPAM] Error LGHT0094: Unresolved reference to symbol 'WixBootstrapperApplication:ManagedBootstrapperApplicationHost' in section 'Bundle:MyApp Bootstrapper'
Hello, I am trying to create a custom Bootstrapper Application. I had it running this morning but after trying to implement the WiX Extended Bootstrapper Application (https://wixextba.codeplex.com/) I made too many changes at once and now I cannot build and cannot figure out why this error is being thrown. =Project layout=Bootstrapper <-- Bootstrapper project template--References:BootstrapperCustom (Project)Setup (Project)WixBalExtensionExtWixNetFxExtensionWixUIExtensionWixUtilExtensionBootstrapperCustom <-- Custom BootstrapperApplication (CustomBA : BootstrapperApplication)--References:BootstrapperCoreMicrosoft.Deployment.WindowsInstallerMyApp <-- Application to deploySetup <-- Setup project template for "MyApp"--References:LicenseCheck (Custom Action)MyApp (Project)WixBalExtensionExtWixUIExtension=Bundle.wxs=<?xml version="1.0" encoding="UTF-8"?><?include ..\Setup\Variables.wxi ?><Wix xmlns="http://schemas.microsoft.com/wix/2006/wi"; xmlns:util="http://schemas.microsoft.com/wix/UtilExtension"; xmlns:netfx="http://schemas.microsoft.com/wix/NetFxExtension"; xmlns:bal="http://schemas.microsoft.com/wix/BalExtension";> <Bundle Name="$(var.ProductName) Bootstrapper" Version="$(var.BuildVersion)" UpgradeCode="$(var.GUID_BOOTSTRAPPER)" Manufacturer="$(var.Manufacturer)" Copyright="Copyright © 2013, $(var.Manufacturer)" IconSourceFile="../$(var.ProductName)/Resources/Images/favicon.ico" SplashScreenSourceFile="../$(var.ProductName)/Resources/Images/$(var.ProductName).bmp" Condition="((VersionNT >= v5.1) AND (ServicePackLevel >= 3)) OR ((VersionNT >= v5.2) AND (ServicePackLevel >= 2)) OR (VersionNT >= v6.0)">=BUILD ERROR=7>-- Rebuild All started: Project: Setup, Configuration: Debug x86 --7>C:\Program Files (x86)\WiX Toolset v3.7\bin\Heat.exe dir ..\MyApp\bin\Debug\ -cg MyApp_Project -dr INSTALLLOCATION -scom -sreg -srd -gg -sfrag -out MyApp_Files.wxs7> C:\Program Files (x86)\WiX Toolset v3.7\bin\candle.exe -dDebug -d"DevEnvDir=C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\\" -d"SolutionDir=C:\Users\dirt\Documents\Visual Studio 2012\Projects\MyApp\MyApp\MyApp\\" -dSolutionExt=.sln -dSolutionFileName=MyApp.sln -dSolutionName=MyApp -d"SolutionPath=C:\Users\dirt\Documents\Visual Studio 2012\Projects\MyApp\MyApp\MyApp\MyApp.sln" -dConfiguration=Debug -dOutDir=bin\Debug\ -dPlatform=x86 -d"ProjectDir=C:\Users\dirt\Documents\Visual Studio 2012\Projects\MyApp\MyApp\MyApp\Setup\\" -dProjectExt=.wixproj -dProjectFileName=Setup.wixproj -dProjectName=Setup -d"ProjectPath=C:\Users\dirt\Documents\Visual Studio 2012\Projects\MyApp\MyApp\MyApp\Setup\Setup.wixproj" -d"TargetDir=C:\Users\dirt\Documents\Visual Studio 2012\Projects\MyApp\MyApp\MyApp\Setup\bin\Debug\\" -dTargetExt=.exe -dTargetFileName=MyApp.exe -dTargetName=MyApp -d"TargetPath=C:\Users\dirt\Documents\Visual Studio 2012\Projects\MyApp\MyApp\MyApp\Setup\bin\Debug\MyApp.exe" -dLicenseCheck.Configuration=Debug -d"LicenseCheck.FullConfiguration=Debug|x86" -dLicenseCheck.Platform=x86 -d"LicenseCheck.ProjectDir=C:\Users\dirt\Documents\Visual Studio 2012\Projects\MyApp\MyApp\MyApp\LicenseCheck\\" -dLicenseCheck.ProjectExt=.csproj -dLicenseCheck.ProjectFileName=LicenseCheck.csproj -dLicenseCheck.ProjectName=LicenseCheck -d"LicenseCheck.ProjectPath=C:\Users\dirt\Documents\Visual Studio 2012\Projects\MyApp\MyApp\MyApp\LicenseCheck\LicenseCheck.csproj" -d"LicenseCheck.TargetDir=C:\Users\dirt\Documents\Visual Studio 2012\Projects\MyApp\MyApp\MyApp\LicenseCheck\bin\Debug\\" -dLicenseCheck.TargetExt=.dll -dLicenseCheck.TargetFileName=LicenseCheck.dll -dLicenseCheck.TargetName=LicenseCheck -d"LicenseCheck.TargetPath=C:\Users\dirt\Documents\Visual Studio 2012\Projects\MyApp\MyApp\MyApp\LicenseCheck\bin\Debug\LicenseCheck.dll" -dMyApp.Configuration=Debug -d"MyApp.FullConfiguration=Debug|AnyCPU" -dMyApp.Platform=AnyCPU -d"MyApp.ProjectDir=C:\Users\dirt\Documents\Visual Studio 2012\Projects\MyApp\MyApp\MyApp\MyApp\\" -dMyApp.ProjectExt=.csproj -dMyApp.ProjectFileName=MyApp.csproj -dMyApp.ProjectName=MyApp -d"MyApp.ProjectPath=C:\Users\dirt\Documents\Visual Studio 2012\Projects\MyApp\MyApp\MyApp\MyApp\MyApp.csproj" -d"MyApp.TargetDir=C:\Users\dirt\Documents\Visual Studio 2012\Projects\MyApp\MyApp\MyApp\MyApp\bin\Debug\\" -dMyApp.TargetExt=.exe -dMyApp.TargetFileName=MyApp.exe -dMyApp.TargetName=MyApp -d"MyApp.TargetPath=C:\Users\dirt\Documents\Visual Studio 2012\Projects\MyApp\MyApp\MyApp\MyApp\bin\Debug\MyApp.exe" -out obj\Debug\ -
