Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Have a look at our Games Focus blog post series which will show what Unity is doing for all game developers – now, next year, and in the future.
    Dismiss Notice

2017.3f2 Visual Studio for Mac opening new instances all the time

Discussion in '2017.3 Beta' started by Foriero, Dec 9, 2017.

  1. Foriero

    Foriero

    Joined:
    Jan 24, 2012
    Posts:
    575
    Unity is opening new instances of Visual Studio for Mac everytime we open project. Is that intentional. I found it a bit annoying previous behavior ( 2017.3f1 ) we got always the instance that was active in dock.
     
  2. greg-harding

    greg-harding

    Joined:
    Apr 11, 2013
    Posts:
    505
    Opening in Visual Studio Code (releases from November onwards) does something similar with their new workspaces too, which handles multiple solutions from different folders.

    Opening a C# project from Unity makes a new empty workspace which you're prompted to save when exiting VSCode. Open the C# project again from Unity and it makes another new workspace, ignoring the previous one (so settings, open files etc. are all reset).

    Ends up being a slightly frustrating workflow having to manually open VSCode and open or drag the project folder in before doing anything in Unity like opening the C# project or double-clicking a script to edit it.
     
  3. andrar

    andrar

    Unity Technologies

    Joined:
    Sep 27, 2017
    Posts:
    18
    Unity does not want to mess with the existing VS instance as the user may have some other solution open there. Unity spawns its own VS instance and talks to it instead. When Unity gets restarted it cannot recognize which VS instance it was so it starts a new one. Previously in 2017.3f1 Unity would always start a new process to open a file.