User Modified Appware

In MSI/Deployment terms, Modified appware files constitute un-versioned, language neutral files, whose "Created Date" and "Modified Date" differ. However, if appware files have been moved or handled in certain ways, then it is possible that the "Created Date" and "Modified Date" will not differ, in which case the file replacement behavior of the installation will be different.

In the case where an appware files "Created Date" and "Modified Date" is different, no MSI will ever overwrite such a file. So Modified appware will never be upgraded (by default), changed or bug fixed by an AVEVA MSI or Patch.

In the case where a modified appware files "Created Date" and "Modified Date" does not differ, the appware file with the newest date will prevail (by default). This scenario is most likely to happen when installing a Patch or an MSI which is not classed as a "Service Pack" or a "Full Release", since releases with more minor designations are not side-by-side deployable, as they are intended as upgrades to pre-existing releases.

Once appware has been modified, it must fall to the author/owner to maintain the changes, since there is no reliable way to reconcile code differences. In extreme cases this may mean that AVEVA installations cannot be used to deploy appware, and those clients must make their own code merges.