Discussion:
[WiX-users] .NET Prerequisite, Burn, and the ARP
Colin Sim
2015-05-20 02:48:32 UTC
Permalink
When a .NET package is successfully installed as a prerequisite for our Burn bootstrapper application, and the user cancels the install, the bootstrapper package is still listed in the Add/Remove programs. I understand that the .NET package is part of the bundle but from a user's perspective none of the product has technically been installed. Especially, when someone takes a look in the Add/Remove programs window, the bundle is there, and they assume everything is in place.

Are there any settings to prevent this from happening? Alternatively, what are the strategies to deal with this scenario?

This e-mail contains IPFX information which may be privileged or confidential and is intended for use only by the individual(s) or entity named above. If you are not the intended recipient, note that disclosing, copying, distributing or using this information is prohibited. If you have received this e-mail in error, please advise immediately to the e-mail address above and permanently delete this message and any attachments. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. We monitor our e-mail system and may record your e-mails. Thank you.
Phill Hogland
2015-05-20 13:11:14 UTC
Permalink
I came across a different, but I suspect it might be a related issue,
discussed in this thread
<http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/RollbackBoundry-Can-t-Upgrade-or-uninstall-bundle-td7598888.html>
. Frankly because of other responsibilities, I set this issue aside and did
not fully dig into the cause or solution. In my case it was not the mba
prereq, but additional prereqs at the top of my chain (vc runtimes, and .Net
3.51) which I install but never uninstall. When I had a RollbackBoundary
immediately after a ExePackage with ExePackage/@Permanent="yes", and if
while processing a package after the RollbackBoundary, in certain situations
like user cancel, the rollback happened to the boundary, but the bundle was
left in the ARP. When this happens I could not find any way to get an
Uninstall (or an Upgrade) of that bundle to "work". The log simply reports
"success" which is correct since there is nothing in the chain that is not
permanent, to uninstall, but the ARP registration remains.

I eventually concluded that I should not use a RollbackBondary after a
'Permanent' package, and I also add a small simple MSI package immediately
after the permanent package, so that there is a high likelihood that it
installs. If a latter package fails, there remains something in the chain
for the Bundle to "uninstall", and then it removes the ARP registration.
It has been my intent to get back to this and setup a test scenario that I
can debug into and try to understand if my observations are accurate, and
then file a bug or figure out a fix, but I have not gotten back to this
issue. Sorry.



--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/NET-Prerequisite-Burn-and-the-ARP-tp7600376p7600382.html
Sent from the wix-users mailing list archive at Nabble.com.
Colin Sim
2015-05-20 18:48:16 UTC
Permalink
Phil: there's absolutely no need to apologise. All forum users (I know I am) appreciate your input and time spent helping out on the forum.

I'll need to look into this issue anyway as part of a project of mine (which I'll get back to soon I hope). I'll report back anything meaningful that I find. I'll certainly give your suggestion, regarding the use of a dummy package ago. If it works though, it still feels like a hack as opposed to a proper solution to me.

I haven't looked through the Burn engine code, but from my experience of using Burn to date (granted not very long) - it feels like at some earlier point in development, it was easier to piggy back of the bundle chain to support the runtime environment for the bootstrapper as opposed to having a clean and separate concept for prerequisite(s) specifically for the bootstrapper itself. Could any of the developers comment or share their insight into the design intent that has resulting in what we're seeing now?


-----Original Message-----
From: Phill Hogland [mailto:***@rimage.com]
Sent: Thursday, 21 May 2015 1:11 a.m.
To: wix-***@lists.sourceforge.net
Subject: Re: [WiX-users] .NET Prerequisite, Burn, and the ARP

I came across a different, but I suspect it might be a related issue, discussed in this thread <http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/RollbackBoundry-Can-t-Upgrade-or-uninstall-bundle-td7598888.html>
. Frankly because of other responsibilities, I set this issue aside and did not fully dig into the cause or solution. In my case it was not the mba prereq, but additional prereqs at the top of my chain (vc runtimes, and .Net
3.51) which I install but never uninstall. When I had a RollbackBoundary immediately after a ExePackage with ExePackage/@Permanent="yes", and if while processing a package after the RollbackBoundary, in certain situations like user cancel, the rollback happened to the boundary, but the bundle was left in the ARP. When this happens I could not find any way to get an Uninstall (or an Upgrade) of that bundle to "work". The log simply reports "success" which is correct since there is nothing in the chain that is not permanent, to uninstall, but the ARP registration remains.

I eventually concluded that I should not use a RollbackBondary after a 'Permanent' package, and I also add a small simple MSI package immediately after the permanent package, so that there is a high likelihood that it installs. If a latter package fails, there remains something in the chain for the Bundle to "uninstall", and then it removes the ARP registration.
It has been my intent to get back to this and setup a test scenario that I can debug into and try to understand if my observations are accurate, and then file a bug or figure out a fix, but I have not gotten back to this issue. Sorry.



--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/NET-Prerequisite-Burn-and-the-ARP-tp7600376p7600382.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-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
This e-mail contains IPFX information which may be privileged or confidential and is intended for use only by the individual(s) or entity named above. If you are not the intended recipient, note that disclosing, copying, distributing or using this information is prohibited. If you have received this e-mail in error, please advise immediately to the e-mail address above and permanently delete this message and any attachments. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. We monitor our e-mail system and may record your e-mails. Thank you.
Rob Mensching
2015-05-20 19:13:24 UTC
Permalink
IIRC, Burn should keep registration in ARP when the first non-permanent package is installed (aka: there is something Burn would do). A RollbackBoundary after the permanent packages *may* be necessary but my memory is fuzzy there.

_____________________________________________________________
Short replies here. Complete answers over there: http://www.firegiant.com/

-----Original Message-----
From: Colin Sim [mailto:***@ipfx.com]
Sent: Wednesday, May 20, 2015 11:48 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] .NET Prerequisite, Burn, and the ARP

Phil: there's absolutely no need to apologise. All forum users (I know I am) appreciate your input and time spent helping out on the forum.

I'll need to look into this issue anyway as part of a project of mine (which I'll get back to soon I hope). I'll report back anything meaningful that I find. I'll certainly give your suggestion, regarding the use of a dummy package ago. If it works though, it still feels like a hack as opposed to a proper solution to me.

I haven't looked through the Burn engine code, but from my experience of using Burn to date (granted not very long) - it feels like at some earlier point in development, it was easier to piggy back of the bundle chain to support the runtime environment for the bootstrapper as opposed to having a clean and separate concept for prerequisite(s) specifically for the bootstrapper itself. Could any of the developers comment or share their insight into the design intent that has resulting in what we're seeing now?
Jiri Tomek
2015-07-08 08:02:01 UTC
Permalink
Hello,
I have the same issue. I double-checked that .NET package is marked as
permanent and I tried both with and without rollback boundary but I still
get ARP entry right after .NET is installed as prerequisite. I'm using Wix
3.9.

My Chain is defined this way:
<Chain>
<PackageGroupRef Id="NetFx45Redist"/>
<RollbackBoundary />
<PackageGroupRef Id="TestPackage" />
</Chain>

The log from initial run is this:

[0690:0168][2015-07-08T00:29:07]i001: Burn v3.9.1006.0, Windows v6.1 (Build
7601: Service Pack 1), path:
C:\Users\Administrator\Desktop\TestInstaller.exe, cmdline: '-burn.unelevated
BurnPipe.{4303C9F0-DB96-41D1-A217-26466A0A9178}
{253C2727-CA99-43F7-B8B1-CF0835E221F0} 380 '
... snip ...
[0690:0168][2015-07-08T00:29:07]i000: Loading prerequisite bootstrapper
application because managed host could not be loaded, error: 0x80070490.
[0690:0464][2015-07-08T00:29:07]i000: Setting version variable
'WixBundleFileVersion' to value '1.0.0.0'
[0690:0168][2015-07-08T00:29:07]i100: Detect begin, 2 packages
[0690:0168][2015-07-08T00:29:07]i000: Registry key not found. Key =
'SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full'
[0690:0168][2015-07-08T00:29:07]i052: Condition 'PreviousInstallFolder'
evaluates to false.
[0690:0168][2015-07-08T00:29:07]i052: Condition 'NETFRAMEWORK45 >= 378389'
evaluates to false.
[0690:0168][2015-07-08T00:29:07]i101: Detected package: NetFx45Redist,
state: Absent, cached: None
[0690:0168][2015-07-08T00:29:07]i101: Detected package: TestPackage, state:
Absent, cached: None
[0690:0168][2015-07-08T00:29:07]i199: Detect complete, result: 0x0
[0690:0168][2015-07-08T00:29:09]i200: Plan begin, 2 packages, action:
Install
[0690:0168][2015-07-08T00:29:09]w321: Skipping dependency registration on
package with no dependency providers: NetFx45Redist
[0690:0168][2015-07-08T00:29:09]i000: Setting string variable
'NetFx45FullLog' to value
'C:\Users\ADMINI~1\AppData\Local\Temp\TestInstaller_20150708002907_0_NetFx45Redist.log'
[0690:0168][2015-07-08T00:29:09]i201: Planned package: NetFx45Redist, state:
Absent, default requested: Present, ba requested: Present, execute: Install,
rollback: None, cache: Yes, uncache: No, dependency: None
[0690:0168][2015-07-08T00:29:09]i201: Planned package: TestPackage, state:
Absent, default requested: Absent, ba requested: None, execute: None,
rollback: None, cache: No, uncache: No, dependency: None
[0690:0168][2015-07-08T00:29:09]i299: Plan complete, result: 0x0
[0690:0168][2015-07-08T00:29:09]i300: Apply begin
[017C:054C][2015-07-08T00:29:09]i360: Creating a system restore point.
[017C:054C][2015-07-08T00:29:09]i362: System restore disabled, system
restore point not created.
[017C:054C][2015-07-08T00:29:09]i000: Caching bundle from:
'C:\Users\ADMINI~1\AppData\Local\Temp\{380d557e-ec88-4923-9924-a37299972102}\.be\TestInstaller.exe'
to: 'C:\ProgramData\Package
Cache\{380d557e-ec88-4923-9924-a37299972102}\TestInstaller.exe'
[017C:054C][2015-07-08T00:29:09]i320: Registering bundle dependency
provider: {380d557e-ec88-4923-9924-a37299972102}, version: 1.0.0.0
[017C:0504][2015-07-08T00:29:09]i305: Verified acquired payload:
NetFx45Redist at path: C:\ProgramData\Package
Cache\.unverified\NetFx45Redist, moving to: C:\ProgramData\Package
Cache\CD57380514DC157DF75A09D3E54C96D1DF3DF51A\redist\dotnetfx45_full_x86_x64.exe.
[017C:054C][2015-07-08T00:29:09]i301: Applying execute package:
NetFx45Redist, action: Install, path: C:\ProgramData\Package
Cache\CD57380514DC157DF75A09D3E54C96D1DF3DF51A\redist\dotnetfx45_full_x86_x64.exe,
arguments: '"C:\ProgramData\Package
Cache\CD57380514DC157DF75A09D3E54C96D1DF3DF51A\redist\dotnetfx45_full_x86_x64.exe"
/q /norestart /ChainingPackage "Test Installer" /log
"C:\Users\ADMINI~1\AppData\Local\Temp\TestInstaller_20150708002907_0_NetFx45Redist.log.html"'
[0690:0168][2015-07-08T00:33:20]i319: Applied execute package:
NetFx45Redist, result: 0x0, restart: None
[0690:0168][2015-07-08T00:33:20]i399: Apply complete, result: 0x0, restart:
None, ba requested restart: No
[0690:0168][2015-07-08T00:33:20]i500: Shutting down, exit code: 0x0
[0690:0168][2015-07-08T00:33:20]i000: The prerequisites were successfully
installed. The bootstrapper application will be reloaded.
[0690:0168][2015-07-08T00:33:20]i006: Bootstrapper application requested to
be reloaded.
[0690:0168][2015-07-08T00:33:20]i000: Loading managed bootstrapper
application.
[0690:0168][2015-07-08T00:33:20]i000: Creating BA thread to run
asynchronously.
[0690:060C][2015-07-08T00:33:20]i000: Starting Bootstrapper. Assembly
CodeBase:file:///C:/Users/Administrator/AppData/Local/Temp/{380d557e-ec88-4923-9924-a37299972102}/.ba1/TestInstaller.DLL
[0690:060C][2015-07-08T00:33:20]i000: Command Action: Install Resume: None
Restart: Prompt Display: Full LayoutDir: Passthrough: False Relation: None
... snip ...
[0690:060C][2015-07-08T00:33:50]i000: Exiting UI.
[0690:0168][2015-07-08T00:33:50]i500: Shutting down, exit code: 0xffffffff
[0690:0168][2015-07-08T00:33:50]i000: Shutting down without restart.
... snip ...
[0690:0168][2015-07-08T00:33:50]i007: Exit code: 0xffffffff, restarting: No




--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/NET-Prerequisite-Burn-and-the-ARP-tp7600376p7600835.html
Sent from the wix-users mailing list archive at Nabble.com.
Rob Mensching
2015-07-08 17:22:44 UTC
Permalink
Ahh, the prereqba completed successfully. So the bundle was successfully installed before being restarted to load the ManagedBA. That basically makes sense.

_______________________________________________________________
FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/

-----Original Message-----
From: Jiri Tomek [mailto:***@volny.cz]
Sent: Wednesday, July 8, 2015 1:02 AM
To: wix-***@lists.sourceforge.net
Subject: Re: [WiX-users] .NET Prerequisite, Burn, and the ARP

Hello,
I have the same issue. I double-checked that .NET package is marked as permanent and I tried both with and without rollback boundary but I still get ARP entry right after .NET is installed as prerequisite. I'm using Wix 3.9.

My Chain is defined this way:
<Chain>
<PackageGroupRef Id="NetFx45Redist"/>
<RollbackBoundary />
<PackageGroupRef Id="TestPackage" />
</Chain>

The log from initial run is this:

[0690:0168][2015-07-08T00:29:07]i001: Burn v3.9.1006.0, Windows v6.1 (Build
7601: Service Pack 1), path:
C:\Users\Administrator\Desktop\TestInstaller.exe, cmdline: '-burn.unelevated BurnPipe.{4303C9F0-DB96-41D1-A217-26466A0A9178}
{253C2727-CA99-43F7-B8B1-CF0835E221F0} 380 '
... snip ...
[0690:0168][2015-07-08T00:29:07]i000: Loading prerequisite bootstrapper application because managed host could not be loaded, error: 0x80070490.
[0690:0464][2015-07-08T00:29:07]i000: Setting version variable 'WixBundleFileVersion' to value '1.0.0.0'
[0690:0168][2015-07-08T00:29:07]i100: Detect begin, 2 packages
[0690:0168][2015-07-08T00:29:07]i000: Registry key not found. Key = 'SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full'
[0690:0168][2015-07-08T00:29:07]i052: Condition 'PreviousInstallFolder'
evaluates to false.
[0690:0168][2015-07-08T00:29:07]i052: Condition 'NETFRAMEWORK45 >= 378389'
evaluates to false.
[0690:0168][2015-07-08T00:29:07]i101: Detected package: NetFx45Redist,
state: Absent, cached: None
[0690:0168][2015-07-08T00:29:07]i101: Detected package: TestPackage, state:
Absent, cached: None
[0690:0168][2015-07-08T00:29:07]i199: Detect complete, result: 0x0
[0690:0168][2015-07-08T00:29:09]i200: Plan begin, 2 packages, action:
Install
[0690:0168][2015-07-08T00:29:09]w321: Skipping dependency registration on package with no dependency providers: NetFx45Redist
[0690:0168][2015-07-08T00:29:09]i000: Setting string variable 'NetFx45FullLog' to value 'C:\Users\ADMINI~1\AppData\Local\Temp\TestInstaller_20150708002907_0_NetFx45Redist.log'
[0690:0168][2015-07-08T00:29:09]i201: Planned package: NetFx45Redist, state:
Absent, default requested: Present, ba requested: Present, execute: Install,
rollback: None, cache: Yes, uncache: No, dependency: None
[0690:0168][2015-07-08T00:29:09]i201: Planned package: TestPackage, state:
Absent, default requested: Absent, ba requested: None, execute: None,
rollback: None, cache: No, uncache: No, dependency: None
[0690:0168][2015-07-08T00:29:09]i299: Plan complete, result: 0x0
[0690:0168][2015-07-08T00:29:09]i300: Apply begin
[017C:054C][2015-07-08T00:29:09]i360: Creating a system restore point.
[017C:054C][2015-07-08T00:29:09]i362: System restore disabled, system restore point not created.
[017C:054C][2015-07-08T00:29:09]i000: Caching bundle from:
'C:\Users\ADMINI~1\AppData\Local\Temp\{380d557e-ec88-4923-9924-a37299972102}\.be\TestInstaller.exe'
to: 'C:\ProgramData\Package
Cache\{380d557e-ec88-4923-9924-a37299972102}\TestInstaller.exe'
[017C:054C][2015-07-08T00:29:09]i320: Registering bundle dependency
provider: {380d557e-ec88-4923-9924-a37299972102}, version: 1.0.0.0
[017C:0504][2015-07-08T00:29:09]i305: Verified acquired payload:
NetFx45Redist at path: C:\ProgramData\Package Cache\.unverified\NetFx45Redist, moving to: C:\ProgramData\Package Cache\CD57380514DC157DF75A09D3E54C96D1DF3DF51A\redist\dotnetfx45_full_x86_x64.exe.
[017C:054C][2015-07-08T00:29:09]i301: Applying execute package:
NetFx45Redist, action: Install, path: C:\ProgramData\Package Cache\CD57380514DC157DF75A09D3E54C96D1DF3DF51A\redist\dotnetfx45_full_x86_x64.exe,
arguments: '"C:\ProgramData\Package
Cache\CD57380514DC157DF75A09D3E54C96D1DF3DF51A\redist\dotnetfx45_full_x86_x64.exe"
/q /norestart /ChainingPackage "Test Installer" /log "C:\Users\ADMINI~1\AppData\Local\Temp\TestInstaller_20150708002907_0_NetFx45Redist.log.html"'
[0690:0168][2015-07-08T00:33:20]i319: Applied execute package:
NetFx45Redist, result: 0x0, restart: None
[0690:0168][2015-07-08T00:33:20]i399: Apply complete, result: 0x0, restart:
None, ba requested restart: No
[0690:0168][2015-07-08T00:33:20]i500: Shutting down, exit code: 0x0
[0690:0168][2015-07-08T00:33:20]i000: The prerequisites were successfully installed. The bootstrapper application will be reloaded.
[0690:0168][2015-07-08T00:33:20]i006: Bootstrapper application requested to be reloaded.
[0690:0168][2015-07-08T00:33:20]i000: Loading managed bootstrapper application.
[0690:0168][2015-07-08T00:33:20]i000: Creating BA thread to run asynchronously.
[0690:060C][2015-07-08T00:33:20]i000: Starting Bootstrapper. Assembly CodeBase:file:///C:/Users/Administrator/AppData/Local/Temp/{380d557e-ec88-4923-9924-a37299972102}/.ba1/TestInstaller.DLL
[0690:060C][2015-07-08T00:33:20]i000: Command Action: Install Resume: None
Restart: Prompt Display: Full LayoutDir: Passthrough: False Relation: None ... snip ...
[0690:060C][2015-07-08T00:33:50]i000: Exiting UI.
[0690:0168][2015-07-08T00:33:50]i500: Shutting down, exit code: 0xffffffff
[0690:0168][2015-07-08T00:33:50]i000: Shutting down without restart.
... snip ...
[0690:0168][2015-07-08T00:33:50]i007: Exit code: 0xffffffff, restarting: No
soundararajan dhakshinamoorthy
2015-07-09 01:36:48 UTC
Permalink
Hi Rob,

Do you have any advice on how to handle prerequisites (not prereqmba)
without adding an entry ?

Thanks in advance
Sound
Post by Rob Mensching
Ahh, the prereqba completed successfully. So the bundle was successfully
installed before being restarted to load the ManagedBA. That basically
makes sense.
_______________________________________________________________
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-----Original Message-----
Sent: Wednesday, July 8, 2015 1:02 AM
Subject: Re: [WiX-users] .NET Prerequisite, Burn, and the ARP
Hello,
I have the same issue. I double-checked that .NET package is marked as
permanent and I tried both with and without rollback boundary but I still
get ARP entry right after .NET is installed as prerequisite. I'm using Wix
3.9.
<Chain>
<PackageGroupRef Id="NetFx45Redist"/>
<RollbackBoundary />
<PackageGroupRef Id="TestPackage" />
</Chain>
[0690:0168][2015-07-08T00:29:07]i001: Burn v3.9.1006.0, Windows v6.1 (Build
'-burn.unelevated BurnPipe.{4303C9F0-DB96-41D1-A217-26466A0A9178}
{253C2727-CA99-43F7-B8B1-CF0835E221F0} 380 '
... snip ...
[0690:0168][2015-07-08T00:29:07]i000: Loading prerequisite bootstrapper
application because managed host could not be loaded, error: 0x80070490.
[0690:0464][2015-07-08T00:29:07]i000: Setting version variable
'WixBundleFileVersion' to value '1.0.0.0'
[0690:0168][2015-07-08T00:29:07]i100: Detect begin, 2 packages
[0690:0168][2015-07-08T00:29:07]i000: Registry key not found. Key =
'SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full'
[0690:0168][2015-07-08T00:29:07]i052: Condition 'PreviousInstallFolder'
evaluates to false.
[0690:0168][2015-07-08T00:29:07]i052: Condition 'NETFRAMEWORK45 >= 378389'
evaluates to false.
[0690:0168][2015-07-08T00:29:07]i101: Detected package: NetFx45Redist,
state: Absent, cached: None
Absent, cached: None
[0690:0168][2015-07-08T00:29:07]i199: Detect complete, result: 0x0
Install
[0690:0168][2015-07-08T00:29:09]w321: Skipping dependency registration on
package with no dependency providers: NetFx45Redist
[0690:0168][2015-07-08T00:29:09]i000: Setting string variable
'NetFx45FullLog' to value
'C:\Users\ADMINI~1\AppData\Local\Temp\TestInstaller_20150708002907_0_NetFx45Redist.log'
Absent, default requested: Present, ba requested: Present, execute: Install,
rollback: None, cache: Yes, uncache: No, dependency: None
Absent, default requested: Absent, ba requested: None, execute: None,
rollback: None, cache: No, uncache: No, dependency: None
[0690:0168][2015-07-08T00:29:09]i299: Plan complete, result: 0x0
[0690:0168][2015-07-08T00:29:09]i300: Apply begin
[017C:054C][2015-07-08T00:29:09]i360: Creating a system restore point.
[017C:054C][2015-07-08T00:29:09]i362: System restore disabled, system
restore point not created.
'C:\Users\ADMINI~1\AppData\Local\Temp\{380d557e-ec88-4923-9924-a37299972102}\.be\TestInstaller.exe'
to: 'C:\ProgramData\Package
Cache\{380d557e-ec88-4923-9924-a37299972102}\TestInstaller.exe'
[017C:054C][2015-07-08T00:29:09]i320: Registering bundle dependency
provider: {380d557e-ec88-4923-9924-a37299972102}, version: 1.0.0.0
NetFx45Redist at path: C:\ProgramData\Package
Cache\.unverified\NetFx45Redist, moving to: C:\ProgramData\Package
Cache\CD57380514DC157DF75A09D3E54C96D1DF3DF51A\redist\dotnetfx45_full_x86_x64.exe.
NetFx45Redist, action: Install, path: C:\ProgramData\Package
Cache\CD57380514DC157DF75A09D3E54C96D1DF3DF51A\redist\dotnetfx45_full_x86_x64.exe,
arguments: '"C:\ProgramData\Package
Cache\CD57380514DC157DF75A09D3E54C96D1DF3DF51A\redist\dotnetfx45_full_x86_x64.exe"
/q /norestart /ChainingPackage "Test Installer" /log
"C:\Users\ADMINI~1\AppData\Local\Temp\TestInstaller_20150708002907_0_NetFx45Redist.log.html"'
NetFx45Redist, result: 0x0, restart: None
None, ba requested restart: No
[0690:0168][2015-07-08T00:33:20]i500: Shutting down, exit code: 0x0
[0690:0168][2015-07-08T00:33:20]i000: The prerequisites were successfully
installed. The bootstrapper application will be reloaded.
[0690:0168][2015-07-08T00:33:20]i006: Bootstrapper application requested to be reloaded.
[0690:0168][2015-07-08T00:33:20]i000: Loading managed bootstrapper application.
[0690:0168][2015-07-08T00:33:20]i000: Creating BA thread to run asynchronously.
[0690:060C][2015-07-08T00:33:20]i000: Starting Bootstrapper. Assembly
CodeBase:file:///C:/Users/Administrator/AppData/Local/Temp/{380d557e-ec88-4923-9924-a37299972102}/.ba1/TestInstaller.DLL
[0690:060C][2015-07-08T00:33:20]i000: Command Action: Install Resume: None
Restart: Prompt Display: Full LayoutDir: Passthrough: False Relation: None ... snip ...
[0690:060C][2015-07-08T00:33:50]i000: Exiting UI.
[0690:0168][2015-07-08T00:33:50]i500: Shutting down, exit code: 0xffffffff
[0690:0168][2015-07-08T00:33:50]i000: Shutting down without restart.
... snip ...
[0690:0168][2015-07-08T00:33:50]i007: Exit code: 0xffffffff, restarting: No
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--
-Soundararajan Dhakshinamoorthy
Rob Mensching
2015-07-09 04:32:22 UTC
Permalink
Add feature to Burn.

_______________________________________________________________
FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/

-----Original Message-----
From: soundararajan dhakshinamoorthy [mailto:***@gmail.com]
Sent: Wednesday, July 8, 2015 6:37 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] .NET Prerequisite, Burn, and the ARP

Hi Rob,

Do you have any advice on how to handle prerequisites (not prereqmba) without adding an entry ?

Thanks in advance
Sound
soundararajan dhakshinamoorthy
2015-07-10 02:47:42 UTC
Permalink
Hi,
Added the issue ,
http://wixtoolset.org/issues/4822

We will try to contribute to the issue :-).

Thanks,
Sound
Post by Rob Mensching
Add feature to Burn.
_______________________________________________________________
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-----Original Message-----
Sent: Wednesday, July 8, 2015 6:37 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] .NET Prerequisite, Burn, and the ARP
Hi Rob,
Do you have any advice on how to handle prerequisites (not prereqmba)
without adding an entry ?
Thanks in advance
Sound
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--
-Soundararajan Dhakshinamoorthy
Rob Mensching
2015-07-10 04:26:41 UTC
Permalink
Cool. It's a very big feature. So you'll want to do all this first: http://wixtoolset.org/development/ Also, a WIP (http://wixtoolset.org/development/wips/0000-wix-improvement-proposal/) will definitely be in order.

_______________________________________________________________
FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/

-----Original Message-----
From: soundararajan dhakshinamoorthy [mailto:***@gmail.com]
Sent: Thursday, July 9, 2015 7:48 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] .NET Prerequisite, Burn, and the ARP

Hi,
Added the issue ,
http://wixtoolset.org/issues/4822

We will try to contribute to the issue :-).

Thanks,
Sound
Post by Rob Mensching
Add feature to Burn.
_______________________________________________________________
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-----Original Message-----
From: soundararajan dhakshinamoorthy
Sent: Wednesday, July 8, 2015 6:37 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] .NET Prerequisite, Burn, and the ARP
Hi Rob,
Do you have any advice on how to handle prerequisites (not prereqmba)
without adding an entry ?
Thanks in advance
Sound
----------------------------------------------------------------------
-------- Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--
-Soundararajan Dhakshinamoorthy
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
soundararajan dhakshinamoorthy
2015-07-11 01:35:15 UTC
Permalink
Ok, Rob, I will take a look into those and first write the WIP. Sounds like
a good way to start in a unknown territory.

Thanks
Soundararajan
Post by Rob Mensching
http://wixtoolset.org/development/ Also, a WIP (
http://wixtoolset.org/development/wips/0000-wix-improvement-proposal/)
will definitely be in order.
_______________________________________________________________
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-----Original Message-----
Sent: Thursday, July 9, 2015 7:48 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] .NET Prerequisite, Burn, and the ARP
Hi,
Added the issue ,
http://wixtoolset.org/issues/4822
We will try to contribute to the issue :-).
Thanks,
Sound
Post by Rob Mensching
Add feature to Burn.
_______________________________________________________________
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-----Original Message-----
From: soundararajan dhakshinamoorthy
Sent: Wednesday, July 8, 2015 6:37 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] .NET Prerequisite, Burn, and the ARP
Hi Rob,
Do you have any advice on how to handle prerequisites (not prereqmba)
without adding an entry ?
Thanks in advance
Sound
----------------------------------------------------------------------
-------- Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--
-Soundararajan Dhakshinamoorthy
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that you
need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--
-Soundararajan Dhakshinamoorthy
Jiri Tomek
2015-07-13 10:22:38 UTC
Permalink
So just to make sure, the current behavior is kind of "by design" and
currently there is no way how to not get ARP entry if .NET prereqba
succeeds? It needs to be implemented as a new feature to Burn?



--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/NET-Prerequisite-Burn-and-the-ARP-tp7600376p7600875.html
Sent from the wix-users mailing list archive at Nabble.com.
Rob Mensching
2015-07-13 16:30:05 UTC
Permalink
Yes. There are very good reasons why Burn behaves the way it does today and handling this case requires additional (non-trivial) code (not fixing existing code).

_______________________________________________________________
FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/

-----Original Message-----
From: Jiri Tomek [mailto:***@volny.cz]
Sent: Monday, July 13, 2015 3:23 AM
To: wix-***@lists.sourceforge.net
Subject: Re: [WiX-users] .NET Prerequisite, Burn, and the ARP

So just to make sure, the current behavior is kind of "by design" and currently there is no way how to not get ARP entry if .NET prereqba succeeds? It needs to be implemented as a new feature to Burn?
Phill Hogland
2015-07-13 18:34:57 UTC
Permalink
I believe that there 'may' be a bug in the existing implementation along the
lines that Colin described or and related to the comment "Burn should keep
registration in ARP when the first non-permanent package is installed (aka:
there is something Burn would do).". In the scenarios where I had
difficulty I could not do an Uninstall or a Major Upgrade of a Burn chain
which had previously failed after only successfully installing 'permanent'
items in the chain. To get past this issue at the time I removed a Rollback
boundary which immediately followed the last permanent item in the chain
(just before the non-permanent item in the chain which had failed) in the
original installation. While I never did find a way to uninstall the
original failed setup, every since I removed the RollbackBoundary from my
chain I have not been able to recreate the problem scenario. So I think
there might be a problem in handling this scenario in 3.9/3.10 but I did not
go back an validate my memory that this did not happen in 3.8, nor have I
had a chance to setup a more indepth debug to see if I can track down where
the problem is. I suspect that the non-trivial new feature issue of making
Burn behave like a fire-and-forget bootstrapper is a separate issue (which I
do not have an interest in).



--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/NET-Prerequisite-Burn-and-the-ARP-tp7600376p7600877.html
Sent from the wix-users mailing list archive at Nabble.com.

Loading...