Search Unity

  1. Megacity Metro Demo now available. Download now.
    Dismiss Notice
  2. Unity support for visionOS is now available. Learn more in our blog post.
    Dismiss Notice

MonoDevelop-Unity 5.9 Preview Release

Discussion in 'Scripting' started by lukaszunity, Aug 25, 2015.

Thread Status:
Not open for further replies.
  1. lukaszunity

    lukaszunity

    Administrator

    Joined:
    Jun 11, 2014
    Posts:
    461
    ATTENTION: Unity 5.3 with MonoDevelop-Unity 5.9 has been released. This thread is no longer being updated


    We are releasing preview builds of MonoDevelop-Unity 5.9, which will ship with Unity 5.3, for early testing and feedback.

    These builds are different from using Xamarin Studio 5.9 with the Unity Add-ins as they also contain fixes that are not yet included in Xamarin Studio. We are working on getting these fixes into Xamarin Studio.

    Download
    Installation
    • OSX:
      • Mount the .dmg.
      • Copy MonoDevelop.app to a path without spaces on your disk.
      • Unmount the .dmg.
    • Windows:
      • Right click the zip file, select "Properties" and then click "Unblock".
      • Unpack the zip to your disk.
      • Might be required to install GTK# using GTKSharp/gtk-sharp.msi (Only once).
    • In Unity:
      • Open Preferences and change the External Script Editor path to point to MonoDevelop.exe (Windows) / MonoDevelop.app (OSX).
    Release notes

    Beta 2
    • Fixed ERR_UNLOADED error when setting breakpoints. Regression introduced in Beta 1.
    • OSX: Added .NET 4.0 assemblies in bundled Mono framework.
    Beta 1
    • Fixed missing syntax highlighting for ShaderLab files
    • Fixed Mono.Debugger.Soft.ObjectCollectedException error message when setting a breakpoint
    Alpha 4
    • Removed "Show Error Reference" and "API Documentation" menu items that launch the documentation browser, which we do not include nor support.
    • Updated MonoDevelop to 5.9.6
    Alpha 3
    • Fixed "The requested item has been unloaded" when inspecting enums.
    • Fixed "The requested item has been unloaded" dialog when enabling/disabling breakpoints.
    • Fixed "Debugger operation failed. Argument cannot be null" error.
    • Included DocFood (/// documentation) and VersionControl add-ins.
    Alpha 2
    • Fixed issue with MonoDevelop crashing on OSX.
    • Regression: MonoDevelop OSX must be installed in path without spaces.
    • Fixed issue with being unable to set conditional breakpoints.
    • Bundled GTK# installer. Will be installed by the Unity editor installer for Unity 5.3.
    Alpha 1
    • Fixed issue with MonoDevelop-Unity opening a new instance when clicking a script on Windows.
    • Fixed “The request is not supported by the protocol version implemented by the debugee” when inspecting generic List/Dictionary.
    • Fixed error messages when trying to recompile your scripts in Unity while the debugger is attached.
    Minimum Requirements
    Unity patch releases are available here : https://unity3d.com/unity/qa/patch-releases

    Not supported
    • Boo/UnityScript: Code completion and source navigation. (Editing, building and debugging of Boo/UnityScript projects is supported).
    • Debugger: Launching Unity from MonoDevelop/Xamarin Studio.
    Source code repositories
     
    Last edited: Dec 9, 2015
  2. oops64

    oops64

    Joined:
    Jul 2, 2015
    Posts:
    4
    wow...
     
    zworp likes this.
  3. Pharan

    Pharan

    Joined:
    Oct 28, 2013
    Posts:
    102
    Download links aren't working. :(
     
    sanpats likes this.
  4. lukaszunity

    lukaszunity

    Administrator

    Joined:
    Jun 11, 2014
    Posts:
    461
    Sorry. Should be fixed now.
     
  5. Pharan

    Pharan

    Joined:
    Oct 28, 2013
    Posts:
    102
    It's strangely super slow. I just downloaded 170 KB in 10 minutes.
     
  6. lukaszunity

    lukaszunity

    Administrator

    Joined:
    Jun 11, 2014
    Posts:
    461
    ocimum likes this.
  7. sanpats

    sanpats

    Joined:
    Aug 24, 2011
    Posts:
    343
    Tried to edit colors in custom syntax highlighting make Monodevelop-Unity crash every time, not happen in Xamarin Studio with Unity Add-ins.

    Bug# 722356
     
    Last edited: Aug 25, 2015
  8. lukaszunity

    lukaszunity

    Administrator

    Joined:
    Jun 11, 2014
    Posts:
    461
    Thanks for the bug report. We will have a look.
     
  9. laurentlavigne

    laurentlavigne

    Joined:
    Aug 16, 2012
    Posts:
    6,222
    It works really well for me, even opens up to the right script, right light.
     
  10. sanpats

    sanpats

    Joined:
    Aug 24, 2011
    Posts:
    343
    It crashes a lot for me, especially when using source analysis.

    I notice that the add-ins are all 5.9.0. In Xamarin Studio version, some is 5.9.1. Is this correct?
     
    Last edited: Aug 25, 2015
  11. lukaszunity

    lukaszunity

    Administrator

    Joined:
    Jun 11, 2014
    Posts:
    461
    I would be very interested in repro steps for these crashes. Using Help - Open Log Directory you can open the logs files for MonoDevelop and you should see call stacks for the crashes. These would also be very helpful.
     
  12. sanpats

    sanpats

    Joined:
    Aug 24, 2011
    Posts:
    343
    There are many log files. I will just send you the latest one. I test MonoDevelop-Unity 5.9.4a1 to know the cause of crash for awhile now. I can always reproduce the crash by move mouse cursor over the red underline error to see the tooltip box of the error. The's when MD will crash.

    INFO [2015-08-26 03:29:47Z]: Starting MonoDevelop-Unity 5.9.4
    INFO [2015-08-26 03:29:47Z]: Running on Mono 4.0.2 ((detached/c99aa0c Fri Jul 10 13:28:51 CEST 2015)
    WARNING [2015-08-26 03:29:48Z]: Gtk-Warning: Locale not supported by C library.
    Using the fallback 'C' locale.
    Stack trace:
    at Gtk.Application.gtk_init(Int32 ByRef , IntPtr ByRef )
    at Gtk.Application.do_init(System.String progname, System.String[] ByRef args, Boolean check)
    at Gtk.Application.Init(System.String progname, System.String[] ByRef args)
    at MonoDevelop.Ide.IdeStartup.Run(MonoDevelop.Ide.MonoDevelopOptions options)
    at MonoDevelop.Ide.IdeStartup.Main(System.String[] args, MonoDevelop.Ide.Extensions.IdeCustomizer customizer)
    at MonoDevelop.Startup.MonoDevelopMain.Main(System.String[] args)
    2015-08-26 03:29:48.100 mono[25982:2429880] *** WARNING: Method userSpaceScaleFactor in class NSView is deprecated on 10.7 and later. It should not be used in new applications. Use convertRectToBacking: instead.
    INFO [2015-08-26 03:29:48Z]: Using GTK+ 2.24.23
    INFO [2015-08-26 03:29:48Z]: Add-in loaded: MonoDevelop.Core
    INFO [2015-08-26 03:29:48Z]: Add-in loaded: MonoDevelop.Ide
    INFO [2015-08-26 03:29:48Z]: Add-in loaded: MonoDevelop.MacPlatform
    INFO [2015-08-26 03:29:48Z]: Initializing Runtime Mono 4.0.2
    ERROR [2015-08-26 03:29:48Z]: Error reading name for assembly '/Applications/MonoDevelop.app/Contents/Frameworks/Mono.framework/Versions/Current/lib/mono/4.5/EntityFramework.SqlServer.dll' in framework '.NETFramework,Version=v4.5.1':
    System.IO.FileNotFoundException: Could not load file or assembly '/Applications/MonoDevelop.app/Contents/Frameworks/Mono.framework/Versions/Current/lib/mono/4.5/EntityFramework.SqlServer.dll' or one of its dependencies. The system cannot find the file specified.
    File name: '/Applications/MonoDevelop.app/Contents/Frameworks/Mono.framework/Versions/Current/lib/mono/4.5/EntityFramework.SqlServer.dll'
    at (wrapper managed-to-native) System.Reflection.Assembly:InternalGetAssemblyName (string,System.Reflection.AssemblyName)
    at System.Reflection.AssemblyName.GetAssemblyName (System.String assemblyFile) [0x00000] in <filename unknown>:0
    at MonoDevelop.Core.Assemblies.SystemAssemblyService.GetAssemblyNameObj (System.String file) [0x00000] in <filename unknown>:0
    ERROR [2015-08-26 03:29:48Z]: Error reading name for assembly '/Applications/MonoDevelop.app/Contents/Frameworks/Mono.framework/Versions/Current/lib/mono/4.5/EntityFramework.dll' in framework '.NETFramework,Version=v4.5.1':
    System.IO.FileNotFoundException: Could not load file or assembly '/Applications/MonoDevelop.app/Contents/Frameworks/Mono.framework/Versions/Current/lib/mono/4.5/EntityFramework.dll' or one of its dependencies. The system cannot find the file specified.
    File name: '/Applications/MonoDevelop.app/Contents/Frameworks/Mono.framework/Versions/Current/lib/mono/4.5/EntityFramework.dll'
    at (wrapper managed-to-native) System.Reflection.Assembly:InternalGetAssemblyName (string,System.Reflection.AssemblyName)
    at System.Reflection.AssemblyName.GetAssemblyName (System.String assemblyFile) [0x00000] in <filename unknown>:0
    at MonoDevelop.Core.Assemblies.SystemAssemblyService.GetAssemblyNameObj (System.String file) [0x00000] in <filename unknown>:0
    Starting MonoDevelop-Unity
    INFO [2015-08-26 03:29:48Z]: Add-in loaded: MonoDevelop.Debugger
    INFO [2015-08-26 03:29:48Z]: Add-in loaded: MonoDevelop.SourceEditor2
    INFO [2015-08-26 03:29:48Z]: Add-in loaded: MonoDevelop.UnityScript
    INFO [2015-08-26 03:29:48Z]: Add-in loaded: MonoDevelop.DesignerSupport
    INFO [2015-08-26 03:29:48Z]: Add-in loaded: MonoDevelop.Refactoring
    INFO [2015-08-26 03:29:48Z]: Add-in loaded: MonoDevelop.CSharpBinding
    INFO [2015-08-26 03:29:48Z]: Add-in loaded: Unity.Utilities
    INFO [2015-08-26 03:29:48Z]: Add-in loaded: MonoDevelop.Boo
    INFO [2015-08-26 03:29:50Z]: Add-in loaded: MonoDevelop.NUnit
    INFO [2015-08-26 03:29:50Z]: Add-in loaded: MonoDevelop.Debugger.Soft
    INFO [2015-08-26 03:29:50Z]: Add-in loaded: MonoDevelop.Debugger.Soft.Unity
    INFO [2015-08-26 03:29:50Z]: Add-in loaded: MonoDevelop.Xml
    Loading Workbench
    INFO [2015-08-26 03:29:50Z]: Add-in loaded: MonoDevelop.RegexToolkit
    INFO [2015-08-26 03:29:50Z]: Add-in loaded: MonoDevelop.AssemblyBrowser
    Initializing Main Window
    INFO [2015-08-26 03:29:50Z]: Creating DefaultWorkbench
    INFO [2015-08-26 03:29:51Z]: Add-in loaded: MonoDevelop.ILAsmBinding
    INFO [2015-08-26 03:29:52Z]: Add-in loaded: MonoDevelop.HexEditor
    ERROR [2015-08-26 03:29:58Z]: Failed to load: /PlaybackEngines/iOSSupport/Data/iosdevices.csv
    System.IO.DirectoryNotFoundException: Could not find a part of the path "/PlaybackEngines/iOSSupport/Data/iosdevices.csv".
    at System.IO.FileStream..ctor (System.String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, Boolean anonymous, FileOptions options) [0x00000] in <filename unknown>:0
    at System.IO.FileStream..ctor (System.String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, System.String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) [0x00000] in <filename unknown>:0
    at (wrapper remoting-invoke-with-check) System.IO.FileStream:.ctor (string,System.IO.FileMode,System.IO.FileAccess,System.IO.FileShare,int,System.IO.FileOptions,string,bool,bool,bool)
    at System.IO.StreamReader..ctor (System.String path, System.Text.Encoding encoding, Boolean detectEncodingFromByteOrderMarks, Int32 bufferSize, Boolean checkHost) [0x00000] in <filename unknown>:0
    at System.IO.StreamReader..ctor (System.String path, System.Text.Encoding encoding, Boolean detectEncodingFromByteOrderMarks, Int32 bufferSize) [0x00000] in <filename unknown>:0
    at System.IO.StreamReader..ctor (System.String path, Boolean detectEncodingFromByteOrderMarks) [0x00000] in <filename unknown>:0
    at System.IO.StreamReader..ctor (System.String path) [0x00000] in <filename unknown>:0
    at (wrapper remoting-invoke-with-check) System.IO.StreamReader:.ctor (string)
    at System.IO.File.OpenText (System.String path) [0x00000] in <filename unknown>:0
    at System.IO.File.ReadAllLines (System.String path) [0x00000] in <filename unknown>:0
    at MonoDevelop.Debugger.Soft.Unity.iOSDevices.LoadDescriptions (System.String path) [0x00000] in <filename unknown>:0
    at MonoDevelop.Debugger.Soft.Unity.iOSDevices.SetupDescriptions (System.String path) [0x00000] in <filename unknown>:0
    ERROR [2015-08-26 03:29:58Z]: Error while initializing usbmuxd
    System.Exception: dlopen: dlopen(/PlaybackEngines/iOSSupport/UnityEditor.iOS.Extensions.Native.dylib, 2): image not found
    at MonoDevelop.Debugger.Soft.Unity.PosixDllLoader.LoadLibrary (System.String fileName) [0x00000] in <filename unknown>:0
    at MonoDevelop.Debugger.Soft.Unity.Usbmuxd.LoadDll (System.String nativeDll) [0x00000] in <filename unknown>:0
    at MonoDevelop.Debugger.Soft.Unity.Usbmuxd.Setup (System.String dllPath) [0x00000] in <filename unknown>:0
    at MonoDevelop.Debugger.Soft.Unity.iOSDevices.SetupDll (System.String path) [0x00000] in <filename unknown>:0
     
  13. lukaszunity

    lukaszunity

    Administrator

    Joined:
    Jun 11, 2014
    Posts:
    461
    Thanks for the report. I will have look.

    Regarding the 5.9.0 add-ins being included, the 5.9.1 add-ins did not make the cut for this build, but will be included in the next one.
     
  14. Ferazel

    Ferazel

    Joined:
    Apr 18, 2010
    Posts:
    517
    I tried giving this a go on my 10.11 (PB5) Mac using Unity 5.1.3 and received the following error log as soon as intellisense appeared to come up with a documentation window. In this cause it was "Application.OpenURL(" then the app would crash.

    Code (csharp):
    1. INFO [2015-08-26 00:30:02Z]: Starting MonoDevelop-Unity 5.9.4
    2. INFO [2015-08-26 00:30:02Z]: Running on Mono 4.0.2 ((detached/c99aa0c Fri Jul 10 13:28:51 CEST 2015)
    3. INFO [2015-08-26 00:30:02Z]: Using GTK+ 2.24.23
    4. INFO [2015-08-26 00:30:02Z]: Add-in loaded: MonoDevelop.Core
    5. INFO [2015-08-26 00:30:02Z]: Add-in loaded: MonoDevelop.Ide
    6. INFO [2015-08-26 00:30:02Z]: Add-in loaded: MonoDevelop.MacPlatform
    7. INFO [2015-08-26 00:30:02Z]: Initializing Runtime Mono 4.0.2
    8. ERROR [2015-08-26 00:30:02Z]: Error reading name for assembly '/Applications/Unity/MonoDevelop.app/Contents/Frameworks/Mono.framework/Versions/Current/lib/mono/4.5/EntityFramework.SqlServer.dll' in framework '.NETFramework,Version=v4.5.1':
    9. System.IO.FileNotFoundException: Could not load file or assembly '/Applications/Unity/MonoDevelop.app/Contents/Frameworks/Mono.framework/Versions/Current/lib/mono/4.5/EntityFramework.SqlServer.dll' or one of its dependencies. The system cannot find the file specified.
    10. File name: '/Applications/Unity/MonoDevelop.app/Contents/Frameworks/Mono.framework/Versions/Current/lib/mono/4.5/EntityFramework.SqlServer.dll'
    11.   at (wrapper managed-to-native) System.Reflection.Assembly:InternalGetAssemblyName (string,System.Reflection.AssemblyName)
    12.   at System.Reflection.AssemblyName.GetAssemblyName (System.String assemblyFile) [0x00000] in <filename unknown>:0
    13.   at MonoDevelop.Core.Assemblies.SystemAssemblyService.GetAssemblyNameObj (System.String file) [0x00000] in <filename unknown>:0
    14. ERROR [2015-08-26 00:30:02Z]: Error reading name for assembly '/Applications/Unity/MonoDevelop.app/Contents/Frameworks/Mono.framework/Versions/Current/lib/mono/4.5/EntityFramework.dll' in framework '.NETFramework,Version=v4.5.1':
    15. System.IO.FileNotFoundException: Could not load file or assembly '/Applications/Unity/MonoDevelop.app/Contents/Frameworks/Mono.framework/Versions/Current/lib/mono/4.5/EntityFramework.dll' or one of its dependencies. The system cannot find the file specified.
    16. File name: '/Applications/Unity/MonoDevelop.app/Contents/Frameworks/Mono.framework/Versions/Current/lib/mono/4.5/EntityFramework.dll'
    17.   at (wrapper managed-to-native) System.Reflection.Assembly:InternalGetAssemblyName (string,System.Reflection.AssemblyName)
    18.   at System.Reflection.AssemblyName.GetAssemblyName (System.String assemblyFile) [0x00000] in <filename unknown>:0
    19.   at MonoDevelop.Core.Assemblies.SystemAssemblyService.GetAssemblyNameObj (System.String file) [0x00000] in <filename unknown>:0
    20. Starting MonoDevelop-Unity
    21. INFO [2015-08-26 00:30:02Z]: Add-in loaded: MonoDevelop.Debugger
    22. INFO [2015-08-26 00:30:02Z]: Add-in loaded: MonoDevelop.SourceEditor2
    23. INFO [2015-08-26 00:30:02Z]: Add-in loaded: MonoDevelop.Boo
    24. INFO [2015-08-26 00:30:02Z]: Add-in loaded: MonoDevelop.DesignerSupport
    25. INFO [2015-08-26 00:30:02Z]: Add-in loaded: MonoDevelop.Refactoring
    26. INFO [2015-08-26 00:30:02Z]: Add-in loaded: MonoDevelop.CSharpBinding
    27. INFO [2015-08-26 00:30:02Z]: Add-in loaded: MonoDevelop.UnityScript
    28. INFO [2015-08-26 00:30:02Z]: Add-in loaded: Unity.Utilities
    29. INFO [2015-08-26 00:30:05Z]: Add-in loaded: MonoDevelop.Debugger.Soft
    30. INFO [2015-08-26 00:30:05Z]: Add-in loaded: MonoDevelop.Debugger.Soft.Unity
    31. INFO [2015-08-26 00:30:05Z]: Add-in loaded: MonoDevelop.Xml
    32. INFO [2015-08-26 00:30:05Z]: Add-in loaded: MonoDevelop.NUnit
    33.    Loading Workbench
    34. INFO [2015-08-26 00:30:06Z]: Add-in loaded: MonoDevelop.AssemblyBrowser
    35. INFO [2015-08-26 00:30:06Z]: Add-in loaded: MonoDevelop.RegexToolkit
    36.       Initializing Main Window
    37. INFO [2015-08-26 00:30:06Z]: Creating DefaultWorkbench
    38. INFO [2015-08-26 00:30:07Z]: Add-in loaded: MonoDevelop.ILAsmBinding
    39. INFO [2015-08-26 00:30:08Z]: Add-in loaded: MonoDevelop.HexEditor
    40. Loaded: /Applications/Unity/Unity.app/Contents/PlaybackEngines/iOSSupport/UnityEditor.iOS.Extensions.Native.dylib
    41. [usbmuxd] Start listen thread
    42. [usbmuxd] Listen thread started
    43. [usbmuxd] Send listen message
    44. INFO [2015-08-26 00:30:14Z]: CodeTemplateService: No user templates, reading default templates.
    45. Stacktrace:
    46.  
    47.   at <unknown> <0xffffffff>
    48.   at (wrapper managed-to-native) Pango.Layout.pango_layout_get_pixel_size (intptr,int&,int&) <0xffffffff>
    49.   at Pango.Layout.GetPixelSize (int&,int&) <0x00023>
    50.   at MonoDevelop.Components.FixedWidthWrapLabel.OnSizeRequested (Gtk.Requisition&) <0x00053>
    51.   at Gtk.Widget.sizerequested_cb (intptr,intptr) <0x00075>
    52.   at (wrapper native-to-managed) Gtk.Widget.sizerequested_cb (intptr,intptr) <0xffffffff>
    53.   at <unknown> <0xffffffff>
    54.   at (wrapper managed-to-native) Gtk.Application.gtk_main () <0xffffffff>
    55.   at Gtk.Application.Run () <0x0000b>
    56.   at MonoDevelop.Ide.IdeApp.Run () <0x0000b>
    57.   at MonoDevelop.Ide.IdeStartup.Run (MonoDevelop.Ide.MonoDevelopOptions) <0x018f7>
    58.   at MonoDevelop.Ide.IdeStartup.Main (string[],MonoDevelop.Ide.Extensions.IdeCustomizer) <0x00127>
    59.   at MonoDevelop.Startup.MonoDevelopMain.Main (string[]) <0x0001b>
    60.   at (wrapper runtime-invoke) <Module>.runtime_invoke_int_object (object,intptr,intptr,intptr) <0xffffffff>
    61.  
    62. Native stacktrace:
    63.  
     
    Last edited: Aug 26, 2015
  15. lukaszunity

    lukaszunity

    Administrator

    Joined:
    Jun 11, 2014
    Posts:
    461
    Thanks. Looks like there is an issue with how we package MonoDevelop on OSX, where we bundle Pango (used for text rendering and layout) and Pango crashes. This seems to be the case for the crash reports so far.
     
  16. Pharan

    Pharan

    Joined:
    Oct 28, 2013
    Posts:
    102
    OSX. It crashes when I bring up code completion/intellisense for method parameters.
    Also, it throws up something about needing Xcode and command line developer tools?

    I can repro consistently by making a new script, opening it, and then inside Start, typing "StartCoroutine(" or "gameObject.SetActive(". Just looking through member fields/properties does not seem to cause it to crash.

    I just copied the top part of the log. Not sure if this makes any sense. But the whole log was crazy long.
    Process: mono-sgen [1173]
    Path: /Applications/MonoDevelop.app/Contents/Frameworks/Mono.framework/Versions/Current/bin/mono
    Identifier: com.unity.monodevelop
    Version: 5.9.4 (5.9.4)
    Code Type: X86 (Native)
    Parent Process: ??? [1]
    Responsible: mono-sgen [1173]
    User ID: 503

    Date/Time: 2015-08-26 18:42:39.441 +0800
    OS Version: Mac OS X 10.10.5 (14F27)
    Report Version: 11
    Anonymous UUID: 256E1DEB-26DA-8C76-9B66-90D29CA960E4

    Time Awake Since Boot: 3300 seconds

    Crashed Thread: 0 Dispatch queue: com.apple.main-thread

    Exception Type: EXC_BAD_ACCESS (SIGABRT)
    Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000

    VM Regions Near 0:
    -->
    __TEXT 000000000002f000-0000000000502000 [ 4940K] r-x/rwx SM=COW /Applications/MonoDevelop.app/Contents/Frameworks/Mono.framework/Versions/Current/bin/mono-sgen

    Just curious. Is the Windows version more stable right now?
     
  17. sanpats

    sanpats

    Joined:
    Aug 24, 2011
    Posts:
    343
    Looking forward to the fixed version. I will turn back to the Xamarin Studio with Unity Add-ins for the time being. That one is rock solid stable for me.
     
  18. lukaszunity

    lukaszunity

    Administrator

    Joined:
    Jun 11, 2014
    Posts:
    461
    It tries to open the developer tools because of the crash. Yes, the Windows version is more stable because it runs on .NET, where as the OSX version runs on Mono.

    I've found the root cause of the crash on OSX and this will be fixed in the next alpha.
     
  19. Pharan

    Pharan

    Joined:
    Oct 28, 2013
    Posts:
    102
    Cool. I'll try the Windows version. I'll report back on any weird stuff that happens.

    Looking forward to MonoDevelop-Unity 5.9 though. Great work so far. :)


    EDIT: Ok, just right off the bat. MonoDevelop.exe doesn't seem to do anything. Doesn't launch. Nothing through command prompt either. Is there an error log somewhere it'd be logging to?
     
    Last edited: Aug 27, 2015
  20. lukaszunity

    lukaszunity

    Administrator

    Joined:
    Jun 11, 2014
    Posts:
    461
    I forgot to mention in the instructions above that you need to have .NET 4.5 installed on Windows for MonoDevelop to turn, but if Xamarin Studio runs, this build should also.

    The log files are stored in C:\Users\<username>\AppData\Local\MonoDevelop-Unity-5.0\Logs
     
  21. Pharan

    Pharan

    Joined:
    Oct 28, 2013
    Posts:
    102
    Ok, found the log:
    INFO [2015-08-27 07:53:23Z]: Starting MonoDevelop-Unity 5.9.4
    INFO [2015-08-27 07:53:23Z]: Running on Microsoft .NET 4.0.30319.42000
    INFO [2015-08-27 07:53:23Z]: Found GTK# version 2.12.25
    INFO [2015-08-27 07:53:23Z]: Using GTK+ 2.24.22
    ERROR: Add-in scan operation failed. The runtime may have encountered an error while trying to load an assembly.
    ERROR: Add-in scan operation failed (Could not load file or assembly 'file:///C:\Program Files Portable\MonoDevelop\bin\Mono.Addins.dll' or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515))
    ERROR: The add-in database could not be updated. It may be due to file corruption. Try running the setup repair utility
    ERROR: Add-in scan operation failed. The runtime may have encountered an error while trying to load an assembly.
    ERROR: Add-in scan operation failed (Could not load file or assembly 'file:///C:\Program Files Portable\MonoDevelop\bin\Mono.Addins.dll' or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515))
    ERROR: The add-in database could not be updated. It may be due to file corruption. Try running the setup repair utility
    System.InvalidOperationException: Extension node not found in path: /MonoDevelop/Core/WebCredentialProviders
    at Mono.Addins.ExtensionContext.GetExtensionObjects[T](String path, Boolean reuseCachedInstance) in c:\buildslave\monoDevNGExAddin\monodevelop\main\external\mono-addins\Mono.Addins\Mono.Addins\ExtensionContext.cs:line 636
    at Mono.Addins.ExtensionContext.GetExtensionObjects[T](String path) in c:\buildslave\monoDevNGExAddin\monodevelop\main\external\mono-addins\Mono.Addins\Mono.Addins\ExtensionContext.cs:line 607
    at Mono.Addins.AddinManager.GetExtensionObjects[T](String path) in c:\buildslave\monoDevNGExAddin\monodevelop\main\external\mono-addins\Mono.Addins\Mono.Addins\AddinManager.cs:line 629
    at MonoDevelop.Core.WebRequestHelper.Initialize() in c:\buildslave\monoDevNGExAddin\monodevelop\main\src\core\MonoDevelop.Core\MonoDevelop.Core\WebRequestHelper.cs:line 49
    at MonoDevelop.Core.Runtime.Initialize(Boolean updateAddinRegistry) in c:\buildslave\monoDevNGExAddin\monodevelop\main\src\core\MonoDevelop.Core\MonoDevelop.Core\Runtime.cs:line 118
    Starting MonoDevelop-Unity
    ERROR [2015-08-27 07:53:24Z]: MonoDevelop-Unity failed to start. Some of the assemblies required to run MonoDevelop-Unity (for example gtk-sharp)may not be properly installed in the GAC.
    System.InvalidOperationException: Extension node not found in path: /MonoDevelop/Core/PlatformService
    at Mono.Addins.ExtensionContext.GetExtensionObjects(String path, Type arrayElementType, Boolean reuseCachedInstance) in c:\buildslave\monoDevNGExAddin\monodevelop\main\external\mono-addins\Mono.Addins\Mono.Addins\ExtensionContext.cs:line 669
    at Mono.Addins.AddinManager.GetExtensionObjects(String path) in c:\buildslave\monoDevNGExAddin\monodevelop\main\external\mono-addins\Mono.Addins\Mono.Addins\AddinManager.cs:line 553
    at MonoDevelop.Ide.DesktopService.Initialize() in c:\buildslave\monoDevNGExAddin\monodevelop\main\src\core\MonoDevelop.Ide\MonoDevelop.Ide\DesktopService.cs:line 56
    at MonoDevelop.Ide.IdeStartup.Run(MonoDevelopOptions options) in c:\buildslave\monoDevNGExAddin\monodevelop\main\src\core\MonoDevelop.Ide\MonoDevelop.Ide\IdeStartup.cs:line 173
    at MonoDevelop.Ide.IdeStartup.Main(String[] args, IdeCustomizer customizer) in c:\buildslave\monoDevNGExAddin\monodevelop\main\src\core\MonoDevelop.Ide\MonoDevelop.Ide\IdeStartup.cs:line 658

    I'll see if there's anything I can do on my end to get it to work based on the log.

    I'm on Windows 10 and I checked what .NET version I had installed. Does this not have me covered?
    dotnetinstalled.png
    Anyway, I'll (re)download .NET and see if it'll work.
    EDIT: Nope. Wouldn't let me install it. It says I already have it (or an updated version) installed.
     
    Last edited: Aug 27, 2015
  22. lukaszunity

    lukaszunity

    Administrator

    Joined:
    Jun 11, 2014
    Posts:
    461
    I think your .NET install is fine.

    I think the problem in this case might be that you need to right click the MonoDevelop zip file, select "Properties" and then "Unblock" before you unpack it. It looks like Windows is blocking loading of the managed assemblies.
     
  23. Pharan

    Pharan

    Joined:
    Oct 28, 2013
    Posts:
    102
    Cool. That fixed it. :D

    I'll let you know if something weird happens while I use it.

    EDIT:
    I was digging through the preferences and I found that it actually has detailed "Source Analysis" preferences. Are all these preferences compatible with Unity's older Mono compiler supported language features?

    I meant in the context of, C# since Roslyn has the ?. operator. I didn't find that in particular, but I remember MonoDevelop 4.x had some weird errors when I used named/optional arguments but the Unity compiler seemed to compile them fine except in certain situations.
     
    Last edited: Aug 27, 2015
  24. lukaszunity

    lukaszunity

    Administrator

    Joined:
    Jun 11, 2014
    Posts:
    461
    We currently do not use the Unity Mono C# compiler when building projects in MonoDevelop, so there are some differences in compiler behavior between building in MonoDevelop and building in Unity. Any source analysis features you see in MonoDevelop completely contained within MonoDevelop and are in no way affected by how the Unity C# compiler works.

    For Unity 5.4 we currently have MonoDevelop and Unity REST Integration on the roadmap and once that is released, we will always build projects opened in MonoDevelop using Unity and then provide the build results from Unity in MonoDevelop. At that point in time the build results in MonoDevelop and Unity will always be the same.
     
  25. sanpats

    sanpats

    Joined:
    Aug 24, 2011
    Posts:
    343
    Looking forward to the next alpha. Will it release soon?
     
  26. Pharan

    Pharan

    Joined:
    Oct 28, 2013
    Posts:
    102
    Oh, so that's what REST Integration was for. I was vaguely wondering what Unity Editor had to do with talking in http.

    Anyway, I LOVE the Source Analysis stuff this has. I had to tinker around a bit with the preferences to get it to ignore some Unity things but it seems to work great otherwise.

    I know it's a Visual Studio thing too but in the many occasions I tried to switch to it, Visual Studio's intellisense really annoyed me (or I couldn't figure out how to get it to sort its member suggestions according to the base class it belongs to like MD/Xamarin does by default, which is important for MonoBehaviours 'cause if I have to extend one of my own classes, intellisense suggestions turns into a mess of a list of members). That and UnityVS is inconvenient and somehow keeps breaking for me. :c
     
    Last edited: Aug 28, 2015
  27. jojo665_

    jojo665_

    Joined:
    Feb 16, 2014
    Posts:
    4
    as much as i understand the reason for branching off MD59, i actually prefers the style of initial alpha test -- ie release unity tools as addon for XS. This allow others to upgrade XS as needed without waiting for unity. This is similar to how VisualStudio+SyntaxTree+Unity, which is awesome

    eg, we waited over year for upgrading from MD2 to MD4, and then ~2 years from MD4 to MD5... and are stuck with various bug in MD during those time, most are already fixed in XS

    2 cents
     
    Ferazel, Pharan and sanpats like this.
  28. Pharan

    Pharan

    Joined:
    Oct 28, 2013
    Posts:
    102
    The default language in the Assembly Browser seems to be "Summary". I didn't notice it at first so I thought something was wrong when it just showed me a bunch of method signatures and properties instead of showing me the actual implementation. (I was checking the UnityEngine.Color type to double-check if I could use the * operator to multiply it by a float, and to confirm if that did what I thought it did-- trivia: it multiplies all channels including alpha, so it's pretty useless for sprites or premultiplied shaders).

    Turns out you have to select "C#" in Language the dropdown on the upper right to show the method bodies.

    Seems like some Unity-helpful defaults from MonoDevelop-Unity 4 aren't in this build yet.
     
    Last edited: Aug 29, 2015
    ThinhHB and sanpats like this.
  29. liortal

    liortal

    Joined:
    Oct 17, 2012
    Posts:
    3,562
    Is this a complete MonoDevelop install, or just the add-in?

    I already have Xamarin Studio installed. Can i still use it with this or is this a completely independant install ?
     
  30. Ferazel

    Ferazel

    Joined:
    Apr 18, 2010
    Posts:
    517
    This is the entire app, not a plug-in like the previous tests were.

    I understand why they want to keep a solid version that they can maintain and package with Unity. I think the idea is that they want to maintain just one version of the IDE rather than trying to support every new version that comes down the pipe. The problem is that Unity has been very slow to update in the past and we've been stuck with broken or buggy versions of MonoDevelop for years before they decide to update again.
     
  31. liortal

    liortal

    Joined:
    Oct 17, 2012
    Posts:
    3,562
    @Ferazel isn't updating a single version what they've done so far?

    The problem is that they're lagging behind new releases, not to mention the MonoDevelop version that is currently bundled is severely buggy :)

    BTW - i was playing with this new experimental version today and it crashes around 5 times on me. I currently switched back to the default one.
     
  32. lukaszunity

    lukaszunity

    Administrator

    Joined:
    Jun 11, 2014
    Posts:
    461
    Regarding the lack of MonoDevelop updates in the past and releasing MonoDevelop-Unity vs just the Unity Add-ins:

    Previously we forked the official MonoDevelop/Xamarin Studio repository and as issues with our MonoDevelop-Unity build were discovered, we would fix them in our fork, but not get the fixes into the official repository. This is the reason why Xamarin Studio 5.9 opens a new window every time you click a script on Windows, but MonoDevelop-Unity 4.0.1 does not.

    As time passed, the official MonoDevelop repository diverged from our fork and it made it difficult to update MonoDevelop due to our local fixes. Also, the APIs for the add-ins changed, so it was no longer possible to just install the MonoDevelop 4.0.1 add-ins into a newer Xamarin Studio.

    We have learned from the past and we are now trying to avoid getting into the same situation again. The first step was to update our add-ins to work with the latest MonoDevelop/Xamarin Studio. We then decided to release these early so the developers could test them and get a short term solution to some of the issues with MonoDevelop-Unity 4.0.1.

    The next step is to fix all the Unity specific issues in MonoDevelop 5.9, as we had done with MonoDevelop-Unity 4.0.1. But this time we are actively working on getting the changes into the official MonoDevelop/Xamarin Studio repository, so that we in the future can bundle a completely unmodified version of MonoDevelop. This is what we are currently working on. This will solve the problem of updating MonoDevelop in future being difficult for us.

    In the end we have to provide complete builds of MonoDevelop with Unity, as you need to be able to edit scripts when you double click them in the editor. The MonoDevelop builds we will be providing with Unity 5.3 are the ones we are making available in this thread to all developers interested in providing early feedback.

    However, if you want to keep using the Unity Add-Ins with Xamarin Studio, it is possible for you to generate the .mpacks yourself from the MonoDevelop builds in this thread. I should remind you that this is not officially supported by Unity and that if you experiencing issue with Xamarin Studio that you do not with the builds in this thread, then it is likely that the issue has only be fixed in our local builds and we have not yet gotten the changes into the official MonoDevelop repository, but we are working on it!

    On OSX install the Mono framework and extract MonoDevelop.app to your desktop, you can use the shell script below to generate the .mpacks and install them in Xamarin Studio. You can also change the MD_PATH variable to point another location within your user directory where you extracted MonoDevelop.app. The .mpacks can also be generated on Windows by calling mdtool.exe with the same parameters on the Unity Add-ins .dll files.

    Code (csharp):
    1. #!/bin/sh
    2. export MD_PATH="${HOME}/Desktop/MonoDevelop.app/Contents/MacOS/lib/monodevelop"
    3. mono "${MD_PATH}/bin/mdtool.exe" setup pack "${MD_PATH}/Addins/MonoDevelop.Boo.UnityScript.Addins/Boo.MonoDevelop.dll"
    4. mono "${MD_PATH}/bin/mdtool.exe" setup pack "${MD_PATH}/Addins/MonoDevelop.Boo.UnityScript.Addins/UnityScript.MonoDevelop.dll"
    5. mono "${MD_PATH}/bin/mdtool.exe" setup pack "${MD_PATH}/Addins/MonoDevelop.Debugger.Soft.Unity/MonoDevelop.Debugger.Soft.Unity.dll"
    6. mono "${MD_PATH}/bin/mdtool.exe" setup pack "${MD_PATH}/Addins/MonoDevelop.Debugger.Soft.Unity/UnityUtilities.dll"
    Regarding the crashes on OSX, these should be fixed and the fixes will be included in the next release.
     
    jojo665_ and Pharan like this.
  33. Pharan

    Pharan

    Joined:
    Oct 28, 2013
    Posts:
    102
    [Windows]
    I'm not sure if it's helpful, but I was checking the Log Directory and I noticed some logs were unusually large, like almost 1MB large with errors that just keep repeating.

    The stacktraces seem to have this in common at the top:

    WARNING [2015-08-31 15:12:17Z]: Pango-Warning: pango_layout_set_markup_with_accel: Unknown tag 'Collider' on line 1 char 106
    Stack trace:
    at Pango.Layout.pango_layout_set_markup(IntPtr raw, IntPtr markup, Int32 length)
    at Pango.Layout.SetMarkup(String markup)
    at MonoDevelop.Components.FixedWidthWrapLabel.SetLayoutMarkupAndResize() in c:\buildslave\monoDevNGExAddin\monodevelop\main\src\core\MonoDevelop.Ide\MonoDevelop.Components\FixedWidthWrapLabel.cs:line 239
    at MonoDevelop.Components.FixedWidthWrapLabel.CreateLayout() in c:\buildslave\monoDevNGExAddin\monodevelop\main\src\core\MonoDevelop.Ide\MonoDevelop.Components\FixedWidthWrapLabel.cs:line 95
    at MonoDevelop.Components.FixedWidthWrapLabel.OnStyleSet(Style previous_style) in c:\buildslave\monoDevNGExAddin\monodevelop\main\src\core\MonoDevelop.Ide\MonoDevelop.Components\FixedWidthWrapLabel.cs:line 139

    On another file, this was the repeated log:
    WARNING [2015-08-27 18:30:26Z]: Gtk-Warning: Failed to set text from markup due to error parsing markup: Error on line 1 char 57: Element 'markup' was closed, but the currently open element is 'T'
    Stack trace:
    at Gtk.Dialog.gtk_dialog_run(IntPtr raw)
    at Gtk.Dialog.Run()
    at Mono.TextEditor.GtkWorkarounds.RunDialogWithNotification(Dialog dialog) in c:\buildslave\monoDevNGExAddin\monodevelop\main\src\core\Mono.Texteditor\Mono.TextEditor\Gui\GtkWorkarounds.cs:line 322
    at MonoDevelop.Ide.MessageService.RunCustomDialog(Dialog dialog, Window parent) in c:\buildslave\monoDevNGExAddin\monodevelop\main\src\core\MonoDevelop.Ide\MonoDevelop.Ide\MessageService.cs:line 377

    There weren't any problems while I was using it though.
     
  34. lukaszunity

    lukaszunity

    Administrator

    Joined:
    Jun 11, 2014
    Posts:
    461
    I think this either because you have an older GTK# version installed or this is an issue they fixed in Xamarin Studio 5.9.5.

    "Fixed: Fixed GTK log spew that can potentially cause IDE slowness"

    https://developer.xamarin.com/releases/studio/xamarin.studio_5.9/xamarin.studio_5.9/

    We will also update MonoDevelop to version 5.9.5 soon.
     
  35. sanpats

    sanpats

    Joined:
    Aug 24, 2011
    Posts:
    343
    Will we see the fixed OSX alpha this week?
     
  36. lukaszunity

    lukaszunity

    Administrator

    Joined:
    Jun 11, 2014
    Posts:
    461
    Yes.
     
  37. liortal

    liortal

    Joined:
    Oct 17, 2012
    Posts:
    3,562
    Is the update going to be posted here on this thread ?
     
  38. lukaszunity

    lukaszunity

    Administrator

    Joined:
    Jun 11, 2014
    Posts:
    461
    Yes, I will continue to post new builds in this thread until Unity 5.3 ships, at which point only the regular releases and patch releases will contain updates to MonoDevelop.
     
  39. lukaszunity

    lukaszunity

    Administrator

    Joined:
    Jun 11, 2014
    Posts:
    461
    Alpha 2 is now available for download.

    Release notes

    Alpha 2
    • Fixed issue with MonoDevelop crashing on OSX.
    • Regression: MonoDevelop OSX must be installed in path without spaces.
    • Fixed issue with being unable to set conditional breakpoints.
    • Bundled GTK# installer. Will be installed by the Unity installer for Unity 5.3.
     
  40. sanpats

    sanpats

    Joined:
    Aug 24, 2011
    Posts:
    343
    Alpha 2 is very stable on OS X now. No previous crashing.
     
  41. Pharan

    Pharan

    Joined:
    Oct 28, 2013
    Posts:
    102
    [Windows]
    I can't put my finger on the cause but it seems slower and more buggy than the last build, though that could just be me. It occasionally fails to load projects and I have to tell it to reload or, worse, restart the whole program. (This was a problem for me in MD 4.x and it frustrated me to no end.)
    And now the usings (particularly `using UnityEngine`, and everything dependent on it) turn red for like 5 to 10 seconds before stuff finally loads correctly.

    No logs though. I'm not even sure if I did something to cause it on my end.
     
  42. lukaszunity

    lukaszunity

    Administrator

    Joined:
    Jun 11, 2014
    Posts:
    461
    The Windows build should be more or less identical. What feels slow for you, it might be worth profiling and see if anything can be done to speed things up.

    How frequently do the project fail to load and are you doing anything specific that might trigger it? Like adding multiple script files after each other in Unity or something similar that cause multiple updates to the project and MD fails to load the project.

    Regarding using UnityEngine turning red for 5-10 seconds, what are the repro steps for this?
     
    Last edited: Sep 2, 2015
  43. Pharan

    Pharan

    Joined:
    Oct 28, 2013
    Posts:
    102
    It usually seems to happen the first time I open MD. But it doesn't happen all the time.
    The Assembly-CSharp-firstpass project seems to fail most frequently.

    I'll try to figure out how to repro reliably and I'll post here again if I have details.
     
  44. liortal

    liortal

    Joined:
    Oct 17, 2012
    Posts:
    3,562
    With the latest version, no more crashes (so far, knock on wood).

    Note that i don't have the decompilation feature (e.g: navigate into Unity's built in classes) as i used to have with the older MonoDevelop :(
     
  45. lukaszunity

    lukaszunity

    Administrator

    Joined:
    Jun 11, 2014
    Posts:
    461
    When you open the Assembly Browser you can select "C#" instead of "Summary" in the top right drop down.
     
    liortal likes this.
  46. Arx

    Arx

    Joined:
    Jan 28, 2014
    Posts:
    22
    I'm trying this out and so far it's without problems. However, is there any way to enable Version Control tools (e.g. Git Support) in this MonoDevelop-Unity?
     
  47. liortal

    liortal

    Joined:
    Oct 17, 2012
    Posts:
    3,562
    Also, i couldn't get tooltips with variable values while debugging today. need to test that again to see i wasn't daydreaming due to lack of coffee.
     
  48. lukaszunity

    lukaszunity

    Administrator

    Joined:
    Jun 11, 2014
    Posts:
    461
    Not currently, we have removed all default add-ins that were not required for Unity development. We could add the git add-in and disable it by default.
     
  49. seaders

    seaders

    Joined:
    Oct 28, 2014
    Posts:
    29
    Since we started using Xamarin, we definitely got used to some of the other available Xamarin tools (specifically Android Device Manager et al). Will we be able to install those plugins here as well? If not, what tools will be available, because if we're left with having to not getting this at all from the IDE, it's a hard sell for me.
     
  50. Deleted User

    Deleted User

    Guest

    So does this mean we can use .NET 4.5 when releasing builds or are we still stuck with a .NET 3.5 subset?
     
Thread Status:
Not open for further replies.