Compare commits

..
3 Commits
Author SHA1 Message Date
nobody 6f9059cfb8 This commit was manufactured by cvs2svn to create tag 'MCS_0_11'.
svn path=/tags/MCS_0_11/mcs/; revision=4034
2002-04-24 22:18:01 +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
8484 changed files with 171494 additions and 1135347 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
-818
View File
@@ -1,820 +1,3 @@
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
about IBM DB2 data provider at Mono.Data.DB2Client
* makefile
* commands: added ibmdb2 web page to go-mono web site
* doc/ado-net: added a couple more developers email, plus made the
email spam resistant, added Mono's DB2 data provider to list,
added more info about the ProviderFactory and retrieving data using
ADO.NET from ASP.NET, add notes about testing, misc cleanup
* doc/mysql
* doc/postgresql
* doc/sqlclient
* doc/oracle
* doc/tdsclient
* doc/firebird
* doc/oledb
* doc/odbc
* doc/sybase
* doc/sqlite: added testing notes and C# examples
* doc/gtk-sharp: added links for GTK# for Windows
* man/sqlsharp.1: added providers Npgsql and MySQLNet
2003-01-17 Duncan Mak <[email protected]>
* runtime/Makefile.am: Add the new Mono.Data.DB2Client.dll.
2003-01-16 Martin Baulig <[email protected]>
* configure.in (GTHREAD_LIBS, GTHREAD_CFLAGS): Removed the gthread
check again, we're now using the mono/io-layer for this.
Wed Jan 15 16:20:54 CET 2003 Paolo Molaro <[email protected]>
* configure.in: allow MacOSX (from various people).
2003-01-14 Martin Baulig <[email protected]>
* configure.in (GTHREAD_LIBS, GTHREAD_CFLAGS): Added check for gthread.
2002-12-27 Jeroen Janssen <[email protected]>
* fixed url for System.Windows.Forms in the class status
2002-12-18 Gonzalo Paniagua Javier <[email protected]>
* configure.in: moved struct tm field tm_gmtoff check before the check
for timezone global variable. This makes Timezone work for me (debian
sid, linux, x86, which has both the field and the global variables).
2002-12-10 Daniel Morgan <[email protected]>
* doc/oracle: added file which is
a new web page oracle.html
* doc/ado-net: clean up and add link
to oracle.html
* doc/web/commands
* doc/web/makefile: added oracle.html
2002-12-10 Daniel Morgan <[email protected]>
* man/Makefile.am: changed sqlsharpcli.1 to sqlsharp.1
* man/sqlsharpcli.1: renamed to sqlsharp.1
2002-12-09 Tim Haynes <[email protected]>
* mono/jit/jit.c
* mono/metadata/icall.c: added mono_install_get_config_dir() to
utilize the MONO_CFG_DIR environment variable for specifying
different machine.configs.
2002-12-06 Duncan Mak <[email protected]>
* data/Makefile.am (EXTRA_DIST): Add machine.config
(DISTCLEANFILES): Add config.
2002-11-30 Daniel Morgan <[email protected]>
* man/sqlsharpcli.1: added file - a man page
for SQL# CLI
* man/Makefile.am: added sqlsharpcli.1 to man_MANS
2002-11-20 Daniel Morgan <[email protected]>
* doc/firebird: updated web page
2002-11-19 Mike Kestner <[email protected]>
* data/Config.in : added the gtk# dll mapping entries
2002-11-19 Daniel Morgan <[email protected]>
* doc/firebird: updated web page based on input
from the firebird .net data provider author
Mon Nov 18 16:40:34 CET 2002 Paolo Molaro <[email protected]>
* configure.in, mono/os/gc_wrapper.h: check that the gc headers have
been installed.
2002-11-12 Daniel Morgan <[email protected]>
* doc/oledb
* doc/odbc
* doc/mysql
* doc/sqlite
* doc/sqlclient
* doc/tdsclient
* doc/sybase
* doc/firebird: added web pages
for each specific data provider
* doc/ado-net
* doc/postgresql: updated web page
with current status
* doc/web/commands
* doc/web/makefile: updated to include
new web pages
2002-11-06 Gonzalo Paniagua Javier <[email protected]>
* autogen.sh: make it work when MONO_PATH is set and it has more than
one directory or ends in ":". Also check that the directory added to
ACLOCAL_FLAGS and PATH exist (aclocal fails if they don't).
2002-10-22 Miguel de Icaza <[email protected]>
* configure.in: Also allow the miss-spelled bohem.
2002-10-18 Daniel Morgan <[email protected]>
* doc/ado-net
* doc/postgresql
* doc/tds-providers: cleaned up the web pages
* doc/web/commands: postgresql.html page was mistyped
2002-10-18 Daniel Morgan <[email protected]>
* doc/ado-net: updated status of
the ADO.NET functionality and providers
and added link to tds-providers.html
* doc/tds-providers: added file to
describe the design and status of
the SqlClient, SybaseClient, and TdsClient
ADO.NET providers.
* doc/web/makefile
* doc/web/command: added new web page
tds-providers.html to build of www.go-mono.com web site
2002-10-17 Daniel Morgan <[email protected]>
* doc/web/makefile
* doc/web/commands: web page
postgresql needed to be added
2002-10-13 Mark Crichton <[email protected]>
* doc/index: Even more spelling errors fixed.
2002-10-13 Daniel Morgan <[email protected]>
* doc/adonet: updated status of all providers, added links,
and added information
about the Mono.Data.SqliteClient provider that
Vladimir Vukicevic contributed. Added Brian Ritchie's
and Vladimir Vukicevic's email addresses as
people to contact about ADO.NET in Mono.
Added information about SQL#, configuration tools,
and an ADO.NET Multiplexor, etc...
2002-10-10 Daniel Morgan <[email protected]>
* doc/index: corrected some mistypes
* doc/adonet: updated the status and plans of all the ADO.NET providers
and moved PostgreSQL specific stuff to doc/postgresql
* doc/postgresql: added new file to detail
the status of the PostgreSQL ADO.NET provider
and provide test notes for setting it up
2002-10-09 Daniel Morgan <[email protected]>
* data/config.in: add entry for MySQL native shared libraries
which are different on Windows and Linux
2002-10-04 Diego Sevilla Ruiz <[email protected]>
* doc/ccvs: Fixed some ugly formatting.
2002-10-03 Dick Porter <[email protected]>
* acconfig.h:
* configure.in: Freebsd pthread_t is a pointer
2002-10-01 Duncan Mak <[email protected]>
* mono/os/Makefile.am: Add gc_wrapper.h.
* runtime/Makefile.am: Fix the path for monoresgen.exe.
2002-09-27 Dick Porter <[email protected]>
* configure.in: Check for semaphore.h. Patch for BSD from
[email protected] (Julio Merino).
2002-09-20 Duncan Mak <[email protected]>
* data/config.in: Added reference to libxslt.
2002-09-20 Mark Crichton <[email protected]>
* configure.in: added NEED_LINK_UNLINK to make io-layer more portable.
Linux has a "virtual fs" for UNIX sockets, Solaris and BSD don't.
For systems that do not have such a virtual FS, define
NEED_LINK_UNLINK.
* acconfig.h: added NEED_LINK_UNLINK
Wed Sep 4 18:09:58 CEST 2002 Paolo Molaro <[email protected]>
* configure.in: add some needed defines to fix support of
threads in the GC.
2002-09-19 Mark Crichton <[email protected]>
* configure.in: Added checks for Solaris to use X/Open functionality.
Really needed for the io-layer code.
2002-09-15 Andrew Birkett <[email protected]>
* man/mcs.1: --probe is now --expect-error.
2002-09-09 Dick Porter <[email protected]>
* acconfig.h:
* configure.in: Simplify thread checks, by using canned rules for
particular systems (based on the sleepycat db configure.in).
Tested on linux/x86, freebsd and w32. Solaris also added, but I
don't have a solaris machine to try it on.
2002-09-04 Juli Mallett <[email protected]>
* configure.in: Include <sys/types.h> when checking <sys/un.h> stuff.
2002-09-02 Diego Sevilla Ruiz <[email protected]>
* doc/ccvs: Added how to convert SSH keys (from SSH Communications
Security) to the OpenSSH keys required by mono CVS
access.
2002-09-01 Juli Mallett <[email protected]>
* configure.in, mono/interpreter/interp.c,
mono/io-layer/handles.c, mono/io-layer/processes.c,
mono/io-layer/threads.c, mono/io-layer/timed-thread.c,
mono/io-layer/wait.c, mono/jit/helpers.c, mono/jit/jit.c,
mono/metadata/appdomain.c, mono/metadata/class.c,
mono/metadata/domain.c, mono/metadata/gc.c,
mono/metadata/object.c, mono/metadata/reflection.c,
mono/metadata/threads.c, mono/os/gc_wrapper.h,
mono/utils/mono-hash.c: Add a new header, gc_wrapper.h, to
wrap inclusion of gc.h for boehm, since from FreeBSD and
OpenBSD ports, gc.h is <gc.h>, but on GNU it seems to be
in <gc/gc.h>. This will reduce the diffs FreeBSD ports has
to apply, and also makes it possible for me to build with
GC on OpenBSD/macppc built by hand.
2002-09-01 Juli Mallett <[email protected]>
* configure.in: On BSD don't try to use -ldl, we simply don't use it.
2002-09-01 Juli Mallett <[email protected]>
* mono/dis/dis-cil.c:
* configure.in: Check for <wchar.h> via autoconf, don't use it if
it isn't there, as it seems to work fine without it on OpenBSD.
2002-08-28 Dick Porter <[email protected]>
* mono/os/win32/util.c:
* mono/os/unix/util.c:
* mono/os/util.h: mono_set_rootdir() doesnt take any args now.
(It doesn't do anything on unix builds, and the w32 version no
longer needs an arg.)
* configure.in: Add HOST_CC for w32 builds
Tue Aug 27 18:17:43 CEST 2002 Paolo Molaro <[email protected]>
* configure.in: remove iconv checks.
2002-08-24 Juli Mallett <[email protected]>
* configure.in: Recognise OpenBSD/macppc as PowerPC.
Tue Aug 20 15:15:52 CEST 2002 Paolo Molaro <[email protected]>
* configure.in: patch by [email protected] (Daniel Resare)
to error out if bison is missing.
2002-08-17 Gonzalo Paniagua Javier <[email protected]>
* configure.in: don't link against libdl on windoze.
2002-08-12 Dick Porter <[email protected]>
* mono.pc.in: Add $includedir to Cflags
Fri Jul 19 18:38:38 CEST 2002 Paolo Molaro <[email protected]>
* configure.in, Makefile.am, mono.pc.in: add a mono.pc file for use
with pkg-config.
* */Makefile.am: makefile overhaul to create a shared libmono library.
* */*.h: do not include config.h in headers that should be installed.
2002-07-12 Dick Porter <[email protected]>
* acconfig.h:
* configure.in: Check the size of sockaddr_un.sun_path
2002-06-23 Miguel de Icaza <[email protected]>
* man/Makefile.am (man_MANS): Added new man page
* man/mono-config.5: New manual page describing the mono-config
file format.
2002-06-10 Jaroslaw Kowalski <[email protected]>
* configure.in: added checks for MSG_NOSIGNAL
2002-05-30 Daniel Morgan <[email protected]>
* doc/ado-net: update the ado-net web page on go-mono.com
input parameters support, beginnings of Mono.Data.MySQL
and System.Data.OleDb, updated the sample source code,
and output from a PostgresTest
2002-05-21 Martin Baulig <[email protected]>
* mono.1: Documented the "--debug-args" debugging arguments.
2002-05-21 Martin Baulig <[email protected]>
* mono.1: Updated to reflect my latest changes and beautified this a bit.
(FIXME: There are still command line argument which aren't documented here.)
2002-05-19 Daniel Morgan <[email protected]>
* doc/ado-net: updated page to include C# code snippets using
System.Data. Update status: handle reading NULL values, DataSet/DataAdapter
works, executing/reading multiple results, and stored procedures.
And other tweaks about the providers.
2002-05-19 Martin Baulig <[email protected]>
* mono/Makefile.am (SUBDIRS): Added `os', it's referenced by
interpreter/Makefile.am.
Wed May 15 12:22:09 CEST 2002 Paolo Molaro <[email protected]>
* configure.in: search for pthread functions also in libc_r (patch
from Garrett Rooney <[email protected]>).
2002-05-11 Daniel Morgan <[email protected]>
* doc/ado-net: added instructions for installing PostgreSQL on Linux
and for using nant to re-compile just the System.Data.dll assembly
on Windows.
2002-05-10 Rodrigo Moya <[email protected]>
* doc/ado-net: added instructions for compiling System.Data.dll
(a subset of) on Linux.
2002-05-10 Daniel Morgan <[email protected]>
* doc/ado-net: added links
2002-05-09 Dick Porter <[email protected]>
* configure.in: Set CPPFLAGS not CFLAGS (bug 23767)
2002-05-05 Daniel Morgan <[email protected]>
* doc/ado-net: correct formatting
* doc/index: added credit i forgot to add
2002-05-05 Daniel Morgan <[email protected]>
* doc/ado-net: i did not format it correctly earlier, i
tried added various tags where appropriate.
* doc/index: added news item for May 5, 2002 - ado.net able
to retrieve data now
2002-05-05 Daniel Morgan <[email protected]>
* doc/ado-net: updated the current status which
I kept forgetting to do.
2002-05-05 Daniel Morgan <[email protected]>
* doc/ado-net: updated to includes an example for
running ipc-daemon as a Windows service. Thanks
to gonzalo.
2002-05-05 Daniel Morgan <[email protected]>
* doc/ado-net: updated to include installation of
PostgreSQL DBMS under cygwin. It is a TODO for Linux though.
Also included notes on running the System.Data/Test/PostgresTest.cs
that should work on a lot of Mono installations that have
PostgreSQL installed. If not please let me, rodrigo, or gonzalo
know.
2002-05-01 Rodrigo Moya <[email protected]>
* doc/ado-net: updated a little bit.
2002-04-30 Jeffrey Stedfast <[email protected]>
* configure.in: Added checks for timezone stuff.
2002-04-30 Dick Porter <[email protected]>
* acconfig.h:
* configure.in: Added option to disable using shared memory for
handles
2002-04-28 Gonzalo Paniagua Javier <[email protected]>
* configure.in: fix for conditional "THREADS_PTHREAD" was never
defined problem under cygwin with latest version of automake and
autoconf. Patch from Jeroen Janssen <[email protected]>.
2002-04-23 Gonzalo Paniagua Javier <[email protected]>
* configure.in: removed -Wshadow from CFLAGS.
@@ -1209,4 +392,3 @@ Wed Jul 11 00:36:36 CEST 2001 Paolo Molaro <[email protected]>
* NEWS:
+1 -60
View File
@@ -1,62 +1,3 @@
AUTOMAKE_OPTIONS = foreign
SUBDIRS = @libgc_dir@ mono doc docs runtime scripts man data samples
dnl EXTRA_SUBDIRS = libgc
EXTRA_DIST= mono.pc.in mono.spec.in
pkgconfigdir = $(libdir)/pkgconfig
pkgconfig_DATA= mono.pc
DISTCLEANFILES= mono.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)
(cd ../mcs/class/corlib; $(MAKE) MCS=mcs)
cp ../mcs/class/lib/corlib.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)
mcs-rest:
(cd ../mcs/class; $(MAKE))
remove-binaries:
rm ../mcs/class/lib/corlib.dll ../mcs/mcs/mcs.exe runtime/*dll runtime/*.exe >& /dev/null; 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
SUBDIRS = mono doc docs runtime scripts man
-1568
View File
File diff suppressed because it is too large. Load diff
+23 -52
View File
@@ -1,62 +1,24 @@
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:
If you obtained this package as an officially released tarball,
this is very simple, use configure and make:
http://www.go-mono.com/download.html
./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 do:
./autogen --prefix=/usr/local
make fullbuild
2. Using Mono
=============
Once you have installed the software, you can run a few programs:
* runtime engine
mono program.exe
or
mint program.exe
* C# compiler
mcs program.cs
* CIL Disassembler
monodis program.exe
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 documentation and the web site contents.
mono/
The core of the Mono Runtime.
The core of the executable.
metadata/
The object system and metadata reader.
jit/
The Just in Time Compiler.
The library to deal with executables and libraries for
.NET
dis/
CIL executable Disassembler
@@ -64,10 +26,6 @@ This is Mono.
cli/
Common code for the JIT and the interpreter.
io-layer/
The I/O layer and system abstraction for
emulating the .NET IO model.
cil/
Common Intermediate Representation, XML
definition of the CIL bytecodes.
@@ -75,7 +33,20 @@ This is Mono.
interp/
Interpreter for CLI executables.
arch/
Architecture specific portions.
* Using Mono
Once you have installed the software, you can run a few programs:
monodis program.exe
That will dump the bytecodes for program.exe. Monodis support
a number of options that dumps various metadata tables
(chapter 23 of the Partition III).
You can try the interpreter like this:
mint program.exe
+1 -15
View File
@@ -1,12 +1,10 @@
#undef HAVE_INET_PTON
#undef HAVE_INET_ATON
#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
#undef HAVE_PTHREAD_MUTEX_TIMEDLOCK
#undef USE_MONO_MUTEX
#undef HAVE_LARGE_FILE_SUPPORT
@@ -15,15 +13,3 @@
#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
+2 -17
View File
@@ -8,17 +8,8 @@ srcdir=`dirname $0`
test -z "$srcdir" && srcdir=.
if [ -n "$MONO_PATH" ]; then
# from -> /mono/lib:/another/mono/lib
# to -> /mono /another/mono
for i in `echo ${MONO_PATH} | tr ":" " "`; do
i=`dirname ${i}`
if [ -n "{i}" -a -d "${i}/share/aclocal" ]; then
ACLOCAL_FLAGS="-I ${i}/share/aclocal $ACLOCAL_FLAGS"
fi
if [ -n "{i}" -a -d "${i}/bin" ]; then
PATH="${i}/bin:$PATH"
fi
done
ACLOCAL_FLAGS="-I $MONO_PATH/share/aclocal $ACLOCAL_FLAGS"
PATH="$MONO_PATH/bin:$PATH"
export PATH
fi
@@ -117,12 +108,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
+145 -446
View File
@@ -1,129 +1,31 @@
AC_INIT(README)
AC_CANONICAL_SYSTEM
AM_CONFIG_HEADER(config.h)
AM_INIT_AUTOMAKE(mono,0.26)
AM_INIT_AUTOMAKE(mono, 0.10)
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)
# Thread configuration inspired by sleepycat's db
AC_MSG_CHECKING([host platform characteristics])
libgc_threads=no
dnl ****************************************
dnl *** Check if we're building on win32 ***
dnl ****************************************
AC_MSG_CHECKING([if building for some Win32 platform])
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"
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*)
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"
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)
libdl=
libgc_threads=no
gc_default=none
;;
*)
AC_MSG_WARN([*** Please add $host to configure.in checks!])
platform_win32=no
libdl="-ldl"
;;
esac
AC_MSG_RESULT(ok)
AC_MSG_RESULT($platform_win32)
AM_CONDITIONAL(PLATFORM_WIN32, test x$platform_win32 = 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";
then
AC_MSG_ERROR([You need to install bison])
fi
dnl may require a specific autoconf version
dnl AC_PROG_CC_FOR_BUILD
@@ -143,25 +45,18 @@ 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)
AC_CHECK_HEADERS(sys/filio.h sys/sockio.h netdb.h utime.h)
# for mono/mini/tramp-x86.c
AC_CHECK_HEADERS(valgrind/memcheck.h)
AC_CHECK_HEADERS(iconv.h)
AC_CHECK_HEADERS(giconv.h)
# for mono/metadata/debug-symfile.c
AC_CHECK_HEADERS(elf.h)
# for mono/dis
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'
fi
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
@@ -170,8 +65,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)
@@ -193,8 +88,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`
@@ -203,84 +98,38 @@ 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])
AC_CHECK_LIB(gc, GC_malloc, found_boehm="yes")
gc=auto
AC_ARG_WITH(gc, [ --with-gc=boehm,none],[gc=$with_gc])
# 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)
xboehm|xyes)
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.")
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.")
AC_MSG_ERROR("GC requested but libgc not found!")
fi
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"
;;
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.])
dnl When the JIT works with libgc, use this chunk.
dnl # If libgc was found, use it. Otherwise just warn.
if test "x$found_boehm" != "xyes"; then
AC_MSG_WARN("Compiling mono without GC.")
else
AC_DEFINE(HAVE_BOEHM_GC)
AC_SUBST(HAVE_BOEHM_GC)
LIBS="$LIBS -lgc"
gc="boehm"
fi
dnl AC_MSG_WARN("Compiling mono without GC.")
;;
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 ***
@@ -289,7 +138,7 @@ if test x$platform_win32 = xno; then
# Check that off_t can represent 2**63 - 1 correctly, working around
# potential compiler bugs. Defines LARGE_FILE_SUPPORT, adds $1 to
# CPPFLAGS and sets $large_offt to yes if the test succeeds
# CFLAGS and sets $large_offt to yes if the test succeeds
large_offt=no
AC_DEFUN(LARGE_FILES, [
large_CPPFLAGS=$CPPFLAGS
@@ -311,7 +160,7 @@ if test x$platform_win32 = xno; then
], [
AC_MSG_RESULT(ok)
AC_DEFINE(HAVE_LARGE_FILE_SUPPORT)
large_CPPFLAGS="$large_CPPFLAGS $1"
CFLAGS="$CFLAGS $1"
large_offt=yes
], [
AC_MSG_RESULT(no)
@@ -334,21 +183,6 @@ if test x$platform_win32 = xno; then
dnl *****************************
AC_CHECK_LIB(socket, socket, LIBS="$LIBS -lsocket")
dnl *******************************
dnl *** Checks for MSG_NOSIGNAL ***
dnl *******************************
AC_MSG_CHECKING(for MSG_NOSIGNAL)
AC_TRY_COMPILE([#include <sys/socket.h>], [
int f = MSG_NOSIGNAL;
], [
# Yes, we have it...
AC_MSG_RESULT(yes)
AC_DEFINE(HAVE_MSG_NOSIGNAL)
], [
# We'll have to use signals
AC_MSG_RESULT(no)
])
dnl *****************************
dnl *** Checks for SOL_IP ***
dnl *****************************
@@ -364,21 +198,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 *****************************
@@ -420,32 +239,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 *****************************
@@ -455,125 +250,99 @@ if test x$platform_win32 = xno; then
AC_CHECK_FUNCS(inet_pton inet_aton)
dnl ***********************************************
dnl *** Checks for size of sockaddr_un.sun_path ***
dnl ***********************************************
# AC_CHECK_SIZEOF can't cope with struct members :-(
AC_MSG_CHECKING(size of sockaddr_un.sun_path)
AC_CACHE_VAL(cv_mono_sizeof_sunpath,
[AC_TRY_RUN([
#include <sys/types.h>
#include <stdio.h>
#include <sys/un.h>
int main(void) {
struct sockaddr_un sock_un;
FILE *f=fopen("conftestval", "w");
if(!f) exit(1);
fprintf(f, "%d\n", sizeof(sock_un.sun_path));
exit(0);
}
], cv_mono_sizeof_sunpath=`cat conftestval`,
cv_mono_sizeof_sunpath=0,
cv_mono_sizeof_sunpath=0)])dnl
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 *****************************
case "${host}" in
*solaris* )
AC_MSG_CHECKING(for Solaris XPG4 support)
if test -f /usr/lib/libxnet.so; then
CPPFLAGS="$CPPFLAGS -D_XOPEN_SOURCE=500"
CPPFLAGS="$CPPFLAGS -D__EXTENSIONS__"
CPPFLAGS="$CPPFLAGS -D_XOPEN_SOURCE_EXTENDED=1"
LIBS="$LIBS -lxnet"
AC_MSG_RESULT(yes)
else
AC_MSG_RESULT(no)
fi
if test "$GCC" = "yes"; then
CFLAGS="$CFLAGS -Wno-char-subscripts"
fi
;;
esac
dnl *****************************
dnl *** Checks for libpthread ***
dnl *****************************
AC_CHECK_LIB(pthread, main, LIBS="$LIBS -lpthread")
AC_CHECK_FUNCS(pthread_mutex_timedlock)
AC_MSG_CHECKING(for PTHREAD_MUTEX_RECURSIVE)
AC_TRY_COMPILE([ #include <pthread.h>], [
pthread_mutexattr_t attr;
pthread_mutexattr_settype(&attr, PTHREAD_MUTEX_RECURSIVE);
AC_SEARCH_LIBS(pthread_create, pthread, [
AM_CONDITIONAL(THREADS_PTHREAD, true)
AC_DEFINE(HAVE_PTHREAD)
# Need pthread_mutex_timedlock
pthread_CFLAGS=""
orig_CPPFLAGS=$CPPFLAGS
# This is a gcc-specific error, but we already set
# gcc-specific options in CFLAGS
CPPFLAGS="$CPPFLAGS -Werror-implicit-function-declaration"
AC_MSG_CHECKING(for pthread_mutex_timedlock)
AC_TRY_COMPILE([ #include <pthread.h>], [
pthread_mutex_t mut=PTHREAD_MUTEX_INITIALIZER;
pthread_mutex_timedlock(&mut, NULL);
], [
# Works!
AC_MSG_RESULT(yes)
AC_DEFINE(HAVE_PTHREAD_MUTEX_TIMEDLOCK)
], [
AC_MSG_RESULT(no)
# glibc requires -D_GNU_SOURCE before it will declare
# this function
AC_MSG_CHECKING(whether _GNU_SOURCE is needed for pthread_mutex_timedlock)
CPPFLAGS="$CPPFLAGS -D_GNU_SOURCE"
AC_TRY_COMPILE([ #include <pthread.h>], [
pthread_mutex_t mut=PTHREAD_MUTEX_INITIALIZER;
pthread_mutex_timedlock(&mut, NULL);
], [
AC_MSG_RESULT(yes)
pthread_CFLAGS="-D_GNU_SOURCE"
AC_DEFINE(HAVE_PTHREAD_MUTEX_TIMEDLOCK)
], [
AC_MSG_RESULT(no)
dnl Add other variants here
AC_MSG_WARN(Working around pthread_mutex_timedlock)
])
])
CPPFLAGS=$orig_CPPFLAGS
CFLAGS="$CFLAGS $pthread_CFLAGS"
# Need PTHREAD_MUTEX_RECURSIVE
pthread_CFLAGS=""
orig_CPPFLAGS=$CPPFLAGS
# This is a gcc-specific error, but we already set
# gcc-specific options in CFLAGS
CPPFLAGS="$CPPFLAGS -Werror-implicit-function-declaration"
AC_MSG_CHECKING(for PTHREAD_MUTEX_RECURSIVE)
AC_TRY_COMPILE([ #include <pthread.h>], [
pthread_mutexattr_t attr;
pthread_mutexattr_settype(&attr, PTHREAD_MUTEX_RECURSIVE);
], [
# Works!
AC_MSG_RESULT(ok)
], [
AC_MSG_RESULT(no)
# glibc requires -D_GNU_SOURCE before it will declare
# this macro
AC_MSG_CHECKING(whether _GNU_SOURCE is needed for PTHREAD_MUTEX_RECURSIVE)
CPPFLAGS="$CPPFLAGS -D_GNU_SOURCE"
AC_TRY_COMPILE([ #include <pthread.h>], [
pthread_mutexattr_t attr;
pthread_mutexattr_settype(&attr, PTHREAD_MUTEX_RECURSIVE);
], [
AC_MSG_RESULT(ok)
pthread_CFLAGS="-D_GNU_SOURCE"
], [
AC_MSG_RESULT(no)
dnl Add other variants here
AC_MSG_WARN(Using mono_mutex_t for recursive mutexes)
AC_DEFINE(USE_MONO_MUTEX)
])
])
CPPFLAGS=$orig_CPPFLAGS
CFLAGS="$CFLAGS $pthread_CFLAGS"
], [
AC_MSG_RESULT(ok)
], [
AC_MSG_RESULT(no)
AC_MSG_WARN(Using mono_mutex_t for recursive mutexes)
AC_DEFINE(USE_MONO_MUTEX)
AC_MSG_ERROR([libpthread is required on non-win32 hosts])
])
dnl ********************************
dnl *** Checks for semaphore lib ***
dnl ********************************
AC_CHECK_LIB(rt, sem_init, LIBS="$LIBS -lrt")
dnl ********************************
dnl *** Checks for timezone stuff **
dnl ********************************
AC_CACHE_CHECK(for tm_gmtoff in struct tm, ac_cv_struct_tm_gmtoff,
AC_TRY_COMPILE([
#include <time.h>
], [
struct tm tm;
tm.tm_gmtoff = 1;
], ac_cv_struct_tm_gmtoff=yes, ac_cv_struct_tm_gmtoff=no))
if test $ac_cv_struct_tm_gmtoff = yes; then
AC_DEFINE(HAVE_TM_GMTOFF)
else
AC_CACHE_CHECK(for timezone variable, ac_cv_var_timezone,
AC_TRY_COMPILE([
#include <time.h>
], [
timezone = 1;
], ac_cv_var_timezone=yes, ac_cv_var_timezone=no))
if test $ac_cv_var_timezone = yes; then
AC_DEFINE(HAVE_TIMEZONE)
else
AC_ERROR(unable to find a way to determine timezone)
fi
fi
dnl ****************************************************************
dnl *** Checks for working poll() (macosx defines it but doesn't ***
dnl *** have it in the library (duh)) ***
dnl ****************************************************************
AC_CHECK_FUNCS(poll)
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?))
# This is a kludge, we really ought to test for libws2_32, but
# I can't make AC_CHECK_LIB link (the symbols seem to be mangled
# with @num suffixes)
LIBS="$LIBS -lws2_32"
CFLAGS="$CFLAGS -mno-cygwin"
fi
dnl ****************************
@@ -641,91 +410,42 @@ if test "x$ac_cv_have_dev_random" = "xno" \
***]])
fi
AC_MSG_CHECKING([if inter-process shared handles are requested])
AC_ARG_ENABLE(shared-handles, [ --disable-shared-handles disable inter-process shared handles], try_shared_handles=$enableval, try_shared_handles=yes)
AC_MSG_RESULT($try_shared_handles)
if test "x$try_shared_handles" != "xyes"; then
AC_DEFINE(DISABLE_SHARED_HANDLES)
AC_SUBST(DISABLE_SHARED_HANDLES)
if test "x$cross_compiling" = "xno"; then
# check for new iconv version
AC_MSG_CHECKING(for new iconv)
AC_CACHE_VAL(new_iconv,[
AC_TRY_RUN([#include <stdio.h>
#include <iconv.h>
int main()
{
exit (iconv_open ("UTF-16le", "UTF-8") == (iconv_t)-1);
}
],
new_iconv=yes,new_iconv=)])
if test -n "$new_iconv"; then
AC_MSG_RESULT(yes)
AC_DEFINE(HAVE_NEW_ICONV)
else
AC_MSG_RESULT(no)
fi
fi
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
# ;;
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;;
powerpc-*-linux* | powerpc-*-sysv*) TARGET=POWERPC; arch_target=ppc;;
arm-*-linux-*) TARGET=ARM; arch_target=arm; 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"
CFLAGS="$CFLAGS -DNO_PORT"
AC_MSG_WARN("mono has not been ported to $host: some things may not work.")
fi
@@ -738,58 +458,37 @@ 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(JIT_SUPPORTED, test x$JIT_SUPPORTED = xyes)
AC_SUBST(LIBC)
AC_SUBST(arch_target)
AC_SUBST(CFLAGS)
AC_SUBST(CPPFLAGS)
AC_SUBST(LDFLAGS)
AC_OUTPUT([
Makefile
mono.pc
mono/Makefile
mono/utils/Makefile
mono/metadata/Makefile
mono/dis/Makefile
mono/cil/Makefile
mono/arch/Makefile
mono/os/Makefile
mono/os/win32/Makefile
mono/os/unix/Makefile
mono/arch/x86/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 "
-4
View File
@@ -1,4 +0,0 @@
Makefile.in
Makefile
config
.cvsignore
-6
View File
@@ -1,6 +0,0 @@
monodir = $(sysconfdir)/mono
EXTRA_DIST = config.in machine.config
mono_DATA = config machine.config
-19
View File
@@ -1,19 +0,0 @@
<configuration>
<dllmap dll="cygwin1.dll" target="@LIBC@" />
<dllmap dll="libc" target="@LIBC@" />
<dllmap dll="libxslt.dll" target="libxslt.so" />
<dllmap dll="libmySQL.dll" target="libmysqlclient.so" />
<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="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" />
</configuration>
-119
View File
@@ -1,119 +0,0 @@
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<configSections>
<section name="appSettings" type="System.Configuration.NameValueFileSectionHandler, System" />
<section name="system.diagnostics" type="System.Diagnostics.DiagnosticsConfigurationHandler, System" />
<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="webServices"
type="System.Web.Services.Configuration.WebServicesConfigurationSectionHandler, System.Web.Services" />
</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" />
</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="*.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="*" 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="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" />
</httpModules>
<authentication mode="Forms">
<forms name=".MONOAUTH" loginUrl="login.aspx" protection="All" timeout="30" path="/">
<credentials passwordFormat="Clear">
<!--<user name="gonzalo" password="gonz"/>-->
</credentials>
</forms>
</authentication>
<machineKey validationKey="AutoGenerate" decryptionKey="AutoGenerate" validation="SHA1" />
<!-- Sample globalization settings
<globalization requestEncoding="iso-8859-1"
responseEncoding="iso-8859-1"
fileEncoding="iso-8859-1"
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>
</system.web>
<appSettings>
<!--<add key="yourkey" value="your value" /> -->
<!--<remove key="a key defined higher in the hierarchy" /> -->
<!--<clear/> Removes all defined settings -->
</appSettings>
<system.diagnostics>
<trace autoflush="false" indentsize="4" />
</system.diagnostics>
<system.drawing>
</system.drawing>
</configuration>
+4 -9
View File
@@ -1,12 +1,7 @@
WEB_FILES= \
ado-net anoncvs asp-net books ccvs c-sharp class-library contact contributing devel-faq documentation download \
embedded-api faq firebird gcc-frontend hackers ideas index \
java jit-debug languages mailing-lists monodoc-xml mysql odbc \
oledb papers \
passport plans porting postgresql ppc projects rationale \
resources roadmap runtime sqlclient sqlite sybase tdsclient \
tds-providers status testing thanks tools \
porting anoncvs monodoc-xml winforms
WEB_FILES= \
ado-net c-sharp class-library contact contributing documentation download \
faq gcc-frontend ideas index passport rationale resources \
roadmap runtime status team testing thanks tools porting anoncvs monodoc-xml winforms
OTHERS= pending resources-pending todo mono-build.sh mono-build-w32.sh
BIN
View File
Binary file not shown.

Before

Width:  |  Height:  |  Size: 448 B

-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
+30 -432
View File
@@ -1,446 +1,44 @@
* ADO.NET
<p>Mono's ADO.NET Developers:
The coordinator for the ADO.NET implementation is <a
href="mailto:[email protected]">Rodrigo Moya</a>.
<table border=1>
* Action plan
<tr>
<td><b>Developer</b></td>
<td><b>Email</b></td>
<td><b>Contribution</b></td>
</tr>
The current plan to implement ADO.NET is as follows:
<tr>
<td>Rodrigo Moya</td>
<td>rodrigo -AT-<br> ximian.comNOSPAM</td>
<td>ADO.NET coordinator,<br> OLE DB provider,<br> and tests</td>
</tr>
<tr>
<td>Daniel Morgan</td>
<td>danmorg -AT-<br> sc.rr.comNOSPAM</td>
<td>MySQL, PostgreSQL, <br>Oracle providers,<br> and tests</td>
</tr>
<tr>
<td>Tim Coleman</td>
<td>tim -AT- <br>timcoleman.comNOSPAM</td>
<td>Microsoft SQL Server, <br>Sybase, <br>TDS providers,<br> Oracle,
<br>and tests.<br>
He has
contributed <br>to other parts <br>of Mono too, <br>such as,
<br>EnterpriseServices,
XML, <br>and WebServices.</td>
</tr>
<tr>
<td>Brian Ritchie</td>
<td>brianlritchie -AT-<br> hotmail.comNOSPAM</td>
<td>ODBC provider <br>and the ProviderFactory <br>in Mono.Data</td>
</tr>
<tr>
<td>Vladimir Vukicevic</td>
<td>vladimir -AT-<br> pobox.comNOSPAM</td>
<td>SQL Lite provider. <br> He has contributed to GTK# <br>and mPhoto too.</td>
</tr>
<tr>
<td>Christopher Bockner</td>
<td>cleared -AT-<br> rogers.comNOSPAM</td>
<td>IBM DB2 Universal <br>Database provider</td>
</tr>
<tr>
<td>Ville Palo</td>
<td>vi64pa -AT-<br> koti.soon.fiNOSPAM</td>
<td>XML stuff <br>in System.Data <br>including DataSet <br>
and XmlDataDocument, <br>and tests</td>
</tr>
<tr>
<td>Gonzalo Paniagua Javier</td>
<td>gonzalo -AT-<br> ximian.comNOSPAM</td>
<td>Integration between <br>System.Web and <br>System.Data</td>
</tr>
<tr>
<td>Gaurav Vaish</td>
<td>gvaish -AT-<br> iitk.ac.inNOSPAM</td>
<td>Web controls</td>
</tr>
<tr>
<td>Phillip Jerkins</td>
<td>Phillip.Jerkins -AT-<br> morgankeegan.comNOSPAM</td>
<td>Named Instance support <br>in System.Data.SqlClient</td>
</tr>
</table>
** 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>
<li>Any RFE (Request For Enhancement) for features missing or new functionality
should be entered as a bug in Bugzilla too</li>
</ul>
** ADO.NET Data Providers
<p>List of ADO.NET Data Providers working in Mono:
<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">TDS Generic</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><b>SQL# CLI</b> - a SQL query tool with a command-line interface.
It can be used to enter and execute SQL statements or
execute a batch of SQL commands from a file. It can
be used to test connection strings, connect to various ADO.NET
providers, save output to text, html, or xml. It is a work-in-progress.
The SQL# CLI is distributed with the
Mono runtime and class libraries as an executable assembly sqlsharp.exe.
The source to SQL# CLI can be found in the mcs source at
mcs/tools/SqlSharp/SqlSharpCli.cs
</li>
<li><p><b>SQL# GUI - a graphical SQL query tool</b> allows a user
to enter SQL commands in a top panel which is a text editor. 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).
Also, the bottom panel would allow logging of SQL command executed.
Currently, there is a <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. SQL# For GTK#
is a work-in-progress and can be found in the mcs source at
mcs/tools/SqlSharp/gui/gtk-sharp</li>
</ul>
<p>Tools we would like to have, but they have not been created yet:
<ul>
<li><b>XML Schema Definition tool</b> <a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cptools/html/cpconxmlschemadefinitiontoolxsdexe.asp">xsd.exe</a> needs
to be created. Maybe this TODO item should be at the System.XML web page instead.
<ul>
<li>This tool
would work like the xsd.exe tool included with
the .NET Framework. The Xsd.exe tools 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>
</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>
<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>
<li>setup configurations for the Mono.Data.ProviderFactory
that Brian Ritchie created</li>
<li>setup native database client library configurations too, such as,
freetds.conf for Microsoft SQL Server and Sybase</li>
</ul>
</li>
</ul>
** 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.
** 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><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><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.
<p><b>XML support in System.Data</b> needs work. This involves working on
the classes: DataSet, XmlDataDocument, and the method ExecuteXmlReader() that
exists in a provider's class that implements IDbCommand, and others.
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.
<p><b>Database Access from ASP.NET</b>:
<ul>
<li>Take a look at xsp in cvs and look at the examples in test: dbpage1.aspx
and dbpage2.aspx:
<ul>
<li>Notice that the namespace System.Data is imported via <b>import</b></li>
<li>A NameValueCollection is gotten using ConfigurationSettings.AppSetings. These
settings are gotten from the file server.exe.config which is a XML file. The XML
file has a section appSettings. In the appSettings section, you have keys
for DBProviderAssembly, DBConnectionType, and DBConnectionString.
<ul>
<li><b>DBProviderAssembly</b> is the assembly of the ADO.NET provider.
For example:
"Mono.Data.PostgreSqlClient"</li>
<li><b>DBConnectionType</b> is the System.Type of the class that
implements System.Data.IDbConnection that is found
in the DBProviderAssembly.
For example:
"Mono.Data.PostgreSqlClient.PgConnection"</li>
<li><b>DBConnectionString</b> is the ConnectionString to set to the
IDbConnection object to use in opening a connection to a data source.
For Example:
"hostaddr=127.0.0.1;user=monotest;password=monotest;dbname=monotest"</li>
</ul>
<li>The function GetConnectionData() gets the database provider assembly, connection type,
and connection string parameters if they exist; otherwise, it uses default values. This is
done during the loading of the web page.</li>
<li>With the connection parameters, the assembly is loaded, the connection type is verified that
it implements IDbConnection and an instance of the class can be created, creates a instance
of the class, sets the connection string, and opens the connection.</li>
</ul>
</li>
</ul>
<p><b>Integration with Windows.Forms</b> has not been started, such as, data binding
to a System.Windows.Forms.DataGrid. This may involve implementing many classes
in System.Windows.Forms and System.Data.
<p><b>Integration with <a href="http://gtk-sharp.sourceforge.net/">GTK#</a></b>
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#.
<p><b>Integration with QT#</b> has not been started. Any information on
how this can be done is appreciated. Adam Treat would be the best
person to ask about QT#.
<p><b>Building System.Data</b>
<p>The System.Data.dll gets built with the rest of the class library.
To compile the System.Data.dll assembly separately, you need:
<b>On Unix</b>
<b>Step 1:</b> SqlClient:
<ul>
* update your mono sources. Be sure you have latest mcs.exe
and .dll's, since there have been many fixes needed for
compilation on Linux.
* Implementation of System.Data.SqlClient based on
the PostgreSQL C API.
* Once the System.Data.SqlClient code is functional and
is usable by other people, we willl move it to
System.Data.PostgreSQL, and will convert the existing
System.Data.SqlClient to be just a wrapper around
System.Data.PostgreSQL.
* compile System.Data.dll:
<pre>
cd mcs/class/System.Data<br>
mcs --target library -o \
System.Data.dll @list
</pre>
</ul>
<b>On Windows</b>
<b>Step 2:</b> OleDBClient:
<ul>
* On Unix systems: System.Data.OleDb will use LibGDA as its
engine.
LibGDA is the data access engine that is used by
Gnome-Db (only libgda, not libgnomedb at all).
* On Windows systems: System.Data.OleDb will use OLE-DB as
its engine.
</ul>
<b>Step 3:</b> System.Data.SqlClient Providers:
<ul>
* update your mono sources. Be sure you have latest mcs.exe
and .dll's. You can use the same method as Linux,
or you can use NAnt.
* To use NAnt:
<pre>
cd mcs/class/System.Data
../../nant/NAnt.exe
</pre>
* This will automatically copy the System.Data.dll to Test.
If you need to do a clean for the System.Data.dll assembly,<br><br>
<pre>
cd mcs/class/System.Data
../../nant/NAnt.exe clean
</pre>
* System.Data.SqlClient will then become a generic
proxy for binding to other SQL implementations other
than PostgreSQL (MySQL on Unix/Windows; MS SQL on
Window; Interbase on Unix/Windows). Others are welcomed.
</ul>
** 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> (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</td>
</tr>
<tr>
<td>ODBC</br> (Mono)</td>
<td>System.Data.OracleClient /</br> System.Data.OracleClient</td>
<td>TestOracleClient.cs at</br> System.Data.OracleClient</td>
</tr>
</table>
<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>
+2 -2
View File
@@ -30,7 +30,7 @@
To update your sources every day, you use this command:
<pre>
export CVSROOT=:pserver:anonymous@anoncvs.go-mono.com:/mono
export CVSROOT=:pserver:anonymous@reypastor.hispalinux.es:/mono
cvs -z3 update -dP mcs mono gtk-sharp
</pre>
@@ -46,7 +46,7 @@
<a name="#mirror">
** Becoming an AnonCVS mirror
To become an AnonCVS mirror, you currently need about 40
To become an AnonCVS mirror, you currently need about 20
megabytes of free disk space and bandwidth that you do not
mind sharing (you probably want enough to spare).
+7 -97
View File
@@ -1,101 +1,11 @@
* ASP.NET
ASP.NET support is divided in two pieces:
<ul>
* Web Forms (Web Applications infrastructure).
The classes for running ASP.NET are being actively written.
Gaurav, Leen and Patrik have been building the classes
required to run ASP.NET web application as well as a small
embeddable web server.
* Web Services (the SOAP-based rpc system).
</ul>
Both are functional at this point, and applications like
"IBuySpy" run with Mono.
ASP.NET works either embedded into
our XSP server test server or the mod_mono Apache module.
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. Lluis is in charge of
it now and web services are now supported. He also added a web
service sample to the XSP server set of tests.
** Hosting
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.
* <a href="#mod_mono">mod_mono</a>: An apache module
that can host the Mono runtime and the ASP.NET runtime
</ul>
<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.
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.
There is also a set 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 available at <a
href="http://www.apacheworld.org/modmono/">ApacheWorld.org</a>
hosts the Mono runtime and the Mono's ASP.NET runtime, and
allows apache to server asp.net web 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),
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.
We can now render all HtmlControls and all WebControls.
Help in making the controls better is appreciated.
** ASP.NET and free controls.
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.
** How to Help
Testing and fixing HtmlControls, WebControls and validators is an
easy way to help.
In the CVS module XSP you can find a small web server used for
testing and a directory containing sample aspx pages.
You have some documentation under doc directory and in the README
file of each directory. They explain how to test our System.Web.
Testing is really easy!
As the server also works with MS runtime, you can use it to check
what the expected results are.
Currently ASP.NET does not work, but work is underway. If you
are interested in helping the effort please contact the
mono-list mailing list.
+1 -17
View File
@@ -1,19 +1,7 @@
* Mono Books
<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# 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">
@@ -31,10 +19,6 @@
A Retargetable C Compiler - Design and Implementation: C. Fraser, David
Hanson
* Threading
.NET Multithreading: Alan L. Dennis (ISBN 1-930110-54-5)
* Reference Manuals
<a
@@ -50,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>
-69
View File
@@ -1,69 +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%2FAssembler&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%2FAssembler">[Add]</a> IL Assembler.
* <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">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FMCS">[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%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%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">[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).
+38 -24
View File
@@ -1,28 +1,23 @@
* 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).
* Pending tasks
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.
There are a few known bugs in the Mono C# compiler, but
they are very very few at this point,
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.
MCS was able to parse itself on April 2001, MCS compiled itself
for the first time on December 28 2001. MCS became self hosting
on January 3rd, 2002.
The Mono Runtime and the Mono execution engine were able to make
our compiler self hosting on March 12, 2002.
A test suite is maintained to track the progress of
the compiler and various programs are routinely compiled and
ran.
** Slides
Slides for the Mono C# Compiler presentation at .NET ONE are
available <a
href="http://primates.ximian.com/~miguel/slides-europe-nov-2002/Mono_C_Sharp_Overview_1007.sxi">here</a>
in StarOffice format.
** Obtaining MCS
The Mono C# compiler is part of the `mcs' module in the Mono CVS
@@ -32,8 +27,8 @@
** Running MCS
MCS is written in C# and uses heavily the .NET APIs. MCS runs
on Linux with the Mono runtime and on Windows with both the
.NET runtime and the Mono runtime.
on Linux (with the Mono runtime) and Windows (with the .NET
framework runtime)
** Reporting Bugs in MCS
@@ -108,14 +103,33 @@
able to use this generic CIL optimizer in their projects
reducing their time to develop a production compiler.
** History
<a name="tasks">
** Current pending tasks
MCS was able to parse itself on April 2001, MCS compiled itself
for the first time on December 28 2001. MCS became self hosting
on January 3rd, 2002.
Simple tasks:
The Mono Runtime and the Mono execution engine were able to make
our compiler self hosting on March 12, 2002.
<ul>
* Redo the way we deal with built-in operators.
</ul>
Larger tasks:
<ul>
* Jay does not work correctly with `error'
productions, making parser errors hard to point. It
would be best to port the Bison-To-Java compiler to
become Bison-to-C# compiler.
Nick Drochak has started a project on SourceForge for this.
You can find the project at: <a href="http://sourceforge.net/projects/jb2csharp/">
http://sourceforge.net/projects/jb2csharp/</a>
* Semantic Analysis: Return path coverage and
initialization before use coverage are two great
features of C# that help reduce the number of bugs
in applications. It is one interesting hack.
</ul>
** Questions and Answers
+54 -202
View File
@@ -1,196 +1,28 @@
* CVS Access
Here we describe how one obtains commit access to the 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.
** What is CVS?
If you are not a developer, but want to track the development, please
see the <a href="anoncvs.html">AnonCVS</a> instructions.
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.
Send an e-mail to miguel with your public SSH key for this
purpose. Please specify if the key was generated with SSH1 or SSH2.
** 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 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.
* 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.
** 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
the code that the module has.
Check the license if you are unsure, but it is basically:
class libraries X11; compiler and tools: GPL; runtime: LGPL.
If in doubt, check with the maintainers of the module, or send
mail to [email protected].
** Changing 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.
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.
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.
** 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
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.
This is a small tutorial for using CVS.
** Generating an SSH key
If you are using SSH version 2, please generate your key using:
If you are using SSH2, please generate your key using:
<pre>
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:
If you are using SSH1, run:
<pre>
ssh-keygen
</pre>
And mail <a href="mailto:[email protected]">miguel</a> 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
convert your public key to the required format. You have to use
OpenSSH's ssh-keygen program and write the following:
<pre>
ssh-keygen -i -f id_XXX.pub > my_public_key.pub
</pre>
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.
The *exact* format for this file must be:
<pre>
ssh-rsa XXXXX....
</pre>
And mail me your identity.pub file.
You will need CVS and SSH. Windows users can get both by
installing Cygwin (<a
@@ -226,7 +58,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>
@@ -235,25 +67,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>
* Keeping track of changes.
** Keeping track of changes.
We provide two e-mail based mechanisms to keep track of
changes to the code base:
@@ -272,6 +86,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 List
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'.
@@ -279,8 +115,24 @@
This will send you an email message every time a change is
made to the CVS repository, together with the information that
the author of the changes submitted.
** Recommendations
You might also want to track the live changes, subscribe to
the <a
href="mailto:[email protected]">[email protected]</a>
to receive the patches as they are checked into CVS.
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.
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.
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).
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.
+9 -37
View File
@@ -1,45 +1,17 @@
* Status of the various pieces of the class library
Classes in Mono are organized by the assembly that they belong to.
You can browse the status of the class library and see who has
registered to work on what parts of the system. These list
work-in-progress components currently.
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>.
<li><a href="http://www.go-mono.com/class-status-System.Xml.html">System.Xml</a>.
Browse the current <a href="class-status/index.html">status</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).
You can also download the XML <a
href="class-status/maintainers.xml">maintainers</a> file that
contains the actual maintainers list.
<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>
You can also download the master <a
href="class-status/class.xml">Class Status XML</a> file.
* List of not-implemented classes
+80 -20
View File
@@ -2,44 +2,104 @@
** Summary
<em>
[This documentation is in progress. Comments to
<a href="mailto:[email protected]">[email protected]</a>.]
</em>
While using inline XML tags to document classes is certainly
convenient, properly verbose documentation quickly overwhelms
the code, making the source quite difficult to read. Furthermore,
multilingual documentation makes for significant additional text.
With these considerations in mind, Mono will use external XML files
for type documentation, rather than documenting the source
inline. The XML file format used is inspired by the XML format used
to document the ECMA APIs.
for type documentation, rather than documenting the source inline.
Several tools will be created for managing, verifying, generating,
and updating class library documentation, including:
<ul>
<li><a href="#monodoc">monodoc - A graphical documentation viewer.</a></li>
<li>xmllint: a tool used to validate a proper XML document.
<li><a href="#docstub">docstub</a></li>
<li><a href="#docverify">docverify</a></li>
<li><a href="#docconv">docconv</a></li>
<li><a href="#docgen">docgen</a></li>
<li><a href="#monodoc">monodoc</a></li>
</ul>
** XML Documentation Files and Formats
You can download the tools to document Mono from the CVS
repository from module `monodoc'.
*** Monodoc XML
This XML is similar to the XML documentation described in the
C# standard, with added tags for internationalization and a
slightly different structure. Documentation and a DTD/Schema
for Monodoc XML is forthcoming.
Monodoc XML does not contain any definitive type information,
and is only useful in conjunction with the Type definition for
whatever is being documented.
This XML could be generated by hand, by monostub, or by monodoc.
*** Assembly XML
This XML is generated by combining runtime type information for
an Assembly with a collection of Monodoc XML files. The resultant
XML (in the best of cases) contains both complete type and
documentary information for each type in the assembly.
This XML contains enough information to be transformed into
user-accessible documentation. It is likely that scripts
will be created to generate reference docs as HTML and other
formats.
Documentation and a DTD/Schema for Assembly XML is forthcoming.
** Documentation Tools
*** <a name="monodoc">MonoDoc</a>
*** <a name="docstub">docstub</a>
Given a type name and an assembly, generates stub Monodoc XML
documentation for the type. Optionally, docstub can attempt to
populate initial documentation from an XML file in the format
published along with the ECMA standard.
*** <a name="docverify">docverify</a>
Given a Monodoc XML file and an assembly, verifies that the
documentation matches the compiled type. Checks signatures,
parameters, et cetera.
*** <a name="docconv">docconv</a>
Converts from Monodoc XML to the standard C# compiler-emitted
XML format and vice versa.
*** <a name="docgen">docgen</a>
Given an assembly and a collection of Monodoc XML files, creates
an Assembly XML file containing all documentation and type information
available. This output is suitable for transforming into user
documentation.
*** <a name="monodoc">monodoc</a>
A GUI tool for documentation and translation, this encapsulates
the capabilities of docstub, docverify, docconv, and docgen in
a friendly user interface. In addition, monodoc provides features
to ease translation, such as side-by-side editing and coverage
statistics.
** Status and Roadmap
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.
*** 2 January 2002
The GUI edition uses <a
href="http://gtk-sharp.sf.net">Gtk#</a> and the Web edition
uses Mono's ASP.NET implementation.
<img src="images/Screenshot-Monodoc.png">
As I write the initial version of this document, very little has been
implemented. Currently, there is a:
<ul>
<li>Preliminary version of the Monodoc XML format</li>
<li>Preliminary version of the docstub utility</li>
</ul>
Here's hoping for frequent, productive updates.
** Get Involved
Help us develop Mono's documentation tools! Subscribe to
Help us define Mono's documentation structure! Subscribe to
<a href="http://lists.ximian.com/mailman/listinfo/mono-docs-list">mono-docs-list</a>
and wade right in.
+1 -1
View File
@@ -9,5 +9,5 @@
href="http://primates.ximian.com/~miguel">http://primates.ximian.com/~miguel"</a>
You can also <a
href="http://www.ximian.com/about_us/contact/">reach Ximian.</a>
href="http://www.ximian.com/about/contact.php3">reach Ximian.</a>
+12 -98
View File
@@ -1,51 +1,18 @@
* Contributing to the Mono project
Mono has not been completed yet. It is a project under
active development and with a vibrant community. If you are
looking at ways of helping the project, you have come to the
right web page.
There are many ways in which you can help in the Mono project:
There are three different philosophical approaches to helping
the Mono project, the selfish way, the altruistic or the
educational way.
<ul>
* <b>Programmers:</b> You can work on a free
implementation of the <a
href="class-library.html">class libraries</a>, the
<a href="runtime.html">runtime engine</a>, <a
href="tools.html">the tools</a>, the <a
href="testing.html">testing framework</a>
The <b>selfish</b> way is packed with adventure. You start by
building your own software, and start using the compiler and
tools that come with Mono. Eventually you will run into
missing features, or a bug in the software. Since we ship all
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
<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
href="http://lists.ximian.com/mailman/listinfo/mono-list">mono
mailing list</a>; or discuss the solution on the mailing
list. Ideally you will also write a <a
href="testing.html">regression test</a> so the bug does not
get re-introduced in the future.
The <b>altruistic</b> is probably the easiest because you get
to pick a piece of Mono that you might want to work on. You
can pick an unfinished <a href="class-library.html">class</a> (from our <a
href="class-status.html">class status page</a>); help with the
<a href="documentation.html">documentation effort</a> (<a
href="http://lists.ximian.com/mailman/listinfo/mono-docs-list">mailing
list for the documentation effort</a>); fix existing <a
href=http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FClass+Libraries&product=Mono%2FRuntime&component=CORLIB&component=misc&component=System&component=System.Web&component=System.XML&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">runtime
bugs</a>; <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">compiler
bugs</a>; help with the <a href="tools.html">tools</a> or
writing <a href="testing.html">tests</a> that help make Mono
more robust or help with the <a
href="http://www.go-mono.com/winforms.html">Winforms
effort</a>.
The <b>educational</b> way is an interesting one, because you
pick a technology you are interested in, and work on that
technology to learn the technology.
* <b>Writers:</b> You can help us bywriting <a
href="documentation.html">documentation</a>.
</ul>
Those are just broad things that need to be worked on, but
something that would help tremendously would be to help with
@@ -53,11 +20,6 @@
You can see what needs to be done in the class libraries <a href="class-status.html">here</a>
* IRC Channel
Many developers get together on the <b>#mono</b> irc channel
on the <b>irc.gnome.org</b> server.
** To start contributing
As a programmer, you can contribute in three different scenarios to Mono:
@@ -99,8 +61,7 @@
world that only has a test suite.
To get started writing tests see the <a href="testing.html">Test Suite</a>
section. <a href="mono-contribution-howto.html">Here</a> there is a good All-In-One introduction to the art of writing tests.
section.
*** Contributing to the runtime engine
@@ -128,53 +89,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:
-378
View File
@@ -1,378 +0,0 @@
* Cryptography
In the .NET framework cryptography can be found under a number of
namespaces in several assemblies.
** Assembly: corlib
*** Namespace: <b>System.Security.Cryptography</b>
Thanks to the work of many people this namespace is almost complete.
**** Status
<ul>
* Every classes are present.
* Most classes have their unit tests. Some tests like <code>
SymmetricAlgorithmTest</code> are generated by external
tools.
* MACTripleDES is compatible with the implementation shipped in
framework 1.0. Version 1.1 gives different results when the
MACed data is a multiple of BlockSize (8 bytes).
</ul>
**** TODO
<ul>
* 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 specific alternative is available
using the Mono.Security.Win32 assembly.
* 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).
</ul>
**** Notes
<ul>
* All cryptographic algorithms are entirely managed, including
classes named <code>*CryptoServiceProvider</code>, with the
exception of <code>RNGCryptoServiceProvider</code> (which
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).
</ul>
*** Namespace: <b>System.Security.Cryptography.X509Certificates</b>
**** Status
<ul>
* X.509 certificates are parsed using 100% managed code
(using the Mono.Security.ASN1 class).
* Software Publisher Certificates (SPC) used by Authenticode
(tm) to sign assemblies are supported (extraction from PE
files) but <b>not yet</b> validated.
* Unit 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).
</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). See Tools section for more information.
</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>).
* 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). From the exceptions
thrown Authenticode(tm) support is done via COM.
</ul>
<hr>
** Assembly: System.Security
*** Namespace: <b>System.Security.Cryptography.Xml</b>
This namespace implements the <a href="http://www.w3.org/TR/xmldsig-core/">
XML Digital Signature</a> specification from
<a href="http://www.w3.org/">W3C</a>.
**** Status
<ul>
* All classes are present but some Transforms are only stubbed.
* We now have a fully managed C14N implementation.
* Most classes have their unit tests.
</ul>
**** TODO
<ul>
* Complete all Transform derived classes.
</ul>
<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, ARCFOUR (required for SSL)
* Convertion helpers
</ul>
*** Namespace: Mono.Security.X509
<ul>
* X.509 structures (certificate, CRL...) building and decoding.
</ul>
*** Namespace: Mono.Security.X509.Extensions
<ul>
* X.509 extensions (from public X.509 to private PKIX, Netsapce,
Microsoft, Entrust...).
</ul>
**** Status
<ul>
* Some part of the work has not yet been commited (still cleaning up).
* 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.
</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).
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>).
* 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).
</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.
</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
Microsoft Web Service Enhancement (WSE), known as Web Service
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.
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.
<b>[*] There are some licensing issues to consider before starting 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 [*]
*** Namespace: Microsoft.Web.Services.Timestamp [*]
**** Status
<ul>
* Nothing (yet) commited in CVS <b>[*]</b>.
</ul>
*** Namespace: Microsoft.Web.Services.Security.X509
**** Status
<ul>
* Nothing (yet) commited in CVS. However the classes in this
namespace are outside WS-Security scope. So development, for
those classes, could be done without signing this agreement.
</ul>
**** TODO
<ul>
* We need to define certificate stores (for both users and
machines). These sames stores must be linked with asymmetric
keypairs. This could also be used to store the SPC roots.
</ul>
*** Notes
<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.
</ul>
<hr>
** 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 (mostly 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.
</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>sn</code> is a clone of the <code>sn</code> to manage
strongnames. Current version is limited to creating new keypairs
and converting values.
* <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:
<ul>
* <code>signcode</code> and <code>chktrust</code> (in progress)
for signing and validating Authenticode(tm) signatures on
assemblies (or any PE file).
* 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.
<hr>
** Other stuff
<ul>
* SSL/TLS for secure communication (a prototype is under way).
Some work is already visible in Mono.Security assembly (e.g.
RC4, RSAManaged ...).
</ul>
<hr>
** How to Help
<ul>
* 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>
* 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
<b>monodoc</b> as I'm not a very good writer (at least in English).
</ul>
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.
<hr>
Last reviewed: August 9, 2003 (post mono 0.25)
+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
+238 -1175
View File
File diff suppressed because it is too large. Load diff
-301
View File
@@ -1,301 +0,0 @@
* Embedding the Mono runtime, preliminary version
This document describes how to embed the Mono runtime in your
application, and how to invoke CIL methods from C, and how to
invoke C code from CIL
Slides for Paolo's presentation at .NET ONE on the embedding
API are available here: <a
href="http://primates.ximian.com/~lupus/slides/embed">Hosting the Mono
Runtime</a>. You can also get his <a
href="http://primates.ximian.com/~lupus/slides/embed/Mono-0.01.tar.gz">sample
Mono module for Perl</a>
Authors: Paolo Molaro, Miguel de Icaza.
* Embedding the runtime.
Embedding the runtime consists of various steps:
<ul>
* Compiling and linking the Mono runtime
* Initializing the Mono runtime
* Optionally expose C code to the C#/CIL universe.
</ul>
These are discussed in detail next.
** Compiling and Linking
To embed the runtime, you have to link your code against the
Mono runtime libraries. To do this, you want to pass the
flags returned by pkg-config to your compiler:
<pre>
pkg-config --cflags --libs mono
</pre>
Like this:
<pre>
gcc sample.c `pkg-config --cflags --libs mono`
</pre>
You can separate the compilation flags from the linking flags, for
instance, you can use the following macros in your makefile:
<pre>
CFLAGS=`pkg-config --cflags mono`
LDFLAGS=`pkg-config --libs mono`
</pre>
** Initializing the Mono runtime
To initialize the runtime, call mono_jit_init, like this:
<pre>
MonoDomain *domain;
domain = mono_jit_init ("domain-name");
</pre>
That will return a MonoDomain where your code will be
executed. You can create multiple domains. Each domain is
isolated from the other domains and code in one domain will
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:
<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");
if (!assembly)
error ();
</pre>
In the above example, the contents of `file.dll' will be
loaded into the domain. This only loads the code, but it will
not execute anything yet. You can replace `file.dll' with
another transport file, like `file.exe'
To start executing code, you must invoke a method in the
assembly, or if you have provided a static Main method (an
entry point), you can use the convenience function:
<pre>
retval = mono_jit_exec (domain, assembly, argc - 1, argv + 1);
</pre>
If you want to invoke a different method, look at the
`Invoking Methods in the CIL universe' section later on.
** Shutting down the runtime
To shutdown the Mono runtime, you have to clean up all the
domains that were created, use this function:
<pre>
mono_jit_cleanup (domain);
</pre>
** Applications that use threads.
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.
* Exposing C code to the CIL universe
The Mono runtime provides two mechanisms to expose C code to
the CIL universe: internal calls and native C code. Internal
calls are tightly integrated with the runtime, and have the
least overhead, as they use the same data types that the
runtime uses.
The other option is to use the Platform Invoke (P/Invoke) to
call C code from the CIL universe, using the standard P/Invoke
mechanisms.
To register an internal call, use this call in the C code:
<pre>
mono_add_internal_call ("Hello::Sample", sample);
</pre>
Now, you need to declare this on the C# side:
<pre>
using System;
using System.Runtime.CompilerServices;
</pre>
<pre>
class Hello {
[MethodImplAttribute(MethodImplOptions.InternalCall)]
extern static string Sample ();
}
</pre>
Since this routine returns a string, here is the C definition:
<pre>
static MonoString*
Sample ()
{
return mono_string_new (mono_domain_get (), "Hello!");
}
</pre>
Notice that we have to return a `MonoString', and we use the
`mono_string_new' API call to obtain this from a string.
* Invoking Methods in the CIL universe
Calling a method in the CIL universe from C requires a number of steps:
<ul>
* Obtaining the MonoMethod handle to the method.
* The method invocation.
</ul>
** Obtaining a MonoMethod
To get a MonoMethod there are several ways.
You can get a MonoClass (the structure representing a type)
using:
<pre>
MonoClass *
mono_class_from_name (MonoImage *image, const char* name_space, const char *name);
</pre>
and then loop in the returned class method array until you get
the one you're looking for. There are examples of such
searches as static functions in several C files in
metadata/*.c: we need to expose one through the API and remove
the duplicates.
The other, simpler, way is to use the functions in
debug-helpers.h: there are examples of their use in monograph,
mint and the jit as well. You basically use a string
description of the method, like:
<pre>
"System.Object:GetHashCode()"
</pre>
and create a MonoMethodDesc out of it with:
<pre>
MonoMethodDesc* mono_method_desc_new (const char *name, gboolean include_namespace);
</pre>
You can then use:
<pre>
MonoMethod* mono_method_desc_search_in_class (MonoMethodDesc *desc, MonoClass *klass);
MonoMethod* mono_method_desc_search_in_image (MonoMethodDesc *desc, MonoImage *image);
</pre>
to search for the method in a class or in an image. You would
tipically do this just once at the start of the program and
store the result for reuse somewhere.
** Invoking a Method
There are two functions to call a managed method:
<pre>
MonoObject*
mono_runtime_invoke (MonoMethod *method, void *obj, void **params,
MonoObject **exc);
and
MonoObject*
mono_runtime_invoke_array (MonoMethod *method, void *obj, MonoArray *params,
MonoObject **exc);
</pre>
obj is the 'this' pointer, it should be NULL for static
methods, a MonoObject* for object instances and a pointer to
the value type for value types.
The params array contains the arguments to the method with the
same convention: MonoObject* pointers for object instances and
pointers to the value type otherwise. The _invoke_array
variant takes a C# object[] as the params argument (MonoArray
*params): in this case the value types are boxed inside the
respective reference representation.
From unmanaged code you'll usually use the
mono_runtime_invoke() variant.
Note that this function doesn't handle virtual methods for
you, it will exec the exact method you pass: we still need to
expose a function to lookup the derived class implementation
of a virtual method (there are examples of this in the code,
though).
You can pass NULL as the exc argument if you don't want to
catch exceptions, otherwise, *exc will be set to the exception
thrown, if any. if an exception is thrown, you can't use the
MonoObject* result from the function.
If the method returns a value type, it is boxed in an object
reference.
We have plans for providing an additional method that returns
an unmanaged->managed thunk like this:
<pre>
void* mono_method_get_unmanaged_thunk (MonoMethod *method);
</pre>
You'll be able to store the returned pointer in a function
pointer with the proper signature and call that directly from
C:
<pre>
typedef gint32 (*GetHashCode) (MonoObject *obj);
GetHashCode func = mono_method_get_unmanaged_thunk (System_Object_GetHashCode_method);
gint32 hashvalue = func (myobject);
</pre>
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
embedding the Mono runtime in your application.
+83 -954
View File
File diff suppressed because it is too large. Load diff
-196
View File
@@ -1,196 +0,0 @@
* 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
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>
</ul>
** Current Status
<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>
<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>
<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>
** Action Plan
<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:
<pre>
using System;
using System.Data;
using FirebirdSql.Data.Firebird;
public class Test
{
public static void Main(string[] args)
{
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;
IDataReader reader = dbcmd.ExecuteReader();
while(reader.Read()) {
object dataValue = myReader.GetValue(0);
string sValue = dataValue.ToString();
Console.WriteLine("Value: " + sValue);
}
// 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 FirebirdSql.Data.Firebird.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 FirebirdSql.Data.Firebird.dll
</pre>
</li>
</ul>
</li>
<li>Running the Example:
<pre>
mono TestExample.exe
</pre>
</li>
</ul>
+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.
-162
View File
@@ -1,162 +0,0 @@
* Gtk#
<a href="http://gtk-sharp.sourceforge.net">Gtk#</a> (Gtk
sharp) is a set of C# language bindings for the
<a href="http://www.gtk.org">Gtk+</a> toolkit and other
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.
** 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">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>Buidling on Linux:
<ul>
<li>Get GTK# source from <a href="http://gtk-sharp.sourceforge.net">Gtk# Project</a>.</li>
<li>run ./autogen.sh --prefix=my_mono_installation_prefix</li>
<li>make</li>
<li>make install</li>
</ul>
** 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>If you want to build GTK# yourself on Windows:
<p>To build gtk# under windows, you will need the following:
<ul>
<li>cygwin from <a href="http://www.cygwin.com/">here</a> When installing Cygwin via setup.exe,
by default binutils and other tools do not get installed; you have to make
sure to select these items. Just make
sure Base and Development are set to Install.</li>
<li>Mono 0.17 or later from <a href="http://www.go-mono.com/download.html">here</a>
You can use Windows Setup Wizard (NT/2000/XP).</li>
<li>GTK+ 2.0 (and dependencies). You can obtain gtk+ 2.0 by either of the
following:
<ul>
<li>You can get a Windows Installer at:
<a href="http://www.dropline.net/jade/download.html">here</a> </li>
<li>or get the separate binary and dev/lib packages at
at <a href="http://www.gimp.org/~tml/gimp/win32/downloads.html">here</a> </li>
<li>or binary package from Dev-C++ site <a href="http://www.bloodshed.net/dev/packages/gtk.html">here</a> </li>
<li>or get Gtk4Win <a href="http://wingtk.sourceforge.net/index.html">here</a> </li>
<li>or the source at <a href="http://www.gtk.org/">here</a> </li>
</ul>
</li>
<li>binary distriubtion of a current web browser
like Internet Explorer 4.0, Mozilla 1.0, or Netscape 7.0 which
includes things like msvcrt.dll.</li>
<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>
<li>PATH - set to your mono installation bin and lib path.
For example, my mono installation prefix is:
<pre>
F:/cygwin/home/DanielMorgan/mono/install
</pre>
<p>So, I would set my PATH in the Windows Control Panel as:
<pre>
F:/cygwin/home/DanielMorgan/mono/install/bin;F:/cygwin/home/DanielMorgan/mono/install/lib</li>
</pre>
</li>
<li>LD_LIBRARY_PATH - set to your mono installation lib path</li>
<li>PKG_CONFIG_PATH - set to your mono installation lib/pkgconfig path, such
as,
<pre>
F:/cygwin/home/DanielMorgan/mono/install/lib/pkgconfig</li>
</pre>
<p>If you got the gtk-sharp source, cd to the gtk-sharp directory, type:
<pre>
./autogen.sh --prefix=~/mono/install
</pre>
<p>Set your --prefix= to whatever your mono installation prefix is located.
This will take awhile to go through the ./autogen.sh and ./configure...
<p>After that it finishes succesfully, you run make with the makefile.win32
like:
<pre>
make -f makefile.win32
</pre>
<p>After that finishes succesfully, you can copy to your mono installation lib
path like:
<pre>
cp */*.dll ~/mono/install/lib
</pre>
</ul>
<p>The pkg-config files for
gtk+ 2.0 and dependencies will need to be set correctly if they haven't
already been.
<p>Look in your mono installation/lib/pkgconfig, such as,
<pre>
F:/cygwin/home/DanielMorgan/mono/install/lib/pkgconfig
</pre>
<p>You will find files like: gtk+-2.0.pc
<p>Edit the line that says
<pre>
prefix=something
</pre>
<p>And set it to your mono installation prefix, such as,
<pre>
prefix=F:/cygwin/home/DanielMorgan/mono/install
</pre>
<p>Do this for all the .pc files in that directory. If there are not any, then
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?
** GTK# On AIX
TODO. Any volunteers?
-39
View File
@@ -1,39 +0,0 @@
* Mono Hackers Hall Of Fame
Without the help, the skills and the time of many passionate developers outside of
the Ximian Mono team, Mono would not be where it is today.
Many of them do it for fun, some do it because they really want a nice CLR they
can hack on, some do it because they need a working solution to some development
issues and mono is the ideal tool for the job.
Some of them may start contributing because they want a mention in the
<b>Mono Hackers Hall Of Fame</b>! Whatever the cause, join us in a big<br>
<h1 align="center">Thank you!</h1>
* 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
work on the class libraries that were critical to Mono's origin: every
time you use a Hashtable in Mono, it runs Sergey's code, to the
low-level optimizations on the JIT engine and to his work on ILASM and
the PEToolkit. And countless other things.
** Nick Drochak
The first, deserved, entry in the <b>Mono Hackers Hall Of Fame</b> is for
Nick Drochak, who joined us in the first days of Mono and built the testing
infrastructure for the C# assemblies, fixed tons of bugs and even adventured
himself in the lands of the C runtime. His work is invaluable for keeping
Mono on the right track through the daily changes in the codebase.
-157
View File
@@ -1,157 +0,0 @@
* 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
DllImport's have similiar function names.</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
<ul>
<li>Compiles on Windows and Linux. Works on Windows. Still needs to be tested on Linux.</li>
<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>
** Action Plan
<ul>
<li>Still needs work to get it to retrieve data via ExecuteReader() and
use the data reader to read data.</li>
</ul>
** Testing
In order to test.
<ul>
<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-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">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>
<li>In mcs/class/Mono.Data.DB2Client/Test/DBConnTest, you will find
a DBConnTest.cs.</li>
<li>To build DBConnTest:
<ul>
<li>On Unix:</li>
<pre>
mcs DBConnTest.cs -r System.Data.dll -r Mono.Data.DB2Client.dll
</pre>
</li>
<li>On Windows via Cygwin:
<pre>
mono C:/cygwin/home/MyHome/mono/install/bin/mcs.exe DBConnTest.cs \
-lib:C:/cygwin/home/MyHome/mono/install/lib \
-r System.Data.dll -r Mono.Data.DB2Client.dll
</pre>
</li>
<li>To run it on mono:
<pre>
mono DBConnTest.exe database userid password
</pre>
</li>
</ul>
</li>
<li>C# Example:
<pre>
using System;
using System.Data;
using Mono.Data.DB2Client;
public class Test
{
public static void Main(string[] args)
{
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.ExecuteNonQuery();
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 Mono.Data.DB2Client.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 Mono.Data.DB2Client.dll
</pre>
</li>
</ul>
</li>
<li>Running the Example:
<pre>
mono TestExample.exe
</pre>
</li>
</ul>
+17 -2
View File
@@ -56,7 +56,11 @@ TODO=multimedia
<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>
TODO=guavac,Java compiler for .NET
* You could take one of the existing Java compilers
@@ -69,8 +73,19 @@ TODO=guavac,Java compiler for .NET
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 <a href="http://remoting-corba.sourceforge.net/">CORBA</a> is done, implement the Bonobo interfaces
* 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!
+869 -1187
View File
File diff suppressed because it is too large. Load diff
-14
View File
@@ -1,9 +1,5 @@
* Java
<b>This is an outline on how to support Java, actual
implementations of ideas like this can be found <a href="http://radio.weblogs.com/0109845/">here</a></b>
It would be interesting to support the Java language as part
of the Mono project.
@@ -14,16 +10,6 @@
Microsoft J# compiler. We could then allow the migration of
Java applications to the Mono runtime.
** Native compiler
Although a native compiler can be built, and probably should be
built using an existing compiler, a short term solution is to
build a translator from Java class files to the ECMA CIL images.
This has the advantage that we can use an existing and tested
Java compiler to generate the code, and then we can use an automated
code compiler that compiles Java VM bytecodes to CIL bytecodes.
** The translator.
It would be interesting to write a semantic translator that
+170 -30
View File
@@ -1,41 +1,181 @@
* Debugging information
* How to debug your C# application with the JIT engine
Compile your programs using the `-g' flag in MCS, that will all a special
resource containing debugging information to your executable.
To debug a C# application you need to run the JIT in your debugger.
To get stack traces with line number information, you need to run your
program like this:
Before you can do anything useful in a debugger, you need a symbol
file which tells your debugger about functions, types, line numbers
and such. Unfortunately, this symbol file needs to be recreated each
time the JIT compiles a new method since it doesn't know anything
about this method (especially not its memory address) before actually
compiling it.
<b>
mono --debug program.exe
</b>
You have two ways of creating a symbol file:
Notice that the program will need to be compiled with the -g
flag and that running with --debug will slow down the execution.
** Letting the JIT dynamically create the symbol file
* Mono Debugger
This'll give you a symbol file which is suitable for debugging IL byte
code - you won't see your C# source code.
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.
However, this method has the advantage that it works with every assembly,
no matter whether it has been compiled with Mono's C# compiler (MCS) or
with any other compiler. It's currently the only way to debug
<tt>corlib.dll</tt> or any other library which cannot be compiled with
our compiler yet.
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).
All that you need is a dump of the IL bytecode for each assembly (including
all assemblies this assembly is referencing). This is done by using the
<tt>monodis</tt> utility:
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>
<pre>
monodis /home/export/martin/MONO-LINUX/lib/corlib.dll > corlib.il<br>
monodis /home/export/martin/MONO-LINUX/lib/System.dll > System.il<br>
monodis /home/export/martin/MONO-LINUX/bin/mcs.exe > mcs.il
</pre>
Make sure that all the .il files have the same name as their corresponding
assembly and that they're all created in the current directory.
The JIT supports two different debugging file formats:
<ul>
* STABS: This is a very simple debugging format, but it may be the only one
which is supported on your system. It is limited to source files of no more
than 65.535 lines and it's type support is also very limited. You should only
use this if your debugger doesn't support DWARF 2.
To generate STABS output, use the <tt>--stabs</tt> command line argument.
* DWARF 2: The DWARF 2 debugging format is a very powerful debugging format
which can handle source files of arbitrary size and has a highly sophisticated
type support. It's the recommended format unless you need to use STABS because
your debugger doesn't support DWARF 2.
To generate DWARF 2 output, use the <tt>--dwarf</tt> command line argument.
</ul>
You need to regenerate the symbol file each time the JIT compiled a new
method and each time you restart the JIT. You cannot reuse your symbol file
if you start the JIT a second file, not even if you're running the same
application with the same input data a second time.
Regenerating the symbol file is done by calling the JIT's
<tt>mono_debug_make_symbols ()</tt> function from within your debugger and
then reloading the symbol files. This function creates a <tt>filename-dwarf.s</tt>
(or <tt>filename-stabs.s</tt>) assembler input file in the current directory and
an object file in <tt>/tmp/filename.o</tt> - you need to tell your debugger to
add this object file as symbol file.
If you're using the GNU debugger, this is done like this:
<pre>
call mono_debug_make_symbols ()
add-symbol-file /tmp/corlib.o
add-symbol-file /tmp/mcs.o
add-symbol-file /tmp/Mono.CSharp.Debugger.o
</pre>
You can also write a GDB macro like this:
<pre>
define reload
call mono_debug_make_symbols ()
add-symbol-file /tmp/corlib.o
add-symbol-file /tmp/mcs.o
add-symbol-file /tmp/Mono.CSharp.Debugger.o
end
</pre>
Then you can just say <tt>reload</tt> to have GDB recreate the symbol file.
There's also an <a href="jit-debug-sample.html">example debugging session</a> using
the GNU debugger.
** Using a symbol file which have been created by the Mono C# compiler
If you compiled your application with Mono's C# compiler (MCS), you can tell it to
create a symbol file which is then processed and rewritten by the JIT engine.
To do this, you must give MCS the <tt>-g</tt> option:
<pre>
$ mcs -g Foo.cs
</pre>
This creates a <tt>Foo-debug.s</tt> assembler input file.
To use this in the JIT, you must first copy it to the target machine (the machine
where you want to run the JIT to debug your application) and run it through the
assembler to produce an object file <tt>Foo-debug.o</tt>. This object file must be
in the current directory.
Then start the JIT in your debugger and give it the <tt>--dwarf-plus</tt> command
line argument.
Each time you call <tt>mono_debug_make_symbols ()</tt> from withing your debugger,
the JIT will read this <tt>Foo-debug.o</tt>, fix some machine dependent things like
memory addresses etc. in it and write it back to disk.
If you're using the GNU debugger, you'll want to use a macro like this:
<pre>
define relocate
call mono_debug_make_symbols ()
add-symbol-file /tmp/corlib.o
add-symbol-file mcs-debug.o
add-symbol-file Mono.CSharp.Debugger-debug.o
end
</pre>
If there is no <tt>assembly-debug.o</tt> file, but an <tt>assembly.il</tt> one, the
JIT will fall back to normal DWARF 2 (in the example above, <tt>corlib.dll</tt> was
compiled with Microsoft's compiler and the JIT is thus using DWARF to debug it).
This debugging method only works if you compiled your assembly with MCS, but it'll
allow you to actually debug your C# source code :-)
Here's an <a href="jit-debug-sample2.html">example debugging session</a> using
the GNU debugger.
** Breakpoints and single stepping
The JIT has a <tt>--debug</tt> command line argument to insert a breakpoint at the
beginning of this method. It takes a <tt>Namespace.Class:Method</tt> argument which
is the method. This argument can be given multiple times.
However, once your application is stopped in GDB you may want to insert a breakpoint
the next time the JIT compiles a method. There's a global variable
<tt>mono_debug_insert_breakpoint</tt> which you can modify in your debugger.
If this variable is set to a non-zero value, the JIT's <tt>arch_compile_method</tt>
will insert a breakpoint the next time it is called, ie. at the top of the next
method it compiles. If this value has a positive value, it acts as a counter and is
decremented after inserting the breakpoint - setting it to a negative value will let
the JIT insert the breakpoint each time it compiles a new method.
There's also global variable <tt>mono_debug_last_breakpoint_address</tt> which always
contains the address of the last inserted breakpoint. You may manually override this
address with a <tt>nop</tt> instruction to delete the breakpoint.
For instance, I have a GDB macro called <tt>enter</tt> which I use to enter a method
rather than stepping over it:
<pre>
define enter
set mono_debug_insert_breakpoint = 1
continue
set *mono_debug_last_breakpoint_address = 0x90
relocate
frame
</pre>
Btw. speaking of single stepping - you should use your debuggers <tt>next</tt> command,
not its <tt>step</tt> command for single stepping unless you compiled the JIT without
debugging support. The reason for this is that the JIT creates machine code which contains
calls to JIT methods such as <tt>mono_object_new_wrapper</tt> at places where you don't
expect them - so unless the JIT is compiled at least without line numbers, your debugger
will enter such methods if you use <tt>step</tt> rather than <tt>next</tt>.
+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 --dwarf --debug Foo:Main ./Foo.exe
Starting program: /home/martin/monocvs/mono/mono/jit/mono --dwarf --debug 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 --dwarf-plus --debug Foo:Main ./Foo.exe
Starting program: /home/martin/monocvs/mono/mono/jit/mono --dwarf-plus --debug 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>
+5 -147
View File
@@ -3,159 +3,17 @@
Here are some other free compilers for other languages that
target .NET and should work with Mono with no problem:
<ul>
* <a href="#ComponentPascal">Component Pascal</a>
* <a href="#MonoLogo">MonoLogo</a>
* <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
complete ran of all their regression tests to validate it:
<ul>
* Kylix.NET.
</ul>
Languages we would like to have supported, with links to resources:
<ul>
* <a href="#JavaScript">Java Script</a>
* <a href="#java.html">Java</a>
* <a href="#c">C</a>
</ul>
Some experimental languages:
<ul>
* <a href="#Tachy">Tachy</a> (scheme-like)
* <a href="#python">Python</a>
</ul>
<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>.
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 name="MonoLogo">
** MonoLogo
An implementation of Logo for Mono (and .NET)
The <A href="http://monologo.sf.net">Mono Logo</a> compiler is
hosted in the <a href="ccvs.html">Mono CVS</a> repository
and also available on the <a href="anoncvs.html">AnonCVS</a> mirrors.
<a name="mbas">
** Mono Basic (Mono's VB.NET compiler)
Work has resumed on the Mono Visual Basic compiler (currently
called mbas). It is part of the standard Mono distribution,
but its still an early compiler.
<a name="Oberon">
** Oberon
* Oberon
This Oberon compiler is written in Oberon.NET (another self
hosting compiler).
The main site <a href="http://www.oberon.ethz.ch/oberon.net/">http://www.oberon.ethz.ch/oberon.net/</a>
Download:
<a href="http://www.oberon.ethz.ch/oberon.net/download/">http://www.oberon.ethz.ch/oberon.net/download/</a>
Examples:
<a href="http://www.oberon.ethz.ch/oberon.net/examples/">http://www.oberon.ethz.ch/oberon.net/examples/</a>
hosting compiler):
<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
* 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="www.dataman.ro/dforth">Home
Page</a> and <a href="http://www.dataman.ro/dforth/index.html">more
details here</a>.
<a name="Tachy">
** Tachy
A subset of Scheme language called <a
href="http://radio.weblogs.com/0101156/stories/2002/03/19/tachy.html">Tachy</a>
<a name="Python">
** 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>.
An FAQ document is available <a
href="http://www.zope.org/Members/Brian/PythonNet/FAQ.html">here</a>.
<a name="dotlisp">
** 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
supported. We will try to maintain a set of links here with
technical information for those interested in porting,
implementing or adapting a compiler for any of these
languages:
<a name="c">
* C
Ideally GCC could be modified to generate CIL, but it is a
big task. That would give us various compilers in one pass.
<a href="http://www.cs.princeton.edu/software/lcc">LCC</a> 4.2
has been recently released. This release adds support for compiling
ANSI C programs to CIL. Note that the CIL support only works on Win32
right now, but should be easy to convert to Mono/other architectures.
LCC is not an open source compiler, but it is free as long as you
do not profit from selling it.
<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.
+18 -190
View File
@@ -1,21 +1,8 @@
* Mailing Lists
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>
There are a number of mailing lists for Mono
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 +15,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 +36,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>
@@ -99,6 +58,16 @@
Discussion on the documentation of Mono.
</td>
</tr>
<tr>
<td>
<b><a
href="http://lists.ximian.com/mailman/listinfo/mono-patches">mono-patches</a></b>
</td>
<td>
Track the development of Mono in realtime: receive patches to the Mono repository
by email.
</td>
</tr>
<tr>
<td>
<b><a href="http://lists.ximian.com/mailman/listinfo/mono-bugs">mono-bugs</a></b>
@@ -108,24 +77,6 @@
in <a href="http://bugzilla.ximian.com">Bugzilla.ximian.com</a>
</td>
</tr>
<tr>
<td>
<b><a
href="http://lists.ximian.com/mailman/listinfo/mono-winforms-list">mono-winforms-list</a></b>
</td>
<td>
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>
</table>
Other mailing lists of interest:
@@ -136,127 +87,4 @@
list at Develop.com:</a></b> The guys at Develop Mentor run
this general purpose mailing list.
</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 -->
<center>
<table>
<tr>
<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>
<tr><td>
<FORM method=GET action=http://www.google.com/custom>
<TABLE bgcolor=#FFFFFF cellspacing=0 border=0>
<tr valign=top>
<td>
<INPUT TYPE=text name=q size=31 maxlength=255 value="">
<INPUT TYPE=hidden name=q size=31 maxlength=255 value="mono">
<INPUT type=submit name=sa VALUE="Search">
<input type="hidden" name="cof" value="GIMP:#00ff00;T:#ffffff;LW:401;BIMG:http://www.go-mono.com/images/bgsquares.gif;ALC:#ffffff;L:http://www.go-mono.com/images/mono.gif;GFNT:#cc7700;LC:#ee9900;LH:80;BGC:#444444;AH:center;VLC:#cccccc;S:http://www.go-mono.com;GALT:#eeee00;AWFID:45753ce73241ef7a;">
<font face="arial,sans-serif" size="-1"><input type="hidden" name="domains" value="www.go-mono.com;lists.ximian.com"><br><input type="radio" name="sitesearch" value="www.go-mono.com"> Search www.go-mono.com <input type="radio" name="sitesearch" value="lists.ximian.com"> Search lists.ximian.com </font><br>
</td></tr></TABLE>
</FORM>
</tr></td>
<tr><td>
<FORM method=GET action=http://www.google.com/custom>
<TABLE bgcolor=#FFFFFF cellspacing=0 border=0>
<tr valign=top>
<td>
<INPUT TYPE=text name=q size=31 maxlength=255 value="">
<INPUT TYPE=hidden name=q size=31 maxlength=255 value="mono-list">
<INPUT type=submit name=sa VALUE="Search">
<input type="hidden" name="cof" value="GIMP:#00ff00;T:#ffffff;LW:401;BIMG:http://www.go-mono.com/images/bgsquares.gif;ALC:#ffffff;L:http://www.go-mono.com/images/mono.gif;GFNT:#cc7700;LC:#ee9900;LH:80;BGC:#444444;AH:center;VLC:#cccccc;S:http://www.go-mono.com;GALT:#eeee00;AWFID:45753ce73241ef7a;">
<font face=arial,sans-serif size=-1><input type=hidden name=domains value="lists.ximian.com"><br> <input type=hidden name=sitesearch value="lists.ximian.com"> Search mono-<b>list</b> </font><br>
</td></tr></TABLE>
</FORM>
</tr></td>
<tr><td>
<FORM method=GET action=http://www.google.com/custom>
<TABLE bgcolor=#FFFFFF cellspacing=0 border=0>
<tr valign=top>
<td>
<INPUT TYPE=text name=q size=31 maxlength=255 value="">
<INPUT TYPE=hidden name=q size=31 maxlength=255 value="mono-announce-list">
<INPUT type=submit name=sa VALUE="Search">
<input type="hidden" name="cof" value="GIMP:#00ff00;T:#ffffff;LW:401;BIMG:http://www.go-mono.com/images/bgsquares.gif;ALC:#ffffff;L:http://www.go-mono.com/images/mono.gif;GFNT:#cc7700;LC:#ee9900;LH:80;BGC:#444444;AH:center;VLC:#cccccc;S:http://www.go-mono.com;GALT:#eeee00;AWFID:45753ce73241ef7a;">
<font face=arial,sans-serif size=-1><input type=hidden name=domains value="lists.ximian.com"><br> <input type=hidden name=sitesearch value="lists.ximian.com"> Search mono-<b>announce-list</b> </font><br>
</td></tr></TABLE>
</FORM>
</tr></td>
<tr><td>
<FORM method=GET action=http://www.google.com/custom>
<TABLE bgcolor=#FFFFFF cellspacing=0 border=0>
<tr valign=top>
<td>
<INPUT TYPE=text name=q size=31 maxlength=255 value="">
<INPUT TYPE=hidden name=q size=31 maxlength=255 value="mono-bugs">
<INPUT type=submit name=sa VALUE="Search">
<input type="hidden" name="cof" value="GIMP:#00ff00;T:#ffffff;LW:401;BIMG:http://www.go-mono.com/images/bgsquares.gif;ALC:#ffffff;L:http://www.go-mono.com/images/mono.gif;GFNT:#cc7700;LC:#ee9900;LH:80;BGC:#444444;AH:center;VLC:#cccccc;S:http://www.go-mono.com;GALT:#eeee00;AWFID:45753ce73241ef7a;">
<font face=arial,sans-serif size=-1><input type=hidden name=domains value="lists.ximian.com"><br> <input type=hidden name=sitesearch value="lists.ximian.com"> Search mono-<b>bugs</b> </font><br>
</td></tr></TABLE>
</FORM>
</tr></td>
<tr><td>
<FORM method=GET action=http://www.google.com/custom>
<TABLE bgcolor=#FFFFFF cellspacing=0 border=0>
<tr valign=top>
<td>
<INPUT TYPE=text name=q size=31 maxlength=255 value="">
<INPUT TYPE=hidden name=q size=31 maxlength=255 value="mono-gc-list">
<INPUT type=submit name=sa VALUE="Search">
<input type="hidden" name="cof" value="GIMP:#00ff00;T:#ffffff;LW:401;BIMG:http://www.go-mono.com/images/bgsquares.gif;ALC:#ffffff;L:http://www.go-mono.com/images/mono.gif;GFNT:#cc7700;LC:#ee9900;LH:80;BGC:#444444;AH:center;VLC:#cccccc;S:http://www.go-mono.com;GALT:#eeee00;AWFID:45753ce73241ef7a;">
<font face=arial,sans-serif size=-1><input type=hidden name=domains value="lists.ximian.com"><br> <input type=hidden name=sitesearch value="lists.ximian.com"> Search mono-<b>gc-list</b> </font><br>
</td></tr></TABLE>
</FORM>
</tr></td>
<tr><td>
<FORM method=GET action=http://www.google.com/custom>
<TABLE bgcolor=#FFFFFF cellspacing=0 border=0>
<tr valign=top>
<td>
<INPUT TYPE=text name=q size=31 maxlength=255 value="">
<INPUT TYPE=hidden name=q size=31 maxlength=255 value="mono-cvs-list">
<INPUT type=submit name=sa VALUE="Search">
<input type="hidden" name="cof" value="GIMP:#00ff00;T:#ffffff;LW:401;BIMG:http://www.go-mono.com/images/bgsquares.gif;ALC:#ffffff;L:http://www.go-mono.com/images/mono.gif;GFNT:#cc7700;LC:#ee9900;LH:80;BGC:#444444;AH:center;VLC:#cccccc;S:http://www.go-mono.com;GALT:#eeee00;AWFID:45753ce73241ef7a;">
<font face=arial,sans-serif size=-1><input type=hidden name=domains value="lists.ximian.com"><br> <input type=hidden name=sitesearch value="lists.ximian.com"> Search mono-<b>cvs-list</b> </font><br>
</td></tr></TABLE>
</FORM>
</tr></td>
<tr><td>
<FORM method=GET action=http://www.google.com/custom>
<TABLE bgcolor=#FFFFFF cellspacing=0 border=0>
<tr valign=top>
<td>
<INPUT TYPE=text name=q size=31 maxlength=255 value="">
<INPUT TYPE=hidden name=q size=31 maxlength=255 value="mono-patches">
<INPUT type=submit name=sa VALUE="Search">
<input type="hidden" name="cof" value="GIMP:#00ff00;T:#ffffff;LW:401;BIMG:http://www.go-mono.com/images/bgsquares.gif;ALC:#ffffff;L:http://www.go-mono.com/images/mono.gif;GFNT:#cc7700;LC:#ee9900;LH:80;BGC:#444444;AH:center;VLC:#cccccc;S:http://www.go-mono.com;GALT:#eeee00;AWFID:45753ce73241ef7a;">
<font face=arial,sans-serif size=-1><input type=hidden name=domains value="lists.ximian.com"><br> <input type=hidden name=sitesearch value="lists.ximian.com"> Search mono-<b>patches</b> </font><br>
</td></tr></TABLE>
</FORM>
</tr></td>
</table>
</tr>
</table>
</center>
<!-- /Google Search with mods -->
</ul>
-54
View File
@@ -1,54 +0,0 @@
* mbas: Mono's Basic.NET Compiler.
MBAS is a CIL compiler for the Visual Basic language, an extended
version of VisualBasic.NET. It's based on the MCS compiler
and still in heavy development, though many language features are
already supported.
** What works
<ul>
* Classes, Fields and Methods. Properties are still
being worked on.
* Module definition and Sub functionality (TODO: Function's)
* Namespace Import, so can you reference, instantiate
and call external assemblies
* Parameter passing between Sub's. ByVal and ByRef
parameters are being worked on.
* Delegates
* Object creation
* Events - to a limited extent. You can declare a
Class-Field as 'WithEvents' and dynamic events (i.e
AddHandler MyButton.Click, Button1_OnClick). Please
beware: just after committing the code, I discovered
that the handler field in the AddHandler call is
case-sensitive, a remnant of mBas' mcs heritage)
* Statements supported are 'If..Then..Else' ,
'While..End While' and assignment statements. Simple
operators (+, -, *, /, >, <, =) should also
work. Other statements (For..Next, etc.) should be
quite trivial to implement.
</ul>
A lot of this stuff is implemented rebuilding proper expressions and
statements on top of the classes provided by mcs (look at the grammar -
mb-parser.jay - and compare it with cs-parser.jay, if interested).
** TODO-list
At this stage almost every element of the language must be still checked for
conformance to MS'implementation. Help is particularly needed for those areas
I know little of (mcs internals are still quite obscure to me). I'd like to
implement class properties, the missing statements, exception handling,
structures and actual event support (not necessarily in this order). Once we
have all this stuff set up and reasonably bug-free, more work could be done
on helper functions and Object-vars handling.
-34
View File
@@ -1,34 +0,0 @@
* Mono for beginners
Hinne Hettema and Jaime Anguiano Olarra are providing us with
nice and complete set of documents (HOWTOs) about how to install,
configure, run and test the software developed by the Mono Project.
You can read them online, get PDF versions or get the XML sources.
HTML Format (read it online)
For <a href="mono-beginning/t1.html">RPM Linux based systems</a>
For <a href="http://monoevo.sourceforge.net/mono-windows/mono-beginning-windows/t1.html">Microsoft Windows</a>
PDF Format
For <a href="mono-beginning.pdf">RPM Linux based systems</a>
XML Source
For <a href="mono-beginning.xml">RPM Linux based systems</a>
For <a href="http://monoevo.sourceforge.net/mono-windows/mono-beginning-windows.xml">Microsoft Windows</a>
Currently Hinne is working on a Mono Tools HOWTO. Which will be
very useful for the hackers that would like to get in touch with
Mono and Jaime is working out a Mono Beginning HOWTO for Debian
users.
File diff suppressed because it is too large. Load diff
File diff suppressed because it is too large. Load diff
+12 -56
View File
@@ -17,12 +17,6 @@ echo "Building Mono and dependencies in $here, installing to $here/install"
PATH=$here/install/bin:$here/install/lib:$PATH
# Make sure cygwin's libiconv is installed, or libtool blows its tiny mind
if [ ! -f /usr/lib/libiconv.la ]; then
echo "You need to install the cygwin \"libiconv\" package!"
exit -1
fi
# Check mono out first, so we can run aclocal from inside the mono dir (it
# needs to see which version of the real aclocal to run)
test -z "$CVSROOT" && CVSROOT=:pserver:[email protected]:/mono
@@ -48,26 +42,10 @@ fi
cvs checkout mono || exit -1
echo "Checking automake version"
automake_required="1.6.2"
automake_version=`automake --version | head -1 | awk '{print $4}' | tr -d '[a-zA-Z]' | sed 's/-.*$//g'`
echo "Found automake version $automake_version"
if expr $automake_version \< $automake_required > /dev/null; then
echo "Your automake is too old! You need version $automake_required or newer."
exit -1
else
echo "Automake version new enough."
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
# glib we're about to install in $here/install.
# glib we're about to install in $here/install. This script could
# attempt to be clever and see if glib 2 is already installed, too.
# --print-ac-dir was added in 1.2h according to the ChangeLog. This
@@ -78,17 +56,15 @@ fi
# it finds two copies of the m4 macros). The GIMP for Windows
# pkgconfig sets its prefix based on the location of its binary, so we
# dont need PKG_CONFIG_PATH (the internal pkgconfig config file
# $prefix is handled similarly). For the cygwin pkgconfig we do need to
# set it, and we need to edit the mingw pc files too.
# $prefix is handled similarly).
function aclocal_scan () {
# Quietly ignore the rogue '-I' and other aclocal flags that
# aren't actually directories...
#
# cd into mono/ so that the aclocal wrapper can work out which version
# of aclocal to run, and add /usr/share/aclocal too cos aclocal looks there
# too.
for i in `(cd mono && aclocal --print-ac-dir)` /usr/share/aclocal $ACLOCAL_FLAGS
# of aclocal to run
for i in `(cd mono && aclocal --print-ac-dir)` $ACLOCAL_FLAGS
do
if [ -f $i/$1 ]; then
return 0
@@ -115,17 +91,10 @@ function install_package() {
fi
}
# pkgconfig is only used during the build, so we can use the cygwin version
# if it exists
if aclocal_scan pkg.m4 ; then
install_pkgconfig=no
else
install_pkgconfig=yes
if ! aclocal_scan pkg.m4 ; then
ACLOCAL_FLAGS="-I $here/install/share/aclocal $ACLOCAL_FLAGS"
fi
# 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
@@ -136,28 +105,15 @@ fi
# Fetch and install pkg-config, glib, iconv, intl
if [ $install_pkgconfig = "yes" ]; then
install_package pkgconfig-0.11-20020310.zip bin/pkg-config.exe pkgconfig
else
echo "Not installing pkgconfig, you already seem to have it installed"
fi
install_package glib-2.0.4-20020703.zip lib/libglib-2.0-0.dll glib
install_package glib-dev-2.0.4-20020703.zip lib/glib-2.0.lib glib-dev
install_package pkgconfig-0.80-tml-20020101.zip bin/pkg-config.exe pkgconfig
install_package glib-1.3.12-20020101.zip lib/libglib-1.3-12.dll glib
install_package glib-dev-1.3.12-20020101.zip lib/glib-1.3.lib glib-dev
install_package libiconv-1.7.zip lib/iconv.dll iconv
install_package libiconv-dev-1.7.zip lib/iconv.lib iconv-dev
install_package libintl-0.10.40-20020101.zip lib/libintl-1.dll intl
install_package libgc-dev.zip lib/gc.dll gc-dev
if [ $install_pkgconfig = "no" ]; then
echo "Fixing up the pkgconfig paths"
for i in $here/install/lib/pkgconfig/*.pc
do
mv $i $i.orig
sed -e "s@^prefix=/target\$@prefix=$here/install@" < $i.orig > $i
done
export PKG_CONFIG_PATH=$here/install/lib/pkgconfig
fi
# Needed to find the libgc bits
# Needed to find the libiconv bits
CPPFLAGS="$CPPFLAGS -I$here/install/include"
LDFLAGS="$LDFLAGS -L$here/install/lib"
export CPPFLAGS
+12 -83
View File
@@ -1,4 +1,4 @@
#! /usr/bin/env bash
#!/bin/bash
# Script to automate the building of mono and its dependencies.
# Relies on wget being installed (could make it fall back to using
@@ -17,44 +17,6 @@ echo "Building Mono and dependencies in $here, installing to $here/install"
PATH=$here/install/bin:$PATH
LD_LIBRARY_PATH=$here/install/lib:$LD_LIBRARY_PATH
# Find a tool to fetch files. It must take an HTTP URL on the command line and
# save the file in the current directory. (It must also talk HTTP/1.1, which
# rules out BSD's ftp(1), at least on FreeBSD 4.4.)
viable_downloaders="wget fetch"
for i in $viable_downloaders
do
if which $i > /dev/null; then
downloader=`which $i`
break
fi
done
if [ -z "$downloader" ]; then
echo "Can't find a commandline download tool (tried: $viable_downloaders)"
exit -1
else
echo "Using $downloader to fetch files"
fi
# We need to prefer GNU make if there's a choice. BSD make falls over in
# the glib build if gtk-doc is disabled.
viable_makers="gmake make"
for i in $viable_makers
do
if which $i > /dev/null; then
MAKE=$i
break
fi
done
if [ -z "$MAKE" ]; then
echo "Can't find a make tool (tried: $viable_makers)"
exit -1
else
echo "Using $MAKE"
export MAKE
fi
# Need to install pkgconfig and set ACLOCAL_FLAGS if there is not a
# pkgconfig installed already. Otherwise set PKG_CONFIG_PATH to the
# glib we're about to install in $here/install. This script could
@@ -102,14 +64,14 @@ function install_package() {
echo "Installing $name..."
if [ ! -f $here/$tarfile ]; then
(cd $here && $downloader http://www.go-mono.com/archive/$tarfile)
wget http://www.go-mono.org/archive/$tarfile
fi
# Assume that the package built correctly if the dir is there
if [ ! -d $here/$dirname ]; then
# Build and install package
(cd $here && tar xzf $tarfile) || exit -1
(cd $here/$dirname; ./configure --prefix=$here/install $configure_options || exit -1; $MAKE || exit -1; $MAKE install || exit -1)
tar xzf $here/$tarfile || exit -1
(cd $here/$dirname; ./configure --prefix=$here/install $configure_options || exit -1; make || exit -1; make install || exit -1)
success=$?
if [ $success -ne 0 ]; then
echo "***** $name build failure. Run rm -rf $here/$dirname to have this script attempt to build $name again next time"
@@ -151,45 +113,12 @@ export LD_LIBRARY_PATH
export ACLOCAL_FLAGS
export PKG_CONFIG_PATH
# Freebsd puts iconv in /usr/local, so see if we need to add
# /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.
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
CPPFLAGS="$CPPFLAGS -I$here/install/include"
LDFLAGS="$LDFLAGS -L$here/install/lib"
export CPPFLAGS
export LDFLAGS
# Grab pkg-config, glib and libgc if necessary
# Grab pkg-config-0.8, glib-1.3.12 if necessary
if [ $install_pkgconfig = "yes" ]; then
install_package pkgconfig-0.8.0.tar.gz pkgconfig-0.8.0 pkgconfig ""
@@ -198,16 +127,16 @@ else
fi
if [ $install_glib = "yes" ]; then
install_package glib-2.0.6.tar.gz glib-2.0.6 glib ""
install_package glib-1.3.13.tar.gz glib-1.3.13 glib ""
else
echo "Not installing glib, you already seem to have it installed"
fi
if [ $install_libgc = "yes" ]; then
install_package gc6.1alpha5.tar.gz gc6.1alpha5 libgc "--enable-threads=pthreads"
LIBS="-ldl" install_package gc6.0.tar.gz gc6.0 libgc "--enable-threads=pthreads"
# make install didnt do the headers!
mkdir -p $here/install/include/gc
cp -r $here/gc6.1alpha5/include/* $here/install/include/gc
cp -r $here/gc6.0/include/* $here/install/include/gc
else
echo "Not installing libgc, you already seem to have it installed"
fi
@@ -237,12 +166,12 @@ elif [ ${CVSROOT:0:9} = ":pserver:" ]; then
fi
fi
(cd $here && cvs checkout mono) || exit -1
cvs checkout mono || exit -1
# Build and install mono
echo "Building and installing mono"
(cd $here/mono; ./autogen.sh --prefix=$here/install || exit -1; $MAKE || exit -1; $MAKE install || exit -1) || exit -1
(cd $here/mono; ./autogen.sh --prefix=$here/install || exit -1; make || exit -1; make install || exit -1) || exit -1
echo ""
-551
View File
@@ -1,551 +0,0 @@
<Mono newbie coders start file>
<h1> A little help for mono newbie coders </h1>
For those who are new to Mono and are impatient to contribute
with code (uhh... you are brave!!) here is the document you
should read.
You will see all Mono hackers say the same (great minds have
similar way of thinking): First, DO WRITE TESTS!!!. In order
to do that:
<ul>
* Start with the NUnit Tests Guidelines. In the cvs
they are located at: mcs/class/doc/NUnitGuideli...
* But wait, this is a document for impatient
people. So EVERYTHING should be here. Well, it is.
</ul>
<h2> The NUnit Tests Guidelines document </h2>
Mono NUnit Test Guidelines and Best Practices
Authors: Nick Drochak <[email protected]>
Martin Baulig <[email protected]>
Last Update: 2002-03-02
Rev: 0.3
<b> Purpose </b>
This document captures all the good ideas people have had
about writing NUnit tests for the mono project. This document
will be useful for anyone who writes or maintains unit tests.
<b> Other resources </b>
- mcs/class/README has an explanation of the build process and
how it relates to the tests.
- http://nunit.sourceforge.net is the place to find out about
NUnit
<b> Getting Started </b>
If you are new to writing NUnit tests, there is a template
you may use to help get started. The file is:
mcs/class/doc/TemplateTest.cs
(2.- This is the point two!. This file is just after the end
of the guidelines. Copy/paste it in another buffer. And keep
reading.)
Save a copy of this file in the appropriate test subdirecty
(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.
mcs/class/corlib/Test/System.Collections/CollectionBaseTest.cs
is a small one that might help.
(3.- You reached the third point. And as expected, it's just
here to tell you that the content of CollectionBaseTest.cs is
after the TemplateTest.cs code at the end of these
guidelines.)
The directory that will contain your new file depends on the
assembly/namespace of the class for which you are creating the
tests. Under mcs/class there is a directory for each assembly.
In each assembly there is a Test directory, e.g.
mcs/class/corlib/Test. In the Test directory there are
sub-directories for each namespace in the assembly, e.g.
mcs/class/corlib/Test/Sytem. Put your new test file in 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 will be automagically included
in the build and the tests will be run along with all the
others.
<b> Tips </b>
<b> Provide an unique error message for Assert() </b>
Include an unique message for each Assert() so that when the
assert 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.
Bad:
<pre>
AssertEquals("array match", compare[0], i1[0]);
AssertEquals("array match", compare[1], i1[1]);
AssertEquals("array match", compare[2], i1[2]);
AssertEquals("array match", compare[3], i1[3]);
</pre>
Good:
<pre>
AssertEquals("#A01", compare[0], i1[0]);
AssertEquals("#A02", compare[1], i1[1]);
AssertEquals("#A03", compare[2], i1[2]);
AssertEquals("#A04", compare[3], i1[3]);
</pre>
Once you used such a number in an Assert(), don't change it
later on - people might use it it identify the test in bug
reports or in mailing lists.
<b> Use AssertEquals() to compare things, not Assert(). </b>
Never compare two values with Assert() - if the test fails,
people have no idea what went wrong while AssertEquals()
reports the failed value.
Bad:
<pre>
Assert ("A01", myTicks[0] == t1.Ticks);
</pre>
Good:
<pre>
AssertEquals ("A01", myTicks[0], t1.Ticks);
</pre>
<b> Constructors </b>
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>
<b> Namespace </b>
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".
<b> Test your test with the microsoft runtime </b>
If possible, try to run your testsuite with the Microsoft
runtime on 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 ....
Don't worry if you're writing your test on Linux, other people
can test it for you on Windows.
Sometimes you may discover that a test doesn't show the
expected 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 list -
we'll forward this to the Microsoft people from time to time
to help them fix their documentation and runtime.
<pre>
-------------------- TemplateTest.cs begins ----------
// this is a template for making NUnit tests. Text enclosed
// in square brackets (and the brackets themselves) should be
// replaced by appropiate code.
// [File Name].cs - NUnit Test Cases for [explain here]
//
// [Author Name] ([Author email Address])
//
// (C) [Copyright holder]
//
// these are the standard namespaces you will need. You may
// need to add more depending on your tests.
using NUnit.Framework;
using System;
// all test namespaces start with "MonoTests." Append the
// Namespace that contains the class you are testing, e.g.
// MonoTests.System.Collections
namespace MonoTests.[Namespace]
{
// the class name should end with "Test" and start with the name
// of the class you are testing, e.g. CollectionBaseTest
public class [Class to be tested]Test : TestCase {
// there should be two constructors for your class. The first
// one (without parameters) should set the name to something
// unique.
// Of course the name of the method is the same as the name of
// the class
public [Constructor]() : base ("[Namespace.Class]") {}
public [Constructor](string name) : base(name) {}
// this method is run before each Test* method is called. You
// can put variable initialization, etc. here that is common to
// each test.
// Just leave the method empty if you don't need to use it.
protected override void SetUp() {}
// this method is run after each Test* method is called. You
// can put clean-up code, etc. here. Whatever needs to be done
// after each test. Just leave the method empty if you don't need
// to use it.
protected override void TearDown() {}
// this property is required. You need change the parameter for
// typeof() below to be your class.
public static ITest Suite {
get {
return new TestSuite(typeof([Classname here]));
}
}
// this is just one of probably many test methods in your test
// class. each test method must start with "Test". All methods
// in your class which start with "Test" will be automagically
// called by the NUnit framework.
public void Test[Something] {
// inside here you will exercise your class and then
// call Assert()
}
}
---------------------- TemplateTest.cs ends --------------
---------------------- CollectionBaseTest.cs begins ------
//
// System.Collections.CollectionBase
// Test suite for System.Collections.CollectionBase
//
// Author:
// Nick D. Drochak II
//
// (C) 2001 Nick D. Drochak II
//
using System;
using System.Collections;
using NUnit.Framework;
namespace MonoTests.System.Collections
{
public class CollectionBaseTest : TestCase
{
public CollectionBaseTest () : base
("System.Collection.CollectionBase testsuite")
{}
public CollectionBaseTest (String name) : base (name)
{}
// We need a concrete class to test the abstract base
// class
public class ConcreteCollection : CollectionBase
{
// These fields are used as markers to test
// the On* hooks.
public bool onClearFired;
public bool onClearCompleteFired;
public bool onInsertFired;
public int onInsertIndex;
public bool onInsertCompleteFired;
public int onInsertCompleteIndex;
public bool onRemoveFired;
public int onRemoveIndex;
public bool onRemoveCompleteFired;
public int onRemoveCompleteIndex;
public bool onSetFired;
public int onSetOldValue;
public int onSetNewValue;
public bool onSetCompleteFired;
public int onSetCompleteOldValue;
public int onSetCompleteNewValue;
// This constructor is used to test OnValid()
public ConcreteCollection()
{
IList listObj;
listObj = this;
listObj.Add(null);
}
// This constructor puts consecutive integers into the list
public ConcreteCollection(int i) {
IList listObj;
listObj = this;
int j;
for (j = 0; j< i; j++) {
listObj.Add(j);
}
}
// A helper method to look at a value in the
// list at a specific index
public int PeekAt(int index)
{
IList listObj;
listObj = this;
return (int) listObj[index];
}
// Mark the flag if this hook is fired
protected override void OnClear() {
this.onClearFired = true;
}
// Mark the flag if this hook is fired
protected override void OnClearComplete()
{
this.onClearCompleteFired = true;
}
// Mark the flag, and save the paramter if
// this hook is fired
protected override void OnInsert(int index,
object value)
{
this.onInsertFired = true;
this.onInsertIndex = index;
}
// Mark the flag, and save the paramter if
// this hook is fired
protected override void OnInsertComplete(int index,
object value)
{
this.onInsertCompleteFired = true;
this.onInsertCompleteIndex = index;
}
// Mark the flag, and save the paramter if this hook
// is fired
protected override void OnRemove(int index,
object value)
{
this.onRemoveFired = true;
this.onRemoveIndex = index;
}
// Mark the flag, and save the paramter if this hook
// is fired
protected override void OnRemoveComplete(int index,
object value)
{
this.onRemoveCompleteFired = true;
this.onRemoveCompleteIndex = index;
}
// Mark the flag, and save the paramters if this hook
// is fired
protected override void OnSet(int index, object oldValue,
object newValue)
{
this.onSetFired = true;
this.onSetOldValue = (int) oldValue;
this.onSetNewValue = (int) newValue;
}
// Mark the flag, and save the paramters if this hook
// is fired
protected override void OnSetComplete(int index,
object oldValue,
object newValue)
{
this.onSetCompleteFired = true;
this.onSetCompleteOldValue = (int) oldValue;
this.onSetCompleteNewValue = (int) newValue;
}
} // public class ConcreteCollection
public static ITest Suite {
get {
return new TestSuite
(typeof(CollectionBaseTest));
}
}
// Check the count property
public void TestCount() {
ConcreteCollection myCollection;
myCollection = new ConcreteCollection(4);
Assert(4 == myCollection.Count);
}
// Make sure GetEnumerator returns an object
public void TestGetEnumerator() {
ConcreteCollection myCollection;
myCollection = new ConcreteCollection(4);
Assert(null != myCollection.GetEnumerator());
}
// OnValid disallows nulls
public void TestOnValid() {
ConcreteCollection myCollection;
try {
myCollection = new ConcreteCollection();
}
catch (ArgumentNullException) {
}
}
// Test various Insert paths
public void TestInsert() {
ConcreteCollection myCollection;
int numberOfItems;
numberOfItems = 3;
// The constructor inserts
myCollection = new ConcreteCollection(numberOfItems);
Assert(myCollection.onInsertFired);
Assert(myCollection.onInsertCompleteFired);
// Using the IList interface, check inserts in the middle
IList listObj = myCollection;
listObj.Insert(1, 9);
Assert(myCollection.onInsertIndex == 1);
Assert(myCollection.onInsertCompleteIndex == 1);
Assert(myCollection.PeekAt(1) == 9);
}
// Test Clear and it's hooks
public void TestClear()
{
ConcreteCollection myCollection;
int numberOfItems;
numberOfItems = 1;
myCollection = new ConcreteCollection(numberOfItems);
myCollection.Clear();
Assert(myCollection.Count == 0);
Assert(myCollection.onClearFired);
Assert(myCollection.onClearCompleteFired);
}
// Test RemoveAt, other removes and the hooks
public void TestRemove()
{
ConcreteCollection myCollection;
int numberOfItems;
numberOfItems = 3;
// Set up a test collection
myCollection = new ConcreteCollection(numberOfItems);
// The list is 0-based. So if we remove the second one
myCollection.RemoveAt(1);
// We should see the original third one in it's place
Assert(myCollection.PeekAt(1) == 2);
Assert(myCollection.onRemoveFired);
Assert(myCollection.onRemoveIndex == 1);
Assert(myCollection.onRemoveCompleteFired);
Assert(myCollection.onRemoveCompleteIndex == 1);
IList listObj = myCollection;
listObj.Remove(0);
// Confirm parameters are being passed to the hooks
Assert(myCollection.onRemoveIndex == 0);
Assert(myCollection.onRemoveCompleteIndex == 0);
}
// Test the random access feature
public void TestSet()
{
ConcreteCollection myCollection;
int numberOfItems;
numberOfItems = 3;
myCollection = new ConcreteCollection(numberOfItems);
IList listObj = myCollection;
listObj[0] = 99;
Assert((int) listObj[0] == 99);
Assert(myCollection.onSetFired);
Assert(myCollection.onSetCompleteFired);
Assert(myCollection.onSetOldValue == 0);
Assert(myCollection.onSetCompleteOldValue == 0);
Assert(myCollection.onSetNewValue == 99);
Assert(myCollection.onSetCompleteNewValue == 99);
}
}
}
----------------------- CollectionBaseTest.cs ends --------
</pre>
<ul>
* If you use Emacs, you might want to use the .emacs
file and the package developed by Brad Merrill
mailto:[email protected]. It will allow you to
highlight and indent in C# style in your Emacs
editor. (XEmacs will still work but it'll also
complain).
* CSharpDevelop is a GPLed IDE developed by IC#Code.
Search for it at sourceforge if you are interested
in it.
* For those who Java: "A comparison of Microsoft's
C# programming language to Sun Microsystem's Java
Programming language" by Dare Obasanjo is a really good
(very complete) text to read.
* Suggest this point and more, now I can't think of
anything more.
</ul>
Enjoy!!.
(c) 2002, <a href="mailto:[email protected]">Jaime Anguiano Olarra</a>.
The parts included in this document are property of their
respective authors.
Note: The identation of the source code has been changed a bit
so it could fit better in the website. Anyway, as nothing more
changed, the files should work as expected.
-194
View File
@@ -1,194 +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>
* Write documentation.
* Write regression tests.
* Complete the implementations of the class libraries.
* 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>not assigned
</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>not assigned
</tr>
<tr>
<td>JIT (mono/mini/)
<td>Port the JIT to additional architectures.
Currently ports are in the works for ppc, 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>not assigned
</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>
</table>
-329
View File
@@ -1,329 +0,0 @@
* 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>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>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>
</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>
</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>Mono.Data.MySql (deprecated)
<ul>
<li>Currently, only works with version 3.23.x of MySQL</li>
<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>
</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>
<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>
</ul>
</li>
<li>Running the Example:
<pre>
mono TestExample.exe
</pre>
</li>
</ul>
** Testing for Mono's MySQL provider (Mono.Data.MySql)
<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>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"
(or)
"Host=hostname;Dbname=database;User=username;Passwd=password"
</pre>
<li>C# Example:
<pre>
using System;
using System.Data;
using Mono.Data.MySql;
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 = 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 Mono.Data.MySql.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 Mono.Data.MySql.dll
</pre>
</li>
</ul>
</li>
<li>Running the Example:
<pre>
mono TestExample.exe
</pre>
</li>
</ul>
-218
View File
@@ -1,218 +0,0 @@
* 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>Works on Windows and Linux. Should have no problems working on UNIX too.</li>
<li>Works on Windows via the native Windows odbc32.dll</li>
<li>Works on Linux via:
<ul>
<li><a href="http://www.unixodbc.org/">unixODBC</a> which has
commercial support
from <a href="http://www.easysoft.com/">Easysoft</a></li>
<li><a href="http://www.iodbc.org/">iODBC</a> which has
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://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.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/default.asp">MS Access</a>
(via <a href="http://mdbtools.sourceforge.net/">MDB Tools</a> on UNIX)</li>
</ul>
<li>ODBC Provider created by Brian Ritchie.</li>
<li>Does not support trusted connections</li>
</ul>
** Current Status
<ul>
<li>Can Connect on:
<ul>
<li>Windows via native Windows odbc32.dll</a></li>
<li>Linux via:
<ul>
<li>unixODBC's libodbc.so</li>
<li>iODBC's libiodbc.so</li>
</ul>
</li>
</ul>
</li>
<li>Various databases have been tested using their
ODBC drivers: MySQL, PostgreSQL, Oracle, IBM DB2, and Microsoft SQL Server</li>
<li>Can execute non-query commands via ExecuteNonQuery of a OdbcCommand</li>
<li>Can execute aggreates and retrieve a single row single column result via
ExecuteScalar of a OdbcCommand</li>
<li>Can execute queries via ExecuteReader of a OdbcCommand and
retrieve results using an OdbcDataReader</li>
<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
<ul>
<li>Fixing bugs
<li>Testing with other setups
</ul>
** Testing ODBC provider with IBM DB2 Universal Database
<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-3.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
<ul>
<li><a href="http://www.unixodbc.com/doc/db2.html">unixODBC web page about IBM DB2</a></li>
<li><a href="http://www-3.ibm.com/software/data/db2/udb/ad/v8/cli/t0010406">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"
</pre>
</li>
<li>Here is a ConnectionString format if you do not have a DSN (have not
gotten this to work though):
<pre>
"DRIVER={MySQL ODBC 3.51 Driver};" +
"SERVER=localhost;DATABASE=test;" +
"UID=myuserid;PASSWORD=mypassword;" +
"OPTION=3";
</pre>
</li>
<li>C# Example:
<pre>
using System;
using System.Data;
using System.Data.Odbc;
public class Test
{
public static void Main(string[] args)
{
// have an ODBC DSN setup named MYSQLDSN
// that accesses a MySQL database via
// MyODBC driver for ODBC with a
// hostname of localhost and database test
string connectionString =
"DSN=MYSQLDSN;" +
"UID=myuserid;" +
"PWD=mypassword";
IDbConnection dbcon;
dbcon.Open();
dbcon = new OdbcConnection(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.CommandText = 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
</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
</pre>
</li>
</ul>
</li>
<li>Running the Example:
<pre>
mono TestExample.exe
</pre>
</li>
</ul>
-1507
View File
File diff suppressed because it is too large. Load diff
-153
View File
@@ -1,153 +0,0 @@
* OLE DB Provider
<ul>
<li> Provides a OleDb-like provider for Mono
using <a href="http://www.gnome-db.org/">GDA</a> as the data access layer.</li>
<li> Exists in namespace System.Data.OleDb and assembly System.Data</li>
<li>Created by Rodrigo Moya</li>
<li>LibGDA has providers for:</li>
<ul>
<li><a href="http://www.mysql.com/">MySQL</a></li>
<li><a href="http://www.postgresql.org/">PostgreSQL</a></li>
<li>XML</li>
<li>ODBC (via <a href="http://www.unixodbc.org/">unixODBC</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> and
<a href="http://www.microsoft.com/sql/default.asp">Microsoft SQL Server</a> (
via <a href="http://www.freetds.org/">FreeTDS</a>)</li>
<li><a href="http://www-3.ibm.com/software/data/db2/">IBM DB2 Universal Database</a></li>
<li><a href="http://www.hwaci.com/sw/sqlite/download.html">SQL Lite</a></li>
<li><a href="http://www.microsoft.com/office/access/default.asp">MS Access</a></li>
(via <a href="http://mdbtools.sourceforge.net/">MDB Tools</a>)</li>
</ul>
</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
<ul>
<li>The OleDb provider is working with libgda (an OLE-DB/ADO data access for Unix).
The C-Sharp bindings to libgda currently work - meaning they can compile, run,
and you can connect to a
PostgreSQL database via libgda via the C-Sharp bindings to libgda.</li>
<li>Basic
functionality (execution of commands, data retrieval, transactions, etc) are
now working.</li>
<li>An inital implementation of GetSchemaTable() for
the OleDbDataReader has been checked into cvs. GetSchemaTable() isn't correct for OleDb,
but the foundation is there.</li>
</ul>
** Action Plan
<ul>
<li>Current focus is on filling up the missing pieces (Data adapters
mainly) and schema support.</li>
<li>We need help building libgda on Windows though. libgda
builds find on linux though.</li>
<li>Need to make the OleDb provider compatible with the OleDb provider in Microsoft .NET</li>
</ul>
** Testing OleDb with libgda's PostgreSQL provider
<ul>
<li>Requires a working mono and mcs</li>
<li>Requires Linux because the OleDb provider uses libgda and libgda only
works on Linux.</li>
<li>Connection String format: "Provider=providerName;...". providerName is the
name of the Provider you use, such as, PostgreSQL, MySQL, etc. The elipsis ...
means that the connection parameters are dependent upon the provider being used and
are passed to libgda for connecting. Such paramters, can be: Database, User ID, Password,
Server, etc...</li>
<li>See the test TestOleDb.cs found at mcs/class/System.Data/System.Data.OleDb</li>
<li>C# Example for Mono's System.Data.OleDb:
<pre>
using System;
using System.Data;
using System.Data.OleDb;
public class Test
{
public static void Main(string[] args)
{
// there is a libgda PostgreSQL provider
string connectionString =
"Provider=PostgreSQL;" +
"Addr=127.0.0.1;" +
"Database=test;" +
"User ID=postgres;" +
"Password=fun2db";
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
// 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 = 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
</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
</pre>
</li>
</ul>
</li>
<li>Running the Example:
<pre>
mono TestExample.exe
</pre>
</li>
</ul>
-184
View File
@@ -1,184 +0,0 @@
* 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</li>
<li>Untested, but should work with Oracle 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>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
<ul>
<li>OracleConnection can connect and disconnect to an Oracle 8i database on
Windows and Linux via OCI (Oracle Call-level Interface)</li>
<li>No longer uses a glue library (a library between the System.Data.OracleClient.dll
assembly and the oci library). In Current Mono cvs, System.Data.OracleClient
directly platform invokes into the oci library thanks to Tim Coleman.</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>Can execute simple DML SQL statements, such as,
INSERT a row into the EMP table via the OracleCommand's ExecuteNonQuery method</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.</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. The
Data Adapter is abstract enough that it should work as expected.</li>
<li>Lots of missing functionality and bugs.</li>
<li>Works with SQL# command-line and GTK# versions in cvs. Only works with
simple character data though. SQL# For GTK# can only show the results to
the TextView because the Data Adapter is not yet available</li>
</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>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 (UNKNOWN)</li>
<li>Support LOBs</li>
<li>Support all the data types</li>
<li>Implement Connection pooling</li>
<li>Security</li>
</ul>
** Testing System.Data.OracleClient
<ul>
<li>Have a working mono and mcs</li>
<li>Have access to an Oracle 8i 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>Make sure System.Data.OracleClient.dll assembly is built, if not, go
into System.Data.OracleClient and do a make -f makefile.gnu (on Linux) or
../../nant/NAnt.exe (on Windows using Cygwin).</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"
</pre>
</li>
<li>C# Example:
<pre>
using System;
using System.Data;
using System.Data.OracleClient;
public class Test
{
public static void Main (string[] args)
{
string connectionString =
"Data Source=testdb;" +
"User ID=scott;" +
"Password=tiger;";
IDbConnection dbcon;
dbcon = new OracleConnection (connectionString);
dbcon.Open ();
IDbCommand dbcmd = dbcon.CreateCommand ();
string sql = "SELECT ename, job FROM scott.emp";
dbcmd.CommandText = sql;
IDataReader reader = dbcmd.ExecuteReader ();
while (reader.Read ()) {
string employeeName = reader["ename"];
string job = reader["job"];
Console.WriteLine ("Employee Name: {0} Job: {1}",
employeeName, job);
}
// clean up
reader.Close ();
reader = null;
dbcmd.CommandText = sql;
dbcmd.ExecuteNonQuery ();
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 System.Data.OracleClient.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 System.Data.OracleClient.dll
</pre>
</li>
</ul>
</li>
<li>Running the Example:
<pre>
mono TestExample.exe
</pre>
</li>
</ul>
-34
View File
@@ -1,34 +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.
</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
@@ -100,11 +100,6 @@
available, means that trojans or worms could be built
into the products by malicious engineers.
Various government officials in non-US countries also
have a policy that no state sensitive information can
be held by foreign companies in foreign soil. A natural
matter of national security to some.
* <b>Security:</b> With a centralized system like
Passport, imagine the repercussions of a malicious
hacker gaining access to the Passport database.
-578
View File
@@ -1,578 +0,0 @@
* PostgreSQL Data Provider
There are two ADO.NET data providers for <a href="http://www.postgresql.org/">PostgreSQL</a> in Mono:
<ul>
<li><a href="http://gborg.postgresql.org/project/npgsql/projdisplay.php">Npgsql</a>
<ul>
<li>a .NET Managed Data Provider for PostgreSQL
<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>
</ul>
</li>
<li>Mono.Data.PostgreSQL (deprecated)
<ul>
<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>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>
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>
<li>We can execute multiple queries and do a NextResult() in PgSqlDataReader()
to get the next result set.</li>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<li>A lot of Exceptions need to be thrown for various exceptions. However,
PgSqlException, PgSqlErrorCollection, and PgSqlError have been partially
implemented.</li>
<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>
</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>
** Testing Mono.Data.PostgreSqlClient
<ul>
* <p>In order to test Mono.Data.PostgreSqlClient, you will need to have
access to a remote PostgreSQL DBMS, or you will have to install
one locally. PostgreSQL was the first ADO.NET provider created in Mono.
<p>Why use PostgreSQL? Because it is free software, has a client
library that is easy to use, PostgreSQL is easy to install on
Unix and Windows (using the Cygwin install program), not difficult to setup after
installation, and it runs under: Linux,
Windows (via cygwin and ipc-daemon), Unix, and
others. This allowed us to create the
System.Data functionality in Mono much quicker.
<p>If you plan on using a remote PostgreSQL DBMS Server,
than you will need to have the PostgreSQL client software on your
local computer that includes libpq.so (pq.dll on Windows).
<p>The System.Data tests use this connection string to connect
to the PostgreSQL database named "test" at host "localhost" as
user "postgres".
<pre>
"Server=localhost;Database=test;User ID=postgres;Password=fun2db"
(or)
"host=localhost;dbname=test;user=postgres;password=fun2db"
</pre>
</ul>
<p>Installation instructions for PostgreSQL DBMS:
<b>On Unix</b>
<ul>
* Read the PostgreSQL Installation Instructions
at \usr\doc\postgresql-x.x.x\html\installation.html
* Depending on your Unix system,
PostgreSQL maybe already installed, a database user 'postgres' created,
a linux user 'postgres' created and initdb ran. Or maybe not.
<pre>
su
adduser postgres
mkdir /usr/local/pgsql/data
chown postgres /usr/local/pgsql/data
su - postgres
initdb -D /usr/local/pgsql/data
postmaster -i -D /usr/local/pgsql/data
createdb test
psql test
</pre>
* Make sure you have a database user named postgres. It is best to install
the PostgreSQL DBMS under linux user postgres. When you run the postmaster,
run it under the user postgres as well. If this was not done, then you
will need to create a user named postgres for the System.Data tests.
* If you already installed PostgeSQL and you do not have a database
user named postgres, then you can create user postgres using psql:
<pre>
psql test
create user postgres with password 'fun2db';
</pre>
* The postmaster must be run with -i option.
* In the /usr/local/pgsql/data/pg_hba.conf file, you need
to have the AUTH_TYPE set to md5. You can read more on this at
/usr/doc/postgresql-7.2.1/html/client-authentication.html
or wherever your
PostgreSQL html docs are located. See the 2nd line below,
host 127.0.0.1 has an AUTH_TYPE md5 in pg_hba.conf.
<pre>
# TYPE DATABASE IP_ADDRESS MASK AUTH_TYPE
local all trust
host all 127.0.0.1 255.255.255.255 md5
</pre>
* If you can not find your PostgreSQL documentation locally or you
did not install it, then you
can get it <a href="http://www.postgresql.org/idocs/">here</a>.
</ul>
<b>On Windows</b>
<ul>
* Use the <a href="http://www.cygwin.com/">Cygwin</a> installer to
install the PostgreSQL DBMS. It is
found in the database category.
* <p>Read the file postgres-x.x.README at /usr/doc/Cygwin and read
the requirements to install PostgreSQL. Those requirements
are included with cygwin except cygipc. A default installtion
of cygwin does not install everything you will need, so on the
safe side, just include everything when installing cygwin.
* <p>The -x.x in postgres-x.x is the version of your PostgreSQL DBMS.
* <p>Once Cygwin has installed the PostgreSQL DBMS on your computer,
read the file FAQ_MSWIN which is available
in /usr/doc/postgres-x.x
* <p>Important notes from this file are:
<ul>
<p><b>2.</b> - Install the latest <a href="http://www.neuro.gatech.edu/users/cwilson/cygutils/cygipc/index.html">CygIPC</a> package.
Cygwin includes a utility bunzip2 which can be used to unzip it. Now, change to
the root directory by
typing "cd /" then
you can use "tar xvf cygipc.xxx.tar" to untar it
in the root directory in cygwin.
<p>The cygipc package contains the support to run ipc-daemon
that you will need
to run before you can
run the PostgreSQL DBMS Server daemon (postmaster) or run
initdb which initializes the PostgreSQL database.
<p><b>3.</b> The Cygwin bin directory has to be placed in
the path before the Windows program directories,
for example, C:\cygwin\bin
<p><b>My own note.</b> In the Windows control panel, I set
the environment variables PATH to my cygwin /usr/local/bin,
/usr/bin, and /bin. I also set my LD_LIBRARY_PATH to
/usr/local/lib and /usr/lib. For example:
<p>
<pre>
PATH=c:\cygwin\usr\local\bin;c:\cygwin\usr\bin;c:\cygwin\bin;
LD_LIBRARY_PATH=c:\cygwin\usr\local\lib;c:\cygwin\usr\lib;
</pre>
<p><b>4.</b> Start the ipc-daemon that came with the cygipc
package. There
are two ways to do this: run it from the command line as:
<p>
<pre>
ipc-daemon &
</pre>
<p>or you can set it up as a Windows service. See the
file cygrunsrv.README at /usr/doc/Cygwin on how to do this
for ipc-daemon and postmaster. Note the
troubleshooting section at the end of
the cygrunsrv.README file.
<p>To install ipc-daemon as a service,
you just have to run
<p>
<pre>
ipc-daemon --install-as-service' (--remove-as-service)
</pre>
<p>and then run
<pre>
net start ipc-daemon
</pre>
</ul>
<p>Read the installation.html file
at /usr/doc/postgresql-x.x/html/installation.html
<p>You will see in this file that you will need to
run the following commands:
<p>
<pre>
mkdir /usr/local/pgsql/data
initdb -D /usr/local/pgsql/data
postmaster -D /usr/local/pgsql/data
createdb test
psql test
</pre>
<p>When you need to connect to the database,
you will need ipc-daemon and postmaster running. Start ipc-daemon
before any of the command above. If you restart your computer, you
need to start ipc-daemon and postmaster either manually or as a
service.
<p>psql is a command-line PostgreSQL client tool to
enter and run SQL commands and queries.
<p>If there is no database user named postgres, create a user named
postgres with the following SQL command in the client tool psql:
<p>
<pre>
psql test
create user postgres with password 'fun2db';
</pre>
<p>The only reason I say this is so you can easily use the System.Data tests
without having to change the database, userid, etc.
</ul>
<p>In the path mcs/class/System.Data/Test
there is a test for Mono.Data.PostgreSqlClient named
PostgreTest.cs. Thanks goes to Gonzalo for creating the original
PostgreSQL test.
<p>
To compile the PostgresTest.cs program, do:
<p>
<pre>
mcs PostgresTest.cs \
-r System.Data.dll \
-r Mono.Data.PostgreSqlClient.dll
</pre>
<p>If there are compile errors, such as, can not convert IDbConnection
to PgSqlConnection, then you need to run mcs like:
<pre>
mono C:/cygwin/home/MyHome/mono/install/bin/mcs.exe \
PostgresTest.cs \
-r System.Data.dll \
-r Mono.Data.PostgreSqlClient.dll
</pre>
<p>
To run using mint, do:
<p>
<pre>
mint PostgresTest.exe
</pre>
<p>
To run using mono, do:
<pre>
mono PostgresTest.exe
</pre>
<p>C# Example for Mono.Data.PostgreSqlClient:
<pre>
using System;
using System.Data;
using Mono.Data.PostgreSqlClient;
public class Test
{
public static void Main(string[] args)
{
string connectionString =
"Server=localhost;" +
"Database=test;" +
"User ID=postgres;" +
"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
// 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 = 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 Mono.Data.PostgreSqlClient.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 Mono.Data.PostgreSqlClient.dll
</pre>
</li>
</ul>
</li>
<li>Running the Example:
<pre>
mono TestExample.exe
</pre>
</li>
</ul>
** Testing Npgsql
<ul>
<li>Have a working mono and mcs</li>
<li>Get <a href="http://gborg.postgresql.org/project/npgsql/projdisplay.php">Npgsql</a>
and make sure the binary assembly Npgsql.dll is installed in the same place that the
mono class libraries are located.
<li>Read the Testing notes for Mono.Data.PostgreSqlClient too
<li>C# Example for Npgsql:
<pre>
using System;
using System.Data;
using Npgsql;
public class Test
{
public static void Main(string[] args)
{
string connectionString =
"Server=localhost;" +
"Database=test;" +
"User ID=postgres;" +
"Password=fun2db;";
IDbConnection dbcon;
dbcon.Open();
dbcon = new NpgsqlConnection(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.CommandText = 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 Npgsql.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 Npgsql.dll
</pre>
</li>
</ul>
</li>
<li>Running the Example:
<pre>
mono TestExample.exe
</pre>
</li>
</ul>
-33
View File
@@ -1,33 +0,0 @@
* Mono PowerPC Port
** Status
It passes and compiles the same amount of mono tests as on the x86 architecture.
mcs is self hosting on Linux/PPC.
*** Interpreter
Up to date.
*** Jitter
Start the port
** Documentation
*** PowerPC architecture:
<A HREF="http://e-www.motorola.com/brdata/PDFDB/docs/MPCFPE32B.pdf">PowerPC Programming environments manual</A><BR>
<A HREF="http://e-www.motorola.com/brdata/PDFDB/docs/MPC7410UM.pdf">G4 (7410) User's manual</A>
There's a very nice introduction to PowerPC assembly language
at <a
href="http://www-106.ibm.com/developerworks/library/l-ppc/">http://www-106.ibm.com/developerworks/library/l-ppc/</a>.
*** Calling conventions:
<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
-24
View File
@@ -1,24 +0,0 @@
* Open Projects
The .NET framework is a good first in terms of a new
development foundation, but it falls short of providing
higher-level components or building blocks for people to
reuse.
A few ideas of projects and classes that would be useful to
develop applications follows:
** EOG component
** XmlStorageSystem component
* Gtk# related projects
Gnome Canvas Bindings.
Bezier Canvas Item Binding.
* Graphical bindings
Binding for the Libart library
-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?
+18 -78
View File
@@ -11,13 +11,9 @@
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>
The changes between .NET 1.0 and .NET 1.1 are available <a href="http://www.csharphelp.com/archives2/archive406.html">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>
** IRC
@@ -26,19 +22,6 @@
** Mono related sites.
The Mono Tutorial:
<a href="http://go-mono.com/tutorial/">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>.
Sergey's web page on Mono resources:
<a href="http://mono.eurosoft.od.ua">http://mono.eurosoft.od.ua</a>
@@ -47,10 +30,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>
@@ -66,14 +45,6 @@
href="http://www.foundstone.com/pdf/dotnet-security-framework.pdf">.NET
security architecture</a>.
** Development Tools
A tool to compare two assemblies:
<ul>
<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>
@@ -87,8 +58,8 @@
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>
@@ -132,57 +103,26 @@
There are a number of related projects to Mono:
<li><b>Development tools</b></li>
<ul>
* <a
href="http://www.icsharpcode.net/OpenSource/SD/default.asp">Sharp
Develop:</a> an IDE for the C# language written in C#.
* <a href="http://nunit.sourceforge.net">NUnit:</a> A
testing framework for .NET classes.
* <a
href="http://www.improve-technologies.com/alpha/esharp/">Eclipse
Plugin for C#</a>
* <a
href="http://janet-js.sourceforge.net/">Janet:</a>
an implemention of ECMAScript (the standarized
version of JavaScript) in C#
* <a
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://9mm.com/~ogl/sdldotnet/">SDL for
.NET:</a> Bindings for the popular SDL graphics library.
* C# bindings for OpenGL and SDL are available here: <a
href="http://csgl.sourceforge.net">http://csgl.sourceforge.net</a>
* <a
href="http://qtcsharp.sourceforge.net">Qt#:</a>
C# bindings for the Qt toolkit.
* <a
href="http://codigolivre.org.br/projects/monoqle">Project MonoQLE:</a> a C# Message Queue Server.
Sorry only in portuguese, for now.
</ul>
<li><b>Programming languages:</b></li>
<ul>
* <a
href="http://janet-js.sourceforge.net/">Janet:</a>
an implemention of ECMAScript (the standarized
version of JavaScript) in C#
</ul>
<li><b>Other projects</b></li>
<ul>
* <a
href="http://www.improve-technologies.com/alpha/esharp/">Eclipse
Plugin for C#</a>
* <a href="http://nunit.sourceforge.net">NUnit:</a> A
testing framework for .NET classes.
* <a href="http://www.kaffe.org">Kaffe:</a> A popular
Free Software JIT engine for Java.
@@ -190,18 +130,18 @@
* <a href="http://www.intel.com/research/mrl/orp">ORP:</a> A research
JIT/VM/GC system from Intel.
* C# bindings for OpenGL and SDL are available here: <a
href="http://csgl.sourceforge.net">http://csgl.sourceforge.net</a>
* <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
Documentation on GNOME, and the GNOME APIs is available from
Documnetation on GNOME, and the GNOME APIs is available from
the <a href="http://developer.gnome.org">developer</a> site at
GNOME:
+70 -78
View File
@@ -1,82 +1,71 @@
* 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, but we working on incorporating the ORP GC engine.
The Mono runtime can be used as a stand-alone process, or it
can be <a href="embedded-api">embedded into applications</a> (see
the documentation in mono/samples/embed for more details).
** Executing MSIL/CIL images
Embedding the Mono runtime allows applications to be extended
in C# while reusing all of the existing C and C++ code.
The code will load an executable and map the references to
external assemblies to our own version of the assemblies on
Linux.
Paolo Molaro did a presentation on the current JIT engine and
the new JIT engine. You can find his <a
href="http://primates.ximian.com/~lupus/slides/jit/">slides
here</a>
** Current JIT Engine: technical details (<b>updated, June 28th, 2003</b>)
We have re-written our JIT compiler. We wanted to support a
number of features that were missing:
Our roadmap looks like this, this has been updated as of
<b>Dec 18, 2001</b>:
<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.
* Milestone 1: <b>Done</b> Fully read and parse all CIL byte-codes
and metadata tokens (ie, a disassembler).
Although in Mono this has not been a visible problem, we
wanted to pro-actively address this problem.
* Milestone 2: <b>Done</b> Complete an interpreter for CIL byte
codes. This interpreter can be used temporarly to
run CIL byte code on a system where no JIT is
available.
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.
* Milestone 3: <b>Done</b>Define an <i>lburg</i>-like
instruction selector for the JITer for Intel.
This is done in the Microsoft.NET world with a tool
called ngen.exe
* Milestone 4: <b>Done</b> Implement JITer. This is where our
current efforts are focused on, the JITer currently runs
all of the code we have tested on it. The major limitation
is that our class libraries are not complete, and hence not
every application can be ran.
* 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.
* Milestone 5: Port of the JITer to non IA32 systems.
</ul>
A setup similar to the Kaffe JIT engine will be used to
layout the code to support non-IA32 architectures. Our work
will be focused on getting a IA32 version running first.
The JIT engine works on Linux and Win32, although you
will need to install the CygWin32 development tools to get a
Unix-like compilation environment (mostly we use GNU make in
a few of the makefiles).
** JIT Engine (<b>updated, April 21, 2002</b>)
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:
<ul>
@@ -86,18 +75,11 @@
* Inlining.
* Constant folding, copy propagation, dead code elimination.
* Constant folding.
Although compilers typically do
constant folding, the combination of inlining with
constant folding gives some very good results.
* 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 +88,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 +98,30 @@
</ul>
** Future plans
We are evaluating the future directions for the JIT engine:
both from our needs (optimizations like inlining, better register allocation,
instruction scheduling, and porting to other CPUs).
We have not yet decided how we will evolve the JIT engine. We
might just upgrade our current architecture, and provide optimizations as
an extra layer.
** 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 +145,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 +174,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>
-214
View File
@@ -1,214 +0,0 @@
* Microsoft SQL Server Provider
<ul>
<li>ADO.NET Provider for Microsoft SQL Server 7/2000 databases</li>
<li>Exists in namespace System.Data.SqlClient and assembly System.Data</li>
<li>Created by Tim Coleman</li>
<li>Used the <a href="http://www.freetds.org/">FreeTDS</a> and
<a href="http://jtds.sourceforge.net/">jTDS</a> projects as resources.</li>
<li>Implemented in 100% C#</li>
<li>Is similar to the Mono.Data.TdsClient and Mono.Data.SybaseClient providers.</li>
<li>Requires the assembly Mono.Data.Tds.dll which implements the TDS protocol in 100% C#.</li>
<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>
</ul>
** Current Status
<ul>
<li>Able to connect to Microsoft SQL Server 7/2000 databases</li>
<li>Connection pooling works.</li>
<li>Stored Procedures work</li>
<li>Parameters work.</li>
<li>Prepare works.</li>
<li>SQL commands can be executed
via ExecuteNonQuery() of a SqlCommand.</li>
<li>SQL aggregates can be executed and a single row and single column
result can be retrieved via ExecuteScalar() of a SqlCommand</li>
<li>SQL queries can be executed via ExecuteReader() and results
can be retrieved via SqlDataReader.</li>
<li>a DataTable with schema info about a result can be gotten via GetSchemaTable()
in a SqlDataReader</li>
<li>XML can be read via ExecuteXmlReader in a SqlCommand.</li>
<li>Data can be filled in a DataTable in a DataSet via a SqlDataAdapter</li>
<li>Uses TDS Protocol Version 7.0</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>
<li>Works in the SQL# command-line and GTK# GUI version</li>
</ul>
** Action plan
<ul>
<li>Connection timeouts is being developed now</li>
<li>Needs more testing</li>
<li>Would like to figure out how to connect via Trusted_Connection or Integrated Security</li>
<li>Start work on TDS Protocol Version 8.0 support</li>
</ul>
** Testing
<ul>
<li>Have a working mono and mcs installed</li>
<li>Have access to a Microsoft SQL Server database
or either download it:
<ul>
<li><a href="http://www.microsoft.com/sql/default.asp">Microsoft SQL Server</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. If using
MSDE 2000, make sure you have the special Service Pack 3 for MSDE 2000.</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:
<pre>
Server=hostname;Database=databaseName;User ID=userid;Password=password
</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;
using System.Data;
using System.Data.SqlClient;
public class Test
{
public static void Main(string[] args)
{
string connectionString =
"Server=localhost;" +
"Database=pubs;" +
"User ID=myuserid;" +
"Password=mypassword;";
IDbConnection dbcon;
dbcon = new SqlConnection(connectionString);
dbcon.Open();
IDbCommand dbcmd = dbcon.CreateCommand();
string sql =
"SELECT fname, lname " +
"FROM employee";
dbcmd.CommandText = sql;
IDataReader reader = dbcmd.ExecuteReader();
while(reader.Read()) {
string FirstName = reader["fname"];
string LastName = reader["lname"];
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
</pre>
</li>
<li>Build on Windows via Cygwin:
<pre>
mono C:/cygwin/home/MyHome/mono/install/bin/mcs.exe \
TestExample.cs -r System.Data.dll
</pre>
</li>
</ul>
</li>
<li>Running the Example:
<pre>
mono TestExample.exe
</pre>
</li>
</ul>
-143
View File
@@ -1,143 +0,0 @@
* 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>
</ul>
** Current Status
<ul>
<li>Able to connect, execute commands, and retrieve data...</li>
<li>Works in mPhoto by providing access to a SQL Lite database to store images.</li>
</ul>
** Action Plan
<ul>
<li>Create a DataAdapter for SQL Lite named SqliteDataAdapter that can be used to
Fill a DataTable in a DataSet</li>
<li>Get the method GetSchemaTable() in class SqliteDataReader to return a DataTable
that works</li>
</ul>
** Testing
<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;
using System.Data;
using Mono.Data.SqliteClient;
public class Test
{
public static void Main(string[] args)
{
string connectionString = "URI=file:SqliteTest.db";
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 = reader[0];
string LastName = reader[1];
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 Mono.Data.SqliteClient.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 Mono.Data.SqliteClient.dll
</pre>
</li>
</ul>
</li>
<li>Running the Example:
<pre>
mono TestExample.exe
</pre>
</li>
</ul>
+1 -1
View File
@@ -11,7 +11,7 @@
* The Mono JIT engine (<b>mono</b>. The JIT engine is
the real
virtual machine that we support. It is
currently functional, and we are improving its speed,
functionaly currently, and we are improving its speed,
and making it feature complete.
* A CIL bytecode interpreter (<b>mint</b>). This
-155
View File
@@ -1,155 +0,0 @@
* Sybase Data Provider
<ul>
<li>ADO.NET Provider for Sybase SQL Server databases</li>
<li>Exists in namespace Mono.Data.SybaseClient and assembly Mono.Data.SybaseClient</li>
<li>Created by Tim Coleman</li>
<li>Used the <a href="http://www.freetds.org/">FreeTDS</a> and
<a href="http://jtds.sourceforge.net/">jTDS</a> projects as resources.</li>
<li>Implemented in 100% C#</li>
<li>Is similar to the Mono.Data.TdsClient and System.Data.SqlClient providers.</li>
<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>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
<ul>
<li>Able to connect to Sybase databases</li>
<li>SQL commands can be executed
via ExecuteNonQuery() of a SybaseCommand.</li>
<li>SQL aggregates can be executed and a single row and single column
result can be retrieved via ExecuteScalar() of a SybaseCommand</li>
<li>SQL queries can be executed via ExecuteReader() and results
can be retrieved via SybaseDataReader.</li>
<li>a DataTable with schema info about a result can be gotten via GetSchemaTable()
in a SybaseDataReader</li>
<li>Data can be filled in a DataTable in a DataSet via a SybaseDataAdapter</li>
</ul>
** Action plan
<ul>
<li>Connection timeouts is being developed now.
<li>Needs more testing...
</ul>
** Testing
<ul>
<li>Have a working mono and mcs installed</li>
<li>Have access to a Sybase database
or either download it:
<ul>
<li><a href="http://www.sybase.com/downloads">Sybase</a></li>
</ul>
</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;
using System.Data;
using Mono.Data.SybaseClient;
public class Test
{
public static void Main(string[] args)
{
string connectionString =
"Server=localhost;" +
"Database=pubs;" +
"User ID=myuserid;" +
"Password=mypassword;";
IDbConnection dbcon;
dbcon = new SybaseConnection(connectionString);
dbcon.Open();
IDbCommand dbcmd = dbcon.CreateCommand();
string sql =
"SELECT fname, lname " +
"FROM employee";
dbcmd.CommandText = sql;
IDataReader reader = dbcmd.ExecuteReader();
while(reader.Read()) {
string FirstName = reader["fname"];
string LastName = reader["lname"];
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 Mono.Data.SybaseClient.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 Mono.Data.SybaseClient.dll
</pre>
</li>
</ul>
</li>
<li>Running the Example:
<pre>
mono TestExample.exe
</pre>
</li>
</ul>
-164
View File
@@ -1,164 +0,0 @@
* Design of the Microsoft SQL Server, Sybase, and TDS Data Providers in Mono
<ul>
* After much discussion among the Mono ADO.NET developers,
we have come up with the design of implementing a Sybase, Microsoft
SQL Server, and TDS Generic ADO.NET providers. These providers have
been created and are actively developed by Tim Coleman.
* Since Sybase and Microsoft SQL Server databases both
use the TDS protocol for data access, and other implementations
of TDS (FreeTDS and jTDS) have included support for multiple
versions of the TDS, we have decided to do the same.
* The TdsClient ADO.NET provider will be Mono's first provider
written completely in C# without any dependencies except
the usual suspects: corlib.dll, System.dll, and System.Xml.dll.
</ul>
* New ADO.NET Providers
<p>There will be three ADO.NET providers that will use TDS.
<ol>
<li><p>Mono.Data.SybaseClient namepace and assembly will
hold the ADO.NET provider for Sybase SQL Server database.
This provider uses TDS version 5.0 which
can only be used with Sybase databases.
<li><p>System.Data.SqlClient namespace and System.Data assembly
will hold the ADO.NET provider
for Microsoft SQL Server 7.0/2000 databases. This provider is to be
compatible with SqlClient in Microsoft .NET and uses TDS version 7.0
which only supports Microsoft SQL Server 7.0/2000.
There is TDS version 8.0
which we will need to support as well, but it is used for
Microsoft SQL Server 2000 databases.
<li><p>Mono.Data.TdsClient namespace and assembly is a generic
provider for older TDS databases. This provider will default to
using TDS version 4.2 which can be used by older Sybase and
Microsoft SQL Server databases.
</ol>
* Building The New Providers
<p> All three providers will use common internal code
at Mono.Data.TdsClient.Internal. Any classes in
Mono.Data.TdsClient.Internal will have the internal
keyword and will be built with the assembly of that provider.
<ol>
<li><p>SqlClient will build its assembly System.Data using files
from System.Data, System.Data.SqlClient, System.Data.SqlTypes,
System.Data.Common, and Mono.Data.TdsClient.Internal.
<p>SqlClient
will only reference the usual
suspects: corlib.dll, System.dll, and System.Xml.dll. SqlClient will be
a wrapper around TdsClient.Internal, but provide specific functionality to
Microsoft SQL Server 7.0/2000 databases.
<p>SqlClient build example:
<pre>
mcs -target:library -out:System.Data.dll \
System.Data.SqlClient/*.cs \
..\Mono.Data.TdsClient\Mono.Data.TdsClient.Internal\*.cs \
[any other classes in System.Data assembly...] \
-r corlib.dll -r System.dll -r System.Xml.dll
</pre>
<li><p>SybaseClient will build its assembly Mono.Data.SybaseClient using
files from Mono.Data.SybaseClient and Mono.Data.TdsClient.Internal.
SybaseClient will reference
the usual suspects plus System.Data.dll SybaseClient will
be a wrapper around TdsClient.Internal, but provide specific
functionality to Sybase.
<p>SybaseClient build example:
<pre>
mcs -target:library -out:Mono.Data.SybaseClient.dll \
Mono.Data.SybaseClient\*.cs \
..\Mono.Data.TdsClient\Mono.Data.TdsClient.Internal\*.cs
-r corlib.dll -r System.dll -r System.Xml.dll -r System.Data.dll
</pre>
<li><p>TdsClient will build its assembly Mono.Data.TdsClient
using files from Mono.Data.TdsClient
and Mono.Data.TdsClient.Internal. TdsClient will reference the
usual suspects plus System.Data.dll TdsClient is a wrapper
provider around TdsClient.Internal used for generic
unit tests. TdsClient will a wrapper around TdsClient.Internal
as a generic TDS provider
and allow TDS configuration options not exposed in SqlClient
nor SybaseClient, such as, TdsVersion will be exposed in TdsClient
but not in SqlClient nor SybaseClient.
<p>TdsClient build example:
<pre>
mcs -target:library -out:Mono.Data.TdsClient.dll \
Mono.Data.TdsClient\*.cs \
Mono.Data.TdsClient.Internal\*.cs \
-r corlib.dll -r System.dll -r System.Xml.dll -r System.Data.dll
</pre>
</ol>
* Classes in Mono.Data.TdsClient.Internal will:
<ul>
<li>use the internal keyword to prevent exposing these classes
to the System.Data.dll assembly.
<li> implement the ADO.NET interfaces just like any other ADO.NET provider, such as,
IDbConnection, IDbCommand, IDataReader, IDataRecord, IDataAdapter, etc...
<li> be sealed just like other providers
<li> provide features to be directly used by the SqlClient and SybaseClient
providers, such
as, setting the default TDS version: SqlClient to 7.0 and SybaseClient
to 5.0 and TdsClient to 4.2.
<li> be written completely in C# or IL assembly language (if need be).
<li> implement the TDS protocol version 4.2, 5.0, 7.0, and 8.0. This
is where most of the
work will take place.
<li> be an internal ADO.NET provider to the public ADO.NET providers:
System.Data.SqlClient, Mono.Data.SybaseClient, and Mono.Data.TdsClient.
</ul>
* Implementation Details of the TDS Protocol
<ul>
* will be implemented in pure C# from scratch
* will reside in Mono.Data.TdsClient.Internal
* will use FreeTDS and jTDS as rerferences.
</ul>
* More Information
<ul>
* <a href="http://www.freetds.org/">FreeTDS</a> is C API that implements
the TDS protocol. Has libraries for tds, ctlib, and dblib. It builds
and runs on Windows, Linux, and other platforms. FreeTDS provides
data access to Microsoft SQL Server and Sybase databases.
* <a href="http://jtds.sf.net/">jTDS</a> is a 100% Java JDBC provider
for Microsoft SQL Server and Sybase databases.
* <a href="http://www.freetds.org/tds.html">TDS Protocol</a>
</ul>
* Contribute
<p>Anybody willing to help? If so,
contact any of the people working on the ADO.NET support
in Mono: Rodrigo Moya, Tim Coleman, Daniel Morgan, Brian Ritchie,
Vladimir Vukicevic, Ville Palo, Franklin Wise, and others.
-159
View File
@@ -1,159 +0,0 @@
* TDS Generic Provider
<ul>
<li>ADO.NET Provider for older Sybase and Microsoft SQL Server databases</li>
<li>Exists in namespace Mono.Data.TdsClient and assembly Mono.Data.TdsClient</li>
<li>Created by Tim Coleman</li>
<li>Used the <a href="http://www.freetds.org/">FreeTDS</a> and
<a href="http://jtds.sourceforge.net/">jTDS</a> projects as resources.</li>
<li>Implemented in 100% C#</li>
<li>Is similar to the Mono.Data.SybaseClient and System.Data.SqlClient providers.</li>
<li>Requires the assembly Mono.Data.Tds.dll which implements the TDS protocol in 100% C#.</li>
<li>Uses TDS Protocol Version 4.2 by default</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
<ul>
<li>Only builds on Windows currently due to mcs does not support modules and mcs
has problems with code that is internal.</li>
<li>Able to connect to Microsoft SQL Server and Sybase databases</li>
<li>SQL commands can be executed
via ExecuteNonQuery() of a TdsCommand.</li>
<li>SQL aggregates can be executed and a single row and single column
result can be retrieved via ExecuteScalar() of a TdsCommand</li>
<li>SQL queries can be executed via ExecuteReader() and results
can be retrieved via TdsDataReader.</li>
<li>a DataTable with schema info about a result can be gotten via GetSchemaTable()
in a TdsDataReader</li>
<li>Data can be filled in a DataTable in a DataSet via a TdsDataAdapter</li>
</ul>
** Action plan
<ul>
<li>Connection timeouts is being developed now.</li>
<li>TODO</li>
</ul>
** Testing
<ul>
<li>Have a working mono and mcs installed</li>
<li>Have access to a Sybase or Microsoft SQL Server database
or either download it:
<ul>
<li><a href="http://www.microsoft.com/sql/default.asp">Microsoft SQL Server</a></li>
<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;
using System.Data;
using Mono.Data.TdsClient;
public class Test
{
public static void Main(string[] args)
{
string connectionString =
"Server=localhost;" +
"Database=pubs;" +
"User ID=myuserid;" +
"Password=mypassword;";
IDbConnection dbcon;
dbcon = new TdsConnection(connectionString);
dbcon.Open();
IDbCommand dbcmd = dbcon.CreateCommand();
string sql =
"SELECT fname, lname " +
"FROM employee";
dbcmd.CommandText = sql;
IDataReader reader = dbcmd.ExecuteReader();
while(reader.Read()) {
string FirstName = reader["fname"];
string LastName = reader["lname"];
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 Mono.Data.TdsClient.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 Mono.Data.TdsClient.dll
</pre>
</li>
</ul>
</li>
<li>Running the Example:
<pre>
mono TestExample.exe
</pre>
</li>
</ul>
+2
View File
@@ -0,0 +1,2 @@
* The MonoNet Team
+4 -105
View File
@@ -9,114 +9,13 @@
** Class Library Tests
All classes in Mono libraries should have comprehensive unit test
suites to go with them. Unit testing is a software engineering
methodology that makes it easier to build correct code. Every
suites to go with them. Unit testing is a software engineering
methodology that makes it easier to build correct code. Every
method in every class should have a set of tests to verify
that they work correctly. Mono also needs a testing framework
that they work correctly. Mono also needs a testing framework
to make it easy to write and run lots of tests.
** Getting started
If you are new to writing NUnit tests, there is a template you may use
to help get started. The file is:
<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
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.
mcs/class/corlib/Test/System.Collections/CollectionBaseTest.cs
is a small one that might help.
The directory that will contain your new file depends on the
assembly/namespace of the class for which you are creating the
tests. Under mcs/class there is a directory for each
assembly. In each assembly there is a Test directory,
e.g. mcs/class/corlib/Test. In the Test directory there are
sub-directories for each namespace in the assembly,
e.g. mcs/class/corlib/Test/Sytem. Put your new test file in
the appropriate sub-directory under Test for the class you are
testing.
Once all of that is done, you can do a 'make test' from the top mcs
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
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
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.
Ok:
<pre>
AssertEquals("array match", compare[0], i1[0]);
AssertEquals("array match", compare[1], i1[1]);
AssertEquals("array match", compare[2], i1[2]);
AssertEquals("array match", compare[3], i1[3]);
</pre>
Excellent:
<pre>
AssertEquals("#A01", compare[0], i1[0]);
AssertEquals("#A02", compare[1], i1[1]);
AssertEquals("#A03", compare[2], i1[2]);
AssertEquals("#A04", compare[3], i1[3]);
</pre>
Once you used such a number in an Assert(), don't change it later on -
people might use it it identify the test in bug reports or in mailing
lists.
** Use AssertEquals() to compare things, not Assert().
Do not compare two values with Assert() - if the test fails,
people have no idea what went wrong while AssertEquals()
reports the failed value.
Ok:
<pre>
Assert ("A01", myTicks[0] == t1.Ticks);
</pre>
Excellent:
<pre>
AssertEquals ("A01", myTicks[0], t1.Ticks);
</pre>
** 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
important if you're writing a totally new testcase - without this
check you can never be sure that your testcase contains no bugs ....
Don't worry if you're writing your test on Linux, other people can
test it for you on Windows.
Sometimes you may discover that a test doesn't show the expected
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">mailing list</a> - we'll forward this to the
Microsoft people from time to time to help them fix their documentation
and runtime.
** Unit tests.
Try <a href="http://nunit.sourceforge.net">NUnit</a>
Why do unit testing? It becomes simple to run automated tests
for the whole library. Unit tests are a safety net - you can
+17 -48
View File
@@ -1,71 +1,40 @@
0,Home,index.html,index.src
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
1,Classes,class-library.html,class-library.src
1,Gtk#,gtk-sharp.html,gtk-sharp.src
1,ASP.NET,asp-net.html,asp-net.src
1,ADO.NET,ado-net.html,ado-net.src
1,Gtk#,http://gtk-sharp.sourceforge.net
1,Class Status,class-status.html,class-status.src,cm/cormissing.css,cm/cormissing.js
2,corlib,class-status-corlib.html,class-status-corlib.src,cm/cormissing.css,cm/cormissing.js
2,System,class-status-System.html,class-status-System.src,cm/cormissing.css,cm/cormissing.js
2,System.Xml,class-status-System.Xml.html,class-status-System.Xml.src,cm/cormissing.css,cm/cormissing.js
2,System.Data,class-status-System.Data.html,class-status-System.Data.src,cm/cormissing.css,cm/cormissing.js
2,System.Web,class-status-System.Web.html,class-status-System.Web.src,cm/cormissing.css,cm/cormissing.js
1,C# Compiler,c-sharp.html,c-sharp.src
1,VB Compiler,mbas.html,mbas.src
1,Debugging,jit-debug.html,jit-debug.src
2,Example 1,jit-debug-sample.html,jit-debug-sample.src
2,Example 2,jit-debug-sample2.html,jit-debug-sample2.src
1,Status,status.html,status.src
0,Download,download.html,download.src
1,CVS access,ccvs.html,ccvs.src
1,AnonCVS access,anoncvs.html,anoncvs.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
1,HOWTO,mono-contribution-howto.html,mono-contribution-howto.src
0,Plans,plans.html,plans.src
1,ADO.NET,ado-net.html,ado-net.src
1,ASP.NET,asp-net.html,asp-net.src
1,Java,java.html,java.src
1,Windows.Forms,winforms.html,winforms.src
0,Resources,resources.html,resources.src
1,Beginning,mono-beginning.html,mono-beginning.src
1,Mailing Lists,mailing-lists.html,mailing-lists.src
1,Ideas,ideas.html,ideas.src
1,Passport,passport.html,passport.src
1,Books,books.html,books.src
1,Papers,papers.html,papers.src
1,Languages,languages.html,languages.src
1,Debugging,jit-debug.html,jit-debug.src
0,Plans,plans.html,plans.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
2,MySQL,mysql.html,mysql.src
2,ODBC,odbc.html,odbc.src
2,OLE DB,oledb.html,oledb.src
2,Oracle,oracle.html,oracle.src
2,PostgreSQL,postgresql.html,postgresql.src
2,SQL Lite,sqlite.html,sqlite.src
2,Sybase,sybase.html,sybase.src
2,TDS Generic,tdsclient.html,tdsclient.src
1,Crypto,crypto.html,crypto.src
1,Java,java.html,java.src
1,Windows.Forms,winforms.html,winforms.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
1,Xml,class-status-System.Xml.html,class-status-System.Xml.src,cm/cormissing.css,cm/cormissing.js
1,Data,class-status-System.Data.html,class-status-System.Data.src,cm/cormissing.css,cm/cormissing.js
1,Drawing,class-status-System.Drawing.html,class-status-System.Drawing.src,cm/cormissing.css,cm/cormissing.js
1,Web,class-status-System.Web.html,class-status-System.Web.src,cm/cormissing.css,cm/cormissing.js
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,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 -1
View File
@@ -212,7 +212,7 @@ 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)
{
-5
View File
@@ -15,11 +15,6 @@ while (<>){
print "<p>\n";
} elsif (/^\t\t\* (.*)$/) {
print "<li>$1\n";
} elsif (/^\@item (.*)$/){
$name = $link = $1;
$link =~ s/ //g;
print "<a name=\"$link\">\n";
print "<h2>$name</h2>\n";
} elsif (/^Q: (.*)$/){
print "<p><a name=\"q$q\"></a><b>Question $q:</b> $1\n";
$q++;
Binary file not shown.

Before

Width:  |  Height:  |  Size: 32 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 6.1 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 14 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 429 B

+55 -115
View File
@@ -1,121 +1,66 @@
ifeq ($(findstring CYGWIN,$(shell uname)),)
CSC=mcs
RUN_MONO=mono
else
CSC=csc /nologo
endif
CSCRIPT = $(SYSTEMROOT)/system32/cscript.exe
CORCOMPARE=../../../mcs/tools/corcompare
OBJECTS= \
deploy/ado-net.html \
deploy/bugs.html \
deploy/provider-factory.html \
deploy/mysql.html \
deploy/odbc.html \
deploy/oledb.html \
deploy/oracle.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/contact.html \
deploy/c-sharp.html \
deploy/ccvs.html \
deploy/documentation.html \
deploy/download.html \
deploy/crypto.html \
deploy/embedded-api.html \
deploy/faq.html \
deploy/firebird.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/other.html \
deploy/papers.html \
deploy/passport.html \
deploy/plans.html \
deploy/porting.html \
deploy/ppc.html \
deploy/rationale.html \
deploy/resources.html \
deploy/roadmap.html \
deploy/runtime.html \
deploy/screenshots.html \
deploy/status.html \
deploy/team.html \
deploy/testing.html \
deploy/tools.html \
deploy/winforms.html \
deploy/class-library.html \
deploy/classlib-doc.html
OBJECTS= \
deploy/ado-net.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.Xml.html \
deploy/class-status-System.Data.html \
deploy/class-status-System.Web.html \
deploy/class-library.html \
deploy/classlib-doc.html \
deploy/contact.html \
deploy/c-sharp.html \
deploy/ccvs.html \
deploy/documentation.html \
deploy/download.html \
deploy/faq.html \
deploy/gcc-frontend.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/monodoc-xml.html \
deploy/papers.html \
deploy/passport.html \
deploy/plans.html \
deploy/porting.html \
deploy/rationale.html \
deploy/resources.html \
deploy/roadmap.html \
deploy/runtime.html \
deploy/status.html \
deploy/testing.html \
deploy/tools.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
# deploy/class-status-System.html \
# deploy/class-status-System.Configuration.Install.html \
# deploy/class-status-System.Runtime.Remoting.html \
NON_HTML_SOURCES= \
NON_HTML_SOURCES= \
../mono-build.sh \
../mono-build-w32.sh
all: $(OBJECT) deploy/index.rss ../team
all: $(OBJECTS)
perl process.pl commands template.html.in deploy
-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
mono-beginning.html.stamp: mono-beginning.xml
db2html mono-beginning.xml
touch mono-beginning.html.stamp
mono-beginning.pdf: mono-beginning.xml
db2pdf mono-beginning.xml
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: 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
push:
cp -f $(NON_HTML_SOURCES) deploy
#echo scp -P 2200 -r deploy/* www@www.go-mono.com:/web/cvsmodules/mono
#(cd deploy; rsync --verbose --recursive --checksum --update --rsh='ssh' . www@www.go-mono.com:/web/cvsmodules/mono )
(cd deploy; rsync --verbose --recursive --checksum --update --rsh='ssh' . [email protected]:/web/cvsmodules/mono )
echo scp -P 2200 -r deploy/* www@www.ximian.com:/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
@@ -124,37 +69,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)/cormissing.xsl
$(RUN_MONO) ./transform.exe $< $(CORCOMPARE)/cormissing.xsl > $@
src/%.html.in: src/%.xml $(CORCOMPARE)/transform.js $(CORCOMPARE)/cormissing.xsl
$(CSCRIPT) /nologo $(CORCOMPARE)/transform.js $< $(CORCOMPARE)/cormissing.xsl > $@
.PRECIOUS: src/%.xml
src/%.xml: ../../../mcs/class/lib/%.dll $(CORCOMPARE)/CorCompare.exe
$(RUN_MONO) $(CORCOMPARE)/CorCompare.exe -x $@ $<
$(CORCOMPARE)/CorCompare.exe -x $@ $<
src/corlib.xml: ../../../mcs/class/lib/corlib_cmp.dll $(CORCOMPARE)/CorCompare.exe
$(RUN_MONO) $(CORCOMPARE)/CorCompare.exe -f corlib -ms mscorlib -x $@ $<
$(CORCOMPARE)/CorCompare.exe -f corlib -ms mscorlib -x $@ $<
src/System.Security.xml: ../../../mcs/class/lib/System.Security_cmp.dll $(CORCOMPARE)/CorCompare.exe
$(RUN_MONO) $(CORCOMPARE)/CorCompare.exe -f System.Security -ms System.Security -x $@ $<
../class-status: ../class-status.in
cp -f $< $@
make-rss:
$(CSC) make-rss.cs -o
-112
View File
@@ -1,112 +0,0 @@
//
// Generates the Mono RSS feed
//
// Miguel de Icaza
//
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;
}
if (s == null || !s.StartsWith ("@item ")){
Console.WriteLine ("Could not find beginning of text to RSS");
return;
}
Item i = null;
string description = "";
do {
if (s.StartsWith ("@item ")){
if (item_count++ > 25)
break;
if (i != null){
i.Description = description;
description = "";
}
string title = s.Substring (6);
string link = "http://www.go-mono.com/index.html#";
foreach (char ch in title){
if (ch != ' ')
link += ch;
}
i = c.NewItem ();
i.Title = title;
i.Link = link;
} else {
description += "\n" + (s == "\n" ? "<p>" : s);
}
line++;
} while ((s = input.ReadLine ()) != null);
if (i != null){
i.Description = description;
}
}
static void MakeRSS (string input, string output)
{
rss = new RSS.RSS ();
c = rss.NewChannel ("Mono Project News", "http://www.go-mono.com");
c.Title = "Mono Project News";
c.Link = "http://www.go-mono.com";
c.Description =
"News from the Mono project: a portable implementation of the .NET Framework";
c.WebMaster = "[email protected]";
c.ManagingEditor = "[email protected]";
string t = File.GetLastWriteTime (input).ToString ("r");
c.PubDate = t;
c.LastBuildDate = t;
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;
}
}
}
rss.XmlDocument.Save (output);
}
static int Main (string [] args)
{
switch (args.Length){
case 0:
MakeRSS ("index", "index.rss");
break;
case 2:
MakeRSS (args [0], args [1]);
break;
default:
Console.WriteLine ("Usage is: mono-rss [input output.rss]");
return 1;
}
return 0;
}
}
+1 -1
View File
@@ -26,7 +26,7 @@ while (<COMMANDS>) {
$menu .= "<tr><td valign=\"top\" class=\"navi" . $command[0];
$menu .= "\"><a class=\"navi" . $command[0];
$menu .= "\"";
$menu .= " HREF=\"$command[2]\">$command[1]</A></td></tr>\n\n";
$menu .= "HREF=\"$command[2]\">$command[1]</A></td></tr>\n\n";
}
}
close COMMANDS;
-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;
}
}
-262
View File
@@ -1,262 +0,0 @@
//
// RSS.cs: Some utility classes to generate RSS feeds
//
// (C) 2002 Miguel de Icaza ([email protected])
//
//
using System;
using System.Xml;
using System.IO;
namespace RSS {
public class Item {
XmlDocument doc;
XmlNode item;
XmlText title, link, description;
public Item (XmlDocument doc, XmlNode item)
{
this.doc = doc;
this.item = item;
}
XmlText MakeTextElement (string name)
{
XmlNode node = doc.CreateElement (name);
XmlText text = doc.CreateTextNode ("");
item.AppendChild (node);
node.AppendChild (text);
return text;
}
public string Title {
get {
if (title == null)
return null;
return title.Value;
}
set {
if (title == null)
title = MakeTextElement ("title");
title.Value = value;
}
}
public string Link {
get {
if (link == null)
return null;
return link.Value;
}
set {
if (link == null)
link = MakeTextElement ("link");
link.Value = value;
}
}
public string Description {
get {
if (description == null)
return null;
return description.Value;
}
set {
if (description == null)
description = MakeTextElement ("description");
description.Value = value;
}
}
}
public class Channel {
XmlDocument doc;
XmlNode channel;
XmlText title, link, description, language, pubDate, lastBuildDate;
XmlText managingEditor, webMaster;
XmlText MakeTextElement (string name)
{
XmlNode node = doc.CreateElement (name);
XmlText text = doc.CreateTextNode ("");
channel.AppendChild (node);
node.AppendChild (text);
return text;
}
public Channel (XmlDocument doc, XmlNode node)
{
this.channel = node;
this.doc = doc;
title = MakeTextElement ("title");
link = MakeTextElement ("link");
description = MakeTextElement ("description");
}
public Item NewItem ()
{
XmlNode node = doc.CreateElement ("item");
Item item;
channel.AppendChild (node);
item = new Item (doc, node);
return item;
}
public string Title {
get {
return title.Value;
}
set {
title.Value = value;
}
}
public string Link {
get {
return link.Value;
}
set {
link.Value = value;
}
}
public string Description {
get {
return description.Value;
}
set {
description.Value = value;
}
}
#region Optional Values
public string ManagingEditor {
get {
if (managingEditor == null)
return null;
return managingEditor.Value;
}
set {
if (managingEditor == null)
managingEditor = MakeTextElement ("managingEditor");
managingEditor.Value = value;
}
}
public string WebMaster {
get {
if (webMaster == null)
return null;
return webMaster.Value;
}
set {
if (webMaster == null)
webMaster = MakeTextElement ("webMaster");
webMaster.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 string LastBuildDate {
get {
if (lastBuildDate == null)
return null;
return lastBuildDate.Value;
}
set {
if (lastBuildDate == null)
lastBuildDate = MakeTextElement ("lastBuildDate");
lastBuildDate.Value = value;
}
}
public string Language {
get {
if (language == null)
return null;
return language.Value;
}
set {
if (language == null)
language = MakeTextElement ("language");
language.Value = value;
}
}
#endregion
}
class RSS {
XmlDocument doc;
XmlNode rss;
const string rss_base =
"<?xml version=\"1.0\"?> <rss version=\"0.92\"></rss>";
public RSS ()
{
doc = new XmlDocument ();
doc.LoadXml (rss_base);
rss = doc.DocumentElement;
}
public Channel NewChannel (string title, string url)
{
XmlNode node = doc.CreateElement ("channel");
Channel c;
rss.AppendChild (node);
c = new Channel (doc, node);
return c;
}
public XmlDocument XmlDocument {
get {
return doc;
}
}
}
}
-1471
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.3 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 6.4 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 4.4 KiB

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