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
- [Asset Bundles] A new bundle hash is not generated when the name of a serialized field is changed
- "Editor unavailable" message is displayed when navigating to "Get set up" tab in Unity Hub
- Icon section shows incomplete message and unusable check box in Build Profiles and Player Settings window instead of “Not applicable for this platform” for Dedicated Server Platform
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
This is a duplicate of issue #907393