Visual StudioVerified account. Follow us for the latest Microsoft Visual Studio news and related information for developers. But i can't install it. Visual studio for mac installer crashes #bugs.
If you are interested in evaluating the new Visual Studio for Mac (Preview) from Microsoft, the easiest way to install Visual Studio on your Mac is to simply open up a terminal window and execute the following command: $ curl -s sh This will download the disk image, execute the installer and remove the disk image when the installation has finished. If you want to preview the script before executing it (which I strongly encourage) navigate to the url or choose to Read more below.
The best way for getting help with advanced issues is to submit bug reports. This way we can properly track and prioritize everything.
Microsoft and Unity teams are working together daily to solve your issues. We really need minimal reproduction projects for those bugs! That’s super important for us, because so many times it was a very project-specific thing that was causing an issue. We made a troubleshooting page to help you solve common issues with Visual Studio (you can even add your own comments or add extra content): The best way to quick solve issues is to be sure you are using the latest Visual Studio and Unity versions (when possible of course). Regards Sebastien Lebreton MSFT.
Click to expand. Please submit bug reports + reproduction projects for your issues at - Regarding VS 2017: The cause for this issue has been identified.
In the meantime, as a temporary workaround, you can. Play the game in Unity (to trigger a reload of the code in Unity). Delete csproj+sln in the project folder. Double click on a script to properly generate the projects. Regarding VS:. This issue is under investigation.
The following issues are related and a fix for them will become available in one of the upcoming releases (the fix already exists). VS for Mac:. VS 2015:. VS:. VS. I've found an issue with the Mono 4.6 /.NET Standard 2.0 Runtime that seems to affect both Visual Studio 2017 and Visual Studio Code. When I open my project in either, I get errors of the form: 'Type AFFECTEDTYPE exists in both System.Core and netstandard'.
Not sure if this was reported elsewhere. Seemingly affects only.NET source types (such as HashSet, several delegate types, Linq operators, etc). Happens on both Windows 10 (64bit) and Mac OSX (64bit). I haven't tested Linux VS Code. Changing between Mono/IL2CPP for desktop doesn't make a difference.
It seems that the actual Unity Editor Compilation isn't affected, as I don't get the same errors. Issue # is 996937. You have a troubleshooting page when the plugin is not active: Regarding conditional breakpoints, every-time the Unity runtime is hitting a breakpoint (it has no clue there is a condition, this is a debugger client-only concept), it will stop all threads, then notify the debugger, then the debugger will check the condition and eventually instruct Unity to resume all threads in the case the condition is not met.
This back and forth is super time consuming. That's why it is not suitable for all usages, and sometimes it is easier to write a real 'if' condition in your code and put a breakpoint inside. This way the runtime will only suspend all threads when the breakpoint is really hit and will keep the game in a playable state. You have a troubleshooting page when the plugin is not active: Regarding conditional breakpoints, every-time the Unity runtime is hitting a breakpoint (it has no clue there is a condition, this is a debugger client-only concept), it will stop all threads, then notify the debugger, then the debugger will check the condition and eventually instruct Unity to resume all threads in the case the condition is not met. This back and forth is super time consuming. That's why it is not suitable for all usages, and sometimes it is easier to write a real 'if' condition in your code and put a breakpoint inside. This way the runtime will only suspend all threads when the breakpoint is really hit and will keep the game in a playable state.
Click to expand.Bonjour Laurent, Unity fixed an issue early in the beta cycle and then some more in 2018.1 b8 where they weren't properly delegating to the Tools for Unity plugin the project generation. Down the line it meant the generated project wasn't recognized by Visual Studio as a Unity project, and the Unity specific features were not enabled. Could you give a try to 2018.1 b8, and if you're still running into troubles, it's probably something funny and exotic. I'll encourage you to reach out directly to my team at and we'll help you investigate. I usually don't say anything because I just deal with the pain. But it's getting ridiculous.
I've got already about 25 asmdefs in my project, and the second I add a new file and alt-tab out back to Visual Studio I have to sit there waiting somewhere between 40 - 50 seconds for the loading-unloading to occur. I've tried to switch everything to VS code, and while I LOVE the instant opening speeds, I can't handle the lack of the shortcuts I know and love in Visual Studio proper. I just want to see if I can understand - this reloading problem is fixed in the next VS version, (15.6), then, and will not be resolved as part of a Unity Beta update, right? And if that's the case, is there any way to try out the 15.6 early? I just got the VS 15.6 preview to test to see if it fixed the reloading issues others have mentioned. I don't see it as fixed as it still reloads every single assembly definition and package added through Unity. Also, I believe I've found a pretty consistent way to get it to trigger this reload problem: Have VS open.
Trigger a script recompile in Unity, either by Right click - Reimport or edit a script. Then double-click a script in the project view and VS should start reloading everything.
Not sure if it's Unity or VS causing this. Tested with the latest VS stable build and preview build 15.6 and Unity b8. Project reloading seems to be fixed for me in 15.6 P6. Can delete or add files from within Unity no problems and VS updates without reloading the projects. There is still the glaring issue of most of my Asset folders and non-script files being visible in every Assembly in the Solution Explorer though. Which makes it very difficult to actually use the Solution explorer to manage files instead of Unity.
![Visual studio for mac installer crashes 2017 Visual studio for mac installer crashes 2017](/uploads/1/2/5/4/125424953/398518559.png)
Make sure you manually added the VS preview through your Unity editor settings, you can't just install it and expect it to work, it's a separate install, you have to click the manual 'Browse' option and find it, default folder is: C: Program Files (x86) Microsoft Visual Studio Preview Community Common7 IDE devenv.exe. Project reloading seems to be fixed for me in 15.6 P6. Can delete or add files from within Unity no problems and VS updates without reloading the projects. There is still the glaring issue of most of my Asset folders and non-script files being visible in every Assembly in the Solution Explorer though. Which makes it very difficult to actually use the Solution explorer to manage files instead of Unity.
Make sure you manually added the VS preview through your Unity editor settings, you can't just install it and expect it to work, it's a separate install, you have to click the manual 'Browse' option and find it, default folder is: C: Program Files (x86) Microsoft Visual Studio Preview Community Common7 IDE devenv.exe. Hi, I'm now getting same 38 errors (subset below) when trying to run and attach the debugger. I can run the project no errors and even create a build. I'm running out of solutions. Anybody hit similar issues?
I'm using Beta 9 and VS 7.3.3 thx Target HandlePackageFileConflicts: Encountered conflict between 'Reference:mscorlib' and 'Reference:mscorlib'. Choosing 'Reference:mscorlib' because file version '4.7.2558.0' is greater than '4.6.57.0'. Encountered conflict between 'Reference:System' and 'Reference:System'. Choosing 'Reference:System' because file version '4.7.2558.0' is greater than '4.6.57.0'. Encountered conflict between 'Reference:System.Core' and 'Reference:System.Core'.
More errors here /Library/Frameworks/Mono.framework/Versions/5.4.1/lib/mono/4.5/csc.exe /noconfig /unsafe+ /nowarn:1701,1702,2008 /langversion:6 /nostdlib+ /errorreport rompt /warn:4 Done building target 'CoreCompile' in project 'Unity.ProBuilder.AddOns.Editor.csproj' - FAILED. Done building project 'Unity.ProBuilder.AddOns.Editor.csproj' - FAILED. Click to expand.Thanks for the script, it actually gave me an idea on how I could solve the issue of the AssemblyDefinition files being loaded with includes to nearly everything outside of the Assembly's folder as well. I was looking through the Editor DLL and found CompilationPipeline.GetAssemblyDefinitionFilePathFromAssemblyName which I can use with the csproj's file name, and if it returns a string, it means we're working with an assembly definition csproj, and I can remove all the '.
Hello again, For 2018.1 beta testers, you can try the following builds of the Visual Studio Tools for Unity. What will change?
With those versions, instead of generating from scratch Visual Studio projects, the Tools for Unity are going to participate in Unity's project generation. This means that we're going back to projects that are named Assembly-CSharp, but that Visual Studio still recognizes them as Unity projects to enable debugging and other Unity specific features.
Unity's project generator in b9 doesn't support everything that VSTU's project generator supported (like full RSP file parsing), but most of you shouldn't have any issue, and we hear that full RSP parsing is in b10. Visual Studio for Mac, please upgrade to version 7.4 in the Beta channel (Visual Studio - Check for Updates - Select Beta channel), and then install the extension (Visual Studio - Extensions - Install from File): Visual Studio 2015, please install this version: Visual Studio 2017, please install both components: For 2017, the VSIX is the Visual Studio extension, the MSI is the Unity extension, both are necessary. After you've installed the version that you need, please check that Unity has loaded the new bits in its About window. Hello again, For 2018.1 beta testers, you can try the following builds of the Visual Studio Tools for Unity. What will change? With those versions, instead of generating from scratch Visual Studio projects, the Tools for Unity are going to participate in Unity's project generation. This means that we're going back to projects that are named Assembly-CSharp, but that Visual Studio still recognizes them as Unity projects to enable debugging and other Unity specific features.
Unity's project generator in b9 doesn't support everything that VSTU's project generator supported (like full RSP file parsing), but most of you shouldn't have any issue, and we hear that full RSP parsing is in b10. Visual Studio for Mac, please upgrade to version 7.4 in the Beta channel (Visual Studio - Check for Updates - Select Beta channel), and then install the extension (Visual Studio - Extensions - Install from File): Visual Studio 2015, please install this version: Visual Studio 2017, please install both components: For 2017, the VSIX is the Visual Studio extension, the MSI is the Unity extension, both are necessary. Thanks for the script, it actually gave me an idea on how I could solve the issue of the AssemblyDefinition files being loaded with includes to nearly everything outside of the Assembly's folder as well. I was looking through the Editor DLL and found CompilationPipeline.GetAssemblyDefinitionFilePathFromAssemblyName which I can use with the csproj's file name, and if it returns a string, it means we're working with an assembly definition csproj, and I can remove all the '. Click to expand.Thanks for that, I was not aware this existed. The other way was the recommended way of doing these things by the Unity devs themselves. But thanks to your warning I looked around and it seems I had another similar bad behaviour script 'RXSolutionFixer' that was shared on this forum a while back for fixing the incorrect.NET version being set in the csproj files (a bug I believe is long since fixed now).
So that file was likely a source for some of my issues as well, and may be for others. In case anyone is interested, I restructured my script to use the way Sebastien has recommended.
Edit: Wrapped code in #if ENABLEVSTU to prevent errors thrown for team members who don't have VS. Hello again, For 2018.1 beta testers, you can try the following builds of the Visual Studio Tools for Unity. What will change? With those versions, instead of generating from scratch Visual Studio projects, the Tools for Unity are going to participate in Unity's project generation. This means that we're going back to projects that are named Assembly-CSharp, but that Visual Studio still recognizes them as Unity projects to enable debugging and other Unity specific features. Unity's project generator in b9 doesn't support everything that VSTU's project generator supported (like full RSP file parsing), but most of you shouldn't have any issue, and we hear that full RSP parsing is in b10.
Visual Studio for Mac, please upgrade to version 7.4 in the Beta channel (Visual Studio - Check for Updates - Select Beta channel), and then install the extension (Visual Studio - Extensions - Install from File): Visual Studio 2015, please install this version: Visual Studio 2017, please install both components: For 2017, the VSIX is the Visual Studio extension, the MSI is the Unity extension, both are necessary. After you've installed the version that you need, please check that Unity has loaded the new bits in its About window. Click to expand.Hi - this is pretty exciting. However, I'm still in the same boat. It does seem faster, but I'm still seeing the unloading-reloading of all 20+ files of mine every time I add a file.
![Visual Studio For Mac Installer Crashes Visual Studio For Mac Installer Crashes](/uploads/1/2/5/4/125424953/190627309.png)
I installed both the vsix and the msi; and I'm on B9 with Preview 15.6. I can tell that 3.6.0.5 is in my VS installs - but I'm not sure where in the About page I can see the VSTU bits installed in unity?
I suppose I'm wondering why my addition of a new file to, say the Assembly-csharp top-level project forces reloads of all of the csproj's in my project. A lot of them are 'finished' code, and I'm half tempted to just move everything out to DLLs at this point just to avoid the constant reloading. That said, I just wanted to say thank you for being so active here on these forums and being so willing to hear us out and look into things for us. For all of our bitching here on the forums, VSTU is still an incredible product, and the only reason we complain is because using Unity with Visual Studio is just leaps and bounds better than anything else. Hi - this is pretty exciting. However, I'm still in the same boat. It does seem faster, but I'm still seeing the unloading-reloading of all 20+ files of mine every time I add a file.
I installed both the vsix and the msi; and I'm on B9 with Preview 15.6. I can tell that 3.6.0.5 is in my VS installs - but I'm not sure where in the About page I can see the VSTU bits installed in unity? I suppose I'm wondering why my addition of a new file to, say the Assembly-csharp top-level project forces reloads of all of the csproj's in my project. A lot of them are 'finished' code, and I'm half tempted to just move everything out to DLLs at this point just to avoid the constant reloading.