Projucer launches a duplicate instance of Visual Studio 2019 for each modification?

Windows
1

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:

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?

2

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.

3

Thanks - is it necessary to use ā€œReload Allā€, or can you just use ā€œReloadā€?

4

ā€œReload allā€ is probably safer.

5

Just tried that. Visual Studio crashed. :confounded:

Will test some moreā€¦

6

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.)

1 Like
7

Yeah, I guess I can quit and relaunch if I need to modify the Projucer file. I just got spoiled in MacOSā€¦

8

Iā€™ve been doing the same thing in macOs (quit Xcode and only then re-export from Projucer). Maybe it hasnā€™t been necessary?

9

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.

10

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 :sweat_smile:

1 Like
11

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.