Mono Download Mac


Supported on GNU/Linux, Mac OS X and Windows. MonoDevelop is a multiplatform application, supported on GNU/Linux, Mac OS X and Microsoft Windows operating systems. All GNU/Linux distributions are supported, allowing the user to easily install the application using the built-in Software. The recently updated Mono 1.2.6 package for MacOS X contains Imendio's Native Gtk+ for OSX, Gtk# and MonoDevelop 0.18.1 with Mac support. It is now available from Mono's downloads page. It appears that you have to run all three of these installs to get it to work: Mono 2.25 Framework - Universal; MonoDevelop 2.0 Alpha 2; Cocoa# 0.9.4 source.

Linux

  1. Pair to Mac performs necessary software installations/updates when Visual Studio 2019 is connecting to the Mac. Pair to Mac will check to make sure that Mono is installed. If it is not installed, Pair to Mac will download and install the latest stable version of Mono on the Mac.
  2. 1 Add the Mono repository to your system. The package repository hosts the packages you need, add it with the following commands. Note: the packages should work on newer Ubuntu versions too but we only test the ones listed below. Ubuntu 18.04 (i386, amd64, armhf) sudo apt install apt-transport-https dirmngr sudo apt-key adv -keyserver hkp://keyserver.ubuntu.com:80 -recv-keys.
  3. Making the web more beautiful, fast, and open through great typography.
  4. Mono/Poly V2 for Mac/Win is included in the KORG Collection 3. The Full Version of 11 pieces of KORG software. All at once you will be able to get the famous analog machines that laid the groundwork for the synthesizer as an instrument in the 1970s and early 80s, as well as the well-known digital machines that changed the history of music in.

Installing dependencies

MonoDevelop requires the following packages (or newer versions):

JetBrains Mono uses a 9° angle; this maintains the optimal contrast to minimize distraction and eye strain. Only for “a”, “y”, and “f” is the construction taken from True italic to slightly enhance the horizontal flow for the eyes.

  • Mono 5.10
  • Mono.Addins 0.6
  • Gtk# 2.12.45
  • monodoc 1.0
  • F# (fsharpc program)
  • cmake
  • libssh2

You can build them from git, source releases or, even easier, simply install the pre-built packages appropriate for your platform.

We strongly recommend you install everything from packages if possible. If not, you should use a Parallel Mono Environment. Do not install anything to /usr or /usr/local unless you completely understand the implications of doing so.

Note that if your distro has sufficiently up-to-date Gtk# or Mono.Addins packages, you can configure a parallel Mono environment to use them instead of building them from source. See the section on MONO_GAC_PREFIX in the Parallel Mono Environment guide.

Building from Git

After getting the source code from GitHub, run the following code in the root directory:

It may fail because of missing dependencies; install them, and re-run the command.

This script allows selecting and configuring a set of MonoDevelop modules to be included in an integrated build. The MonoDevelop build system consists of a ‘main’ module, which contains the main distribution, and a number of additional add-ins in subdirectories of ‘extras’.
The ‘extras’ add-ins are designed to be built and distributed separately, and therefore build against your system-installed MonoDevelop by default. However, this script sets them up to build against the MonoDevelop in ‘main’, and ensures that they will be loaded when MonoDevelop is launched with ‘make run’ in this top-level directory. This is very useful for development and testing.

You can select the list of extra add-ins to be built by running this command:

Further executions of the configure script will configure only the selected add-ins.
You can also configure a predefined list of modules by specifying a build profile using the –profile option. Use the –help option to get information about available profiles and other build options.

Linux: Running

Since you’ll be working on the development version, it’s best not to install it; instead, you can use

to run it without installing it. It is a good idea to keep separate copies for using and developing.

Building from Tarballs

MonoDevelop is split in several tarballs: one for the main application, and one for each optional add-in. You can get the tarballs from the Download page.

First of all you have to configure and install the main tarball:

The configure script may fail because of missing dependencies; install them, and re-run the command.

After this, you can build and install any of the additional tarballs using the same procedure.

macOS

Building MonoDevelop from source on the Mac is straightforward when the latest Mono SDK package is installed. In general, the instructions in Development:Getting Started can be applied directly to building MD on macOS. However, there are a few caveats, so this page explains the Mac build process in more detail.

Building using Makefiles

Building

First you will need Xcode installed. If you have Xcode 4.3 or later, you will need to then install the Xcode Commandline tool from Xcode preferences, and install autoconf and automake from brew.

NOTE: Please ensure that you have the very latest Mono MDK.

Check out MD, configure using the Mac profile:

NOTE: DO NOT use configure –select on Mac - the Mac profile passes adds required arguments to the configuration of main. Instead edit profiles/mac manually to add any additional modules.

IMPORTANT: Do not install MonoDevelop into the install prefix. MonoDevelop will pick up libraries from the prefix automatically. If you configured with a non-default prefix, then when you build an app bundle, the entire prefix will be merged into the app bundle.

Things you might have to do before running the configure script

  1. Tell aclocal where to find the pkgconfig M4 macro (pkg.m4), e.g.

    Comment: this did not appear necessary

  2. Add the GTK+ libraries’ location to the Mac dynamic loader path:

    Comment: this did not appear necessary

Building extras

To include additional addins from extras in the build, instead of using the Mac profile, use configure --select to select addins. This will write the default profile. Next, replace the line in profiles/default that begins with “main” with the one from profiles/mac, then run configure again using the default profile.

Mac: Running

To run MD, simply use:

Building the App package

To build the app package, navigate to the macOS build directory:

From here, build the MonoDevelop.app using make app. You can then build the .dmg using the ./make-dmg-bundle.sh script. To include addins from extras, manually copy their build directories into the MonoDevelop.app directory, e.g.

Building using MonoDevelop

When building MonoDevelop using MonoDevelop, be sure to select the Mac configuration, as this will enable building only the addins that work on Mac.

Main

Building main is straightforward. Open main/Main.sln, select the Mac configuration, and run the Build command. Note that running MonoDevelop from within MD will currently only work if you export DYLD_FALLBACK_LIBRARY_PATH as described above.

Extras

Loading the full MonoDevelop.mdw workspace and building the addin solutions from extras will only work if the Makefiles’ configure script has been run. Even then, not all of them will build correctly. Until this is resolved, use the makefiles to build extras.

TL;DR - Getting a MD Master App Bundle

Install the latest Mono MDK (2.10.6 at the time of writing) and git. Then run the following commands

To update, run the following commands in the monodevelop directory:

Windows

Prerequisites and Source

  • Install Visual Studio 2017 with the .NET Desktop and .NET Core workloads and the F# optional component (note, F# is disabled by default so need to enable it in the VS installer).
  • Install Git for Windows (from here)
  • Make sure you have .NET Framework 4.7.1 Reference Assemblies (4.7.1 Targeting Pack)
  • Install Gtk# (installer). Direct link: gtk-sharp-2.12.45.msi
  • Install the Mono libraries package (installer)
  • Install GNU Gettext tools (from here)

Building using Visual Studio or MonoDevelop

Monodevelop For Mac Os X 10.8

You need at least Visual Studio 2017 or MonoDevelop 7.1

Monodevelop Download

  • git clone https://github.com/mono/monodevelop --recursive -j8
  • Open main/Main.sln.
  • Select the DebugWin32 configuration and Any CPU platform (this is important!).
  • Build the solution.

Mac Os X El Capitan

Building using MSBuild

Monodevelop Ide Windows

Monoproxymac

Open a Command Prompt in main and run winbuild.bat. You can easily run MD directly after building with the winbuild.bat script (run monodevelopmainbuildbinmonodevelop.exe).


-->

This guide describes how to use Pair to Mac to connect Visual Studio 2019to a Mac build host. The same instructions apply to Visual Studio 2017.

Overview

Building native iOS applications requires access to Apple's build tools,which only run on a Mac. Because of this, Visual Studio 2019 must connect toa network-accessible Mac to build Xamarin.iOS applications.

Visual Studio 2019's Pair to Mac feature discovers, connects to,authenticates with, and remembers Mac build hosts so that Windows-basediOS developers can work productively.

Pair to Mac enables the following development workflow:

Mono

  • Developers can write Xamarin.iOS code in Visual Studio 2019.

  • Visual Studio 2019 opens a network connection to a Mac build host anduses the build tools on that machine to compile and sign the iOS app.

  • There is no need to run a separate application on the Mac – VisualStudio 2019 invokes Mac builds securely over SSH.

  • Visual Studio 2019 is notified of changes as soon as they happen. Forexample, when an iOS device is plugged in to the Mac or becomes availableon the network, the iOS Toolbar updates instantly.

  • Multiple instances of Visual Studio 2019 can connect to the Macsimultaneously.

  • It's possible to use the Windows command-line to build iOS applications.

Note

Before following the instructions in this guide, complete the following steps:

  • On a Windows machine, install Visual Studio 2019
  • On a Mac, install Xcode and Visual Studio for Mac
    • You must manually open Xcode after installing so that it can add any additional components.

If you would prefer not to install Visual Studio for Mac, Visual Studio 2019can automatically configure the Mac build host with Xamarin.iOS and Mono.You must still install and run Xcode.For more information, see Automatic Mac provisioning.

Enable remote login on the Mac

To set up the Mac build host, first enable remote login:

  1. On the Mac, open System Preferences and go to the Sharing pane.

  2. Check Remote Login in the Service list.

    Make sure that it is configured to allow access for All users, orthat your Mac username or group is included in the list of allowedusers.

  3. If prompted, configure the macOS firewall.

    If you have set the macOS firewall to block incoming connections, youmay need to allow mono-sgen to receive incoming connections. An alertappears to prompt you if this is the case.

  4. If it is on the same network as the Windows machine, the Mac shouldnow be discoverable by Visual Studio 2019. If the Mac is still notdiscoverable, try manually adding a Mac or takea look at the troubleshooting guide.

Connect to the Mac from Visual Studio 2019

Now that remote login is enabled, connect Visual Studio 2019 to the Mac.

  1. In Visual Studio 2019, open an existing iOS project or create a new oneby choosing File > New > Project and then selecting an iOS projecttemplate.

  2. Open the Pair to Mac dialog.

    • Use the Pair to Mac button iOS toolbar:

    • Or, select Tools > iOS > Pair to Mac.

    • The Pair to Mac dialog displays a list of all previously-connectedand currently-available Mac build hosts:

  3. Select a Mac in the list. Click Connect.

  4. Enter your username and password.

    • The first time you connect to any particular Mac, you areprompted to enter your username and password for that machine:

      Tip

      When logging in, use your system username rather than full name.

    • Pair to Mac uses these credentials to create a new SSH connectionto the Mac. If it succeeds, a key is added to the authorized_keysfile on the Mac. Subsequent connections to the same Mac will loginautomatically.

  5. Pair to Mac automatically configures the Mac.

    Starting with Visual Studio 2019 version15.6,Visual Studio 2019 installs or updates Mono and Xamarin.iOS on aconnected Mac build host as needed (note that Xcode must still beinstalled manually). See Automatic Macprovisioning for more details.

  6. Look for the connection status icon.

    • When Visual Studio 2019 is connected to a Mac, that Mac's itemin the Pair to Mac dialog displays an icon indicating thatit is currently connected:

      There can be only one connected Mac at a time.

      Tip

      Right-clicking any Mac in the Pair to Mac list brings up a contextmenu that allows you to Connect..., Forget this Mac, orDisconnect:

      If you choose Forget this Mac, your credentials for the selectedMac will be forgotten. To reconnect to that Mac, you will need to re-enteryour username and password.

If you have successfully paired to a Mac build host, you are ready to buildXamarin.iOS apps in Visual Studio 2019. Take a look at theIntroduction to Xamarin.iOS for Visual Studioguide.

If you have not been able to pair a Mac, try manually adding aMac or take a look at the troubleshootingguide.

Manually add a Mac

If you do not see a particular Mac listed in the Pair to Mac dialog,add it manually:

  1. Locate your Mac’s IP address.

    • Open System Preferences > Sharing > Remote Login on your Mac:

    • Alternatively, use the command line. In Terminal, issue this command:

      Depending on your network configuration, you may need to use aninterface name other than en0. For example: en1, en2, etc.

  2. In Visual Studio 2019's Pair to Mac dialog, select Add Mac...:

  3. Enter the Mac's IP address and click Add:

  4. Enter your username and password for the Mac:

    Tip

    When logging in, use your system username rather than full name.

  5. Click Login to connect Visual Studio 2019 to the Mac over SSH and addit to the list of known machines.

Automatic Mac provisioning

Starting with Visual Studio 2019 version 15.6,Pair to Mac automatically provisions a Mac with software necessary forbuilding Xamarin.iOS applications: Mono, Xamarin.iOS (the softwareframework, not the Visual Studio for Mac IDE), and various Xcode-relatedtools (but not Xcode itself).

Important

  • Pair to Mac cannot install Xcode; you must manually install it on theMac build host. It is required for Xamarin.iOS development.
  • Automatic Mac provisioning requires that remote login isenabled on the Mac, and the Mac must be network-accessible to the Windowsmachine. See Enabling remote login on the Macfor more details.
  • Automatic Mac provisioning requires 3GB of free space on the Mac to install Xamarin.iOS.

Pair to Mac performs necessary software installations/updates when VisualStudio 2019 is connecting to theMac.

Mono

Pair to Mac will check to make sure that Mono is installed. If it is notinstalled, Pair to Mac will download and install the latest stable versionof Mono on the Mac.

Progress is indicated by various prompts, as shown by the followingscreenshots (click to zoom):

MonoInstall CheckDownloadingInstalling

Xamarin Mono Mac

Xamarin.iOS

Pair to Mac upgrades Xamarin.iOS on the Mac to match the versioninstalled on the Windows machine.

Important

Pair to Mac will not downgrade Xamarin.iOS on the Mac from alpha/betato stable. If you have Visual Studio for Mac installed, set yourrelease channel asfollows:

  • If you use Visual Studio 2019, select the Stable updates channel inVisual Studio for Mac.
  • If you use Visual Studio 2019 Preview, select the Alpha updateschannel in Visual Studio for Mac.

Progress is indicated by various prompts, as shown by the followingscreenshots (click to zoom):

Xamarin.iOSInstall CheckDownloadingInstalling

Xcode tools and license

Pair to Mac will also check to determine whether Xcode has been installedand its license accepted. While Pair to Mac does not install Xcode, itdoes prompt for license acceptance, as shown in the following screenshots(click to zoom):

XcodeInstall CheckLicense Acceptance

Additionally, Pair to Mac will install or update various packagesdistributed with Xcode. For example:

  • MobileDeviceDevelopment.pkg
  • XcodeExtensionSupport.pkg
  • MobileDevice.pkg
  • XcodeSystemResources.pkg

The installation of these packages happens quickly and without a prompt.

Note

These tools are distinct from the Xcode Command Line Tools, whichas of macOS 10.9 areinstalled with Xcode.

Troubleshooting automatic Mac provisioning

If you encounter any trouble using automatic Mac provisioning, take a lookat the Visual Studio 2019 IDE logs, stored in%LOCALAPPDATA%XamarinLogs16.0. These logs may contain error messagesto help you better diagnose the failure or get support.

Build iOS apps from the Windows command-line

Pair to Mac supports building Xamarin.iOS applications from the commandline. For example:

The parameters passed to msbuild in the above example are:

  • ServerAddress – The IP address of the Mac build host.
  • ServerUser – The username to use when logging in to the Mac build host.Use your system username rather than your full name.
  • ServerPassword – The password to use when logging in to the Mac build host.

Note

Visual Studio 2019 stores msbuild in the following directory:C:Program Files (x86)Microsoft Visual Studio2019<Version>MSBuildCurrentBin

The first time Pair to Mac logs in to a particular Mac build host fromeither Visual Studio 2019 or the command-line, it sets up SSH keys. With thesekeys, future logins will not require a username or password. Newlycreated keys are stored in %LOCALAPPDATA%XamarinMonoTouch.

If the ServerPassword parameter is omitted from a command-line buildinvocation, Pair to Mac attempts to log in to the Mac build hostusing the saved SSH keys.

Summary

This article described how to use Pair to Mac to connect Visual Studio 2019 to aMac build host, enabling Visual Studio 2019 developers to build native iOSapplications with Xamarin.iOS.

What Is Mono For Mac

Next steps