Since a couple of days ago when Visual Studio 2022 was updated to v17.12.3 I’ve been unable to build previously-working VST3 JUCE projects. Builds end with error MSB3073 and the resulting VST3 won’t load. (Also just realised that the Standalone build won’t run.)
I’m using Juce 8.0.3 and VS 17.12.3 and my VST3 projects compile fine, once I figured out the font changes from 7.
I’m using the Projucer to launch VS, are you?
Hi DaveH, thanks for confirming that this should work. I use Projucer also. Everything built fine until a couple of days ago. I’ll try doing a repair install of VS and see if that helps.
Update: VS doesn’t have a repair install option so I couldn’t try that. The actual error I’m getting is in the final copy stage where it copies ‘MyPlugin.dll’ to ‘MyPlugin.vst3\Contents\x86_64-win\MyPlugin.vst3’
A stab in dark, as they say:
I would also delete the JUCE folder and re-clone it to what ever version you are using.
Check that the folder being copied to is not protected, and manually delete the plug-in from there first.
The copy stage is in ‘Build Events->Post Build’ part of properties under VST 3. Make sure the destination of that copy is not protected.
This is quite unusual, do you have any anti-virus software that may be stopping it?
You can repair and change anything in Visual Studio by running the installer and selecting ‘more’ - see screenshot.
But it probably isn’t the problem here.
I’ve had this error in the past because the case of some file changed (i.e. “someFile.h → somefile.h”) or because a previously-existing build-products folder no longer exists, or … worse … some internal cache folder that the IDE expects to exist, no longer exists.
Try re-cloning your whole project in a new path and rebuilding everything, including any submodules (i.e. JUCE/tracktion) from scratch.
Also, it has to be said, this is why we separate build and development environments by putting builds in a VM, and isolating builds from development-tool hassles, and don’t update your tools in the builder-VM until you get everything sorted on your developer workstation, mmkay…
Update: I found VS installer’s repair install option (under ‘more’ dropdown in the main screen), used it and the problem has gone. Thank you DaveH and ibisum.