Cleaning office add-in cache

Question

I have taken over a previously written office add-in with yeoman. I have been changing settings and else but after the initial install to see how far it has gone I believe my outlook client has stored some kind of cache. When I try to install the updated version it still holds the logos and settings for the previous version but when install it on a system which did not have a previous version of it its all good.

Any suggestions help. I have tried deleting my local profile file and recreate it by relaunching outlook but that does not seem to have effect on the whole process.

Thanks

EDIT:

I am talking about the Outlook standalone client.

Answer 1

Outlook Desktop for Windows add-in runs in iFrame of IE Web browser control. To clean up the cache of the add-in open IE browser, go to settings and remove cache. Re-launch your add-in and it should be as good as new.

Outlook for web user may run under supported browsers. In this case go to settings of the web browser used and remove the cache of this browser.

Outlook Desktop for Mac add-in runs under some kind of variation of web browser control (built in with Office 2016 for Mac) and how to remove cache over here is still puzzle for me.

If your application uses RoamingSettings object, take a look if you saveAsync any custom properties and remove them as you need with following saveAsync.

EDIT:

Of cause the described methods above are for your/QA/dev use only. For your customers you, as developer, has to take care of the cache for the files you have changed, when posting new release. As your add-in is nothing else as website, use web technology to re-fresh cache of the browser. There are many ways to achieve that. For example you may change location of the files for new release ...

<script src="/v1.0/Commands.js" type="text/javascript"></script>
<script src="/v1.1/Commands.js" type="text/javascript"></script>

or add some random parameter to the sources file ...

<script src="Commands.js?version=a56b34a87" type="text/javascript"></script>

and so on. Those simple methods will force browser to reload the file content.