# Projucer launches a duplicate instance of Visual Studio 2019 for each modification? **URL:** \ **Category:** Windows\ **Created:** [January 24, 2020, 9:53pm UTC](https://forum.juce.com/t/projucer-launches-a-duplicate-instance-of-visual-studio-2019-for-each-modification/37311 "2020-01-24T21:53:48Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![stephenk](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/stephenk/32/15198_2.png) [@stephenk](https://forum.juce.com/u/stephenk)\ **Post date:** [January 24, 2020, 9:53pm UTC](https://forum.juce.com/t/projucer-launches-a-duplicate-instance-of-visual-studio-2019-for-each-modification/37311/1 "2020-01-24T21:53:48Z")
Windows 10. I am completely new to trying JUCE on Windows and VS 2019, but is this normal? I have the Projucer file of a simple plugin project open. I use the exporter button to open it in VS 2019. So far, so good. I make a change to the configurations settings in the Projucer file, and hit the export button again. On the Mac, this simply takes me back to the same Xcode project, with the changes applied. On Windows 10, this launches a completely new VS 2019 solution, which gives a window with an error about Intellisense data: ```auto Visual C++ examined the folder "C:\Users\sk\Documents\My JUCE\PanProcessorWidth05\Builds\VisualStudio2019\.vs\PanProcessorWidth\v16." This folder is not suitable because of the following: The browsing database in this directory is open by another instance of Visual Studio and cannot be reopened. User stephen on WINDOWS10-DEV has it open. ``` Any way around this? ---
**Author:** ![xenakios](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/xenakios/32/4047_2.png) [@xenakios](https://forum.juce.com/u/xenakios)\ **Post date:** [January 24, 2020, 10:46pm UTC](https://forum.juce.com/t/projucer-launches-a-duplicate-instance-of-visual-studio-2019-for-each-modification/37311/2 "2020-01-24T22:46:09Z")
I just recently discovered you should not use the “export to IDE” button in Projucer in that situation. Instead, you should use the command “Save project” (shortcut Control+P in Windows) in Projucer. Visual Studio will still prompt when you go back to it, but in that case you can just tell it to reload the files and things should _probably_ work OK. ---
**Author:** ![stephenk](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/stephenk/32/15198_2.png) [@stephenk](https://forum.juce.com/u/stephenk)\ **Post date:** [January 24, 2020, 10:53pm UTC](https://forum.juce.com/t/projucer-launches-a-duplicate-instance-of-visual-studio-2019-for-each-modification/37311/3 "2020-01-24T22:53:14Z")
Thanks - is it necessary to use “Reload All”, or can you just use “Reload”? ---
**Author:** ![xenakios](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/xenakios/32/4047_2.png) [@xenakios](https://forum.juce.com/u/xenakios)\ **Post date:** [January 24, 2020, 10:54pm UTC](https://forum.juce.com/t/projucer-launches-a-duplicate-instance-of-visual-studio-2019-for-each-modification/37311/4 "2020-01-24T22:54:45Z")
“Reload all” is probably safer. ---
**Author:** ![stephenk](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/stephenk/32/15198_2.png) [@stephenk](https://forum.juce.com/u/stephenk)\ **Post date:** [January 25, 2020, 12:32am UTC](https://forum.juce.com/t/projucer-launches-a-duplicate-instance-of-visual-studio-2019-for-each-modification/37311/5 "2020-01-25T00:32:28Z")
Just tried that. Visual Studio crashed. 😖 Will test some more… ---
**Author:** ![xenakios](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/xenakios/32/4047_2.png) [@xenakios](https://forum.juce.com/u/xenakios)\ **Post date:** [January 25, 2020, 12:35am UTC](https://forum.juce.com/t/projucer-launches-a-duplicate-instance-of-visual-studio-2019-for-each-modification/37311/6 "2020-01-25T00:35:46Z")
Well, the thing that worked for me for years was to quit Visual Studio and then re-export from the Projucer…(I only made some quick tests with Visual Studio 2017 when I was told about the other way to do it in the Projucer.) ---
**Author:** ![stephenk](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/stephenk/32/15198_2.png) [@stephenk](https://forum.juce.com/u/stephenk)\ **Post date:** [January 25, 2020, 1:21am UTC](https://forum.juce.com/t/projucer-launches-a-duplicate-instance-of-visual-studio-2019-for-each-modification/37311/7 "2020-01-25T01:21:40Z")
Yeah, I guess I can quit and relaunch if I need to modify the Projucer file. I just got spoiled in MacOS… ---
**Author:** ![xenakios](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/xenakios/32/4047_2.png) [@xenakios](https://forum.juce.com/u/xenakios)\ **Post date:** [January 25, 2020, 1:25am UTC](https://forum.juce.com/t/projucer-launches-a-duplicate-instance-of-visual-studio-2019-for-each-modification/37311/8 "2020-01-25T01:25:50Z")
I’ve been doing the same thing in macOs (quit Xcode and only then re-export from Projucer). Maybe it hasn’t been necessary? ---
**Author:** ![stephenk](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/stephenk/32/15198_2.png) [@stephenk](https://forum.juce.com/u/stephenk)\ **Post date:** [January 25, 2020, 3:04am UTC](https://forum.juce.com/t/projucer-launches-a-duplicate-instance-of-visual-studio-2019-for-each-modification/37311/9 "2020-01-25T03:04:19Z")
> [@Xenakios](#): > > I’ve been doing the same thing in macOs (quit Xcode and only then re-export from Projucer). Maybe it hasn’t been necessary? Not necessary at all. You can add new source files, rearrange their order and folders, change compile time settings in Projucer, then hit the export button and watch the new files get added and rearranged right into the already open Xcode project. ---
**Author:** ![mcmartin](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/mcmartin/32/7432_2.png) [@mcmartin](https://forum.juce.com/u/mcmartin)\ **Post date:** [January 25, 2020, 9:17am UTC](https://forum.juce.com/t/projucer-launches-a-duplicate-instance-of-visual-studio-2019-for-each-modification/37311/10 "2020-01-25T09:17:41Z")
I think the safest workflow is to never use “Open in IDE…” or the exporter button. What I usually do is: - start Visual Studio from its shortcut on the taskbar (created by “Pin to taskbar”) - open the solution I’m interested in (either from the list of recent projects or by browsing) - in Projucer, use “Save Project” (Ctrl+P) anytime I change some project settings - in Visual Studio, click on “Reload All” to make sure that everything is up-to-date (and also to avoid clicking on “Reload” for each project) It’s quite stable, though I can’t guarantee that I’ve never experienced a crash. But it’s Windows, it’s kind of expected 😅 ---
**Author:** ![gustav-scholda](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/gustav-scholda/32/4172_2.png) [@gustav-scholda](https://forum.juce.com/u/gustav-scholda)\ **Post date:** [January 26, 2020, 8:05am UTC](https://forum.juce.com/t/projucer-launches-a-duplicate-instance-of-visual-studio-2019-for-each-modification/37311/11 "2020-01-26T08:05:16Z")
I usually just close VS Studio, modify the Projucer project, then reopen VS Studio using „Open in IDE…“ in Projucer. I‘m using Windows 10 for 3 years now and haven’t had a single crash, so I wouldn‘t expect any.