Monodevelop

Package Details: monodevelop-bin 7.8.4.1_0xamarin6_ubuntu1804b1-2

MonoDevelop is an open-source integrated development environment for Linux, macOS, and Windows. It’s used for the development of projects that use Mono and.NET frameworks. It is also known a. MonoDevelop is an IDE primarily designed for C# and other.NET languages it is an open source integrated development environment for the Linux platform, Mac OS X, and Microsoft Windows. It enables developers to quickly write desktop and ASP.NET Web applications on Linux, Windows and Mac OSX.

Package Actions

  • View PKGBUILD / View Changes
Git Clone URL: https://aur.archlinux.org/monodevelop-bin.git (read-only, click to copy)
Package Base: monodevelop-bin
Description: MonoDevelop is a GNOME IDE primarily designed for C# and other CLI (.NET) languages
Upstream URL: https://github.com/mono/monodevelop
Licenses: MIT
Conflicts: monodevelop
Provides: monodevelop
Submitter: SolarAquarion
Maintainer: SolarAquarion
Last Packager: SolarAquarion
Votes: 10
Popularity: 0.62
First Submitted: 2019-08-26 03:11
Last Updated: 2020-04-08 12:46

Dependencies (3)

  • gtk-sharp-2(gtk-sharp-2-git)
  • gtk-sharp-3(gtk-sharp-git, gtk-sharp-3-git, gtk-sharp-3-mono-git)
  • fsharp(fsharp-mono-bin, fsharp-git)(optional) – for building fsharp programs

Required by (4)

  • hexchat-theme-manager(requires monodevelop)(make)
  • janet(requires monodevelop)
  • monogame-git(requires monodevelop)(make)

sum01 commented on 2020-09-06 01:25

mono-msbuild is a required dependency to create projects. The program does start without it, but you cannot actually make anything without this dependency. See https://github.com/mono/monodevelop/issues/6684

Peredo commented on 2020-07-25 18:39

warwickmm commented on 2020-07-03 22:35

Is gtk-sharp-3 really a required dependency? I was having issues elsewhere on my system when gtk-sharp-3 is installed. After I removed gtk-sharp-3 from the PKGBUILD dependencies, monodevelop still seemed to work without any issues.

palein commented on 2020-05-18 21:26

Outdated binary. Compiling any program with this version requires dotnet core 1.1 which is outdated and can't be build.

erayerdin commented on 2020-03-29 23:20

Alright, the issue is solved.

A temporary solution (I hope maintainer will fix it) is to do the steps below. Also have yay and nano (or a text editor of your choice) installed, otherwise, your installation process might differ.

  1. Install gtk-sharp-2 and gtk-sharp-3 packages as I've told you. I don't know if this fixes the issue but better be safe than sorry.

  2. Then do yay -S monodevelop-bin --editmenu --mflags --skipinteg. What this does it to enable editing PKGBUILD on the run and skip integration checking. Integration checks are usually needed but I suppose you trust your government, ISP or network in this case (so they won't inject arbitrary code into the package you download).

  3. If you have tried to install the package before, you probably have your build cached. yay will ask you to cleanBuild. Simply press 1 and clean the build or it will use the previous build and it won't work.

  4. When you come to 'Edit PKGBUILD' step, say yes, type nano (or your editor choice). This will open up the editor. If you do not know how to use nano, google it. It's the simplest terminal editor to use.

  5. When your editor opens up, as hussam says, change arm64.deb bit to amd64.deb. I have checked the URL, they have the package.

  6. Save and exit the editor. Then, it will install the package.

You will then finally be able to launch monodevelop. Hope this helps.

erayerdin commented on 2020-03-29 23:04

Running 'sudo pacman -S gtk-sharp-2 gtk-sharp-3' on Manjaro will resolve sudden exit, yet it still hangs there and will not launch.

hussam commented on 2020-02-18 17:48

That's expected. He is using the arm64 bit binary.source=('monodevelop-amd64-v${_pkgver}.deb::http://download.mono-project.com/repo/ubuntu/pool/main/m/monodevelop/monodevelop_7.8.4.1-0xamarin6+ubuntu1804b1_arm64.deb')You want the amd64 binary instead.

notfood commented on 2020-02-18 16:53

Is it launching for anyone else? Running monodevelop just exits with no error for me.

rrprabhu commented on 2020-02-08 23:37

Monodevelop Vs Visual Studio

SolarAquarion commented on 2019-12-20 13:51

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.

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.

In Windows, the CBinding supports the following toolchains:

  • MinGW32
  • CLang
  • Visual Studio 15 2017
  • Visual Studio 14 2015
  • Visual Studio 12 2013
Monodevelop

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.

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 :)

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.com

The code can be found here:

Monodevelop

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!