Only the step 1 is necessary - step 2 and 3 are likely to cause problems, so I’d recommend re-saving your project in the Projucer.
After that, in Visual Studio, you should see a sidebar with the names of the different targets in the solution. In particular, there should be separate VST3 and Standalone targets. To build and test the Standalone, right-click the Standalone target, and select “Set as startup project”. Now, the “Run” button will build the Standalone and launch it under the debugger.
Thanks for quick response @reuk !
I tried as you mentioned here, but on setting standalone as startup project, encountered this error, #error: to compile audiounitv3 and/or standalone plug-ins, you need to add the juce_audio_utils and juce_audio_devices modules!
I know it’s pretty straight forward, but I am using juce as submodule directly from JUCE git repository.
How to deal with that?
Adding it in .jucer would help?
@reuk on changing the project settings to build standalone plugin,
I ran into the exception thrown when trying to build the project, which mentions
JUCE Assertion failure in juce_AudioProcessorValueTreeState.cpp:315
I did some searching, and found the related topic,
As discussed here, I added treeState.state = ValueTree("MyPlugin"); explicitly. (after adding parameters)
But still running into same exception,
and one thing to mention, I get this exception, only when building in standalone, vst3 builds successfully.