Search code examples
outlookoffice-jsoutlook-addinoffice-addinsoutlook-web-addins

When updating an Outlook Add-In, how can I force Outlook to recognise the update i.e. stop the browser etc. from caching the old version?


We are finding that updating an Outlook App-In results in a long propagation time (more than hours, possibly a day or more); for development purposes this can be circumvented by a) using the web app, rather than Desktop b) using an in-private browser - but that is no use for production deployment ...

I'm updating using Filezilla (an FTP client), as it's fast

Re-starting Outlook, even re-booting the device, does not seem to help

Is there any work-around simple enough for end users who use Outlook Desktop?


Solution

  • You can configure the Cache-Control HTTP header fields that hold directives (instructions) — in both requests and responses — that control caching in browsers and shared caches (e.g. Proxies, CDNs). So, when the browser requests a file, you instruct the browser how frequently a file should be requested anew from the server.

    If you have access to users machines you may Clear the Office cache. To clear the Office cache on Windows 10 when the add-in is running in Microsoft Edge, you can use the Microsoft Edge DevTools.