Keep the working directories consistent between versions.
Some organizations have Carbon Black to monitor and block unauthorized code execution. I had previously whitelisted the intermediate directories for LinqPad, but the newest version uses different directories so everything needed to be whitelisted again. The people who configure these monitors aren't always the brightest or most responsive to requests, so it would be best to keep the paths consistent, so they don't need to be reconfigured for each future version.
-
Michael Miller commented
Yes, carbon black will block dlls and any executing code that is not signed. In order to make LINQPad work the temp directories and filenames need to be white listed. But if those change the new ones need to be whitelisted.