Gtk Doc Tools Centos Download For Mac
Download gtk-doc-tools packages for Debian, Ubuntu.
Mono for macOS is available as a Mac Package (.pkg)
Please refer to the installation guide for more information about how to install and configure your Mono environment.
Supported on macOS 10.9 and later. Check the uninstall instructions if you want to remove Mono from your Mac.
* We recommend this package if you're using Visual Studio for Mac since the stability of Visual Studio for Mac is only guaranteed with the Visual Studio channel releases.
- Ubuntu
- Debian
- Raspbian
- CentOS/RHEL
- Fedora
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, arm64, ppc64el)
Ubuntu 16.04 (i386, amd64, armhf, arm64, ppc64el)
2 Install Mono
The package mono-devel should be installed to compile code.
The package mono-complete should be installed to install everything - this should cover most cases of 'assembly not found' errors.
The package mono-dbg should be installed to get debugging symbols for framework libraries - allowing you to get line numbers in stack traces.
The package referenceassemblies-pcl should be installed for PCL compilation support - this will resolve most cases of 'Framework not installed: .NETPortable' errors during software compilation.
The package ca-certificates-mono should be installed to get SSL certificates for HTTPS connections. Install this package if you run into trouble making HTTPS connections.
The package mono-xsp4 should be installed for running ASP.NET applications.
3 Verify Installation
After the installation completed successfully, it's a good idea to run through the basic hello world examples on this page to verify Mono is working correctly.
Notes
Mono on Linux before 3.12 by default didn't trust any SSL certificates so you got errors when accessing HTTPS resources. This is not required anymore as 3.12 and later include a new tool that runs on package installation and syncs Mono's certificate store with the system certificate store (on older versions you had to import Mozilla's list of trusted certificates by running mozroots --import --sync). Some systems are configured in a way so that the necessary package isn't pulled in when Mono is installed, in those cases make sure the ca-certificates-mono package is installed.
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 Debian versions too but we only test the ones listed below.
Debian 10 (i386, amd64, armhf, arm64, armel, ppc64el)
Debian 9 (i386, amd64, armhf, arm64, armel, ppc64el)
2 Install Mono
The package mono-devel should be installed to compile code.
The package mono-complete should be installed to install everything - this should cover most cases of 'assembly not found' errors.
The package mono-dbg should be installed to get debugging symbols for framework libraries - allowing you to get line numbers in stack traces.
The package referenceassemblies-pcl should be installed for PCL compilation support - this will resolve most cases of 'Framework not installed: .NETPortable' errors during software compilation.
The package ca-certificates-mono should be installed to get SSL certificates for HTTPS connections. Install this package if you run into trouble making HTTPS connections.
The package mono-xsp4 should be installed for running ASP.NET applications.
3 Verify Installation
After the installation completed successfully, it's a good idea to run through the basic hello world examples on this page to verify Mono is working correctly.
Notes
Mono on Linux before 3.12 by default didn't trust any SSL certificates so you got errors when accessing HTTPS resources. This is not required anymore as 3.12 and later include a new tool that runs on package installation and syncs Mono's certificate store with the system certificate store (on older versions you had to import Mozilla's list of trusted certificates by running mozroots --import --sync). Some systems are configured in a way so that the necessary package isn't pulled in when Mono is installed, in those cases make sure the ca-certificates-mono package is installed.
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 Raspbian versions too but we only test the ones listed below.
Raspbian 10 (armhf)
Raspbian 9 (armhf)
2 Install Mono
The package mono-devel should be installed to compile code.
The package mono-complete should be installed to install everything - this should cover most cases of 'assembly not found' errors.
The package mono-dbg should be installed to get debugging symbols for framework libraries - allowing you to get line numbers in stack traces.
The package referenceassemblies-pcl should be installed for PCL compilation support - this will resolve most cases of 'Framework not installed: .NETPortable' errors during software compilation.
The package ca-certificates-mono should be installed to get SSL certificates for HTTPS connections. Install this package if you run into trouble making HTTPS connections.
The package mono-xsp4 should be installed for running ASP.NET applications.
3 Verify Installation
After the installation completed successfully, it's a good idea to run through the basic hello world examples on this page to verify Mono is working correctly.
Notes
0 ad for mac. Mono on Linux before 3.12 by default didn't trust any SSL certificates so you got errors when accessing HTTPS resources. This is not required anymore as 3.12 and later include a new tool that runs on package installation and syncs Mono's certificate store with the system certificate store (on older versions you had to import Mozilla's list of trusted certificates by running mozroots --import --sync). Some systems are configured in a way so that the necessary package isn't pulled in when Mono is installed, in those cases make sure the ca-certificates-mono package is installed.
1 Add the Mono repository to your system
The package repository hosts the packages you need, add it with the following commands in a root shell.
Note: the packages should work on newer CentOS/RHEL versions too but we only test the ones listed below.
CentOS/RHEL 8 (x86_64)
CentOS/RHEL 7 (x86_64)
CentOS/RHEL 6 (x86_64, i686)
2 Install Mono
The package mono-devel should be installed to compile code.
The package mono-complete should be installed to install everything - this should cover most cases of 'assembly not found' errors.
The package referenceassemblies-pcl should be installed for PCL compilation support - this will resolve most cases of 'Framework not installed: .NETPortable' errors during software compilation.
The package xsp should be installed for running ASP.NET applications.
3 Verify Installation
After the installation completed successfully, it's a good idea to run through the basic hello world examples on this page to verify Mono is working correctly.
1 Add the Mono repository to your system
The package repository hosts the packages you need, add it with the following commands in a root shell.
Note: we're using the CentOS/RHEL repositories on Fedora.
Fedora 29 (x86_64)
Fedora 28 (x86_64)
2 Install Mono
The package mono-devel should be installed to compile code.
The package mono-complete should be installed to install everything - this should cover most cases of 'assembly not found' errors.
The package referenceassemblies-pcl should be installed for PCL compilation support - this will resolve most cases of 'Framework not installed: .NETPortable' errors during software compilation.
The package xsp should be installed for running ASP.NET applications.
3 Verify Installation
After the installation completed successfully, it's a good idea to run through the basic hello world examples on this page to verify Mono is working correctly.
Mono for Windows is available as a Windows Installer file
Please refer to the installation guide for more information about how to install and configure your Mono environment.
Supported on Windows 7, 8, 10 or later.
GTK# for .NET
Installer for running Gtk#-based applications on Microsoft .NET:
Mono is available on Docker Hub
The simplest way to get started is:
This will download the latest Mono Docker image, create a container and put you into an interactive shell.
Available tags
There are several tags for selecting the desired Mono version:
latest- Always points to the latest releaseX.X.X.X- points to a specific version, e.g. 5.8.0.108X.X.X- points to the latest version in the X.X.X series, e.g. 5.8.0X.X- points to the latest version in the X.X series, e.g. 5.8X- points to the latest version in the X series, e.g. 5
The latest version, one minor version before that and the last version before a major version bump are periodically rebuilt by Docker Hub to pull in updates from the base Debian image.
All other version tags are still available, but won't get those updates so you need to keep your images up to date by running apt update yourself. We encourage you to move to latest Mono releases as soon as they're available.
Starting with Mono 5.2 we provide a slim variant (e.g. latest-slim) which only contains the bare minimum to run a simple console app. You can use this as a base and add just what you need.