Hello to the JUCE team!
Recently, after a JUCE version update, I remarked that something in the base code broke my usual development workflow. I code my plug-ins on Windows 10 before porting them to mac OS, using Visual Studio 2019. I have the DAW Reaper 64 bits opened all the time, with a very useful setting being checked (Reaper preferences > Plug-ins > VST > allow complete unload of VST plug-ins).
This way, I can compile my project, and without opening / closing my DAW all the time, I can just load the plug-in in Reaper, delete the instance, re-compile, load the plug-in, delete the instance, re-compile etc.
But now, this doesn’t work anymore, because Reaper can’t unload fully the plug-in when I delete any instance. To be able to recompile the plug-in and copy it where it can be loaded again, I need now to close Reaper and open it again.
With the very last version of JUCE from the develop branch, this problem happens all the time, for example if I create a new plug-in straight from the Projucer template, and I guess it might have implications in other contexts too obviously. However, if I replace the 6.1.5 juce_audio_basics module with say the 6.0.5 version, the plug-in still compile fine, but the problem diseappears.
Thanks in advance!