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