You cannot run plugins on windows, that were compiled for OSX. There exists a process called cross-compiling, which means you compile for a different platform other than the one you run the compiler on. But that is complicated and neither XCode nor Visual Studio support that out of the box afaik.
The route to go is to copy your juce project to a windows box and have the projucer to create a visualStudio project and compile it in VisualStudio (the community edition is free, you can use different IDEs as well, but that usually leads to more fiddling).
To test your plugin, there is
- juce plugin host: find it in the examples of projucer, pro is that is very small and you can debug into the host as well (hosts AU components, VST and VST3)
- AuLab is also shipped with OSX or maybe bundeled with XCode. Also a minimalistic host (for AU components only)
- auval is a test script that will check your component for errors that would lead to exclude your plugin from hosts (for AU components only)
You can use any other host, many have a 1 month trial periode. When you start to market your plugin, i.e. you have a website and a video of your plugin prototype, you might try to ask host manufacturers, if they give you a NFR license to test compatibility. Their generosity is very variable form here to take it via I keep you waiting for two months, or here is a one month license up to no reply, YMMV.
Which host to test depends, what type your plugin is, is it targeted to musicians or sound designers, is it specific to a genre, are the customers professionals, prosumer or home kids…
Typical ones I am aware of (and that I would definitely check before release):
- Cubase / (Nuendo)
- Logic / GarageBand / (FinalCutPro)
- Ableton live
- many more optionals…
Worth noting: ProTools have their own plugin format. If your PlugIn sounds interesting you can also apply there to become a partner and get their SDK called AAX. For that you need to communicate with them and sign a NDA.
Hope that helps