Visual Studio can't be used on 5.4.0b5 & b6

-Visual Studio 2015 can't be used on Unity 5.4.0b5 & Unity 5.4.0b6
and Monodeveloper was crash when open any scripts.

-Unity 5.4.0b4 can't automatic syncing scripts
I need to open Preferences window and close to manual sync.

-Unity 5.4.0b4 can't double-click on console to go to scripts but not found any crash.

Thank you Unity Developer! Unity Editor is very awesome and easy to use.

 

Existing one sir.

 

I noticed some weird stuff with both Beta 4 and Beta 5. I updated a 5.3 project and there were some errors from https://www.assetstore.unity3d.com/en/#!/content/18253 that I had to fix (Blackberry had to be ignored as platform or something). After editing the script in Visual Studio and going back to Unity, the the indicator on the bottom right corner would never finish spinning until I manually chose a script an reimported. After a restart all seemed to work though.

 

We experienced similar issues on three separate Win 10 64 bit enterprise machines when running b5 64 bit AND having an installation of 32 bit unity editor 5.3.2 on the machine. Both existing and new projects.

Cause of issue: b5 stuck trying to use 32 bit compiler, regardless of override settings. Editor wouldn't compile past built-in Advertisements task, "fail to open" on Visual Studio 2015 in editor log, followed by opening in 32 bit mono.

Our fix: Open on machine without 32 bit version installed, save, reopen of machine experiencing issues.

No issues seen on b6.

 

I'm using 5.4.0b5 and it works just fine with Visual Studio 2015 Community for me. More Info: I had upgraded a 5.3 project to 5.4.0b5. At first it wouldn't open the VS solution file when I tried to open a script from Unity's editor. It would open the script file but the rest of the solution wasn't there so classes from other namespaces were still black. It wasn't until I went to use the Open C# Project that it finally connected up properly.

 

Experiencing a similar issue. When I choose the menu to Open C# project it goes directly to Mono now rather than Visual Studio.

However if I open Visual Studio manually and then open the project solution file manually that works fine.

 

I have just sent a bug report in for this with a new project, created in 5.4 Beta 6, trying to access Visual Studio 2010. I am having this same issue too. I have not received the confirmation email yet, so I could attach it here.

 

FYI this also happened in b4 too

 

Hey, I'm having this in b7 (scripts are opened with MonoDevelop instead of VS). Should I report it or better to wait for b8?

 

Thanks for your quick responce, @GabrieleUnity !

I've made a small investigation which led me to this:

- it works fine (opens VS) if project directory is placed on drive C:\
- it doesn't works fine if project directory is placed on drives D:\ and E:\

I experimented on new project and each time I moved directory, I removed all files and folders except the Assets and ProjectSettings folders.

This seems to be pretty specific and I'm not sure it's reproducible on other machines.
Should I report this via bug reporter anyways?

Please let me know if I can help somehow further.

 

Sure thing, just submitted it as case 776125.

 

Just tried b8 - unfortunately it's still there.

 

I can confirm this problem exists in b8 also. It has been this way for the last few builds on existing projects. If I create a new project, there are no issues.

 

It seems that it works if Visual Studio 2015 is already open in the background. But only if you manually opened the project .sln file in the project folder.