Search Issue Tracker
Duplicate
Votes
0
Found in
2017.1.0f3
Issue ID
930813
Regression
No
MonoDevelop throws errors when being attached to Unity projects with .NET 4.6
Reproduction steps:
1) Create or open already existing project
2) Switch your code editor to MonoDevelop
3) Change project Scripting Runtime Version to .NET 4.6
4) Create script and open it with MonoDevelop (double click on a script)
5) Try to attach MonoDevelop to Unity
-- Notice that attaching failed with errors in MonoDevelop:
MacOS has 31 errors - each error is about System class. https://gyazo.com/16cb104d342b11b04bd7e251995919fd
Windows has only 1 error:
Error CS1617: Invalid option '6' for /langversion; must be ISO-1, ISO-2, 3, 4, 5 or Default (CS1617) (Assembly-CSharp)
Reproduced with:
2017.1.0b1, 2017.2.0b3
Unity 5.6 doesn't have .NET 4.6
Tested on Windows and MacOS
Comments (1)
-
PhilippCh
Jul 26, 2017 19:24
You'll need to use MonoDevelop-Unity 6.x (which is in Preview right now) for debugging to work properly:
https://forum.unity3d.com/threads/monodevelop-unity-6-x-preview-builds.472058/
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- SystemInfo.get_graphicsDeviceName() is generating garbage GC Alloc when using Metal graphics API
- Crash on D3D12CommonShader::ApplyGpuProgram when attaching material which samples "_UnityFBInput0" to "Full Screen Pass Renderer Feature" Component
- SpeedTree meshes and objects count differs when comparing the numbers in the Player with the Editor
- Model and Prefab Preview icons are not updated after upgrading associated Materials to URP
- Game view is rendered white when viewing the Editor with HDR display and Post Proccesing is enabled on the Main Camera with 2D URP
This is a duplicate of issue #907393