Distributing a shared copy of the ClickOnce deployment manifest file (Ifs.Fnd.Explorer.application) to client PCs, rather than a shortcut to the IFS landing page, does this file need to be re-copied out to every client PC every time an IFS Update or Delivery is applied to the application instance?

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

Generally no — the ClickOnce manifest file itself is just a pointer, and ClickOnce automatically detects and pulls through the updated application version via that same manifest reference, without needing a fresh copy distributed after every routine Update or Delivery. The two specific situations that DO require redistributing a fresh copy of that manifest file to client PCs are: the file's own signing/encryption certificate expiring, or a specific update happening to directly affect or change that particular manifest file itself, an uncommon but possible case. Outside of those two specific triggers, the existing manifest file continues to correctly point users to the latest deployed IEE client version automatically.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions