BinaryCache causes incorrect results when DLL is updated
ClxS opened this issue · 1 comments
This is an issue I ran into when working on exporting a third party library as a DLL. My first attempt failed at setting up the dllexport failed, I verified this with Dependencies.
I then fixed my issue, rebuilt, and to my surprise Dependencies still reports that the DLL has no exported symbols.
I did not know about the binary caching mechanism at the time so assumed I had made a mistake, causing a wild goose chase. I eventually figured it out when I copied the DLL somewhere else and then re-checked with Dependencies, and magically it showed the dllexports I had been looking for!
Should BinaryCache at very least verify that the datetime of the cache entry is newer than the file being checked to prevent this issue in the future? or have the caching behaviour as a UI configurable option.