MonoDevelop is a simple multiplatform Integrated Development Environment. MonoDevelop is an Integrated Development Environment (IDE) for multiple operating systems, including Linux, Mac OS X and Windows. Developers can use it to create both desktop and web applications. Most importantly, to keep MonoDevelop open sourced, Microsoft had to release certain code base from VS for Windows (such as vstest, and part of the code editor) under an open source license. This often requires a lengthy internal process with legal guys, and lots of efforts to clean up the code. MonoDevelop is a Mono/C# Integrated Development Environment for Windows, Linux and macOS. It parses your C# and VB programs as you type them and is able to provide contextual completion of methods. In late 2003, a few developers from the Mono community began migrating SharpDevelop, a successful.NET open source IDE from System.Windows.Forms on.
Author: Anubhav Singh
The MonoDevelop IDE is built around the concept of an extension tree. An extension package is a set of extensions that plug into extension points to add functionality to the IDE. The whole IDE is built this way.
- Phablet con sistema operativo iOS, display da 9.70 pollici, risoluzione massima di 2048 x 1536 pixel pari ad un rapporto di 264 Pixel per pollice (PPI).
- MonoDevelop is installed by default with Unity, although there is the option to exclude it from the installation on Windows. You should check that MonoDevelop is set as the external script editor in the Preferences (menu: Unity Preferences and then select the External Tools panel).
The CBinding extension package enables developers to write C/C++ solutions in the IDE. However, there were many features missing in it. My project was about writing some of those features and make changes to existing ones.
I have been working in this over past 4 months as part of Google Summer of Code 2017 student and there are still lot of things that are yet to be done! The very first feature I worked on was implementing support to be able to use compilers present on Windows (GCC, MSVC, mingw32 etc..). This was done via CMake as that’s the only project format currently supported.
Monodevelop8
In Windows, the CBinding supports the following toolchains:
- MinGW32
- CLang
- Visual Studio 15 2017
- Visual Studio 14 2015
- Visual Studio 12 2013
Users can easily switch between these toolchains using Tools > Options. It currently lists available toolchains based upon the platform (Windows, Linux, Mac) but I plan to write an additional check to load only the toolchains installed on that particular platform.
Monodevelop Vs Visual Studio
The old “MD1” project system and templates are removed from the CBinding and now it only supports CMake. For code completion, CLangManager now targets CMake project system.
Since the inception of CBinding, MonoDevelop’s codebase has changed a lot and the extensions still use some of the APIs of MonoDevelop that are no longer public, so enabling some functionality required changing the MonoDevelop codebase and upstreaming these changes, this is in progress :)
Monodevelop Windows Binaries
Apart from this, the CMake projects subclass SolutionItem but it needs some functionality from the Project base class which is quite specific to MSBuild project system, so I have done some chaining between the Project and SolutionItem/WorkspaceObject in the MonoDevelop source code to allow CBinding to use those properties.
Monodevelop Ubuntu
The code can be found here:
Overall it was a great learning experience which I would like to continue further. I would like to thank the entire Mono organisation specially Mikayla Hutchinson for being a constant support for me. Understanding and working on such a large codebase was an ultimate experience. I had a lot of fun this summer!