Training
Module
Perform custom updates in a Power Apps canvas app - Training
With some Power Apps canvas apps, a form isn't the solution. This module focuses on how to perform custom updates when your data isn't in a form.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
It is not possible to eliminate all circumstances under which the application of a patch may require access to the original installation source.
Adhere to following points to minimize the possibility that your patch will require access to the original source:
Access to the original installation sources may be required to apply the patch in the following cases:
The patch applies to a feature that is currently run from source. In this case, the feature is transitioned from the run-from-source state to the local state.
The patch applies to a component that has a missing or corrupted file.
The patch applies to a file in a component that also contains unversioned files with no MsiFileHash entries. A populated MsiFileHash Table is required to prevent unnecessary recopying of unversioned files from the source location.
The patch was applied with a REINSTALLMODE of amus or emus. This option is dangerous in that it performs file copy operations regardless of file version. This can lead to down-reving of files and almost always requires the source. The recommended REINSTALLMODE value is omus.
The cached package for the product is missing. The cached package is needed for application of a patch. The cached package is stored in the %windir%\Installer folder.
The package is authored to make a call to the ResolveSource Action. This action should generally be avoided or conditionalized appropriately, because its execution always results in an access to the source.
The package has a custom action that attempts to access the source in some manner. The most common example is a type 23 concurrent installation custom action.
Note
Concurrent installations are not recommended for the installation of applications intended for release to the public. For information about concurrent installations please see Concurrent Installations.
The patch package consists of binary patches that do not apply to the current version of the file on the computer.
Consider the following example where Windows Installer requires access to the original source when applying a patch:
Access to the original installation sources may be required to remove a patch if the Windows Installer has not stored baseline information about the patch. Beginning with Windows Installer 3.0, the installer selectively saves baseline information about files when they are updated. For more information about the baseline cache, see Reducing Patch Size .
Training
Module
Perform custom updates in a Power Apps canvas app - Training
With some Power Apps canvas apps, a form isn't the solution. This module focuses on how to perform custom updates when your data isn't in a form.