You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some packages, such as SQL Server, have a number of dependencies, especially on older versions of Windows that may require reboots before installing the dependent package. It would be useful to be able to postpone these reboots until a particular checkpoint. I therefore propose a element. A reboot checkpoint is treated much like a package, and entered into a plan, and when the Burn engine comes to execute it, if any previously executed packages scheduled a reboot, Burn should reboot.
It should be able to be placed in a Chain or PackageGroup.
It should have an Id attribute, so that it can be referenced by other package's @after attribute.
It should have an After attribute, much like other package's @after attribute.
It should have InstallCondition attributes and UninstallCondition attributes to control its entry into the execution plan.
In chain with dotNet 4.0 installation reboot doesn't happens, even with dotNet return code 3010.
Without reboot dotNet doesn't work correctly.
It cause error on installing next package which use dotNet 4.0 during installation.
PS. This situation occured only on preloaded package (not on standard dotNet with RemotePayload).
Env: clean Windows 7 x64, Burn v3.8.520.0.
Some packages, such as SQL Server, have a number of dependencies, especially on older versions of Windows that may require reboots before installing the dependent package. It would be useful to be able to postpone these reboots until a particular checkpoint. I therefore propose a element. A reboot checkpoint is treated much like a package, and entered into a plan, and when the Burn engine comes to execute it, if any previously executed packages scheduled a reboot, Burn should reboot.
It should be able to be placed in a Chain or PackageGroup.
It should have an Id attribute, so that it can be referenced by other package's @after attribute.
It should have an After attribute, much like other package's @after attribute.
It should have InstallCondition attributes and UninstallCondition attributes to control its entry into the execution plan.
The text was updated successfully, but these errors were encountered: