More control over deleting compile cache

[Intaris]

I'd like sometimes to have more control over what to delete from the compiled cache.

If I am working on a certain project and I'm having trouble with RT deploys and inlined VI code change propagation (it's a real thing) then I have found out that deleting the compiled code cache can help a lot.  Thing is, I don't really want to delete all of the cache, only those related to a sub-set (current project / directory on disk).

It's not a huge deal-breaker but if the technical barriers are not great, it would be a nice choice to have.

[Intaris]

This issue still exists. While the compile cache is a great addition, there are so many corner cases where really weird things happen.

We've seem cases where the visible source code changes depending on the state of the compile cache, a thing which obviously should never happen. The code on disk should ALWAYS have priority. Same binary file, rename it (so that no cache exists for the new file) and suddenly the source code is different.

There are some issues which may be 0.01% issues with the usage, but they are enough to cause serious problems in larger projects. The number of users mentioning "weird" issues which are fixed by clearing the cache are increasing, probably due to the complexity of projects increasing.

Some tools to interact with the cache and clear only selected portions would be a very welcome addition. I don't want to clear ALL cached VIs when a single VI or repository is exhibiting a problem.

[joerg.hampel]

I just want to add that we also constantly run into the issues mentioned by Intaris, for larger projects to the extent of not even bothering trying to deploy anymore without clearing all cashes first. 

Any improvement here (robustness of LabVIEW and/or finer granularity in deleting or updating caches) would be very much appreciated.