Does anyone know if MS is going to fix the issue where if you do a lot of builds and test runs of your app, at some point VBCSCompiler.exe (or many instances of it) stays in memory, causing issues . From my experience, this has caused an CSC.EXE Stopped Working error message. I have found a work-around for it for now (Exist VS, use Task Manager and kill all instances of VBCSCompiler.exe, delete the "Roslyn" folder from my project's BIN folder, and re-start VS). This works, but it's tiresome and if I'm doing several test builds and runs in a day, it can get time consuming to have to do this over and over again.
I hear that this is a problem that started in VS 2015 (not sure if it persists in 2017 as I haven't installed it yet) but I'm thinking that the majority of people may still be using VS 2015, and hopefully MS will fix this issue in their next Update. I do have Update 3 installed as I installed recently using the web installer.