multiple instance of visual studio

Everytime I try to edit a script, it opens in a new visual studio version…
Mac, Unity2020.1.5f1

Deleting the snl file does not solve this.
Happens after updating to this new unity version…

@wouter_vugt ,

First, check that the Visual Studio Editor package is updated. Check in Windows > Package Manager of the Unity Editor to update this.

Also make sure that VS for Mac is set as the external editor in the Unity Editor > Preferences > External Tools window.

If the issue continues after that, please use the Help > Report a Problem menu from Visual Studio for Mac and file the issue so our team to can look into it. Thanks!

3 Likes

well that doesn’t work, still happening…
will make a bug report…

Gotta say it is almost impossible to code with this bug, so hopefully there is a quick fix fo this…

I was able to fix this by going to Package Manager and then removing the two Visual Studio packages (Visual Studio Editor & Visual Studio Code Editor) which were originally added automatically. New everything runs just fine on Catalina with Unity and it never opens multiple instances of Visual Studio.

4 Likes

Mine worked by removing the Visual Studio Editor but only after restarting Unity.

2 Likes

** @John_MSFT ,**

Hello, I’m having the same problem here. And submited the issue Developer Community

Looks the problem starts from 2.0.0

#Update
They are already looking at the issue,
https://developercommunity2.visualstudio.com/t/Unity:-Visual-Studio-Community-2019-for-/1192544
Best regards,

Luiz

@Milluz

Sorry for the confusion - the issue with multiple instances of Visual Studio for Mac opening is fixed and will be released in the next version of the Visual Studio Editor package.

3 Likes

And when will that be, please?

I have spent hours trying to use/configure VS Code or just trying to get VS running with the spawning of multiple editor instances.

@Mike-Church

It’s available now. :slight_smile:

6520513--735604--upload_2020-11-13_9-25-35.png

2 Likes

Had the same issue and updating the Visual Studio Editor package fixed it for me.

Hey guys, a little bit later, but just wanted to say it works now with the update!
I went back to 2019, but really wanted to use the serializable generics in 2020, so I switched back, looked for this bug again, and it was solved, awesome!

1 Like

Unity 2020.2.0f1 with Visual Studio Editor package v2.0.5

It appears to still be happening

@tonycoculuzzi

To confirm, VS for Mac or VS on Windows?

Either way, please use the Report a Problem menu in VS/VS for Mac to file a bug so we can investigate. Thanks!

The known issues were fixed in 2.0.5, so if it’s still happening on Mac, it could be something new.

@John_MSFT

Ah right, VS on Windows 10 :smile:

I’ll watch out for it and report it when I see it again

I can confirm it for macOS Big Sur with 2020.2.01f.

it looks to me to be an issue with opening scripts from Unity during any kind of compilation, or during a dialogue popup (specifically, the reload solution popup) within Visual Studio

@MrPaparoz Interesting… Please double-check you have version 2.0.5 of the Visual Studio Editor package installed in the project using the Unity Package Manager.

If it continues, please use the Help > Report a Problem feature in VS for Mac to submit a bug and share as much detail as you can on how to reproduce it.

@tonycoculuzzi , if there is any dialog open in Visual Studio, this will happen - it’s a known issue, unfortunately. When a dialog is open in VS, the communication between VS and Unity is blocked/unknown so a new instance is launched.

However, you shouldn’t see too many solution reload dialogs these days - what are you doing in the project that causes the dialogs? We might be able to optimize that scenario and prevent this. Thanks!

Seems like most changes to the codebase will cause the reload dialogue to appear. Renaming or moving scripts are probably the biggest offenders

Same issue here on windows