Compare commits

..
3 Commits
Author SHA1 Message Date
nobody 1bce5f4a2a This commit was manufactured by cvs2svn to create tag 'MCS_0_19'.
svn path=/tags/MCS_0_19/mcs/; revision=10733
2003-01-20 14:34:04 +00:00
Martin Baulig 7f0542b133 Importing NUnit 1.11.
svn path=/branches/NUNIT/mcs/; revision=2713
2002-02-27 09:38:21 +00:00
nobody 9f187b5dd0 This commit was manufactured by cvs2svn to create branch 'NUNIT'.
svn path=/branches/NUNIT/mcs/; revision=2712
2002-02-27 09:38:18 +00:00
7219 changed files with 156274 additions and 925080 deletions

No files matched your search

-2
View File
@@ -15,5 +15,3 @@ Makefile.in
mono-*.tar.gz
stamp-h
stamp-h.in
mono.pc
mono.spec
-595
View File
@@ -1,598 +1,3 @@
Fri Jan 23 16:07:05 EST 2004 Paolo Molaro <[email protected]>
* configure.in, acconfig.h: check for truncl. Disable
version script on MacOSX (see bug #51590 if a check becomes
necessary).
Fri Jan 23 21:26:01 CET 2004 Paolo Molaro <[email protected]>
* configure.in, acconfig.h: added check for socklen_t.
2004-01-22 Zoltan Varga <[email protected]>
* Makefile.am: Do not install mono.pc on platforms without a JIT.
2004-01-21 Zoltan Varga <[email protected]>
* Makefile.am (remove-binaries): Get rid of non-portable >& construct.
2003-12-29 Miguel de Icaza <[email protected]>
* scripts/sn.in: Add sn script.
2004-01-15 Zoltan Varga <[email protected]>
* scripts/Makefile.am: Add al.exe.
* scripts/al.in: New file.
* runtime/Makefile.am: Add al.exe.
2004-01-10 Jackson Harper <[email protected]>
* data/machine.config: Add trace handler (Trace.axd) add trace
configuration handlers.
2004-01-06 Martin Willemoes Hansen <[email protected]>
* doc/books: Added books on Web Services and ASP.NET
2004-01-04 Daniel Morgan <[email protected]>
* monowiz.win32.nsi: update the NSIS installer script for windows
to support NSIS 2.0 rc1 and Mono 0.29
2003-12-22 Bernie Solomon <[email protected]>
* configure.in: missed in my last change
* samples/embed/testi.c: interpreter embedding example
* docs/embedded-api: add info on interpreter embedding
Mon Dec 22 18:27:14 CET 2003 Paolo Molaro <[email protected]>
* configure.in, acconfig.h: use mach semaphores on darwin.
2003-12-22 Bernie Solomon <[email protected]>
* Makefile.am: Create mint.pc
mint.pc.in: Added for embedding the interpreter
2003-12-16 Martin Baulig <[email protected]>
* Makefile.am: In a Makefile.am, comments are started with `#' and
not with `dnl' - I must have been an idiot ...
2003-12-10 Todd Berman <[email protected]>
* configure.in: adding libicu url to the ICU: no message.
2003-12-05 John Luke <[email protected]>
* data/config.in: new dll mapping entry for libgstreamer
2003-12-02 Atsushi Enomoto <[email protected]>
* README: tiny fix ;-)
2003-11-26 Zoltan Varga <[email protected]>
* configure.in: Add -fno-strict-aliasing to CFLAGS.
* configure.in: Applied patch from [email protected]. Avoid linking in
librt if not neccesary.
2003-11-24 Zoltan Varga <[email protected]>
* configure.in: Fix signbit check. Fixes #51315.
2003-11-20 Jackson Harper <[email protected]>
* data/machine.config: Add OutputCacheModule
2003-11-19 Jackson Harper <[email protected]>
* doc/web/team.xml: New email address and job description
* doc/web/team/jackson.png: Picture of me debugging...seems appropriate
2003-11-14 Jackson Harper <[email protected]>
* Makefile.am: delete mscorlib.dll
2003-11-12 Jackson Harper <[email protected]>
* Makefile.am: corlib is now named mscorlib.dll
2003-11-12 Zoltan Varga <[email protected]>
* configure.in acconfig.h: Add check for signbit, which is missing in
FreeBSD 4.x.
2003-11-07 Zoltan Varga <[email protected]>
* configure.in: Remove debugging junk accidently checked in.
* configure.in: Add new --with-nptl option to enable NPTL only
features since auto-detection is not reliable.
* autogen.sh: Fix previous patch and silence noisy GNU which.
2003-11-07 Bernie Solomon <[email protected]>
* autogen.sh: tweak glibtool check so it works
if which doesn't set return code properly
2003-11-07 Zoltan Varga <[email protected]>
* autogen.sh: Silence noisy GNU which.
* autogen.sh: Applied patch from Peter Teichman ([email protected]).
Use 'glibtool' instead of 'libtool' on OSX.
2003-11-06 Zoltan Varga <zovarga@ws-zovarga2>
* mono/benchmark/pinvoke.cs: New benchmark for testing the performance
of the managed/unmanaged boundary.
2003-11-06 Zoltan Varga <[email protected]>
* configure.in acconfig.h: Add check for __thread keyword in gcc.
2003-10-29 Dick Porter <[email protected]>
* man/mono.1: Document MONO_EXTERNAL_ENCODINGS variable
2003-10-16 Miguel de Icaza <[email protected]>
* man/mono.1: Document new --trace options
2003-10-13 Bernie Solomon <[email protected]>
* configure.in: add hppa support (64bit only)
make solaris build work with Forte compiler
2003-10-13 Zoltan Varga <[email protected]>
* configure.in: Added check for pthread_attr_setstacksize.
* mono/tests/ChangeLog: New file.
2003-10-13 Zoltan Varga <[email protected]>
* mono/tests/Makefile.am: Link the tests with the test driver program
used for the mini tests.
2003-10-10 Zoltan Varga <[email protected]>
* mono/tests/libtest.c (mono_test_marshal_delegate): Added test for
stdcall calling convention.
2003-10-09 Dick Porter <[email protected]>
* acconfig.h:
* configure.in: Check for ICU availability
2003-10-09 Bernie Solomon <[email protected]>
* mono/tests/libtest.c: fix after merge of pinvoke2.cs
2003-10-07 Bernie Solomon <[email protected]>
* mono/tests/Makefile.am mono/tests/libtest.c
mono/tests/pinvoke18.cs: new test for bool marshalling.
2003-10-07 Bernie Solomon <[email protected]>
* mono/scripts/Makefile.am mono/scripts/*.in: fix
managed .exe paths so they are found under cygwin.
2003-10-07 Zoltan Varga <[email protected]>
* mono/tests/pinvoke2.cs mono/tests/libtest.c: Fix array of structs
test.
2003-10-06 Bernie Solomon <[email protected]>
* mono/tests/pinvoke2.cs mono/tests/pinvoke11.cs
mono/tests/libtest.c: Add more pass by value struct
tests for platforms with more complex calling conventions
(Sparc V9, HPPA 64 bit).
2003-10-06 Zoltan Varga <[email protected]>
* mono/tests/pinvoke2.cs mono/tests/libtest.c: Add array of structs
marshalling test.
2003-10-04 Bernie Solomon <[email protected]>
* mono/tests/libtest.c: remove warnings except
"no previous prototype"
2003-10-03 Bernie Solomon <[email protected]>
* mono/tests/libtest.c: (test_lpwstr_marshal) remove undefined
behaviour of increment, (mono_test_marshal_char) = should be ==
2003-09-30 Zoltan Varga <[email protected]>
* mono/tests/remoting1.cs: Added test for interface casts on
TransparentProxies.
2003-09-24 Bernie Solomon <[email protected]>
* mono/tests/pinvoke*.cs, delegate4.cs, marshal10.cs, marshal4.cs
marshal5.cs: remove .so from DllImport of libtest to aid portability.
2003-09-08 Zoltan Varga <[email protected]>
* configure.in: Added check for valgrind headers.
2003-09-03 Zoltan Varga <[email protected]>
* Makefile.am: Use $(MAKE) in even more places. Patch by Bernie Solomon
([email protected]).
2003-08-27 Zoltan Varga <[email protected]>
* Makefile.am: Use $(MAKE) instead of make. Patch by Bernie Solomon
([email protected]).
2003-08-25 Zoltan Varga <[email protected]>
* mono.pc.in: Added gthread-2.0.
2003-08-22 Zoltan Varga <[email protected]>
* configure.in: Added gthread-2.0 to GLIB_CFLAGS and GLIB_LIBS, so we
can call g_thread_init ().
2003-08-21 Zoltan Varga <[email protected]>
* mono/tests/threadpool.cs mono/tests/threadpool1.cs: Make increments
of static variables atomic. Fixes bug #47683.
2003-08-21 Johannes Roith <[email protected]>
* mono/Makefile.am: small update. make sure, glib makes it in the build, add optional target for dependencies
2003-08-18 Johannes Roith <[email protected]>
* mono/Makefile.am: add windows build option
* mono/monowiz.win32.nsi: add windows build script
* mono/mono-win32-light.bmp: add bitmap
2003-08-16 Zoltan Varga <[email protected]>
* mono/tests/checked.cs: Added mul.ovf tests.
2003-08-15 Duncan Mak <[email protected]>
* doc/mysql: Change references to ByteFX.Data.MySQLClient to the
correct ByteFX.Data.MySqlClient (note the change in
capitalization). Thanks to Tom Wagner <[email protected]> for
spotting the error.
2003-08-15 Zoltan Varga <[email protected]>
* mono/tests/bug-47295.cs: Regression test for bug #47295.
2003-08-11 Duncan Mak <[email protected]>
* runtime/Makefile.am (assemblies_DATA): Add Mono.Cairo.dll.
Sun Aug 3 21:12:13 BST 2003 Malte Hildingson <[email protected]>
* configure.in: added FPU test for ARM.
Thu Jul 31 16:19:07 CEST 2003 Paolo Molaro <[email protected]>
* configure.in, etc.: portability fixes and support for
buidling outside the srcdir from Laurent Morichetti <[email protected]>.
2003-07-22 Duncan Mak <[email protected]>
* runtime/Makefile.am: Remove sqlsharp as we no longer distribute it.
2003-07-22 Zoltan Varga <[email protected]>
* mono/tests/Makefile.am: Add missing test. Make tests interruptable
by Ctrl-C. Add testinterp target to run the tests with the interpreter.
Do not try to build vararg.cs under mcs.
* configure.in: Fix detection of GC_gcj_malloc.
2003-07-14 Jerome Laban <[email protected]>
* acconfig.h:
* configure.in: Check for gethostbyname2_r availability.
* data/machine.config: Added section system.net/settings. Added
option for IPv6 availability.
2003-07-13 Zoltan Varga <[email protected]>
* mono/tests/cattr-object.cs: Make it run under both mono and MS.NET.
* mono/tests/struct.cs: Add test for unboxing trampolines.
* mono/tests/bug-27420.cs: new regression test.
* mono/tests/Makefile.am: skip vararg test since it does not compile
under mono. Add testinterp target. Add new tests.
2003-07-10 Martin Willemoes Hansen
* doc/web/team.xml : Modified my tasks a bit.
2003-07-01 Paolo Molaro <[email protected]>
* acconfig.h, configure.in: added bundle support.
2003-06-10 Dick Porter <[email protected]>
* acconfig.h:
* configure.in: Check for struct ip_mreq if struct ip_mreqn isn't
available.
2003-06-10 Zoltan Varga <[email protected]>
* configure.in: Define HAVE_GC_GCJ_MALLOC for included libgc.
2003-06-10 Martin Baulig <[email protected]>
* configure.in: Fall back to boehm if we don't have a libgc
subdirectory.
2003-06-10 Martin Baulig <[email protected]>
* configure.in: Make the libgc stuff actually work; we now create
a shared libmonogc.so when using the included libgc.
2003-06-09 Martin Baulig <[email protected]>
* configure.in: Only check for gc if --with-gc=boehm.
2003-06-08 Martin Baulig <[email protected]>
* configure.in: Tell libgc's configure about our threads library.
2003-06-08 Martin Baulig <[email protected]>
* libgc/: Integrate the libgc module here.
[Note: A simple `cvs update' won't work this time; you either need
to re-checkout the `mono' module or manually move the `libgc'
module here.]
* configure.in (--with-gc): Added `included' option to use the
included libgc. This is now also the default.
(LIBGC_CFLAGS, LIBGC_LIBS): Put the libgc stuff here and AC_SUBST it.
(INCLUDED_LIBGC): New automake conditional.
(USE_INCLUDED_LIBGC): #define this if appropriate.
* autogen.sh: Run libgc/autogen.sh.
* Makefile.am (SUBDIRS): Added libgc.
2003-06-05 Duncan Mak <[email protected]>
* mono.spec.in (Requires): Add libxml2 and libxslt dependency on
the package.
2003-05-19 Dick Porter <[email protected]>
* configure.in: Netbsd build fix by [email protected].
2003-05-10 Martin Willemoes Hansen <[email protected]>
* scripts/Makefile.am: Added monoresgen secutil sqlsharp
shell wrapper scripts.
2003-05-08 Zoltan Varga <[email protected]>
* mono/tests/Makefile.am:
- Compile with mcs.
- Disable some warnings.
- Added executables to clean target.
- Make testjit the default target.
- Print list of failed tests at the end of a test run.
- Abort tests when Ctrl-C is pressed.
* mono/tests/test-driver: Return with a special exit code when
SIGINT is detected.
* mono/tests/checked.cs: Make it compile.
2003-05-02 Miguel de Icaza <[email protected]>
* runtime/Makefile.am ($(monobins_DATA)): Use explicit file names
for the target exe binaries.
Copy cilc.exe and secutil.exe from the right paths to the right
location.
Add missing assemblies.
2003-05-02 Alp Toker <[email protected]>
* data/config.in: new dll mapping entry for libglade
2003-05-01 Duncan Mak <[email protected]>
* scripts/Makefile.am:
* runtime/Makefile.am: Install cilc and ilasm.
2003-04-29 Dietmar Maurer <[email protected]>
* mono/tests/Makefile.am (JITTEST_PROG): use mini/mono
2003-04-16 Charles Iliya Krempeaux <[email protected]>
* doc/web/team.xml : Added myself to it.
2003-04-10 Duncan Mak <[email protected]>
* doc/web/render-team-page.cs: Make the names of the element be
lowercase instead. BenM says this makes it XHTML compliant; heck,
I'm generating this from an XmlDocument already, why not make it
XHTML compliant?
2003-04-10 Duncan Mak <[email protected]>
* doc/web/render-team-page.cs (Compare): Correctly fix
ContributorComparer.
(RenderHtml): Add some SetAttribute loving to make it render prettier.
* doc/web/team.xml: Revert excessive indenting.
2003-04-07 Martin Baulig <[email protected]>
* mono/mini/: Added this directory to the build; install `mini'
and `libmini.la'.
2003-04-07 Duncan Mak <[email protected]>
* doc/web/render-team-page.cs: Fix ContributorComparer.
2003-04-04 Duncan Mak <[email protected]>
* doc/web/render-team-page.cs: Make it use 'none.png' if no image
are specified in the XML.
* doc/web/team.xml: Remove the comment.
* doc/web/render-team-page.cs: Make it not output a full HTML file.
2003-04-04 Duncan Mak <[email protected]>
* doc/web/commands:
* doc/web/makefile: Add team page information.
* doc/web/team.xml:
* doc/web/render-team-page.cs: Code for rendering a team page.
2003-04-02 Duncan Mak <[email protected]>
* doc/web/makefile: Add a new make target for generating a team
page on go-mono.com.
2003-04-04 Zoltan Varga <[email protected]>
* configure.in: Added check for GC_gcj_malloc.
2003-04-04 Martin Willemoes Hansen <[email protected]>
* man/sqlsharp.1: changed pass= to password= for the
PostgreSql provider.
>>>>>>> 1.166
2003-03-31 Gonzalo Paniagua Javier <[email protected]>
* data/machine.config: added SessionStateModule to httpModules section.
2003-02-13 Gonzalo Paniagua Javier <[email protected]>
* data/machine.config: added default sessionState section and handler.
2003-02-17 Daniel Morgan <[email protected]>
* doc/provider-factory: add new web page
about Mono.Data's ProviderFactory
* doc/web/commands
* doc/web/makefile: add provider-factory web page to build
* doc/ado-net
* doc/ibmdb2
* doc/postgresql
* doc/sqlclient
* doc/tdsclient
* doc/sybase
* doc/mysql
* doc/firebird
* doc/oracle
* doc/oledb
* doc/odbc
* doc/sqlite: updated web pages
2003-02-16 Martin Baulig <[email protected]>
* doc/jit-debug-sample
* doc/jit-debug-sample2: Removed.
* doc/jit-debug: Updated.
2003-02-13 Daniel Morgan <[email protected]>
* doc/screenshots
* doc/ado-net
* doc/oracle
* doc/gtk-sharp: update web pages
2003-02-13 Gonzalo Paniagua Javier <[email protected]>
* data/machine.config: added sample globalization section.
2003-02-12 Gonzalo Paniagua Javier <[email protected]>
* data/machine.config: added UrlAuthorizationModule and
AuthenticationConfigHandler.
2003-02-11 Tim Coleman <[email protected]>
* data/config.in: Add mapping for Oracle call interface
(OCI) native libraries.
2003-02-04 Gonzalo Paniagua Javier <[email protected]>
* configure.in: added check for sys/un.h.
2003-01-29 Daniel Morgan <[email protected]>
* doc/postgresql
* doc/mysql
* doc/ado-net: updates to web pages
* man/sqlsharp.1: update to man page
2003-01-28 Gonzalo Paniagua Javier <[email protected]>
* configure.in: added WIN32_THREADS flag when building under windows.
It seems that the header files of the gc do not always define it when
GC_WIN32_THREADS is defined.
2003-01-26 Daniel Morgan <[email protected]>
* doc/index
* doc/ado-net
* doc/firebird
* doc/ibmdb2
* doc/mysql
* doc/odbc
* doc/oledb
* doc/oracle
* doc/postgresql
* doc/sqlclient
* doc/sqlite
* doc/sybase
* doc/tdsclient: corrections
2003-01-26 Duncan Mak <[email protected]>
* doc/jit-debug: Update the links. Thanks for Andy Oliver for the report.
2003-01-22 Martin Baulig <[email protected]>
* configure.in: Set version number to 0.19.1.
Heads up: I'm going to commit some changes to the debugger
which'll require you to use this new runtime, so if you update the
debugger from CVS, you also need this new runtime.
2003-01-20 Duncan Mak <[email protected]>
* configure.in: Bump the release number to 0.19.
2003-01-19 Daniel Morgan <[email protected]>
* doc/ibmdb2: added file which is new web page
+4 -62
View File
@@ -1,67 +1,9 @@
AUTOMAKE_OPTIONS = foreign
SUBDIRS = @libgc_dir@ mono doc docs runtime scripts man data samples
SUBDIRS = mono doc docs runtime scripts man data
# EXTRA_SUBDIRS = libgc
EXTRA_DIST= mono.pc.in mono.spec.in mint.pc.in
EXTRA_DIST= mono.pc.in mono.spec.in
pkgconfigdir = $(libdir)/pkgconfig
if JIT_SUPPORTED
pkgconfig_DATA= mono.pc mint.pc
else
pkgconfig_DATA= mint.pc
endif
DISTCLEANFILES= mono.pc mint.pc
#
# The following target is used to compile and install
# mono and mcs without running into the out-of-sync
# problems by doing the compilation in the right order.
#
fullbuild: remove-binaries mcs-tree-safe-build xinstall-runtime mcs-rest install
mcs-tree-safe-build:
(cd ../mcs/jay; $(MAKE))
(cd ../mcs/mcs; $(MAKE) MCS=mcs BOOTSTRAP_MCS=mcs)
(cd ../mcs/class/corlib; $(MAKE) MCS=mcs BOOTSTRAP_MCS=mcs)
cp ../mcs/class/lib/mscorlib.dll runtime
cp ../mcs/mcs/mcs.exe runtime
xinstall-runtime:
if echo $(SUBDIRS) | grep "libgc " > /dev/null; then (cd libgc; $(MAKE) && $(MAKE) install); fi
(cd mono; $(MAKE) && $(MAKE) install)
(cd runtime; $(MAKE) install assemblies_DATA=mscorlib.dll monobins_DATA=mcs.exe)
mcs-rest:
(cd ../mcs/class; $(MAKE))
remove-binaries:
rm ../mcs/class/lib/mscorlib.dll ../mcs/mcs/mcs.exe runtime/*dll runtime/*.exe > /dev/null 2>&1; echo
win32getdeps:
wget http://www.go-mono.com/archive/pkgconfig-0.11-20020310.zip
wget http://www.go-mono.com/archive/glib-2.0.4-20020703.zip
wget http://www.go-mono.com/archive/glib-dev-2.0.4-20020703.zip
wget http://www.go-mono.com/archive/libiconv-1.7.zip
wget http://www.go-mono.com/archive/libiconv-dev-1.7.zip
wget http://www.go-mono.com/archive/libintl-0.10.40-20020101.zip
wget http://www.jroith.de/nsis4cygwin.zip
unzip -n -d / pkgconfig-0.11-20020310.zip
unzip -n -d / glib-2.0.4-20020703.zip
unzip -n -d / glib-dev-2.0.4-20020703.zip
unzip -n -d / libiconv-1.7.zip
unzip -n -d / libiconv-dev-1.7.zip
unzip -n -d / libintl-0.10.40-20020101.zip
unzip -n -d / nsis4cygwin.zip
win32setup:
cp /usr/lib/libglib-2.0-0.dll @prefix@/lib
cp /usr/lib/iconv.dll @prefix@/lib
cp /usr/lib/libgmodule-2.0-0.dll @prefix@/lib
cp /usr/lib/libgobject-2.0-0.dll @prefix@/lib
cp /usr/lib/libgthread-2.0-0.dll @prefix@/lib
cp /usr/lib/libintl-1.dll @prefix@/lib
makensis /DMILESTONE=@VERSION@ /DSOURCE_INSTALL_DIR=`cygpath -a -w @prefix@`\\* monowiz.win32.nsi
pkgconfig_DATA= mono.pc
DISTCLEANFILES= mono.pc
-511
View File
@@ -1,514 +1,3 @@
Hello everyone!
We are releasing a new version of Mono, Mono 0.22. A new release
is made today because of the few recent bug-fixes that were committed
to CVS.
Source code and binaries for this release can be found on the
web page,
http://www.go-mono.com/download.html
The URLs for the sources are:
* MCS package (the Class Libraries, C# and VB.NET compiler
and other assorted tools written in Managed code):
http://www.go-mono.com/archive/mcs-0.22.tar.gz
* Mono package (the Runtime engine and JIT compiler):
http://www.go-mono.com/archive/mono-0.22.tar.gz
RPM packages for this release can be downloaded from the web-page
as well as from the 'Mono' channel on Red Carpet. Debian packages will
appear on the download page later, as well as an installer for our
Windows users.
Since last Thursday, 320 commits have been made to our CVS
repository. These following hackers contributed to Mono since version
0.21:
Aleksey Demakov, Alexandre Pigolkine, Atsushi Enomoto, Elan
Feingeld, Dick Porter, Dietmar Maurer, Duncan Mak, Gonzalo
Paniagua, Ian MacLean, Jackson Harper, Jean-Marc Andre, Jerome
Laban, Lluis Sanchez, Martin Baulig, Miguel de Icaza, Nick
Drochak, Paolo Molaro, Pedro Martinez, Per Ameng, Peter Williams,
Rafael Teixeira, Reggie Burnett, Sebastien Pouliot, Tim Coleman
and Zoltan Varga.
Highlights:
* The "MemoryStream" bug.
This bug affected a lot of classes, and made them crashy,
database code, XML parsing and a few others were
crashing. Thanks to Gonzalo for fixing this bug.
* System.Data:
More bug fixes from Aleksey and Tim.
* Reflection:
Zoltan continues to provide fixes to our Reflection.Emit code
to host IKVM.
* Remoting:
Lluis added support for activation using activation
attributes.
* PEToolkit:
Jackson imported the PEAPI package from the Queensland
University of Technology in Australia. This will replace the
existing Mono.PEToolkit for our ILasm back-end.
* Windows Forms:
More fixes from Reggie and Alexandre.
* System.Web.Mail:
Per has been working on this namespace. He announces recently
that all major parts of System.Web.Mail has now been implemented.
* System.Web.Mobile:
Gaurav continues to make progress here.
* Misc:
Ian MacLean contributed a /compile flag to monoresgen and
assorted bug-fixes and improvements from the rest of the team.
My name is Duncan Mak, and I just made my first Mono release.
-----------------------------------------------------------------------------
Hello everyone!
The Mono Team introduces the best Mono release so far we have
done. Thanks to everyone who contributed fixes, code, ideas, and bug
reports.
Mono 0.20 has been released, it is available at the usual location:
http://www.go-mono.com/download.html
This is a truly heroic release of Mono. Major architectural
chunks that were missing, or were miss-implemented have been fixed in
this release, and we are very proud of it. Please see the list of
features, because there is no short way of introducing just how good
this release is. A big thanks goes to Piers for setting up a
Tinderbox that monitors problems with the Mono CVS repository.
We released packages for SuSE 8.0, Mandrake 8.2, and various
Red Hat releases. It is also available from Red Carpet on the Mono
channel.
Source code for Mono, MCS, the Mono Debugger, XSP is available as
well from that web page. The sources are:
MCS package (Class Libraries, C# and VB.NET compiler and managed tools):
http://www.go-mono.com/archive/mcs-0.20.tar.gz
Mono package (Runtime engine, JIT compiler):
http://www.go-mono.com/archive/mono-0.20.tar.gz
XSP package (XSP test web server for ASP.NET webforms):
http://www.go-mono.com/archive/xsp-0.3.tar.gz
This release is brought to you by: Alvaro del Castillo, Alan Tam,
Alp Toker, Alejandro Sánchez, Alexandre Pigolkin, Atsushi Enomoto,
Brian Ritchie, Christopher Bockner, Daniel Lopez, Daniel Morgan,
Dennis Hayes, Dick Porter, Dietmar Maurer, Duncan Mak, Gaurav Vaish,
Gonzalo Paniagua, Jackson Harper, Jaime Anguiano, Jeff Stedfast,
Johannes Roith, John Sohn, Jonathan Pryor, "Lee Mallabone, "Lluis
Sanchez, "Marco Ridoni, Mark Crichton, Martin Baulig, Martin Willemoes
Hansen, Miguel de Icaza, Mike Kestner, Nick Drochak, Paolo Molaro,
Patrik Torstensson, Pedro Martinez, Per Arneng, Peter Williams, Petr
Danecek, Piers Haken, Radek Doulik, Rafael Teixeira, Rodrigo Moya,
Sebastien Pouliot, Tim Coleman, Ville Palo, and Zoltan Varga.
They commited 1810 changes to CVS patches in the past 33 days.
* New in this release
* Zoltan and IKVM
Zoltan's patches to run Jeroen's IKVM (the Java VM that
translates JVM bytecodes into .NET bytecodes) are in.
* Remoting.
The remoting team's patches that were held off on the previous
release are here. Lluis and Patrik have done a fantastic job
in getting remoting to work. Many low-level runtime engine
changes, and plenty of work on the class-library stuff.
Lluis has posted a couple of sample applications to the
mailing list, you can try those out.
The new release includes a working BinaryFormatter and
BinaryFormatterSink. It means that together with TcpChannel
it is possible to make remote calls with any type of
parameters and return values, including value types,
MarshalByRefObject types (that are properly
marshalled/unmarshalled), delegates, enums, etc.
RemotingConfiguration is partially implemented. It cannot read
from config files, but manual configuration using the api is
fully working.
Implemented full support for client activated types and for
well known objects (both singleton and single call).
Lease manager fully working (it manages the lifetime of server
objects).
Implemented interception of the new operator, so it is
possible to create a remote object using "new", if the type is
properly registered in RemotingConfiguration.
In Lluis' words: `Basically, 0.20 will have almost all needed
for a distributed application with Remoting'
* New threading semantics, IO-layer
Dick Porter in a couple of weeks has heroically redone much of
the threading support to match the .NET behavior (details are
on the .NET threading book as posted on the Mono site).
He also did a lot of bug fixes in the IO/threading space. The
threading implementation now contains a new and faster Monitor
implementation, as well as a correct Pulse()/Wait()
implementation.
GC thread finalization has been re-enabled. This means that
finalizers will be ran on a separate thread, as done in the
Microsoft.NET Framework. This might expose some bugs on
existing finalizer code.
* Moved to NUnit2
Nick and Gonzalo helped us move to the new NUnit2 platform for
all of our tests. A big applause goes to them.
* Cross Appdomain invocations work now.
ASP.NET and NUnit2 both used cross appdomain invocations, we
have fixed a number of problems, and they are now functional.
The AppDomain fixes and the Remoting fixes have allowed us to
remove a number of hacks in the ASP.NET implementation that
were previously there.
Implemented CrossAppDomainChannel, for calls between domains.
* C# Compiler and Debugging.
When generating debugging information in the compiler (with
-debug, -g or -debug+) the compiler will embed the debugging
information into the resulting executable instead of
generating a separate file. Very nice.
Generating debugging information has also improved vastly
performance-wise, and now it is possible to always use
debugging builds for software development.
A number of bugs were fixed on the compiler as well and
by using the Mono profiler we have reduced the memory
consumption and accelerated the compiler.
Thanks to Jackson, Martin, Paolo and for helping here.
* VB.NET Compiler.
Plenty of new features are included in the compiler in our
path to conformance. See <FIXME:get-url-for-posting> for
details on the status of the compiler, and the pieces missing.
* ILasm and Mono.PEToolkit.
Work on the IL assembler has resumed, but it is not yet ready
for production use. The Mono IL Assembler uses the
Mono.PEToolkit library done by Sergey and Jackson to
manipulate CIL image files.
* Cryptographic work.
Sebastien has provided a cert2spc and secutil tools for
certificate management. This is the first release that ships
an assembly for System.Security
Also a new internal assembly used only on Windows allows Mono
users to use the unmanaged crypto providers.
* System.XML
Atsushi has continued to improve the work on our XML
implementation: fixing bugs and more closely matching the
Microsoft implementation.
* More PowerPC/Alpha support.
Taylor Christopher has contributed more code generation macros
for PPC and Laramie Leavitt for Alpha.
* System.XML.Xsl
Gonzalo continued the implementation of our XSLT transformation
API (custom .NET functions are still missing though). It no
longer uses temporary files to apply transformations. Thanks
to an idea from Zdravko Tashev. Xslt Web controls work as
part of this fix.
* ASP.NET
Gonzalo has cleaned up a lot the code base, and now our test
server supports a --root and --virtual command line options
for better control.
Also, now we generate a much nicer error page on errors. We
are looking for volunteers to improve the default look of this
page.
Authentication is now supported
* Mobile Controls.
Gaurav Vaish continues on his quest to complete the
implementation of the Mobile controls. These controls are
required to run a stock IBuySpy application.
* Class Libraries:
New Mono.Posix class library that contains classes for working
on a Posix systems. Things like Unix domain sockets are here.
* System.Windows.Forms
Alexandre Pigolkine continues to contribute more code to our
Windows.Forms implementation. Currently it only runs on
Windows (or in Linux without GC enabled, due to the
pthread/Wine threading library mismatch. This is being
actively addressed as part of the Wine work due to the
movement to the new thread implementation available in RH 8.1).
* Database providers
Christopher Bockner has updated his DB2 database provider (now
with prepared statement functionality) and Tim Coleman has
continued work on the Oracle database provider (welcome back
Tim!)
* Database code.
Dan Morgan continues to develop core components in System.Data
(and now we welcome Alan Tam to the System.Data core hackers)
The SQL# tool now supports MySQLNet, Npgsql, DB2Client, and
Oracle clients.
* Runtime
mono --profile now performs memory allocation profiling too.
* Runtime fixes.
We now support multi-module with external file reference
assemblies.
The above in English means that we can now run Eiffel.NET code
in Mono.
* Monograph:
More statistics supported now.
* System.Web.Mail
Per has contributed the code for this namespace.
* Bugs
Plenty of bugs were closed.
-------------------------------------------------------------------------
Hello everyone!
We have made a new release of Mono available. Despite the fact
that we just did Mono 0.18, this release is packed with new features.
* Availability.
Mono 0.19 is available in package format from:
http://www.go-mono.com/download.html
We released packages for SuSE 8.0, Mandrake 8.2, Debian and various
Red Hat releases. It is also available from Red Carpet on the Mono
channel.
Source code for Mono, MCS, the Mono Debugger, XSP is available as
well from that web page.
* New in this release
* Remoting news:
Lluis has implemented and documented the Binary formatter
Woohoo! He has done a lot of work as well to support
remoting.
Patrik has also been working heavily on fixing a
number of remoting related bugs and missing features.
Ajay also implemented 1-d array serialization in System.Xml
* New database provider: IBM DB2
Christopher Bockner has contributed a DB2 data
provider for System.Data. We have a very complete
range of data providers.
* System.Web.Mobile
Gaurav has started work on this assembly, this will
allow us to run the unmodified reference ASP.NET
applications that were designed to support Mobile
browsing.
* System.Data and System.XML:
More implementation work on XmlDataDocument from Ville
and plenty of fixes from Atsushi.
* MacOS patches:
Paolo integrated John Duncan's and Benjamin Reed
patches to make Mono run on MacOS X out of the box.
* IsolatedStorage
The initial implementation of it was done by Jonathan
Pryor and included in this release.
* Compilers:
More work on the Mono Visual Basic compiler (it is now
included in the packages).
Plenty of bug fixes from Jackson, Miguel to the C#
compiler.
Patches from Francesco and Daniel to the VB.NET
support runtime.
* Debugger support
Plenty of updates to run the new Mono Debugger from Martin.
* Main missing bits:
Some of everyone's favorite patches or code chunks have not yet
been integrated, hopefully Mono 0.20 will have them:
* Zoltan's patch to run IKVM is not yet on this release
* Some parts of Patrik's remoting code did not make it to the
release either.
* Reggie's MySQL native provider is also missing.
Enjoy!
Miguel.
-------------------------------------------------------------------------
Hello everyone!
We have made a new release of Mono available. Despite the fact
that we just did Mono 0.18, this release is packed with new features.
* Availability.
Mono 0.19 is available in package format from:
http://www.go-mono.com/download.html
We released packages for SuSE 8.0, Mandrake 8.2, Debian and various
Red Hat releases. It is also available from Red Carpet on the Mono
channel.
Source code for Mono, MCS, the Mono Debugger, XSP is available as
well from that web page.
* New in this release
* Remoting news:
Lluis has implemented and documented the Binary formatter
Woohoo! He has done a lot of work as well to support
remoting.
Patrik has also been working heavily on fixing a
number of remoting related bugs and missing features.
Ajay also implemented 1-d array serialization in System.Xml
* New database provider: IBM DB2
Christopher Bockner has contributed a DB2 data
provider for System.Data. We have a very complete
range of data providers.
* System.Web.Mobile
Gaurav has started work on this assembly, this will
allow us to run the unmodified reference ASP.NET
applications that were designed to support Mobile
browsing.
* System.Data and System.XML:
More implementation work on XmlDataDocument from Ville
and plenty of fixes from Atsushi.
* MacOS patches:
Paolo integrated John Duncan's and Benjamin Reed
patches to make Mono run on MacOS X out of the box.
* IsolatedStorage
The initial implementation of it was done by Jonathan
Pryor and included in this release.
* Compilers:
More work on the Mono Visual Basic compiler (it is now
included in the packages).
Plenty of bug fixes from Jackson, Miguel to the C#
compiler.
Patches from Francesco and Daniel to the VB.NET
support runtime.
* Debugger support
Plenty of updates to run the new Mono Debugger from Martin.
* Main missing bits:
Some of everyone's favorite patches or code chunks have not yet
been integrated, hopefully Mono 0.20 will have them:
* Zoltan's patch to run IKVM is not yet on this release
* Some parts of Patrik's remoting code did not make it to the
release either.
* Reggie's MySQL native provider is also missing.
Enjoy!
Miguel.
------------------------------------------------------------------------------
Happy new year!
The Mono team is proud to release Mono 0.18, with plenty of bug
+7 -111
View File
@@ -1,98 +1,14 @@
This is Mono.
1. Installation
2. Using Mono
3. Directory Roadmap
Installation:
1. Compilation and Installation
===============================
Read doc/download for installation instructions,
or read the HTML version:
a. Build Requirements
---------------------
http://www.go-mono.com/download.html
To build Mono, you will need the following components:
* pkg-config
Available from: http://www.freedesktop.org/Software/pkgconfig
* glib 2.0
Available from: http://www.gtk.org/
Optional dependencies:
* ICU library
http://oss.software.ibm.com/icu/index.html
You will need this one to get complete support for the international
features of the .NET Framework.
* Cairo and libgdiplus
If you want to get support for System.Drawing, you will need to get
both Libgdiplus and Cairo.
b. Building the Software
------------------------
If you obtained this package as an officially released tarball,
this is very simple, use configure and make:
./configure --prefix=/usr/local
make
make install
If you obtained this as a snapshot, you will need an existing
Mono installation. To upgrade your installation, unpack both
mono and mcs:
tar xzf mcs-XXXX.tar.gz
tar xzf mono-XXXX.tar.gz
cd mono-XXXX
./autogen.sh --prefix=/usr/local
make fullbuild
c. Upgrade from CVS
-------------------
If you are upgrading from CVS you will need an existing Mono installation.
First verify that you have a working installation:
echo 'class X { static void Main () { System.Console.Write("OK");}'}' > x.cs
Compile:
mcs x.cs
And run:
mono x.exe
If you get the output `OK' and no errors, you are ready to start your CVS upgrade.
First, make sure that you have up-to-date mcs and mono sources:
cvs co mono mcs
Then, go into the mono directory, and configure:
cd mono
./autogen --prefix=/usr/local
Then compile using the special target `fullbuild':
make fullbuild
This step will compile and install at the same time.
Failure to follow these steps will result in a broken installation.
2. Using Mono
=============
* Using Mono
Once you have installed the software, you can run a few programs:
@@ -113,17 +29,10 @@ This is Mono.
See the man pages for mono(1), mint(1), monodis(1) and mcs(2)
for further details.
3. Directory Roadmap
====================
* A directory roadmap:
doc/
Contains the web site contents.
docs/
Technical documents about the Mono runtime.
data/
Configuration files installed as part of the Mono runtime.
Contains documentation and the web site contents.
mono/
The core of the Mono Runtime.
@@ -154,17 +63,4 @@ This is Mono.
arch/
Architecture specific portions.
man/
Manual pages for the various Mono commands and programs.
scripts/
Scripts used to invoke Mono and the corresponding program.
runtime/
A directory holding a pre-compiled version of the Mono
runtime.
-14
View File
@@ -3,10 +3,8 @@
#undef HAVE_MSG_NOSIGNAL
#undef HAVE_SOL_IP
#undef HAVE_SOL_TCP
#undef HAVE_SOL_IPV6
#undef HAVE_IP_PKTINFO
#undef HAVE_STRUCT_IP_MREQN
#undef HAVE_STRUCT_IP_MREQ
#undef HAVE_PTHREAD_MUTEX_TIMEDLOCK
#undef USE_MONO_MUTEX
#undef HAVE_LARGE_FILE_SUPPORT
@@ -15,21 +13,9 @@
#undef NAME_DEV_RANDOM
#undef HAVE_CRYPT_RNG
#undef HAVE_BOEHM_GC
#undef USE_INCLUDED_LIBGC
#undef DISABLE_SHARED_HANDLES
#undef HAVE_TIMEZONE
#undef HAVE_TM_GMTOFF
#undef MONO_SIZEOF_SUNPATH
#undef MONO_ZERO_ARRAY_LENGTH
#undef NEED_LINK_UNLINK
#undef PTHREAD_POINTER_ID
#undef HAVE_GC_H
#undef HAVE_GC_GCJ_MALLOC
#undef WITH_BUNDLE
#undef HAVE_GETHOSTBYNAME2_R
#undef HAVE_ICU
#undef HAVE_KW_THREAD
#undef HAVE_SIGNBIT
#undef USE_MACH_SEMA
#undef HAVE_SOCKLEN_T
#undef HAVE_TRUNCL
+2 -15
View File
@@ -30,15 +30,8 @@ fi
DIE=1
}
if [ -z "$LIBTOOL" ]; then
LIBTOOL=`which glibtool 2>/dev/null`
if [ ! -x "$LIBTOOL" ]; then
LIBTOOL=`which libtool`
fi
fi
(grep "^AM_PROG_LIBTOOL" $srcdir/configure.in >/dev/null) && {
($LIBTOOL --version) < /dev/null > /dev/null 2>&1 || {
(libtool --version) < /dev/null > /dev/null 2>&1 || {
echo
echo "**Error**: You must have \`libtool' installed to compile Mono."
echo "Get ftp://ftp.gnu.org/pub/gnu/libtool-1.2d.tar.gz"
@@ -98,7 +91,7 @@ esac
if grep "^AM_PROG_LIBTOOL" configure.in >/dev/null; then
if test -z "$NO_LIBTOOLIZE" ; then
echo "Running libtoolize..."
${LIBTOOL}ize --force --copy
libtoolize --force --copy
fi
fi
@@ -124,12 +117,6 @@ automake --add-missing --gnu $am_opt ||
echo "Running autoconf ..."
autoconf || { echo "**Error**: autoconf failed."; exit 1; }
if test -d $srcdir/libgc; then
echo Running libgc/autogen.sh ...
(cd $srcdir/libgc ; NOCONFIGURE=1 ./autogen.sh "$@")
echo Done running libgc/autogen.sh ...
fi
conf_flags="--enable-maintainer-mode --enable-compile-warnings" #--enable-iso-c
+41 -417
View File
@@ -1,110 +1,56 @@
AC_INIT(README)
AC_CANONICAL_SYSTEM
AM_CONFIG_HEADER(config.h)
AM_INIT_AUTOMAKE(mono,0.30)
AM_INIT_AUTOMAKE(mono, 0.18)
AM_MAINTAINER_MODE
dnl
dnl libgc checks
dnl
gc_headers=no
gc=included
use_included_gc=no
if test -d $srcdir/libgc ; then
gc_default=included
else
gc_default=boehm
fi
#
# These are the flags that need to be stored in the mono.pc file for
# compiling code that will embed Mono
#
libmono_cflags=""
libmono_ldflags=""
AC_SUBST(libmono_cflags)
AC_SUBST(libmono_ldflags)
dnl if linker handles the version script
no_version_script=no
# Thread configuration inspired by sleepycat's db
AC_MSG_CHECKING([host platform characteristics])
libgc_threads=no
case "$host" in
*-*-mingw*|*-*-cygwin*)
platform_win32=yes
AC_DEFINE(PLATFORM_WIN32)
CC="gcc -mno-cygwin"
HOST_CC="gcc"
# latest libgc already defines GC_WIN32_THREADS
# CPPFLAGS="$CPPFLAGS -DGC_WIN32_THREADS -DWIN32_THREADS"
CPPFLAGS="$CPPFLAGS -DWIN32_THREADS"
CPPFLAGS="$CPPFLAGS -DGC_WIN32_THREADS"
libdl=
libgc_threads=win32
gc_default=boehm
;;
*-*-*netbsd*)
platform_win32=no
CPPFLAGS="$CPPFLAGS -D_REENTRANT"
libmono_cflags="-D_REENTRANT"
LDFLAGS="$LDFLAGS -pthread"
libmono_ldflags="-pthread"
AC_DEFINE(NEED_LINK_UNLINK)
libdl=
libgc_threads=pthreads
;;
*-*-*freebsd*|*-*-*openbsd*)
*-*-*bsd*)
platform_win32=no
CPPFLAGS="$CPPFLAGS -D_THREAD_SAFE"
libmono_cflags="-D_THREAD_SAFE"
LDFLAGS="$LDFLAGS -pthread"
libmono_ldflags="-pthread"
AC_DEFINE(NEED_LINK_UNLINK)
AC_DEFINE(PTHREAD_POINTER_ID)
libdl=
libgc_threads=pthreads
;;
*-*-linux*)
platform_win32=no
CPPFLAGS="$CPPFLAGS -DGC_LINUX_THREADS -DMONO_USE_EXC_TABLES -D_GNU_SOURCE -D_REENTRANT -fexceptions"
libmono_cflags="-DMONO_USE_EXC_TABLES -fexceptions -D_REENTRANT"
libmono_ldflags="-lpthread"
libdl="-ldl"
libgc_threads=pthreads
;;
*-*-hpux*)
platform_win32=no
CPPFLAGS="$CPPFLAGS -DGC_HPUX_THREADS -D_HPUX_SOURCE -D_XOPEN_SOURCE_EXTENDED -D_REENTRANT"
CFLAGS="$CFLAGS +ESdbgasm"
LDFLAGS="$LDFLAGS -z"
libmono_cflags="-D_REENTRANT"
libmono_ldflags="-lpthread"
libgc_threads=pthreads
AC_DEFINE(NEED_LINK_UNLINK)
;;
*-*-solaris*)
platform_win32=no
CPPFLAGS="$CPPFLAGS -DGC_SOLARIS_THREADS -DGC_SOLARIS_PTHREADS -D_REENTRANT"
AC_DEFINE(NEED_LINK_UNLINK)
libmono_cflags="-D_REENTRANT"
libgc_threads=pthreads
;;
*-*-darwin*)
platform_win32=no
CPPFLAGS="$CPPFLAGS -no-cpp-precomp -D_THREAD_SAFE"
libmono_cflags="-D_THREAD_SAFE"
LDFLAGS="$LDFLAGS -pthread"
libmono_ldflags="-pthread"
AC_DEFINE(NEED_LINK_UNLINK)
AC_DEFINE(PTHREAD_POINTER_ID)
AC_DEFINE(USE_MACH_SEMA)
no_version_script=yes
libdl=
libgc_threads=no
gc_default=none
;;
*)
AC_MSG_WARN([*** Please add $host to configure.in checks!])
@@ -114,18 +60,11 @@ case "$host" in
esac
AC_MSG_RESULT(ok)
AM_CONDITIONAL(PLATFORM_WIN32, test x$platform_win32 = xyes)
AM_CONDITIONAL(NO_VERSION_SCRIPT, test x$no_version_script = xyes)
AC_CHECK_TOOL(CC, gcc, gcc)
AC_PROG_CC
AM_PROG_CC_STDC
AC_PROG_INSTALL
dnl We should use AM_PROG_AS, but it's not available on automake/aclocal 1.4
: ${CCAS='$(CC)'}
# Set ASFLAGS if not already set.
: ${CCASFLAGS='$(CFLAGS)'}
AC_SUBST(CCAS)
AC_SUBST(CCASFLAGS)
AC_CHECK_PROG(BISON, bison,yes,no)
if test "x$BISON" = "xno";
@@ -151,10 +90,7 @@ AC_HEADER_STDC
AC_LIBTOOL_WIN32_DLL
AM_PROG_LIBTOOL
AC_CHECK_HEADERS(sys/filio.h sys/sockio.h netdb.h utime.h semaphore.h sys/un.h)
# for mono/mini/tramp-x86.c
AC_CHECK_HEADERS(valgrind/memcheck.h)
AC_CHECK_HEADERS(sys/filio.h sys/sockio.h netdb.h utime.h semaphore.h)
# for mono/metadata/debug-symfile.c
AC_CHECK_HEADERS(elf.h)
@@ -165,21 +101,7 @@ AC_CHECK_HEADERS(wchar.h)
# not 64 bit clean in cross-compile
AC_CHECK_SIZEOF(void *, 4)
WARN=''
if test x"$GCC" = xyes; then
WARN='-Wall -Wunused -Wmissing-prototypes -Wmissing-declarations -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-cast-qual -Wcast-align -Wwrite-strings'
# The runtime code does not respect ANSI C strict aliasing rules
CFLAGS="$CFLAGS -fno-strict-aliasing"
else
# The Sun Forte compiler complains about inline functions that access static variables
# so disable all inlining.
case "$host" in
*-*-solaris*)
CFLAGS="$CFLAGS -Dinline="
;;
esac
fi
CFLAGS="$CFLAGS -g $WARN"
CFLAGS='-g -Wall -Wunused -Wmissing-prototypes -Wmissing-declarations -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-cast-qual -Wcast-align -Wwrite-strings'
AC_PATH_PROG(PKG_CONFIG, pkg-config, no)
if test "x$PKG_CONFIG" = "xno"; then
@@ -188,8 +110,8 @@ fi
dnl for use on the build system
dnl pkg-config is stupid
BUILD_GLIB_CFLAGS=`$PKG_CONFIG --cflags glib-2.0 gthread-2.0`
BUILD_GLIB_LIBS=`$PKG_CONFIG --libs glib-2.0 gthread-2.0`
BUILD_GLIB_CFLAGS=`$PKG_CONFIG --cflags glib-2.0`
BUILD_GLIB_LIBS=`$PKG_CONFIG --libs glib-2.0`
AC_SUBST(BUILD_GLIB_CFLAGS)
AC_SUBST(BUILD_GLIB_LIBS)
@@ -211,8 +133,8 @@ GLIB_REQUIRED_VERSION=1.3.11
PKG_CHECK_MODULES(BASE_DEPENDENCIES, glib-2.0 >= $GLIB_REQUIRED_VERSION)
GLIB_CFLAGS=`$PKG_CONFIG --cflags glib-2.0 gthread-2.0`
GLIB_LIBS=`$PKG_CONFIG --libs glib-2.0 gthread-2.0`
GLIB_CFLAGS=`$PKG_CONFIG --cflags glib-2.0`
GLIB_LIBS=`$PKG_CONFIG --libs glib-2.0`
GMODULE_CFLAGS=`$PKG_CONFIG --cflags gmodule-2.0`
GMODULE_LIBS=`$PKG_CONFIG --libs gmodule-2.0`
@@ -221,31 +143,16 @@ AC_SUBST(GLIB_LIBS)
AC_SUBST(GMODULE_CFLAGS)
AC_SUBST(GMODULE_LIBS)
AC_ARG_WITH(gc, [ --with-gc=boehm,included,none],[gc=$with_gc],[gc=$gc_default])
gc_headers=no
AC_CHECK_HEADERS(gc.h gc/gc.h, gc_headers=yes)
AC_CHECK_LIB(gc, GC_malloc, found_boehm="yes",,$libdl)
gc=auto
AC_ARG_WITH(gc, [ --with-gc=boehm,none],[gc=$with_gc])
# Enable support for NPTL only features like fast thread-local storage
# We can't reliably detect nptl at compile & run time
# so this option will stay until nptl becomes more widespread
AC_ARG_WITH(nptl, [ --with-nptl Enable support for NPTL])
# assembly bundle support, see metadata/make-bundle.pl for more info
AC_ARG_WITH(bundle, [ --with-bundle=bundle_template],[
BUNDLE_FILE=$with_bundle
AC_SUBST(BUNDLE_FILE)
AC_DEFINE(WITH_BUNDLE)
],[with_bundle=no])
AM_CONDITIONAL(WITH_BUNDLE, test x$with_bundle != xno)
LIBGC_CFLAGS=
LIBGC_LIBS=
libgc_dir=
case "x$gc" in
xboehm|xbohem|xyes)
AC_CHECK_HEADERS(gc.h gc/gc.h, gc_headers=yes)
AC_CHECK_LIB(gc, GC_malloc, found_boehm="yes",,$libdl)
if test "x$found_boehm" != "xyes"; then
AC_MSG_ERROR("GC requested but libgc not found! Install libgc or run configure with --with-gc=none.")
AC_MSG_ERROR("GC requested but libgc not found!")
fi
if test "x$gc_headers" != "xyes"; then
AC_MSG_ERROR("GC requested but header files not found! You may need to install them by hand.")
@@ -253,57 +160,27 @@ case "x$gc" in
AC_DEFINE(HAVE_BOEHM_GC)
AC_SUBST(HAVE_BOEHM_GC)
LIBGC_LIBS="-lgc $libdl"
# AC_CHECK_FUNCS does not work for some reason...
AC_CHECK_LIB(gc, GC_gcj_malloc, found_gcj_malloc="yes",,$libdl)
if test "x$found_gcj_malloc" = "xyes"; then
AC_DEFINE(HAVE_GC_GCJ_MALLOC)
fi
LIBS="$LIBS -lgc $libdl"
;;
xincluded)
AC_CONFIG_SUBDIRS(libgc)
found_boehm=yes
gc_headers=yes
use_included_gc=yes
libgc_dir=libgc
LIBGC_CFLAGS='-I$(top_srcdir)/libgc/include'
LIBGC_LIBS='$(top_builddir)/libgc/libmonogc.la'
AC_DEFINE(HAVE_BOEHM_GC)
AC_SUBST(HAVE_BOEHM_GC)
AC_DEFINE(HAVE_GC_H)
AC_DEFINE(USE_INCLUDED_LIBGC)
# The included libgc contains GCJ support
AC_DEFINE(HAVE_GC_GCJ_MALLOC)
;;
xnone)
AC_MSG_WARN("Compiling mono without GC.")
;;
*)
AC_MSG_ERROR([Invalid argument to --with-gc.])
# If libgc was found, use it. Otherwise just warn.
if test "x$found_boehm" != "xyes"; then
AC_MSG_WARN("Compiling mono without GC.")
else
if test "x$gc_headers" != "xyes"; then
AC_MSG_ERROR("Found libgc but not its header files! You may need to install them by hand.")
fi
AC_DEFINE(HAVE_BOEHM_GC)
AC_SUBST(HAVE_BOEHM_GC)
LIBS="$LIBS -lgc $libdl"
gc="boehm"
fi
;;
esac
we_are_embedded_in_mono=yes
export we_are_embedded_in_mono
export libgc_threads
AM_CONDITIONAL(INCLUDED_LIBGC, test x$use_included_gc = xyes)
AC_SUBST(LIBGC_CFLAGS)
AC_SUBST(LIBGC_LIBS)
AC_SUBST(libgc_dir)
dnl
dnl End of libgc checks
dnl
if test x$platform_win32 = xno; then
dnl ******************************************************************
dnl *** Check for large file support ***
@@ -387,21 +264,6 @@ if test x$platform_win32 = xno; then
AC_MSG_RESULT(no)
])
dnl *****************************
dnl *** Checks for SOL_IPV6 ***
dnl *****************************
AC_MSG_CHECKING(for SOL_IPV6)
AC_TRY_COMPILE([#include <netdb.h>], [
int level = SOL_IPV6;
], [
# Yes, we have it...
AC_MSG_RESULT(yes)
AC_DEFINE(HAVE_SOL_IPV6)
], [
# We'll have to use getprotobyname
AC_MSG_RESULT(no)
])
dnl *****************************
dnl *** Checks for SOL_TCP ***
dnl *****************************
@@ -443,32 +305,8 @@ if test x$platform_win32 = xno; then
AC_MSG_RESULT(yes)
AC_DEFINE(HAVE_STRUCT_IP_MREQN)
], [
# We'll just have to try and use struct ip_mreq
# We'll just have to use struct ip_mreq
AC_MSG_RESULT(no)
AC_MSG_CHECKING(for struct ip_mreq)
AC_TRY_COMPILE([#include <netinet/in.h>], [
struct ip_mreq mreq;
mreq.imr_interface.s_addr = 0;
], [
# Yes, we have it...
AC_MSG_RESULT(yes)
AC_DEFINE(HAVE_STRUCT_IP_MREQ)
], [
# No multicast support
AC_MSG_RESULT(no)
])
])
dnl **********************************
dnl *** Check for gethostbyname2_r ***
dnl **********************************
AC_MSG_CHECKING(for gethostbyname2_r)
AC_TRY_LINK([#include <netdb.h>], [
gethostbyname2_r(NULL,0,NULL,NULL,0,NULL,NULL);
], [
# Yes, we have it...
AC_MSG_RESULT(yes)
AC_DEFINE(HAVE_GETHOSTBYNAME2_R)
])
dnl *****************************
@@ -502,23 +340,6 @@ if test x$platform_win32 = xno; then
AC_MSG_RESULT($cv_mono_sizeof_sunpath)
AC_DEFINE_UNQUOTED(MONO_SIZEOF_SUNPATH, $cv_mono_sizeof_sunpath)
dnl *************************************
dnl *** Checks for zero length arrays ***
dnl *************************************
AC_MSG_CHECKING(whether $CC supports zero length arrays)
AC_TRY_COMPILE([
struct s {
int length;
char data [0];
};
], [], [
AC_MSG_RESULT(yes)
AC_DEFINE_UNQUOTED(MONO_ZERO_ARRAY_LENGTH, 0)
], [
AC_MSG_RESULT(no)
AC_DEFINE_UNQUOTED(MONO_ZERO_ARRAY_LENGTH, 1)
])
dnl *****************************
dnl *** Checks for libxnet ***
dnl *****************************
@@ -545,7 +366,6 @@ if test x$platform_win32 = xno; then
dnl *** Checks for libpthread ***
dnl *****************************
AC_CHECK_LIB(pthread, main, LIBS="$LIBS -lpthread")
AC_CHECK_HEADERS(pthread.h)
AC_CHECK_FUNCS(pthread_mutex_timedlock)
AC_MSG_CHECKING(for PTHREAD_MUTEX_RECURSIVE)
AC_TRY_COMPILE([ #include <pthread.h>], [
@@ -558,59 +378,11 @@ if test x$platform_win32 = xno; then
AC_MSG_WARN(Using mono_mutex_t for recursive mutexes)
AC_DEFINE(USE_MONO_MUTEX)
])
AC_CHECK_FUNCS(pthread_attr_setstacksize)
dnl ***********************************
dnl *** Checks for working __thread ***
dnl ***********************************
AC_MSG_CHECKING(for working __thread)
AC_TRY_RUN([
#include <pthread.h>
__thread int i;
static int res1, res2;
void thread_main (void *arg)
{
i = arg;
sleep (1);
if (arg == 1)
res1 = (i == arg);
else
res2 = (i == arg);
}
int main () {
pthread_t t1, t2;
i = 5;
pthread_create (&t1, NULL, thread_main, 1);
pthread_create (&t2, NULL, thread_main, 2);
pthread_join (t1, NULL);
pthread_join (t2, NULL);
return !(res1 + res2 == 2);
}
], [
if test "x$with_nptl" = "x"; then
AC_MSG_RESULT(disabled)
else
AC_MSG_RESULT(yes)
AC_DEFINE(HAVE_KW_THREAD)
fi
], [
AC_MSG_RESULT(no)
])
dnl ********************************
dnl *** Checks for semaphore lib ***
dnl ********************************
# 'Real Time' functions on Solaris
# posix4 on Solaris 2.6
# pthread (first!) on Linux
AC_SEARCH_LIBS(sem_init, pthread rt posix4)
AC_CHECK_LIB(rt, sem_init, LIBS="$LIBS -lrt")
dnl ********************************
dnl *** Checks for timezone stuff **
@@ -637,66 +409,11 @@ if test x$platform_win32 = xno; then
AC_ERROR(unable to find a way to determine timezone)
fi
fi
dnl *********************************
dnl *** Checks for math functions ***
dnl *********************************
LIBS="$LIBS -lm";
AC_CHECK_FUNCS(finite, , AC_MSG_CHECKING(for finite in math.h)
AC_TRY_LINK([#include <math.h>],
[ finite(0.0); ],
AC_DEFINE(HAVE_FINITE) AC_MSG_RESULT(yes),
AC_MSG_RESULT(no)))
AC_CHECK_FUNCS(isfinite, , AC_MSG_CHECKING(for isfinite in math.h)
AC_TRY_LINK([#include <math.h>],
[ isfinite(0.0); ],
AC_DEFINE(HAVE_ISFINITE) AC_MSG_RESULT(yes),
AC_MSG_RESULT(no)))
dnl ****************************************************************
dnl *** Checks for working poll() (macosx defines it but doesn't ***
dnl *** have it in the library (duh)) ***
dnl ****************************************************************
AC_CHECK_FUNCS(poll)
dnl *************************
dnl *** Check for signbit ***
dnl *************************
AC_MSG_CHECKING(for signbit)
AC_TRY_LINK([#include <math.h>], [
int s = signbit(1.0);
], [
AC_MSG_RESULT(yes)
AC_DEFINE(HAVE_SIGNBIT)
], [
AC_MSG_RESULT(no)
])
else
AC_CHECK_LIB(ws2_32, main, LIBS="$LIBS -lws2_32", AC_ERROR(bad mingw install?))
AC_CHECK_LIB(psapi, main, LIBS="$LIBS -lpsapi", AC_ERROR(bad mingw install?))
fi
dnl socklen_t check
AC_MSG_CHECKING(for socklen_t)
AC_TRY_COMPILE([
#include <sys/types.h>
#include <sys/socket.h>
],[
socklen_t foo;
],[
ac_cv_c_socklen_t=yes
AC_DEFINE(HAVE_SOCKLEN_T)
AC_MSG_RESULT(yes)
],[
AC_MSG_RESULT(no)
])
AC_CHECK_FUNCS(truncl, , AC_MSG_CHECKING(for truncl in math.h)
AC_TRY_LINK([#include <math.h>],
[ truncl(0.0); ],
AC_DEFINE(HAVE_TRUNCL) AC_MSG_RESULT(yes),
AC_MSG_RESULT(no)))
dnl ****************************
dnl *** Look for /dev/random ***
dnl ****************************
@@ -770,102 +487,20 @@ if test "x$try_shared_handles" != "xyes"; then
AC_SUBST(DISABLE_SHARED_HANDLES)
fi
ICU_CFLAGS=""
ICU_LIBS=""
enable_icu=no
AC_PATH_PROG(ICU_CONFIG, icu-config, no)
if test "x$ICU_CONFIG" = "xno" -o ! -x "$ICU_CONFIG"; then
AC_MSG_WARN([Only invariant locale available; install ICU for I18N support])
enable_icu="no, if you want full i18n support download it from: http://oss.software.ibm.com/icu/index.html"
else
enable_icu="yes. Version: `$ICU_CONFIG --version`"
AC_DEFINE(HAVE_ICU)
ICU_CFLAGS=`$ICU_CONFIG --cppflags`
ICU_LIBS=`$ICU_CONFIG --ldflags`
fi
AC_SUBST(ICU_CFLAGS)
AC_SUBST(ICU_LIBS)
TARGET="unknown"
ACCESS_UNALIGNED="yes"
JIT_SUPPORTED=no
LIBC="libc.so.6"
case "$host" in
# mips-sgi-irix5.* | mips-sgi-irix6.*)
# TARGET=MIPS;
# ACCESS_UNALIGNED="no"
# ;;
i*86-*-*)
TARGET=X86;
arch_target=x86;
JIT_SUPPORTED=yes
;;
sparc*-*-*)
TARGET=SPARC;
arch_target=sparc;
ACCESS_UNALIGNED="no"
;;
# alpha*-*-linux* | alpha*-*-osf*)
# TARGET=ALPHA;
# ACCESS_UNALIGNED="no"
# ;;
# ia64-*-linux* | ia64-*-hpux*)
# TARGET=IA64;
# arch_target=ia64;
# JIT_SUPPORTED=no;
# ACCESS_UNALIGNED="no";
# case "$host_os" in
# linux*) LIBC="libc.so.6.1";;
# hpux*) LIBC="libc.so.1";;
# esac
# ;;
# m68k-*-linux*)
# TARGET=M68K
# ;;
hppa2.0w-hp-hpux11.00 | hppa64-hp-hpux11.00)
TARGET=HPPA;
arch_target=hppa;
ACCESS_UNALIGNED="no"
;;
macppc-*-openbsd* | powerpc-*-linux* | powerpc-*-openbsd* | \
powerpc-*-sysv* | powerpc-*-darwin*)
TARGET=POWERPC;
arch_target=ppc;
JIT_SUPPORTED=yes
;;
arm-*-linux-* | armv4l-*-linux-*)
TARGET=ARM;
arch_target=arm;
ACCESS_UNALIGNED="no"
;;
s390-*-linux*)
TARGET=S390;
arch_target=s390;
ACCESS_UNALIGNED="no"
;;
#mips-sgi-irix5.* | mips-sgi-irix6.*) TARGET=MIPS; ACCESS_UNALIGNED="no";;
i*86-*-*) TARGET=X86; arch_target=x86;;
sparc*-*-*) TARGET=SPARC; arch_target=sparc; ACCESS_UNALIGNED="no";;
#alpha*-*-linux* | alpha*-*-osf*) TARGET=ALPHA; ACCESS_UNALIGNED="no";;
#m68k-*-linux*) TARGET=M68K;;
macppc-*-openbsd* | powerpc-*-linux* | powerpc-*-openbsd* | powerpc-*-sysv* | powerpc-*-darwin*) TARGET=POWERPC; arch_target=ppc;;
arm-*-linux-* | armv4l-*-linux-*) TARGET=ARM; arch_target=arm; ACCESS_UNALIGNED="no";;
s390-*-linux*) TARGET=S390; arch_target=s390; ACCESS_UNALIGNED="no";;
esac
if test ${TARGET} = ARM; then
dnl ******************************************
dnl *** Check to see what FPU is available ***
dnl ******************************************
AC_MSG_CHECKING(which FPU to use)
AC_TRY_COMPILE([], [
__asm__ ("ldfd f0, [r0]");
], fpu=FPA, [
AC_TRY_COMPILE([], [
__asm__ ("fldd d0, [r0]");
], fpu=VFP, fpu=NONE)
])
AC_MSG_RESULT($fpu)
CPPFLAGS="$CPPFLAGS -DARM_FPU_$fpu"
unset fpu
fi
if test ${TARGET} = unknown; then
CPPFLAGS="$CPPFLAGS -DNO_PORT"
AC_MSG_WARN("mono has not been ported to $host: some things may not work.")
@@ -880,25 +515,20 @@ AM_CONDITIONAL(MIPS_SGI, test ${TARGET}${ac_cv_prog_gcc} = MIPSno)
AM_CONDITIONAL(SPARC, test x$TARGET = xSPARC)
AM_CONDITIONAL(X86, test x$TARGET = xX86)
AM_CONDITIONAL(ALPHA, test x$TARGET = xALPHA)
AM_CONDITIONAL(IA64, test x$TARGET = xIA64)
AM_CONDITIONAL(M68K, test x$TARGET = xM68K)
AM_CONDITIONAL(POWERPC, test x$TARGET = xPOWERPC)
AM_CONDITIONAL(ARM, test x$TARGET = xARM)
AM_CONDITIONAL(S390, test x$TARGET = xS390)
AM_CONDITIONAL(HPPA, test x$TARGET = xHPPA)
AM_CONDITIONAL(JIT_SUPPORTED, test x$JIT_SUPPORTED = xyes)
LIBC="libc.so.6"
AC_SUBST(LIBC)
AC_SUBST(arch_target)
AC_SUBST(CFLAGS)
AC_SUBST(CPPFLAGS)
AC_SUBST(LDFLAGS)
AC_OUTPUT([
Makefile
mint.pc
mono.pc
mono/Makefile
mono/utils/Makefile
@@ -910,35 +540,29 @@ mono/os/Makefile
mono/os/win32/Makefile
mono/os/unix/Makefile
mono/arch/x86/Makefile
mono/arch/hppa/Makefile
mono/arch/ppc/Makefile
mono/arch/sparc/Makefile
mono/arch/s390/Makefile
mono/arch/arm/Makefile
mono/arch/alpha/Makefile
mono/interpreter/Makefile
mono/tests/Makefile
mono/tests/tests-config
mono/benchmark/Makefile
mono/monoburg/Makefile
mono/monograph/Makefile
mono/jit/Makefile
mono/io-layer/Makefile
mono/handles/Makefile
mono/mini/Makefile
mono/profiler/Makefile
runtime/Makefile
scripts/Makefile
man/Makefile
doc/Makefile
docs/Makefile
data/Makefile
samples/Makefile
data/config
mono.spec
])
echo "
GC: $gc
ICU: $enable_icu
"
-5
View File
@@ -1,5 +0,0 @@
Makefile.in
Makefile
config
.cvsignore
browscap.ini
File diff suppressed because it is too large. Load diff
+6 -10
View File
@@ -1,15 +1,11 @@
monodir = $(sysconfdir)/mono
EXTRA_DIST = config.in \
machine.config \
DefaultWsdlHelpGenerator.aspx \
browscap.ini.gz
EXTRA_DIST = config.in machine.config
mono_DATA = config \
machine.config \
DefaultWsdlHelpGenerator.aspx \
browscap.ini
mono_DATA = config machine.config
browscap.ini: browscap.ini.gz
gunzip -c $^ > $@
DISTCLEANFILES = config
config: config.in Makefile
sed -e 's^\@LIBC\@^libc.so.6^g' < $(srcdir)/config.in > config.tmp \
&& mv config.tmp config
Binary file not shown.
+1 -8
View File
@@ -6,16 +6,9 @@
<dllmap dll="odbc32.dll" target="libodbc.so" />
<dllmap dll="libglib-2.0-0.dll" target="libglib-2.0.so" />
<dllmap dll="libgobject-2.0-0.dll" target="libgobject-2.0.so" />
<dllmap dll="libgthread-2.0-0.dll" target="libgthread-2.0.so" />
<dllmap dll="libpango-1.0-0.dll" target="libpango-1.0.so" />
<dllmap dll="libatk-1.0-0.dll" target="libatk-1.0.so" />
<dllmap dll="libgdk-win32-2.0-0.dll" target="libgdk-x11-2.0.so" />
<dllmap dll="libgdk_pixbuf-2.0-0.dll" target="libgdk_pixbuf-2.0.so" />
<dllmap dll="libgdk_pixbuf-2.0-0.dll" target="libgdk-pixbuf-2.0.so" />
<dllmap dll="libgtk-win32-2.0-0.dll" target="libgtk-x11-2.0.so" />
<dllmap dll="libgtk-win32-2.0-0.dll" target="libgtk-x11-2.0.so" />
<dllmap dll="libglade-2.0-0.dll" target="libglade-2.0.so" />
<dllmap dll="oci" target="clntsh" />
<dllmap dll="gtkhtml-3.0" target="libgtkhtml-3.0.so.2" />
<dllmap dll="db2cli" target="libdb2_36.so"/>
<dllmap dll="gstreamer" target="libgstreamer-0.6.so" />
</configuration>
+6 -155
View File
@@ -3,98 +3,27 @@
<configuration>
<configSections>
<section name="appSettings" type="System.Configuration.NameValueFileSectionHandler, System" />
<section name="appSettings" type="System.Configuration.NameValueFileSectionHandler, System" />
<section name="system.diagnostics" type="System.Diagnostics.DiagnosticsConfigurationHandler, System" />
<section name="system.runtime.remoting" type="System.Configuration.IgnoreSectionHandler, System" allowLocation="false"/>
<sectionGroup name="system.web">
<section name="httpHandlers"
type="System.Web.Configuration.HttpHandlersSectionHandler, System.Web" />
<section name="httpModules"
type="System.Web.Configuration.HttpModulesConfigurationHandler, System.Web" />
<section name="machineKey"
type="System.Web.Configuration.MachineKeyConfigHandler, System.Web" />
<section name="authentication"
type="System.Web.Configuration.AuthenticationConfigHandler, System.Web" />
<section name="authorization"
type="System.Web.Configuration.AuthorizationConfigHandler, System.Web" />
<section name="globalization"
type="System.Web.Configuration.GlobalizationConfigurationHandler, System.Web" />
<section name="sessionState"
type="System.Web.SessionState.SessionStateSectionHandler, System.Web" />
<section name="trace"
type="System.Web.Configuration.TraceConfigurationHandler, System.Web" />
<section name="webServices"
type="System.Web.Services.Configuration.WebServicesConfigurationSectionHandler, System.Web.Services" />
<section name="webControls"
type="System.Web.Configuration.WebControlsSectionHandler, System.Web" />
<section name="compilation"
type="System.Web.Configuration.CompilationConfigurationHandler, System.Web" />
<section name="httpRuntime"
type="System.Web.Configuration.HttpRuntimeConfigurationHandler, System.Web" />
<section name="customErrors"
type="System.Web.Configuration.CustomErrorsConfigHandler, System.Web" />
<section name="pages"
type="System.Web.Configuration.PagesConfigurationHandler, System.Web" />
<section name="httpHandlers" type="System.Web.Configuration.HttpHandlersSectionHandler, System.Web" />
<section name="httpModules" type="System.Web.Configuration.HttpModulesConfigurationHandler, System.Web" />
<section name="machineKey" type="System.Web.Configuration.MachineKeyConfigHandler, System.Web" />
<section name="authentication" type="System.Web.Configuration.AuthenticationConfigHandler, System.Web" />
</sectionGroup>
<sectionGroup name="system.net">
<section name="settings"
type="System.Net.Configuration.NetConfigurationHandler, System" />
<section name="connectionManagement"
type="System.Net.Configuration.ConnectionManagementHandler, System" />
<section name="authenticationModules"
type="System.Net.Configuration.NetAuthenticationModuleHandler, System" />
<section name="defaultProxy"
type="System.Net.Configuration.DefaultProxyHandler, System" />
<section name="webRequestModules"
type="System.Net.Configuration.WebRequestModuleHandler, System" />
</sectionGroup>
<section name="system.drawing" type="System.Configuration.NameValueSectionHandler" />
</configSections>
<system.net>
<connectionManagement>
<add address="*" maxconnection="2" />
</connectionManagement>
<authenticationModules>
<add type="System.Net.BasicClient" />
<add type="System.Net.DigestClient" />
<add type="System.Net.NtlmClient" />
</authenticationModules>
<defaultProxy>
<proxy />
<!-- bypassonlocal and proxyaddress are ok -->
<!-- usessystemdefault is not supported -->
</defaultProxy>
<webRequestModules>
<add prefix="http" type="System.Net.HttpRequestCreator, System" />
<add prefix="https" type="System.Net.HttpRequestCreator, System" />
<add prefix="file" type="System.Net.FileWebRequestCreator, System" />
</webRequestModules>
<settings>
<ipv6 enabled="false"/>
</settings>
</system.net>
<system.web>
<httpHandlers>
<add verb="*" path="Trace.axd" type="System.Web.Handlers.TraceHandler, System.Web" />
<add verb="*" path="*.aspx" type="System.Web.UI.PageHandlerFactory, System.Web" />
<add verb="*" path="*.asmx" validate="false"
type="System.Web.Services.Protocols.WebServiceHandlerFactory, System.Web.Services" />
<add verb="*" path="*.ashx" type="System.Web.UI.SimpleHandlerFactory, System.Web" />
<add verb="GET" path="WebResource.axd" type="System.Web.Handlers.AssemblyResourceLoader, System.Web" />
<add verb="*" path="*.asax" type="System.Web.HttpForbiddenHandler, System.Web" />
<add verb="*" path="*.ascx" type="System.Web.HttpForbiddenHandler, System.Web" />
<add verb="*" path="*.config" type="System.Web.HttpForbiddenHandler, System.Web" />
<add verb="*" path="*.cs" type="System.Web.HttpForbiddenHandler, System.Web" />
<add verb="*" path="*.rem" type="System.Runtime.Remoting.Channels.Http.HttpRemotingHandlerFactory, System.Runtime.Remoting" validate="false" />
<add verb="*" path="*.soap" type="System.Runtime.Remoting.Channels.Http.HttpRemotingHandlerFactory, System.Runtime.Remoting" validate="false" />
<add verb="GET,HEAD" path="*" type="System.Web.StaticFileHandler, System.Web" />
<add verb="*" path="*" type="System.Web.HttpMethodNotAllowedHandler, System.Web" />
</httpHandlers>
<httpModules>
<add name="FormsAuthentication" type="System.Web.Security.FormsAuthenticationModule, System.Web" />
<add name="UrlAuthorization" type="System.Web.Security.UrlAuthorizationModule, System.Web" />
<add name="Session" type="System.Web.SessionState.SessionStateModule, System.Web" />
<add name="OutputCache" type="System.Web.Caching.OutputCacheModule, System.Web" />
</httpModules>
<authentication mode="Forms">
<forms name=".MONOAUTH" loginUrl="login.aspx" protection="All" timeout="30" path="/">
@@ -104,83 +33,8 @@
</forms>
</authentication>
<machineKey validationKey="AutoGenerate" decryptionKey="AutoGenerate" validation="SHA1" />
<globalization requestEncoding="utf-8"
responseEncoding="utf-8"
fileEncoding="utf-8"/>
<!--
culture="en-US"
uiculture="en-US" />
-->
<sessionState mode="InProc" />
<webServices>
<protocols>
<add name="HttpSoap"/>
<add name="HttpPost"/>
<add name="HttpGet"/>
<add name="Documentation"/>
</protocols>
<wsdlHelpGenerator href="DefaultWsdlHelpGenerator.aspx" />
</webServices>
<webControls clientScriptsLocation="/web_scripts" />
<compilation debug="false" defaultLanguage="c#">
<compilers>
<compiler language="cs;c#;csharp" extension=".cs" warningLevel="1" compilerOptions=""
type="Microsoft.CSharp.CSharpCodeProvider, System" />
<compiler language="vb;vbs;visualbasic;vbscript" extension=".vb"
warningLevel="1" compilerOptions=""
type="Microsoft.VisualBasic.VBCodeProvider, System" />
</compilers>
<assemblies>
<!--<add assembly="mscorlib" /> -->
<add assembly="System" />
<add assembly="System.Xml" />
<add assembly="System.Data" />
<add assembly="System.Web" />
<add assembly="System.Web.Services" />
<add assembly="System.Drawing" />
<add assembly="*" /> <!-- Add assemblies in bin directory -->
</assemblies>
</compilation>
<httpRuntime executionTimeout="90"
maxRequestLength="4096"
useFullyQualifiedRedirectUrl="false"
minFreeThreads="8"
minLocalRequestFreeThreads="4"
appRequestQueueLimit="100" />
<pages buffer="true"
enableSessionState="true"
autoEventWireup="true"
validateRequest="true" />
</system.web>
<system.runtime.remoting>
<application>
<channels>
<channel ref="http client" displayName="http client (delay loaded)" delayLoadAsClientChannel="true" />
<channel ref="tcp client" displayName="tcp client (delay loaded)" delayLoadAsClientChannel="true" />
</channels>
</application>
<channels>
<channel id="http" type="System.Runtime.Remoting.Channels.Http.HttpChannel, System.Runtime.Remoting" />
<channel id="http client" type="System.Runtime.Remoting.Channels.Http.HttpClientChannel, System.Runtime.Remoting" />
<channel id="http server" type="System.Runtime.Remoting.Channels.Http.HttpServerChannel, System.Runtime.Remoting" />
<channel id="tcp" type="System.Runtime.Remoting.Channels.Tcp.TcpChannel, System.Runtime.Remoting" />
<channel id="tcp client" type="System.Runtime.Remoting.Channels.Tcp.TcpClientChannel, System.Runtime.Remoting" />
<channel id="tcp server" type="System.Runtime.Remoting.Channels.Tcp.TcpServerChannel, System.Runtime.Remoting" />
</channels>
<channelSinkProviders>
<clientProviders>
<formatter id="soap" type="System.Runtime.Remoting.Channels.SoapClientFormatterSinkProvider, System.Runtime.Remoting" />
<formatter id="binary" type="System.Runtime.Remoting.Channels.BinaryClientFormatterSinkProvider, System.Runtime.Remoting" />
</clientProviders>
<serverProviders>
<formatter id="soap" type="System.Runtime.Remoting.Channels.SoapServerFormatterSinkProvider, System.Runtime.Remoting" />
<formatter id="binary" type="System.Runtime.Remoting.Channels.BinaryServerFormatterSinkProvider, System.Runtime.Remoting" />
<provider id="wsdl" type="System.Runtime.Remoting.MetadataServices.SdlChannelSinkProvider, System.Runtime.Remoting" />
</serverProviders>
</channelSinkProviders>
</system.runtime.remoting>
<appSettings>
<!--<add key="yourkey" value="your value" /> -->
<!--<remove key="a key defined higher in the hierarchy" /> -->
@@ -189,8 +43,5 @@
<system.diagnostics>
<trace autoflush="false" indentsize="4" />
</system.diagnostics>
<system.drawing>
</system.drawing>
</configuration>
-16
View File
@@ -1,16 +0,0 @@
2004-01-22 Atsushi Enomoto <[email protected]>
* xml-classes : status update, additional infos.
2004-01-16 Atsushi Enomoto <[email protected]>
* web/commands : Added xml-classes (forgot to commit).
* mono-build-w32.sh : Added icu support as well as glib.
* ChangeLog : tiny fix
2004-01-11 Atsushi Enomoto <[email protected]>
* xml-classes : added v2 info. schema status updates.
Added ChangeLog. (There is no reason not to keep ChangeLog for
documents, at least for not a little changes ;-)
+4 -4
View File
@@ -5,10 +5,10 @@ WEB_FILES= \
oledb papers \
passport plans porting postgresql ppc projects rationale \
resources roadmap runtime sqlclient sqlite sybase tdsclient \
tds-providers status testing thanks tools \
tds-providers team status team testing thanks tools \
porting anoncvs monodoc-xml winforms
OTHERS= pending resources-pending todo mono-build.sh mono-build-w32.sh print-stack
OTHERS= pending resources-pending todo mono-build.sh mono-build-w32.sh
EXTRA_DIST = $(WEB_FILES) README $(OTHERS)
@@ -17,8 +17,8 @@ all-docs: $(WEB_FILES)
runtime documentation download faq contributing \
resources status > all-docs
class-status: class-status.in Makefile.am
cat class-status.in > class-status
class-status: class-status.in pending-classes Makefile.am
cat class-status.in pending-classes > class-status
pending-classes:
-30
View File
@@ -15,33 +15,3 @@ To publish changes:
cd web
make push
############## Samples
If you want to add a new item in the left menu
you have to edit mono/doc/web/commands and add
the entry there.
For new files you can add something as:
level,entry,path_to_the_file,file.src
ex: 1,COBOL#,cobol.html,cobol.src
If you just want to add a link to the menu:
1,MyEntry,URL
ex: 1,About Linux,http://www.linux.org
To test the results under Linux:
1. Edit mono/doc/web/makefile
Delete all the references to class status
and the deploy/index.rss as well as the
mono.exe commands.
2. make
3. Open your browser and point to the
file:///(YOUR PATH HERE)mono/doc/web/deploy/index.html
+111 -262
View File
@@ -1,174 +1,96 @@
* ADO.NET
** Data Access in Mono
<ul>
<li>Today, our goal is to be compatible with .NET 1.0 and .NET 1.1. We also would like
to extend data access beyond what is included with .NET 1.0 and .NET 1.1,
such as, including access to more databases, such as, PostgreSQL and MySQL,
but also provide classes that help in creating data source-agnostic code, such as, Mono.Data.ProviderFactory.</li>
<li>In the future, we would like to be compatible with .NET 1.2. This
would include features like:
<ul>
<li><a href="http://longhorn.msdn.microsoft.com/lhsdk/ndp/daconworkingwithobjectspacesarchitecture.aspx">ObjectSpaces</a></li>
<li>provide support for hosting Mono languages (C-Sharp, MonoBASIC, etc...)
within a DBMS engine, such as, MySQL or PostgreSQL.</li>
<li>implement .net 1.2 classes, such as, those found in System.Data.ProviderBase</li>
<li>other stuff which can be brought up on the mono-list</li>
</ul></li>
</ul>
** Bugs and Feature Requests
<ul>
<li>Bugs with Mono or any data provider in Mono should be reported
in Mono's Bugzilla <a href="http://bugzilla.ximian.com/">here</a>. If you
do not have a Bugzilla user account, it is free
and easy to create
one <a href="http://bugzilla.ximian.com/createaccount.cgi">here</a>.</li>
<p>Mono's ADO.NET Developers:
<ul>
<li>rodrigo -AT- ximian.comNOSPAM - <b>Rodrigo Moya</b> - coordinator
for the ADO.NET implementation and works on the OLE DB provider</li>
<li>danmorg -AT- sc.rr.comNOSPAM - <b>Daniel Morgan</b> - works on
the MySQL, PostgreSQL, and Oracle providers</li>
<li>tim -AT- timcoleman.comNOSPAM - <b>Tim Coleman</b> - works on
the Microsoft SQL Server, Sybase, and TDS providers</li>
<li>brianlritchie -AT- hotmail.comNOSPAM - <b>Brian Ritchie</b> - works on
the ODBC provider and the ProviderFactory</li>
<li>vladimir -AT- pobox.comNOSPAM - <b>Vladimir Vukicevic</b> - works on
the SQL Lite provider</li>
<li>cleared -AT- rogers.comNOSPAM - <b>Christopher Bockner</b> - works on
the IBM DB2 provider</li>
<li>vi64pa -AT- koti.soon.fiNOSPAM - <b>Ville Palo</b> - works on XML stuff in System.Data
including DataSet, XmlDataDocument, and has done lots of testing</li>
</ul>
<li>Any requests for new features or missing functionality
can entered as a bug in Bugzilla too</li>
* Action plan
</ul>
** ADO.NET Data Providers
<p>Mono has many ADO.NET Data Providers to get you connected:
<p>The current plan to implement ADO.NET is as follows:
<ul>
<li>Either create ADO.NET providers or modify pre-exiting ADO.NET providers to
work with Mono</li>
<ul>
<li>Create ADO.NET Providers
<ul>
<li><a href="http://www.go-mono.com/ibmdb2.html">IBM DB2 Universal Database</a></li>
<li><a href="http://www.go-mono.com/mysql.html">MySQL</a></li>
<li><a href="http://www.go-mono.com/odbc.html">ODBC</a></li>
<li><a href="http://www.go-mono.com/oracle.html">Oracle</a></li>
<li><a href="http://www.go-mono.com/oledb.html">OLE DB</a></li>
<li><a href="http://www.go-mono.com/postgresql.html">PostgreSQL</a></li>
<li><a href="http://www.go-mono.com/sqlclient.html">Microsoft SQL Server</a></li>
<li><a href="http://www.go-mono.com/sqlite.html">SQL Lite</a></li>
<li><a href="http://www.go-mono.com/sybase.html">Sybase</a></li>
<li><a href="http://www.go-mono.com/tdsclient.html">Older Microsoft SQL Server and Sybase databases</a></li>
</ul>
<p>Providers which we do not have, but we would like to have. Currently,
some of these databases are supported via the ODBC or OLE DB providers.
<ul>
<li><a href="http://msdn.microsoft.com/library/en-us/dnsql2k/html/sqlxml_intromanagedclasses.asp?frame=true">Managed Classes for SqlXml</a> which is
a .NET data provider for retrieving XML data from a Microsoft SQL Server 2000 database. The System.Data.SqlClient provider
in Mono can be used as a starting point at mcs/class/System.Data/System.Data.SqlClient.</li>
<li><a href="http://www.hughes.com.au/">miniSQL</a></li>
<li><a href="http://www.sleepycat.com/">BerkeleyDB (Sleepycat)</a></li>
<li><a href="http://www.sapdb.org/">SapDB</a></li>
<li><a href="http://www-3.ibm.com/software/data/informix/">Informix</a></li>
<li><a href="http://msdn.microsoft.com/vfoxpro/">Foxpro</a></li>
<li>Microsoft Access - could be done by creating C# bindings to <a href="http://mdbtools.sourceforge.net">MDB Tools</a></li>
<li>dbase or xbase type database files</li>
<li>Others are welcome</li>
</ul>
<p>External Projects that have created ADO.NET Providers that work on Mono:
<ul>
<li><a href="http://www.go-mono.com/firebird.html">Firebird Interbase</a></li> is a
Firebird SQL Managed data provider. It can be used with Interbase databases too. It
is written in 100%C# and does not require a client library. Works on .NET and Mono.</a>
<li><a href="http://gborg.postgresql.org/project/npgsql/projdisplay.php">Npgsql</a> is a
PostgreSQL Managed data provider written
in 100% C#, does not require a client library, and works on .NET and Mono</li>
<li><a href="http://sourceforge.net/projects/mysqlnet/">MySQLNet</a> is a
MySQL Managed data provider written in 100% C#, does not
require a client library, and works on .NET and Mono</li>
</ul>
** Tools
<p>Some tools that can be used for ADO.NET and other technologies (ASP.NET, XML, etc).
<ul>
<li><p><b>SQL# command line query tool</b> is a command-line tool to
enter and execute SQL statements or
execute a batch of SQL commands from a file.
<p>It can
be used to test connection strings, connect to various ADO.NET
providers, save output to text, html, or xml.
<p>The SQL# CLI is distributed with the
Mono runtime and class libraries as an executable assembly sqlsharp.exe.
<p>The source to SQL# CLI can be found in the mcs source at
mcs/tools/SqlSharp/SqlSharpCli.cs
</li>
<li><p><b>SQL# For GTK#</b> - is a graphical SQL database query tool</b> allows a user
to enter SQL commands in a top panel which is a text editor.
<p>It has a toolbar and menu for various tasks, such as, executing
SQL commands one-at-a-time or in a batch. The results would appear
in a bottom panel in a grid or could be saved to a file (xml, html, csv).
<p>Also, the bottom panel would allow logging of SQL command executed.
Here is a screenshot of <a href="http://go-mono.com/images/sqlsharp.png">SQL# For GTK#</a> which
provides a GUI interface using the <a href="http://gtk-sharp.sourceforge.net">Gtk#</a> toolkit.
<p>SQL# For GTK# can be found in mono cvs as sqlsharpgtk.</li>
</ul>
<p>Tools we would like to have, but they have not been created yet:
<ul>
<li>Mono has an <b>XML Schema Definition tool</b> (xsd.exe).</b>
<ul>
<li>This tool
would works like the xsd.exe tool included with
the .NET Framework. The Xsd.exe tool has the
following uses:
<ul>
<li><b>XDR to XSD</b> - used to generate an XML schema from an XDR (XML Data Reduced schema) file.
XDR was used by Microsoft prior to XSD becoming a W3C recommendation. So, this needs
to be supported for legacy reasons</li>
<li><b>XML to XSD</b> - used to generate an XML schema from an XML file</li>
<li><b>XSD to DataSet</b> - used to generate DataSet classes from an XSD schema file. The
DataSet classes created can then be used with XML data</li>
<li><b>XSD to Classes</b> - used to generate classes from an XSD schema file. The
classes created can be used with System.XML.Serialization.XMLSerializer
to read and write XML code that follows the schema</li>
<li><b>Classes to XSD</b> - used to generate an XML schema
from type(s) in a assembly file. The
XML schema created by the tool defines the XML format used
by System.XML.Serialization.XMLSerializer</li>
</ul>
<li>Xsd.exe is used to manipulate XML schemas that
follow the http://www.w3.org/XML/Schema">XML Schema Definition (XSD)</a> language
recommended by the <a href="http://w3.org/">World Wide Web Consortium (W3C)</a></li>
<li>How this tool could be created:
<ul>
<li>Write xsd.exe in C# and run on Mono</li>
<li>Make sure we have XML Schema support in System.Xml.Schema. Currently,
it is wrapped around libxlst</li>
<li>XML serialization support in System.Data classes</li>
<li>Create the TypedDataSetGenerator class in System.Data</li>
<li>Using CodeDOM or Reflection.Emit to create code</li>
<li>Make sure DataSet, XmlDataDocument, and related classes
are implemented fully</li>
</ul>
</li>
<li><a href="http://www.go-mono.com/ibmdb2.html">IBM DB2 Universal Database</a></li>
<li><a href="http://www.go-mono.com/mysql.html">MySQL</a></li>
<li><a href="http://www.go-mono.com/odbc.html">ODBC</a></li>
<li><a href="http://www.go-mono.com/oracle.html">Oracle</a></li>
<li><a href="http://www.go-mono.com/oledb.html">OLE DB</a></li>
<li><a href="http://www.go-mono.com/postgresql.html">PostgreSQL</a></li>
<li><a href="http://www.go-mono.com/sqlclient.html">Microsoft SQL Server</a></li>
<li><a href="http://www.go-mono.com/sqlite.html">SQL Lite</a></li>
<li><a href="http://www.go-mono.com/sybase.html">Sybase</a></li>
<li><a href="http://www.go-mono.com/tdsclient.html">TDS Generic</a></li>
<li>Providers which we do not have, but we would like to have. Currently,
some of these databases are supported via the ODBC or OLEDB providers.</li>
<ul>
<li><a href="http://msdn.microsoft.com/library/en-us/dnsql2k/html/sqlxml_intromanagedclasses.asp?frame=true">Managed Classes for SqlXml</a> which is
a .NET data provider for retrieving XML data from a Microsoft SQL Server 2000 database. The System.Data.SqlClient provider
in Mono can be used as a starting point at mcs/class/System.Data/System.Data.SqlClient.</li>
<li><a href="http://www.hughes.com.au/">miniSQL</a></li>
<li><a href="http://www.sleepycat.com/">BerkeleyDB (Sleepycat)</a></li>
<li><a href="http://www.sapdb.org/">SapDB</a></li>
<li>Microsoft Access - could be done by creating C# bindings to <a href="http://mdbtools.sourceforge.net">MDB Tools</a></li>
<li>dbase or xbase type database files</li>
<li>Others are welcome</li>
</ul>
</ul></li>
<br>
<li>Modify Pre-existing ADO.NET Providers to work with Mono. This may
require fixing or implementing areas of Mono too.
<ul>
<li><a href="http://www.go-mono.com/firebird.html">Firebird Interbase</a></li>
<li><a href="http://gborg.postgresql.org/project/npgsql/projdisplay.php">Npgsql</a> is a
PostgreSQL Managed data provider written
in 100% C#, does not require a client library, and works on Mono</li>
<li><a href="http://sourceforge.net/projects/mysqlnet/">MySQLNet</a> is a
MySQL Manager data provider written in 100% C#, does not
require a client library, and works on Mono</li>
</ul>
</li>
</ul>
</li>
<li><b>Application XML Configuration File Editor</b> - a tool
to create and edit an application configuration file, such as,
we have a .net application named Accouting.exe, the tool could edit
the application configuration file Accounting.exe.config so a user could
connect to the database used by the program. This tool has not
been created.</li>
</ul>
<br>
<li>Create Tools for Configuration, Testing, and Entering SQL Queries
<ul>
<li><b>SQL# CLI - a command-line tool</b> written in C# to
execute SQL commands,
test connection strings, and connect to various ADO.NET
providers in Mono. The SQL# CLI can be found in
mcs/tools/SqlSharp/SqlSharpCli.cs</li>
<li><p><b>SQL# GUI - a GUI tool</b> written in C# to
execute SQL commands.
Currently, there is SQL# For GTK# which
can be found at
mcs/tools/SqlSharp/gui/gtk-sharp
It has a SQL editor with
syntax hi lighting of SQL keywords. This will be
moving to its own cvs modeul sqlsharpgtk.</li>
<li><b>Configuration Command-Line and GUI Tools for ADO.NET</b>.
These tools have not been started. The tools would be written in
C# and run on Mono. The
configuration tool can be used to do the following:
<ul>
<li>bebased on the Application XML Configuration File Editor</li>
<li>setup DSNs for the ODBC and OLE-DB
providers and configurations for
their underlying libraries (unixODBC and libgda)</li>
@@ -178,39 +100,22 @@
freetds.conf for Microsoft SQL Server and Sybase</li>
</ul>
</li>
</ul>
</ul>
* Current Status
** Extra Classes in Mono ADO.NET
<p>An ADO.NET <a href="http://www.go-mono.com/provider-factory.html">Provider Factory</a>
was created by Brian Ritchie. The
Provider Factory is a way to dynamically create
connections, commands, parameters, and data adapters based on configuration
information.
<p>Variouls ADO.NET Providers have been created: PostgreSQL, MySQL, Sybase, SQL Lite,
Microsoft SQL Server, OLE DB, ODBC, and TDS Generic. See their respective web page for
more information.
** Current Status
<p>Various ADO.NET Providers have been created at various stages of
development including:
Firebird/Interbase, IBM DB2 Universal Database, MySQL, ODBC, OLE DB, Oracle,
PostgreSQL, SQL Lite, Sybase, Microsoft SQL Server, and TDS Generic.
See their respective web page for more information.
<p>Constraints need lots of work
<p><b>Data Relations</b> via DataRelation, DataRelationCollection, and
other classes have not been implemented
<p><b>Constraints</b> need lots of work
<p><b>XML Schema Definition tool</b> xsd.exe that is included
in the .NET Framework has not been created for Mono
<p><b>TypeDataSetGenerator</b> needs to be stubbed and implemented.
<p>TypeDataSetGenerator needs to be stubbed and implemented.
<p><b>DataSet, DataAdaptor, DataTable, DataRelation, DataRow, DataColumn,
DataColumnCollection, DataRowCollection, and others</b> need more work. There are
many classes that are just stubs and need to be implemented. Ville Palo has been
doing much testing here.
many classes that are just stubs and need to be implemented.
<p><b>XML support in System.Data</b> needs work. This involves working on
the classes: DataSet, XmlDataDocument, and the method ExecuteXmlReader() that
@@ -218,13 +123,22 @@
Stuart Caborn has started the XML support in a DataSet. Tim Coleman started
XML support in the ExecuteXmlReader() in a SqlCommand. Ville Palo has been
heavily modifying DataSet, XmlDataDocument, and other classes for reading
and writing XML. XML Serialization support in DataSet needs to be implemented.
<p><b>Integration with ASP.NET</b> has been created. Data binding of
a DataTable in a DataSet to a System.Web.UI.WebControls.DataGrid works. Data binding
of other types works too.
and writing XML.
<p><b>Database Access from ASP.NET</b>:
<p><b>ADO.NET Provider Factory</b> has been started by Brian Ritchie. The
Provider Factory is way to dynamically create
connections, commands, parameters, and data adapters based on configuration information. The
provider factory also provides utility functions needed by a lot of
providers but are not exposed via the provider. The ProviderFactory
is found at mcs/class/Mono.Data and includes a test named test.cs for it in
mcs/class/Mono.Data/Test. Also, take a look at the sample .config file for the
test.exe application named test.exe.config. The .config file is automatically
read when you use the Mono.Data.ProviderFactory or Mono.Data.DataTools.
<p><b>Integration with ASP.NET</b> has not been started, such as, data binding
to a System.Web.UI.WebControls.DataGrid. This may involve implementing many classes
in System.Web and System.Data. If you want to help,
contact Gonzalo Paniagua Javier. Here is information about using ADO.NET in ASP.NET:
<ul>
<li>Take a look at xsp in cvs and look at the examples in test: dbpage1.aspx
and dbpage2.aspx:
@@ -266,10 +180,10 @@
has not been started, such as, data binding
to a GtkTreeView. This may involve creating new classes
to go between the glist data model and the ADO.NET data model.
Mike Kestner or Rachel Hestilov would be the best people to ask for help on GTK#.
Mike Kestner would be the best person to ask for help on GTK#.
<p><b>Integration with QT#</b> has not been started. Any information on
how this can be done is appreciated. Marcus would be the best
how this can be done is appreciated. Adam Treat would be the best
person to ask about QT#.
<p><b>Building System.Data</b>
@@ -315,77 +229,12 @@
</pre>
</ul>
** Testing
* Testing
<ul>
<li>Testing connection-oriented classes are done
via the provider specific tests
found in the mcs source at mcs/class</br>
<table border=1>
<tr>
<td><b>Name</b></td>
<td><b>Assembly /</br> Namespace</b></td>
<td><b>Test</b></td>
</tr>
<tr>
<td>Microsoft</br> SQL</br> Server</br></td>
<td>System.Data /</br> System.Data.SqlClient</td>
<td>SqlTest.cs at</br> System.Data/Test</td>
</tr>
<tr>
<td>PostgreSQL</br> (Npgsql)</td>
<td>Npgsql /</br> Npgsql</td>
<td>*.cs at</br> Npgsql/Test</td>
</tr>
<tr>
<td>PostgreSQL</br> (Mono)</td>
<td>Mono.Data.PostgreSqlClient /</br> Mono.Data.PostgreSqlClient</td>
<td>PostgresTest.cs at</br> System.Data/Test</td>
</tr>
<tr>
<td>MySQL</br> (Mono)</td>
<td>Mono.Data.MySql /</br> Mono.Data.MySql</td>
<td>MySqlTest.cs at</br> Mono.Data.MySql/Test</td>
</tr>
<tr>
<td>Oracle</br> (Mono)</td>
<td>System.Data.OracleClient /</br> System.Data.OracleClient</td>
<td>TestOracleClient.cs at</br> System.Data.OracleClient/Test</td>
</tr>
<tr>
<td>ODBC</br> (Mono)</td>
<td>System.Data.Odbc /</br> System.Data</td>
<td>OdbcTest.cs (to connect to MS SQL Server)at</br> System.Data/Test</td>
</tr>
</table>
<li>Testing connection-oriented classes are done via the provider specific tests
<li><a href="http://www.go-mono.com/testing.html">Testing non-connection classes</a> are
done via mono's modified version of NUnit.
<ul>
<li>To run all the NUnit tests for Mono, you need the mcs source. cd to the root
of the mcs source. To run it:
<ul>
<li>On Linux: make -f makefile test</li>
<li>On Windows: make test</li>
</ul>
</li>
<li>If you just want to run the NUnit tests for System.Data, you would cd into
the mcs source at class/System.Data/Test and run it:
<ul>
<li>On Linux: make -f makefile test</li>
<li>On Windows: make test</li>
</ul>
</li>
</ul>
</li>
</ul>
done via mono's modified version of NUnit.</li>
</ul>
+1 -4
View File
@@ -2,7 +2,7 @@
Anonymous access to the Mono is available currently from three
servers (anoncvs-spain-1.go-mono.com,
anoncvs-spain-2.go-mono.com and us-anoncvs.go-mono.com).
anoncvs-spain-2.go-mono.com and anoncvs-us-1.go-mono.com).
You can also use `anoncvs.go-mono.com', and that will pick a
server automatically for you.
@@ -43,9 +43,6 @@
Special thanks to Jesus Climent, Rodrigo Moya, Juantomás
García and Ismael Olea for making this happen.
Thanks to Matt Liotta of MontaraSoftware for hosting our
US-based AnonCVS server.
<a name="#mirror">
** Becoming an AnonCVS mirror
+73 -59
View File
@@ -7,88 +7,102 @@
* Web Services (the SOAP-based rpc system).
</ul>
Both are functional at this point, and applications like
"IBuySpy" run with Mono.
There is work underway for both systems. The Web Forms
support is more advanced at this point, and various ".aspx"
programs can be run using the Mono runtime (embedded into
either the XSP server or the mod_mono Apache module).
ASP.NET works either embedded into
our XSP server test server or the mod_mono Apache module.
We are now working on bug fixing and adding missing features
We are now working bug fixing and adding missing features
after making the whole pipeline compatible with MS.
Tim started work on the Web Services. After that, Lluis is in
charge and has been working hard on them as part of our
<a href="http://www.ximian.com/about_us/press_center/press_releases/index.html?pr=sourcegear">SourceGear</a> contract.
Web services are now supported and there are some samples in the
XSP set of tests.
Tim started work on the Web Services. Although we have a
SoapFormatter as part of the remoting infrastructure already
(contributed by Jesus), most people will be using the ASP.NET
Web Services support. Work for the supporting class libraries
just started recently.
** Hosting
** HttpRuntime
ASP.NET provides a hosting interface. Today we ship support
for two different hosting mechanisms:
<ul>
* <a href="#xsp">XSP</a>: A light-weight C# web server.
Patrik has authored most of the HttpRuntime support (both on
the System.Web and on the foundation).
* <a href="#mod_mono">mod_mono</a>: An apache module
that can host the Mono runtime and the ASP.NET runtime
</ul>
We are currently working on this.
<a name="xsp">
** XSP
XSP is a simple web server written in C# that can be used to
run your ASP.NET applications. The code is available from our
<a href="download.html">download page</a> or from the <a
href="anoncvs.html">Anonymous CVS</a> repository (module name:
xsp)/.
This is where initial development of the .aspx/.ascx/.asax
compiler to C# took place. That compiler is now integrated in
System.Web classes mostly under System.Web.Compilation
namespace. We added a new web server that works with mono and
MS runtime and is being used to debug our classes. It resides
in xsp/server.
This is where initial development of the .aspx/.ascx/.asax compiler
to C# took place. That compiler is now integrated in System.Web classes
mostly under System.Web.Compilation namespace.
A couple of classes of this new server can be reused/extended
to make an apache module/cgi using mono (MonoWorkerRequest and
MonoApplicationHost). This server also uses a couple of
plugins distributed with Mono to support gzip HTTP transfers.
We added a new web server that works with mono and MS runtime and is
being used to debug our classes. It resides in xsp/server. A couple of
classes of this new server can be reused/extended to make an apache
module/cgi using mono (MonoWorkerRequest and MonoApplicationHost).
There is also a set of .aspx pages to test the server along with
There is also a bunch of .aspx pages to test the server along with
a few user controls under xsp/test.
You can check it out from CVS and run 'make install' to test it.
<a name="mod_mono">
* mod_mono
This Apache module is available from our <a
href="download.html">download page</a>. The <a href="anoncvs.html">
cvs</a> module name is mod_mono. It works with both 1.3 and 2.0
versions of the <a href="http://httpd.apache.org">apache server</a>.
It allows apache to serve ASP.NET pages.
Work is underway to improve it.
** Controls
A lot of work has been put in the various classes that
implement the controls (UI.HtmlControls and UI.WebControls).
They have been coded mostly in the dark, and without being
implement the controls (UI.HtmlControls and UI.WebControls),
but they have been coded mostly in the dark, and without being
able to test them in real life: Gaurav and Leen worked very
hard on this namespace. After that, we keep fixing bugs on
them.
hard on this namespace.
We can now render all HtmlControls and all WebControls.
We can now render all HtmlControls and almost all WebControls.
DataGrid and DataList controls are being finished by Gaurav.
Xml control needs some work on System.Xml related to XSL.
Help in making the controls better is appreciated.
** Extending ASP.NET
** ASP.NET and free controls.
Currently you have to reference in your ASP.NET the control
and all of its properties, which works fine if you have a GUI
designer, but is harder for people used to develop using text
editors.
We want to encourage developers to create open source controls
that can be used both on Mono's ASP.NET and Microsoft's ASP.NET.
Since we have a parser, we could extend this parser to allow
people to still use ASP.NET controls, using a simpler syntax.
For example people doing blogs and editing their templates
over the web probably do not want to use direct ASP.NET but a
wrapper around it.
* Web Forms: The pieces (historical)
There are a couple of components to the puzzle:
<ul>
* .aspx page parser (converts .aspx to C# code).
* System.Web.HttpRuntime support.
* Web controls (System.Web.UI.HtmlControls and
System.Web.UI.WebControls).
* Underlying infrastructure for the controls (System.Web.UI).
* HttpRuntime.ProcessRequest is the core of the ASP.NET
implementation.
</ul>
Gonzalo has been working on an ASP.NET parser that takes .aspx
files and generated the code required to run them (the code lives in
module `xsp' along with a little web server for testing).
Most of the runtime support was written by Patrik Torstensson
(now at Intel). This was interesting, because in order to implement
some of its features, Patrik had to go into the runtime/JIT engine and
he spent a few weeks doing work there.
The classes for running ASP.NET are being actively written.
Gaurav, Leen and Patrik worked in the core of the classes
required to run ASP.NET web application as well as a small
embeddable web server.
Duncan got our System.Web assembly to compile.
** How to Help
-38
View File
@@ -1,38 +0,0 @@
You can read the aggregates news from the Mono developers in
<a href="http://www.go-mono.com/monologue">Monologue</a>. You
can also download our aggregator from the <a
href="anoncvs.html">AnonCVS</a> server.
Various Mono contributors maintain blogs, some are listed here:
<a href="http://codeblogs.ximian.com/blogs/benm/index.rdf"><img align="center" src="images/xml.gif"></a>
<a href="http://codeblogs.ximian.com/blogs/benm/">Ben Maurer</a>
<br>
<a href="http://ada.fciencias.unam.mx/~olopez/jscript/cesar.rss2"><img align="center" src="images/xml.gif"></a>
<a href="http://ada.fciencias.unam.mx/~olopez/jscript/">Cesar Nataren</a>
<br>
<a href="http://www.jacksonh.net/jackson/blog/jackson.rss2"><img align="center" src="images/xml.gif"></a>
<a href="http://www.jacksonh.net/jackson/blog/">Jackson Harper</a>
<br>
<a href="http://primates.ximian.com/~lluis/blog/index.rdf"><img align="center" src="images/xml.gif"></a>
<a href="http://primates.ximian.com/~lluis/blog/">Lluis S&aacute;nchez</a>
<br>
<a href="http://primates.ximian.com/~martin/blog/rss.xml"><img align="center" src="images/xml.gif"></a>
<a href="http://primates.ximian.com/~martin/blog/">Martin Baulig</a>
<br>
<a href="http://primates.ximian.com/~miguel/miguel.rss2"><img align="center" src="images/xml.gif"></a>
<a href="http://primates.ximian.com/~miguel/activity-log.php">Miguel de Icaza</a>
<br>
<a href="http://primates.ximian.com/~mkestner/blog/index.rdf"><img align="center" src="images/xml.gif"></a>
<a href="http://primates.ximian.com/~mkestner/blog/">Mike Kestner</a>
<br>
<a href="http://pages.infinit.net/ctech/poupou.rss"><img align="center" src="images/xml.gif"></a>
<a href="http://pages.infinit.net/ctech/poupou.html">Sebastien Pouliot</a>
<br>
<a href="http://primates.ximian.com/~gonzalo/mono/blog/index.xml"><img align="center" src="images/xml.gif"></a>
<a href="http://primates.ximian.com/~gonzalo/mono/blog/">Gonzalo Paniagua</a>
<br>
<a href="http://codeblogs.ximian.com/blogs/ndrochak/index.rdf"><img align="center" src="images/xml.gif"></a>
<a href="http://codeblogs.ximian.com/blogs/ndrochak/">Nick Drochak</a>
+4 -31
View File
@@ -1,38 +1,11 @@
* Mono
<a href="http://www.amazon.de/exec/obidos/ASIN/3827264928/qid=1050051051/sr=2-1/ref=sr_2_3_1/028-2755135-1623712">
Mono: .NET-kompatible Anwendungen mit dem Open Source-Framework
</a>
* C#
* C# Books
A Programmer's Introduction to C# - Second Edition: Eric Gunnerson
* .NET Framework
Avery good techincal book about .NET is Don Box's <a
href="http://service.bfast.com/bfast/click?bfmid=2181&sourceid=39391960&isbn=0201734117">Essential
.NET</a>
* Remoting
<a href="http://www.dotnetremoting.cc/book/AdvancedDotNetRemoting.asp">Advanced .NET Remoting: Ingo Rammer</a>
* Threading
.NET Multithreading: Alan L. Dennis (ISBN 1-930110-54-5)
* Web Services
Web Services: Architecture and Implementation with .NET: Keith Ballinger
* ASP.NET
Essential ASP.NET with Examples in C# by Fritz Onion
ASP.NET in a Nutshell by G. Andrew Duthie & Matthew MacDonald
Programming ASP.NET by Jessy Liberty & Dan Hurtwitz
<a href="http://www.dotnetremoting.cc/book/AdvancedDotNetRemoting.asp">
Advanced .NET Remoting: Ingo Rammer</a>
* Compiler Implementation
@@ -61,4 +34,4 @@
MIPS Processor supplement</a>
<a href="http://www.sparc.org/standards/V8.pdf">The SPARC Architecture
Manual Version 8</a>
Manual Version 8</a>
-76
View File
@@ -1,76 +0,0 @@
* Bug reporting
To report bugs you need to create a <a
href="http://bugzilla.ximian.com/createaccount.cgi">Bugzilla
Account</a>.
Here are some convenient shortcuts to browse or add bug reports.
<ul>
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FClass+Libraries&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&newqueryname=&form_name=query&order=bugs.priority%2C%20bugs.bug_id">[Query]</> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FClass%20Libraries">[Add]</a> Class Libraries
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FCompilers&component=IL+assembler&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FCompilers&component=IL%20assembler">[Add]</a> IL Assembler.
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FCompilers&component=C%23&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FCompilers&component=C%23">[Add]</a> C# Compiler.
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FRuntime&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FRuntime">[Add]</a> Runtime
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FDoctools&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FDoctools">[Add]</a> Documentation system.
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=gtk%23&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=gtk%23">[Add]</a> Gtk#
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FClass+Libraries&component=System.Web&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FClass%20Libraries&component=System.Web">[Add]</a> ASP.NET WebForms
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FClass+Libraries&component=System.Web.Services&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FClass%20Libraries&component=System.Web.Services">[Add]</a> ASP.NET Web Services
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FDebugger&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FDebugger">[Add]</a> Debugger.
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono+Develop&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono+Develop">[Add]</a> Mono Develop.
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono+Tasks&product=Mono%2FClass+Libraries&product=Mono%2FCompilers&product=Mono%2FDebugger&product=Mono%2FDoctools&product=Mono%2FRuntime&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> All core components.
</ul>
<a name="goodbugreport"/>
** How to make good bug reports
<ol>
* Submit a test case, the smaller it is, the better
* Use <a href="http://bugzilla.ximian.com">
http://bugzilla.ximian.com</a> to report the bug.
<p>In <b>addition</b> to bugzilla, posting to the list is
fine if the bug merits larger exposure or design
discussions to solve; posting to the list twice or more
is just a way to annoy people and make them waste time,
specially when you start a new thread about it.
* If the test involves libraries or assemblies that are
not part of mono, add info about where to download all
the dependencies, and how to compile/install them.
* If compiling the test case requires more than:
<pre> mcs test.cs </pre>
provide the <b>full command line</b> you used to compile
the test.
* If running the test requires more than:
<pre> mono test.exe </pre>
provide the <b>full command line</b> needed to replicate
the bug.
* Provide info about the version of the software you're
using (both mono and the operating system or relevant
libraries).
* Provide the output you expect the test case to produce.
* Provide the actual output <b>you</b> get from the test case.
</ol>
A good bug report complies with at least 6 items from the list.
If your bug report complies with 3 or less items, it is very
poor and it means it will take much more time to fix (when it's
not ignored).
+7 -9
View File
@@ -1,15 +1,13 @@
* MCS: The Ximian C# compiler
The Mono C# compiler is considered feature complete at this
point and relatively mature. MCS is able to compile itself
and many more C# programs (there is a test suite included that
you can use). It is routinely used to compile Mono, roughly
half a million lines of C# code.
MCS is currently able to compile itself and many more C#
programs (there is a test suite included that you can use).
It is routinely used to compile Mono, roughly half a million
lines of C# code.
* Pending tasks
There are a few known bugs in the Mono C# compiler, but
they are very very few at this point,
We are in feature completion mode right now. There are still
a couple of areas that are not covered by the Mono compiler, but
they are very very few at this point (security attributes),
you can also browse the MCS <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FMCS&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">bugs</a> from Bugzilla.
A test suite is maintained to track the progress of
+59 -231
View File
@@ -1,54 +1,25 @@
* CVS Access
Here we describe how one obtains commit access to the Mono CVS
repository and the responsibilities that come with that access
privilege.
If you are an active Mono developer, you can get a CVS account
that hosts the Mono source code. This web page contains
details about how to use the CVS server as well as the
policies to use it.
These only apply to the Mono CVS repository, and not to the <a
href="http://forge.novell.com/modules/xfmod/community/?monocomm">Mono
Community</a> repositories at Novell Forge.
If you are not a developer, but want to track the development, please
see the <a href="anoncvs.html">AnonCVS</a> instructions.
** What is CVS?
Briefly, CVS is a system tool used to store and maintain files and
a history of their changes over time. The Mono source code and related
files are kept on a CVS server at Ximian.
** What Access?
We mean "commit" access. This is the privilege to make permanent
changes to the Mono source code and related files. You need an account
created by the CVS server administrator in order to commit changes to
the files on that server.
** How Does One Obtain Access?
Any active Mono developer can get a CVS account. Normally one is
considered an 'active' developer after sending several patches to the
mailing lists and/or bugzilla for review.
If you are not a developer, but want to access the latest sources,
please see the <a href="anoncvs.html">AnonCVS</a>
instructions. If you are not a direct contributor to Mono,
but want to host your .NET or Mono-based project, you can use
<a href="forge.html">Novell Forge</a>.
If you feel you are ready for a CVS account send an e-mail to
<a href="mailto:[email protected]">miguel</a> with your public OpenSSH
key for this purpose. Please specify if the key was generated with SSH
version 1 or version 2. Detailed instructions are below.
Send an e-mail to miguel with your public OpenSSH key for this
purpose. Please specify if the key was generated with SSH version 1
or version 2.
* Policies
It is necessary that everyone with CVS commit access respect and
adhere to the following rules. If you ask for and are granted CVS
access, you are agreeing to follow these policies.
Here are some policies about the use of the Mono CVS server.
** Code License
If you are about to commit code to a module, the code that is
being committed should be released under the same license as
being commited should be released under the same license as
the code that the module has.
Check the license if you are unsure, but it is basically:
@@ -57,105 +28,25 @@
If in doubt, check with the maintainers of the module, or send
mail to [email protected].
** Changing code
** Commiting code.
Even if you have CVS commit access, that doesn't mean you can change
code at will in any directory or module. Directories and Namespaces
have a sort of unofficial ownership. If you are not the owner of a
piece of code and you want to make changes/fixes to it, there are two
cases.
1) The change is a typo fix or a one-liner build or trivial fix. In
this case almost anyone can commit (always remembering to add the
proper changelog entry to explain the change). We say "almost anyone",
because changes to certain directories almost always should be reviewed
first. Such as changes to core stuff: corlib/System, System.Collections,
mini/, metadata/, System.IO.
If you are the maintainer for a piece of code, feel free to
commit code, and delegate the work to others.
2) The change is larger. In this case the patch *must* be sent to
mono-devel-list for review by the owner of the code and by the other
hackers. Always submit such patches to the list or bugzilla, although
you may put the owner of the code in the CC header. Hackers come and go.
Mailing a patch to only a personal address is a good way to get the
patch forgotten and missed. Plus, getting the patches reviewed as well
as reviewing them, is a good thing, so try to get used to it.
Use ChangeLog entries so we can keep textual descriptions of
your work, and use the contents of your ChangeLog file as the
CVS commit message (ie, paste the contents of this into the
editor buffer).
Note: If the patch is an addition of code and doesn't change any of the
existing code, the rules are slightly relaxed: there is more freedom
in committing such changes, if they don't interfere with the existing
codebase.
If you are making changes to someone else's code, please make
sure you get in touch with the maintainer of that code before
applying patches. You want to avoid commiting conflicting
work to someone else's code.
** Owning Code
Now, how do you get to be the owner of a chunk of code? The answer is
simple. You wrote the code, so you're the unofficial owner. There is
also another way. After sending a few patches for the code, the
owner (or the core developers of mono, if the owner somehow disappeared)
trusts you and tells you you're free to commit without getting his
review first.
Here is a (partial) list of namespaces/directories with their owners:
<ul>
<li>Debugger module and debug code in mono: martin
<li>mcs compiler: miguel, martin, ravi
<li>Reflection/Reflection.Emit: lupus, zoltan
<li>IO-layer: dick
<li>mini: lupus, dietmar
<li>test suite: nickd (though anyone should feel free to add test cases)
<li>System.IO: dick, ville
<li>security stuff: spouliot
<li>ilasm: jackson
<li>System.Web and related: gonzalo
<li>System.Xml: eno, piers
<li>Remoting: dietmar, lluis
<li>interop/marshal: dietmar
<li>threads: dick
</ul>
If you are the owner of a piece of code, feel free to commit code, and
delegate the work to others.
But, if you're not the owner of the code, committing a rewrite without
getting a review first is not good cvsitizenship (especially when the
rewrite claimed to fix bugs, but not a single regression test has been
added to the suite).
** Commit Rules
Once you know you can commit a patch (because of the rules above) there
are a few other small rules to follow:
<ul>
<li>Always add a changelog entry with a meaningful explanation
<li>If you fix a bug, add a regression test for it in the regression
suite
<li>Don't commit unrelated changes together with a fix: do fine-grained
commits
<li>Always check what you're committing: make sure you're only committing
what you need and make sure you don't change line endings and
whitespace. Do a 'cvs diff -u' of the files you're going to commit and
check the changes.
<li>Don't do reformatting commits, unless you're the original author of
the code
<li>When fixing bugs, don't follow the documentation blindly, it may
well be wrong. Test the behavior on the MS runtime or ask on the list
for discussion if unsure. Don't be afraid of having your changes
reviewed.
<li>Never remove copyright notices from the code
<li>Never remove licensing info from code
<li>Never commit code you didn't write yourself or code that doesn't
have a suitable license
<li>Follow the style conventions
<li>Keep an eye on performance considerations, especially for code in
core classes, ask on the list for guidance
<li>Do a regression test run and a bootstrapping build if making changes
to core functionality before committing. Do not commit code that would
break the compile, because that wastes everybody's time. Two things
Please do not commit code that would break the compile to the
CVS, because that normally wastes everybody's time. Two things
are important in this step: trying to build your sources and making
sure that you add all the new files before you do a commit.
</ul>
Also, remember to pat yourself on the back after the commit, smile and
think we're a step closer to a better free software world.
* Using CVS.
@@ -170,16 +61,14 @@
ssh-keygen -t rsa
</pre>
And mail <a href="mailto:[email protected]">miguel</a> the
id_rsa.pub file.
And mail me the id_rsa.pub file.
If you are using SSH version 1, run:
<pre>
ssh-keygen
</pre>
And mail <a href="mailto:[email protected]">miguel</a> your
identity.pub file.
And mail me your identity.pub file.
If you are using SSH from SSH Communications Security (they offer
a free SSH client for personal use), you have to use OpenSSH to
@@ -192,8 +81,7 @@
where the file id_XXX.pub is your public key file,
normally located under ~/.ssh/ or ~/.ssh2/.
Send to <a href="mailto:[email protected]">miguel</a> the
my_public_key.pub file.
Send to miguel the my_public_key.pub file.
The *exact* format for this file must be:
@@ -235,7 +123,7 @@
** Making patches
Usually you will want to make a patch to contribute, and let
other people review it before committing it. To obtain such a
other people review it before commiting it. To obtain such a
"patch", you type:
<pre>
@@ -244,96 +132,7 @@
mail [email protected] < file.diff
</pre>
** Committing your work
Once you get approval to commit to the CVS, or if you are
committing code that you are the maintainer of, you will want
to commit your code to CVS.
To do this, you have to "add" any new files that you created:
<pre>
cvs add new-file.cs
</pre>
And then commit your changes to the repository:
<pre>
cvs commit file-1.cs file-2.cs
</pre>
* Using SVN
This is a small tutorial for using SVN (subversion).
For a more complete tutorial on subversion, look at
<a href="http://svnbook.red-bean.com/">the svn book</a>
or <a href="http://subversion.tigris.org">the svn homepage</a>
** Generating a key
Follow the cvs instructions above.
** Checking out the sources
To checkout the sources for the first time use the command:
Note: You should be running 0.35.1 (latest) of svn before attempting
anything here.
<pre>
svn co svn+ssh://mono-cvs.ximian.com/svn/monodevelop/trunk/MonoDevelop
</pre>
If you have a different username on mono-cvs and the local computer
you can do the following:
<pre>
svn co svn+ssh://[email protected]/svn/monodevelop/trunk/MonoDevelop
</pre>
before checking out.
** Updating your sources
You can update your repository to the latest copy of MonoDevelop by
running the following command:
<pre>
svn up
</pre>
from inside your repository.
** Committing your work
Before you commit anything, you should first update to the latest
sources by following the updating directions. After you are up to date
you need to run a:
<pre>
svn add filename
</pre>
for every file that you have created. You can get a list of these files
by running:
<pre>
svn status
</pre>
After all the files are added, run:
<pre>
svn commit
</pre>
to commit your changes.
** For more information
Look at the MonoDevelop website (coming soon)
* Keeping track of changes.
** Keeping track of changes.
We provide two e-mail based mechanisms to keep track of
changes to the code base:
@@ -352,6 +151,28 @@
We hope to offer LXR and Bonsai in the future as well.
** Commiting your work
Once you get approval to commit to the CVS, or if you are
commiting code that you are the maintainer of, you will want
to commit your code to CVS.
To do this, you have to "add" any new files that you created:
<pre>
cvs add new-file.cs
</pre>
And then commit your changes to the repository:
<pre>
cvs commit file-1.cs file-2.cs
</pre>
* The Mailing Lists
To keep track of the various development and changes to the
CVS tree, you can subscribe to the [email protected].
To subscribe, send an email message to
[email protected] and in the body of the
message put `subscribe'.
@@ -364,3 +185,10 @@
the <a
href="mailto:[email protected]">[email protected]</a>
to receive the patches as they are checked into CVS.
** Recommendations
To build the sources, most of the type trying the `make' command
is enough. In some cases (the class libraries) we use nant, so
you need to run nant manually.
+11 -4
View File
@@ -5,29 +5,36 @@
Here is the status of the different assemblies:
<ul>
<li><a href="http://www.go-mono.com/class-status-corlib.html">corlib</a>: The core library.
<li><a href="http://www.go-mono.com/class-status-System.html">System</a>: Extra modules
<li><a href="http://www.go-mono.com/class-status-System.html">System</a>.
<li><a href="http://www.go-mono.com/class-status-System.Xml.html">System.Xml</a>.
<li><a
href="http://www.go-mono.com/class-status-System.Data.html">System.Data</a>:
Database access functionality (also check the <a href="ado-net.html">Mono ADO.NET status</a> pages).
<li><a href="http://www.go-mono.com/class-status-System.Drawing.html">System.Drawing</a>.
<li><a
href="http://www.go-mono.com/class-status-System.Web.html">System.Web</a>:
ASP.NET classes, also check the <a href="asp-net.html">Mono ASP.NET status pages</a>
<li><a href="http://www.go-mono.com/class-status-System.Web.Services.html">System.Web.Services</a>.
<li><a
href="http://www.go-mono.com/class-status-Microsoft.VisualBasic.html">Microsoft.VisualBasic</a>:
Support runtime for Visual Basic applications
<li><a
href="http://www.go-mono.com/class-status-System.Windows.Forms.html">Windows.Forms</a>:
there is also a <a
href="http://lists.ximian.com/mailman/listinfo/mono-winforms-list">mailing
list available</a>
<li><a href="http://www.go-mono.com/class-status-System.EnterpriseServices.html">EnterpriseServices</a>.
<li><a
href="http://www.go-mono.com/class-status-System.Runtime.Serialization.Formatters.Soap.html">System.Runtime.Serialization.Formatters.Soap</a>.
<li><a
href="http://www.go-mono.com/class-status-System.Security.html">System.Security</a>:
Xml Signature Security classes, also check the <a href="crypto.html">Cryptography status pages</a>
</ul>
+38 -25
View File
@@ -7,43 +7,56 @@
the code, making the source quite difficult to read. Furthermore,
multilingual documentation makes for significant additional text.
With these considerations in mind, Mono is using external XML files
for class documentation, rather than documenting the source
inline. The XML file format used is inspired by the XML format used
to document the ECMA APIs.
Several tools exist for managing, verifying, generating,
and updating class library documentation.
The documentation infrastructure is part of the `Monodoc'
module. Monodoc includes a graphical GUI browser and tools to
generate the initial stubbed XML document out of an assembly.
With these considerations in mind, Mono will use external XML files
for type documentation, rather than documenting the source inline.
Download `monodoc' to start producing documentation for your
application.
Several tools will be created for managing, verifying, generating,
and updating class library documentation, including:
<ul>
<li><a href="#monodoc">MonoDoc - A graphical documentation editor and viewer.</a></li>
<li><a href="#mkmaster">MkMaster - A command line tool to feed stub information to MonoDoc.</a></li>
<li><a href="#aspnet">An ASP.NET documentation editor.</a></li>
<li><a href="#xsltool">An xsl tool to convert monodoc xml to html documentation.</a></li>
</ul>
For instructions, read the monodoc/README file.
** XML Documentation Files and Formats
*** Monodoc XML
This XML is Mono's documentation format. Documentation and a DTD/Schema
for Monodoc XML is located in cvs and can be found <a href="http://go-mono.org/monodoc.dtd">here</a>.
This XML could be generated by MonoDoc or the ASP.NET client.
More about the XML format <a href="http://go-mono.org/monodoc-xml.html">here</a>.
** Documentation Tools
*** <a name="monodoc">MonoDoc</a>
A graphical documentation editor and viewer. Currently, MonoDoc
consists of a Qt# application and is in heavy development.
The MonoDoc system offers both a GUI client as well as a <a
href="http://www.go-mono.com:8080">Web-based interface</a> to
the documentation.
*** <a name="mkmaster">MkMaster</a>
This tool creates the Master.xml file that MonoDoc uses as a reference
for documentation generation. This is a reflection engine that is used
to gather metadata from assemblies and create an xml representation.
The GUI edition uses <a
href="http://gtk-sharp.sf.net">Gtk#</a> and the Web edition
uses Mono's ASP.NET implementation.
*** <a name="aspnet">ASP.NET</a>
This tool is planned.
<img src="images/Screenshot-Monodoc.png">
*** <a name="xsltool">An XSL converter</a>
This tool is planned. If someone wants to step forward and adopt this
project, it would be very helpful ;)
** Status and Roadmap
*** 16, September 2002
A preliminary version of MonoDoc is in Mono's cvs. It is under heavy development.
Once this is complete we will start documenting the API!
** Get Involved
Help us develop Mono's documentation tools! Subscribe to
<a href="http://lists.ximian.com/mailman/listinfo/mono-docs-list">mono-docs-list</a>
and wade right in.
Monodoc today also supports a GUI-based collaborative editing
system. You can now edit the documentation from the browser
and upload your contributions directly to the Mono site.
-235
View File
@@ -1,235 +0,0 @@
* Compiling Mono
This document describes how to compile and install Mono from
its source code. If you are only interested in running Mono,
you might want to install Mono from packages, which have been
tested.
The core of Mono is split in two components:
<ul>
* C components (available in the mono package)
* C# components (available in the mcs package).
</ul>
Mono is also available in various forms:
<dl>
<dt>Officially <a href="download.html">released</a> packages.</dt>
<dd>
<p>This is the format of choice for people to use, since these
have been tested and are known to build and work.
</dd>
<dt><a href="daily">Daily</a> packages.</dt>
<dd>
<p>This is a service offered for people who want to try out the
daily changes. Baked daily.</dd>
<dt>CVS source code.</dt>
<dd>
<p>These are available to Mono <a href="ccvs.html">developers</a> and
also for enthusiasts through <a href="anoncvs.html">anonymous CVS</a>.
</dd>
<dt>CVS snapshots.</dt>
<dd>
<p>Available for curious developers which do not necessarily want to
install the CVS source. Baked daily.
</dd>
</dl>
* Compiling the code
There are a number of ways of compiling Mono
<ul>
<li>From the <a href="#scripts">scripts</A>
<LI><a href="#install">Manually</a> for the first time.
<li>Manually, <a href="#upgrade">while upgrading</a> to CVS
</ul>
(which is an easy way to get the latest CVS information)
<a name="scripts">
* Compiling with scripts
These scripts should be used for installing from packages, specially
on Windows, where dependencies have not always been installed.
There are scripts to help build mono for both Unix and Windows. Get
<a href="mono-build.sh">mono-build.sh</a> for Unix, or <a
href="mono-build-w32.sh">mono-build-w32.sh</a> 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:
<ul>
* Save the script for your platform somewhere (e.g. /usr/local/bin)
* Make the script executable (i.e chmod 755 /usr/local/bin/mono-build.sh)
* Create a directory to hold the mono source, and the compiled binaries (e.g. mkdir ~/mono)
* Change to the new directory (i.e. cd ~/mono)
* run the script (i.e. /usr/local/bin/mono-build.sh)
</ul>
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. <b>IMPORTANT!:</b> The cvs server chosen defaults to
anonymous cvs;
set your CVSROOT environment variable before running the script to
select a particular cvs server.
<a name="install">
** Building the software manually
You will need to obtain the Mono dependencies first: <a
href="http://www.gtk.org">glib 2.x</a> and
<a href="http://www.freedesktop.org/software/pkgconfig">pkg-config</a>.
*** Building From Packages
This applies to both the officially released packages, as well as the
daily tarball packages.
<ul>
Unpack the Mono runtime distribution:
<pre class="shell">
tar xzvf mono-X.XX.tar.gz
cd mono-X.XX</pre>
<p>
Then configure, compile and install:
<pre class="shell">
./configure --prefix=/usr/local
make
make install</pre>
This will give you a runtime, C# compiler and runtime
libraries.
If you want to recompile the runtime and the compiler,
follow these steps, first unpack the MCS package:
<pre class="shell">
tar xzvf mcs-X.XX.tar.gz</pre>
Then use the following command to compile and install:
<pre class="shell">
./configure --profile=atomic
make</pre>
You can change /usr/local to something else if you want.
</ul>
*** Building from CVS
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 <a href="ccvs.html">Cvs and Mono</a> and the <A
href="anoncvs.html">AnonCVS and Mono</a> pages).
<pre>
(cd mono; cvs update -dP .)
(cd mcs; cvs update -dP .)
</pre>
Then you can run:
<pre>
(cd mono; make fullbuild)
</pre>
Now you can install the result:
<pre>
(cd mono; make install)
</pre>
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.
* Software resources and notes
The required and additional software can be downloaded here:
* Microsoft's .NET Framework SDK from
<a href="http://msdn.microsoft.com/downloads">
msdn.microsoft.com/downloads</a>.
* Cygwin and the GNU Make tools from
<a href="http://www.cygwin.com">www.cygwin.com</a>.
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 <a href="http://www.gimp.org/~tml/gimp/win32//index.html">GIMP for Windows</a> project from
<a href="http://www.go-mono.com/archive/pkgconfig-0.11-20020310.zip">http://www.go-mono.com/archive/pkgconfig-0.11-20020310.zip</a><br>
<a href="http://www.go-mono.com/archive/glib-2.0.4-20020703.zip">http://www.go-mono.com/archive/glib-2.0.4-20020703.zip</a> <br>
<a href="http://www.go-mono.com/archive/glib-dev-2.0.4-20020703.zip">http://www.go-mono.com/archive/glib-dev-2.0.4-20020703.zip</a> <br>
<a href="http://www.go-mono.com/archive/libiconv-1.7.zip">http://www.go-mono.com/archive/libiconv-1.7.zip</a> <br>
<a href="http://www.go-mono.com/archive/libiconv-dev-1.7.zip">http://www.go-mono.com/archive/libiconv-dev-1.7-20020101.zip</a> <br>
<a href="http://www.go-mono.com/archive/libintl-0.10.40-20020101.zip">http://www.go-mono.com/archive/libintl-0.10.40-20020101.zip</a><br>
* Download the Mono source code from the
<a href="download.html">packaged versions</a> or
the <a href="http://www.go-mono.com/snapshots">
nightly snapshots</a> or the <a href="anoncvs.html">
Anonymous CVS</a>. 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.
</ul>
*** Notes on compiling GLIB 2.0 and pkg-config from source:
<ul>
* Some people observed problems with autoconf 2.52. Installing
autoconf 2.13 helped in those cases (don't forget to do a
`make maintainer-clean' after the update).
* Download, compile and install <a href="http://www.freedesktop.org/software/pkgconfig">pkg-config</a> from source.
(I had to change line 674 of
<nobr><tt>pkg-config-0.8.0/glib-1.2.8/gstrfuncs.c</tt></nobr> from
<nobr><tt>extern char *strsignal (int sig);</tt></nobr> to
<nobr><tt>extern const char *strsignal (int sig);</tt></nobr>.
<pre class="shell">
tar xzvf pkg-config-0.8.0.tar.gz
cd pkg-config-0.8.0
./configure --prefix=/usr
make
make install
</pre>
* Download, compile and install <a href="ftp://ftp.gnu.org/pub/gnu/libiconv/libiconv-1.7.tar.gz">libiconv</a> from source.<br>
If you dont have MS Visual C/C++ 4.0 or 5.0 or 6.0 you can also try
the binary package available at <a
href="http://www.gimp.org/~tml/gimp/win32/libiconv-1.9.1.bin.woe32.zip">
http://www.gimp.org/~tml/gimp/win32/libiconv-1.9.1.bin.woe32.zip</a>
* Download, compile and install the
<a href="ftp://ftp.gtk.org/pub/gtk/v2.0/glib-2.0.6.tar.gz">
glib 2.0</a> from source.
</ul>
+1 -49
View File
@@ -16,8 +16,7 @@
the source code for Mono, you can start tracking down the
problem. Depending on how much time you have to devote to the
problem you could: <a href="http://bugzilla.ximian.com">File a
bug report</a> (read <a href="#goodbugreport">this</a>); track
down the problem and provide a better
bug report</a>; track down the problem and provide a better
<a href="http://bugzilla.ximian.com">bug report</a>; fix the
bug and provide a patch (you can <a
href="mailto:[email protected]">post it</a> to the <a
@@ -128,53 +127,6 @@
You can review the list of current bugs by going <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FClass+Libraries&product=Mono%2FMCS&product=Mono%2FRuntime&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&order=%27Importance%27&form_name=query">here</a>
Check our <a href="bugs.html">Bugs</a> that contains links to
easily add a bug report, or to query the existing bugs.
<a name="goodbugreport"/>
** How to make good bug reports
A mail from Paolo to mono-devel-list contained this check list:
<ol>
* Submit a test case, the smaller it is, the better
* Use <a href="http://bugzilla.ximian.com">
http://bugzilla.ximian.com</a> to report the bug.
<p>In <b>addition</b> to bugzilla, posting to the list is
fine if the bug merits larger exposure or design
discussions to solve; posting to the list twice or more
is just a way to annoy people and make them waste time,
specially when you start a new thread about it.
* If the test involves libraries or assemblies that are
not part of mono, add info about where to download all
the dependencies, and how to compile/install them.
* If compiling the test case requires more than:
<pre> mcs test.cs </pre>
provide the <b>full command line</b> you used to compile
the test.
* If running the test requires more than:
<pre> mono test.exe </pre>
provide the <b>full command line</b> needed to replicate
the bug.
* Provide info about the version of the software you're
using (both mono and the operating system or relevant
libraries).
* Provide the output you expect the test case to produce.
* Provide the actual output <b>you</b> get from the test case.
</ol>
A good bug report complies with at least 6 items from the list.
If your bug report complies with 3 or less items, it is very
poor and it means it will take much more time to fix (when it's
not ignored).
** Small tasks
A few smaller tasks are here, dropped in no particular order:
+123 -232
View File
@@ -11,41 +11,47 @@
**** Status
<ul>
* All classes are present.
* Every classes are present.
* Most classes have their unit tests. Some tests like <code>
SymmetricAlgorithmTest</code> are generated by external
tools.
SymmetricAlgorithmTest</code> are generated by an external
tool.
</ul>
**** TODO
<ul>
* Support for adding/modifying algorithms and OID using the
<code>machine.config</code> configuration file (in progress).
* RNGCryptoServiceProvider is currently only working on Linux.
The current implementation reside in Mono's runtime and use
the <code>/dev/[u]random</code> device (which do not exists
under Windows). A Windows alternative is in the work...
* Keypair persistance for RSA and DSA. This persistance must
somehow be linked with X509 certificate stores (in planning).
* <code>PasswordDeriveBytes.CryptDeriveKey</code> is included
in MS BCL to provide compatibility with existing Windows
applications. The main problem is that the key derivation
algorithm can be different for every CSP (Crypto Service
Provider). However for compatibility we should provide an
implementation compatible with the MS CSP (most likely used).
* <code>PasswordDeriveBytes</code> is currently limited to
generating keys with the maximum length equals to the hash
output (as specified in PKCS #5). However the framework
implementation allows for longer keys to be generated. Also
the algorithms used by CryptDeriveKey (used by Windows
applications) are unknown.
* Analyse the current coverage of the unit tests on the
cryptographic classes and complete the unit tests.
* Optimizations (performance) on most class are possible. Some
have been done using the Community Edition of BoundChecker
(a free VisualStudio addon) - recommanded!
</ul>
**** Notes
<ul>
* All cryptographic algorithms are entirely managed, including
classes named <code>*CryptoServiceProvider</code>, with the
exception of <code>RNGCryptoServiceProvider</code> for which
parts of the implementation resides in the runtime.
* There is a bug in the <code>PKCS1MaskGenerationMethod</code>
class (in both framework 1.0 and 1.1). This means our
implementation isn't compatible with MS (but is compatible with
PKCS#1 v.2.1). However we get OAEP padding for every platform!
* Look at assembly Mono.Security.Win32 if you require more
compatiblity with the Microsoft implementation (like accessing
a particuliar keypair container inside a specific CSP).
exception of <code>RNGCryptoServiceProvider</code> (which
resides in the runtime).
</ul>
@@ -53,41 +59,45 @@
**** Status
<ul>
* X.509 certificates are parsed using 100% managed code
(using the Mono.Security.ASN1 class).
* X.509 certificates are parsed using 100% managed code.
* Software Publisher Certificates (SPC) used by Authenticode
(tm) to sign assemblies are supported and <b>minimally</b>
validated.
(tm) to sign assemblies are supported (extraction from PE
files) but <b>not</b> validated.
* Unit tests are generated from a set of existing certificates
* Tests are generated from a set of existing certificates
(about a dozen) each having different properties. Another
set of certificates (more than 700) are used for a more
complete test (but isn't part of the standard test suite for
size and time consideration, i.e. a 7.5Mb C# source file).
set of certificates (more than 300) are used for a more
complete test (but isn't part of the test suite for size
and time consideration).
</ul>
**** TODO
<ul>
* Authenticode(tm) support is incomplete. We can extract the
certificates from PE files but cannot validate the signature
nor the certificate chain (and we're still missing some trust
anchors).
* Integration with CryptoAPI (on Windows) isn't possible as
long as the <code>X509Certificate(IntPtr)</code> constructor
isn't completed.
</ul>
**** Notes
<ul>
* Except for their structure <b>there are no validation of the
certificates</b> done by this class (this is by design and
isn't a restriction of Mono!). This means that certificate
signatures and validity dates are <b>never</b> checked
(except when used for Authenticode, i.e.
<code>CreateFromSignedFile</code>).
* <b>There's no validation of the certificates</b> done in this
class (this isn't a restriction of Mono!). This means that
certificate signatures and validity dates are <b>never</b>
checked!
* The newer X509Certificate class included in Microsoft's Web
Service Enhancement (WSE) is a little better (as it includes
CryptoAPI's validation) when <code>IsCurrent</code> is called.
See assembly <b>Microsoft.Web.Services</b> for more details.
* The class Mono.Security.X509.X509Certificate (in Mono.Security
assembly) is becoming a much better alternative - and will
continue to evolve to support the security tools.
* Microsoft implementation of <code>X509Certificate</code> is
done by using CryptoAPI (unmanaged code). Based on the
exceptions thrown, Authenticode(tm) support is done via COM.
done by using CryptoAPI. From the exceptions thrown
Authenticode(tm) support is done via COM.
</ul>
<hr>
@@ -101,125 +111,55 @@
**** Status
<ul>
* All classes are present but some Transforms are only stubbed.
* We now have a fully managed C14N implementation.
* All classes are present but some are only stubbed.
* Most classes have their unit tests.
* This assembly is present in CVS but only available when
building using NAnt (i.e. makefile are missing).
</ul>
**** TODO
<ul>
* Complete all Transform derived classes.
</ul>
* All the transforms needs to be done. But this requires far
more XML knowledge than crypto. Note: Most tests runs because
the feeded XML is pre-c14n (by hand in the code) before
signing (not because the transforms works).
<hr>
** Assembly: Mono.Security
<b>Rational: </b>
This assembly provides the missing pieces to .NET security. On Windows
CryptoAPI is often used to provide much needed functionalities (like
some cryptographic algorithms, code signing, X.509 certificates). Mono,
for platform independance, implements these functionalities in 100%
managed code.
*** Namespace: Mono.Security
<ul>
* Structures (ASN1, PKCS7) and primitives (PKCS1).
</ul>
*** Namespace: Mono.Security.Authenticode
<ul>
* Code signing and verification.
* Support for SPC (Software Publisher Certificate) files and
PVK (Private Key) files.
</ul>
*** Namespace: Mono.Security.Cryptography
<ul>
* Additional algorithms: MD2, MD4, ARCFOUR (required for SSL)
* Convertion helpers
</ul>
*** Namespace: Mono.Security.Protocol.*
<ul>
* Tls: An 100% managed TLS implementation from Carlos Guzman
Alvarez.
* Ntlm: NTLM authentication (used for HTTP and SQL Server).
</ul>
*** Namespace: Mono.Security.X509
<ul>
* X.509 structures (certificate, CRL...) building and decoding.
* PKCS#12 decoding.
</ul>
*** Namespace: Mono.Security.X509.Extensions
<ul>
* X.509 extensions (from public X.509 to private PKIX, Netsapce,
Microsoft, Entrust...).
</ul>
**** Status
<ul>
* A big part of this assembly is also included inside Mono's
corlib. The classes are duplicated in this assembly so the
functionalities can be used without a dependency on Mono's
corlib (which depends on Mono's runtime).
* Unit test coverage isn't (yet) complete.
* Makefile for building under non-Windows operating systems.
</ul>
<hr>
** Assembly: Mono.Security.Win32
<b>Rational: </b>
This assembly goal is to provide maximum compatibility with CryptoAPI
to application running with Mono's runtime on the Windows operating
system.
<b>This assembly should NEVER be used directly by any application</b>
(e.g. referecing the assembly from a project).
<b>This assembly should NEVER be used directly by any application</b>.
The classes should only be used by modifying the <code>machine.config
</code> configuration file (and then only if this increased
compatibility is required by an application).
See the file <code><a href="http://cvs.hispalinux.es/cgi-bin/cvsweb/~checkout~/mcs/class/Mono.Security.Win32/README?rev=1.1&content-type=text/plain&cvsroot=mono">/mcs/class/Mono.Security.Win32/README</a></code>
for complete instructions.
*** Namespace: Mono.Security.Cryptography
**** Status
<ul>
* A RNGCryptoServiceProvider built on top of CryptoAPI. This
allows Windows users to get around the limitation of the
runtime RNG (which requires <code>/dev/[u]random/</code>).
* A RNGCryptoServiceProvider built on top of CryptoAPI.
* Wrapper classes for unmanaged versions of hash algorithms:
MD2, MD4, MD5 and SHA1 are supported. <b>note</b>: some
algorithms shouldn't be used in new design (MD4 is broken,
MD2 and MD5 aren't considered safe for some usage). They are
included to preserve interoperability with older applications
(e.g. some old, but still valid, X.509 certificates use MD2,
MD4 is required for NTLM authentication ...).
* Not (yet) commited in CVS - i'm still playing with the base
classes so I can easily add other CryptoAPI-based algorithms.
</ul>
**** TODO
<ul>
* Wrapper classes for unmanaged versions of symmetric
encryption algorithms (like DES, TripleDES, RC2 and others
present in default CSP).
* Wrapper classes for unmanaged versions of asymmetric
algorithms (like DSA and RSA) which persist their keypair
into the specified CSP.
* Unmanaged versions of hash algorithms (SHA1 and MD5).
* Unmanaged versions of symmetric encryption algorithms
(like DES, TripleDES, RC2 and others present in CryptoAPI).
* Unmanaged versions of asymmetric algorithms (like DSA and
RSA) which persist their keypair into the specified CSP.
</ul>
**** Ideas
<ul>
* Similar assemblies (e.g. <code>Mono.Security.XXX</code>)
could be created for <a href="http://www.openssl.org">OpenSSL</a>,
<a href="http://www.mozilla.org/projects/security/pki/nss/">NSS</a>,
<a href="http://www.eskimo.com/~weidai/cryptlib.html">crypto++</a>,
<a href="http://www.cryptlib.orion.co.nz/">cryptlib</a> ... for
improved performance and/or HSM (Hardware Security Module) support
under Linux and/or Windows.
</ul>
<hr>
** Assembly: Microsoft.Web.Services
@@ -227,44 +167,30 @@
Development Kit (WSDK) in it's beta days, is an add-on the .NET
framework that implements WS-Security (and other WS-* specifications).
It also includes improved support for XML Signature (replacing and/or
extending <code>System.Security.Cryptography.Xml</code>) and X.509
certificates classes.
extending <code>System.Security.Cryptography.Xml</code>) and X509
certificates.
Note: WSE is distributed as an add-on because some specifications,
like WS-Security, aren't yet completed by
<a href="http://www.oasis-open.org/committees/wss/">OASIS</a> or
other committees.
Note: WSE is distributed as an add-on because the WS-Security
specification isn't yet completed by
<a href="http://www.oasis-open.org/committees/wss/">OASIS</a>.
<b>There are some licensing issues to consider before stating to
implement WS-Security. All contributors must sign an agreement with
Microsoft before commiting anything related to WS-Security into CVS.
</b>
*** Namespace: Microsoft.Web.Services.Security
**** Status
<ul>
* Most WSE 1.0 classes are implemented.
</ul>
**** TODO
<ul>
* Some classes from System.Security assembly need to be
duplicated (and somewhat fixed) in WSE for XMLDSIG.
* There are still missing classes and <b>many</b> missing
unit tests.
</ul>
*** Namespace: Microsoft.Web.Services.Timestamp
**** Status
<ul>
* This seems complete for WSE 1.0 but some new classes were
introduced in WSE 2.0.
* Nothing (yet) commited in CVS.
</ul>
*** Namespace: Microsoft.Web.Services.Security.X509
**** Status
<ul>
* X509Certificate support is complete for both WSE 1.0 and 2.0.
* Nothing (yet) commited in CVS.
</ul>
**** TODO
@@ -274,111 +200,76 @@
keypairs. This could also be used to store the SPC roots.
</ul>
*** Notes
<hr>
** Other stuff
There are other, not so visible, uses of cryptography both inside and
outside the class library - such as:
<ul>
* Microsoft has <a href="http://microsoft.com/downloads/details.aspx?FamilyId=21FB9B9A-C5F6-4C95-87B7-FC7AB49B3EDD&displaylang=en">released</a>
a technical preview of WSE 2. <b>Note that WSDK (the technical
preview of WSE) had A LOT of changes before it's initial
release!</b>
* SSL/TLS for secure communication (investigation under way).
* Assembly signing (and verification) using StrongNames.
* Assembly signing (and verification) using Authenticode(tm).
</ul>
<hr>
** Tools
*** Tools
There are many tools in the .NET framework that indirectly interacts
with some cryptographic classes. Mono will eventually need these tools.
Unless noted the tools should work on any CLR (tested with both Mono
and Microsoft).
**** Status
The following tools are complete (or mostly complete):
The following tools are complete:
<ul>
* <code>secutil</code> is a tool to extract certificates and
strongnames from assemblies in a format that can be easily
re-used in source code (C# or VB.NET syntax).
* <code>cert2spc</code> is a tool to transform multiple X.509
certificates and CRLs into a Software Publisher Certificate
(SPC) file - which is a long name for a simple PKCS#7 file.
* <code>makecert</code> to create X.509 test certificates that
can be used (once transformed in SPC) to sign assemblies. It's
now possible to generate SSL certificates for web servers.
* <code>sn</code> is a clone of the <code>sn</code> to manage
strongnames. Current version can create, convert, sign and
verify strongnames signatures. Some configuration options
are still missing.
* <code>signcode</code> and <code>chktrust</code> for signing
and validating Authenticode(tm) signatures on assemblies (or
any PE file) are now working (signature and timestamps) but
some options aren't yet supported.
certificates (a chain) into a Software Publisher Certificate
(SPC) - which is a long name for a simple PKCS#7 file.
</ul>
Somewhat usable, somewhat incomplete:
<ul>
* <code>certview</code> is a certificate viewer for
<code>System.Windows.Forms</code> (right now only working on
Windows), while <code>gcertview</code> is the same viewer
implemented for GTK# (working on both Windows and Linux).
* <code>monosn</code> is a clone of the <code>sn</code> to manage
strongnames. This tools is part of the runtime (not the class
library) and as such is written in C and won't run without Mono.
</ul>
**** TODO
The following tools are still missing or largely incomplete:
The following tools are still missing or incomplete:
<ul>
* <code>monosn</code> is a clone of the <code>sn</code> to manage
strongnames. This tools is part of the runtime (not the class
library) and as such is written in C.
* <code>signcode</code> and <code>chktrust</code> for signing
and validating Authenticode(tm) signatures on assemblies.
* <code>makecert</code> to create X.509 test certificates that
can be used (once transformed in SPC) to sign assemblies.
* Other tools like a, GUI-based, certificate manager...
</ul>
Note that many of the tools requires the class library and/or the
runtime to be ready for them. E.g. StrongName and Authenticode signatures
tools are of limited use until supported by the runtime.
runtime to be ready for them.
<hr>
** References
<ul>
* RSA Laboratories' <a href="http://www.rsasecurity.com/rsalabs/faq/index.html">
Frequently Asked Questions</a> About Today's Cryptography, Version 4.1
* Public-Key Cryptography Standards (<a href="http://www.rsasecurity.com/rsalabs/pkcs/index.html">
PKCS</a>)
* National Institute of Standards and Technology - Federal
Information Processing Standards <a href="http://csrc.nist.gov/publications/fips/index.html">
NIST FIPS</a>
</ul>
<hr>
<hr>
** How to Help
<ul>
* Complete any of the TODO (and feel good about it ;-).
Complete any of the TODO (and feel good about it ;-).
* Analyse the current coverage of the unit tests on the
cryptographic classes and complete the unit tests. <b><code>
monocov</code> does a great job at this! Now we just need to
complete the missing unit tests.</b>
Add missing unit tests to classes or methods.
* Optimization can also be done on most algorithms as crypto
is never fast enough. Some have been done using the
Community Edition of BoundChecker (a free VisualStudio
addon) - recommanded! Just be sure to test every optimization
(using the unit tests) carefully - it's so fast to break an
algorithm ;-).
Write some documentation on the cryptographic classes for MonkeyGuide
(as I'm not a good writer, at least in English, but you must be a good
reader if you got to this part).
* Write some documentation on the cryptographic classes for
<b>monodoc</b> as I'm not a very good writer (at least in English).
</ul>
Optimization can also be done on algorithms as crypto is never fast
enough. Just be sure to test every optimization (using the unit test)
carefully - it's so fast to break an algorithm ;-).
Contact Sebastien Pouliot (<a href="mailto:[email protected]">home</a>
, <a href="mailto:[email protected]">work</a>) if you need additional
informations about the status of the cryptographic classes.
Contact <a href="mailto:[email protected]">Sebastien Pouliot</a> if
you need additional informations about the status of the cryptographic
classes.
<hr>
Last reviewed: January 26, 2004 (post mono 0.29)
Last reviewed: January 19, 2003 (post mono 0.18)
+4 -197
View File
@@ -14,219 +14,26 @@
<ul>
* The development tools (compilers, assembler tools,
language reference, design time features): these
live in the `monodoc' CVS module.
language reference, design time features).
* Frequently Asked Question compilations.
* HOWTO documents.
* The Class Libraries (Both the original .NET class
libraries as well as the class libraries produced by
the project).
* The Class Libraries
* Tutorials on Mono and the specifics of running it
(The <a href="http://www.monohispano.org">Mono
Hispano</a> team has produced lots of <a
href="http://www.monohispano.org/tutoriales.php">tutorials
in spanish</a>
* Tutorials on Mono and the specifics of running it.
* A guide to Mono as compared to the Microsoft.NET
Framework SDK
</ul>
* Class Library documentation
** Class Library documentation
We are moving to a new setup for documenting the class libraries,
and you can read about it <a href="classlib-doc.html">here</a>.
There are two classes of documentation: free documentation for
existing .NET classes and documentation for the classes that
we have developed on top of .NET.
There is a large body of documentation that came from the ECMA
standarization effort that has been checked into CVS. It does
not contain everything Mono and .NET have, so they need to be
updated and augmented.
** Gtk# documentation
We also have a large body of class libraries that are specific
to Mono, for example the documentation for Gtk#.
We have checked in stub documentation for Gtk# into the CVS
repository (on gtk-sharp/doc) and we need volunteers to help
populate the documentation for it. Since Gtk# is a wrapper
for Gtk, plenty of documentation exists in the <a
href="http://developer.gnome.org/doc/API">Gnome developer
site</a>.
To get started:
You need to download Gtk# from the CVS repository. The module
name is `gtk-sharp'. You can obtain a copy from both the CVS
repository or the anonymous CVS repository.
To pull your copy type:
<pre>
cvs co gtk-sharp
</pre>
Documentation lives in gtk-sharp/doc/en. The "en" indicates the
English language, the first one we are targeting. We can later
do translations, but for now we are focusing on a single
language.
In that directory you will find the documentation organized by
namespaces. One directory per namespace. In the directories
you will find one XML file per class that needs to be
documented. The mission is to fill in the data with useful
information. Feel free to grab liberally information from the
Gtk documentation from:
<a href="http://developer.gnome.org/doc/API/">http://developer.gnome.org/doc/API/</a>
Of course, the API does not apply directly. It only applies at
a foundational level, so you can not really just copy and
paste. Summaries, and remarks sections can probably be lifted
with little or no effort.
Gtk# uses properties to represent get/set operations in the C
API, so you can also use some bits from there.
Most of the documentation contains already place holders for
text, we use the internationally approved phrase for this
purpose, `To be added'. So the quest is to remove all of the
"To be added" strings with information with resembles as closely
as possible the toolkit reality.
*** The pieces to be filled.
Summaries are one or two line descriptions of the element
(class, struct, interface, method, field, event, delegate), and
its used to render summary pages. So it has to be short.
The "remarks" section is used to describe in detail the element.
**** Tags.
As you document Gtk# you will have a number of tags that you can
use inside the summary and remarks sections, these are:
<pre>
&lt;para&gt; &lt;/para&gt;
</pre>
Used to separate paragraphs.
<pre>
&lt;paramref name="param_name"/&gt;
</pre>
Used to reference a formal parameter to a function.
<pre>
&lt;see cref="T:SomeTypeName"/&gt;
</pre>
Use this to reference a type, this will include an hyper
link to the page for type SomeTypeName.
For example, to reference "System.Enum", do:
<pre>
&lt;see cref="T:System.Enum"/&gt;
</pre>
<pre>
&lt;see cref="P:SomeTypeName.Property"/&gt;
</pre>
Use this to reference a property, this will include an hyper
link to the page for the property `Property' of type `SomeTypeName'.
For example, to reference the BaseType property in System.Type, do:
<pre>
&lt;see cref="P:System.Type.BaseType"/&gt;
</pre>
<pre>
&lt;see cref="M:SomeTypeName.Method(type,type)"/&gt;
</pre>
Use this to reference a method, this will include an hyper
link to the page for the method `Method' of type `SomeTypeName'.
For example, to reference the ToString method in System.Object, do:
<pre>
&lt;see cref="M:System.Object.ToString()"/&gt;
</pre>
<pre>
&lt;see langword="keyword"/&gt;
</pre>
Use this to link to a keyword in the C# language, for
example to link to `true', do:
<pre>
&lt;see langword="true"/&gt;
</pre>
<pre>
&lt;example&gt; ... &lt;/example&gt;
</pre>
Use example to insert an example. The example can
contain explanatory text and code.
<pre>
&lt;code lang="C#"&gt;.. &lt;/code&gt;
</pre>
Use this to provide a sample C# program, typically used
within the &lt;example&gt; tags.
When providing examples, try to provide a full example,
we would like to be able to have a button to compile and
run samples embedded into the documentation, or pop up
an editor to let the user play with the sample.
You can link to an example like this:
<pre>
&lt;code lang="C#" source="file.cs"&gt; &lt;/code&gt;
</pre>
<pre>
&lt;item&gt;
</pre>
<pre>
&lt;list type="bullet"&gt; &lt;/list&gt;
</pre>
Use this to create lists. Lists contains &lt;item&gt;
elements which have to contain &lt;term&gt; containers.
<pre>
&lt;list type="table"&gt; &lt;/lits&gt;
&lt;listheader&gt;
&lt;term&gt;YOUR FIRST COLUMN&lt;/term&gt;
&lt;description&gt;YOUR DESCRIPTION&lt;/description&gt;
&lt;/listheader&gt;
</pre>
For two-column tables. Inside use:
<pre>
&lt;item&gt;
&lt;term&gt;First&lt;/term&gt;
&lt;description&gt;First descritpion&lt;/description&gt;
&lt;/item&gt;
&lt;item&gt;
&lt;term&gt;Second&lt;/term&gt;
&lt;description&gt;Second descirption&lt;/description&gt;
&lt;/item&gt;
</pre>
** Words of warning.
A few words of warning and advice for class documentors:
A well-documented API can ease hours of frustration; as Mono
+351 -943
View File
File diff suppressed because it is too large. Load diff
-51
View File
@@ -1,51 +0,0 @@
* Drawing
Mono provides two mechanism to draw. The first exposes the
Microsoft System.Drawing API and the second exposes the <a
href="http://www.cairographics.org">Cairo</a> API.
* System.Drawing
The System.Drawing implementation in Mono is designed to be
compatible with the Microsoft API. The imaging model is very
similar to the PDF 1.4 composition-based imaging model.
Our implementation is a C# wrapper around the GDI+ C API (also
called the <a
href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/gdicpp/GDIPlus/GDIPlusReference.asp">"GDI+
Flat API"</a>).
This means that the C# code is the same for Windows and Unix
systems. The following graph explains the situation:
<center>
<img src="images/system-drawing.png">
</center>
In Windows Mono uses the GDI+ library that is included with
the operating system (<tt>GDIPLUS.DLL</tt>, while in Unix we
provide an implementation of this API in the
<tt>libgdiplus.so</tt> shared library. Our
<tt>libgdiplus.so</tt> has the same C Flat API as the
<tt>GDIPLUS.DLL</tt>. Our implementation uses Cairo to do
the heavy lifting.
The implementation of GDI+ lives in mcs/class/System.Drawing
in the gdiplus directory and requires <a
href="http://www.cairographics.org">Cairo</a> to be installed
to get the package built.
The C# code that implement System.Drawing is the same for
Windows and Unix builds.
Since this is an implementation of an existing Microsoft API
no architectural changes go here.
* Mono.Cairo
The Mono.Cairo.dll assembly exposes the Cairo API to managed
applications. The mapping is a pretty straightforward one,
and the programming model is very close to the C API.
This API is still unstable due to the nature of the underlying
API being used and will be revisited as Cairo evolves.
+2 -26
View File
@@ -68,20 +68,9 @@
not interfere with code in other domains. This is useful if
you want to host different applications in your program.
Now, it is necessary to transfer control to Mono, and setup
the threading infrastructure, you do this like this:
Then you can load an assembly containing code into the domain:
<pre>
void *user_data = NULL;
mono_runtime_exec_managed_code (domain, main_thread_handler, user_data);
</pre>
Where your main_thread_handler can load your assembly and execute it:
<pre>
static void main_thread_handler (gpointer user_data)
{
MonoAssembly *assembly;
assembly = mono_domain_assembly_open (domain, "file.dll");
@@ -118,11 +107,7 @@
The Boehm GC system needs to catch your calls to the pthreads
layer, so in each file where you use pthread.h you should
include the &lt;gc/gc.h&gt; file.
If you can not do this for any reasons, just remember that you
can not store pointers to Mono Objects on the stack, you can
store them safely in the heap, or in global variables though
include the <gc/gc.h> file.
* Exposing C code to the CIL universe
@@ -288,15 +273,6 @@
It may not be possible to manage exceptions in that case,
though. I need to think more about it.
** Threading issues
If your application creates threads on its own, and you want them to
be able to call code into the CIL universe with Mono, you have to
register the thread with Mono before issuing the call.
To do so, call the mono_thread_attach() function before you execute
any managed code from the thread
* Samples
See the sample programs in mono/sample/embed for examples of
+282 -560
View File
File diff suppressed because it is too large. Load diff
+84 -62
View File
@@ -1,36 +1,29 @@
* Firebird and Interbase Data Provider
<ul>
<li>ADO.NET Data Provider for Firebird and Interbase databases</li>
<li>Does not exist in Mono, but is a separate project</li>
<li>The <a href="http://firebird.sourceforge.net/index.php">Firebird Relational Database</a> is
is an independent project which uses source code based on the Interbase source code released
<li><a href="http://firebird.sourceforge.net/index.php">Firebird Relational Database</a> is
an independent project which uses source code based on the Interbase source code released
by Borland under the Interbase Public License</li>
<li>Both the Firebird Relational Database and the Firebird .NET Data Provider can be
downloaded from <a href="http://sourceforge.net/projects/firebird/">here</a></li>
<li>The Firebird .NET Data provider has been made
available by Carlos Guzmán Álvarez (aka "Carlos G.A."), who has also made a
number of contributions to the OdbcJdbc code</li>
<li>Bugs with Mono or the data provider should be reported
in Mono's Bugzilla <a href="http://bugzilla.ximian.com/">here</a>. If you
do not have Bugzilla user account, it is free
and easy to create one <a href="http://bugzilla.ximian.com/createaccount.cgi">here</a>.</li>
available by Carlos Guzmán Álvarez (aka "Carlos G.A."), who has also made a
number of contributions to the OdbcJdbc code</li>
</ul>
** Current Status
<ul>
<li>Current stable version: 1.0</li>
<li>Current developement version: 1.5</li>
<li>The new data provider/driver is written in C# and provides a high-performance native
<ul>
<li>Currently, it is able to connect to Firebird and Interbase databases
and execute commands</li>
<li>The new data
provider/driver is written in C# and provides a high-performance native
implementation of the GDS32/API functions. This means that .Net developers
will be able to access Firebird databases without the need of Firebird
client install</li>
@@ -38,54 +31,85 @@
<li>In support of the new module, a new mailing list
<a href="http://lists.sourceforge.net/lists/listinfo/firebird-net-provider">firebird-net-provider</a> has
been created. Please use this list for any
questions that you may have about the provider</li>
questions that you may have about the provider</li>
<li>Stuff that works:
<ul>
<li>Currently implemented classes:
<ul>
<li>Connection and Connection Pooling</li>
<li>Command</li>
<li>Transaction</li>
<li>CommandBuilder</li>
<li>DataAdapter</li>
<li>DataReader</li>
<li>Error</li>
<li>ErrorCollection</li>
<li>Exception</li>
<li>Parameter</li>
<li>ParameterCollection</li>
<li>Transaction</li>
</ul>
</li>
</ul>
</li>
</ul>
** New features & enhancements in 1.5 version
** Action Plan
<ul>
<li>Better fit to ADO.NET</li>
<li>New GDS implementation</li>
<li>Implicit transaction support</li>
<li>Array datatype support</li>
<li>Firebird services API support</li>
<li>Firebird events API support</li>
<li>Stored procedure calls using Sql Server style</li>
<li>Support for retrieve database schema information ( FbConnection.GetDbSchema )</li>
<li>Improved Commandbuilder implementation</li>
</ul>
<li>Bug fixing</li>
<li>Improving API reference documentation</li>
<li>Full testing with Firebird 1.5</li>
<li>Test with Mono ( http://www.go-mono.com )
<ul>
<li>Status : Started</li>
</ul>
</li>
<li>Support for array datatype
<ul>
<li>Status : Started</li>
<li>Comments: See Interbase API reference documentation</li>
<li>Add new file FbArray.cs for array fields management</li>
</ul>
</li>
<li>Support for Stored Procs calls that have returns values
<ul>
<li>Status : Pending.</li>
<li>Comments: Modify the isc_dsql_prepare method of GDS implementation for
allow to return the output parameters.</li>
</ul>
</li>
<li>Implementation of FbClientPermission and FbClientPermissionAttribute
<ul>
<li>Status : Pending</li>
<li>Comments: See if these are really needed for Firebird</li>
</ul>
</li>
<li>Improve Logger implementation
<ul>
<li>Status: Pending</li>
</ul>
</li>
</ul>
** Testing
<ul>
<li>Need a working mono and mcs</li>
<li>Need access to a Firebird Relational Database or you can download
it from <a href="http://firebird.sourceforge.net">here</a></li>
<li>Get the Firebird .NET data provider from here as
<a href="http://lists.sourceforge.net/lists/listinfo/firebird-net-provider">firebird-net-provider</a>. Make
sure the Firebird .NET data provider binary assembly FirebirdSql.Data.Firebird.dll is
installed in the same place as the mono class libraries.</li>
<li>Has a ConnectionString format:
<pre>
"Database=databasefile.gdb;User=user;Password=pass;Dialect=3;Server=hostname"
</pre>
</li>
<li>C# Example:
<li>C# Example for Mono's System.Data.OleDb:
<pre>
using System;
using System.Data;
@@ -95,21 +119,19 @@
{
public static void Main(string[] args)
{
string connectionString =
"Database=C:\\PROGRAM FILES\\FIREBIRD\\EXAMPLES\\EMPLOYEE.GDB;" +
"User=SYSDBA;" +
"Password=masterkey;" +
"Dialect=3;" +
"Server=localhost";
string connectionString =
"Database=C:\\PROGRAM FILES\\FIREBIRD\\EXAMPLES\\EMPLOYEE.GDB;" +
"User=SYSDBA;" +
"Password=masterkey;" +
"Dialect=3;" +
"Server=localhost";
IDbConnection dbcon = new FbConnection(connectionString);
dbcon.Open();
IDbCommand dbcmd = dbcon.CreateCommand();
string sql = "SELECT * FROM employee";
dbcmd.CommandText = sql;
dbcmd.ConnectionString = sql;
IDataReader reader = dbcmd.ExecuteReader();
while(reader.Read()) {
object dataValue = reader.GetValue(0);
object dataValue = myReader.GetValue(0);
string sValue = dataValue.ToString();
Console.WriteLine("Value: " + sValue);
}
-72
View File
@@ -1,72 +0,0 @@
* Novell Forge
Novell Forge (<a
href="http://forge.novell.com/">http://forge.novell.com/</a>)
is a website managed by Novell to promote the development of
open source applications and solutions. Novell Forge features
communities, akin to foundries on SourceForge.net, which exist
for the purpose of facilitating collaboration and information
exchange about certain technologies or solutions. At Miguel's
request, we have created a Mono community on Novell Forge that
is administered by Miguel. This community, located at
http://forge.novell.com/modules/xfmod/community/?monocomm,
provides a resource for interaction and collaboration on Mono
and associated solutions. Each community has the ability to
provide forums, mailing lists, FAQs, news, documentation,
surveys, sample code, and links to related applications. The
Mono community has been created for anyone interested in Mono
to use, and the exact set of features offered at the community
is determined by Miguel.
Any individual or group that wishes to provide Mono-based solutions in
an open source fashion is encouraged to host their solution on the
Novell Forge website, free of charge. Once the project is hosted on
Novell Forge, you can send Miguel an e-mail requesting that your project
be associated with the Mono project. This promotes a symbiotic
relationship where the growth of Mono applications helps to improve
Mono, and the growth of Mono likewise helps to increase the visibility
and usefulness of your applications.
* Creating an Account
A Novell Forge account is required in order to create a project on
Novell Forge as well as for certain levels of participation within a
community like the Mono community. In order to create an account, do
the following:
<ul>
<li>Go to http://forge.novell.com/ and click on the "Register" link.
<li>You will be redirected to the Novell Login page. This one resource
is used by all of Novell's websites that require authentication, so if
you already have a Novell login you may use that login here. Otherwise,
simply create a login account.
<li>You will be redirected back to the Novell Forge page. Click on the
"create my Novell Forge account" link, near the top left of the page.
<li>A form should be filled in with the correct information for you.
If you like, choose an avatar and then submit the form.
<li>Confirm the creation of your account.
</ul>
You should be good to go at this point. Now, to create a project,
simply choose the "Start New Project" link from the left menu and follow
the steps.
Novell Forge offers a limited set of context-sensitive help links and a
full help section. If you have trouble, go to the help section at
http://forge.novell.com/modules/xfmod/help/about.php.
* Important Links:
Novell Forge - <a href="http://forge.novell.com/">http://forge.novell.com/</a>
Mono Community - <a href="http://forge.novell.com/modules/xfmod/community/?monocomm">http://forge.novell.com/modules/xfmod/community/?monocomm</a>
Novell Forge Help - <a href="http://forge.novell.com/modules/xfmod/help/about.php">http://forge.novell.com/modules/xfmod/help/about.php</a>
+6 -4
View File
@@ -1,7 +1,9 @@
* The GCC front-end
Jeremy Singer has developed a .NET backend for GCC, his
research work is available <a
href="http://www.cl.cam.ac.uk/~jds31/research/gccnet/">here</a>.
The GCC front-end will accept input in a binary file with
codes in the Common Intermediate Language (CIL), and generate
native code.
This will allow pre-compilation and full optimization to take
place before a program is executed.
+12 -22
View File
@@ -6,31 +6,20 @@
libraries that are part of the
<a href="http://www.gnome.org">GNOME</a> platform .
* Wiki
There is a <a
href="http://www.nullenvoid.com/gtksharp/wiki/index.php/">Gtk#
Wiki</a>. You are encouraged to contribute to it.
** API of Gtk#
The Gtk# API is documented using the ECMA XML document format, you can read
more about it <a href="documentation.html">here</a>. You can
also use the MonoDoc tool that ships with Gtk# documentation.
The API is browsable
<a href="http://primates.ximian.com/~tvgm/gtk-sharp-docs/">here</a>
** Where to learn more.
Visit the official site for the <a href="http://gtk-sharp.sourceforge.net">Gtk# Project</a>.
The <a href="http://www.go-mono.org/faq.html">Mono FAQ</a> has some useful
The <a href="http://www.go-mono.org/faq">Mono FAQ</a> has some useful
information too.
** GTK# On Linux
<p>Where to get distributions of GTK# for Linux:
<ul>
<li><a href="http://gtk-sharp.sourceforge.net">RPMs</a></li>
<li><a href="http://www.debianplanet.org/mono/">Debs</a></li>
</ul>
<p>Where to get distributions of GTK# for Linux: TODO
<p>Buidling on Linux:
@@ -43,8 +32,7 @@
** GTK# On Windows
<p>Look at our Wiki for installation instructions <a href="http://www.nullenvoid.com/gtksharp/wiki/index.php/InstallingBeginnersGuide">here</a>
<p>There is a Windows Installer for GTK# <a href="http://www.sport-huettn.de/mono/gtk-sharp-0.6-stable-2.exe">here</a>.
<p>If you want to build GTK# yourself on Windows:
@@ -75,6 +63,11 @@ following:
<li>Microsoft .NET Framework at
<a href="http://msdn.microsoft.com/downloads/default.asp?url=/downloads/sample.asp?url=/msdn-files/027/000/976/msdncompositedoc.xml&frame=true">here</a> </li>
<p>If you are running Windows 95/98/ME, then you will need Unicode support.
Look in
mono-list archives for information about how to get
Mono to work on Windows 9x.
<a href="http://lists.ximian.com/archives/public/mono-list/2002-December/004158.html">here</a>
<p>Environment Variables to set:
<ul>
@@ -144,14 +137,11 @@ you will need to create them. Or get them from somewhere like the dev
packages at
<a href="http://www.gimp.org/~tml/gimp/win32/downloads.html">here</a>
** GTK# On FreeBSD
TODO. Any volunteers?
** GTK# On Solaris
TODO. Any volunteers?
TODO
** GTK# On AIX
TODO. Any volunteers?
TODO
-8
View File
@@ -13,14 +13,6 @@ Some of them may start contributing because they want a mention in the
* Mono Hackers
** Zoltan Varga
Zoltan has contributed significantly to Mono, with bug reports and bug
fixes as well as pushing the envelope of the things that can be done in
and with the mono runtime: the gcc-based ngen compiler, code coverage
and more recently his work with Reflection.Emit that got mono to the
point of running the IKVM Java virtual machine.
** Sergey Chaban
Sergey has been a long time contributor to the project, from the early
+7 -32
View File
@@ -1,24 +1,17 @@
* IBM DB2 Data Provider
<ul>
<li>ADO.NET Data Provider for <a href="http://www-3.ibm.com/software/data/db2/">IBM DB2 Universal Database</a></li>
<li>Exists in namespace DB2ClientCS and assembly Mono.Data.DB2Client</li>
<li>The source code exists at mcs/class/Mono.Data.DB2Client</li>
<li>Requires the Call Level Interface to IBM DB2 shared library. This
is db2cli.dll on Windows. The IBM DB2 CLI API is very similar to the ODBC API. If
you take a look at Mono's <a href="http://www.go-mono.com/odbc.html">System.Data.Odbc</a> ODBC provider, you will see the
you take a look at Mono's System.Data.Odbc ODBC provider, you will see the
DllImport's have similiar function names.</li>
<li><a href="http://www-3.ibm.com/software/data/db2/">IBM DB2 Universal Database</a> can be downloaded from IBM.</li>
<li>IBM DB2 Provider created by Christopher Bockner.</li>
<li>Bugs with Mono or the data provider should be reported
in Mono's Bugzilla <a href="http://bugzilla.ximian.com/">here</a>. If you
do not have Bugzilla user account, it is free
and easy to
create one <a href="http://bugzilla.ximian.com/createaccount.cgi">here</a>.</li>
</ul>
** Current Status
@@ -29,8 +22,6 @@
<li>Able to connect to IBM DB2</li>
<li>Able to execute DML, such as, CREATE TABLE via ExecuteNonQuery()</li>
<li>Christopher says it can retrieve data via the DB2ClientDataReader</li>
</ul>
@@ -49,29 +40,14 @@ In order to test.
<li>Have working mono and mcs setup</li>
<li>Have access to an IBM DB2 database. If you do not have access, download the
<a href="http://www-306.ibm.com/software/data/db2/">IBM DB2</a> software. There
<a href="http://www-3.ibm.com/software/data/db2/">IBM DB2</a> software. There
are versions for Windows, Linux, AIX, and Sun Solaris.</li>
<li>Make sure the assembly Mono.Data.DB2Client.dll was built and installed
where the other class libraries are installed.</li>
<li>If you do not have the source to mcs, get the source from
<a href="http://www.go-mono.com/download.html">here</a></li>
<li>Has a ConnectionString format like ODBC</li>
<li>Here is a ConnectionString format if you have a DSN setup:
<pre>
"DSN=dataSetName;UID=myuserid;PWD=mypassword"
</pre>
</li>
<li>Here is a ConnectionString format if you do not have a DSN (have not
gotten this to work though, so, I am open to suggestions):
<pre>
"DRIVER={DB2 Driver};SERVER=localhost;DATABASE=test;UID=myuserid;PASSWORD=mypassword"
</pre>
</li>
<a href="http://www.go-mono.com/download">here</a></li>
<li>In mcs/class/Mono.Data.DB2Client/Test/DBConnTest, you will find
a DBConnTest.cs.</li>
@@ -111,14 +87,13 @@ mono DBConnTest.exe database userid password
string connectionString =
"DSN=sample;UID=db2admin;PWD=mypass";
IDbConnection dbcon = new DB2ClientConnection(connectionString);
dbcon.Open();
IDbCommand dbcmd = dbcon.CreateCommand();
string sql =
"CREATE TABLE mono_db2_test1 ( " +
" testid varchar(2), " +
" testdesc varchar(16) " +
")";
dbcmd.CommandText = sql;
dbcmd.ConnectionString = sql;
dbcmd.ExecuteNonQuery();
dbcmd.Dispose();
dbcmd = null;
+43 -2
View File
@@ -15,13 +15,25 @@
<a name="runtime">
** Runtime
We need a verifier that can be run on an executable (assembly)
and tells whether the metadata for the executable is correct
or not. It should report any anomalies.
For a list of anomalies in assemblies, check the various assertions
that are described on the ECMA documentation.
This will help test our generated executables and can be also
used as an external verifier.
<a name="classes">
** Classes
<ul>
TODO=jxta,The JXTA Peer to Peer foundation
* Implement a JXTA protocol implementation:
<a href="http://www.jxta.org">http://www.jxta.org</a>
TODO=camel,Mail API
* Implement a Mail API, similar to Camel or JavaMail (Camel has
significant architecture features that are required on a real
mailer).
@@ -33,6 +45,7 @@
Such an implementation could be used both with
Microsoft .NET and Mono.
TODO=multimedia
* Interfacing to Multimedia systems. You might want
to look into the Quicktime API. I know <a
href="mailto:[email protected]">Vladimir</a> has
@@ -43,12 +56,40 @@
<a name="projects">
** Projects
This list of projects ideas is outdated
<ul>
TODO=xmlStorage,
* Implement an xmlStorageSystem for the CLI:
<a href="http://www.soapware.org/xmlStorageSystem">
http://www.soapware.org/xmlStorageSystem</a>
* Once <a href="http://remoting-corba.sourceforge.net/">CORBA</a> is done, implement the Bonobo interfaces
TODO=guavac,Java compiler for .NET
* You could take one of the existing Java compilers
(Guavac comes to mind as it is so nice) and modify
it to generate .NET code rather than JVM byte
codes.
This should be a pretty straightforward task.
Guavac has the advantage of being written in C++ and
it could be compiled with the Microsoft Managed C++
compiler and produce a .NET executable with it.
TODO=CORBA,CORBA implementation
* Build a CORBA interoperability engine for the CLR.
You do not need to do all of the work, just talking
the protocol will get us a long way (<a
href="http://www.omg.org">The OMG site</a> has the
CORBA specs).
Get in touch with David Taylor (dtaylo11 at bigpond
dot net dot au) as he has been working on this
project.
TODO=Bonobo,Bonobo for Mono
* Once CORBA is done, implement the Bonobo interfaces
to allow people to use Bonobo components in Mono and
Mono components with Bonobo. The best of both worlds!
TODO=moniker,Object Naming System with Monikers
* A naming space for Mono. An object naming space is
a very powerful tool. Bonobo implements a moniker
system that is more powerful than the original
+2004 -463
View File
File diff suppressed because it is too large. Load diff
+6 -52
View File
@@ -1,7 +1,7 @@
* Debugging information
Compile your programs using the `-g' flag in MCS, that will all a special
resource containing debugging information to your executable.
Compile your programs using the `-g' flag in MCS, that will generate a file
with the extension .dbg containing the dwarf symbols for your executable.
To get stack traces with line number information, you need to run your
program like this:
@@ -13,57 +13,11 @@
Notice that the program will need to be compiled with the -g
flag and that running with --debug will slow down the execution.
* Debugging with GDB
If you use GDB to debug your mono process, you can use the function
print_method_from_ip(void *address) to obtain the name of a method
given an address.
For example:
<pre>
(gdb) where
#0 ves_icall_System_String_GetHashCode (me=0x80795d0) at string-icalls.c:861
#1 0x0817f490 in ?? ()
#2 0x0817f42a in ?? ()
#3 0x0817f266 in ?? ()
#4 0x0817f1a5 in ?? ()
</pre>
You can now use:
<pre>
(gdb) p print_method_from_ip (0x0817f490)
IP 0x817f490 at offset 0x28 of method (wrapper managed-to-native) System.String:GetHashCode () (0x817f468 0x817f4a4)
$1 = void
(gdb) p print_method_from_ip (0x0817f42a)
IP 0x817f42a at offset 0x52 of method System.Collections.Hashtable:GetHash (object) (0x817f3d8 0x817f43b)
$2 = void
</pre>
* Mono Debugger
The Mono debugger is written in C# and can debug both managed
and unmanaged applications, support for multiple-threaded
applications and should be relatively easy to port to new
platforms.
A new debugger has been created in C# and using Gtk# for its
user interface, this will simplify the debugging of CLI applications.
Details of the release are available in <a
href="http://lists.ximian.com/archives/public/mono-list/2003-January/011415.html">post</a>.
The debugger contains both Gtk# and command line interfaces.
The debugging file format used in Dwarf (its already supported
by our class libraries and the Mono C# compiler; To debug C
applications, you need a recent GCC, or to pass the -gdwarf-2
flag to gcc).
Stay turned for its first public release.
The debugger is available now, you can get it from <a
href="http://primates.ximian.com/~martin/debugger/mono-debugger-0.2.0.tar.gz">here</a>
+86
View File
@@ -0,0 +1,86 @@
* A debugging session using a dynamically generated symbol file.
Let's assume we have the following C# application which we want to debug:
<pre>
using System;
public class Foo
{
public struct MyStruct {
int a;
long b;
double c;
}
public static void Main ()
{
Int32 value = 5;
long test = 512;
MyStruct my_struct;
my_struct.a = 5;
my_struct.b = test;
my_struct.c = 23323.5235;
}
}
</pre>
First of all, we need to compile it and create the .il files:
<pre>
$ mcs ./Foo.cs
$ monodis /home/export/martin/MONO-LINUX/lib/corlib.dll > corlib.il
$ monodis Foo.exe > Foo.il
</pre>
Now we can start the JIT in the debugger:
<pre>
$ gdb ~/monocvs/mono/mono/jit/mono
(gdb) r --debug=dwarf --break Foo:Main ./Foo.exe
Starting program: /home/martin/monocvs/mono/mono/jit/mono --debug=dwarf --break Foo:Main ./Foo.exe
0x081e8911 in ?? ()
(gdb) call mono_debug_make_symbols ()
(gdb) add-symbol-file /tmp/Foo.o
Reading symbols from /tmp/Foo.o...done.
Current language: auto; currently c++
(gdb) frame
#0 Foo.Main () at Foo.il:26
26 // method line 2
(gdb) n
Foo.Main () at Foo.il:38
38 IL_0000: ldc.i4.5
(gdb) list
33 .maxstack 2
34 .locals (
35 int32 V_0,
36 int64 V_1,
37 valuetype MyStruct V_2)
38 IL_0000: ldc.i4.5
39 IL_0001: stloc.0
40 IL_0002: ldc.i4 512
41 IL_0007: conv.i8
42 IL_0008: stloc.1
43 IL_0009: ldloca.s 2
44 IL_000b: ldc.i4.5
45 IL_000c: stfld int32 .MyStruct::a
46 IL_0011: ldloca.s 2
47 IL_0013: ldloc.1
48 IL_0014: stfld int64 .MyStruct::b
49 IL_0019: ldloca.s 2
50 IL_001b: ldc.r8 23323.5
51 IL_0024: stfld float64 .MyStruct::c
52 IL_0029: ret
(gdb) until 52
Foo.Main () at Foo.il:53
53 }
(gdb) info locals
V_0 = 5
V_1 = 512
V_2 = {a = 5, b = 512, c = 23323.523499999999}
</pre>
As you see in this example, you need to know IL code to use this debugging method - but
it may be the only way to debug a library.
+70
View File
@@ -0,0 +1,70 @@
* A debugging session using a symbol file which has been created by MCS.
Let's assume we have the following C# application which we want to debug:
<pre>
using System;
public class Foo
{
public struct MyStruct {
int a;
long b;
double c;
}
public static void Main ()
{
Int32 value = 5;
long test = 512;
MyStruct my_struct;
my_struct.a = 5;
my_struct.b = test;
my_struct.c = 23323.5235;
}
}
</pre>
First of all, we need to compile it with MCS, assemble the generated .s file and
create the .il files for all referenced assemblies which were not compiled with MCS:
<pre>
$ mcs -g ./Foo.cs
$ as -o Foo-debug.o Foo-debug.s
$ monodis /home/export/martin/MONO-LINUX/lib/corlib.dll > corlib.il
</pre>
Now we can start the JIT in the debugger:
<pre>
$ gdb ~/monocvs/mono/mono/jit/mono
(gdb) r --debug=dwarf-plus --break Foo:Main ./Foo.exe
Starting program: /home/martin/monocvs/mono/mono/jit/mono --debug=dwarf-plus --break Foo:Main ./Foo.exe
Program received signal SIGTRAP, Trace/breakpoint trap.
0x081e8681 in ?? ()
(gdb) call mono_debug_make_symbols ()
(gdb) add-symbol-file Foo-debug.o
(gdb) add-symbol-file /tmp/corlib.o
` (gdb) frame
#0 Main () at ./Foo.cs:11
11 public static void Main ()
(gdb) n
Main () at ./Foo.cs:13
13 Int32 value = 5;
(gdb)
14 long test = 512;
(gdb)
17 my_struct.a = 5;
(gdb)
18 my_struct.b = test;
(gdb)
19 my_struct.c = 23323.5235;
(gdb)
20 }
(gdb) info locals
value = 5
test = 512
my_struct = { a = 5, b = 512, c = 23323.5235 }
</pre>
+25 -45
View File
@@ -9,7 +9,6 @@
* <a href="#Oberon">Oberon</a>
* <a href="#Forth">Forth</a>
* <a href="#mbas">Mono Basic</a> (Mono's VB.NET compiler)
* <a href="#dotlist">dotLisp</a>
</ul>
Languages which are known to run, but we have not done a
@@ -31,22 +30,17 @@
<ul>
* <a href="#Tachy">Tachy</a> (scheme-like)
* <a href="#python">Python</a>
</ul>
<a name="Java"></a>
<a name="Java">
** Java
There is a very interesting project to make a JavaVM for .NET
<a href="http://radio.weblogs.com/0109845/">here</a>.
Currently this will not work with Mono, as they use some
pieces of Managed C++ to implement the JNI interface.
Zoltan has got IKVM to work with Mono.
<a name="PHP">
** PHP
Sterling has code to allow PHP developers to use Mono code, in
his <a href="http://www.php.net/~sterling/mono/">site</a>
A workaround has been discussed, contact the author if you want to contribute.
<a name="MonoLogo">
** MonoLogo
@@ -78,20 +72,24 @@
Examples:
<a href="http://www.oberon.ethz.ch/oberon.net/examples/">http://www.oberon.ethz.ch/oberon.net/examples/</a>
<a href="http://www.superin.formativ.net/mono/oberon/oberon.zip">http://www.superin.formativ.net/mono/oberon/oberon.zip</a>
<a name="ComponentPascal">
** Component Pascal
The Component Pascal compiler: <a
href="http://www.citi.qut.edu.au/research/plas/projects/cp_files/cpnet.html">Home
href="http://www2.fit.qut.edu.au/CompSci/PLAS/ComponentPascal">Home
Page</a>, you can <a
href="http://www.citi.qut.edu.au/research/plas/projects/cp_files/cpdownload.html">
href="http://www2.fit.qut.edu.au/CompSci/PLAS/ComponentPascal/gpcp1.1.4-netRTM.zip">
download it</a>
<a name="Forth">
** Delta Forth
The Delta Forth.NET project: <a href="http://www.dataman.ro/dforth">Home
Page</a> and <a href="http://www.dataman.ro/dforth">more
The Delta Forth.NET project: <a
href="www.dataman.ro/dforth">Home
Page</a> and <a href="http://www.dataman.ro/dforth/index.html">more
details here</a>.
@@ -101,26 +99,6 @@
A subset of Scheme language called <a
href="http://radio.weblogs.com/0101156/stories/2002/03/19/tachy.html">Tachy</a>
<a name="Python"></a>
** Python
<a href="mailto:[email protected]">Brian Lloyd</a> is
working on linking the Python runtime with the .NET runtime.
More information on the PS.NET project can be found <a
href="http://www.zope.org/Members/Brian/PythonNet">here</a>.
<a name="dotlisp"></a>
** dotLisp
DotLisp is available from: <a
href="http://sourceforge.net/projects/dotlisp/">http://sourceforge.net/projects/dotlisp/</a>
<a name="JavaScript">
* Java Script
Cesar is working on Mono's implementation of JScript, the code
is available on CVS on module `mcs'.
* Missing languages
Here is a list of a few languages that we would like to see
@@ -129,6 +107,19 @@
implementing or adapting a compiler for any of these
languages:
<a name="JavaScript">
* Java Script
The Mozilla project has an implementation of JavaScript
written in Java called <a
href="http://www.mozilla.org/rhino/">Rhino</a>.
You could port this code from Java to C#.
Note that since JavaScript allows for evaluation at runtime,
the compiler has to be built as a class that can be invoked at
runtime.
<a name="c">
* C
@@ -143,20 +134,9 @@
LCC is not an open source compiler, but it is free as long as you
do not profit from selling it.
<a name="ada"></a>
* ADA
A# is an ADA compiler for the CIL platform, it can be downloaded from:
<a
href="http://www.usafa.af.mil/dfcs/bios/mcc_html/a_sharp.html">http://www.usafa.af.mil/dfcs/bios/mcc_html/a_sharp.html</a>
<a name="Java">
* Java
Java bytecode can run directly on Mono using the <a
href="http://www.ikvm.net">IKVM</a> java virtual machine for
.NET.
We have a <a href="java.html">separate page</a> for Java.
+8 -68
View File
@@ -2,20 +2,11 @@
Most of the mailing lists are in english, but there is also
Mono Hispano that has lists in Spanish. <a
href="http://www.monohispano.org/mailman/listinfo/mono-hispano">Mono Hispano list</a>
href="http://mono.es.gnome.org/mailman/listinfo/mono-hispano">Mono Hispano list</a>
There are a number of mailing lists for Mono in English:
<table border=1>
<tr>
<td>
<b><a
href="http://lists.ximian.com/mailman/listinfo/mono-announce-list">mono-announce-list</a></b>
</td>
<td>
Announcements of Mono developments.
</td>
</tr>
<table>
<tr>
<td>
<b><a
@@ -28,39 +19,11 @@
<tr>
<td>
<b><a
href="http://lists.ximian.com/mailman/listinfo/mono-devel-list">mono-devel-list</a></b>
</td>
<td>
A mailing list specifically dedicated to discussions
about developing Mono and programming *with* Mono.
Programmers that work on Mono are _strongly_ encouraged
to join this list. Third-party programmers interested
in running or compiling their managed applications with
Mono or that are interested in using mono-specific
technologies should join the list as well.
<p>
Examples of on-topic arguments are:
<ul>
<li>proposals and patches for new features for the mono runtime and programs
<li>discussions about bugs in the mono runtime and programs
<li>discussions about future directions
<li>embedding API, scripting language bridges
<li>mono/mcs build issues
<li>programming with mono-specific assemblies
<li>discussions about third-party compilers that target and/or use directly the CLR
<li>discussions about getting a managed application run with mono
</ul>
<p>Topics that are better discussed on other mailing lists:
<ul>
<li> general C# questions (use the specific lists at develop.com)
<li> issues that are already covered by a more specific mono
mailing list (like System.Windows.Forms or Gtk#)
<li> success reports about new apps running on mono, including
runtime/buildtime support for new programming languages (use
mono-list to reach a wider audience)
</ul>
href="http://lists.ximian.com/mailman/listinfo/mono-announce-list">mono-announce-list</a></b>
</td>
<td>
Announcements of Mono developments.
</td>
</tr>
<tr>
<td>
@@ -77,7 +40,7 @@
href="http://lists.ximian.com/mailman/listinfo/mono-patches">mono-patches</a></b>
</td>
<td>
Track the CVS activity of Mono on this mailing list (patches are sent to recipients). <p>
Track the CVS activity of Mono on this mailing list (patches are sent to recipients).
You can get <a href="http://www.go-mono.com/snapshots">daily snapshots</a> as well.
</td>
</tr>
@@ -117,24 +80,6 @@
Used to discuss the Windows.Forms implementatation for Mono using Wine.
</td>
</tr>
<tr>
<td>
<b><a
href="http://lists.ximian.com/mailman/listinfo/gtk-sharp-list">gtk-sharp-list</a></b>
</td>
<td>
Used to discuss the Gtk bindings for Mono (<a href="http://gtk-sharp.sf.net">Gtk#</a>).
</td>
</tr>
<tr>
<td>
<b><a
href="http://lists.ximian.com/mailman/listinfo/mono-vb">mono-vb</a></b>
</td>
<td>
Mono's implementation of Visual Basic.NET.
</td>
</tr>
</table>
Other mailing lists of interest:
@@ -147,11 +92,6 @@
</ul>
</ul>
* Alternative archive site
An alternate site that archives Mono List is available <a
href="http://archive.neotonic.com/archive/mono-list">http://archive.neotonic.com/archive/mono-list</a>
* Google search of the archives
<!-- Google Search with mods -->
@@ -159,7 +99,7 @@
<table>
<tr>
<td><a href="http://www.google.com/search"><img src="images/Logo_40wht.gif" border="0" alt="Google" align="middle"></a></td>
<td><a href="http://www.google.com/search"><img src="mailing-lists_files/Logo_40wht.gif" border="0" alt="Google" align="middle"></a></td>
<td>
<table>
-91
View File
@@ -1,91 +0,0 @@
<html>
<head>
<title>Mono 1.0 assemblies</title>
</head>
<body>
<h1>Assemblies</h1>
<pre>
Stable:
Commons.RelaxNG
Cscompmgd
Mono.Data
Mono.Data.Tds
Mono.Posix
Mono.Security
Mono.Security.Win32
System.Web
System.Configuration.Install
System.Data
System.Data.OracleClient
System.DirectoryServices
System
System.Drawing
System.Runtime.Remoting
System.Security
System.Web.Services
System.XML
Unstable:
Accessibility
Mono.Cairo
Mono.CSharp.Debugger
Mono.Data.DB2Client
Mono.Data.SqlLite
Mono.Data.SybaseClient
Mono.GetOptions
System.Web.Mobile
System.Design
System.Drawing.Design
System.Windows.Forms
Formatters.Soap
Mono.Data.TdsClient (older Sybase and MS SQL)
Missing:
System.EnterpriseServices
System.Management
System.Messaging
System.ServiceProcess
System.Web.RegularExpressions
Third party assemblies.
ByteFX.Data
Npgsql
PEAPI
SharpZipLib.
Java integration with IKVM.NET
</pre>
<h1>Languages</h1>
<pre>
Stable:
C#
Unstable:
VB.NET
Not ready:
JScript
</pre>
<h1>Virtual Machine</h1>
<pre>
JIT, 32 bits:
PPC
x86
Interpreter, 32 bits:
s390
HPPA
StrongARM
SPARC v8
Interpreter, 64 bits:
ia64
SPARC v9
</body>
</html>
+13 -28
View File
@@ -59,13 +59,11 @@ else
echo "Automake version new enough."
fi
# This causes libgc-not-found problem
#
## Select the stable version anyway...
#if [ ! -z "${AUTO_STABLE}" -o -e /usr/autotool/stable ]; then
# export AUTO_STABLE=${AUTO_STABLE:-/usr/autotool/stable}
# export AUTO_DEVEL=${AUTO_STABLE}
#fi
# Select the stable version anyway...
if [ ! -z "${AUTO_STABLE}" -o -e /usr/autotool/stable ]; then
export AUTO_STABLE=${AUTO_STABLE:-/usr/autotool/stable}
export AUTO_DEVEL=${AUTO_STABLE}
fi
# Need to install pkgconfig and set ACLOCAL_FLAGS if there is not a
# pkgconfig installed already. Otherwise set PKG_CONFIG_PATH to the
@@ -100,15 +98,6 @@ function aclocal_scan () {
return 1
}
function install_icuconfig() {
if [ ! -f $here/install/bin/icu-config ]; then
wget http://www.go-mono.com/archive/icu-config
mv icu-config $here/install/bin
chmod 755 $here/install/bin/icu-config
fi
}
function install_package() {
zipfile=$1
markerfile=$2
@@ -134,13 +123,11 @@ else
install_pkgconfig=yes
fi
# This causes libgc-not-found problem
#
## But we still need to use the mingw libs for glib & co
#ACLOCAL_FLAGS="-I $here/install/share/aclocal $ACLOCAL_FLAGS"
# But we still need to use the mingw libs for glib & co
ACLOCAL_FLAGS="-I $here/install/share/aclocal $ACLOCAL_FLAGS"
#export PATH
#export ACLOCAL_FLAGS
export PATH
export ACLOCAL_FLAGS
# Grab pkg-config, glib etc
if [ ! -d $here/install ]; then
@@ -159,9 +146,6 @@ install_package glib-dev-2.0.4-20020703.zip lib/glib-2.0.lib glib-dev
install_package libiconv-1.7.zip lib/iconv.dll iconv
install_package libintl-0.10.40-20020101.zip lib/libintl-1.dll intl
install_package libgc-dev.zip lib/gc.dll gc-dev
install_package icu-2.6.1-Win32_msvc7.zip icu/bin/icuuc26.dll icu
install_icuconfig
if [ $install_pkgconfig = "no" ]; then
echo "Fixing up the pkgconfig paths"
@@ -174,9 +158,10 @@ if [ $install_pkgconfig = "no" ]; then
fi
# Needed to find the libgc bits
export CFLAGS="-I $here/install/include -I $here/install/icu/include"
export LDFLAGS="-L$here/install/lib -L$here/install/icu/lib"
export PATH="$here/install/icu/bin:$PATH"
CPPFLAGS="$CPPFLAGS -I$here/install/include"
LDFLAGS="$LDFLAGS -L$here/install/lib"
export CPPFLAGS
export LDFLAGS
# Make sure we build native w32, not cygwin
#CC="gcc -mno-cygwin"
+7 -29
View File
@@ -155,37 +155,15 @@ export PKG_CONFIG_PATH
# /usr/local/include and /usr/local/lib to CPPFLAGS and LDFLAGS. We could
# skip this if it would add /usr/include and /usr/lib, but leaving it
# shouldnt break anything.
#
# Actually, it does break stuff :-( gcc 3.2 prints gratuitous warnings
# and configure fails to find header files because of this cpp output.
iconvh=`locate include/iconv.h`
iconvh_dir=`dirname $iconvh`
iconvlib_dir=`echo $iconvh_dir | sed -e 's/include/lib/'`
if [ ! -f /usr/include/iconv.h ]; then
iconvdirs="/usr/local/include"
for i in $iconvdirs
do
if [ -f $i/iconv.h ]; then
iconvh_dir=$i
break
fi
done
if [ -z "$iconvh_dir" ]; then
echo "Can't find iconv headers (looked in $iconvdirs)"
exit -1
fi
iconvlib_dir=`echo $iconvh_dir | sed -e 's/include/lib/'`
echo "Adding $iconvh_dir to CPPFLAGS"
echo "Adding $iconvlib_dir to LDFLAGS"
CPPFLAGS="$CPPFLAGS -I$here/install/include -I$iconvh_dir"
LDFLAGS="$LDFLAGS -L$here/install/lib -L$iconvlib_dir"
else
CPPFLAGS="$CPPFLAGS -I$here/install/include"
LDFLAGS="$LDFLAGS -L$here/install/lib"
fi
echo "Adding $iconvh_dir to CPPFLAGS"
echo "Adding $iconvlib_dir to LDFLAGS"
CPPFLAGS="$CPPFLAGS -I$here/install/include -I$iconvh_dir"
LDFLAGS="$LDFLAGS -L$here/install/lib -L$iconvlib_dir"
export CPPFLAGS
export LDFLAGS
-271
View File
@@ -1,271 +0,0 @@
<html>
<head><title>Mono Hacking Roadmap</title>
<style type="text/css">
h1 {
color: #efefef;
font-size: 18pt;
font-family: "Trebuchet MS";
border: 0;
margin: 0;
padding: 1em;
background: #666666;
}
h2, h3, h4, h5, h6 {
font-family: Verdana,sans-serif;
font-weight: bold;
margin: 9pt;
}
h2, h3 {
font-size: 18px;
}
h2 {
padding: 3px;
color: #000000;
}
h3 {
font-size: 13px;
border-bottom: 2px solid #dddddd;
}
h4 {
border-bottom: 2px solid #dddddd;
}
body, table {
background-color: #ffffff;
font-family: Verdana, sans-serif; font-size: 12px;
color: black;
margin: 0;
padding: 0;
border: 0;
margin-left: 20%;
margin-right: 20%;
}
p {
margin-left: 2em;
margin-right: 2em;
}
ul li {
margin-left: 2em;
}
img {
border: 0;
vertical-align: top;
}
</style>
</head>
<body>
<center>
<h1>
Mono Hacking Roadmap
<br>
<font size=1>Miguel de Icaza (<a href="mailto:[email protected]">[email protected]</a>)</font>
</h1>
<p>
</center>
<h3>Introductory notes</h3>
<p>The intention of this document and the <a
href="http://www.go-mono.com/mono-roadmap.html">Mono
Roadmap</a> is to be a basis for discussion. I want to build
on these two documents, and update as we get more insight into
the release process and the technologies we want to ship.
<h3>Background</h3>
<p>At the 2003 PDC Microsoft introduced many new technologies,
which many of us are very excited about. To me, it underlined
the importance of having a roadmap for users of Mono
technologies. That way they know precisely what to expect
from us when. We have been working on Mono for more than two
years, and it is important that we release a stable product to
the public.
<p>We have various degrees of maturity and feature
completeness in our code base, and I do not believe that we
should aim to be full implementation .NET 1.0 or .NET 1.1 in
our 1.0 release, that would just push the release at least for
another year . The <a
href="http://www.go-mono.com/mono-roadmap.html">Mono
Roadmap</a> emphasizes this assumption.
<p>The 1.0 release is critical for the adoption of Mono on the
Linux environment, even if it is not as complete as the
Framework, lets get something stable, and fun to people to
use.
<h3>Mono 1.0: missing functionality.</h3>
<p>For the 1.0 release, there are a number of features that we
will have to complete, in no particular order:
<ul>
<li>We need to fix corcompare and our cor-compare
pages to support both 1.0 and 1.1 API API compares.
We might want to move this outside of the Mono site,
to reduce the complexity of the HTML hackage, and use
ASP.NET to implement this. Bonus points if we use
Piers' nice dynamic tree to load the CorCompare data
dynamically.
<li>Global Assembly Cache: Needed to support the
parallel installation of .NET 1.0 and 1.1 assemblies,
and to fix the various Assembly loading routines.
<li>PowerPC port.
<li>ECMA profile: We will like take care of this one
at Novell.
<li>Assembly signing: I do not know what is the state
of this feature currently in Mono, maybe Sebastien and
Zoltan could give us an update here.
<li>ASP.NET caching: Non-existant at this point, this
needs to be implemented.
<li>Stability of ASP.NET and Mod_Mono. They are both
functional, but they fail under load. Much debugging
and testing must go into these components. As we use
more of it, we have found more little problems surface
on it.
<li>Codebase audit: Duncan did an audit of Corlib, but
we must do an audit of all the assemblies that we we
are going to ship, just to get an idea of the major
areas missing.
</ul>
<p>The team at Novell will focus on these areas. We of course
welcomes the contribution of the rest of the Mono team and
encourage the developers to focus on 1.0, to have a solid
release, and a solid foundation that can lead to 1.2
<p>We will use Bugzilla milestones to track these issues.
<h3>Synchronized releases</h3>
<p>It would be great if we can ship Mono 1.0 with Gtk# 1.0 and
a preview of Monodoc with the early documentation.
<h3>Alpha components.</h3>
<p>Various Mono developers are working on areas that will not
make it into the 1.0 timeframe: JScript, WSE, VB.NET,
Windows.Forms, Generics. We should continue to work on
those components, as they will come shortly after, and they
are probably more fun to develop than stabilizing the core.
<h3>New components: Whidbey and Longhorn features</h3>
<p>Everyone is probably very excited about the new features in
the Whidbey release of .NET, and most importantly the Longhorn
features. I am sure that many of us will not resist the urge
to put some of the new assemblies on CVS.
<p>We will likely add a profile for those of you that want to
work on this, and can not wait to get your hands in the code,
although keep in mind that your contributions wont reach the
general audience until we successfully ship 1.0.
<p>The things to keep in mind while adding code which is not
in .NET 1.0 and .NET 1.1:
<ul>
<li>Make sure you surround new classes and methods
with the appropriate define: NET_1_2 for things
available on the .NET 1.2 SDK (Whidbey) and NET_3
define for things only available on the Longhorn API.
We need this so that these methods do not appear on
the 1.0 and 1.1 builds.
<li>If you add generic types or methods, also surround
the method with GENERICS for now, since our compiler
can not currently build this code yet. This is
redundant with the NET_1_2 define but important.
<li>For every assembly you update, make sure that you
also add the relevant AssemblyInfo versioning
information. If possible, when you add methods from
.NET 1.2 to the build, also update the AssemblyInfo.cs
for the library.
</ul>
<p>There are three areas of new hot features:
<ul>
<li>Class library improvements (Whidbey, Mono 1.2
time frames).
<li>Indigo: They will release this in 2005 or 2006 and
wont make it into the 2004 Whidbey .NET 1.2 release.
<li>Avalon: Definitely a Longhorn-bound feature.
</ul>
<p>Most code that will reach the users in the short time frame
(next year) will be related to the Whidbey improvements, so I
encourage developers to work on those pieces, as they are the
ones that will help Mono the most.
<h3>ASP.NET 2.0 plans</h3>
<p>Gonzalo will continue to coordinate this effort; At this
time ASP.NET 2.0 features will not make it into Mono 1.0.
<h3>Avalon plans</h3>
<p>On the surface Avalaon seems like it uses something like
GdiPlus/Cairo for rendering. That was my initial feeling, but
it turns out that they had to rewrite everything to have a
performing rendering engine, and implement some very advanced
rendering features that include compositing with video
streams, also their brushes seem to be fairly powerful.
<p>XAML, a new markup language that binds tags to .NET classes
was also presented, but this is the least interesting part. A
tiny compiler translates the XAML source files into C# code.
The whole process is just like Glade, and should be easy to
do.
<p>The really elaborate parts are the rendering engine, and the
composition model for widgets. It is a complete new toolkit,
and if we want to implement this one, we will have to have a
new toolkit on Unix, incompatible with everything else, maybe
stressing the importance of working with other open source
projects in defining a cross-toolkit theming strategy to
address this particular problem.
<p>A Mini-Avalon is easy to do, but a complete one will
require much interaction with other groups: the Cairo folks
are probably the most qualified to assist us.
<h3>Indigo Plans</h3>
<p>Indigo is still an early product (<a
href="http://msdn.microsoft.com/Longhorn/understanding/pillars/Indigo/default.aspx?pull=/library/en-us/dnlong/html/indigofaq1.asp">FAQ</a>),
but it could benefit from continued development of our WSE1
and WSE2 components, later to bring some of the code to it.
<p>Again, since people are visibly excited about this
technology, we will lay down in the next few days a framework
to contribute to it.
<p>
<i>Last Updated: Nov 1st, 2003</i>
</body>
</html>
-396
View File
@@ -1,396 +0,0 @@
<html>
<head><title>Mono Roadmap</title>
<style type="text/css">
h1 {
color: #efefef;
font-size: 18pt;
font-family: "Trebuchet MS";
border: 0;
margin: 0;
padding: 1em;
background: #666666;
}
h2, h3, h4, h5, h6 {
font-family: Verdana,sans-serif;
font-weight: bold;
margin: 9pt;
}
h2, h3 {
font-size: 18px;
}
h2 {
padding: 3px;
color: #000000;
}
h3 {
font-size: 13px;
border-bottom: 2px solid #dddddd;
}
h4 {
border-bottom: 2px solid #dddddd;
}
body, table {
background-color: #ffffff;
font-family: Verdana, sans-serif; font-size: 12px;
color: black;
margin: 0;
padding: 0;
border: 0;
margin-left: 20%;
margin-right: 20%;
}
p {
margin-left: 2em;
margin-right: 2em;
}
ul li {
margin-left: 2em;
}
img {
border: 0;
vertical-align: top;
}
</style>
</head>
<body>
<center>
<h1>
Mono Project Roadmap
<br>
<font size=1>Miguel de Icaza ([email protected])</font>
</h1>
<p>
</center>
<i>Last update: Jan 18th, 2004</i>
<h3>Introduction</h3>
<p>This document describes the high-level roadmap for <a
href="http://www.go-mono.com">Mono</a>.
<p>The Mono project started in 2001 as an effort to implement
the .NET Framework to Unix. To bring both the new programming
model based on the Common Language Infrastructure and C# as
well as helping people migrate their existing knowledge and
applications to Unix. Mono today supports a wide variety of
operating systems, CPUs and a large chunk of the functionality
available in the .NET Framework.
<p>At the October 2003 PDC conference a number of new
technologies were announced. From the Mono release schedule
perspective, we should think about these technologies from
their release time standpoint, and the features that must be
supported.
<p>This document outlines the roadmap for the Mono project
from my perspective: what we can effectively deliver on the
dates outlined. Since Mono is a large open source project,
things might change and new features can be incorporated
into the plan if external sources devote enough attention to
those problems.
<p>This is the timeline:
<p>
<center>
<img src="roadmap.png">
</center>
<h3>Background</h3>
<p>So far Microsoft has published two versions of the .NET
Framework: 1.0 and 1.1, the later with incremental updates to
the changes in 1.0
<p>The Mono project has been tracking some of the
improvements available in those two releases, some of the
highlights of our work so far are:
<ul>
<li> Core: mscorlib, System, System.Security and
System.XML assemblies.
<li> ADO.NET: System.Data and various other database
providers.
<li> ASP.NET: WebForms and Web Services are
supported. Work on WSE1/WSE2 has also started.
<li> Compilers: C#, VB.NET and various command line tools
that are part of the SDK.
<li> Open Source, Unix and Gnome specific libraries.
</ul>
<p>Other components like Windows.Forms, Directory.Services,
Enterprise Services and JScript are being developed but are not
as mature as the other components but are under development by
various people.
<p>Some other smaller and less used components do not have yet
a Mono equivalent (System.Management, System.Drawing.Design).
<h3>Mono release strategy</h3>
<p>The levels of maturity of Mono fluctuate depending on the
development effort we have put into it, and the use we have
given to them. For example, the virtual machine and the C#
compiler very mature, while less commonly used functionality
in Mono like Windows.Forms or VB.NET are still under heavy
development.
<p>Our strategy is to release the mature components as Mono
1.0, and have upcoming versions of Mono add extra
functionality.
<h3>Mono 1.0 goals</h3>
<p>The Mono 1.0 release would include the following
components:
<ul>
<li>C# compiler.
<li>VM, with JIT and pre-compiler.
<li>IL assembler, disassembler.
<li>Development and security tools.
<li>Core libraries: mscorlib, System, System.XML.
<li>System.Data and Mono database providers.
<li>System.Web: Web applications platform and Apache
integration module.
<li>System.Web.Services: client and server support.
<li>System.Drawing.
<li>System.DirectoryServices
<li>JIT support: x86 and PPC architectures
(interpreter available for other architectures).
<li>ECMA profiles: special build options to build
Mono as an implementation of the various ECMA profiles
will be available.
<li>Java integration through IKVM.
<li>Embedding interface for the runtime.
</ul>
<p>Packaging:
<ul>
<li>mono: will contain the above features implementing
the .NET 1.1 API.
<li>mono-1.0-compat: Will include a build of the
libraries with the .NET 1.0 API, this is a
compatibility build for people running .NET 1.0
applications.
<li>mono-unstable: Will contain a snapshot of the
other technologies under development for developer's
convenience, but will be unsupported at this time.
These include the Generics edition of the C#
compiler.
<li>mono-ecma: A build that only includes the ECMA
components.
</ul>
<p>Release target: Q2/2004.
<p>Bug fix releases would be done on a monthly basis.
<p>For a detailed list, see the <a
href="mono-1.0.html">mono-1.0 feature list.</a>
<h3>Microsoft's Whidbey</h3>
<p>To understand post 1.0 editions of Mono, it is important to
put it into perspective with the Microsoft Whidbey product, to
be released in 2004.
<p>The new features in the Whidbey release of the .NET Framework
include:
<ul>
<li><b>Generic types</b><br>
These introduce changes to the compiler, runtime and
class libraries.
<li><b>ASP.NET 2</b><br>
Many tools to simplify web application development:
Master pages, new controls for common operations,
personalization and themes.
<li><b>Remoting</b><br>
New security channels and version-resistant remoting
(good news in the interop department).
<li><b>XML</b><br>
XQuery debuts on this release as well as an improved
XmlDocument system based on XPath: XPathDocument.
<li><b>Networking</b><br>
FTP client, Ssl streams.
<li><b>Console and Serial ports:</b></br>
Console terminal input/output is available as well as
serial port handling.
<li><b>Windows.Forms</b><br>
Layout containers finally appeared on Windows.Forms as
well as various new controls.
<li><b>ObjectSpaces</b><br>
An API for simpler data-base access.
</ul>
<h3>Mono 1.2</h3>
<p>The Mono team is developing in parallel some features that
wont make it to the 1.0 release in stable form. These will be
the foundation for the 1.2 release. The focus of this release
is to track the core API for the .NET Framework 1.2, but
again, only a subset of the total framework will be
available.
<p>Mostly, Mono 1.2 consists of components that were not
stable enough for Mono 1.0, but that would be mature at this
point, plus the incorporation of some new features from
Whidbey. In addition to the Mono 1.0 components, this release
will add:
<ul>
<li>Generic types support: C# compiler, execution
system and core class libraries.
<li>ASP.NET 2.0 improvements.
<li>Remoting improvements from Whidbey.
<li>System.XML: simpler improvements from Whidbey,
lacking the large additions (XQuery for example).
<li>Console and Serial ports support.
<li>New compilers: VB.NET and JScript support.
<li>WSE1/WSE2 implementations.
<li>System.Windows.Forms officially debuts with .NET
1.0 API; 1.2 API available as an unstable addition.
</ul>
<p>This release will by default provide .NET 1.2 APIs, but
compatibility libraries for 1.0 and 1.1 will be distributed in
the mono-compat package. The unstable components of Mono will
be distributed on the `mono-unstable' package, the libraries
in this release will be unsupported.
<p>Release target: Q4/2004.
<h3>Mono 1.4</h3>
<p>A refresh update on the Mono 1.2 release containing the
missing components from the previous release and complete any
under performing pieces. Updates to System.Xml, ASP.NET and
Windows.Forms to match the .NET 1.2 API.
<p>Release target: Q2/2005.
<h3>Peer projects</h3>
<p>Other projects like the debugger, the documentation
browser, Java integration through IKVM and Gtk# will remain on
their own schedules. This page will be updated to contain
that information when it becomes available.
<h3>Unscheduled activities</h3>
<p>A missing component of Mono is the Code Access Security
(CAS). This functionality is not needed in today's Mono as
currently Mono is being used to run fully trusted
applications, and we are not using it on embedded scenarios
where assemblies would have different trust levels.
<p>This is an important component, but requires three major
pieces of work:
<ul>
<li>Runtime support for implementing the security
demands.
<li>A guidelines document outlining what and where
must have security demands in place.
<li>A full audit of our class libraries: method by
method
</ul>
<p>All of these are major pieces of work, and we currently
have no plans to implement any of those. A volunteer effort might be
able to help with the runtime requirements and the document,
but until those are done, we are unlikely to start doing any
work on the actual class library audit and instrumentation.
<h3>Mono and WinFX: 2006</h3>
<p>WinFX is the name given to the new set of libraries that
makes up .NET in the Longhorn operating system: the existing
.NET set of class libraries, plus the new functionality
available in the OS.
<p>WinFX adds things like storage facilities (WinFS), a
new versatile communications stack (Indigo) and a new
eye-candy packed GUI programming system (Avalon).
<p>Although WinFS, Avalon and Indigo are very exciting
components, at this time it is too early to tell when those
components will be available for Mono. Open source developers
will very likely start work on these, but since they are still
far from being officially released, they are not in the radar
at this point.
<h3>Unsupported technologies</h3>
<p>Some technologies are very hard to implement or are being
phased out by components in the Longhorn time frame. In some
cases, we feel that they are not crucial to the future of the
open source desktop.
<p>System.EnterpriseServices and System.Management come to
mind, and we are unlikely to put any resources into the task.
We would gladly host the code if someone cares to implement
it, but they would likely remain unsupported features of Mono.
<h3>Mono Developer Strategy</h3>
<p>Mono Developers should read the <a
href="mono-hacking-roadmap.html">Mono Hacking Roadmap</a>
<h3>Comments</h3>
<p>Feel free to send your comments or questions the roadmap to
<a href="mailto:[email protected]">[email protected]</a>
<p>
<i>Last Updated: Nov 1st, 2003</i>
-295
View File
@@ -1,295 +0,0 @@
* Mono hacking TODO list
From time to time people that want to contribute to Mono ask
on the mailing list what they can help with. The generic
answer is always:
<ul>
<li> Write documentation.
<li> Write regression tests.
<li> Complete the implementations of the class libraries.
<li> Help fix the bugs filed in our bugzilla database.
</ul>
The proposed tasks are very important for the Mono project and
are suitable for people that can dedicate even just an hour
per week to contribute. But some people may need something
more focused to work on, such as students that want to do a
thesis on their contribution to Mono. For such people (and
also for professors who want ideas for thesis regarding JIT or
VM technologies), here is a list of tasks that need attention.
The estimated time to complete any of the tasks is between 1
week to several months to accomodate for different hacking
possibilities.
Note on the time estimates: they are very rough estimates, a
smart and dedicated hacker can complete the tasks in half of
the minimum time, a part-time hacker that also has a social
life can take more than double the max time, but there's
nothing to worry as long as progress is being done.
If some people (or group of people) want to take on a task,
they should write to the mono-devel mailing list and in the
relative bugzilla bug report. Discussions about how to
implement a feature or additional information on the task
should be mailed to the list or in the bugzilla report as well
so that people can keep informed on the progress or have the
information needed to start contributing.
Mono is an excellent platform for research on JITs, virtual
machines and specifically the CLR because it provides an
advanced free software implementation that can be used as a
basis for more optimizations, new approaches to problems and
new features.
There are different areas of interest where high-level
contributions can be made:
<ul>
* <b>JIT compiler</b>: tasks can be: adding more optimizations, reducing
compile time, porting to different architectures.
* <b>AOT compiler</b>: optimizing the compiler output and the AOT loader,
better support for multiple application domains.
* <b>VM runtime</b>: optimizing the runtime data structures, experimenting with
different garbage collectors, integration with different component models.
* <b>Class library</b>: many opportunities in the implementation of regular
expressions, Xml related technologies (XPath, XLST, etc).
* <b>Compilers</b>: writing compilers, interpreters and runtimes for langauges
so that they run on the CLR (using Reflection.Emit support, for example).
</ul>
Happy hacking!
<table border=1 cellspacing="0" cellpadding="0">
<tr>
<th>Area<th>Description<th>Difficulty<th>Time estimate<th>Bugzilla ID
</tr>
<tr>
<td>Runtime (mono/metadata)
<td>Optimize method vtable. Currently all the methods in a class
are added to the method vtable, including static and non-virtual methods.
This makes vtables bigger and the instructions to access them are longer,
increasing also code size. Some code in metadata/icall.c and maybe also some
remoting code may depend on the current layout: such code should be fixed as well.
<td>Medium
<td>1-2 weeks
<td>not assigned
</tr>
<tr>
<td>System assembly (mcs/class/System/)
<td>Implement the IL-based regular expression engine. Instead of
intepreting the regular expression pattern, a method is created at runtime using
Reflection.Emit. This makes for faster pattern matching because there is no
intepreter overhead and the matching code is jitted to fast native code.
Bonus points if the compiled regular expression is compatible with the ones generated
by the MS runtime.
<td>Medium-hard (thesis subject)
<td>2-4 months
<td><a href="http://bugzilla.ximian.com/show_bug.cgi?id=52605">52605</a>
</tr>
<tr>
<td>JIT (mono/mini/)
<td>Implement common subexpression elimination.
Global and local common subexpression elimination needs to be implemented
to achieve better performance. The local case is easier and may take just one month.
It should be implemented in the context of the SSA framework (mini/ssa.c).
<td>Hard (thesis subject)
<td>2-4 months
<td>not assigned
</tr>
<tr>
<td>JIT (mono/mini/)
<td>Optimize AOT compiler output.
Currently the code generated by the AOT compiler may be significantly slower than
jitted code. This is mostly because the AOT code supports multiple application domains
and some values that are constant at JIT-time are not constant at AOT-time. It may be
needed to write a simple dynamic linker and/or binary object writer. Bonus poinst if
it supports ELF, PE/COFF and mach-O binary formats. A possible idea for improvements
is also the use of appdomain ID-indexed tables to get at the appdomain specific data.
<td>Medium-hard (thesis subject)
<td>3-6 months
<td>not assigned
</tr>
<tr>
<td>JIT (mono/mini/)
<td>Implement generics support.
We need to add support for the additional instructions and change existing ones to
support the generics requirements.
<td>Medium-hard
<td>2-3 months
<td>lupus and Martin
</tr>
<tr>
<td>JIT (mono/mini/)
<td>Port the JIT to additional architectures.
Currently ports are in the works for mips, arm, sparc, s390. None of the ports
are as feature-complete as the x86 one, yet, so help is needed in getting them
up to speed. Ports to more architectures are welcome as well.
<td>Medium-hard
<td>3-6 months per arch
<td>not assigned
</tr>
<tr>
<td>Runtime and JIT (mono/metadata and mono/mini/)
<td>Add support for COM and/or XPCOM and/or ORBit.
We need a way to seamlessy use existing component technologies inside the mono runtime.
The COM support needs to match the MS runtime behaviour and is targeted at windows systems.
XPCOM and ORBit support are important on Unix platforms. Bonus points for developing
the runtime support so that different component systems can be used at the same time.
<td>Medium-hard (thesis subject)
<td>3-4 months for each
<td>not assigned
</tr>
<tr>
<td>Runtime and JIT (mono/metadata and mono/mini/)
<td>Implement support for Code Access Security.
Support needs to be added to the JIT and the runtime to ensure
code that executes privileged operations is permitted to do so.
The task includes loading the security information from metadata,
collecting evidence, inserting calls to the permission objects,
stack walking to collect security info.
<td>Medium-hard (thesis subject)
<td>4-5 months
<td><a href="http://bugzilla.ximian.com/show_bug.cgi?id=52606">52606</a>
</tr>
<tr>
<td>Runtime and JIT (mono/metadata and mono/mini/)
<td>Implement support for a generational GC.
We're currently using a conservative non-moving GC.
Support for a generational and moving GC requires changes to the JIT
(to record locations in frames as well as registers that may contain
pointers to GC-allocated memory) and to the runtime code (when
objects are manipulated directly we should make sure they are pinned
and reachable by the GC also in the C unmanaged code). Code from an existing
precise GC such as the ORP one could be reused or a new GC may be developed
(increasing the estimated development time).
<td>Hard (thesis subject)
<td>6-8 months
<td>not assigned
</tr>
<tr>
<td>Compilers for dynamic languages
<td>Write a IL compiler and runtime support for dynamic languages like
Python, Perl, Ruby, PHP.
<td>Medium-hard (thesis subject)
<td>6-12 months
<td>not assigned
</tr>
<tr>
<td>Tools
<td>Write an implementation of the MSBuild compilation tool available in .NET 1.2
<td>Medium
<td>4-6 months
<td>not assigned
</tr>
<tr>
<td>Build tools.
<td>Currently it is easy for people doing daily
updates from CVS to break their installation. Design a mechanism by
which Mono never fails to compile.
<td>Easy
<td>1-2 weeks
<td>not assigned
</tr>
<tr>
<td>Documentation.
<td>Editorial review of the Monkeyguide: The monkeyguide is known to contain outdated
statements, it needs to be reviewed and it needs an
editor to take control over it. Some simple tasks
include flattening out the Monkeyguide, since it is
too nested today.
<td>Easy
<td>Ongoing work.
<td>not assigned
</tr>
<tr>
<td>Documentation
<td>GNOME.NET Chapter should probably be separated
from the Monkeyguide. This is probably the most
complete chapter, but it is burried in various nested
levels of stuff, and because of this, it is not being
updated. Write a chapter on custom control
authoring and common patterns of app development.
<td>Easy
<td>Ongoing work.
<td>not assigned
</tr>
<tr>
<td>Documentation Tools
<td>The Monodoc collaborative service needs a better
administration tool than it has today; Someone needs
to redo the UI and streamline its process.
<td>Easy
<td>2-3 months.
<td>not assigned
</tr>
<tr>
<td>Comment Service API
<td>Design a full system for comments and ratings so
people can annotate the documentation in Monodoc.
<td>Easy
<td>2-3 months.
<td>not assigned
</tr>
<tr>
<td>POSIX bindings.
<td>The Mono.POSIX assembly is a project to create a binding to
the various low-level calls in Unix which are not available
thought he regular assemblies in .NET.
The work should be done in two steps: one step is doing the
low-level binding for the system call, and another possibly is
to expose .NET-level objects like Streams for common patterns:
for example Streams for socketpairs.
<ul>
<li>Complete the bindings for all POSIX calls.
<li>Design a glue layer, because the various low-level
structures and values differ from operating system to
operating system, so we must do the translation from
our own set of definitions to the OS definitions.
The details are availble on bug <a
href="http://bugzilla.ximian.com/show_bug.cgi?id=51849">51849</a>
for details.
</ul>
<td>Medium
<td>2-3 months + QA.
<td>not assigned
</tr>
<tr>
<td>System.Drawing CODECs
<td>Complete the JPEG and PNG codecs to be fully
finished; Implement EXIF data loading; Implement the missing image codecs.
<td>Medium
<td>2-3 months.
<td>not assigned
</tr>
<tr>
<td>System.Data updates
<td>.NET 1.2 introduced many new updates to the
System.Data namespace: MARS and ObjectSpaces are the
big ones.
<td>Medium
<td>6-9 months.
<td>Work with the mono-devel-list to keep track of things.
</tr>
</table>
+163 -222
View File
@@ -1,237 +1,74 @@
* MySQL Data Provider
<p>There are two ADO.NET providers in Mono
for a <a href="http://www.mysql.com/">MySQL</a> database:
<ul>
<li><a href="http://sourceforge.net/projects/mysqlnet/">ByteFX.Data.MySQLClient</a>
<ul>
<li>Written in 100% C#</li>
<li>Does not require a client library</li>
<li>Works on Mono and Microsoft .NET</li>
<li>Requires at least Mono 0.18 and MySQLNet 0.65 for it to work on Mono</li>
<li>Works in the SQL# command-line and GTK# GUI version</li>
</ul>
</li>
<li>MySQL Data Provider for
<a href="http://www.mysql.com/">MySQL</a> databases. It is written in C# and uses
the MySQL C Client Library</li>
<li>Mono.Data.MySql (deprecated)
<ul>
<li>Deprecated in favor of ByteFX.Data.MySQLClient
<li>Written in C# and uses
the MySQL C Client Library</li>
<li>Exists in namespace Mono.Data.MySql and assembly Mono.Data.MySql</li>
<li>Exists in namespace Mono.Data.MySql and assembly Mono.Data.MySql</li>
<li>Works on Windows and Linux via the MySQL client shared library
(libmySQL.dll on Windows and libmysqlclient.so on Linux).</li>
<li>Works on Windows and Linux via the MySQL client shared library
(libmySQL.dll on Windows and libmysqlclient.so on Linux).</li>
<li>Started by Daniel Morgan using
<a href="http://www.cybercom.net/~zbrad/DotNet/MySql/">C# Bindings to MySQL</a> from <a href="mailto:[email protected]">Brad Merill</a></li>
<li>Started by Daniel Morgan using
<a href="http://www.cybercom.net/~zbrad/DotNet/MySql/">C# Bindings to MySQL</a> from <a href="mailto:[email protected]">Brad Merill</a>
<li><a href="http://www.mysql.com/articles/dotnet/">Exploring MySQL in the Microsoft .NET Environment</a> is an article
by Mr. Venu who is a MySQL AB developer.</li>
<li>There is a good alternative to the provider in Mono:
<ul>
<li><a href="http://sourceforge.net/projects/mysqlnet/">MySQLNet</a> from ByteFX
is a MySQL Managed provider written in 100% C#,
does not require a client library, and works on Microsoft .NET and Mono. You
need at least Mono 0.18 and MySQLNet 0.65 for it to work on Mono.</li>
</ul>
</li>
<li>Bugs with Mono or the data provider should be reported
in Mono's Bugzilla <a href="http://bugzilla.ximian.com/">here</a>. If you
do not have Bugzilla user account, it is free
and easy to
create one <a href="http://bugzilla.ximian.com/createaccount.cgi">here</a>.</li>
</li>
<li>Testing for Mono's Mono.Data.MySql and ByteFX's ByteFX.Data.MySQLClient is below...</li>
</ul>
<p><a href="http://www.mysql.com/articles/dotnet/">Exploring MySQL
in the Microsoft .NET Environment</a> is an article
by Mr. Venu who is a MySQL AB developer.</li>
<p>Testing for Mono's Mono.Data.MySql and ByteFX's ByteFX.Data.MySqlClient is below.
** Current Status
Current Status of the MySQL providers:
<ul>
<li>ByteFX.Data.MySqlClient
<ul>
<li>Build and Runs on Microsoft .NET and Mono</li>
<li>Works with SQL# (command-line and GTK# GUI versions)</li>
<li>MySQLCommandBuilder now implemented</li>
<li>Transaction support now implemented (not all table types support this)</li>
<li>GetSchemaTable fixed to not use xsd (for Mono)</li>
<li>Driver is now Mono-compatible</li>
<li>TIME data type now supported</li>
<li>More work to improve Timestamp data type handling</li>
<li>Changed signatures of all classes to match corresponding SqlClient classes</li>
<li>Protocol compression using <a href="http://www.icsharpcode.net/OpenSource/SharpZipLib/default.asp">SharpZipLib</a></li>
<li>Named pipes on Windows now working properly</li>
<li>Work done to improve Timestamp data type handling</li>
<li>Implemented IEnumerable on DataReader so DataGrid would work</li>
<li>Speed increased dramatically by removing bugging network sync code</li>
<li>Driver no longer buffers rows of data (more ADO.Net compliant)</li>
<li>Conversion bugs related to TIMESTAMP and DATETIME fields fixed</li>
</ul>
</li>
<li>can connect
<li>Mono.Data.MySql (deprecated)
<ul>
<li>Currently, only works with version 3.23.x of MySQL</li>
<li>can execute non-queries via ExecuteNonQuery()
<li>can execute aggregates via ExecuteScalar() and retrieve the
single row/single column result
<li>can execute queries and retrieve results using a data reader.
<li>a schema DataTable has been partially
implemented which is returned from GetSchemaTable() in MySqlDataReader.
<li>a DataTable in a DataSet can be filled via a MySqlDataAdapter
<li>can connect</li>
<li>can execute non-queries via ExecuteNonQuery()</li>
<li>can execute aggregates via ExecuteScalar() and retrieve the
single row/single column result</li>
<li>can execute queries and retrieve results using a data reader.</li>
<li>a schema DataTable has been partially
implemented which is returned from GetSchemaTable() in MySqlDataReader.</li>
<li>a DataTable in a DataSet can be filled via a MySqlDataAdapter</li>
<li>The shared client libraries
between windows version and linux are different: windows has libmySQL.dll
while linux has libmysqlclient.so. This is handled by the
file etc/mono/config which is mapped by the mono runtime in knowing
which native shared library to load. In cvs, this file is mono/config.in and
can be modified with a text editor.</li>
<li>Works in the SQL# command-line and GTK# GUI version</li>
</ul>
</li>
<li>The shared client libraries
between windows version and linux are different: windows has libmySQL.dll
while linux has libmysqlclient.so. This is handled by the
file etc/mono/config which is mapped by the mono runtime in knowing
which native shared library to load. In cvs, this file is mono/config.in and
can be modified with a text editor.
</ul>
** Action plan
The current plan for the MySQL data providers:
<ul>
<li>ByteFX.Data.MySqlClient
<ul>
<li>Testing and fixes</li>
<li>Implement missing features</li>
<li>Only fixes for bugs to build and run MySQLClient on Mono
will be accepted in mono-cvs. Most bugs and any new features will
go into sourceforge cvs. Anytime there is a release of MySQLClient,
the source code will be copied from sourceforge cvs to mono-cvs</li>
<li>Releases of MySQLClient are determined by Reggie Burnett and releases
of Mono are determined by Miguel de Icaza</li>
<li>Implement any missing features or fix any bugs in Mono to get new
features all of MySQLClient to work on Mono</li>
</ul>
</li>
<li>Mono.Data.MySql (deprecated)
<ul>
<li>Testing and bug fixes</li>
<li>Mono.Data.MySql is deprecated and therefore maybe removed
at a later date. It will stay in Mono for now because other
programs maybe using it now.</li>
</ul>
</li>
</ul>
** Testing for MySQLNet provider (ByteFX.Data.MySQLClient)
<ul>
<li>Have access to a MySQL database or download it from
<ul>
<li><a href="http://www.mysql.com/downloads/index.html">MySQL AB</a></li>
</ul>
</li>
The current plan to work on the MySQL data provider:
<li>MySQLNet can be gotten from <a href="http://sourceforge.net/projects/mysqlnet/">here</a> and the
binary assembly ByteFX.Data.dll needs to be installed
in the same place as the mono class libraries.</li>
<li>MySQLNet requires <a href="http://www.icsharpcode.net/OpenSource/SharpZipLib/default.asp">SharpZipLib</a> which is
a Zip Library written in 100% C#. This is used for compression/decompression of data
sent/received over the network. The SharpZipLib binary assembly SharpZipLib.dll should
be installed in the same place as the mono class libraries.</li>
<li>Has a ConnectionString format:
<pre>
"Server=hostname;" +
"Database=database;" +
"User ID=username;" +
"Password=password"
</pre>
</li>
<li>C# Example:
<pre>
using System;
using System.Data;
using ByteFX.Data.MySqlClient;
public class Test
{
public static void Main(string[] args)
{
string connectionString =
"Server=localhost;" +
"Database=test;" +
"User ID=myuserid;" +
"Password=mypassword;";
IDbConnection dbcon;
dbcon = new MySqlConnection(connectionString);
dbcon.Open();
IDbCommand dbcmd = dbcon.CreateCommand();
// requires a table to be created named employee
// with columns firstname and lastname
// such as,
// CREATE TABLE employee (
// firstname varchar(32),
// lastname varchar(32));
string sql =
"SELECT firstname, lastname " +
"FROM employee";
dbcmd.CommandText = sql;
IDataReader reader = dbcmd.ExecuteReader();
while(reader.Read()) {
string FirstName = (string) reader["firstname"];
string LastName = (string) reader["lastname"];
Console.WriteLine("Name: " +
FirstName + " " + LastName);
}
// clean up
reader.Close();
reader = null;
dbcmd.Dispose();
dbcmd = null;
dbcon.Close();
dbcon = null;
}
}
</pre>
</li>
<li>Building C# Example:
<ul>
<li>Save the example to a file, such as, TestExample.cs</li>
<li>Build on Linux:
<pre>
mcs TestExample.cs -r System.Data.dll \
-r ByteFX.Data.dll
</pre>
</li>
<li>Build on Windows via Cygwin:
<pre>
mono C:/cygwin/home/MyHome/mono/install/bin/mcs.exe \
TestExample.cs \
-lib:C:/cygwin/home/MyHome/mono/install/lib \
-r System.Data.dll -r ByteFX.Data.dll
</pre>
</li>
<li>Parameters support via MySqlParameter and MySqlParameterCollection
<li>Support LOBs (Large Object)
<li>Change the MySQL provider to not be dependent on a client library and
be written in 100% C#
<li>Connection pooling
<li>Get the provider to work like other data providers
</ul>
</li>
<li>Running the Example:
<pre>
mono TestExample.exe
</pre>
</li>
</ul>
** Testing for Mono's MySQL provider (Mono.Data.MySql)
@@ -243,13 +80,18 @@ mono TestExample.exe
</li>
<li>Take a look at MySqlTest.cs in mcs/class/Mono.Data.MySql/Test</li>
<li>On Linux, you may need to make a symbolic link from libmySQL.dll to libmysqlclient.dll</li>
<li>Has a ConnectionString format:
<pre>
"Server=hostname;Database=database;User ID=username;Password=password"
"Server=hostname;" +
"Database=database;" +
"User ID=username;" +
"Password=password"
(or)
"Host=hostname;Dbname=database;User=username;Passwd=password"
"host=hostname;" +
"dbname=database;" +
"user=username;" +
"passwd=password"
</pre>
<li>C# Example:
@@ -265,11 +107,10 @@ mono TestExample.exe
string connectionString =
"Server=localhost;" +
"Database=test;" +
"User ID=myuserid;" +
"Password=mypassword;";
"User ID=mysql;" +
"Password=;";
IDbConnection dbcon;
dbcon = new MySqlConnection(connectionString);
dbcon.Open();
IDbCommand dbcmd = dbcon.CreateCommand();
// requires a table to be created named employee
// with columns firstname and lastname
@@ -280,11 +121,11 @@ mono TestExample.exe
string sql =
"SELECT firstname, lastname " +
"FROM employee";
dbcmd.CommandText = sql;
dbcmd.ConnectionString = sql;
IDataReader reader = dbcmd.ExecuteReader();
while(reader.Read()) {
string FirstName = (string) reader["firstname"];
string LastName = (string) reader["lastname"];
string FirstName = reader["firstname"];
string LastName = reader["lastname"];
Console.WriteLine("Name: " +
FirstName + " " + LastName);
}
@@ -327,3 +168,103 @@ mono TestExample.exe
</li>
</ul>
** Testing for MySQLNet provider (ByteFX.Data.MySQLClient)
<ul>
<li>Have access to a MySQL database or download it from
<ul>
<li><a href="http://www.mysql.com/downloads/index.html">MySQL AB</a></li>
</ul>
</li>
<li>MySQLNet can be gotten from <a href="http://sourceforge.net/projects/mysqlnet/">here</a> and the
binary assembly ByteFX.Data.dll needs to be installed
in the same place as the mono class libraries.</li>
<li>MySQLNet requires <a href="http://www.icsharpcode.net/OpenSource/SharpZipLib/default.asp">SharpZipLib</a> which is
a Zip Library written in 100% C#. This is used for compression/decompression of data
sent/received over the network. The SharpZipLib binary assembly SharpZipLib.dll should
be installed in the same place as the mono class libraries.</li>
<li>Has a ConnectionString format:
<pre>
"Server=hostname;" +
"Database=database;" +
"User ID=username;" +
"Password=password"
</pre>
</li>
<li>C# Example:
<pre>
using System;
using System.Data;
using ByteFX.Data.MySQLClient;
public class Test
{
public static void Main(string[] args)
{
string connectionString =
"Server=localhost;" +
"Database=test;" +
"User ID=mysql;" +
"Password=;";
IDbConnection dbcon;
dbcon = new MySQLConnection(connectionString);
IDbCommand dbcmd = dbcon.CreateCommand();
// requires a table to be created named employee
// with columns firstname and lastname
// such as,
// CREATE TABLE employee (
// firstname varchar(32),
// lastname varchar(32));
string sql =
"SELECT firstname, lastname " +
"FROM employee";
dbcmd.ConnectionString = sql;
IDataReader reader = dbcmd.ExecuteReader();
while(reader.Read()) {
string FirstName = reader["firstname"];
string LastName = reader["lastname"];
Console.WriteLine("Name: " +
FirstName + " " + LastName);
}
// clean up
reader.Close();
reader = null;
dbcmd.Dispose();
dbcmd = null;
dbcon.Close();
dbcon = null;
}
}
</pre>
</li>
<li>Building C# Example:
<ul>
<li>Save the example to a file, such as, TestExample.cs</li>
<li>Build on Linux:
<pre>
mcs TestExample.cs -r System.Data.dll \
-r ByteFX.Data.dll
</pre>
</li>
<li>Build on Windows via Cygwin:
<pre>
mono C:/cygwin/home/MyHome/mono/install/bin/mcs.exe \
TestExample.cs \
-lib:C:/cygwin/home/MyHome/mono/install/lib \
-r System.Data.dll -r ByteFX.Data.dll
</pre>
</li>
</ul>
</li>
<li>Running the Example:
<pre>
mono TestExample.exe
</pre>
</li>
</ul>
+25 -68
View File
@@ -1,15 +1,10 @@
* ODBC Data Provider
<ul>
<li>ADO.NET Data Provider for Data Sources
that have <a href="http://www.microsoft.com/data/odbc/">ODBC</a> support.</li>
<li>Exists in namespace System.Data.Odbc and assembly System.Data</li>
<li>Exists in namespace System.Data.Odbc and assembly System.Data
<li>Works on Windows and Linux. Should have no problems working on UNIX too.</li>
<li>Works on Windows and Linux. Should have no problems working on UNIX too.
<li>Works on Windows via the native Windows odbc32.dll</li>
<li>Works on Windows via the native Windows odbc32.dll
<li>Works on Linux via:
@@ -19,33 +14,31 @@
from <a href="http://www.easysoft.com/">Easysoft</a></li>
<li><a href="http://www.iodbc.org/">iODBC</a> which has
commercial support
a commercial support
from <a href="http://oplweb.openlinksw.com:8080/download/">OpenLink Software</a></li>
</ul>
<li>List of unixODBC <a href="http://www.unixodbc.org/drivers.html">drivers</a>
<li>List of <a href="http://www.sqlsummit.com/odbcvend.htm">ODBC Vendors</a>
<li>List of <a href="http://ourworld.compuserve.com/homepages/Ken_North/odbcvend.htm">ODBC Vendors</a>
<li>ODBC can connect to various databases which has an ODBC driver installed:
<ul>
<li><a href="http://www.mysql.com/">MySQL</a></li>
<li><a href="http://www.postgresql.org/">PostgreSQL</a></li>
<li><a href="http://www.oracle.com/">Oracle</a></li>
<li><a href="http://www.borland.com/products/downloads/download_interbase.html">Interbase</a></li>
<li><a href="http://www.sybase.com/downloads">Sybase</a> (
via <a href="http://www.freetds.org/">FreeTDS</a> on UNIX)</li>
<li><a href="http://www.mysql.com/">MySQL</a>
<li><a href="http://www.postgresql.org/">PostgreSQL</a>
<li><a href="http://www.oracle.com/">Oracle</a>
<li><a href="http://www.borland.com/products/downloads/download_interbase.html">Interbase</a>
<li><a href="http://www.sybase.com/downloads">Sybase</a> and
<li><a href="http://www.microsoft.com/sql/default.asp">Microsoft SQL Server</a> (
via <a href="http://www.freetds.org/">FreeTDS</a> on UNIX)</li>
<li><a href="http://www-3.ibm.com/software/data/db2/">IBM DB2 Universal Database</a></li>
<li><a href="http://www.microsoft.com/office/access">MS Access</a>
(via <a href="http://mdbtools.sourceforge.net/">MDB Tools</a> on UNIX)</li>
via <a href="http://www.freetds.org/">FreeTDS</a> on UNIX)
<li><a href="http://www-3.ibm.com/software/data/db2/">IBM DB2 Universal Database</a>
<li><a href="http://www.microsoft.com/office/access/default.asp">MS Access</a>
(via <a href="http://mdbtools.sourceforge.net/">MDB Tools</a> on UNIX)
</ul>
<li>ODBC Provider created by Brian Ritchie.</li>
<li>Does not support trusted connections</li>
</ul>
** Current Status
@@ -77,16 +70,6 @@
<li>Can get a DataTable containing schema info via GetSchemaTable() in a OdbcDataReader</li>
<li>Can Fill a DataTable in a DataSet via an OdbcDataAdapter</li>
<li>Works in SQL#, but Column names don't show up correctly.</li>
<li>Bugs with Mono or the data provider should be reported
in Mono's Bugzilla <a href="http://bugzilla.ximian.com/">here</a>. If you
do not have Bugzilla user account, it is free
and easy to
create one <a href="http://bugzilla.ximian.com/createaccount.cgi">here</a>.</li>
</ul>
** Action Plan
@@ -98,47 +81,22 @@
<li>Testing with other setups
</ul>
** Testing ODBC provider with IBM DB2 Universal Database
** Testing ODBC provider
<ul>
<li>You need a working mono and mcs</li>
<li>For Unix, you will need unixODBC or iODBC installed</li>
<li>Have acess to a <a href="http://www-306.ibm.com/software/data/db2/">IBM DB2 Universal Database</a> or
you can download from IBM</li>
<li>Read these web pages about Unix, ODBC, and IBM DB2
<p>Test Mono's ODBC provider System.Data.Odbc with the MySQL ODBC driver MyODBC
<ul>
<li><a href="http://www.unixodbc.com/doc/db2.html">unixODBC web page about IBM DB2</a></li>
<li><a href="http://www-306.ibm.com/software/data/db2/udb/ad/v8/cli/t0010406.htm">IBM web page about unixODBC and DB2</a></li>
</ul>
</li>
<li>The ODBC provider is similar to the <a href="http://www.go-mono.com/ibmdb2.html">IBM DB2</a> provider.</li>
</ul>
** Testing ODBC provider with MySQL
<p>You can test Mono's ODBC provider System.Data.Odbc with the MySQL ODBC driver MyODBC
<p><ul>
<li>Take a look at OdbcTest.cs in mcs/class/System.Data/Test</li>
<li>Here is a ConnectionString format if you have a DSN setup:
<pre>
"DSN=dataSetName;UID=myuserid;PWD=mypassword"
"DSN=dataSetName;UID=username;PWD=password"
</pre>
</li>
<li>Here is a ConnectionString format if you do not have a DSN (have not
gotten this to work though):
<li>Here is a ConnectionString format if you do not have DSN (have not
gotten this to work):
<pre>
"DRIVER={MySQL ODBC 3.51 Driver};" +
"SERVER=localhost;DATABASE=test;" +
"UID=myuserid;PASSWORD=mypassword;" +
"OPTION=3";
"DRIVER={SQL Server};SERVER=(local);UID=sa;PWD=;DATABASE=pubs"
</pre>
</li>
<li>C# Example:
@@ -157,10 +115,9 @@
// hostname of localhost and database test
string connectionString =
"DSN=MYSQLDSN;" +
"UID=myuserid;" +
"PWD=mypassword";
"UID=mysql;" +
"PWD=;";
IDbConnection dbcon;
dbcon.Open();
dbcon = new OdbcConnection(connectionString);
IDbCommand dbcmd = dbcon.CreateCommand();
// requires a table to be created named employee
@@ -172,11 +129,11 @@
string sql =
"SELECT firstname, lastname " +
"FROM employee";
dbcmd.CommandText = sql;
dbcmd.ConnectionString = sql;
IDataReader reader = dbcmd.ExecuteReader();
while(reader.Read()) {
string FirstName = (string) reader["firstname"];
string LastName = (string) reader["lastname"];
string FirstName = reader["firstname"];
string LastName = reader["lastname"];
Console.WriteLine("Name: " +
FirstName + " " + LastName);
}
-2485
View File
File diff suppressed because it is too large. Load diff
+4 -15
View File
@@ -27,14 +27,6 @@
</li>
<li>Does not support trusted connections</li>
<li>Bugs with Mono or the data provider should be reported
in Mono's Bugzilla <a href="http://bugzilla.ximian.com/">here</a>. If you
do not have Bugzilla user account, it is free
and easy to
create one <a href="http://bugzilla.ximian.com/createaccount.cgi">here</a>.</li>
</ul>
** Current Status
@@ -90,12 +82,9 @@
string connectionString =
"Provider=PostgreSQL;" +
"Addr=127.0.0.1;" +
"Database=test;" +
"User ID=postgres;" +
"Password=fun2db";
"Database=rodrigo";
IDbConnection dbcon;
dbcon = new OleDbConnection(connectionString);
dbcon.Open();
IDbCommand dbcmd = dbcon.CreateCommand();
// requires a table to be created named employee
// with columns firstname and lastname
@@ -106,11 +95,11 @@
string sql =
"SELECT firstname, lastname " +
"FROM employee";
dbcmd.CommandText = sql;
dbcmd.ConnectionString = sql;
IDataReader reader = dbcmd.ExecuteReader();
while(reader.Read()) {
string FirstName = (string) reader["firstname"];
string LastName = (string) reader["lastname"];
string FirstName = reader["firstname"];
string LastName = reader["lastname"];
Console.WriteLine("Name: " +
FirstName + " " + LastName);
}
+66 -86
View File
@@ -1,99 +1,82 @@
* Oracle Data Provider
<ul>
<li>ADO.NET Data Provider for <a href="http://www.oracle.com/">Oracle</a> databases</li>
<li>Exists in namespace System.Data.OracleClient and assembly System.Data.OracleClient</li>
<li>Works on Windows and Linux</li>
<li>Works with Oracle 8i and 9i.</li>
<li>Uses the Oracle CLI (Call Level Interface) which is a C library (API) for the Oracle Client
software</li>
<li>Internally, the OracleClient provider has OCI abstracted to an object-oriented programming model</li>
<li>Created by Daniel Morgan and Tim Coleman</li>
<li>Bugs with Mono or the data provider should be reported
in Mono's Bugzilla <a href="http://bugzilla.ximian.com/">here</a>. If you
do not have Bugzilla user account, it is free
and easy to
create one <a href="http://bugzilla.ximian.com/createaccount.cgi">here</a>.</li>
<li>Works on Windows</li>
<li>Works with Oracle 8i</li>
<li>More information about Oracle can be found at <a href="http://www.oracle.com/"/>here</a></li>
<li>Created by Daniel Morgan.</li>
<li>Does not support trusted connections</li>
</ul>
** Current Status
<ul>
<li>OracleConnection can connect and disconnect to an Oracle 8i or 9i database on
Windows and Linux via OCI (Oracle Call-level Interface)</li>
<li>OracleConnection can connect to an Oracle 8i database on
Windows via oci.dll</li>
<li>Can have multiple connections with different transactions where each transaction is
separated from the others, so a rollback or commit in one transaction
does not affect the other.</li>
<li>The native glue library only has makefiles for Borland C++ and
Microsoft Visual C++ command line compilers. Only the makefile for
Microsoft Visual C++ command-line compiler has been tested.</li>
<li>Can execute simple DML SQL statements, such as,
INSERT a row into the EMP table via the OracleCommand's ExecuteNonQuery method</li>
<li>Can retrieve data via ExecuteReader and OracleDataReader. Currently,
supports character, numeric, some date data types. ExecuteScalar
also works.</li>
<li>Simple input parameters (character and numeric data) can now
be used in SQL queries. Output parameters do not yet work.</li>
<li>OracleException and Error handling exists now.</li>
<li>Message handling needs to be added for non-critical messages
received from Oracle</li>
<li>Handling of various data types need to be added.</li>
<li>Data Adapter exists, and a DataSet can be filled using it.</li>
<li>Lots of missing functionality and bugs.</li>
<li>Works with SQL# command-line and GTK# GUI versions.</li>
<li>The System.Data.OracleClient.dll assembly can be built with mcs/mono via
the makefile.gnu for System.Data.OracleClient or csc/.net via the
System.Data.OracleClient.build nant build file. There is also a Visual Studio.NET
solution it too.
</ul>
** Action Plan
<ul>
<li>Be able to retrieve results via a data reader (WORKING)</li>
<li>Parameters support (IN PROGRESS)</li>
<li>transactions (WORKING)</li>
<li>Get the makefile for the Borland C++ compiler to work
since the <a href="http://www.borland.com/">Borland</a> C++ compiler is
a free download</li>
<li>Get the native glue lib System.Data.OracleClient.ocigule.dll to be built
using gcc on Linux. This would require that Oracle 8i client software be installed
on Linux with the oci headers and shared libraries</li>
<li>Be able to retrieve results via a data reader</li>
<li>Parameters support</li>
<li>Stored Procedures, Functions, and Packages support</li>
<li>Be able to fill a DataTable in a DataSet via a data adapter (IN PROGRESS)</li>
<li>Support for Oracle 8i and 9i (WORKING)</li>
<li>Support LOBs</li>
<li>Support all the data types</li>
<li>Implement Connection pooling</li>
<li>Security</li>
<li>Once Oracle 10g is released, make sure Mono works with Oracle 10g.</li>
<li>Be able to fill a DataTable in a DataSet via a data adapter</li>
<li>Support for Oracle 9i</li>
<li>Figure out how to move the unmanaged OCI handling code in
the oci glue C library to the managed C# assembly. I have been unable
to successfully connect to an Oracle 8i database by using Platform Invoke and
Marshalling in C# to the oci shared library (oci.dll on Windows)</li>
</ul>
** Testing System.Data.OracleClient
** Testing Mono.Data.OracleClient
<ul>
<li>Have a working mono and mcs</li>
<li>Have access to an Oracle 8i or 9i database or download it from
<a href="http://www.oracle.com/">Oracle</a>. If you are connecting
remotely to an Oracle database, you need the Oracle client software.
Registration to the <a href="http://technet.oracle.com/">Oracle Technology Network</a> is free. If installing on Linux,
I suggest you do a lot of searching to see how others installed Oracle on Linux.</li>
<li>Have access to an Oracle 8i database or download it from
<a href="http://www.oracle.com/">Oracle</a>. Registration to the
Oracle Technology Network is free. If installing on Linux, I suggest you
do a lot of searching to see how others installed Oracle on Linux.</li>
<li>Make sure System.Data.OracleClient.dll assembly is built.</li>
<li>Make sure Mono.Data.OracleClient.dll assembly is built, if not, go
into Mono.Data.OracleClient and do a make -f makefile.gnu (on Linux) or
../../nant/NAnt.exe (on Cygwin).</li>
<li>The OCI Glue Library Mono.Data.OracleClient.ociglue.dll will need to be
created as well. Has only been tested with lc (Microsoft Visual C++ command-line compiler).
There is a make file for Microsoft C++ and Borland C++. I'm sure it wouldn't be hard
to create a makefile for gcc if installing on Linux.</li>
<li>Take a look at TestOracleClient.cs found at mcs/class/System.Data.OracleClient/Test</li>
<li>The Data Source is an Oracle TNSNAME</li>
<li>Has a connection string format:
<pre>
"Data Source=tnsname;User ID=userid;Password=password"
@@ -107,33 +90,28 @@
public class Test
{
public static void Main (string[] args)
public static void Main(string[] args)
{
string connectionString =
"Data Source=testdb;" +
"User ID=scott;" +
"Password=tiger;";
OracleConnection dbcon = null;
dbcon = new OracleConnection (connectionString);
dbcon.Open ();
OracleCommand dbcmd = dbcon.CreateCommand ();
string sql = "SELECT ename, job FROM scott.emp";
dbcmd.CommandText = sql;
OracleDataReader reader = dbcmd.ExecuteReader ();
while (reader.Read ()) {
string employeeName = (string) reader["ename"];
string job = (string) reader["job"];
Console.WriteLine ("Employee Name: {0} Job: {1}",
employeeName, job);
}
// clean up
reader.Close ();
reader = null;
dbcmd.CommandText = sql;
dbcmd.ExecuteNonQuery ();
dbcmd.Dispose ();
IDbConnection dbcon;
dbcon = new OracleConnection(connectionString);
IDbCommand dbcmd = dbcon.CreateCommand();
string sql =
"insert into scott.emp " +
"(empno, ename, job, sal, deptno) " +
"values(123," +
"'Don Smith'," +
"'Cook'," +
"23021," +
"20)";
dbcmd.ConnectionString = sql;
dbcmd.ExecuteNonQuery();
dbcmd.Dispose();
dbcmd = null;
dbcon.Close ();
dbcon.Close();
dbcon = null;
}
}
@@ -148,10 +126,12 @@
-r System.Data.OracleClient.dll
</pre>
</li>
<li>Build on Windows:
<li>Build on Windows via Cygwin:
<pre>
mcs TestExample.cs /r:System.Data.dll \
/r:System.Data.OracleClient.dll
mono C:/cygwin/home/MyHome/mono/install/bin/mcs.exe \
TestExample.cs \
-lib:C:/cygwin/home/MyHome/mono/install/lib \
-r System.Data.dll -r System.Data.OracleClient.dll
</pre>
</li>
</ul>
-36
View File
@@ -1,36 +0,0 @@
* International sites
<ul>
<li><a href="http://www.monohispano.org">Mono
Hispano</a>: The spanish-speaking community of Mono
developers and users. They have quite a number of
unique documents and tutorials.
<li><a href="http://www.go-mono.pl">Mono Poland</a>:
Mono site for polish users.
<li><a href="http://primates.ximian.com/~atsushi/mono-jp/">Mono Japanese Translation</a>:
Mono site Japanese translation pages. Translated sources are maintained at <a href="http://forge.novell.com/modules/xfmod/project/?mono-jp">Novell Forge</a>.
</ul>
* User sites
<ul>
<li>Alp Toker's <a
href="http://www.atoker.com/mono/">site</a>: He is an
active Mono developer (gsirc, platano) and produces
very nice Debian packages of Mono.
<li>Brian Ritchie's <a
href="http://www12.brinkster.com/brianr/">site</a>:
Brian is a contributor to Mono's class library (ODBC
provider and the database multiplexing assembly), and
has built an application server for .NET and Mono.
His site contains news, software, as well as his
weblog.
</ul>
-5
View File
@@ -94,8 +94,3 @@
href="http://citeseer.nj.nec.com/seligmann95incremental.html">
Incremental Collection of Mature Objects: Richard Hudson, Eliot Moss</a>
* Threads
<a
href="http://research.microsoft.com/~birrell/papers/ThreadsCSharp.pdf">
Programming with Threads in C#: Andrew Birrell</a>
-204
View File
@@ -1,204 +0,0 @@
* Writing performant .NET and Mono applications
The following document contains a few hints on how to improve
the performance of your Mono/.NET applications.
These are just guidelines, and you should still profile your
code to find the actual performance problems in your
application. It is never a smart idea to make a change with the
hopes of improving the performance of your code without first
measuring. In general, these guidelines should serve as ideas
to help you figure out `how can I make this method run faster'.
It is up to you to figure out, `Which method is running slowly.'
** Using the Mono profiler
So, how does one measure what method are running slowly? A profiler
helps with this task. Mono includes a profiler that is built
into the runtime system. You can invoke this profiler on your program
by running with the --profile flag.
<pre>
mono --profile program.exe
</pre>
The above will instruct Mono to instrument your application
for profiling. The default Mono profiler will record the time
spent on a routine, the number of times the routine called,
the memory consumed by each method broken down by invoker, and
the total amount of memory consumed.
It does this by asking the JIT to insert a call to the profiler
every time a method is entered or left. The profiler times the
amount of time elapsed between the beginning and the end of the
call. The profiler is also notified of allocations.
When the program has finished executing, the profiler prints the
data in human readable format. It looks like:
<pre>
Total time spent compiling 227 methods (sec): 0.07154
Slowest method to compile (sec): 0.01893: System.Console::.cctor()
Time(ms) Count P/call(ms) Method name
########################
91.681 1 91.681 .DebugOne::Main()
Callers (with count) that contribute at least for 1%:
1 100 % .DebugOne::Main(object,intptr,intptr)
...
Total number of calls: 3741
...
Allocation profiler
Total mem Method
########################
406 KB .DebugOne::Main()
406 KB 1000 System.Int32[]
Callers (with count) that contribute at least for 1%:
1 100 % .DebugOne::Main(object,intptr,intptr)
Total memory allocated: 448 KB
</pre>
At the top, it shows each method that is called. The data is sorted
by the total time that the program spent within the method. Then
it shows how many times the method was called, and the average time
per call.
Below this, it shows the top callers of the method. This is very useful
data. If you find, for example, that the method Data::Computate () takes
a very long time to run, you can look to see if any of the calls can be
avoided.
Two warnings must be given about the method data. First,
the profiler has an overhead associated with it. As such,
a high number of calls to a method may show up as comsuming
lots of time, when in reality they do not consume much time
at all. If you see a method that has a very high number of
calls, you may be able to ignore it. However, do consider
removing calls if possible, as that will sometimes help
performance. This problem is often seen with the use
of built in collection types.
Secondly, due to the nature of the profiler, recursive calls
have extermely large times (because the profiler double counts
when the method calls itself). One easy way to see this problem
is that if a method is shown as taking more time than the Main
method, it is very likely recursive, and causing this problem.
Below the method data, allocation data is shown. This shows
how much memory each method allocates. The number beside
the method is the total amount of memory. Below that, it
is broken down into types. Then, the caller data is given. This
data is again useful when you want to figure out how to eliminate calls.
You might want to keep a close eye on the memory consumption
and on the method invocation counts. A lot of the
performance gains in MCS for example came from reducing its
memory usage, as opposed to changes in the execution path.
** Memory Management in the .NET/Mono world.
Since Mono and .NET offer automatic garbage collection, the
programmer is freed from having to track and dispose the
objects it consumes (except for IDispose-like classes). This
is a great productivity gain, but if you create thousands of
objects, that will make the garbage collector do more work,
and it might slow down your application.
Remember, each time you allocate an object, the GC is forced
to find space for the object. Each object has an 8 byte overhead
(4 to tell what type it is, then 4 for a sync block). If
the GC finds that it is running out of room, it will scan every
object for pointers, looking for unreferenced objects. If you allocate
extra objects, the GC then must take the effort to free the objects.
Mono uses the Boehm GC, which is a conservative collector,
and this might lead to some memory fragmentation and unlike
generational GC systems, it has to scan the entire allocated
memory pool.
*** Boxing
The .NET framework provides a rich hierchy of object types.
Each object not only has value information, but also type
information associated with it. This type information makes
many types of programs easier to write. It also has a cost
associated with it. The type information takes up space.
In order to reduce the cost of type information, almost every
Object Oriented language has the concept of `primitatives'.
They usually map to types such as integers and bools. These
types do not have any type information associated with them.
However, the language also must be able to treat primitatives
as first class datums -- in the class with objects. Languages
handle this issue in different ways. Some choose to make a
special class for each primative, and force the user to do an
operation such as:
<pre>
// This is Java
list.add (new Integer (1));
System.out.println (list.get (1).intValue ());
</pre>
The C# design team was not satisfied with this type
of construct. They added a notion of `boxing' to the language.
Boxing preforms the same thing as Java's <code>new Integer (1)</code>.
The user is not forced to write the extra code. However,
behind the scenes the <em>same thing</em> is being done
by the runtime. Each time a primative is cast to an object,
a new object is allocated.
You must be careful when casting a primative to an object.
Note that because it is an implicit conversion, you will
not see it in your code. For example, boxing is happening here:
<pre>
ArrayList foo = new ArrayList ();
foo.Add (1);
</pre>
In high performance code, this operation can be very costly.
*** Using structs instead of classes for small objects
For small objects, you might want to consider using value
types (structs) instead of object (classes).
However, you must be careful that you do not use the struct
as an object, in that case it will actually be more costly.
As a rule of thumb, only use structs if you have a small
number of fields (totaling less than 32 bytes), and
need to pass the item `by value'. You should not box the object.
*** Assisting the Garbage Collector
Although the Garbage Collector will do the right thing in
terms of releasing and finalizing objects on time, you can
assist the garbage collector by clearing the fields that
points to objects. This means that some objects might be
elegible for collection earlier than they would, this can help
reduce the memory consumption and reduce the work that the GC
has to do.
** foreach
The <tt>foreach</tt> C# statement handles various kinds of
different constructs (about seven different code patterns are
generated). Typically foreach generates more efficient code
than loops constructed manually, and also ensures that objects
which implement IDispose are properly released.
But foreach sometimes might generate code that under stress
performs badly. Foreach performs badly when its used in tight
loops, and its use leads to the creation of many enumerators.
Although technically obtaining an enumerator for some objects
like ArrayList is more efficient than using the ArrayList
indexer, the pressure introduced due to the extra memory
requirements and the demands on the garbage collector make it
more inneficient.
There is no straight-forward rule on when to use foreach, and
when to use a manual loop. The best thing to do is to always
use foreach, and only when profile shows a problem, replace
foreach with for loops.
+1 -1
View File
@@ -8,7 +8,7 @@
Currently you can read our plans for <a
href="ado-net.html">ADO.NET</a>, <a
href="asp-net.html">ASP.NET</a>, <a href="java.html">Java</a> and
href="asp-net">ASP.NET</a>, <a href="java.html">Java</a> and
<a href="winforms.html">WinForms</a>.
+45 -157
View File
@@ -1,208 +1,98 @@
* PostgreSQL and Mono
When it comes to Mono and PostgreSQL, there are many ways
you can handle your data. You have many Mono Data Providers which can be used
to access data from a application written for Mono.
Then there is the future goal of having the ability to host Mono within PostgreSQL to
have the applications run on the server which makes things much faster.
* Hosting Mono in PostgreSQL
There is a project to <a href="http://gborg.postgresql.org/project/plmono/projdisplay.php">host Mono within PostgreSQL</a>.
plMono is a PostgreSQL language using the embedded Mono runtime. It provides support for writing functions in C#, or any other language that supports .NET.
* Data Providers
There are many ADO.NET data providers for <a href="http://www.postgresql.org/">PostgreSQL</a>:
There are two providers created specifically for PostgreSQL included with Mono:
* PostgreSQL Data Provider
<ul>
<li><a href="http://gborg.postgresql.org/project/npgsql/projdisplay.php">Npgsql</a>
<li>Exists in namespace Mono.Data.PostgreSql and assembly Mono.Data.PostgreSql</li>
<li>Is a Mono Data Provider for the <a href="http://www.postgresql.org/">PostgreSQL</a>
client/server database management system.</li>
<li>Written in C# and has C# bindings to the PostgreSQL C Client library pq.dll on Windows
and libpq.so on Linux.</li>
<li>Alternative to the PostgreSQL provider in Mono:
<ul>
<li>included with Mono</li>
<li>a .NET Managed Data Provider for PostgreSQL</li>
<li>Written in 100% C#</li>
<li>does not require a client library</li>
<li>works on Mono and Microsoft .NET</li>
<li>created by Francisco Figueiredo jr. and has many developers working on it
<li>works in the SQL# (command-line and GTK# GUI versions)</li>
<li>in namespace Npgsql and assembly Npgsql and is found in mcs
at mcs/class/Npgsql</li>
<li><a href="http://gborg.postgresql.org/project/npgsql/projdisplay.php">Npgsql</a>
is a Managed PostgreSQL provider written in 100% C#, does not require a client library,
and works on Microsoft .NET and Mono.
</li>
</ul>
</li>
<li>Mono.Data.PostgreSQL (deprecated)
<ul>
<li>included with Mono</li>
<li>Deprecated in favor of Npgsql</li>
<li>Exists in namespace Mono.Data.PostgreSql and assembly Mono.Data.PostgreSql</li>
<li>Is a Mono Data Provider for the <a href="http://www.postgresql.org/">PostgreSQL</a>
client/server database management system.</li>
<li>Written in C# and has C# bindings to the PostgreSQL C Client library pq.dll on Windows
and libpq.so on Linux.</li>
</ul>
</li>
<li><a href="http://sourceforge.net/projects/mysqlnet/">ByteFX.Data</a> has a provider for PostgreSQL too, but I do not know how well it works with Mono.</li>
<li>There is another .NET data provider for PostgreSQL named <a href="http://sourceforge.net/projects/pgsqlclient/">PgSqlClient</a>, but I do not know if it works with Mono.</li>
<li>If none of the above providers meet your needs. There is the ODBC and OLEDB providers included with Mono.</li>
<li>Bugs with Mono or the data provider should be reported
in Mono's Bugzilla <a href="http://bugzilla.ximian.com/">here</a>. If you
do not have Bugzilla user account, it is free
and easy to
create one <a href="http://bugzilla.ximian.com/createaccount.cgi">here</a>.</li>
<li>See Testing for both Mono's Mono.Data.PostgreSqlClient and Npgsql.</li>
</ul>
Below, see separate Testing sections for Npgsql and Mono.Data.PostgreSqlClient.
** Current Status
<ul>
<li>Npgsql
<ul>
<li>Builds and Runs on both Microsoft .NET and Mono.</li>
<li>Works using SQL# (command-line and GTK# versions)</li>
<li>You can send insert, update, delete queries
through NpgsqlCommand.ExecuteNonQuery() method.</li>
<li>You can send queries like, select count(*) from table, select version()
with NpgsqlCommand.ExecuteScalar() method.</li>
<li>There is logging support. (Thanks Dave Page)
To use it, place code like that in your program:</li>
<pre>
// Enable logging.
NpgsqlEventLog.Level = LogLevel.Debug; // LogLevel.
NpgsqlEventLog.LogName = "NpgsqlTests.LogFile"; // LogFile.
</pre>
<li>You can use Npgsql with Mono (Thanks Kristis Makris). It is not working perfectly.</li>
<li>There is a winforms test suite (Thanks Dave Page).</li>
<li>Clearer code in NpgsqlConnection removing *magic* numbers and constants. (Thanks Kristis Makris)</li>
<li>Better support of ODBC-like ConnectionString in NpgsqlConnection (Thanks Dave Page)</li>
<li>Thanks Ulrich Sprick for all discussion and ideas.</li>
</ul>
</li>
<li>Mono.Data.PostgreSQL status
<ul>
<li>Deprecated in favor of Npgsql</li>
<li>We are able to do simple CREATE TABLE, DROP TABLE, UPDATE, INSERT, and
DELETE SQL commands using the ExecuteNonQuery method in PgSqlCommand.</li>
DELETE SQL commands using the ExecuteNonQuery method in PgSqlCommand.
<li>We can execute multiple queries and do a NextResult() in PgSqlDataReader()
to get the next result set.</li>
to get the next result set.
<li>We are also able to do simple aggregate functions,
ie, count(), sum(), min(), and max()
in a simple SELECT SQL query using the ExecuteScalar() now.</li>
in a simple SELECT SQL query using the ExecuteScalar() now.
<li>We are also able to retrieve data with a simple SELECT SQL query
using ExecuteReader() which returns a PgSqlDataReader. We are able to
use GetSchemaTable() to get the meta data about the table columns.
We are able to Read() to get each row from the result set.</li>
We are able to Read() to get each row from the result set.
<li>We are able to get
String data (char, character, text, varchar), Int16 (smallint),
Int32 (integer), Int64 (bigint), DateTime (time, date, timestamp),
Boolean (boolean), Single (float), and Double (double).
More data types will come later. Note, the types that do work still
need thorough testing.</li>
need thorough testing.
<li>Rows that are returned which contain columns that are NULL are handled now.
The PgSqlDataReader method IsDBNull() needs to be called to determine
if a field IS NULL before trying to read data from that field.</li>
if a field IS NULL before trying to read data from that field.
<li>Calling PostgreSQL stored procedures works. It does not work perfectly.
It may not
even work to specification - yet. If you want to test it yourself, look at
TestSqlDataReader.cs or PostgresTest.cs in
mcs/class/System.Data/Test.</li>
mcs/class/System.Data/Test.
<li>Below, I have some sample code you can
use to call a PostgreSQL stored procedure named "version". This stored
procedure returns a string containing the PostgreSQL server version. Notice
the CommandType is StoredProcedure and the method ExecuteScalar() is called.</li>
the CommandType is StoredProcedure and the method ExecuteScalar() is called.
<li>ExecuteScalar() is a lightweight method in class PgSqlCommand that only returns
one row and one column as one object - even if there is more than row or column.</li>
one row and one column as one object - even if there is more than row or column.
<li>We have the beginnings of Parameters support PostgreSQL. Only
Input Parameters are currently supported. Output, Input/Output,
and Return parameters still need to be done.</li>
and Return parameters still need to be done.
<li>A lot of functionality in System.Data is missing, but the
infrastructure is starting to come together.
<li>A lot of Exceptions need to be thrown for various exceptions. However,
PgSqlException, PgSqlErrorCollection, and PgSqlError have been partially
implemented.</li>
implemented.
<li>Tim Coleman and Rodrigo Moya got the beginnings of the
PgSqlDataAdapter/DataSet/DataTable/DataRow to work. Currently,
the PgSqlDataAdapter can Fill() relational data into a DataTable in a DataSet.
See the test mcs/class/System.Data/Test/TestSqlDataAdapter.cs to see it in action.</li>
<li>Works in the SQL# command-line version
and the GTK# version on Linux. It only works in SQL# command-line version
on Windows.</li>
</ul>
</li>
See the test mcs/class/System.Data/Test/TestSqlDataAdapter.cs to see it in action.
</ul>
** Action Plan
<ul>
<li>More testing and fixing bugs</li>
<li>Better error handling</li>
<li>More Data Types to use</li>
<li>Any features for Npgsql should be implemented in Npgsql's main cvs repository at
gborg.postgresql.org. Most bugs should be fixed in gborg.postgresql.org's cvs.
Only bugs neccessary for building and running of Npgsql on Mono can be done in Mono cvs,
but once applied they should be sent to Npgsql's mailing list
at gborg.postgresql.org for inclusion into cvs there. Whenever there is
a release of Npgsql (determined by Francisco Figueiredo jr. or a release
of Mono (determined by Miguel de Icaza), then the Npgsql source
in gborg.postgresql.org's cvs will be used to update the Npgsql source in
Mono's cvs.
</li>
<li>Mono.Data.PostgreSqlClient even though deprecated can still
accept bug fixes. This is because other areas, such as, ASP.NET examples
may still use this provider.</li>
<li>Add any missing functionality to Npgsql. If this funtionality works on
.NET but not on Mono, implement the missing features or fix the bugs in Mono</li>
<li>Npgsql has replaced Mono.Data.PostgreSqlClient as the provider of
choice to use. However, Mono.Data.PostgreSqlClient will remain in a
deprecated state until nobody uses it anymore - then it can be removed</li>
<li>Implement more of PostgreSQL 7.3 features in Npgsql</li>
</ul>
<p>More testing and fixing bugs...
** Testing Mono.Data.PostgreSqlClient
<p>Eventually replace the PostgreSQL data provider in Mono
with <a href="http://gborg.postgresql.org/project/npgsql/projdisplay.php">Npgsql</a>.
Npgsql is a .Net Data Provider for PostgreSQL which implements
the <a href="http://developer.postgresql.org/docs/postgres/protocol.html">PostgreSQL Frontend/Backend Protocol</a>.
Npgsql is implemented in 100% C#. This provider was created by Francisco Figueiredo jr.
and has many programmers developing the provider.
** Testing Mono's Mono.Data.PostgreSqlClient
<ul>
* <p>In order to test Mono.Data.PostgreSqlClient, you will need to have
@@ -462,7 +352,6 @@ mono PostgresTest.exe
"Password=fun2db;";
IDbConnection dbcon;
dbcon = new PgConnection(connectionString);
dbcon.Open();
IDbCommand dbcmd = dbcon.CreateCommand();
// requires a table to be created named employee
// with columns firstname and lastname
@@ -473,11 +362,11 @@ mono PostgresTest.exe
string sql =
"SELECT firstname, lastname" +
"FROM employee";
dbcmd.CommandText = sql;
dbcmd.ConnectionString = sql;
IDataReader reader = dbcmd.ExecuteReader();
while(reader.Read()) {
string FirstName = (string) reader["firstname"];
string LastName = (string) reader["lastname"];
string FirstName = reader["firstname"];
string LastName = reader["lastname"];
Console.WriteLine("Name: " +
FirstName + " " + LastName);
}
@@ -546,7 +435,6 @@ mono TestExample.exe
"Password=fun2db;";
IDbConnection dbcon;
dbcon = new NpgsqlConnection(connectionString);
dbcon.Open();
IDbCommand dbcmd = dbcon.CreateCommand();
// requires a table to be created named employee
// with columns firstname and lastname
@@ -557,11 +445,11 @@ mono TestExample.exe
string sql =
"SELECT firstname, lastname " +
"FROM employee";
dbcmd.CommandText = sql;
dbcmd.ConnectionString = sql;
IDataReader reader = dbcmd.ExecuteReader();
while(reader.Read()) {
string FirstName = (string) reader["firstname"];
string LastName = (string) reader["lastname"];
string FirstName = reader["firstname"];
string LastName = reader["lastname"];
Console.WriteLine("Name: " +
FirstName + " " + LastName);
}
+2 -4
View File
@@ -13,9 +13,7 @@
*** Jitter
Works on MacOS X 10.2 and Linux/PPC.
There are known problems on MacOS 10.3
Start the port
** Documentation
@@ -30,6 +28,6 @@
*** Calling conventions:
<a href="http://refspecs.freestandards.org/elf/elfspec_ppc.pdf">The PowerPC SystemV ABI specification</a>
<a href="http://www.esofta.com/softspecs.html">The PowerPC SystemV ABI specification</a>
-15
View File
@@ -1,15 +0,0 @@
#!/bin/sh
MANAGED_CALLS=`gdb -silent $1 -pid $2 << EOF | awk '/.* in \?\? \(\)/ {printf("call print_method_from_ip(%s)\n", $2);}'
set height 0
thread apply all bt
quit
EOF`
gdb -silent $1 -pid $2 << EOF
set height 0
thread apply all bt
$MANAGED_CALLS
quit
EOF
+2
View File
@@ -10,6 +10,8 @@
** EOG component
** XmlStorageSystem component
* Gtk# related projects
Gnome Canvas Bindings.
-156
View File
@@ -1,156 +0,0 @@
* Provider Factory
<p>Brian Ritchie contributed a Provider Factory and Data Tools for Mono ADO.NET<br>
which gives us a foundation for abstract data provider access within Mono
** Here are the deails:
<ul>
<li>The Provider information is seperate from the connection string information.<br>
This allows the list of providers to be stored in the machine.config file.</li>
<li>Provider and ProviderCollection objects are available to access <br>
the list of providers and modify them at runtime.</li>
<li>The ProviderFactory object is used to create new connections, commands,<br>
dataadapters, parameters, etc.</li>
</ul>
** Overview of the ProviderFactory object model:
<ul>
<li><b>ProviderFactory</b>: used to create new Connections, Commands,<br>
DataAdapters, or Commands. All objects are returned using <br>
the provider interfaces such as IDbConnection, IDbCommand,<br>
IDbDataAdapter, or IDataParamter</li>
<li><b>DataTools</b>: static methods for doing <br>
common tasks like filling a DataSet <br>
with the contents of a select statement.</li>
<li><b>ProviderCollection</b>: list of providers configured <br>
in the system. Initially loaded from app.config, but can <br>
be modified at run-time.</li>
<li><b>Provider</b>: represents a given provider (factory) <br>
and holds information needed to <br>
create the types.</li>
<li><b>ProviderSectionHandler</b>: works behind the <br>
scenes to load the list of <br>
providers from the app.config into a ProviderCollection.</li>
</ul>
** C# source code samples for creating a connection:
<pre>
// Create connection using enhanced connection string
// The factory attribute specifies which provider
// to use. The factory attribute is parsed out, the
// object is created, and then the rest of the
// connection string is passed into the provider. The
// providers are defined in
// the app.config (or machine.config).
IDbConnection conn;
string connectionString =
"factory=System.Data.SqlClient;" +
"server=speedy;database=pubs;uid=sa";
conn = ProviderFactory.CreateConnection(connectionString);
// Create connection specifying provider
// and standard connection string
IDbConnection conn;
string provider = "System.Data.SqlClient";
string connectionString = "server=speedy;database=pubs;uid=sa";
conn = ProviderFactory.CreateConnection(provider,connectionString);
// Create connection using connection string stored
// in app.config under &lt;appSettings&gt;
IDbConnection conn;
string appSetting = "PubsConnStr";
conn = ProviderFactory.CreateConnectionFromConfig(appSetting);
</pre>
<p>C# Sample for Creating a DataAdapter and filling a DataSet.
<pre>
// Create Connection
IDbConnection conn =
ProviderFactory.CreateConnectionFromConfig("PubsConnStr");
// Select command
IDbCommand cmd=conn.CreateCommand();
cmd.Text="select * from author";
// Data Adapter
DataSet ds=new DataSet();
IDbDataAdapter adapter=ProviderFactory.CreateDataAdapter(cmd);
adapter.Fill(ds, "Table1");
</pre>
<p>Creating a DataAdapter and filling a DataSet. <br>
The super lazy method for people like me.
<pre>
// Create Connection
IDbConnection conn =
ProviderFactory.CreateConnectionFromConfig("TdsPubsConnStr");
// Data Adapter
DataSet ds=DataTools.FillDataSet(conn, "select * from author");
</pre>
<p>Here's some sample code on displaying a list <br>
of configured ADO.NET providers:
<pre>
Console.WriteLine("Configured Providers:");
foreach (Provider p in ProviderFactory.Providers)
Console.WriteLine(p.Description);
</pre>
<p>A Super lazy overload to the FillDataSet method (in <br>
DataTools.cs) that will fill a dataset in one line of code.
<pre>
DataSet ds=DataTools.FillDataSet("PubsConnStr", "select * from authors");
</pre>
** About Configuration Files
<p>Information about <a href="http://msdn.microsoft.com/library/en-us/vbcon/html/vboriintroductiontoapplicationsettingstorage.asp?frame=true">app.config</a> files
can be found at <a href="http://msdn.microsoft.com/">MSDN</a>.
<p>See the mcs/class/Mono.Data/app.config for sample configuration file in<br>
mcs source. Basically, if your application is named blah.exe, <br>
you would create an app.config file named blah.exe.config
<p>Here's a sample app.config file showing the provider <br>
declarations along with sample connection strings:
<pre>
&lt;?xml version="1.0" encoding="utf-8" ?&gt;
&lt;configuration&gt;
&lt;configSections&gt;
&lt;sectionGroup name="mono.data"&gt;
&lt;section name="providers" type="Mono.Data.ProviderSectionHandler,Mono.Data" /&gt;
&lt;/sectionGroup&gt;
&lt;/configSections&gt;
&lt;appSettings&gt;
&lt;add key="PubsConnStr" value="factory=System.Data.SqlClient;server=speedy;database=pubs;uid=sa;pwd=" /&gt;
&lt;/appSettings&gt;
&lt;mono.data&gt;
&lt;providers&gt;
&lt;provider name="System.Data.SqlClient" connection="System.Data.SqlClient.SqlConnection" adapter="System.Data.SqlClient.SqlDataAdapter" assembly="System.Data, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/&gt;
&lt;provider name="System.Data.OleDb" connection="System.Data.OleDb.OleDbConnection" adapter="System.Data.OleDb.OleDbDataAdapter" assembly="System.Data, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/&gt;
&lt;provider name="System.Data.Odbc" connection="System.Data.Odbc.OdbcConnection" adapter="System.Data.OleDb.OdbcDataAdapter" assembly="System.Data, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/&gt;
&lt;provider name="Mono.Data.TdsClient" connection="Mono.Data.TdsClient.TdsConnection" adapter="Mono.Data.TdsClient.TdsDataAdapter" assembly="Mono.Data.TdsClient" /&gt;
&lt;provider name="Mono.Data.MySql" connection="Mono.Data.MySql.MySqlConnection" adapter="Mono.Data.MySql.MySqlDataAdapter" assembly="Mono.Data.MySql" /&gt;
&lt;provider name="Mono.Data.PostgreSqlClient" connection="Mono.Data.PostgreSqlClient.PgSqlConnection" adapter="Mono.Data.PostgreSqlClient.PgSqlDataAdapter" assembly="Mono.Data.PostgreSqlClient" /&gt;
&lt;provider name="Mono.Data.SqliteClient" connection="Mono.Data.SqliteClient.SqliteConnection" adapter="Mono.Data.SqliteClient.SqliteDataAdapter" assembly="Mono.Data.SqliteClient" /&gt;
&lt;provider name="Mono.Data.SybaseClient" connection="Mono.Data.SybaseClient.SybaseConnection" adapter="Mono.Data.SybaseClient.SybaseDataAdapter" assembly="Mono.Data.SybaseClient" /&gt;
&lt;/providers&gt;
&lt;/mono.data&gt;
&lt;/configuration&gt;
</pre>
+7 -33
View File
@@ -18,7 +18,7 @@
standard GNOME interfaces for easily creating reusable,
language independent components, controls and compound
documents. This technology is known as <a
href="http://developer.ximian.com/articles/whitepapers/bonobo">Bonobo</a>.
href="http://developer.ximian.com/tech/bonobo.html">Bonobo</a>.
Interfaces to Bonobo exist for C, Perl, Python, and
Java.
@@ -134,51 +134,25 @@
** What makes up Mono?
There are various pieces that make up Mono today:
There are various pieces that will make up Mono:
<ul>
* A C# compiler.
* The Virtual Execution System: that has the
* The Virtual Execution System: that will have the
Just-in-Time compiler, garbage collector, loader,
threading engine.
A byte code interpreter is provided for quickly
A byte code interpreter will be provided for quickly
porting Mono to new systems and debugging the JIT
purposes, but it is not intended to be the ideal
execution environment.
* An implemenation of the .NET class libraries:
Remoting, Reflection, Reflection.Emit, Xml, Xpath,
Xslt, Xml Serialization, Web Services support.
* An implemenation of the .NET class library.
* Cross platform class libraries for data access:
Postgress, MySQL, DB2, TDS, Sybase, Oracle, ODBC and
Gnome's GDA.
* Visual development tools.
* Unix class libraries: Mono.Posix
* Gnome-specific class libraries: The Gtk# family.
* A code pre-compiler to generate native code ahead of
time.
* Gtk# a toolkit to develop GNOME applications on Unix
and Windows.
* An implementation of the Remoting infrastructure in
.NET
</ul>
Other work-in-progress components:
<ul>
* A VB.NET compiler and JScript compilers are in the works.
* Web services on the server side.
* We are planning to include Remoting.CORBA as part of
Mono standard distribution.
* A CIL GCC frontend.
</ul>
** Why use GNOME components?
+21 -21
View File
@@ -9,10 +9,10 @@
** Microsoft .NET
The <a href="http://msdn.microsoft.com/netframework">Microsoft.NET site.</a>
The <a href="http://msdn.microsoft.com/net">Microsoft.NET site.</a>
The Microsoft .NET Framework can be downloaded <a
href="http://msdn.microsoft.com/library/default.asp?url=/downloads/list/netdevframework.asp">here</a>
The Microsoft .NET Framework 1.0 can be downloaded <a
href="http://msdn.microsoft.com/downloads/default.asp?url=/downloads/sample.asp?url=/msdn-files/027/000/976/msdncompositedoc.xml&frame=true">here</a>
New methods that are not documented in 1.0, are documented <a
href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/framewrkaddend.asp">here</a>
@@ -28,16 +28,11 @@
The Mono Tutorial:
<a href="http://go-mono.com/tutorial/">GNOME.NET Tutorial</a>
<a href="http://http://go-mono.com/gnometutorial/">GNOME.NET Tutorial</a>
and other useful tutorials (Gtk#, Glade#, Embeded, etc) (in Spanish) at
<a href="http://www.monohispano.org">The Mono Hispano site</a>.
Community site for Mono at <a href="http://www.gotmono.com">Got Mono</a>
Wikis: <a href="http://www.nullenvoid.com/gtksharp/wiki">Gtk# Wiki</a>
and <a href="http://www.nullenvoid.com/mono/wiki">Mono Wiki</a>.
<a href="http://mono.es.gnome.org">The Mono Hispano site</a>.
Sergey's web page on Mono resources:
@@ -47,10 +42,6 @@
<a href="http://www.gotdotnet.com">Got Dot Net</a>
Got Mono:
<a href="http://www.gotmono.com">Got Mono</a>
MonoMail:
<a href="http://sourceforge.net/projects/monomail/">http://sourceforge.net/projects/monomail/</a>
@@ -74,13 +65,21 @@
<li><a href="http://www.gotdotnet.com/userarea/keywordsrch.aspx?keyword=winchurn">http://www.gotdotnet.com/userarea/keywordsrch.aspx?keyword=winchurn</a>
</ul>
** Presentations
Currently the <a href="Presentations/O-Reilly">O'Reilly</a>
presentation on Mono is available. Arturo Espinosa has given
a talk on Mono in Mexico and made <a
href="http://construct.ximian.com/~arturo/Presentations/Mono.OLS/html">spanish
slides</a>
** ECMA Documentation.
You can get the documentation for the ECMA specs from:
<ul>
* <a href="http://www.ecma-international.org/publications/standards/Ecma-334.HTM">C# Language Specification</a>
* <a href="http://www.ecma-international.org/publications/standards/Ecma-335.HTM">Common Language Infrastructure</a>
* <a href="http://www.ecma.ch/ecma1/STAND/ecma-334.htm">C# Language Specification</a>
* <a href="http://www.ecma.ch/ecma1/STAND/ecma-335.htm">Common Language Infrastructure</a>
</ul>
@@ -89,6 +88,7 @@
<ul>
* <a href="http://msdn.microsoft.com/net/ecma">At MSDN</a>
* <a href="http://www.dotnetexperts.com">Dot Net Experts</a>
* <a href="http://developer.intel.com/software/idap/ecma">Intel</a>
* <a href="http://lightning.csse.monash.edu.au/.net/CLI">Monash University</a>
</ul>
@@ -136,15 +136,11 @@
href="http://xmarks.sourceforge.net/doc.html">XMarks DOC.NET:</a> For
creating online documentation you can browse for your own classes.
* <a
href="http://www.cl.cam.ac.uk/~jds31/research/gccnet/">GCC .NET backend</a>.
Jeremy Singer has developed a .NET backend for GCC. This is research work.
</ul>
<li><b>Class Libraries</b></li>
<ul>
* <a href="http://cs-sdl.sourceforge.net/">SDL for
* <a href="http://9mm.com/~ogl/sdldotnet/">SDL for
.NET:</a> Bindings for the popular SDL graphics library.
@@ -184,6 +180,10 @@
* <a
href="http://www.southern-storm.com.au/portable_net.html">Portable.NET:</a>
Another implementation of the CLI and C# compiler.
* A Free (GFDL) tutorial on C# in Spanish with
examples, slides, and extras (under development). Get it <a
href="http://geneura.ugr.es/~jaime/csharp/">here</a>.
</ul>
** GNOME Documentation
+38 -72
View File
@@ -1,25 +1,26 @@
* The Mono runtime
The Mono runtime engine is considered feature complete.
It implements a Just-in-Time compiler engine for the CIL
virtual machine, the class loader, the garbage collector,
threading system and metadata access libraries.
The Mono runtime implements a JIT engine for the CIL virtual
machine (as well as a byte code interpreter, this is to
quickly port it to new systems), the class loader, the garbage
collector, threading system and metadata access libraries.
We currently have two runtimes:
<ul>
* <b>mono:</b> Our Just-in-Time and Ahead-of-Time code
generator for maximum performance.
* <b>mono:</b> The Just In Time compiler implemented
using a BURS instruction selector. We only support
x86 machines in the JIT engine at this point.
* <b>mint:</b> The Mono interpreter. This is an
easy-to-port runtime engine.
</ul>
We are using the Boehm conservative garbage collector.
Currently we are using the Bohem conservative garbage
collector.
The Mono runtime can be used as a stand-alone process, or it
can be <a href="embedded-api.html">embedded into applications</a> (see
can be <a href="embedded-api">embedded into applications</a> (see
the documentation in mono/samples/embed for more details).
Embedding the Mono runtime allows applications to be extended
@@ -30,52 +31,12 @@
href="http://primates.ximian.com/~lupus/slides/jit/">slides
here</a>
** Current JIT Engine: technical details (<b>updated, June 28th, 2003</b>)
** Current JIT Engine (<b>updated, July 8th, 2002</b>)
We have re-written our JIT compiler. We wanted to support a
number of features that were missing:
<ul>
* Ahead-of-time compilation.
The idea is to allow developers to pre-compile their code
to native code to reduce startup time, and the working
set that is used at runtime in the just-in-time compiler.
Although in Mono this has not been a visible problem, we
wanted to pro-actively address this problem.
When an assembly (a Mono/.NET executable) is installed in
the system, it would then be possible to pre-compile the
code, and have the JIT compiler tune the generated code
to the particular CPU on which the software is
installed.
This is done in the Microsoft.NET world with a tool
called ngen.exe
* Have a good platform for doing code optimizations.
The design called for a good architecture that would
enable various levels of optimizations: some
optimizations are better performed on high-level
intermediate representations, some on medium-level and
some at low-level representations.
Also it should be possible to conditionally turn these on
or off. Some optimizations are too expensive to be used
in just-in-time compilation scenarios, but these
expensive optimizations can be turned on for
ahead-of-time compilations or when using profile-guided
optimizations on a subset of the executed methods.
* Reduce the effort required to port the Mono code
generator to new architectures.
For Mono to gain wide adoption in the Unix world, it is
necessary that the JIT engine works in most of today's
commercial hardware platforms.
</ul>
The JIT engine uses a code-generator generator approach for
compilation. Given the properties of CIL byte codes, we can
take full advantage of a real instruction selector for our
code generator.
The JIT engine implements a number of optimizations:
@@ -86,7 +47,7 @@
* Inlining.
* Constant folding, copy propagation, dead code elimination.
* Constant folding.
Although compilers typically do
constant folding, the combination of inlining with
@@ -95,9 +56,6 @@
* Linear scan register allocation. In the past,
register allocation was our achilles heel, but now
we have left this problem behind.
* SSA-based framework. Various optimizations are
implemented on top of this framework
</ul>
There are a couple of books that deal with this technique: "A
@@ -106,13 +64,7 @@
technical description of <a
href="http://research.microsoft.com/copyright/accept.asp?path=http://www.research.microsoft.com/~drh/pubs/iburg.pdf&pub=ACM">lbrug</a>.
The new JIT engines uses three intermediate representations:
the source is the CIL which is transformed into a forest of
trees; This is fed into a BURS instruction selector that
generates the final low-level intermediate representation.
The instruction selector is documented in the following
papers:
A few papers that describe the instruction selector:
<ul>
* <a href="http://research.microsoft.com/copyright/accept.asp?path=http://www.research.microsoft.com/~drh/pubs/interface.pdf&pub=wiley">A code generation interface for ANSI C</a>
@@ -122,13 +74,28 @@
</ul>
** New JIT engine.
We are working on a new JIT engine. The new JIT engine
focuses on portability and in two intermediate representations
that simplify the development of optimizations. This together
with the Ahead-of-Time compilation will allow developers to
deploy applications that match the speed of natively compiled code.
** Garbage Collection
We are using the Boehm conservative GC. We might consider
adopting other GC engines in the future, like the Intel ORP GC
engine. The Intel ORP GC engine as it provides a precise
Currently we are using the Boehm conservative GC. Although our plans
are to move to the Intel ORP GC engine, our plans on a next generation
dual-JIT engine have to be taken into account.
We will be using the Intel ORP GC engine as it provides a precise
garbage collector engine, similar to what is available on the
.NET environment.
.NET environment.
Although using a conservative garbage collector like Bohem's
would work, all the type information is available at runtime,
so we can actually implement a better collector than a
conservative collector.
<ul>
* Garbage collection list and FAQ:<br>
@@ -152,7 +119,7 @@
The ECMA runtime and the .NET runtime assume an IO model and a
threading model that is very similar to the Win32 API.
Dick Porter has developed WAPI: the Mono abstraction layer
Dick Porter has been working on the Mono abstraction layer
that allows our runtime to execute code that depend on this
behaviour.
@@ -181,8 +148,7 @@
as well as talking to system libraries.
Initially we used libffi, but it was fairly slow, so we have
reused parts of the JIT work to create efficient PInvoke
trampolines.
reused parts of the JIT work to create efficient PInvoke trampolines.
** Remoting
-229
View File
@@ -1,229 +0,0 @@
* Screenshots
** Mono Debugger
Some shots of the <a href="jit-debug.html">Mono Debugger</a>
<table border=1>
<tr>
<td>
<a href="images/Screenshot-Debugger-1.png"><img src="images/Screenshot-Debugger-1-thumb.png"></a>
</td>
</tr>
<tr>
Debugger showing the source code view.
</tr>
</table>
<table>
<tr>
<td>
<a href="images/Screenshot-Debugger-2.png"><img src="images/Screenshot-Debugger-2-thumb.png"></a>
</td>
</tr>
<tr>
Debugger showing the CPU view.
</tr>
</table>
** Mono Documentation Browser
The Mono Documentation Browser is available from <a
href="anoncvs.html">CVS</a>, module `monodoc'.
<table border=1>
<tr>
<td>
<a href="images/Screenshot-B2.png"><img src="images/Screenshot-B2-thumb.png"></a>
</td>
</tr>
<tr>
Mono Documentation Browser rendering a method description.
</tr>
</table>
<table>
<tr>
<td>
<a href="images/Screenshot-MethodSummary.png"><img src="images/Screenshot-MethodSummary-thumb.png"></a>
</td>
</tr>
<tr>
Mono Documentation Browser rendering the class method summary
</tr>
</table>
** Eclipse running with Mono
Zoltan Varga made the Java VM for .NET <a
href="http://www.ikvm.net">IKVM</a> run <a
href="http://www.eclipse.org">Eclipse</a>, the IBM Open Source IDE.
<a href="images/ikvm-screenshot.png"><img src="images/ikvm-screenshot-thumb.png"></a>
** Mono Basic
The Mono Basic compiler ships with the Mono distribution.
<table border=1>
<tr>
<td>
<a href="images/gtk-vb.png"><img src="images/gtk-vb-thumb.png"></a>
</td>
</tr>
<tr>
Mono Basic running a sample Gtk# application.
</tr>
</table>
** Platano Media Player
Alp's <a href="http://www.atoker.com/platano/">Platano</a>
Media Player is written with Gtk# (with GStreamer support):
<table border=1>
<tr>
<td>
<img src="images/platano_s.png"></a>
</td>
</tr>
<tr>
Platano startup.
</tr>
</table>
<table>
<tr>
<td>
<img src="images/platano-playing_s.png">
</td>
</tr>
<tr>
Platano playing the <a
href="http://developer.ximian.com/projects/third_party/codemonkey/index.html">Code
Monkey At Work</a> video.
</tr>
</table>
** GSIRC
Alp's <a href="http://www.atoker.com/gsirc/">GSIRC</a>
Gtk-Sharp IRC written with Gtk#
<table border=1>
<tr>
<td>
<a href="http://go-mono.com/images/gsirc-0.2a_overview.jpg"><img src="images/gsirc-0.2a_overview-thumb.jpg"></a>
</td>
</tr>
<tr>
GSIRC is shown with the preferences dialog and chatting on some channels (rooms).
</tr>
</table>
** SQL# For GTK#
Daniel Morgan's SQL query tool that runs on Mono on Linux and Windows. It is
written in C# and allows you to connect to various Mono ADO.NET providers and
enter SQL commands.
<table border=1>
<tr>
<td>
<img src="http://go-mono.com/images/sqlsharp.png">
</td>
</tr>
<tr>
SQL# For GTK# is shown retrieving data from a Microsoft SQL Server 2000 database.
</tr>
</table>
** Type Reflector
Type Reflector is a tool included in Mono to inspect your assemblies.
<table border=1>
<tr>
<td>
<img src="images/type-reflector.png">
</td>
</tr>
</table>
** Object Browser
Radek Doulik's Object Browser (in Mono CVS) is a useful tool
to inspect existing assemblies and their source code:
<table border=1>
<tr>
<td>
<img src="images/Screenshot-ObjectBrowserDemo.png">
</td>
</tr>
</table>
** Windows.Forms
Windows.Forms running with Wine on Linux:
<table border=1>
<tr>
<td>
<a href="http://go-mono.com/images/monomdi.jpg"><img src="http://go-mono.com/images/monomdi-thumb.jpg"></a>
</td>
</tr>
</table>
<table border=1>
<tr>
<td>
<a href="http://go-mono.com/images/WINESWF.JPG"><img src="http://go-mono.com/images/WINESWF-thumb.JPG"></a>
</td>
</tr>
</table>
** Mono running on the iPaq
<table border=1>
<tr>
<td>
<img src="images/familiar-mint-hello.png">
</td>
</tr>
</table>
** Mono Certificate Viewer
<table border=1>
<tr>
<td>
<img src="images/swf-certview.png">
</td>
</tr>
<tr>
<td>
running on Windows using SWF
</td>
</tr>
<tr>
<td>
<img src="images/gtk-certview.png">
</td>
</tr>
<tr>
<td>
running on Linux (RH9) using GTK#
</td>
</tr>
</table>
** SkyNET
SkyNET is written in C# and uses GTK# for displaying a star chart.
<table border=1>
<tr>
<td>
<img src="http://go-mono.com/images/skynet.png">
</td>
</tr>
</table>
+12 -87
View File
@@ -18,12 +18,7 @@
<li>Uses TDS Protocol Version 7.0</li>
<li>Bugs with Mono or the data provider should be reported
in Mono's Bugzilla <a href="http://bugzilla.ximian.com/">here</a>. If you
do not have Bugzilla user account, it is free
and easy to
create one <a href="http://bugzilla.ximian.com/createaccount.cgi">here</a>.</li>
<li>Does not support trusted connections</li>
</ul>
@@ -31,14 +26,11 @@
<ul>
<li>Thanks to Sebastien Pouliot, we now have NT Authentication (Integrated Security) support. This support was
added after the release of Mono 0.29. So, you either get it from cvs or wait for the Mono 0.30 release.</li>
<li>Able to connect to Microsoft SQL Server 7/2000 databases via SQL Server authentication and NT Authentication.</li>
<li>Able to connect to Microsoft SQL Server 7/2000 databases</li>
<li>Connection pooling works.</li>
<li>Stored Procedures work.</li>
<li>Stored Procedures work</li>
<li>Parameters work.</li>
@@ -62,19 +54,15 @@
<li>Uses TDS Protocol Version 7.0</li>
<li>Works in the SQL# command-line and GTK# GUI version</li>
<li><a href="http://www.go-mono.com/tds-providers.html">Design of the Microsoft SQL Server, Sybase, and TDS Providers in Mono</a></li>
</ul>
** Action plan
<ul>
<li>Connection timeouts is being developed now</li>
<li>Needs more testing</li>
<li>Start work on TDS Protocol Version 8.0 support</li>
<li>Add support for .NET 1.2 and 2.0 and Microsoft SQL Server (Yukon) support</li>
<li>Connection timeouts is being developed now.
<li>Needs more testing...
</ul>
@@ -90,71 +78,9 @@
</ul>
</li>
<li><b>IMPORTANT:</b> If using Microsoft SQL Server 2000, make sure
you are using at least Service Pack 3 for Microsoft SQL Server 2000. If using
MSDE 2000, make sure you have the special Service Pack 3 for MSDE 2000. You
can get it from <a href="http://www.microsoft.com/sql/downloads/2000/sp3.asp">here</a></li>
<li>For those that only have MSDE installed. You can change the authentication mode
from Windows Only Authentication to SQL Server and Windows Authentications (also knows as Mixed-mode authentication)
via the <a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;Q322336&sd=tech#4">registry</a></li>. It is
the LoginMode you need to change. By default,
MSDE is installed with Windows Only Authentication. For SqlClient to work with MSDE, you will
need to change the setting.</a>
<li>If using MSDE, you might need to create a new user with password. Give
this user access to various databases in this MSDE instance. Also, for each
database, give this new user at least SELECT access to the various tables you want
to retrieve data from.</li>
<li>If you have Enterprise Manager, you can easily change the authentication mode
for both MSDE and Microsoft SQL Server. To change the authentication mode in
Enterprise Mananger, select the instance, right-click on it, and select properites.
The SQL Server properties dialog for that instance will pop up. Choose the Security
tab. Change the authentication from Windows Only to SQL Server and Windows. If
the instance of your database does not show up in Enterprise Manager, Register first
by selecting the Action menu and choosing New SQL Server Registration.</li>
<li>Located at mcs/class/System.Data/Test is a test for System.Data.SqlClient
named SqlTest.cs and you could use this as a basis for your test.</li>
<li>Mono's SqlClient does not support trusted connections
nor integrated security. You can not use this when connecting. You need
to explicitly use a User ID and Password
authenticated by SQL Server.</li>
<li>Has a connection string format for SQL Server Authentication:
<pre>
Server=hostname;Database=databaseName;User ID=userid;Password=password
</pre>
</li>
<li>Has a connection string format for NT Authentication:
<pre>
Server=hostname;Database=databaseName;User ID=windowsUserid;Password=windowsPassword;Integrated Security=SSPI
</pre>
</li>
<li>The Server part can be used three ways:
<table border=1>
<tr>
<td><b>Server Definition</b></td> <td><b>Example</b></td>
</tr>
<tr>
<td>hostname</td> <td>Server=MYHOST</td>
</tr>
<tr>
<td>hostname,port</td> <td>Server=MYHOST,1433</td>
</tr>
<tr>
<td>hostname\\instance</td> <td>Server=MYHOST\\NETSDK</td>
</tr>
</table>
</li>
<li>C# Example:
<pre>
using System;
@@ -168,20 +94,19 @@
string connectionString =
"Server=localhost;" +
"Database=pubs;" +
"User ID=myuserid;" +
"Password=mypassword;";
"User ID=sa;" +
"Password=;";
IDbConnection dbcon;
dbcon = new SqlConnection(connectionString);
dbcon.Open();
IDbCommand dbcmd = dbcon.CreateCommand();
string sql =
"SELECT fname, lname " +
"FROM employee";
dbcmd.CommandText = sql;
dbcmd.ConnectionString = sql;
IDataReader reader = dbcmd.ExecuteReader();
while(reader.Read()) {
string FirstName = (string) reader["fname"];
string LastName = (string) reader["lname"];
string FirstName = reader["fname"];
string LastName = reader["lname"];
Console.WriteLine("Name: " +
FirstName + " " + LastName);
}
+9 -40
View File
@@ -1,38 +1,13 @@
* SQL Lite Data Provider
<ul>
<li>ADO.NET Data Provider for
the <a href"http://www.hwaci.com/sw/sqlite/">SQL Lite</a> which
is an embeddable SQL database engine</li>
<li>From the SQL Lite web page: SQLite is a C library that
implements an embeddable SQL database engine. Programs that link with
the SQLite library can have SQL database access without
running a separate RDBMS process. The distribution
comes with a standalone command-line access program (sqlite) that
can be used to administer an SQLite database and which serves
as an example of how to use the SQLite library. SQLite is not a client library
used to connect to a big database server. SQLite is the server. The SQLite
library reads and writes directly to and from the database files on disk.</li>
<li>SQL Lite can be downloaded
from <a href"http://www.hwaci.com/sw/sqlite/download.html">here</a>.
binaries exist for Linux and Windows. sqlite.dll on Windows
and sqlite.so on Linux. The source code is available too.</li>
<li>Exists in namespace and assembly Mono.Data.SqliteClient</li>
<li>Created by Vladimir Vukicevic so he could have a database of
thumbnail images for mPhoto. mPhoto is GUI application
for cataloging images. mPhoto runs on Mono
and uses <a href="http://www.go-mono.com/gtk-sharp.html">GTK#</a> for its GUI.</li>
<li>Bugs with Mono or the data provider should be reported
in Mono's Bugzilla <a href="http://bugzilla.ximian.com/">here</a>. If you
do not have Bugzilla user account, it is free
and easy to
create one <a href="http://bugzilla.ximian.com/createaccount.cgi">here</a>.</li>
<li>Created by Vladimir Vukicevic</li>
<li><a href"http://www.hwaci.com/sw/sqlite/download.html">SQL Lite</a>
binaries exist for Linux and Windows. sqlite.dll on Windows
and sqlite.so on Linux.</li>
</ul>
** Current Status
@@ -57,19 +32,14 @@
<ul>
<li>Have a working mcs and mono</li>
<li>Make sure Mono.Data.SqliteClient.dll was built and is installed
in the same place as the mono class libraries.</li>
<li>If you do not have <a href"http://www.hwaci.com/sw/sqlite/download.html">SQL Lite</a>,
download it. There are binaries for Windows and Linux.</li>
<li>There is a test named SqliteTest.cs found at mcs/class/Mono.Data.SqliteTest/Test</li>
<li>Has a connection string format of "URI=file:some/path". For example,
the connection string "URI=file:SqliteTest.db" will use the database file
named SqliteTest.db, if it does not exist, the file will be created.</li>
<li>C# Example:
<pre>
using System;
@@ -82,8 +52,7 @@
{
string connectionString = "URI=file:SqliteTest.db";
IDbConnection dbcon;
dbcon = new SqliteConnection(connectionString);
dbcon.Open();
dbcon = new MySQLConnection(connectionString);
IDbCommand dbcmd = dbcon.CreateCommand();
// requires a table to be created named employee
// with columns firstname and lastname
@@ -94,11 +63,11 @@
string sql =
"SELECT firstname, lastname " +
"FROM employee";
dbcmd.CommandText = sql;
dbcmd.ConnectionString = sql;
IDataReader reader = dbcmd.ExecuteReader();
while(reader.Read()) {
string FirstName = (string) reader[0];
string LastName = (string) reader[1];
string FirstName = reader[0];
string LastName = reader[1];
Console.WriteLine("Name: " +
FirstName + " " + LastName);
}
+7 -26
View File
@@ -17,14 +17,8 @@
<li>Requires the assembly Mono.Data.Tds.dll which implements the TDS protocol in 100% C#.</li>
<li>Uses TDS Protocol Version 5.0</li>
<li>Bugs with Mono or the data provider should be reported
in Mono's Bugzilla <a href="http://bugzilla.ximian.com/">here</a>. If you
do not have Bugzilla user account, it is free
and easy to
create one <a href="http://bugzilla.ximian.com/createaccount.cgi">here</a>.</li>
<li>Does not support trusted connections</li>
</ul>
** Current Status
@@ -71,18 +65,6 @@
<li>Located at mcs/class/System.Data/Test is a test for System.Data.SqlClient
named SqlTest.cs and you could use this as a basis for your test.</li>
<li>Has a connection string format:
<pre>
Server=hostname;Database=databaseName;User ID=userid;Password=password
</pre>
</li>
<li>The Server part can be used two ways:
<ul>
<li>hostname - "Server=MYHOST"</li>
<li>hostname,port - "Server=MYHOST,1533"</li>
</ul>
</li>
<li>C# Example:
<pre>
using System;
@@ -96,20 +78,19 @@
string connectionString =
"Server=localhost;" +
"Database=pubs;" +
"User ID=myuserid;" +
"Password=mypassword;";
"User ID=sa;" +
"Password=;";
IDbConnection dbcon;
dbcon = new SybaseConnection(connectionString);
dbcon.Open();
IDbCommand dbcmd = dbcon.CreateCommand();
string sql =
"SELECT fname, lname " +
"FROM employee";
dbcmd.CommandText = sql;
dbcmd.ConnectionString = sql;
IDataReader reader = dbcmd.ExecuteReader();
while(reader.Read()) {
string FirstName = (string) reader["fname"];
string LastName = (string) reader["lname"];
string FirstName = reader["fname"];
string LastName = reader["lname"];
Console.WriteLine("Name: " +
FirstName + " " + LastName);
}
+6 -26
View File
@@ -18,12 +18,7 @@
<li>Uses TDS Protocol Version 4.2 by default</li>
<li>Bugs with Mono or the data provider should be reported
in Mono's Bugzilla <a href="http://bugzilla.ximian.com/">here</a>. If you
do not have Bugzilla user account, it is free
and easy to
create one <a href="http://bugzilla.ximian.com/createaccount.cgi">here</a>.</li>
<li>Does not support trusted connections</li>
</ul>
** Current Status
@@ -70,24 +65,10 @@
<li><a href="http://www.sybase.com/downloads">Sybase</a></li>
</ul>
</li>
<li>If using Microsoft SQL Server 2000, make sure
you are using at least Service Pack 3 for Microsoft SQL Server 2000</li>
<li>Located at mcs/class/System.Data/Test is a test for System.Data.SqlClient
named SqlTest.cs and you could use this as a basis for your test.</li>
<li>Has a connection string format:
<pre>
Server=hostname;Database=databaseName;User ID=userid;Password=password
</pre>
</li>
<li>The Server part can be used two ways:
<ul>
<li>hostname - "Server=MYHOST"</li>
<li>hostname,port - "Server=MYHOST,1533"</li>
</ul>
</li>
<li>C# Example:
<pre>
using System;
@@ -101,20 +82,19 @@
string connectionString =
"Server=localhost;" +
"Database=pubs;" +
"User ID=myuserid;" +
"Password=mypassword;";
"User ID=sa;" +
"Password=;";
IDbConnection dbcon;
dbcon = new TdsConnection(connectionString);
dbcon.Open();
IDbCommand dbcmd = dbcon.CreateCommand();
string sql =
"SELECT fname, lname " +
"FROM employee";
dbcmd.CommandText = sql;
dbcmd.ConnectionString = sql;
IDataReader reader = dbcmd.ExecuteReader();
while(reader.Read()) {
string FirstName = (string) reader["fname"];
string LastName = (string) reader["lname"];
string FirstName = reader["fname"];
string LastName = reader["lname"];
Console.WriteLine("Name: " +
FirstName + " " + LastName);
}
+2
View File
@@ -0,0 +1,2 @@
* The MonoNet Team
+52 -135
View File
@@ -6,26 +6,7 @@
is very common to introduce bugs in existing code. A test suite
helps us fix the bugs as soon as they are introduced.
There are various kinds of tests in Mono:
<ul>
<li><a href="#unit"><b>Class Library Unit
Tests:</b></a> These are used to test the class
libraries.
<li><a href="#compiler"><b>Compiler tests</b></a>: Both
tests that should pass and tests that should fail are included.
<li><a href="#runtime"><b>Runtime tests</b></a>: Tests for
the virtual machine.
<li><a href="#aspnet"><b>ASP.NET tests</b></a>: ASP.NET tests.
<li><a href="#ws"><b>Web Services tests</b></a>: Web Services
client/server tests.
</ul>
<a name="unit"></a>
* Class Library Tests
** Class Library Tests
All classes in Mono libraries should have comprehensive unit test
suites to go with them. Unit testing is a software engineering
@@ -34,29 +15,6 @@
that they work correctly. Mono also needs a testing framework
to make it easy to write and run lots of tests.
In some classes, we might also provide standalone tests because of
some reasons such as too huge testcases, another downloading and so on.
(For example, managed XSLT has standalone test which downloads and
expands some megabytes of OASIS test suite.)
Here I list them up as long as I know. If you are going to add another
standalone tests, please add one line here. It is also recommended that
you add some notes on how to build and run tests.
<ul>
* Mono.Data/test/
* System.Data/Test, and some individual ADO.NET libraries:
there are some standalone tests. See the bottom of <a href="ado-net.html">
ADO.NET page</a> for detail.
* System.Web/Test/TestMonoWeb : see README
* System.Web.Services/Test/standalone : see README
* System.Windows.Forms/SWFTest/
* System.XML/Tests/System.Xml.Schema/standalone_tests : see README
* System.XML/System.Xml.Serialization/standalone_tests/
* System.XML/Tests/System.Xml.Xsl/standalone_tests : see README
</ul>
** Getting started
@@ -66,7 +24,7 @@
<b>mcs/class/doc/TemplateTest.cs</b>
Save a copy of this file in the appropriate test subdirecty
(see below), and replace all the {text} markers with
(see below), and replace all the [text] markers with
appropriate code. Comments in the template are there to guide
you. You should also look at existing tests to see how other
people have written them.
@@ -83,22 +41,29 @@
the appropriate sub-directory under Test for the class you are
testing.
Once your test class is complete, you need to add it to the
AllTests.cs file in the same directory as your new test. Add a
call to "suite.AddTest()" passing the name of your new test
class's suite property as the parameter. You will see
examples in the AllTests.cs file, so just copy and paste
inside there.
Once all of that is done, you can do a 'make test' from the top mcs
directory. Your test class needs also to be listed in the
.sources file at the top of the Test directory.
directory. Your test class will be automagically included in the
build and the tests will be run along with all the others.
* Tips on writing Unit tests.
You should look at the <a href="http://nunit.org">NUnit documentation</a>,
as it is a fantastic product, and includes fantastic documentation,
but here are some tips for those of you who are already reading
You should look at the NUnit documentation, as it is a
fantastic product, and includes fantastic documentation, but
here are some tips for those of you who are already reading
this web page.
** Provide an unique error message for Assert()
Include an unique message for each Assert() so that when the assert
fails, it is trivial to locate it in the source. Otherwise, it may be
fails, it is trivial to locate the failing one. Otherwise, it may be
difficult to determine which part of the test is failing. A good way
to ensure unique messages is to use something like #A01, #A02 etc.
@@ -139,10 +104,43 @@
AssertEquals ("A01", myTicks[0], t1.Ticks);
</pre>
** Constructors
When writing your testcase, please make sure to provide a constructor
which takes no arguments:
<pre>
public class DateTimeTest : TestCase
{
public DateTimeTest() : base ("[MonoTests.System.DateTimeTest]") {}
public DateTimeTest (string name): base(name) {}
public static ITest Suite
{
get {
TestSuite suite = new TestSuite ();
return suite;
}
}
}
</pre>
** Namespace
Please keep the namespace within each test directory consistent - all
tests which are referenced in the same AllTests.cs must be in the same
namespace. Of course you can use subnamespaces as you like -
especially for subdirectories of your testsuite.
For instance, if your AllTests.cs is in namespace "MonoTests" and you
have a subdirectory called "System", you can put all the tests in that
dir into namespace "MonoTests.System".
** Test your test with the Microsoft runtime
If possible, try to run your testsuite with the Microsoft runtime on
.NET on Windows and make sure all tests in it pass. This is especially
Windows and make sure all tests in it pass. This is especially
important if you're writing a totally new testcase - without this
check you can never be sure that your testcase contains no bugs ....
@@ -153,10 +151,9 @@
result when run with the Microsoft runtime - either because there is a
bug in their runtime or something is misleading or wrong in their
documentation. In this case, please put a detailed description of the
problem to mcs/class/doc/API-notes and do also report it to the
<a href="mailing-lists.html">mailing list</a> - we'll forward this to the
Microsoft people from time to time to help them fix their documentation
and runtime.
problem to mcs/class/doc/API-notes and do also report it to the list -
we'll forward this to the Microsoft people from time to time to help
them fix their documentation and runtime.
** Unit tests.
@@ -187,83 +184,3 @@
Normally, after you send a couple of well-written new files
and/or patches to the list, you will be given cvs access.
<a name="compiler"></a>
* Compiler tests
Mono ships with three compilers: C#, VB.NET and JScript. The
tests are ran by running the makefile target `make
run-test-local' in the appropriate directory.
The C# compilation tests live in mcs/tests, and the C# error
tests live in mcs/errors.
The VB.NET compilation tests live in mcs/btests.
<a name="runtime"></a>
* Runtime Tests
These tests verify the virtual machine, to run these tests, do:
<pre>
cd mono/mono/tests
make test
</pre>
<a name="aspnet"></a>
* ASP.NET tests
XSP, the Mono ASP.NET server has tests for ASP.NET pages. It uses
<a href="http://nunitasp.sourceforge.net">NUnitAsp</a>. Right now
it only has standalone tests, ie., tests that do not need their own
global.asax or web.config files.
If you want to run them, get the xsp CVS module and install it. Then:
<pre>
cd xsp/nunit-tests
make
cd standalone
xsp
</pre>
And from another terminal:
<pre>
cd xsp/nunit-tests/standalone
nunit-console standalone-tests.dll
</pre>
<a name="ws"></a>
* Web Services tests
The Test directory for the System.Web.Services assembly contains a
standalone test suite for testing web services. It tests:
<ul>
<li>Proxy generation using the wsdl tool</li>
<li>Access to web services using the generated client proxies</li>
<li>Execution of web services in the server</li>
</ul>
This suite not only tests web services running on XSP, but it can also test
services running on other platforms and that are available in internet. This
will help track down interoperability issues.
To build the test suite, just run:
<pre>
cd mcs/class/System.Web.Services/Test/standalone
xsp --root server
</pre>
And from another terminal:
<pre>
cd mcs/class/System.Web.Services/Test/standalone
make
nunit-console testclient.dll
</pre>
This will download the wsdl documents, generate the proxies, build a dll with
the proxies, and build the nunit tests. Then you can use nunit-console or
gnunit to run the tests (the nunit dll is testclient.dll).
Read the README file in mcs/class/System.Web.Services/Test/standalone for
more info.
+1 -53
View File
@@ -1,53 +1 @@
** System.Windows.Forms
Progress on Windows.Forms has been good, but we need more work
on this area. Currently redrawing of controls is not
funcional.
** Languages work
Mono has work-in-progress implementations of JScript and the
VB.NET languages
<ul>
<li>Write positive tests for those languages.
<li>Write negative tests for those languages.
<li>Mono-devel-list is the mailing list to discuss
improvements and fixes to those compilers.
</ul>
** Debugger
<ul>
<li>The Mono debugger needs some better widgets to
provide a useful environment, many of those have been
authored for Anjuta/gIDE, we should wrap those for the
debugger
<li>Design a small tool-command-language like Tcl to
build the debugger on top of it.
<li>Design work: a new UI design must be done
for the debugger and later implemented.
</ul>
** Research topics
<ul>
<li>Design and implement a command processor like the
Unix shell, but which uses .NET objects as commands.
This shell would be a CLS consumer ideally, and only
later a CLS producer. This should make it simple for
people to explore the .NET API interactively.
</ul>
** IDE development
Mono lacks an IDE, and we depend on third-parties to work on
these.
<ul>
Sharp
</ul>
Discuss with write new JIT
+2 -17
View File
@@ -1,12 +1,5 @@
0,Home,index.html,index.src
1,Roadmap,mono-roadmap.html
1,FAQ,faq.html,faq.src
1,News archive,http://monoevo.sf.net/mwn/archives.html
1,Screenshots,screenshots.html,screenshots.src
1,Team,team.html,team.src
1,Other sites,other.html,other.src
1,Old News,oldnews.html,oldnews.src
1,Bug Reporting,bugs.html,bugs.src
0,Mono,rationale.html,rationale.src
1,Runtime,runtime.html,runtime.src
2,Embedding,embedded-api.html,embedded-api.src
@@ -19,14 +12,12 @@
0,Download,download.html,download.src
1,CVS access,ccvs.html,ccvs.src
1,AnonCVS access,anoncvs.html,anoncvs.src
1,Forge,forge.html,forge.src
1,Compiling,compiling.html,compiling.src
0,Contributing,contributing.html,contributing.src
1,Hackers,hackers.html,hackers.src
1,Documentation,documentation.html,documentation.src
1,Class Docs,classlib-doc.html,classlib-doc.src
1,Doc format,monodoc-xml.html,monodoc-xml.src
1,Test Suite,testing.html,testing.src
1,Mono TODO,mono-todo.html,mono-todo.src
1,Tools,tools.html,tools.src
1,Porting,porting.html,porting.src
2,PowerPC,ppc.html,ppc.src
@@ -34,7 +25,6 @@
0,Resources,resources.html,resources.src
1,Beginning,mono-beginning.html,mono-beginning.src
1,Mailing Lists,mailing-lists.html,mailing-lists.src
1,Blogs,http://www.go-mono.com/monologue/
1,Ideas,ideas.html,ideas.src
1,Passport,passport.html,passport.src
1,Books,books.html,books.src
@@ -42,9 +32,7 @@
1,Languages,languages.html,languages.src
1,Debugging,jit-debug.html,jit-debug.src
0,Plans,plans.html,plans.src
1,Drawing,drawing.html,drawing.src
1,ADO.NET,ado-net.html,ado-net.src
2,ProviderFactory,provider-factory.html,provider-factory.src
2,Firebird Interbase,firebird.html,firebird.src
2,IBM DB2,ibmdb2.html,ibmdb2.src
2,Microsft SQL Server,sqlclient.html,sqlclient.src
@@ -56,11 +44,9 @@
2,SQL Lite,sqlite.html,sqlite.src
2,Sybase,sybase.html,sybase.src
2,TDS Generic,tdsclient.html,tdsclient.src
2,TDS Providers,tds-providers.html,tds-providers.src
1,Crypto,crypto.html,crypto.src
1,Java,java.html,java.src
1,Windows.Forms,winforms.html,winforms.src
1,XML Classes,xml-classes.html,xml-classes.src
0,Class Status,class-status.html,class-status.src,cm/cormissing.css,cm/cormissing.js
1,corlib,class-status-corlib.html,class-status-corlib.src,cm/cormissing.css,cm/cormissing.js
1,System,class-status-System.html,class-status-System.src,cm/cormissing.css,cm/cormissing.js
@@ -71,8 +57,7 @@
1,Web.Services,class-status-System.Web.Services.html,class-status-System.Web.Services.src,cm/cormissing.css,cm/cormissing.js
1,Microsoft.VisualBasic,class-status-Microsoft.VisualBasic.html,class-status-Microsoft.VisualBasic.src,cm/cormissing.css,cm/cormissing.js
1,Windows.Forms,class-status-System.Windows.Forms.html,class-status-System.Windows.Forms.src,cm/cormissing.css,cm/cormissing.js
1,DirectoryServices,class-status-System.DirectoryServices.html,class-status-System.DirectoryServices.src,cm/cormissing.css,cm/cormissing.js
1,EnterpriseServices,class-status-System.EnterpriseServices.html,class-status-System.EnterpriseServices.src,cm/cormissing.css,cm/cormissing.js
1,Formatters.Soap,class-status-System.Runtime.Serialization.Formatters.Soap.html,class-status-System.Runtime.Serialization.Formatters.Soap.src,cm/cormissing.css,cm/cormissing.js
1,Cscompmgd,class-status-Cscompmgd.html,class-status-Cscompmgd.src,cm/cormissing.css,cm/cormissing.js
1,System.Security,class-status-System.Security.html,class-status-System.Security.src,cm/cormissing.css,cm/cormissing.js
0,Contact,contact.html,contact.src
+1 -4
View File
@@ -212,13 +212,10 @@ function clickHandler (evt)
if (evt.ctrlKey)
{
var strRoot = 'http://cvs.hispalinux.es/cgi-bin/cvsweb/mcs/class/';
var strExtra = '?cvsroot=mono';
var strExtra = '?cvsroot=Mono';
if (strAssembly)
{
if (strAssembly == 'mscorlib')
strAssembly = 'corlib';
strRoot = strRoot + strAssembly + '/';
if (strNamespace)
{
Binary file not shown.

Before

Width:  |  Height:  |  Size: 32 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 14 KiB

-1
View File
@@ -1 +0,0 @@
*.xml
+65 -118
View File
@@ -1,94 +1,75 @@
ifeq ($(findstring CYGWIN,$(shell uname)),)
CSC=mcs
RUN_MONO=mono
else
CSC=csc /nologo
endif
CSCRIPT = $(SYSTEMROOT)/system32/cscript.exe
CSC=csc
CORCOMPARE=../../../mcs/tools/corcompare
OBJECTS= \
deploy/ado-net.html \
deploy/anoncvs.html \
deploy/asp-net.html \
deploy/blogs.html \
deploy/books.html \
deploy/bugs.html \
deploy/contributing.html \
deploy/contact.html \
deploy/c-sharp.html \
deploy/ccvs.html \
deploy/documentation.html \
deploy/download.html \
deploy/drawing.html \
deploy/compiling.html \
deploy/crypto.html \
deploy/embedded-api.html \
deploy/faq.html \
deploy/firebird.html \
deploy/forge.html \
deploy/gcc-frontend.html \
deploy/gtk-sharp.html \
deploy/hackers.html \
deploy/ideas.html \
deploy/ibmdb2.html \
deploy/index.html \
deploy/oldnews.html \
deploy/java.html \
deploy/jit-debug.html \
deploy/languages.html \
deploy/mailing-lists.html \
deploy/mbas.html \
deploy/mono-beginning.html \
deploy/mono-contribution-howto.html \
deploy/mono-todo.html \
deploy/monodoc-xml.html \
deploy/mysql.html \
deploy/odbc.html \
deploy/oledb.html \
deploy/oracle.html \
deploy/other.html \
deploy/postgresql.html \
deploy/sqlclient.html \
deploy/sqlite.html \
deploy/sybase.html \
deploy/tdsclient.html \
deploy/anoncvs.html \
deploy/asp-net.html \
deploy/books.html \
deploy/contributing.html \
deploy/class-status.html \
deploy/class-status-corlib.html \
deploy/class-status-System.html \
deploy/class-status-System.Xml.html \
deploy/class-status-System.Drawing.html \
deploy/class-status-System.Data.html \
deploy/class-status-System.Web.html \
deploy/class-status-System.Web.Services.html \
deploy/class-status-Microsoft.VisualBasic.html \
deploy/class-status-System.EnterpriseServices.html \
deploy/class-status-System.Runtime.Serialization.Formatters.Soap.html \
deploy/class-status-System.Windows.Forms.html \
deploy/class-status-Cscompmgd.html \
deploy/class-library.html \
deploy/classlib-doc.html \
deploy/contact.html \
deploy/c-sharp.html \
deploy/mbas.html \
deploy/ccvs.html \
deploy/documentation.html \
deploy/download.html \
deploy/crypto.html \
deploy/embedded-api.html \
deploy/faq.html \
deploy/gcc-frontend.html \
deploy/hackers.html \
deploy/index.html \
deploy/ideas.html \
deploy/java.html \
deploy/jit-debug.html \
deploy/jit-debug-sample.html \
deploy/jit-debug-sample2.html \
deploy/languages.html \
deploy/mailing-lists.html \
deploy/mono-beginning.html \
deploy/mono-contribution-howto.html \
deploy/monodoc-xml.html \
deploy/papers.html \
deploy/passport.html \
deploy/plans.html \
deploy/porting.html \
deploy/postgresql.html \
deploy/ppc.html \
deploy/provider-factory.html \
deploy/rationale.html \
deploy/resources.html \
deploy/roadmap.html \
deploy/runtime.html \
deploy/screenshots.html \
deploy/sqlclient.html \
deploy/sqlite.html \
deploy/status.html \
deploy/sybase.html \
deploy/tdsclient.html \
deploy/tds-providers.html \
deploy/team.html \
deploy/testing.html \
deploy/tools.html \
deploy/winforms.html \
deploy/xml-classes.html \
deploy/class-library.html \
deploy/classlib-doc.html \
deploy/class-status.html \
deploy/class-status-corlib.html \
deploy/class-status-System.html \
deploy/class-status-System.Xml.html \
deploy/class-status-System.Data.html \
deploy/class-status-System.Security.html \
deploy/class-status-System.Web.html \
deploy/class-status-System.Web.Services.html \
deploy/class-status-System.Drawing.html \
deploy/class-status-Microsoft.VisualBasic.html \
deploy/class-status-System.Windows.Forms.html \
deploy/class-status-System.DirectoryServices.html \
deploy/class-status-Cscompmgd.html \
deploy/class-status-System.Runtime.Serialization.Formatters.Soap.html
HTML_SOURCES = ../mono-roadmap.html
deploy/winforms.html
#2,Configuration.Install,class-status-System.Configuration.Install.html,class-status-System.Configuration.Install.src,cm/cormissing.css,cm/cormissing.js
#2,Runtime.Remoting,class-status-System.Runtime.Remoting.html,class-status-System.Runtime.Remoting.src,cm/cormissing.css,cm/cormissing.js
@@ -99,11 +80,9 @@ NON_HTML_SOURCES= \
../mono-build.sh \
../mono-build-w32.sh
all: $(OBJECTS) deploy/index.rss ../team
all: $(OBJECTS) deploy/index.rss
perl process.pl commands template.html.in deploy
cp $(HTML_SOURCES) deploy
test -d deploy/team || mkdir deploy/team
cp team/*png deploy/team
tutorial: mono-beginning.html.stamp mono-beginning.pdf
cp -a mono-beginning mono-beginning.xml mono-beginning.pdf deploy
@@ -119,27 +98,18 @@ mono-beginning.xml: ../mono-beginning.xml
cp ../mono-beginning.xml .
deploy/index.rss: mono-rss.exe ../index
$(RUN_MONO) ./mono-rss.exe ../index deploy/index.rss
./mono-rss.exe ../index deploy/index.rss
mono-rss.exe: mono-rss.cs rss.cs
$(CSC) mono-rss.cs rss.cs
../team: render-team-page.exe team.xml
$(RUN_MONO) ./render-team-page.exe team.xml "../team"
render-team-page.exe: render-team-page.cs
$(CSC) render-team-page.cs
clean:
rm -f $(OBJECTS) $(patsubst deploy/%.html,src/%.src, $(OBJECTS)) src/*.xml src/*.html.in ../class-status-* ../class-status infos/*.xml
rm -f $(OBJECTS) $(patsubst deploy/%.html,src/%.src, $(OBJECTS)) src/*.xml src/*.html.in ../class-status-* ../class-status
push:
cp -f $(NON_HTML_SOURCES) deploy
cp ../mono-roadmap.html deploy
#echo scp -P 2200 -r deploy/* www@www.go-mono.com:/web/cvsmodules/mono
#(cd deploy; rsync --verbose --recursive --checksum --update --rsh='ssh' . [email protected]:/web/cvsmodules/mono )
(cd deploy; rsync --verbose --recursive --checksum --update --rsh='ssh' . [email protected]:/web/cvsmodules/mono )
echo scp -P 2200 -r deploy/* [email protected]:/web/cvsmodules/mono
(cd deploy; rsync --verbose --recursive --checksum --update --rsh='ssh -p 2200' . www@www.ximian.com:/web/cvsmodules/mono )
push2:
scp -r deploy/* primates:public_html/xxx
@@ -148,55 +118,32 @@ $(OBJECTS): $(patsubst deploy/%.html,src/%.src, $(OBJECTS))
#.PRECIOUS: $(patsubst deploy/%.html,src/%.src, $(OBJECTS))
transform.exe: transform.cs
$(CSC) transform.cs
.PRECIOUS: src/%.src
src/%.src: ../% commands template.html.in makefile
src/%.src: ../% commands makefile template.html.in
perl htmlify $< > $@
.PRECIOUS: ../class-status-%
../class-status-%: src/%.html.in ../class-status.in
cat ../class-status.in $< > $@
.PRECIOUS: src/%.html.in
src/%.html.in: src/%.xml transform.exe $(CORCOMPARE)/mono-api.xsl
$(RUN_MONO) ./transform.exe $< $(CORCOMPARE)/mono-api.xsl > $@ || (rm -f $@ && exit 1)
src/%.html.in: src/%.xml $(CORCOMPARE)/transform.js $(CORCOMPARE)/cormissing.xsl
$(CSCRIPT) /nologo $(CORCOMPARE)/transform.js $< $(CORCOMPARE)/cormissing.xsl > $@
.PRECIOUS: infos/%.xml
infos/%.xml: ../../../mcs/class/lib/%.dll $(CORCOMPARE)/mono-api-info.exe
$(RUN_MONO) $(CORCOMPARE)/mono-api-info.exe $< > $@ || (rm -f $@ && exit 1)
.PRECIOUS: src/%.xml
src/%.xml: infos/%.xml $(CORCOMPARE)/mono-api-diff.exe
$(RUN_MONO) $(CORCOMPARE)/mono-api-diff.exe masterinfos/$(notdir $<) $< > $@ || (rm -f $@ && exit 1)
src/%.xml: ../../../mcs/class/lib/%.dll $(CORCOMPARE)/CorCompare.exe
$(CORCOMPARE)/CorCompare.exe -x $@ $<
# corlib, corlib...
infos/mscorlib.xml: ../../../mcs/class/lib/mscorlib.dll $(CORCOMPARE)/mono-api-info.exe
$(RUN_MONO) $(CORCOMPARE)/mono-api-info.exe $(notdir $(basename $<)) > $@ || (rm -f $@ && exit 1)
src/corlib.xml: ../../../mcs/class/lib/corlib_cmp.dll $(CORCOMPARE)/CorCompare.exe
$(CORCOMPARE)/CorCompare.exe -f corlib -ms mscorlib -x $@ $<
src/corlib.xml: infos/mscorlib.xml $(CORCOMPARE)/mono-api-diff.exe
$(RUN_MONO) $(CORCOMPARE)/mono-api-diff.exe masterinfos/mscorlib.xml $< > $@ || (rm -f $@ && exit 1)
# System
infos/System.xml: ../../../mcs/class/lib/System.dll $(CORCOMPARE)/mono-api-info.exe
$(RUN_MONO) $(CORCOMPARE)/mono-api-info.exe $(notdir $(basename $<)) > $@ || (rm -f $@ && exit 1)
src/System.xml: infos/System.xml $(CORCOMPARE)/mono-api-diff.exe
$(RUN_MONO) $(CORCOMPARE)/mono-api-diff.exe masterinfos/System.xml $< > $@ || (rm -f $@ && exit 1)
# System.Xml
infos/System.Xml.xml: ../../../mcs/class/lib/System.Xml.dll $(CORCOMPARE)/mono-api-info.exe
$(RUN_MONO) $(CORCOMPARE)/mono-api-info.exe $(notdir $(basename $<)) > $@ || (rm -f $@ && exit 1)
src/System.Xml.xml: infos/System.Xml.xml $(CORCOMPARE)/mono-api-diff.exe
$(RUN_MONO) $(CORCOMPARE)/mono-api-diff.exe masterinfos/System.Xml.xml $< > $@ || (rm -f $@ && exit 1)
src/System.DirectoryServices.xml: infos/System.DirectoryServices.xml $(CORCOMPARE)/mono-api-diff.exe
$(RUN_MONO) $(CORCOMPARE)/mono-api-diff.exe masterinfos/System.DirectoryServices.xml $< > $@ || (rm -f $@ && exit 1)
../class-status: ../class-status.in
cp -f $< $@
-1
View File
@@ -1 +0,0 @@
*.xml
-60
View File
@@ -1,60 +0,0 @@
# Note that you will need Microsoft.NET to generate those masterinfos
# Customize to indicate your own installation dir.
DLL_PATH=c:/WINDOWS/Microsoft.NET/Framework/v1.1.4322
all: \
mscorlib.xml \
System.xml \
System.Xml.xml \
System.Data.xml \
System.Web.xml \
System.Web.Services.xml \
System.Runtime.Serialization.Formatters.Soap.xml \
System.Drawing.xml \
System.Security.xml \
System.DirectoryServices.xml \
System.Windows.Forms.xml \
Cscompmgd.xml
mscorlib.xml :
mono-api-info $(DLL_PATH)/mscorlib.dll > mscorlib.xml
System.xml :
mono-api-info $(DLL_PATH)/System.dll > System.xml
System.Xml.xml :
mono-api-info $(DLL_PATH)/System.Xml.dll > System.Xml.xml
System.Data.xml :
mono-api-info $(DLL_PATH)/System.Data.dll > System.Data.xml
System.Web.xml :
mono-api-info $(DLL_PATH)/System.Web.dll > System.Web.xml
System.Web.Services.xml :
mono-api-info $(DLL_PATH)/System.Web.Services.dll > System.Web.Services.xml
System.Runtime.Serialization.Formatters.Soap.xml :
mono-api-info $(DLL_PATH)/System.Runtime.Serialization.Formatters.Soap.dll > System.Runtime.Serialization.Formatters.Soap.xml
System.Drawing.xml :
mono-api-info $(DLL_PATH)/System.Drawing.dll > System.Drawing.xml
System.Security.xml :
mono-api-info $(DLL_PATH)/System.Security.dll > System.Security.xml
System.DirectoryServices.xml :
mono-api-info $(DLL_PATH)/System.DirectoryServices.dll > System.DirectoryServices.xml
System.Windows.Forms.xml :
mono-api-info $(DLL_PATH)/System.Windows.Forms.dll > System.Windows.Forms.xml
Cscompmgd.xml :
mono-api-info $(DLL_PATH)/Cscompmgd.dll > Cscompmgd.xml
clean:
rm mscorlib.xml System.xml System.Xml.xml System.Data.xml System.Web.xml System.Web.Services.xml System.Runtime.Serialization.Formatters.Soap.xml System.Drawing.xml System.Security.xml System.DirectoryServices.xml System.Windows.Forms.xml Cscompmgd.xml
+2 -12
View File
@@ -6,21 +6,18 @@
using System;
using System.IO;
using System.Xml;
using System.Text;
using RSS;
class X {
static RSS.RSS rss;
static Channel c;
static int item_count;
static int line;
static void PopulateRSS (StreamReader input)
{
string s;
while ((s = input.ReadLine ()) != null){
line++;
if (s.StartsWith ("@item "))
break;
}
@@ -52,11 +49,9 @@ class X {
i = c.NewItem ();
i.Title = title;
i.Link = link;
i.PubDate = s.Substring (6, s.IndexOf (":") - 6) + ", 2003";
} else {
description += "\n" + (s == "\n" ? "<p>" : s);
}
line++;
} while ((s = input.ReadLine ()) != null);
if (i != null){
@@ -81,12 +76,7 @@ class X {
using (FileStream fs = new FileStream (input, FileMode.Open)){
using (StreamReader input_stream = new StreamReader (fs)){
try {
PopulateRSS (input_stream);
} catch {
Console.WriteLine ("{0} failure while loading: {1}", line, input);
throw;
}
PopulateRSS (input_stream);
}
}
-352
View File
@@ -1,352 +0,0 @@
//
// RenderTeamPage.cs - Renders an HTML page with team member information from an XML file
//
// Author: Duncan Mak ([email protected])
//
// (C) Copyright 2003, Ximian Inc.
//
using System;
using System.Collections;
using System.IO;
using System.Text;
using System.Xml;
class Write {
static Contributor [] list;
static public XmlNamespaceManager nsmgr;
static void Main (string [] args)
{
if (args.Length != 2) {
Console.WriteLine ("write.exe <input.xml> <output.html>");
Environment.Exit (0);
}
string input = args [0];
string output = args [1];
XmlDocument document = new XmlDocument ();
document.Load (input);
nsmgr = new XmlNamespaceManager (document.NameTable);
nsmgr.AddNamespace ("t", "http://go-mono.org/team.xsd");
XmlNodeList contributors = document.SelectNodes ("/t:contributors/t:contributor", nsmgr);
list = new Contributor [contributors.Count];
Page p = new Page ();
int count = 0;
foreach (XmlNode n in contributors) {
list [count] = new Contributor (n, p.Document);
count ++;
}
Array.Sort (list, new ContributorComparer ());
int length = list.Length % 2 == 0 ? list.Length : list.Length + 1;
int i = 0;
while (i < length) {
try {
p.AddRow (list [i].RenderHtml (), list [i + 1].RenderHtml ());
} catch (IndexOutOfRangeException) {
p.AddRow (list [i].RenderHtml (), null);
}
i += 2;
}
p.Write (output);
}
}
public class ContributorComparer : IComparer
{
public int Compare (object x, object y)
{
return String.Compare (x.ToString (), y.ToString ());
}
}
class Contributor {
public Name name;
public string email;
public string image;
public string location;
public string organization;
public string description;
public string[] tasks;
public XmlDocument document;
public Contributor (XmlNode node, XmlDocument document)
{
name = GetName (node);
image = GetImage (node);
email = GetField (node, "t:e-mail");
location = GetField (node, "t:location");
organization = GetField (node, "t:organization");
description = GetField (node, "t:description");
tasks = GetTasks (node);
this.document = document;
}
public override string ToString ()
{
return name.ToString ();
}
public static string GetImage (XmlNode node)
{
string result = GetField (node, "t:image");
if (result == String.Empty)
return "none.png";
else
return result;
}
public static string GetField (XmlNode node, string selector)
{
XmlNode result = node.SelectSingleNode (selector, Write.nsmgr);
if (result == null)
return String.Empty;
return result.InnerText;
}
public static Name GetName (XmlNode node)
{
string first_name = GetField (node, "t:name/t:first-name");
string last_name = GetField (node, "t:name/t:last-name");
return new Name (first_name, last_name);
}
public static string [] GetTasks (XmlNode node)
{
XmlNodeList nodes = node.SelectNodes ("t:tasks/t:task", Write.nsmgr);
string [] result = new string [nodes.Count];
int i = 0;
foreach (XmlNode n in nodes) {
result [i] = n.InnerText;
i++;
}
return result;
}
public XmlElement RenderHtml ()
{
XmlElement root = document.CreateElement ("td");
XmlElement table = document.CreateElement ("table");
table.SetAttribute ("cellPadding", "0");
table.SetAttribute ("border", "0");
XmlElement tr = document.CreateElement ("tr");
XmlElement td = document.CreateElement ("td");
td.SetAttribute ("bgcolor", "#c3cda7");
td.SetAttribute ("valign", "top");
td.SetAttribute ("width", "1%");
tr.AppendChild (td);
table.AppendChild (tr);
root.AppendChild (table);
XmlElement img = document.CreateElement ("img");
img.SetAttribute ("align", "top");
img.SetAttribute ("border", "0");
img.SetAttribute ("height", "48");
img.SetAttribute ("width", "48");
img.SetAttribute ("src", "team/" + image);
td.AppendChild (img);
td = document.CreateElement ("TD");
td.SetAttribute ("bgcolor", "#c3cda7");
td.SetAttribute ("valign", "bottom");
td.SetAttribute ("width", "100%");
tr.AppendChild (td);
td.AppendChild (name.ToXml (document));
td.AppendChild (document.CreateElement ("br"));
td.AppendChild (RenderEmail ());
tr = document.CreateElement ("tr");
table.AppendChild (tr);
td = document.CreateElement ("td");
td.SetAttribute ("bgcolor", "#f5f8e4");
td.SetAttribute ("valign", "top");
tr.AppendChild (td);
td.AppendChild (RenderLabel ("Location: "));
td = document.CreateElement ("td");
td.SetAttribute ("bgcolor", "#f5f8e4");
td.SetAttribute ("valign", "top");
tr.AppendChild (td);
td.AppendChild (document.CreateTextNode (location));
tr = document.CreateElement ("tr");
table.AppendChild (tr);
td = document.CreateElement ("td");
td.SetAttribute ("bgcolor", "#f5f8e4");
td.SetAttribute ("valign", "top");
tr.AppendChild (td);
td.AppendChild (RenderLabel ("Description: "));
td = document.CreateElement ("td");
td.SetAttribute ("bgcolor", "#f5f8e4");
td.SetAttribute ("valign", "top");
tr.AppendChild (td);
td.AppendChild (document.CreateTextNode (description));
tr = document.CreateElement ("tr");
table.AppendChild (tr);
td = document.CreateElement ("td");
td.SetAttribute ("bgcolor", "#f5f8e4");
td.SetAttribute ("valign", "top");
tr.AppendChild (td);
td.AppendChild (RenderLabel ("Tasks: "));
td = document.CreateElement ("td");
td.SetAttribute ("bgcolor", "#f5f8e4");
td.SetAttribute ("valign", "top");
tr.AppendChild (td);
td.AppendChild (RenderTasks ());
return root;
}
public XmlNode RenderTasks ()
{
XmlElement element = document.CreateElement ("ol");
element.SetAttribute ("type", "I");
foreach (string task in tasks) {
XmlElement li = document.CreateElement ("li");
li.AppendChild (document.CreateTextNode (task));
element.AppendChild (li);
}
return element;
}
public XmlNode RenderEmail ()
{
XmlElement a = document.CreateElement ("a");
a.SetAttribute ("href", "mailto:" + email);
XmlElement font = document.CreateElement ("font");
font.SetAttribute ("size", "3");
XmlText t = document.CreateTextNode (email);
a.AppendChild (font);
font.AppendChild (t);
return a;
}
public XmlNode RenderLabel (string label)
{
string text = String.Format ("{0}: ", label);
XmlElement element = document.CreateElement ("b");
XmlText t = document.CreateTextNode (label );
element.AppendChild (t);
return element;
}
}
class Page {
XmlDocument document;
XmlElement tbody;
public Page ()
{
document = new XmlDocument ();
XmlElement table = document.CreateElement ("table");
document.AppendChild (table);
tbody = document.CreateElement ("tbody");
table.AppendChild (tbody);
}
public XmlDocument Document {
get { return document; }
}
public void AddRow (XmlNode left, XmlNode right)
{
if (left == null && right == null)
return;
XmlElement tr = document.CreateElement ("tr");
tbody.AppendChild (tr);
tr.AppendChild (left);
if (right == null)
tr.AppendChild (document.CreateElement ("td"));
else {
tr.SetAttribute ("valign", "top");
tr.AppendChild (right);
}
}
public void Write (TextWriter text_writer)
{
XmlTextWriter writer = new XmlTextWriter (text_writer);
writer.Formatting = Formatting.Indented;
document.WriteContentTo (writer);
writer.Flush ();
}
public void Write (string filename)
{
XmlTextWriter writer = new XmlTextWriter (filename, Encoding.Default);
writer.Formatting = Formatting.Indented;
document.WriteContentTo (writer);
writer.Flush ();
}
}
class Name {
string first_name;
string last_name;
public Name (string a, string b)
{
this.first_name = a;
this.last_name = b;
}
public override string ToString ()
{
if (first_name == null && last_name == null)
return String.Empty;
return first_name + " " + last_name;
}
public XmlNode ToXml (XmlDocument document)
{
XmlElement element = document.CreateElement ("font");
element.SetAttribute ("size", "3");
XmlElement b = document.CreateElement ("B");
XmlText t = document.CreateTextNode (ToString ());
b.AppendChild (t);
element.AppendChild (b);
return element;
}
}
+1 -16
View File
@@ -13,7 +13,7 @@ namespace RSS {
public class Item {
XmlDocument doc;
XmlNode item;
XmlText title, link, description, pubdate;
XmlText title, link, description;
public Item (XmlDocument doc, XmlNode item)
{
@@ -76,21 +76,6 @@ namespace RSS {
description.Value = value;
}
}
public string PubDate {
get {
if (pubdate == null)
return null;
return pubdate.Value;
}
set {
if (pubdate == null)
pubdate = MakeTextElement ("pubDate");
pubdate.Value = value;
}
}
}
public class Channel {
-1593
View File
File diff suppressed because it is too large. Load diff
-30
View File
@@ -1,30 +0,0 @@
<?xml version="1.0" encoding="iso-8859-1" ?>
<xs:schema id="contributors" targetNamespace="http://go-mono.org/team.xsd" xmlns="http://go-mono.org/team.xsd" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="contributor">
<xs:complexType>
<xs:sequence>
<xs:element name="name" minOccurs="0" maxOccurs="1">
<xs:complexType>
<xs:sequence>
<xs:element name="first-name" type="xs:string" minOccurs="0" maxOccurs="1" />
<xs:element name="last-name" type="xs:string" minOccurs="0" maxOccurs="1" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="e-mail" type="xs:string" minOccurs="0" maxOccurs="1" />
<xs:element name="image" type="xs:string" minOccurs="0" maxOccurs="1" />
<xs:element name="location" type="xs:string" minOccurs="0" maxOccurs="1" />
<xs:element name="organization" type="xs:string" minOccurs="0" maxOccurs="1" />
<xs:element name="description" type="xs:string" minOccurs="0" maxOccurs="1" />
<xs:element name="tasks" minOccurs="0" maxOccurs="1">
<xs:complexType>
<xs:sequence>
<xs:element name="task" type="xs:string" nillable="true" minOccurs="0" maxOccurs="unbounded" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
Binary file not shown.

Before

Width:  |  Height:  |  Size: 6.4 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 4.2 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 3.1 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 1.0 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 4.9 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 4.3 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 4.4 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 4.5 KiB

Loaded 100 of 7219 files, more files were not shown because too many files have changed in this diff. Show more