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!

 

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.

 

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

 

@John_MSFT,

Hello, I'm having the same problem here. And submited the issue https://developercommunity.visualst...dio-unity-package-open-multiple-instance.html

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

 

@Luiz-Aoki

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.

 

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.

 

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!

 

Unity 2020.2.0f1 with Visual Studio Editor package v2.0.5

It appears to still be happening

 

@wildertony

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

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.

@wildertony, 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

 

@wildertony Hm, that surprises me. Please do take advantage of the Report a Problem tool so we can get exact version numbers, etc. We'll investigate.

@ZhavShaw Please also report the issues you're seeing so we can investigate. Thanks!

 

In the time we started talking about this, I've actually switched to VS Code because the issue takes up so much of my time hahaha. I'll let you know if I come across the issue again next time I use VS

 

@John_MSFT It appears to be most common when I'm opening script files from within packages.

 

After two days trying to fix this issue, only one thing finally did the fix. I've tried to exclude the. Sln and .Csproj files, regenerate new .Csproj by External Tools tab, update the VS and all packages, download/update or remove some extensions, change paths and anything you can find on the forums. So, I decided uninstall 2019 and roll back to 2017.

I opened the unistaller and just for a last try, I managed to do a repair run and see what happens. After 1gb of download and some minutes repairing, for my surprise works perfectly fine, no more new instances when open a new file.

For short, try repair via "Visual Studio Installer".

 

Thank you very much ! This solve my problem !!

 

Having this issue constantly on my mac workstation, on the windows 10 machine visual studio works perfectly as expected. MacOS with unity, not so much

 

Sorry for the issues! We did recently fix several issues that caused. Would you make sure that VS for Mac is up to date? If you're using Unity 2020 or higher, please also make sure that the Visual Studio Editor package is updated to version 2.0.7 or newer using the Unity Package Manager via Unity > Windows > Package Manager.

If you still have the issue after that, it could be a bug that we need to fix. In that case, please use VS for Mac > Help > Report a Problem to file the bug so we can investigate quickly. Thank you!

 

I can confirm I have all those, this is also a brand new mac, new project, using Unity 2020.3.0f1 fresh installs and all editor settings at default other than adding the package for Visual Studio (not vs code) and assigning visual studio as the code editor for the project.

VS studio is fully up to date also using 8.9.4 build 25 mac community edition with the Visual Studio for Mac Tools for Unity extension v 2.9.3.0

It's just about a half hour into working between Visual Studio and Unity, I go to open a script either double clicking it form the project window or from the component it is on a gameobject, the Visual studio window opens up with the last few scripts I had open, but not the one I wanted to open there. I close the open scripts and leave the window open, try to open the script the same way again and the empty Visual Studio window opens up again, nothing loading.

Issue persists until I go to regenerate the project files in the Unity preferences, or close/reopen unity or Visual Studio.

This happens all day while I am working on this mac and it's driving me nuts. I will report it as a bug soon

 

After further investigation, this was reproducible on various 2020 Unity versions in any kind of project even a brand new project.

Can I send the problematic Unity project with the bug report to help?

 

Yes, that will help. Thank you!

 

I'll ping over a repro project this weekend for you as this issue is affecting every other mac user in our team on other macs and it's just getting more irritating. You genuinely need to be working on a Unity project for at least an hour just saving scripts making changes to code and hitting play mode/exit play mode a few times so I will take note of what I do from start to 'scripts not opening in Visual Studio'

I am planning to move to using VS Code on the mac for a while until this bug is fixed although VS Code on mac had some horrendous issues with getting intellisense to start up so I could use peek references etc.

This stuff just 'works' instantly on Windows 10 off the bat but on Macs both Visual Studio 2019 and VS Code have some real issues.. not sure if on purpose or not I would prefer to work on windows too but I have to use the mac for IOS builds sadly

 

I am looking into how to reproduce this now as it often happens an hour or two into the day while I am working I may have to find a way to send a stripped out working project to you without anything confidential in it.

I did see another forum user talking about this same issue in a bit more detail than me here:
https://forum.unity.com/threads/visual-studio-for-mac-issues.1014223/

 

I am putting the bug report as we speak I just found how to reproduce it and it was very simple actually - I have made a video and steps below as well as highlighting another issue:

I was actually shocked when I went to report this issue I saw at least 10 copies of this issue all closed due to 'not enough info' and I was able to reproduce it and video it in about 10 minutes today when I spent some time on it. Some of the issues are over 365 days old too!

Issue 1: Visual Studio on Mac for Unity refuses to open scripts from Unity if you have closed/reopened it while working in Unity

Microsoft bug link: https://developercommunity.visualstudio.com/t/Visual-Studio-on-Mac-for-Unity-refuses-t/1395151

1. Open Unity, make sure Visual Studio is set as the editor default script editing program and package manager install Visual Studio package also the latest version.
2. Open a script, edit and save script
3. Close Visual studio
4. Make a new script in the unity project
5. Double click on that new script (or any other perhaps)
6. Visual studio opens, try double clicking other project scripts, they do not open

I really hope this bug can be fixed soon as it seems to also happen under another condition I have not found yet as very rarely during the working day do I actually close Visual Studio - unless in this case it is happening when I open another Unity project at the same time so I have two open, then in that case it probably is the same as closing Visual Studio.

Issue 2:
On Mac the behaviour of Visual Studio with Unity is quite different to windows as with windows if I open 2 Unity Projects, I can have two Visual Studio instances. On Mac, I seem to only be able to have one instance of Visual studio so when editing scripts in multiple open unity projects, visual studio for mac sort of open/close/resets itself between switching between those 2 projects and that is where I also noticed this bug with scripts not opening in Visual Studio for mac.

Microsoft bug link: https://developercommunity.visualstudio.com/t/No-way-to-have-a-new-instance-of-Visual-/1395152

 

Just to update here if anyone else has this issue where Visual studio doesn't open a new instance per project open on Mac OS or if you close and reopen Visual Studio while a project is open then find it doesn't open scripts anymore. The issue is with Unity hubs ruining Visual studio's connection to apple events:

The workaround is to open Unity without its processes being re-parented on the Hub.

You can achieve it like this in the terminal:

/Applications/Unity/Hub/Editor/2020.3.1f1/Unity.app/Contents/MacOS/Unity -debugHub

 

This is an issue with a variety of text editors on the Mac—I've run into it with both Sublime Text and Nova. it seems like @ROBYER1 may be on to something here with the connection to the Unity Hub.

Unity, any update on this?

Thanks!

 

Yeah that fix I posted doesn't actually seem to work, just got to hope Unity fix it - Microsoft have contacted them about it

I already posted it to the main thread here too https://forum.unity.com/threads/uni...ple-events-unity-editor.1093885/#post-7127801

 

This is a fix if you are on windows. You must install in the visual studio modifier package .NET development for C# and Game development with Unity. This will fix that issue

 

Do you have a link for this, the last version of the Visual Studio Editor plugin for Unity that works for me is 2.0.7. Anything after that does not work when double-clicking a script file.

 

Hey John, your team reintroduced the bug. Latest unity, latest vs studio for mac.

 

Please report via Help > Report a Problem. Thanks!