Resources
From Mono
| Table of contents |
|
2.1 Generating class status pages for your own assemblies |
Articles
Articles written about Mono or covering specific parts of Mono.
Papers used during the development of Mono.
Spanish Mono Book (http://tornatmico.org/libro/LibroMono) available as a Wiki.
API completion status pages
These are links to the pages that compare Mono assemblies to MS assemblies to keep track of API and class status and completion.
HEAD vs. Fx 1.1 (http://mono.ximian.com/class-status/1.1)
Compares SVN HEAD against .NET Framework 1.1.
HEAD vs. Fx 2.0 (http://mono.ximian.com/class-status/2.0)
Compares SVN HEAD against .NET Framework 2.0.
HEAD vs. MS VisualBasic (http://mono.ximian.com/class-status/mono-basic)
Compares SVN HEAD against .NET VisualBasic
HEAD vs. MS 3.0 (http://mono.ximian.com/class-status/olive)
Compares SVN HEAD against .NET 3.0 Bits
2.0 vs 2.0SP1 (http://mono.ximian.com/class-status/2.0-vs-3.5/index.html)
Compares the original 2.0 API with the updated version that shipped in 3.5 (2.0SP1).
Generating class status pages for your own assemblies
See Generating class status pages for instructions.
Generating class status pages for your hack on the System assemblies
After having private changes on your local repository, you might want to verify if the changes do not break the expected public API. You can use "corcompare tools" mentioned in the Generating class status pages page for this purpose too, but for Mono System.* assemblies you can do it quickly for either of of 1.1 and 2.0 profiles. The procedure is:
- Go to (svntopdir)/mono/web/web/masterinfos.
- Grab corresponding masterinfos from the links below and expand it in the above directory.
- Go to parent directory. (mono/web/web)
- run "make" for 1.1 profile, or "make PROFILE=net_2_0" for 2.0 profile.
- The output is at (svntopdir)/mono/web/web/deploy/
Note that the output pages are based on our classic website (from go-mono.com era).
MasterInfos
These are the files we compare to when generating our class status pages (we call them "masterinfos"):
- http://mono.ximian.com/masterinfos/masterinfos-1.1.tar.gz
- http://mono.ximian.com/masterinfos/masterinfos-2.0.tar.gz
- http://mono.ximian.com/masterinfos/masterinfos-3.0.tar.gz
- http://mono.ximian.com/masterinfos/masterinfos-3.5.tar.gz
Continuous Tasks
Build Bot
Track the status of the Mono repository (builds and regression tests) executed on multiple platforms on the Mono Build (http://mono.ximian.com/monobuild)
Benchmarks
We keep a page with details on performance testing.
Any tests that are added to the mono/tests directory will become a performance test which can be reviewed a day later at the regressions tests (http://nenya.ms.mff.cuni.cz/projects/mono/benchmarks/rtests.phtml) page.
Cuni Tests
Tomas Kalibera and his team keep a database of improvements done on a daily basis on the Mono runtime, it is available here:
http://nenya.ms.mff.cuni.cz/benchmark
Debian Language Shootout
Language Shootout (http://shootout.alioth.debian.org/debian/benchmark.php?test=all&lang=csharp&lang2=java) benchmarks tracks the performance of Mono vs other frameworks shipped in Debian.
The language shootout is usually a bit lagging regarding the latest version of Mono, but it is close enough.
Daily Regression Test Suite Results
Detailed reports of the regression test suite as well as graphics on progress are available Mono Test Suite Results (http://mono.ximian.com/tests)
New Build System
Browseable Source Code
The source code for Mono can be browsed in the anonymous SVN repository (http://svn.myrealbox.com/)
Third Party Patches
Distributions sometimes apply patches to Mono, you can see a list of distributions and their patches in our ThirdPartyPackages page.
Security Vulnerabilities
A list of known vulnerabilities affecting older versions of Mono is available.
Powered by MediaWiki