* Software Availability The Virtual Execution System is available in package `mono'. Currently this contains a metadata library and the disassembler. Please refer to our Runtime description for more details on this part of the project. The software is also available on the `Mono' channel in Red Carpet. Some useful links: Resources/Beginning section, the FAQ.
Release 0.28
Release notes
Oct 1st, 2003
Source Code
Source RPMs
(No RPMS for XSP).
Red Hat 9.0/x86 Red Hat 8.0/x86
Mandrake 9.1/x86
SuSE 8.2 Windows installer
Release 0.26
Release notes
Aug 14, 2003
Source Code
Source RPMs
(No RPMS for XSP).
Red Hat 9.0/x86 Red Hat 8.0/x86
Debian Mandrake 9.1/x86
SuSE 8.2 Windows installer
Release 0.25
Release notes
Jun 26, 2003
Source Code
Source RPMs
(No RPMS for XSP).
Red Hat 9.0/x86 Red Hat 8.0/x86
Debian Windows Setup Wizard (XP, 2000, NT)
Red Hat 7.3/x86 Mandrake 9.1/x86
Regression Tests
 You can get binaries for the Mono Regression Test Suite here
* Older Releases: We provide binaries for older releases until we have packages for the new release.
Release 0.24
Release notes
May 6, 2003
Source Code
Source RPMs
(No RPMS for XSP).
Red Hat 9.0/x86 Red Hat 8.0/x86
Debian Windows Setup Wizard (XP, 2000, NT)
Red Hat 7.3/x86 Mandrake 8.2/x86
SuSE 8.0/x86 Linux s/390
Regression Tests
 You can get binaries for the Mono Regression Test Suite here
Release 0.23
Release notes
March 5, 2003
Source Code
Source RPMs
(No RPMS for XSP).
Red Hat 7.3/x86 Red Hat 7.2/x86
Red Hat 7.1/x86 Mandrake 8.2/x86
SuSE 8.0/x86 Red Hat 8.0/x86
Windows Setup Wizard (NT/2000/XP) Linux S/390
Regression Tests
 You can get binaries for the Mono Regression Test Suite here
Release 0.22
Release notes
March 5, 2003
Source Code
Source RPMs
(No RPMS for XSP).
Windows Setup Wizard (NT/2000/XP)
Regression Tests
 You can get binaries for the Mono Regression Test Suite here
Release 0.21
Release notes
Feb 27th, 2003
Source Code
Source RPMs
(No RPMS for XSP).
Debian packages
Regression Tests
 You can get binaries for the Mono Regression Test Suite here
Release 0.20
Release notes
Feb 20th, 2003
Source Code
Source RPMs
(No RPMS for XSP).
Red Hat 8.0/x86 Debian packages
Windows Setup Wizard (NT/2000/XP)
Regression Tests
 You can get binaries for the Mono Regression Test Suite here
Release 0.19
Release notes
Jan 20th, 2003
Source Code
Source RPMs
(No RPMS for XSP).
Release 0.18
Release notes
Jan 12th, 2003
Source Code
Source RPMs
(No RPMS for XSP).
Release 0.17
Release notes
Dec 9th, 2002.
Source Code
Source RPMs
(No RPMS for XSP).
Windows Setup Wizard (NT/2000/XP) Debian packages
Release 0.16
Release notes
Oct 1st, 2002.
Source Code
Source RPMs
Linux s390
Release 0.15
Release notes
Aug 23rd, 2002.
Source Code
Source RPMs
Windows (win95 friendly) Red Hat null-8.0/x86
* Binaries for other platforms. Already daily volunteer's made binaries: * Snapshots Nightly snapshots of the CVS repository are made every day at 10pm EST (Boston Time). These are not guaranteed to build, they are just a snapshot of the tree. The anoncvs mirrors provided by Hispalinux are updated every six hours. * Compiling the code There are a number of ways of compiling Mono (which is an easy way to get the latest CVS information) * Compiling with scripts There are scripts to help build mono for both Unix and Windows. Get mono-build.sh for Unix, or mono-build-w32.sh for Windows. These scripts automate the installation of GLIB and pkgconfig (building from source on Unix, and using binary packages provided by the GIMP for Windows project on Windows.) To use the script, follow these simple steps: The script requires wget on either platform, and building the software requires make, gcc, automake, autoconf, and libtool. You should install these packages from your distribution or with the cygwin installer. You should also take care of setting the right environment variables as the PKG_CONFIG_FLAGS, etc. The script will download required packages from www.go-mono.com and do a cvs checkout of mono in the current directory. IMPORTANT!: The cvs server chosen defaults to anonymous cvs; set your CVSROOT environment variable before running the script to select a particular cvs server. ** Building the software manually You will need to obtain the Mono dependencies first: glib 2.x and pkg-config. *** Building on Linux *** On Windows, to install and work on the compiler and the class libraries: **** Install Cygwin and the GNU build tools, Microsoft's .NET Framework SDK and the precompiled GLIB 2.0 and pkg-config libraries. *** On Windows, to compile the mono runtime: * Software resources and notes The required and additional software can be downloaded here: * Microsoft's .NET Framework SDK from msdn.microsoft.com/downloads. * Cygwin and the GNU Make tools from www.cygwin.com. Some people observed problems with autoconf 2.52. Installing autoconf 2.13 helped in those cases. * Precompiled GLIB 2.0 and pkg-config packages (and their dependencies) by the GIMP for Windows project from http://www.go-mono.com/archive/pkgconfig-0.11-20020310.zip
http://www.go-mono.com/archive/glib-2.0.4-20020703.zip
http://www.go-mono.com/archive/glib-dev-2.0.4-20020703.zip
http://www.go-mono.com/archive/libiconv-1.7.zip
http://www.go-mono.com/archive/libiconv-dev-1.7-20020101.zip
http://www.go-mono.com/archive/libintl-0.10.40-20020101.zip
* Download the Mono source code from the packaged versions or the nightly snapshots or the Anonymous CVS. The nightly snapshots are done every night at 10pm EST (Boston Time). The nightly snapshots are not guaranteed to build, but most of the time they should. *** Notes on compiling GLIB 2.0 and pkg-config from source: ** Upgrading To upgrade your Mono installation from CVS, it is very important that you update your Mono and MCS modules from CVS at the same time. Failure to do so might result in a problematic installation as the runtime and the class libraries will be out of sync. Run the following commands to update your CVS tree (more details in Cvs and Mono and the AnonCVS and Mono pages). 
	(cd mono; cvs update -dP .)
	(cd mcs; cvs update -dP .)
Once you have updated your sources, remove any cached assemblies or old binaries from the Mono "runtime" directory, and then compile each component: 
	(cd mono/runtime; rm *exe *dll)
	(cd mono; make)
	(cd mcs; make)
Now you can install the result: 
	(cd mono; make install)
Notice that following the above procedure does not require you to manually install the software in the `mcs' directory, as the relevant files will be copied by the `mono' makefiles.