mirror of
https://github.com/BepInEx/mono.git
synced 2026-11-17 19:10:23 -10:00
Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
0d77b961f5 |
No files matched your search
@@ -1,283 +1,3 @@
|
||||
|
||||
Fri Jan 23 16:07:05 EST 2004 Paolo Molaro <[email protected]>
|
||||
|
||||
* configure.in, acconfig.h: check for truncl. Disable
|
||||
version script on MacOSX (see bug #51590 if a check becomes
|
||||
necessary).
|
||||
|
||||
Fri Jan 23 21:26:01 CET 2004 Paolo Molaro <[email protected]>
|
||||
|
||||
* configure.in, acconfig.h: added check for socklen_t.
|
||||
|
||||
2004-01-22 Zoltan Varga <[email protected]>
|
||||
|
||||
* Makefile.am: Do not install mono.pc on platforms without a JIT.
|
||||
|
||||
2004-01-21 Zoltan Varga <[email protected]>
|
||||
|
||||
* Makefile.am (remove-binaries): Get rid of non-portable >& construct.
|
||||
|
||||
2003-12-29 Miguel de Icaza <[email protected]>
|
||||
|
||||
* scripts/sn.in: Add sn script.
|
||||
|
||||
2004-01-15 Zoltan Varga <[email protected]>
|
||||
|
||||
* scripts/Makefile.am: Add al.exe.
|
||||
|
||||
* scripts/al.in: New file.
|
||||
|
||||
* runtime/Makefile.am: Add al.exe.
|
||||
|
||||
2004-01-10 Jackson Harper <[email protected]>
|
||||
|
||||
* data/machine.config: Add trace handler (Trace.axd) add trace
|
||||
configuration handlers.
|
||||
|
||||
2004-01-06 Martin Willemoes Hansen <[email protected]>
|
||||
|
||||
* doc/books: Added books on Web Services and ASP.NET
|
||||
|
||||
2004-01-04 Daniel Morgan <[email protected]>
|
||||
|
||||
* monowiz.win32.nsi: update the NSIS installer script for windows
|
||||
to support NSIS 2.0 rc1 and Mono 0.29
|
||||
|
||||
2003-12-22 Bernie Solomon <[email protected]>
|
||||
|
||||
* configure.in: missed in my last change
|
||||
|
||||
* samples/embed/testi.c: interpreter embedding example
|
||||
|
||||
* docs/embedded-api: add info on interpreter embedding
|
||||
|
||||
Mon Dec 22 18:27:14 CET 2003 Paolo Molaro <[email protected]>
|
||||
|
||||
* configure.in, acconfig.h: use mach semaphores on darwin.
|
||||
|
||||
2003-12-22 Bernie Solomon <[email protected]>
|
||||
|
||||
* Makefile.am: Create mint.pc
|
||||
mint.pc.in: Added for embedding the interpreter
|
||||
|
||||
2003-12-16 Martin Baulig <[email protected]>
|
||||
|
||||
* Makefile.am: In a Makefile.am, comments are started with `#' and
|
||||
not with `dnl' - I must have been an idiot ...
|
||||
|
||||
2003-12-10 Todd Berman <[email protected]>
|
||||
|
||||
* configure.in: adding libicu url to the ICU: no message.
|
||||
|
||||
2003-12-05 John Luke <[email protected]>
|
||||
|
||||
* data/config.in: new dll mapping entry for libgstreamer
|
||||
|
||||
2003-12-02 Atsushi Enomoto <[email protected]>
|
||||
|
||||
* README: tiny fix ;-)
|
||||
|
||||
2003-11-26 Zoltan Varga <[email protected]>
|
||||
|
||||
* configure.in: Add -fno-strict-aliasing to CFLAGS.
|
||||
|
||||
* configure.in: Applied patch from [email protected]. Avoid linking in
|
||||
librt if not neccesary.
|
||||
|
||||
2003-11-24 Zoltan Varga <[email protected]>
|
||||
|
||||
* configure.in: Fix signbit check. Fixes #51315.
|
||||
|
||||
2003-11-20 Jackson Harper <[email protected]>
|
||||
|
||||
* data/machine.config: Add OutputCacheModule
|
||||
|
||||
2003-11-19 Jackson Harper <[email protected]>
|
||||
|
||||
* doc/web/team.xml: New email address and job description
|
||||
* doc/web/team/jackson.png: Picture of me debugging...seems appropriate
|
||||
|
||||
2003-11-14 Jackson Harper <[email protected]>
|
||||
|
||||
* Makefile.am: delete mscorlib.dll
|
||||
|
||||
2003-11-12 Jackson Harper <[email protected]>
|
||||
|
||||
* Makefile.am: corlib is now named mscorlib.dll
|
||||
|
||||
2003-11-12 Zoltan Varga <[email protected]>
|
||||
|
||||
* configure.in acconfig.h: Add check for signbit, which is missing in
|
||||
FreeBSD 4.x.
|
||||
|
||||
2003-11-07 Zoltan Varga <[email protected]>
|
||||
|
||||
* configure.in: Remove debugging junk accidently checked in.
|
||||
|
||||
* configure.in: Add new --with-nptl option to enable NPTL only
|
||||
features since auto-detection is not reliable.
|
||||
|
||||
* autogen.sh: Fix previous patch and silence noisy GNU which.
|
||||
|
||||
2003-11-07 Bernie Solomon <[email protected]>
|
||||
|
||||
* autogen.sh: tweak glibtool check so it works
|
||||
if which doesn't set return code properly
|
||||
|
||||
2003-11-07 Zoltan Varga <[email protected]>
|
||||
|
||||
* autogen.sh: Silence noisy GNU which.
|
||||
|
||||
* autogen.sh: Applied patch from Peter Teichman ([email protected]).
|
||||
Use 'glibtool' instead of 'libtool' on OSX.
|
||||
|
||||
2003-11-06 Zoltan Varga <zovarga@ws-zovarga2>
|
||||
|
||||
* mono/benchmark/pinvoke.cs: New benchmark for testing the performance
|
||||
of the managed/unmanaged boundary.
|
||||
|
||||
2003-11-06 Zoltan Varga <[email protected]>
|
||||
|
||||
* configure.in acconfig.h: Add check for __thread keyword in gcc.
|
||||
|
||||
2003-10-29 Dick Porter <[email protected]>
|
||||
|
||||
* man/mono.1: Document MONO_EXTERNAL_ENCODINGS variable
|
||||
|
||||
2003-10-16 Miguel de Icaza <[email protected]>
|
||||
|
||||
* man/mono.1: Document new --trace options
|
||||
|
||||
2003-10-13 Bernie Solomon <[email protected]>
|
||||
|
||||
* configure.in: add hppa support (64bit only)
|
||||
make solaris build work with Forte compiler
|
||||
|
||||
2003-10-13 Zoltan Varga <[email protected]>
|
||||
|
||||
* configure.in: Added check for pthread_attr_setstacksize.
|
||||
|
||||
* mono/tests/ChangeLog: New file.
|
||||
|
||||
2003-10-13 Zoltan Varga <[email protected]>
|
||||
|
||||
* mono/tests/Makefile.am: Link the tests with the test driver program
|
||||
used for the mini tests.
|
||||
|
||||
2003-10-10 Zoltan Varga <[email protected]>
|
||||
|
||||
* mono/tests/libtest.c (mono_test_marshal_delegate): Added test for
|
||||
stdcall calling convention.
|
||||
|
||||
2003-10-09 Dick Porter <[email protected]>
|
||||
|
||||
* acconfig.h:
|
||||
* configure.in: Check for ICU availability
|
||||
|
||||
2003-10-09 Bernie Solomon <[email protected]>
|
||||
|
||||
* mono/tests/libtest.c: fix after merge of pinvoke2.cs
|
||||
|
||||
2003-10-07 Bernie Solomon <[email protected]>
|
||||
|
||||
* mono/tests/Makefile.am mono/tests/libtest.c
|
||||
mono/tests/pinvoke18.cs: new test for bool marshalling.
|
||||
|
||||
2003-10-07 Bernie Solomon <[email protected]>
|
||||
|
||||
* mono/scripts/Makefile.am mono/scripts/*.in: fix
|
||||
managed .exe paths so they are found under cygwin.
|
||||
|
||||
2003-10-07 Zoltan Varga <[email protected]>
|
||||
|
||||
* mono/tests/pinvoke2.cs mono/tests/libtest.c: Fix array of structs
|
||||
test.
|
||||
|
||||
2003-10-06 Bernie Solomon <[email protected]>
|
||||
|
||||
* mono/tests/pinvoke2.cs mono/tests/pinvoke11.cs
|
||||
mono/tests/libtest.c: Add more pass by value struct
|
||||
tests for platforms with more complex calling conventions
|
||||
(Sparc V9, HPPA 64 bit).
|
||||
|
||||
2003-10-06 Zoltan Varga <[email protected]>
|
||||
|
||||
* mono/tests/pinvoke2.cs mono/tests/libtest.c: Add array of structs
|
||||
marshalling test.
|
||||
|
||||
2003-10-04 Bernie Solomon <[email protected]>
|
||||
|
||||
* mono/tests/libtest.c: remove warnings except
|
||||
"no previous prototype"
|
||||
|
||||
2003-10-03 Bernie Solomon <[email protected]>
|
||||
|
||||
* mono/tests/libtest.c: (test_lpwstr_marshal) remove undefined
|
||||
behaviour of increment, (mono_test_marshal_char) = should be ==
|
||||
|
||||
2003-09-30 Zoltan Varga <[email protected]>
|
||||
|
||||
* mono/tests/remoting1.cs: Added test for interface casts on
|
||||
TransparentProxies.
|
||||
|
||||
2003-09-24 Bernie Solomon <[email protected]>
|
||||
|
||||
* mono/tests/pinvoke*.cs, delegate4.cs, marshal10.cs, marshal4.cs
|
||||
marshal5.cs: remove .so from DllImport of libtest to aid portability.
|
||||
|
||||
2003-09-08 Zoltan Varga <[email protected]>
|
||||
|
||||
* configure.in: Added check for valgrind headers.
|
||||
|
||||
2003-09-03 Zoltan Varga <[email protected]>
|
||||
|
||||
* Makefile.am: Use $(MAKE) in even more places. Patch by Bernie Solomon
|
||||
([email protected]).
|
||||
|
||||
2003-08-27 Zoltan Varga <[email protected]>
|
||||
|
||||
* Makefile.am: Use $(MAKE) instead of make. Patch by Bernie Solomon
|
||||
([email protected]).
|
||||
|
||||
2003-08-25 Zoltan Varga <[email protected]>
|
||||
|
||||
* mono.pc.in: Added gthread-2.0.
|
||||
|
||||
2003-08-22 Zoltan Varga <[email protected]>
|
||||
|
||||
* configure.in: Added gthread-2.0 to GLIB_CFLAGS and GLIB_LIBS, so we
|
||||
can call g_thread_init ().
|
||||
|
||||
2003-08-21 Zoltan Varga <[email protected]>
|
||||
|
||||
* mono/tests/threadpool.cs mono/tests/threadpool1.cs: Make increments
|
||||
of static variables atomic. Fixes bug #47683.
|
||||
|
||||
2003-08-21 Johannes Roith <[email protected]>
|
||||
|
||||
* mono/Makefile.am: small update. make sure, glib makes it in the build, add optional target for dependencies
|
||||
|
||||
2003-08-18 Johannes Roith <[email protected]>
|
||||
|
||||
* mono/Makefile.am: add windows build option
|
||||
* mono/monowiz.win32.nsi: add windows build script
|
||||
* mono/mono-win32-light.bmp: add bitmap
|
||||
|
||||
2003-08-16 Zoltan Varga <[email protected]>
|
||||
|
||||
* mono/tests/checked.cs: Added mul.ovf tests.
|
||||
|
||||
2003-08-15 Duncan Mak <[email protected]>
|
||||
|
||||
* doc/mysql: Change references to ByteFX.Data.MySQLClient to the
|
||||
correct ByteFX.Data.MySqlClient (note the change in
|
||||
capitalization). Thanks to Tom Wagner <[email protected]> for
|
||||
spotting the error.
|
||||
|
||||
2003-08-15 Zoltan Varga <[email protected]>
|
||||
|
||||
* mono/tests/bug-47295.cs: Regression test for bug #47295.
|
||||
|
||||
2003-08-11 Duncan Mak <[email protected]>
|
||||
|
||||
* runtime/Makefile.am (assemblies_DATA): Add Mono.Cairo.dll.
|
||||
|
||||
+12
-43
@@ -2,17 +2,13 @@ AUTOMAKE_OPTIONS = foreign
|
||||
|
||||
SUBDIRS = @libgc_dir@ mono doc docs runtime scripts man data samples
|
||||
|
||||
# EXTRA_SUBDIRS = libgc
|
||||
dnl EXTRA_SUBDIRS = libgc
|
||||
|
||||
EXTRA_DIST= mono.pc.in mono.spec.in mint.pc.in
|
||||
EXTRA_DIST= mono.pc.in mono.spec.in
|
||||
|
||||
pkgconfigdir = $(libdir)/pkgconfig
|
||||
if JIT_SUPPORTED
|
||||
pkgconfig_DATA= mono.pc mint.pc
|
||||
else
|
||||
pkgconfig_DATA= mint.pc
|
||||
endif
|
||||
DISTCLEANFILES= mono.pc mint.pc
|
||||
pkgconfig_DATA= mono.pc
|
||||
DISTCLEANFILES= mono.pc
|
||||
|
||||
#
|
||||
# The following target is used to compile and install
|
||||
@@ -23,45 +19,18 @@ DISTCLEANFILES= mono.pc mint.pc
|
||||
fullbuild: remove-binaries mcs-tree-safe-build xinstall-runtime mcs-rest install
|
||||
|
||||
mcs-tree-safe-build:
|
||||
(cd ../mcs/jay; $(MAKE))
|
||||
(cd ../mcs/mcs; $(MAKE) MCS=mcs BOOTSTRAP_MCS=mcs)
|
||||
(cd ../mcs/class/corlib; $(MAKE) MCS=mcs BOOTSTRAP_MCS=mcs)
|
||||
cp ../mcs/class/lib/mscorlib.dll runtime
|
||||
(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)
|
||||
(cd runtime; $(MAKE) install assemblies_DATA=mscorlib.dll monobins_DATA=mcs.exe)
|
||||
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))
|
||||
(cd ../mcs/class; make)
|
||||
|
||||
remove-binaries:
|
||||
rm ../mcs/class/lib/mscorlib.dll ../mcs/mcs/mcs.exe runtime/*dll runtime/*.exe > /dev/null 2>&1; echo
|
||||
|
||||
|
||||
win32getdeps:
|
||||
wget http://www.go-mono.com/archive/pkgconfig-0.11-20020310.zip
|
||||
wget http://www.go-mono.com/archive/glib-2.0.4-20020703.zip
|
||||
wget http://www.go-mono.com/archive/glib-dev-2.0.4-20020703.zip
|
||||
wget http://www.go-mono.com/archive/libiconv-1.7.zip
|
||||
wget http://www.go-mono.com/archive/libiconv-dev-1.7.zip
|
||||
wget http://www.go-mono.com/archive/libintl-0.10.40-20020101.zip
|
||||
wget http://www.jroith.de/nsis4cygwin.zip
|
||||
unzip -n -d / pkgconfig-0.11-20020310.zip
|
||||
unzip -n -d / glib-2.0.4-20020703.zip
|
||||
unzip -n -d / glib-dev-2.0.4-20020703.zip
|
||||
unzip -n -d / libiconv-1.7.zip
|
||||
unzip -n -d / libiconv-dev-1.7.zip
|
||||
unzip -n -d / libintl-0.10.40-20020101.zip
|
||||
unzip -n -d / nsis4cygwin.zip
|
||||
|
||||
win32setup:
|
||||
cp /usr/lib/libglib-2.0-0.dll @prefix@/lib
|
||||
cp /usr/lib/iconv.dll @prefix@/lib
|
||||
cp /usr/lib/libgmodule-2.0-0.dll @prefix@/lib
|
||||
cp /usr/lib/libgobject-2.0-0.dll @prefix@/lib
|
||||
cp /usr/lib/libgthread-2.0-0.dll @prefix@/lib
|
||||
cp /usr/lib/libintl-1.dll @prefix@/lib
|
||||
makensis /DMILESTONE=@VERSION@ /DSOURCE_INSTALL_DIR=`cygpath -a -w @prefix@`\\* monowiz.win32.nsi
|
||||
rm ../mcs/class/lib/corlib.dll ../mcs/mcs/mcs.exe runtime/*dll runtime/*.exe >& /dev/null; echo
|
||||
@@ -8,36 +8,6 @@ This is Mono.
|
||||
1. Compilation and Installation
|
||||
===============================
|
||||
|
||||
a. Build Requirements
|
||||
---------------------
|
||||
|
||||
To build Mono, you will need the following components:
|
||||
|
||||
* pkg-config
|
||||
|
||||
Available from: http://www.freedesktop.org/Software/pkgconfig
|
||||
|
||||
* glib 2.0
|
||||
|
||||
Available from: http://www.gtk.org/
|
||||
|
||||
Optional dependencies:
|
||||
|
||||
* ICU library
|
||||
|
||||
http://oss.software.ibm.com/icu/index.html
|
||||
|
||||
You will need this one to get complete support for the international
|
||||
features of the .NET Framework.
|
||||
|
||||
* Cairo and libgdiplus
|
||||
|
||||
If you want to get support for System.Drawing, you will need to get
|
||||
both Libgdiplus and Cairo.
|
||||
|
||||
b. Building the Software
|
||||
------------------------
|
||||
|
||||
If you obtained this package as an officially released tarball,
|
||||
this is very simple, use configure and make:
|
||||
|
||||
@@ -46,51 +16,11 @@ This is Mono.
|
||||
make install
|
||||
|
||||
If you obtained this as a snapshot, you will need an existing
|
||||
Mono installation. To upgrade your installation, unpack both
|
||||
mono and mcs:
|
||||
Mono installation. To upgrade your installation do:
|
||||
|
||||
tar xzf mcs-XXXX.tar.gz
|
||||
tar xzf mono-XXXX.tar.gz
|
||||
cd mono-XXXX
|
||||
./autogen.sh --prefix=/usr/local
|
||||
make fullbuild
|
||||
|
||||
c. Upgrade from CVS
|
||||
-------------------
|
||||
|
||||
If you are upgrading from CVS you will need an existing Mono installation.
|
||||
First verify that you have a working installation:
|
||||
|
||||
echo 'class X { static void Main () { System.Console.Write("OK");}'}' > x.cs
|
||||
|
||||
Compile:
|
||||
|
||||
mcs x.cs
|
||||
|
||||
And run:
|
||||
|
||||
mono x.exe
|
||||
|
||||
If you get the output `OK' and no errors, you are ready to start your CVS upgrade.
|
||||
|
||||
First, make sure that you have up-to-date mcs and mono sources:
|
||||
|
||||
cvs co mono mcs
|
||||
|
||||
Then, go into the mono directory, and configure:
|
||||
|
||||
cd mono
|
||||
./autogen --prefix=/usr/local
|
||||
|
||||
Then compile using the special target `fullbuild':
|
||||
|
||||
make fullbuild
|
||||
|
||||
This step will compile and install at the same time.
|
||||
|
||||
Failure to follow these steps will result in a broken installation.
|
||||
|
||||
|
||||
2. Using Mono
|
||||
=============
|
||||
|
||||
@@ -117,13 +47,7 @@ This is Mono.
|
||||
====================
|
||||
|
||||
doc/
|
||||
Contains the web site contents.
|
||||
|
||||
docs/
|
||||
Technical documents about the Mono runtime.
|
||||
|
||||
data/
|
||||
Configuration files installed as part of the Mono runtime.
|
||||
Contains documentation and the web site contents.
|
||||
|
||||
mono/
|
||||
The core of the Mono Runtime.
|
||||
@@ -154,17 +78,4 @@ This is Mono.
|
||||
arch/
|
||||
Architecture specific portions.
|
||||
|
||||
man/
|
||||
|
||||
Manual pages for the various Mono commands and programs.
|
||||
|
||||
scripts/
|
||||
|
||||
Scripts used to invoke Mono and the corresponding program.
|
||||
|
||||
runtime/
|
||||
|
||||
A directory holding a pre-compiled version of the Mono
|
||||
runtime.
|
||||
|
||||
|
||||
@@ -27,9 +27,3 @@
|
||||
#undef HAVE_GC_GCJ_MALLOC
|
||||
#undef WITH_BUNDLE
|
||||
#undef HAVE_GETHOSTBYNAME2_R
|
||||
#undef HAVE_ICU
|
||||
#undef HAVE_KW_THREAD
|
||||
#undef HAVE_SIGNBIT
|
||||
#undef USE_MACH_SEMA
|
||||
#undef HAVE_SOCKLEN_T
|
||||
#undef HAVE_TRUNCL
|
||||
+2
-9
@@ -30,15 +30,8 @@ fi
|
||||
DIE=1
|
||||
}
|
||||
|
||||
if [ -z "$LIBTOOL" ]; then
|
||||
LIBTOOL=`which glibtool 2>/dev/null`
|
||||
if [ ! -x "$LIBTOOL" ]; then
|
||||
LIBTOOL=`which libtool`
|
||||
fi
|
||||
fi
|
||||
|
||||
(grep "^AM_PROG_LIBTOOL" $srcdir/configure.in >/dev/null) && {
|
||||
($LIBTOOL --version) < /dev/null > /dev/null 2>&1 || {
|
||||
(libtool --version) < /dev/null > /dev/null 2>&1 || {
|
||||
echo
|
||||
echo "**Error**: You must have \`libtool' installed to compile Mono."
|
||||
echo "Get ftp://ftp.gnu.org/pub/gnu/libtool-1.2d.tar.gz"
|
||||
@@ -98,7 +91,7 @@ esac
|
||||
if grep "^AM_PROG_LIBTOOL" configure.in >/dev/null; then
|
||||
if test -z "$NO_LIBTOOLIZE" ; then
|
||||
echo "Running libtoolize..."
|
||||
${LIBTOOL}ize --force --copy
|
||||
libtoolize --force --copy
|
||||
fi
|
||||
fi
|
||||
|
||||
|
||||
-51
@@ -1,51 +0,0 @@
|
||||
/* config.h.in. Generated automatically from configure.in by autoheader 2.13. */
|
||||
|
||||
/* Define if you have the ANSI C header files. */
|
||||
#undef STDC_HEADERS
|
||||
|
||||
#undef HAVE_INET_PTON
|
||||
#undef HAVE_INET_ATON
|
||||
#undef HAVE_SOL_IP
|
||||
#undef HAVE_SOL_TCP
|
||||
#undef HAVE_IP_PKTINFO
|
||||
#undef HAVE_STRUCT_IP_MREQN
|
||||
#undef HAVE_PTHREAD
|
||||
#undef HAVE_PTHREAD_MUTEX_TIMEDLOCK
|
||||
#undef USE_MONO_MUTEX
|
||||
#undef HAVE_LARGE_FILE_SUPPORT
|
||||
#undef PLATFORM_WIN32
|
||||
#undef HAVE_NEW_ICONV
|
||||
#undef NAME_DEV_RANDOM
|
||||
#undef HAVE_CRYPT_RNG
|
||||
#undef HAVE_BOEHM_GC
|
||||
|
||||
/* The number of bytes in a void *. */
|
||||
#undef SIZEOF_VOID_P
|
||||
|
||||
/* Define if you have the inet_aton function. */
|
||||
#undef HAVE_INET_ATON
|
||||
|
||||
/* Define if you have the inet_pton function. */
|
||||
#undef HAVE_INET_PTON
|
||||
|
||||
/* Define if you have the <dlfcn.h> header file. */
|
||||
#undef HAVE_DLFCN_H
|
||||
|
||||
/* Define if you have the <netdb.h> header file. */
|
||||
#undef HAVE_NETDB_H
|
||||
|
||||
/* Define if you have the <sys/filio.h> header file. */
|
||||
#undef HAVE_SYS_FILIO_H
|
||||
|
||||
/* Define if you have the <sys/sockio.h> header file. */
|
||||
#undef HAVE_SYS_SOCKIO_H
|
||||
|
||||
/* Define if you have the <utime.h> header file. */
|
||||
#undef HAVE_UTIME_H
|
||||
|
||||
/* Name of package */
|
||||
#undef PACKAGE
|
||||
|
||||
/* Version number of package */
|
||||
#undef VERSION
|
||||
|
||||
+9
-157
@@ -1,7 +1,7 @@
|
||||
AC_INIT(README)
|
||||
AC_CANONICAL_SYSTEM
|
||||
AM_CONFIG_HEADER(config.h)
|
||||
AM_INIT_AUTOMAKE(mono,0.30)
|
||||
AM_INIT_AUTOMAKE(mono,0.26)
|
||||
AM_MAINTAINER_MODE
|
||||
|
||||
dnl
|
||||
@@ -27,9 +27,6 @@ libmono_ldflags=""
|
||||
AC_SUBST(libmono_cflags)
|
||||
AC_SUBST(libmono_ldflags)
|
||||
|
||||
dnl if linker handles the version script
|
||||
no_version_script=no
|
||||
|
||||
# Thread configuration inspired by sleepycat's db
|
||||
AC_MSG_CHECKING([host platform characteristics])
|
||||
libgc_threads=no
|
||||
@@ -77,9 +74,7 @@ case "$host" in
|
||||
;;
|
||||
*-*-hpux*)
|
||||
platform_win32=no
|
||||
CPPFLAGS="$CPPFLAGS -DGC_HPUX_THREADS -D_HPUX_SOURCE -D_XOPEN_SOURCE_EXTENDED -D_REENTRANT"
|
||||
CFLAGS="$CFLAGS +ESdbgasm"
|
||||
LDFLAGS="$LDFLAGS -z"
|
||||
CPPFLAGS="$CPPFLAGS -DGC_HPUX_THREADS -D_HPUX_SOURCE -D_XOPEN_SOURCE_EXTENDED -D_REENTRANT"
|
||||
libmono_cflags="-D_REENTRANT"
|
||||
libmono_ldflags="-lpthread"
|
||||
libgc_threads=pthreads
|
||||
@@ -100,8 +95,6 @@ case "$host" in
|
||||
libmono_ldflags="-pthread"
|
||||
AC_DEFINE(NEED_LINK_UNLINK)
|
||||
AC_DEFINE(PTHREAD_POINTER_ID)
|
||||
AC_DEFINE(USE_MACH_SEMA)
|
||||
no_version_script=yes
|
||||
libdl=
|
||||
libgc_threads=no
|
||||
gc_default=none
|
||||
@@ -114,7 +107,6 @@ case "$host" in
|
||||
esac
|
||||
AC_MSG_RESULT(ok)
|
||||
AM_CONDITIONAL(PLATFORM_WIN32, test x$platform_win32 = xyes)
|
||||
AM_CONDITIONAL(NO_VERSION_SCRIPT, test x$no_version_script = xyes)
|
||||
|
||||
AC_CHECK_TOOL(CC, gcc, gcc)
|
||||
AC_PROG_CC
|
||||
@@ -153,9 +145,6 @@ AM_PROG_LIBTOOL
|
||||
|
||||
AC_CHECK_HEADERS(sys/filio.h sys/sockio.h netdb.h utime.h semaphore.h sys/un.h)
|
||||
|
||||
# for mono/mini/tramp-x86.c
|
||||
AC_CHECK_HEADERS(valgrind/memcheck.h)
|
||||
|
||||
# for mono/metadata/debug-symfile.c
|
||||
AC_CHECK_HEADERS(elf.h)
|
||||
|
||||
@@ -168,18 +157,8 @@ AC_CHECK_SIZEOF(void *, 4)
|
||||
WARN=''
|
||||
if test x"$GCC" = xyes; then
|
||||
WARN='-Wall -Wunused -Wmissing-prototypes -Wmissing-declarations -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-cast-qual -Wcast-align -Wwrite-strings'
|
||||
# The runtime code does not respect ANSI C strict aliasing rules
|
||||
CFLAGS="$CFLAGS -fno-strict-aliasing"
|
||||
else
|
||||
# The Sun Forte compiler complains about inline functions that access static variables
|
||||
# so disable all inlining.
|
||||
case "$host" in
|
||||
*-*-solaris*)
|
||||
CFLAGS="$CFLAGS -Dinline="
|
||||
;;
|
||||
esac
|
||||
fi
|
||||
CFLAGS="$CFLAGS -g $WARN"
|
||||
CFLAGS="-g $WARN"
|
||||
|
||||
AC_PATH_PROG(PKG_CONFIG, pkg-config, no)
|
||||
if test "x$PKG_CONFIG" = "xno"; then
|
||||
@@ -188,8 +167,8 @@ fi
|
||||
|
||||
dnl for use on the build system
|
||||
dnl pkg-config is stupid
|
||||
BUILD_GLIB_CFLAGS=`$PKG_CONFIG --cflags glib-2.0 gthread-2.0`
|
||||
BUILD_GLIB_LIBS=`$PKG_CONFIG --libs glib-2.0 gthread-2.0`
|
||||
BUILD_GLIB_CFLAGS=`$PKG_CONFIG --cflags glib-2.0`
|
||||
BUILD_GLIB_LIBS=`$PKG_CONFIG --libs glib-2.0`
|
||||
AC_SUBST(BUILD_GLIB_CFLAGS)
|
||||
AC_SUBST(BUILD_GLIB_LIBS)
|
||||
|
||||
@@ -211,8 +190,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`
|
||||
|
||||
@@ -223,11 +202,6 @@ AC_SUBST(GMODULE_LIBS)
|
||||
|
||||
AC_ARG_WITH(gc, [ --with-gc=boehm,included,none],[gc=$with_gc],[gc=$gc_default])
|
||||
|
||||
# Enable support for NPTL only features like fast thread-local storage
|
||||
# We can't reliably detect nptl at compile & run time
|
||||
# so this option will stay until nptl becomes more widespread
|
||||
AC_ARG_WITH(nptl, [ --with-nptl Enable support for NPTL])
|
||||
|
||||
# assembly bundle support, see metadata/make-bundle.pl for more info
|
||||
AC_ARG_WITH(bundle, [ --with-bundle=bundle_template],[
|
||||
BUNDLE_FILE=$with_bundle
|
||||
@@ -545,7 +519,6 @@ if test x$platform_win32 = xno; then
|
||||
dnl *** Checks for libpthread ***
|
||||
dnl *****************************
|
||||
AC_CHECK_LIB(pthread, main, LIBS="$LIBS -lpthread")
|
||||
AC_CHECK_HEADERS(pthread.h)
|
||||
AC_CHECK_FUNCS(pthread_mutex_timedlock)
|
||||
AC_MSG_CHECKING(for PTHREAD_MUTEX_RECURSIVE)
|
||||
AC_TRY_COMPILE([ #include <pthread.h>], [
|
||||
@@ -558,59 +531,11 @@ if test x$platform_win32 = xno; then
|
||||
AC_MSG_WARN(Using mono_mutex_t for recursive mutexes)
|
||||
AC_DEFINE(USE_MONO_MUTEX)
|
||||
])
|
||||
AC_CHECK_FUNCS(pthread_attr_setstacksize)
|
||||
|
||||
dnl ***********************************
|
||||
dnl *** Checks for working __thread ***
|
||||
dnl ***********************************
|
||||
AC_MSG_CHECKING(for working __thread)
|
||||
AC_TRY_RUN([
|
||||
#include <pthread.h>
|
||||
|
||||
__thread int i;
|
||||
static int res1, res2;
|
||||
|
||||
void thread_main (void *arg)
|
||||
{
|
||||
i = arg;
|
||||
sleep (1);
|
||||
if (arg == 1)
|
||||
res1 = (i == arg);
|
||||
else
|
||||
res2 = (i == arg);
|
||||
}
|
||||
|
||||
int main () {
|
||||
pthread_t t1, t2;
|
||||
|
||||
i = 5;
|
||||
|
||||
pthread_create (&t1, NULL, thread_main, 1);
|
||||
pthread_create (&t2, NULL, thread_main, 2);
|
||||
|
||||
pthread_join (t1, NULL);
|
||||
pthread_join (t2, NULL);
|
||||
|
||||
return !(res1 + res2 == 2);
|
||||
}
|
||||
], [
|
||||
if test "x$with_nptl" = "x"; then
|
||||
AC_MSG_RESULT(disabled)
|
||||
else
|
||||
AC_MSG_RESULT(yes)
|
||||
AC_DEFINE(HAVE_KW_THREAD)
|
||||
fi
|
||||
], [
|
||||
AC_MSG_RESULT(no)
|
||||
])
|
||||
|
||||
dnl ********************************
|
||||
dnl *** Checks for semaphore lib ***
|
||||
dnl ********************************
|
||||
# 'Real Time' functions on Solaris
|
||||
# posix4 on Solaris 2.6
|
||||
# pthread (first!) on Linux
|
||||
AC_SEARCH_LIBS(sem_init, pthread rt posix4)
|
||||
AC_CHECK_LIB(rt, sem_init, LIBS="$LIBS -lrt")
|
||||
|
||||
dnl ********************************
|
||||
dnl *** Checks for timezone stuff **
|
||||
@@ -638,65 +563,16 @@ if test x$platform_win32 = xno; then
|
||||
fi
|
||||
fi
|
||||
|
||||
dnl *********************************
|
||||
dnl *** Checks for math functions ***
|
||||
dnl *********************************
|
||||
LIBS="$LIBS -lm";
|
||||
AC_CHECK_FUNCS(finite, , AC_MSG_CHECKING(for finite in math.h)
|
||||
AC_TRY_LINK([#include <math.h>],
|
||||
[ finite(0.0); ],
|
||||
AC_DEFINE(HAVE_FINITE) AC_MSG_RESULT(yes),
|
||||
AC_MSG_RESULT(no)))
|
||||
AC_CHECK_FUNCS(isfinite, , AC_MSG_CHECKING(for isfinite in math.h)
|
||||
AC_TRY_LINK([#include <math.h>],
|
||||
[ isfinite(0.0); ],
|
||||
AC_DEFINE(HAVE_ISFINITE) AC_MSG_RESULT(yes),
|
||||
AC_MSG_RESULT(no)))
|
||||
|
||||
dnl ****************************************************************
|
||||
dnl *** Checks for working poll() (macosx defines it but doesn't ***
|
||||
dnl *** have it in the library (duh)) ***
|
||||
dnl ****************************************************************
|
||||
AC_CHECK_FUNCS(poll)
|
||||
|
||||
dnl *************************
|
||||
dnl *** Check for signbit ***
|
||||
dnl *************************
|
||||
AC_MSG_CHECKING(for signbit)
|
||||
AC_TRY_LINK([#include <math.h>], [
|
||||
int s = signbit(1.0);
|
||||
], [
|
||||
AC_MSG_RESULT(yes)
|
||||
AC_DEFINE(HAVE_SIGNBIT)
|
||||
], [
|
||||
AC_MSG_RESULT(no)
|
||||
])
|
||||
else
|
||||
AC_CHECK_LIB(ws2_32, main, LIBS="$LIBS -lws2_32", AC_ERROR(bad mingw install?))
|
||||
AC_CHECK_LIB(psapi, main, LIBS="$LIBS -lpsapi", AC_ERROR(bad mingw install?))
|
||||
fi
|
||||
|
||||
dnl socklen_t check
|
||||
AC_MSG_CHECKING(for socklen_t)
|
||||
AC_TRY_COMPILE([
|
||||
#include <sys/types.h>
|
||||
#include <sys/socket.h>
|
||||
],[
|
||||
socklen_t foo;
|
||||
],[
|
||||
ac_cv_c_socklen_t=yes
|
||||
AC_DEFINE(HAVE_SOCKLEN_T)
|
||||
AC_MSG_RESULT(yes)
|
||||
],[
|
||||
AC_MSG_RESULT(no)
|
||||
])
|
||||
|
||||
AC_CHECK_FUNCS(truncl, , AC_MSG_CHECKING(for truncl in math.h)
|
||||
AC_TRY_LINK([#include <math.h>],
|
||||
[ truncl(0.0); ],
|
||||
AC_DEFINE(HAVE_TRUNCL) AC_MSG_RESULT(yes),
|
||||
AC_MSG_RESULT(no)))
|
||||
|
||||
dnl ****************************
|
||||
dnl *** Look for /dev/random ***
|
||||
dnl ****************************
|
||||
@@ -770,22 +646,6 @@ if test "x$try_shared_handles" != "xyes"; then
|
||||
AC_SUBST(DISABLE_SHARED_HANDLES)
|
||||
fi
|
||||
|
||||
ICU_CFLAGS=""
|
||||
ICU_LIBS=""
|
||||
enable_icu=no
|
||||
AC_PATH_PROG(ICU_CONFIG, icu-config, no)
|
||||
if test "x$ICU_CONFIG" = "xno" -o ! -x "$ICU_CONFIG"; then
|
||||
AC_MSG_WARN([Only invariant locale available; install ICU for I18N support])
|
||||
enable_icu="no, if you want full i18n support download it from: http://oss.software.ibm.com/icu/index.html"
|
||||
else
|
||||
enable_icu="yes. Version: `$ICU_CONFIG --version`"
|
||||
AC_DEFINE(HAVE_ICU)
|
||||
ICU_CFLAGS=`$ICU_CONFIG --cppflags`
|
||||
ICU_LIBS=`$ICU_CONFIG --ldflags`
|
||||
fi
|
||||
AC_SUBST(ICU_CFLAGS)
|
||||
AC_SUBST(ICU_LIBS)
|
||||
|
||||
TARGET="unknown"
|
||||
ACCESS_UNALIGNED="yes"
|
||||
|
||||
@@ -824,11 +684,6 @@ case "$host" in
|
||||
# m68k-*-linux*)
|
||||
# TARGET=M68K
|
||||
# ;;
|
||||
hppa2.0w-hp-hpux11.00 | hppa64-hp-hpux11.00)
|
||||
TARGET=HPPA;
|
||||
arch_target=hppa;
|
||||
ACCESS_UNALIGNED="no"
|
||||
;;
|
||||
macppc-*-openbsd* | powerpc-*-linux* | powerpc-*-openbsd* | \
|
||||
powerpc-*-sysv* | powerpc-*-darwin*)
|
||||
TARGET=POWERPC;
|
||||
@@ -885,7 +740,6 @@ AM_CONDITIONAL(M68K, test x$TARGET = xM68K)
|
||||
AM_CONDITIONAL(POWERPC, test x$TARGET = xPOWERPC)
|
||||
AM_CONDITIONAL(ARM, test x$TARGET = xARM)
|
||||
AM_CONDITIONAL(S390, test x$TARGET = xS390)
|
||||
AM_CONDITIONAL(HPPA, test x$TARGET = xHPPA)
|
||||
|
||||
AM_CONDITIONAL(JIT_SUPPORTED, test x$JIT_SUPPORTED = xyes)
|
||||
|
||||
@@ -898,7 +752,6 @@ AC_SUBST(LDFLAGS)
|
||||
|
||||
AC_OUTPUT([
|
||||
Makefile
|
||||
mint.pc
|
||||
mono.pc
|
||||
mono/Makefile
|
||||
mono/utils/Makefile
|
||||
@@ -910,7 +763,6 @@ mono/os/Makefile
|
||||
mono/os/win32/Makefile
|
||||
mono/os/unix/Makefile
|
||||
mono/arch/x86/Makefile
|
||||
mono/arch/hppa/Makefile
|
||||
mono/arch/ppc/Makefile
|
||||
mono/arch/sparc/Makefile
|
||||
mono/arch/s390/Makefile
|
||||
@@ -940,5 +792,5 @@ mono.spec
|
||||
echo "
|
||||
|
||||
GC: $gc
|
||||
ICU: $enable_icu
|
||||
|
||||
"
|
||||
@@ -2,4 +2,3 @@ Makefile.in
|
||||
Makefile
|
||||
config
|
||||
.cvsignore
|
||||
browscap.ini
|
||||
File diff suppressed because it is too large.
Load diff
+2
-11
@@ -1,15 +1,6 @@
|
||||
monodir = $(sysconfdir)/mono
|
||||
|
||||
EXTRA_DIST = config.in \
|
||||
machine.config \
|
||||
DefaultWsdlHelpGenerator.aspx \
|
||||
browscap.ini.gz
|
||||
EXTRA_DIST = config.in machine.config
|
||||
|
||||
mono_DATA = config \
|
||||
machine.config \
|
||||
DefaultWsdlHelpGenerator.aspx \
|
||||
browscap.ini
|
||||
|
||||
browscap.ini: browscap.ini.gz
|
||||
gunzip -c $^ > $@
|
||||
mono_DATA = config machine.config
|
||||
|
||||
Binary file not shown.
@@ -6,7 +6,6 @@
|
||||
<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" />
|
||||
@@ -16,6 +15,4 @@
|
||||
<dllmap dll="libglade-2.0-0.dll" target="libglade-2.0.so" />
|
||||
<dllmap dll="oci" target="clntsh" />
|
||||
<dllmap dll="gtkhtml-3.0" target="libgtkhtml-3.0.so.2" />
|
||||
<dllmap dll="db2cli" target="libdb2_36.so"/>
|
||||
<dllmap dll="gstreamer" target="libgstreamer-0.6.so" />
|
||||
</configuration>
|
||||
+7
-84
@@ -3,9 +3,9 @@
|
||||
<configuration>
|
||||
|
||||
<configSections>
|
||||
<section name="appSettings" type="System.Configuration.NameValueFileSectionHandler, System" />
|
||||
<section name="appSettings" type="System.Configuration.NameValueFileSectionHandler, System" />
|
||||
|
||||
<section name="system.diagnostics" type="System.Diagnostics.DiagnosticsConfigurationHandler, System" />
|
||||
<section name="system.runtime.remoting" type="System.Configuration.IgnoreSectionHandler, System" allowLocation="false"/>
|
||||
<sectionGroup name="system.web">
|
||||
<section name="httpHandlers"
|
||||
type="System.Web.Configuration.HttpHandlersSectionHandler, System.Web" />
|
||||
@@ -21,20 +21,8 @@
|
||||
type="System.Web.Configuration.GlobalizationConfigurationHandler, System.Web" />
|
||||
<section name="sessionState"
|
||||
type="System.Web.SessionState.SessionStateSectionHandler, System.Web" />
|
||||
<section name="trace"
|
||||
type="System.Web.Configuration.TraceConfigurationHandler, System.Web" />
|
||||
<section name="webServices"
|
||||
type="System.Web.Services.Configuration.WebServicesConfigurationSectionHandler, System.Web.Services" />
|
||||
<section name="webControls"
|
||||
type="System.Web.Configuration.WebControlsSectionHandler, System.Web" />
|
||||
<section name="compilation"
|
||||
type="System.Web.Configuration.CompilationConfigurationHandler, System.Web" />
|
||||
<section name="httpRuntime"
|
||||
type="System.Web.Configuration.HttpRuntimeConfigurationHandler, System.Web" />
|
||||
<section name="customErrors"
|
||||
type="System.Web.Configuration.CustomErrorsConfigHandler, System.Web" />
|
||||
<section name="pages"
|
||||
type="System.Web.Configuration.PagesConfigurationHandler, System.Web" />
|
||||
</sectionGroup>
|
||||
<sectionGroup name="system.net">
|
||||
<section name="settings"
|
||||
@@ -48,7 +36,7 @@
|
||||
<section name="webRequestModules"
|
||||
type="System.Net.Configuration.WebRequestModuleHandler, System" />
|
||||
</sectionGroup>
|
||||
<section name="system.drawing" type="System.Configuration.NameValueSectionHandler" />
|
||||
<section name="system.drawing" type="System.Configuration.NameValueSectionHandler" />
|
||||
</configSections>
|
||||
<system.net>
|
||||
<connectionManagement>
|
||||
@@ -56,8 +44,6 @@
|
||||
</connectionManagement>
|
||||
<authenticationModules>
|
||||
<add type="System.Net.BasicClient" />
|
||||
<add type="System.Net.DigestClient" />
|
||||
<add type="System.Net.NtlmClient" />
|
||||
</authenticationModules>
|
||||
<defaultProxy>
|
||||
<proxy />
|
||||
@@ -75,18 +61,14 @@
|
||||
</system.net>
|
||||
<system.web>
|
||||
<httpHandlers>
|
||||
<add verb="*" path="Trace.axd" type="System.Web.Handlers.TraceHandler, System.Web" />
|
||||
<add verb="*" path="*.aspx" type="System.Web.UI.PageHandlerFactory, System.Web" />
|
||||
<add verb="*" path="*.asmx" validate="false"
|
||||
type="System.Web.Services.Protocols.WebServiceHandlerFactory, System.Web.Services" />
|
||||
<add verb="*" path="*.ashx" type="System.Web.UI.SimpleHandlerFactory, System.Web" />
|
||||
<add verb="GET" path="WebResource.axd" type="System.Web.Handlers.AssemblyResourceLoader, System.Web" />
|
||||
<add verb="*" path="*.asax" type="System.Web.HttpForbiddenHandler, System.Web" />
|
||||
<add verb="*" path="*.ascx" type="System.Web.HttpForbiddenHandler, System.Web" />
|
||||
<add verb="*" path="*.config" type="System.Web.HttpForbiddenHandler, System.Web" />
|
||||
<add verb="*" path="*.cs" type="System.Web.HttpForbiddenHandler, System.Web" />
|
||||
<add verb="*" path="*.rem" type="System.Runtime.Remoting.Channels.Http.HttpRemotingHandlerFactory, System.Runtime.Remoting" validate="false" />
|
||||
<add verb="*" path="*.soap" type="System.Runtime.Remoting.Channels.Http.HttpRemotingHandlerFactory, System.Runtime.Remoting" validate="false" />
|
||||
<add verb="GET,HEAD" path="*" type="System.Web.StaticFileHandler, System.Web" />
|
||||
<add verb="*" path="*" type="System.Web.HttpMethodNotAllowedHandler, System.Web" />
|
||||
</httpHandlers>
|
||||
@@ -94,7 +76,6 @@
|
||||
<add name="FormsAuthentication" type="System.Web.Security.FormsAuthenticationModule, System.Web" />
|
||||
<add name="UrlAuthorization" type="System.Web.Security.UrlAuthorizationModule, System.Web" />
|
||||
<add name="Session" type="System.Web.SessionState.SessionStateModule, System.Web" />
|
||||
<add name="OutputCache" type="System.Web.Caching.OutputCacheModule, System.Web" />
|
||||
</httpModules>
|
||||
<authentication mode="Forms">
|
||||
<forms name=".MONOAUTH" loginUrl="login.aspx" protection="All" timeout="30" path="/">
|
||||
@@ -104,10 +85,10 @@
|
||||
</forms>
|
||||
</authentication>
|
||||
<machineKey validationKey="AutoGenerate" decryptionKey="AutoGenerate" validation="SHA1" />
|
||||
<globalization requestEncoding="utf-8"
|
||||
responseEncoding="utf-8"
|
||||
fileEncoding="utf-8"/>
|
||||
<!--
|
||||
<!-- Sample globalization settings
|
||||
<globalization requestEncoding="iso-8859-1"
|
||||
responseEncoding="iso-8859-1"
|
||||
fileEncoding="iso-8859-1"
|
||||
culture="en-US"
|
||||
uiculture="en-US" />
|
||||
-->
|
||||
@@ -121,66 +102,8 @@
|
||||
</protocols>
|
||||
<wsdlHelpGenerator href="DefaultWsdlHelpGenerator.aspx" />
|
||||
</webServices>
|
||||
<webControls clientScriptsLocation="/web_scripts" />
|
||||
<compilation debug="false" defaultLanguage="c#">
|
||||
<compilers>
|
||||
<compiler language="cs;c#;csharp" extension=".cs" warningLevel="1" compilerOptions=""
|
||||
type="Microsoft.CSharp.CSharpCodeProvider, System" />
|
||||
<compiler language="vb;vbs;visualbasic;vbscript" extension=".vb"
|
||||
warningLevel="1" compilerOptions=""
|
||||
type="Microsoft.VisualBasic.VBCodeProvider, System" />
|
||||
</compilers>
|
||||
<assemblies>
|
||||
<!--<add assembly="mscorlib" /> -->
|
||||
<add assembly="System" />
|
||||
<add assembly="System.Xml" />
|
||||
<add assembly="System.Data" />
|
||||
<add assembly="System.Web" />
|
||||
<add assembly="System.Web.Services" />
|
||||
<add assembly="System.Drawing" />
|
||||
<add assembly="*" /> <!-- Add assemblies in bin directory -->
|
||||
</assemblies>
|
||||
</compilation>
|
||||
<httpRuntime executionTimeout="90"
|
||||
maxRequestLength="4096"
|
||||
useFullyQualifiedRedirectUrl="false"
|
||||
minFreeThreads="8"
|
||||
minLocalRequestFreeThreads="4"
|
||||
appRequestQueueLimit="100" />
|
||||
<pages buffer="true"
|
||||
enableSessionState="true"
|
||||
autoEventWireup="true"
|
||||
validateRequest="true" />
|
||||
</system.web>
|
||||
|
||||
<system.runtime.remoting>
|
||||
<application>
|
||||
<channels>
|
||||
<channel ref="http client" displayName="http client (delay loaded)" delayLoadAsClientChannel="true" />
|
||||
<channel ref="tcp client" displayName="tcp client (delay loaded)" delayLoadAsClientChannel="true" />
|
||||
</channels>
|
||||
</application>
|
||||
<channels>
|
||||
<channel id="http" type="System.Runtime.Remoting.Channels.Http.HttpChannel, System.Runtime.Remoting" />
|
||||
<channel id="http client" type="System.Runtime.Remoting.Channels.Http.HttpClientChannel, System.Runtime.Remoting" />
|
||||
<channel id="http server" type="System.Runtime.Remoting.Channels.Http.HttpServerChannel, System.Runtime.Remoting" />
|
||||
<channel id="tcp" type="System.Runtime.Remoting.Channels.Tcp.TcpChannel, System.Runtime.Remoting" />
|
||||
<channel id="tcp client" type="System.Runtime.Remoting.Channels.Tcp.TcpClientChannel, System.Runtime.Remoting" />
|
||||
<channel id="tcp server" type="System.Runtime.Remoting.Channels.Tcp.TcpServerChannel, System.Runtime.Remoting" />
|
||||
</channels>
|
||||
<channelSinkProviders>
|
||||
<clientProviders>
|
||||
<formatter id="soap" type="System.Runtime.Remoting.Channels.SoapClientFormatterSinkProvider, System.Runtime.Remoting" />
|
||||
<formatter id="binary" type="System.Runtime.Remoting.Channels.BinaryClientFormatterSinkProvider, System.Runtime.Remoting" />
|
||||
</clientProviders>
|
||||
<serverProviders>
|
||||
<formatter id="soap" type="System.Runtime.Remoting.Channels.SoapServerFormatterSinkProvider, System.Runtime.Remoting" />
|
||||
<formatter id="binary" type="System.Runtime.Remoting.Channels.BinaryServerFormatterSinkProvider, System.Runtime.Remoting" />
|
||||
<provider id="wsdl" type="System.Runtime.Remoting.MetadataServices.SdlChannelSinkProvider, System.Runtime.Remoting" />
|
||||
</serverProviders>
|
||||
</channelSinkProviders>
|
||||
</system.runtime.remoting>
|
||||
|
||||
<appSettings>
|
||||
<!--<add key="yourkey" value="your value" /> -->
|
||||
<!--<remove key="a key defined higher in the hierarchy" /> -->
|
||||
|
||||
@@ -1,16 +0,0 @@
|
||||
2004-01-22 Atsushi Enomoto <[email protected]>
|
||||
|
||||
* xml-classes : status update, additional infos.
|
||||
|
||||
2004-01-16 Atsushi Enomoto <[email protected]>
|
||||
|
||||
* web/commands : Added xml-classes (forgot to commit).
|
||||
* mono-build-w32.sh : Added icu support as well as glib.
|
||||
* ChangeLog : tiny fix
|
||||
|
||||
2004-01-11 Atsushi Enomoto <[email protected]>
|
||||
|
||||
* xml-classes : added v2 info. schema status updates.
|
||||
|
||||
Added ChangeLog. (There is no reason not to keep ChangeLog for
|
||||
documents, at least for not a little changes ;-)
|
||||
+3
-3
@@ -8,7 +8,7 @@ WEB_FILES= \
|
||||
tds-providers status testing thanks tools \
|
||||
porting anoncvs monodoc-xml winforms
|
||||
|
||||
OTHERS= pending resources-pending todo mono-build.sh mono-build-w32.sh print-stack
|
||||
OTHERS= pending resources-pending todo mono-build.sh mono-build-w32.sh
|
||||
|
||||
EXTRA_DIST = $(WEB_FILES) README $(OTHERS)
|
||||
|
||||
@@ -17,8 +17,8 @@ all-docs: $(WEB_FILES)
|
||||
runtime documentation download faq contributing \
|
||||
resources status > all-docs
|
||||
|
||||
class-status: class-status.in Makefile.am
|
||||
cat class-status.in > class-status
|
||||
class-status: class-status.in pending-classes Makefile.am
|
||||
cat class-status.in pending-classes > class-status
|
||||
|
||||
pending-classes:
|
||||
|
||||
|
||||
+103
-48
@@ -1,22 +1,82 @@
|
||||
* ADO.NET
|
||||
|
||||
** Data Access in Mono
|
||||
<p>Mono's ADO.NET Developers:
|
||||
|
||||
<ul>
|
||||
<li>Today, our goal is to be compatible with .NET 1.0 and .NET 1.1. We also would like
|
||||
to extend data access beyond what is included with .NET 1.0 and .NET 1.1,
|
||||
such as, including access to more databases, such as, PostgreSQL and MySQL,
|
||||
but also provide classes that help in creating data source-agnostic code, such as, Mono.Data.ProviderFactory.</li>
|
||||
<li>In the future, we would like to be compatible with .NET 1.2. This
|
||||
would include features like:
|
||||
<ul>
|
||||
<li><a href="http://longhorn.msdn.microsoft.com/lhsdk/ndp/daconworkingwithobjectspacesarchitecture.aspx">ObjectSpaces</a></li>
|
||||
<li>provide support for hosting Mono languages (C-Sharp, MonoBASIC, etc...)
|
||||
within a DBMS engine, such as, MySQL or PostgreSQL.</li>
|
||||
<li>implement .net 1.2 classes, such as, those found in System.Data.ProviderBase</li>
|
||||
<li>other stuff which can be brought up on the mono-list</li>
|
||||
</ul></li>
|
||||
</ul>
|
||||
<table border=1>
|
||||
|
||||
<tr>
|
||||
<td><b>Developer</b></td>
|
||||
<td><b>Email</b></td>
|
||||
<td><b>Contribution</b></td>
|
||||
</tr>
|
||||
|
||||
<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
|
||||
|
||||
@@ -28,14 +88,14 @@
|
||||
and easy to create
|
||||
one <a href="http://bugzilla.ximian.com/createaccount.cgi">here</a>.</li>
|
||||
|
||||
<li>Any requests for new features or missing functionality
|
||||
can entered as a bug in Bugzilla too</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>Mono has many ADO.NET Data Providers to get you connected:
|
||||
<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>
|
||||
@@ -47,7 +107,7 @@
|
||||
<li><a href="http://www.go-mono.com/sqlclient.html">Microsoft SQL Server</a></li>
|
||||
<li><a href="http://www.go-mono.com/sqlite.html">SQL Lite</a></li>
|
||||
<li><a href="http://www.go-mono.com/sybase.html">Sybase</a></li>
|
||||
<li><a href="http://www.go-mono.com/tdsclient.html">Older Microsoft SQL Server and Sybase databases</a></li>
|
||||
<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,
|
||||
@@ -87,38 +147,39 @@
|
||||
<p>Some tools that can be used for ADO.NET and other technologies (ASP.NET, XML, etc).
|
||||
|
||||
<ul>
|
||||
<li><p><b>SQL# command line query tool</b> is a command-line tool to
|
||||
enter and execute SQL statements or
|
||||
execute a batch of SQL commands from a file.
|
||||
<p>It can
|
||||
<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.
|
||||
<p>The SQL# CLI is distributed with the
|
||||
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.
|
||||
<p>The source to SQL# CLI can be found in the mcs source at
|
||||
The source to SQL# CLI can be found in the mcs source at
|
||||
mcs/tools/SqlSharp/SqlSharpCli.cs
|
||||
</li>
|
||||
|
||||
<li><p><b>SQL# For GTK#</b> - is a graphical SQL database query tool</b> allows a user
|
||||
to enter SQL commands in a top panel which is a text editor.
|
||||
<p>It has a toolbar and menu for various tasks, such as, executing
|
||||
<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).
|
||||
<p>Also, the bottom panel would allow logging of SQL command executed.
|
||||
Here is a screenshot of <a href="http://go-mono.com/images/sqlsharp.png">SQL# For GTK#</a> which
|
||||
provides a GUI interface using the <a href="http://gtk-sharp.sourceforge.net">Gtk#</a> toolkit.
|
||||
<p>SQL# For GTK# can be found in mono cvs as sqlsharpgtk.</li>
|
||||
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>Mono has an <b>XML Schema Definition tool</b> (xsd.exe).</b>
|
||||
|
||||
<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 works like the xsd.exe tool included with
|
||||
the .NET Framework. The Xsd.exe tool has the
|
||||
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.
|
||||
@@ -269,7 +330,7 @@
|
||||
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. Marcus would be the best
|
||||
how this can be done is appreciated. Adam Treat would be the best
|
||||
person to ask about QT#.
|
||||
|
||||
<p><b>Building System.Data</b>
|
||||
@@ -333,12 +394,6 @@
|
||||
<td>System.Data /</br> System.Data.SqlClient</td>
|
||||
<td>SqlTest.cs at</br> System.Data/Test</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>PostgreSQL</br> (Npgsql)</td>
|
||||
<td>Npgsql /</br> Npgsql</td>
|
||||
<td>*.cs at</br> Npgsql/Test</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>PostgreSQL</br> (Mono)</td>
|
||||
@@ -355,13 +410,13 @@
|
||||
<tr>
|
||||
<td>Oracle</br> (Mono)</td>
|
||||
<td>System.Data.OracleClient /</br> System.Data.OracleClient</td>
|
||||
<td>TestOracleClient.cs at</br> System.Data.OracleClient/Test</td>
|
||||
<td>TestOracleClient.cs at</br> System.Data.OracleClient</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>ODBC</br> (Mono)</td>
|
||||
<td>System.Data.Odbc /</br> System.Data</td>
|
||||
<td>OdbcTest.cs (to connect to MS SQL Server)at</br> System.Data/Test</td>
|
||||
<td>System.Data.OracleClient /</br> System.Data.OracleClient</td>
|
||||
<td>TestOracleClient.cs at</br> System.Data.OracleClient</td>
|
||||
</tr>
|
||||
|
||||
</table>
|
||||
|
||||
+1
-4
@@ -2,7 +2,7 @@
|
||||
|
||||
Anonymous access to the Mono is available currently from three
|
||||
servers (anoncvs-spain-1.go-mono.com,
|
||||
anoncvs-spain-2.go-mono.com and us-anoncvs.go-mono.com).
|
||||
anoncvs-spain-2.go-mono.com and anoncvs-us-1.go-mono.com).
|
||||
|
||||
You can also use `anoncvs.go-mono.com', and that will pick a
|
||||
server automatically for you.
|
||||
@@ -43,9 +43,6 @@
|
||||
Special thanks to Jesus Climent, Rodrigo Moya, Juantomás
|
||||
García and Ismael Olea for making this happen.
|
||||
|
||||
Thanks to Matt Liotta of MontaraSoftware for hosting our
|
||||
US-based AnonCVS server.
|
||||
|
||||
<a name="#mirror">
|
||||
** Becoming an AnonCVS mirror
|
||||
|
||||
|
||||
+11
-17
@@ -13,15 +13,12 @@
|
||||
ASP.NET works either embedded into
|
||||
our XSP server test server or the mod_mono Apache module.
|
||||
|
||||
We are now working on bug fixing and adding missing features
|
||||
We are now working bug fixing and adding missing features
|
||||
after making the whole pipeline compatible with MS.
|
||||
|
||||
Tim started work on the Web Services. After that, Lluis is in
|
||||
charge and has been working hard on them as part of our
|
||||
<a href="http://www.ximian.com/about_us/press_center/press_releases/index.html?pr=sourcegear">SourceGear</a> contract.
|
||||
|
||||
Web services are now supported and there are some samples in the
|
||||
XSP set of tests.
|
||||
Tim started work on the Web Services. 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
|
||||
|
||||
@@ -63,23 +60,20 @@
|
||||
<a name="mod_mono">
|
||||
* mod_mono
|
||||
|
||||
This Apache module is available from our <a
|
||||
href="download.html">download page</a>. The <a href="anoncvs.html">
|
||||
cvs</a> module name is mod_mono. It works with both 1.3 and 2.0
|
||||
versions of the <a href="http://httpd.apache.org">apache server</a>.
|
||||
|
||||
It allows apache to serve ASP.NET pages.
|
||||
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).
|
||||
They have been coded mostly in the dark, and without being
|
||||
implement the controls (UI.HtmlControls and UI.WebControls),
|
||||
but they have been coded mostly in the dark, and without being
|
||||
able to test them in real life: Gaurav and Leen worked very
|
||||
hard on this namespace. After that, we keep fixing bugs on
|
||||
them.
|
||||
hard on this namespace.
|
||||
|
||||
We can now render all HtmlControls and all WebControls.
|
||||
|
||||
|
||||
@@ -1,38 +0,0 @@
|
||||
|
||||
You can read the aggregates news from the Mono developers in
|
||||
<a href="http://www.go-mono.com/monologue">Monologue</a>. You
|
||||
can also download our aggregator from the <a
|
||||
href="anoncvs.html">AnonCVS</a> server.
|
||||
|
||||
Various Mono contributors maintain blogs, some are listed here:
|
||||
|
||||
<a href="http://codeblogs.ximian.com/blogs/benm/index.rdf"><img align="center" src="images/xml.gif"></a>
|
||||
<a href="http://codeblogs.ximian.com/blogs/benm/">Ben Maurer</a>
|
||||
<br>
|
||||
<a href="http://ada.fciencias.unam.mx/~olopez/jscript/cesar.rss2"><img align="center" src="images/xml.gif"></a>
|
||||
<a href="http://ada.fciencias.unam.mx/~olopez/jscript/">Cesar Nataren</a>
|
||||
<br>
|
||||
<a href="http://www.jacksonh.net/jackson/blog/jackson.rss2"><img align="center" src="images/xml.gif"></a>
|
||||
<a href="http://www.jacksonh.net/jackson/blog/">Jackson Harper</a>
|
||||
<br>
|
||||
<a href="http://primates.ximian.com/~lluis/blog/index.rdf"><img align="center" src="images/xml.gif"></a>
|
||||
<a href="http://primates.ximian.com/~lluis/blog/">Lluis Sánchez</a>
|
||||
<br>
|
||||
<a href="http://primates.ximian.com/~martin/blog/rss.xml"><img align="center" src="images/xml.gif"></a>
|
||||
<a href="http://primates.ximian.com/~martin/blog/">Martin Baulig</a>
|
||||
<br>
|
||||
<a href="http://primates.ximian.com/~miguel/miguel.rss2"><img align="center" src="images/xml.gif"></a>
|
||||
<a href="http://primates.ximian.com/~miguel/activity-log.php">Miguel de Icaza</a>
|
||||
<br>
|
||||
<a href="http://primates.ximian.com/~mkestner/blog/index.rdf"><img align="center" src="images/xml.gif"></a>
|
||||
<a href="http://primates.ximian.com/~mkestner/blog/">Mike Kestner</a>
|
||||
<br>
|
||||
<a href="http://pages.infinit.net/ctech/poupou.rss"><img align="center" src="images/xml.gif"></a>
|
||||
<a href="http://pages.infinit.net/ctech/poupou.html">Sebastien Pouliot</a>
|
||||
<br>
|
||||
<a href="http://primates.ximian.com/~gonzalo/mono/blog/index.xml"><img align="center" src="images/xml.gif"></a>
|
||||
<a href="http://primates.ximian.com/~gonzalo/mono/blog/">Gonzalo Paniagua</a>
|
||||
<br>
|
||||
<a href="http://codeblogs.ximian.com/blogs/ndrochak/index.rdf"><img align="center" src="images/xml.gif"></a>
|
||||
<a href="http://codeblogs.ximian.com/blogs/ndrochak/">Nick Drochak</a>
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
* Mono
|
||||
* 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#
|
||||
* C# Books
|
||||
|
||||
A Programmer's Introduction to C# - Second Edition: Eric Gunnerson
|
||||
|
||||
@@ -16,23 +16,8 @@
|
||||
|
||||
* Remoting
|
||||
|
||||
<a href="http://www.dotnetremoting.cc/book/AdvancedDotNetRemoting.asp">Advanced .NET Remoting: Ingo Rammer</a>
|
||||
|
||||
* Threading
|
||||
|
||||
.NET Multithreading: Alan L. Dennis (ISBN 1-930110-54-5)
|
||||
|
||||
* Web Services
|
||||
|
||||
Web Services: Architecture and Implementation with .NET: Keith Ballinger
|
||||
|
||||
* ASP.NET
|
||||
|
||||
Essential ASP.NET with Examples in C# by Fritz Onion
|
||||
|
||||
ASP.NET in a Nutshell by G. Andrew Duthie & Matthew MacDonald
|
||||
|
||||
Programming ASP.NET by Jessy Liberty & Dan Hurtwitz
|
||||
<a href="http://www.dotnetremoting.cc/book/AdvancedDotNetRemoting.asp">
|
||||
Advanced .NET Remoting: Ingo Rammer</a>
|
||||
|
||||
* Compiler Implementation
|
||||
|
||||
@@ -46,6 +31,10 @@
|
||||
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
|
||||
|
||||
@@ -9,9 +9,9 @@
|
||||
<ul>
|
||||
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FClass+Libraries&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&newqueryname=&form_name=query&order=bugs.priority%2C%20bugs.bug_id">[Query]</> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FClass%20Libraries">[Add]</a> Class Libraries
|
||||
|
||||
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FCompilers&component=IL+assembler&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FCompilers&component=IL%20assembler">[Add]</a> IL Assembler.
|
||||
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%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%2FCompilers&component=C%23&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FCompilers&component=C%23">[Add]</a> C# Compiler.
|
||||
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%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
|
||||
|
||||
@@ -19,16 +19,9 @@
|
||||
|
||||
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=gtk%23&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=gtk%23">[Add]</a> Gtk#
|
||||
|
||||
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FClass+Libraries&component=System.Web&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FClass%20Libraries&component=System.Web">[Add]</a> ASP.NET WebForms
|
||||
|
||||
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FClass+Libraries&component=System.Web.Services&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FClass%20Libraries&component=System.Web.Services">[Add]</a> ASP.NET Web Services
|
||||
|
||||
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FDebugger&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FDebugger">[Add]</a> Debugger.
|
||||
|
||||
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono+Develop&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono+Develop">[Add]</a> Mono Develop.
|
||||
|
||||
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono+Tasks&product=Mono%2FClass+Libraries&product=Mono%2FCompilers&product=Mono%2FDebugger&product=Mono%2FDoctools&product=Mono%2FRuntime&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> All core components.
|
||||
|
||||
* <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"/>
|
||||
|
||||
@@ -1,12 +1,7 @@
|
||||
* CVS Access
|
||||
|
||||
Here we describe how one obtains commit access to the Mono CVS
|
||||
repository and the responsibilities that come with that access
|
||||
privilege.
|
||||
|
||||
These only apply to the Mono CVS repository, and not to the <a
|
||||
href="http://forge.novell.com/modules/xfmod/community/?monocomm">Mono
|
||||
Community</a> repositories at Novell Forge.
|
||||
Here we describe how one obtains commit access to the CVS repository
|
||||
and the responsibilities that come with that access privilege.
|
||||
|
||||
** What is CVS?
|
||||
|
||||
@@ -28,13 +23,9 @@
|
||||
mailing lists and/or bugzilla for review.
|
||||
|
||||
If you are not a developer, but want to access the latest sources,
|
||||
please see the <a href="anoncvs.html">AnonCVS</a>
|
||||
instructions. If you are not a direct contributor to Mono,
|
||||
but want to host your .NET or Mono-based project, you can use
|
||||
<a href="forge.html">Novell Forge</a>.
|
||||
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
|
||||
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.
|
||||
@@ -262,77 +253,6 @@
|
||||
cvs commit file-1.cs file-2.cs
|
||||
</pre>
|
||||
|
||||
* Using SVN
|
||||
|
||||
This is a small tutorial for using SVN (subversion).
|
||||
For a more complete tutorial on subversion, look at
|
||||
<a href="http://svnbook.red-bean.com/">the svn book</a>
|
||||
or <a href="http://subversion.tigris.org">the svn homepage</a>
|
||||
|
||||
** Generating a key
|
||||
|
||||
Follow the cvs instructions above.
|
||||
|
||||
** Checking out the sources
|
||||
|
||||
To checkout the sources for the first time use the command:
|
||||
|
||||
Note: You should be running 0.35.1 (latest) of svn before attempting
|
||||
anything here.
|
||||
|
||||
<pre>
|
||||
svn co svn+ssh://mono-cvs.ximian.com/svn/monodevelop/trunk/MonoDevelop
|
||||
</pre>
|
||||
|
||||
If you have a different username on mono-cvs and the local computer
|
||||
you can do the following:
|
||||
|
||||
<pre>
|
||||
svn co svn+ssh://[email protected]/svn/monodevelop/trunk/MonoDevelop
|
||||
</pre>
|
||||
|
||||
before checking out.
|
||||
|
||||
** Updating your sources
|
||||
|
||||
You can update your repository to the latest copy of MonoDevelop by
|
||||
running the following command:
|
||||
|
||||
<pre>
|
||||
svn up
|
||||
</pre>
|
||||
|
||||
from inside your repository.
|
||||
|
||||
** Committing your work
|
||||
|
||||
Before you commit anything, you should first update to the latest
|
||||
sources by following the updating directions. After you are up to date
|
||||
you need to run a:
|
||||
|
||||
<pre>
|
||||
svn add filename
|
||||
</pre>
|
||||
|
||||
for every file that you have created. You can get a list of these files
|
||||
by running:
|
||||
|
||||
<pre>
|
||||
svn status
|
||||
</pre>
|
||||
|
||||
After all the files are added, run:
|
||||
|
||||
<pre>
|
||||
svn commit
|
||||
</pre>
|
||||
|
||||
to commit your changes.
|
||||
|
||||
** For more information
|
||||
|
||||
Look at the MonoDevelop website (coming soon)
|
||||
|
||||
* Keeping track of changes.
|
||||
|
||||
We provide two e-mail based mechanisms to keep track of
|
||||
|
||||
+11
-1
@@ -5,26 +5,36 @@
|
||||
Here is the status of the different assemblies:
|
||||
<ul>
|
||||
<li><a href="http://www.go-mono.com/class-status-corlib.html">corlib</a>: The core library.
|
||||
<li><a href="http://www.go-mono.com/class-status-System.html">System</a>: Extra modules
|
||||
<li><a href="http://www.go-mono.com/class-status-System.html">System</a>.
|
||||
<li><a href="http://www.go-mono.com/class-status-System.Xml.html">System.Xml</a>.
|
||||
|
||||
<li><a
|
||||
href="http://www.go-mono.com/class-status-System.Data.html">System.Data</a>:
|
||||
Database access functionality (also check the <a href="ado-net.html">Mono ADO.NET status</a> pages).
|
||||
|
||||
<li><a href="http://www.go-mono.com/class-status-System.Drawing.html">System.Drawing</a>.
|
||||
|
||||
<li><a
|
||||
href="http://www.go-mono.com/class-status-System.Web.html">System.Web</a>:
|
||||
ASP.NET classes, also check the <a href="asp-net.html">Mono ASP.NET status pages</a>
|
||||
|
||||
<li><a href="http://www.go-mono.com/class-status-System.Web.Services.html">System.Web.Services</a>.
|
||||
|
||||
<li><a
|
||||
href="http://www.go-mono.com/class-status-Microsoft.VisualBasic.html">Microsoft.VisualBasic</a>:
|
||||
Support runtime for Visual Basic applications
|
||||
|
||||
<li><a
|
||||
href="http://www.go-mono.com/class-status-System.Windows.Forms.html">Windows.Forms</a>:
|
||||
there is also a <a
|
||||
href="http://lists.ximian.com/mailman/listinfo/mono-winforms-list">mailing
|
||||
list available</a>
|
||||
|
||||
<li><a href="http://www.go-mono.com/class-status-System.EnterpriseServices.html">EnterpriseServices</a>.
|
||||
|
||||
<li><a
|
||||
href="http://www.go-mono.com/class-status-System.Runtime.Serialization.Formatters.Soap.html">System.Runtime.Serialization.Formatters.Soap</a>.
|
||||
|
||||
<li><a
|
||||
href="http://www.go-mono.com/class-status-System.Security.html">System.Security</a>:
|
||||
Xml Signature Security classes, also check the <a href="crypto.html">Cryptography status pages</a>
|
||||
|
||||
+14
-23
@@ -7,43 +7,34 @@
|
||||
the code, making the source quite difficult to read. Furthermore,
|
||||
multilingual documentation makes for significant additional text.
|
||||
|
||||
With these considerations in mind, Mono is using external XML files
|
||||
for class documentation, rather than documenting the source
|
||||
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.
|
||||
|
||||
Several tools exist for managing, verifying, generating,
|
||||
and updating class library documentation.
|
||||
|
||||
The documentation infrastructure is part of the `Monodoc'
|
||||
module. Monodoc includes a graphical GUI browser and tools to
|
||||
generate the initial stubbed XML document out of an assembly.
|
||||
Several tools will be created for managing, verifying, generating,
|
||||
and updating class library documentation, including:
|
||||
|
||||
Download `monodoc' to start producing documentation for your
|
||||
application.
|
||||
<ul>
|
||||
<li><a href="#monodoc">monodoc - A graphical documentation viewer.</a></li>
|
||||
<li>xmllint: a tool used to validate a proper XML document.
|
||||
</ul>
|
||||
|
||||
For instructions, read the monodoc/README file.
|
||||
You can download the tools to document Mono from the CVS
|
||||
repository from module `monodoc'.
|
||||
|
||||
** Documentation Tools
|
||||
|
||||
*** <a name="monodoc">MonoDoc</a>
|
||||
|
||||
The MonoDoc system offers both a GUI client as well as a <a
|
||||
href="http://www.go-mono.com:8080">Web-based interface</a> to
|
||||
the documentation.
|
||||
A graphical documentation viewer written in Gtk#. In the
|
||||
future we will have an ASP.NET front-end to present the
|
||||
documentation on the web as well.
|
||||
|
||||
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">
|
||||
** Status and Roadmap
|
||||
|
||||
** Get Involved
|
||||
|
||||
Help us develop Mono's documentation tools! Subscribe to
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/mono-docs-list">mono-docs-list</a>
|
||||
and wade right in.
|
||||
|
||||
Monodoc today also supports a GUI-based collaborative editing
|
||||
system. You can now edit the documentation from the browser
|
||||
and upload your contributions directly to the Mono site.
|
||||
-235
@@ -1,235 +0,0 @@
|
||||
* Compiling Mono
|
||||
|
||||
This document describes how to compile and install Mono from
|
||||
its source code. If you are only interested in running Mono,
|
||||
you might want to install Mono from packages, which have been
|
||||
tested.
|
||||
|
||||
The core of Mono is split in two components:
|
||||
|
||||
<ul>
|
||||
* C components (available in the mono package)
|
||||
|
||||
* C# components (available in the mcs package).
|
||||
</ul>
|
||||
|
||||
Mono is also available in various forms:
|
||||
|
||||
<dl>
|
||||
<dt>Officially <a href="download.html">released</a> packages.</dt>
|
||||
<dd>
|
||||
<p>This is the format of choice for people to use, since these
|
||||
have been tested and are known to build and work.
|
||||
</dd>
|
||||
<dt><a href="daily">Daily</a> packages.</dt>
|
||||
<dd>
|
||||
<p>This is a service offered for people who want to try out the
|
||||
daily changes. Baked daily.</dd>
|
||||
<dt>CVS source code.</dt>
|
||||
<dd>
|
||||
<p>These are available to Mono <a href="ccvs.html">developers</a> and
|
||||
also for enthusiasts through <a href="anoncvs.html">anonymous CVS</a>.
|
||||
</dd>
|
||||
<dt>CVS snapshots.</dt>
|
||||
<dd>
|
||||
<p>Available for curious developers which do not necessarily want to
|
||||
install the CVS source. Baked daily.
|
||||
</dd>
|
||||
</dl>
|
||||
|
||||
* Compiling the code
|
||||
|
||||
There are a number of ways of compiling Mono
|
||||
|
||||
<ul>
|
||||
<li>From the <a href="#scripts">scripts</A>
|
||||
|
||||
<LI><a href="#install">Manually</a> for the first time.
|
||||
|
||||
<li>Manually, <a href="#upgrade">while upgrading</a> to CVS
|
||||
</ul>
|
||||
|
||||
(which is an easy way to get the latest CVS information)
|
||||
|
||||
<a name="scripts">
|
||||
* Compiling with scripts
|
||||
|
||||
These scripts should be used for installing from packages, specially
|
||||
on Windows, where dependencies have not always been installed.
|
||||
|
||||
There are scripts to help build mono for both Unix and Windows. Get
|
||||
<a href="mono-build.sh">mono-build.sh</a> for Unix, or <a
|
||||
href="mono-build-w32.sh">mono-build-w32.sh</a> for Windows.
|
||||
These scripts automate the installation of GLIB and pkgconfig
|
||||
(building from source on Unix, and using binary packages
|
||||
provided by the GIMP for Windows project on Windows.) To use
|
||||
the script, follow these simple steps:
|
||||
|
||||
<ul>
|
||||
* Save the script for your platform somewhere (e.g. /usr/local/bin)
|
||||
* Make the script executable (i.e chmod 755 /usr/local/bin/mono-build.sh)
|
||||
* Create a directory to hold the mono source, and the compiled binaries (e.g. mkdir ~/mono)
|
||||
* Change to the new directory (i.e. cd ~/mono)
|
||||
* run the script (i.e. /usr/local/bin/mono-build.sh)
|
||||
</ul>
|
||||
|
||||
The script requires wget on either platform, and building the
|
||||
software requires make, gcc, automake, autoconf, and libtool.
|
||||
You should install these packages from your distribution or
|
||||
with the cygwin installer. You should also take care of setting
|
||||
the right environment variables as the PKG_CONFIG_FLAGS, etc.
|
||||
|
||||
The script will download required packages from
|
||||
www.go-mono.com and do a cvs checkout of mono in the current
|
||||
directory. <b>IMPORTANT!:</b> The cvs server chosen defaults to
|
||||
anonymous cvs;
|
||||
set your CVSROOT environment variable before running the script to
|
||||
select a particular cvs server.
|
||||
|
||||
<a name="install">
|
||||
|
||||
** Building the software manually
|
||||
|
||||
You will need to obtain the Mono dependencies first: <a
|
||||
href="http://www.gtk.org">glib 2.x</a> and
|
||||
<a href="http://www.freedesktop.org/software/pkgconfig">pkg-config</a>.
|
||||
|
||||
*** Building From Packages
|
||||
|
||||
This applies to both the officially released packages, as well as the
|
||||
daily tarball packages.
|
||||
|
||||
<ul>
|
||||
Unpack the Mono runtime distribution:
|
||||
<pre class="shell">
|
||||
tar xzvf mono-X.XX.tar.gz
|
||||
cd mono-X.XX</pre>
|
||||
<p>
|
||||
|
||||
Then configure, compile and install:
|
||||
|
||||
<pre class="shell">
|
||||
./configure --prefix=/usr/local
|
||||
make
|
||||
make install</pre>
|
||||
|
||||
This will give you a runtime, C# compiler and runtime
|
||||
libraries.
|
||||
|
||||
If you want to recompile the runtime and the compiler,
|
||||
follow these steps, first unpack the MCS package:
|
||||
|
||||
<pre class="shell">
|
||||
tar xzvf mcs-X.XX.tar.gz</pre>
|
||||
|
||||
Then use the following command to compile and install:
|
||||
|
||||
<pre class="shell">
|
||||
./configure --profile=atomic
|
||||
make</pre>
|
||||
|
||||
You can change /usr/local to something else if you want.
|
||||
</ul>
|
||||
|
||||
*** Building from CVS
|
||||
|
||||
To upgrade your Mono installation from CVS, it is very
|
||||
important that you update your Mono and MCS modules from CVS
|
||||
at the same time. Failure to do so might result in a
|
||||
problematic installation as the runtime and the class
|
||||
libraries will be out of sync.
|
||||
|
||||
Run the following commands to update your CVS tree (more
|
||||
details in <a href="ccvs.html">Cvs and Mono</a> and the <A
|
||||
href="anoncvs.html">AnonCVS and Mono</a> pages).
|
||||
|
||||
<pre>
|
||||
(cd mono; cvs update -dP .)
|
||||
(cd mcs; cvs update -dP .)
|
||||
</pre>
|
||||
|
||||
Then you can run:
|
||||
|
||||
<pre>
|
||||
(cd mono; make fullbuild)
|
||||
</pre>
|
||||
|
||||
Now you can install the result:
|
||||
|
||||
<pre>
|
||||
(cd mono; make install)
|
||||
</pre>
|
||||
|
||||
Notice that following the above procedure does not require you
|
||||
to manually install the software in the `mcs' directory, as
|
||||
the relevant files will be copied by the `mono' makefiles.
|
||||
|
||||
* Software resources and notes
|
||||
|
||||
The required and additional software can be downloaded here:
|
||||
|
||||
* Microsoft's .NET Framework SDK from
|
||||
<a href="http://msdn.microsoft.com/downloads">
|
||||
msdn.microsoft.com/downloads</a>.
|
||||
|
||||
* Cygwin and the GNU Make tools from
|
||||
<a href="http://www.cygwin.com">www.cygwin.com</a>.
|
||||
Some people observed problems with autoconf 2.52. Installing
|
||||
autoconf 2.13 helped in those cases.
|
||||
|
||||
* Precompiled GLIB 2.0 and pkg-config packages (and
|
||||
their dependencies) by the <a href="http://www.gimp.org/~tml/gimp/win32//index.html">GIMP for Windows</a> project from
|
||||
<a href="http://www.go-mono.com/archive/pkgconfig-0.11-20020310.zip">http://www.go-mono.com/archive/pkgconfig-0.11-20020310.zip</a><br>
|
||||
<a href="http://www.go-mono.com/archive/glib-2.0.4-20020703.zip">http://www.go-mono.com/archive/glib-2.0.4-20020703.zip</a> <br>
|
||||
<a href="http://www.go-mono.com/archive/glib-dev-2.0.4-20020703.zip">http://www.go-mono.com/archive/glib-dev-2.0.4-20020703.zip</a> <br>
|
||||
<a href="http://www.go-mono.com/archive/libiconv-1.7.zip">http://www.go-mono.com/archive/libiconv-1.7.zip</a> <br>
|
||||
<a href="http://www.go-mono.com/archive/libiconv-dev-1.7.zip">http://www.go-mono.com/archive/libiconv-dev-1.7-20020101.zip</a> <br>
|
||||
<a href="http://www.go-mono.com/archive/libintl-0.10.40-20020101.zip">http://www.go-mono.com/archive/libintl-0.10.40-20020101.zip</a><br>
|
||||
|
||||
|
||||
* Download the Mono source code from the
|
||||
<a href="download.html">packaged versions</a> or
|
||||
the <a href="http://www.go-mono.com/snapshots">
|
||||
nightly snapshots</a> or the <a href="anoncvs.html">
|
||||
Anonymous CVS</a>. The nightly snapshots are done every
|
||||
night at 10pm EST (Boston Time). The nightly snapshots are
|
||||
not guaranteed to build, but most of the time they should.
|
||||
</ul>
|
||||
|
||||
|
||||
*** Notes on compiling GLIB 2.0 and pkg-config from source:
|
||||
|
||||
|
||||
<ul>
|
||||
|
||||
* Some people observed problems with autoconf 2.52. Installing
|
||||
autoconf 2.13 helped in those cases (don't forget to do a
|
||||
`make maintainer-clean' after the update).
|
||||
|
||||
* Download, compile and install <a href="http://www.freedesktop.org/software/pkgconfig">pkg-config</a> from source.
|
||||
(I had to change line 674 of
|
||||
<nobr><tt>pkg-config-0.8.0/glib-1.2.8/gstrfuncs.c</tt></nobr> from
|
||||
<nobr><tt>extern char *strsignal (int sig);</tt></nobr> to
|
||||
<nobr><tt>extern const char *strsignal (int sig);</tt></nobr>.
|
||||
|
||||
<pre class="shell">
|
||||
tar xzvf pkg-config-0.8.0.tar.gz
|
||||
cd pkg-config-0.8.0
|
||||
./configure --prefix=/usr
|
||||
make
|
||||
make install
|
||||
</pre>
|
||||
|
||||
* Download, compile and install <a href="ftp://ftp.gnu.org/pub/gnu/libiconv/libiconv-1.7.tar.gz">libiconv</a> from source.<br>
|
||||
If you dont have MS Visual C/C++ 4.0 or 5.0 or 6.0 you can also try
|
||||
the binary package available at <a
|
||||
href="http://www.gimp.org/~tml/gimp/win32/libiconv-1.9.1.bin.woe32.zip">
|
||||
http://www.gimp.org/~tml/gimp/win32/libiconv-1.9.1.bin.woe32.zip</a>
|
||||
|
||||
|
||||
* Download, compile and install the
|
||||
<a href="ftp://ftp.gtk.org/pub/gtk/v2.0/glib-2.0.6.tar.gz">
|
||||
glib 2.0</a> from source.
|
||||
|
||||
</ul>
|
||||
|
||||
+1
-4
@@ -128,10 +128,7 @@
|
||||
|
||||
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"/>
|
||||
<a name="goodbugreport"/>
|
||||
** How to make good bug reports
|
||||
|
||||
A mail from Paolo to mono-devel-list contained this check list:
|
||||
|
||||
+61
-67
@@ -11,15 +11,25 @@
|
||||
|
||||
**** Status
|
||||
<ul>
|
||||
* All classes are present.
|
||||
* Every classes are present.
|
||||
|
||||
* Most classes have their unit tests. Some tests like <code>
|
||||
SymmetricAlgorithmTest</code> are generated by external
|
||||
tools.
|
||||
|
||||
* 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).
|
||||
|
||||
@@ -35,8 +45,8 @@
|
||||
<ul>
|
||||
* All cryptographic algorithms are entirely managed, including
|
||||
classes named <code>*CryptoServiceProvider</code>, with the
|
||||
exception of <code>RNGCryptoServiceProvider</code> for which
|
||||
parts of the implementation resides in the runtime.
|
||||
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
|
||||
@@ -57,8 +67,8 @@
|
||||
(using the Mono.Security.ASN1 class).
|
||||
|
||||
* Software Publisher Certificates (SPC) used by Authenticode
|
||||
(tm) to sign assemblies are supported and <b>minimally</b>
|
||||
validated.
|
||||
(tm) to sign assemblies are supported (extraction from PE
|
||||
files) but <b>not yet</b> validated.
|
||||
|
||||
* Unit tests are generated from a set of existing certificates
|
||||
(about a dozen) each having different properties. Another
|
||||
@@ -67,6 +77,14 @@
|
||||
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
|
||||
@@ -86,8 +104,8 @@
|
||||
continue to evolve to support the security tools.
|
||||
|
||||
* Microsoft implementation of <code>X509Certificate</code> is
|
||||
done by using CryptoAPI (unmanaged code). Based on the
|
||||
exceptions thrown, Authenticode(tm) support is done via COM.
|
||||
done by using CryptoAPI (unmanaged code). From the exceptions
|
||||
thrown Authenticode(tm) support is done via COM.
|
||||
</ul>
|
||||
|
||||
<hr>
|
||||
@@ -135,19 +153,12 @@
|
||||
</ul>
|
||||
*** Namespace: Mono.Security.Cryptography
|
||||
<ul>
|
||||
* Additional algorithms: MD2, MD4, ARCFOUR (required for SSL)
|
||||
* Additional algorithms: MD2, ARCFOUR (required for SSL)
|
||||
* Convertion helpers
|
||||
</ul>
|
||||
*** Namespace: Mono.Security.Protocol.*
|
||||
<ul>
|
||||
* Tls: An 100% managed TLS implementation from Carlos Guzman
|
||||
Alvarez.
|
||||
* Ntlm: NTLM authentication (used for HTTP and SQL Server).
|
||||
</ul>
|
||||
*** Namespace: Mono.Security.X509
|
||||
<ul>
|
||||
* X.509 structures (certificate, CRL...) building and decoding.
|
||||
* PKCS#12 decoding.
|
||||
</ul>
|
||||
*** Namespace: Mono.Security.X509.Extensions
|
||||
<ul>
|
||||
@@ -157,6 +168,8 @@
|
||||
|
||||
**** 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
|
||||
@@ -195,8 +208,7 @@
|
||||
algorithms shouldn't be used in new design (MD4 is broken,
|
||||
MD2 and MD5 aren't considered safe for some usage). They are
|
||||
included to preserve interoperability with older applications
|
||||
(e.g. some old, but still valid, X.509 certificates use MD2,
|
||||
MD4 is required for NTLM authentication ...).
|
||||
(e.g. some old, but still valid, X.509 certificates use MD2).
|
||||
</ul>
|
||||
|
||||
**** TODO
|
||||
@@ -235,36 +247,26 @@
|
||||
<a href="http://www.oasis-open.org/committees/wss/">OASIS</a> or
|
||||
other committees.
|
||||
|
||||
*** Namespace: Microsoft.Web.Services.Security
|
||||
<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>
|
||||
* Most WSE 1.0 classes are implemented.
|
||||
</ul>
|
||||
|
||||
**** TODO
|
||||
<ul>
|
||||
* Some classes from System.Security assembly need to be
|
||||
duplicated (and somewhat fixed) in WSE for XMLDSIG.
|
||||
|
||||
* There are still missing classes and <b>many</b> missing
|
||||
unit tests.
|
||||
</ul>
|
||||
|
||||
|
||||
*** Namespace: Microsoft.Web.Services.Timestamp
|
||||
|
||||
**** Status
|
||||
<ul>
|
||||
* This seems complete for WSE 1.0 but some new classes were
|
||||
introduced in WSE 2.0.
|
||||
* Nothing (yet) commited in CVS <b>[*]</b>.
|
||||
</ul>
|
||||
|
||||
*** Namespace: Microsoft.Web.Services.Security.X509
|
||||
|
||||
**** Status
|
||||
<ul>
|
||||
* X509Certificate support is complete for both WSE 1.0 and 2.0.
|
||||
* Nothing (yet) commited in CVS. 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
|
||||
@@ -277,9 +279,7 @@
|
||||
*** 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. <b>Note that WSDK (the technical
|
||||
preview of WSE) had A LOT of changes before it's initial
|
||||
release!</b>
|
||||
a technical preview of WSE 2.
|
||||
</ul>
|
||||
|
||||
<hr>
|
||||
@@ -292,7 +292,7 @@
|
||||
|
||||
**** Status
|
||||
|
||||
The following tools are complete (or mostly complete):
|
||||
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
|
||||
@@ -305,16 +305,6 @@
|
||||
* <code>makecert</code> to create X.509 test certificates that
|
||||
can be used (once transformed in SPC) to sign assemblies. It's
|
||||
now possible to generate SSL certificates for web servers.
|
||||
|
||||
* <code>sn</code> is a clone of the <code>sn</code> to manage
|
||||
strongnames. Current version can create, convert, sign and
|
||||
verify strongnames signatures. Some configuration options
|
||||
are still missing.
|
||||
|
||||
* <code>signcode</code> and <code>chktrust</code> for signing
|
||||
and validating Authenticode(tm) signatures on assemblies (or
|
||||
any PE file) are now working (signature and timestamps) but
|
||||
some options aren't yet supported.
|
||||
</ul>
|
||||
|
||||
Somewhat usable, somewhat incomplete:
|
||||
@@ -324,6 +314,10 @@
|
||||
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.
|
||||
@@ -333,6 +327,11 @@
|
||||
**** 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>
|
||||
|
||||
@@ -341,21 +340,15 @@
|
||||
tools are of limited use until supported by the runtime.
|
||||
|
||||
<hr>
|
||||
** References
|
||||
** Other stuff
|
||||
|
||||
<ul>
|
||||
* RSA Laboratories' <a href="http://www.rsasecurity.com/rsalabs/faq/index.html">
|
||||
Frequently Asked Questions</a> About Today's Cryptography, Version 4.1
|
||||
|
||||
* Public-Key Cryptography Standards (<a href="http://www.rsasecurity.com/rsalabs/pkcs/index.html">
|
||||
PKCS</a>)
|
||||
|
||||
* National Institute of Standards and Technology - Federal
|
||||
Information Processing Standards <a href="http://csrc.nist.gov/publications/fips/index.html">
|
||||
NIST FIPS</a>
|
||||
* 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>
|
||||
<hr>
|
||||
** How to Help
|
||||
|
||||
<ul>
|
||||
@@ -377,8 +370,9 @@
|
||||
<b>monodoc</b> as I'm not a very good writer (at least in English).
|
||||
</ul>
|
||||
|
||||
Contact <a href="mailto:[email protected]">Sebastien Pouliot</a> if
|
||||
you need additional informations about the status of the cryptographic
|
||||
classes.
|
||||
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: January 26, 2004 (post mono 0.29)
|
||||
Last reviewed: August 9, 2003 (post mono 0.25)
|
||||
+2
-6
@@ -25,11 +25,7 @@
|
||||
libraries as well as the class libraries produced by
|
||||
the project).
|
||||
|
||||
* 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
|
||||
@@ -203,7 +199,7 @@
|
||||
</pre>
|
||||
|
||||
Use this to create lists. Lists contains <item>
|
||||
elements which have to contain <term> containers.
|
||||
elements
|
||||
|
||||
<pre>
|
||||
<list type="table"> </lits>
|
||||
|
||||
+256
-262
@@ -13,262 +13,6 @@
|
||||
section</a>, the <a
|
||||
href="http://www.go-mono.org/faq.html">FAQ</a>.
|
||||
|
||||
<table>
|
||||
<tbody>
|
||||
<tr bgcolor="#DDDDDD">
|
||||
<td>
|
||||
<b>Release 0.29</b><br>
|
||||
<a href="archive/mono-0.29.html">Release notes</a><br>
|
||||
Dec 2nd, 2003
|
||||
</td>
|
||||
<td>
|
||||
<table cellspacing="1" cellpadding="3">
|
||||
<tr bgcolor="#BBBBBB">
|
||||
<td>
|
||||
<b>Source Code</b>
|
||||
</td>
|
||||
<td>
|
||||
<ul>
|
||||
<li><a href="archive/mcs-0.29.tar.gz">Mono Class Libraries and C# Compiler.</a>
|
||||
<li><a href="archive/mono-0.29.tar.gz">Mono Runtime</a>
|
||||
<li><a href="archive/xsp-0.8.tar.gz">XSP web server (0.8)</a>
|
||||
<li><a href="archive/mod_mono-0.6.tar.gz">Apache Mono module 0.6 (mod_mono)</a>
|
||||
<li><a href="archive/monodoc-0.9.tar.gz">MonoDoc 0.9</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr bgcolor="#bbbbbb">
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/redhat-36.gif"><b>Red Hat 8.0, Red Hat 9.0/x86</b><br>
|
||||
<img src="images/mandrake-36.gif"><b>Mandrake 9.1/x86</b><br>
|
||||
<img src="images/suse-36.gif"><b>SuSE 8.2</b><br>
|
||||
</td>
|
||||
<td>
|
||||
Packages are available on <a
|
||||
href="http://www.ximian.com/products/redcarpet/download.html">Red
|
||||
Carpet's</a> Mono channel.
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/windows-36.gif"><b>Windows installer</b>
|
||||
</td>
|
||||
<td>
|
||||
<a href="archive/mono-0.29-win32-1.exe">mono-0.29-win32-1.exe</a>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</td>
|
||||
</table>
|
||||
|
||||
<table>
|
||||
<tbody>
|
||||
<tr bgcolor="#DDDDDD">
|
||||
<td>
|
||||
<b>Release 0.28</b><br>
|
||||
<a href="archive/mono-0.28.html">Release notes</a><br>
|
||||
Oct 1st, 2003
|
||||
</td>
|
||||
<td>
|
||||
<table cellspacing="1" cellpadding="3">
|
||||
<tr bgcolor="#BBBBBB">
|
||||
<td>
|
||||
<b>Source Code</b>
|
||||
</td>
|
||||
<td>
|
||||
<ul>
|
||||
<li><a href="archive/mcs-0.28.tar.gz">Mono Class Libraries and C# Compiler.</a>
|
||||
<li><a href="archive/mono-0.28.tar.gz">Mono Runtime</a>
|
||||
<li><a href="archive/xsp-0.6.tar.gz">XSP web server (0.6)</a>
|
||||
<li><a href="archive/mod_mono-0.5.tar.gz">Apache Mono module (mod_mono)</a>
|
||||
<li><a href="archive/monodoc-0.7.tar.gz">MonoDoc 0.7</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr bgcolor="#BBBBBB">
|
||||
<td>
|
||||
<b>Source RPMs</b><br>
|
||||
(No RPMS for XSP).
|
||||
</td>
|
||||
<td>
|
||||
<ul>
|
||||
<li><a href="archive/redhat-90-i386/mono-0.28-1.ximian.6.1.src.rpm">mono-0.28-1.src.rpm (RH9)</a>
|
||||
<li><a href="archive/redhat-90-i386/mono-0.28-1.ximian.6.1.src.rpm">mono-0.28-1.src.rpm (RH8)</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/redhat-36.gif"><b>Red Hat 9.0/x86</b>
|
||||
<ul>
|
||||
<li><a href="archive/redhat-90-i386/mono-0.28-1.ximian.6.1.i386.rpm">mono-0.28-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/mono-devel-0.28-1.ximian.6.1.i386.rpm">mono-devel-0.28-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/mono-debuginfo-0.28-1.ximian.6.1.i386.rpm">mono-debuginfo-0.28-1.i386.rpm</a>
|
||||
<br>
|
||||
<li><a href="archive/redhat-90-i386/mono-wine-20030318-1.ximian.6.4.i386.rpm">mono-wine-20030318-1.ximian.6.4.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/mono-wine-debuginfo-20030318-1.ximian.6.4.i386.rpm">mono-wine-debuginfo-20030318-1.ximian.6.4.i386.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/redhat-36.gif"><b>Red Hat 8.0/x86</b>
|
||||
<ul>
|
||||
<li><a href="archive/redhat-80-i386/mono-0.28-1.ximian.5.1.i386.rpm">mono-0.28-1.ximian.5.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-80-i386/mono-devel-0.28-1.ximian.5.1.i386.rpm">mono-devel-0.28-1.ximian.5.1.i386.rpm</a>
|
||||
<br>
|
||||
<li><a href="archive/redhat-80-i386/mono-wine-20030318-1.ximian.5.3.i386.rpm">mono-wine-20030318-1.ximian.5.3.i386.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/mandrake-36.gif"><b>Mandrake 9.1/x86</b>
|
||||
<ul>
|
||||
<li><a href="archive/mandrake-91-i586/mono-0.28-1.ximian.6.1.i586.rpm">mono-0.28-1.ximian.6.1.i586.rpm</a>
|
||||
<li><a href="archive/mandrake-91-i586/mono-devel-0.28-1.ximian.6.1.i586.rpm">mono-devel-0.28-1.ximian.6.1.i586.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
<td bgcolor="#999999">
|
||||
<b>Linux s390</b>
|
||||
<ul>
|
||||
<li><a href="archive/s390/libgc-6.1-1.s390.rpm">libgc-6.1-1.s390.rpm</a>
|
||||
<li><a href="archive/s390/libgc-devel-6.1-1.s390.rpm">libgc-devel-6.1-1.s390.rpm</a>
|
||||
<li><a href="archive/s390/mono-0.28-1.s390.rpm">mono-0.28-1.s390.rpm</a>
|
||||
<li><a href="archive/s390/mono-devel-0.28-1.s390.rpm">mono-devel-0.28-1.s390.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/suse-36.gif"><b>SuSE 8.2</b>
|
||||
<ul>
|
||||
<li><a href="archive/suse-82-i586/mono-0.28-1.ximian.7.1.i586.rpm">mono-0.28-1.ximian.7.1.i586.rpm</a>
|
||||
<li><a href="archive/suse-82-i586/mono-devel-0.28-1.ximian.7.1.i586.rpm">mono-devel-0.28-1.ximian.7.1.i586.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/windows-36.gif"><b>Windows installer</b>
|
||||
<ul>
|
||||
<li><a href="archive/mono-0.28-win32-1.exe">mono-0.28-win32-1.exe</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</td>
|
||||
</table>
|
||||
|
||||
<table>
|
||||
<tbody>
|
||||
<tr bgcolor="#DDDDDD">
|
||||
<td>
|
||||
<b>Release 0.26</b><br>
|
||||
<a href="archive/mono-0.26.html">Release notes</a><br>
|
||||
Aug 14, 2003
|
||||
</td>
|
||||
<td>
|
||||
<table cellspacing="1" cellpadding="3">
|
||||
<tr bgcolor="#BBBBBB">
|
||||
<td>
|
||||
<b>Source Code</b>
|
||||
</td>
|
||||
<td>
|
||||
<ul>
|
||||
<li><a href="archive/mcs-0.26.tar.gz">Mono Class Libraries and C# Compiler.</a>
|
||||
<li><a href="archive/mono-0.26.tar.gz">Mono Runtime</a>
|
||||
<li><a href="archive/xsp-0.5.tar.gz">XSP web server (0.5)</a>
|
||||
<li><a href="archive/mod_mono-0.4.tar.gz">Apache Mono module (mod_mono)</a>
|
||||
<li><a href="archive/monodoc-0.6.tar.gz">MonoDoc 0.6</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr bgcolor="#BBBBBB">
|
||||
<td>
|
||||
<b>Source RPMs</b><br>
|
||||
(No RPMS for XSP).
|
||||
</td>
|
||||
<td>
|
||||
<ul>
|
||||
<li><a href="archive/redhat-90-i386/mono-0.26-1.ximian.6.1.src.rpm">mono-0.26-1.src.rpm (RH9)</a>
|
||||
<li><a href="archive/redhat-90-i386/mono-0.26-1.ximian.6.1.src.rpm">mono-0.26-1.src.rpm (RH8)</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/redhat-36.gif"><b>Red Hat 9.0/x86</b>
|
||||
<ul>
|
||||
<li><a href="archive/redhat-90-i386/mono-0.26-1.ximian.6.1.i386.rpm">mono-0.26-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/mono-devel-0.26-1.ximian.6.1.i386.rpm">mono-devel-0.26-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/mono-debuginfo-0.26-1.ximian.6.1.i386.rpm">mono-debuginfo-0.26-1.i386.rpm</a>
|
||||
<br>
|
||||
<li><a href="archive/redhat-90-i386/libpixregion-0.1.0-1.ximian.6.1.i386.rpm">libpixregion-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/libpixregion-debuginfo-0.1.0-1.ximian.6.1.i386.rpm">libpixregion-debuginfo-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/libic-0.1.0-1.ximian.6.1.i386.rpm">libic-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/libic-debuginfo-0.1.0-1.ximian.6.1.i386.rpm">libic-debuginfo-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/xc-0.1.0-1.ximian.6.1.i386.rpm">xc-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/xc-debuginfo-0.1.0-1.ximian.6.1.i386.rpm">xc-debuginfo-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/xr-0.1.0-1.ximian.6.1.i386.rpm">xr-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/xr-debuginfo-0.1.0-1.ximian.6.1.i386.rpm">xr-debuginfo-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<br>
|
||||
<li><a href="archive/redhat-90-i386/monodoc-0.6-1.ximian.6.1.i386.rpm">monodoc-0.6-1.ximian.6.1.i386.rpm</a> (To be used only with CVS gtk-sharp)
|
||||
<li><a href="archive/redhat-90-i386/monodoc-debuginfo-0.5-1.ximian.6.1.i386.rpm">monodoc-debuginfo-0.5-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/mono-wine-20030318-1.ximian.6.3.i386.rpm">mono-wine-20030318-1.ximian.6.3.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/mono-wine-debuginfo-20030318-1.ximian.6.3.i386.rpm">mono-wine-debuginfo-20030318-1.ximian.6.3.i386.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/redhat-36.gif"><b>Red Hat 8.0/x86</b>
|
||||
<ul>
|
||||
<li><a href="archive/redhat-80-i386/mono-0.26-2.ximian.5.1.i386.rpm">mono-0.26-2.ximian.5.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-80-i386/mono-devel-0.26-2.ximian.5.1.i386.rpm">mono-devel-0.26-2.ximian.5.1.i386.rpm</a>
|
||||
<br>
|
||||
<li><a href="archive/redhat-80-i386/monodoc-0.5-1.ximian.5.1.i386.rpm">monodoc-0.5-1.ximian.5.1.i386.rpm</a> (To be used only with CVS gtk-sharp)
|
||||
<li><a href="archive/redhat-80-i386/mono-wine-20030318-1.ximian.5.3.i386.rpm">mono-wine-20030318-1.ximian.5.3.i386.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/debian-36.gif"><b>Debian</b>
|
||||
<ul>
|
||||
<li><a href="http://www.debianplanet.com/mono/">Debian Packages here.</a>
|
||||
</ul>
|
||||
</td>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/mandrake-36.gif"><b>Mandrake 9.1/x86</b>
|
||||
<ul>
|
||||
<li><a href="archive/mandrake-91-i586/mono-0.26-1.ximian.6.1.i586.rpm">mono-0.26-1.ximian.6.1.i586.rpm</a>
|
||||
<li><a href="archive/mandrake-91-i586/mono-devel-0.26-1.ximian.6.1.i586.rpm">mono-devel-0.26-1.ximian.6.1.i586.rpm</a>
|
||||
<!-- <li><a href="archive/mandrake-91-i586/monodoc-0.5-1.ximian.6.1.i586.rpm">monodoc-0.5-1.ximian.6.1.i586.rpm</a> -->
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/suse-36.gif"><b>SuSE 8.2</b>
|
||||
<ul>
|
||||
<li><a href="archive/suse-82-i586/mono-0.26-2.ximian.7.1.i586.rpm">mono-0.26-2.ximian.7.1.i586.rpm</a>
|
||||
<li><a href="archive/suse-82-i586/mono-devel-0.26-2.ximian.7.1.i586.rpm">mono-devel-0.26-2.ximian.7.1.i586.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/windows-36.gif"><b>Windows installer</b>
|
||||
<ul>
|
||||
<li><a href="archive/mono-0.26-win32-2.exe">mono-0.26-win32-2.exe</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</td>
|
||||
</table>
|
||||
<table>
|
||||
<tbody>
|
||||
<tr bgcolor="#DDDDDD">
|
||||
@@ -289,7 +33,7 @@
|
||||
<li><a href="archive/mono-0.25.tar.gz">Mono Runtime</a>
|
||||
<li><a href="archive/xsp-0.4.tar.gz">XSP web server (0.4)</a>
|
||||
<li><a href="archive/monodoc-0.5.tar.gz">MonoDoc 0.5</a>
|
||||
<li><a href="archive/gtk-sharp-0.11.tar.gz">Gtk# 0.11</a>
|
||||
<li><a href="archive/gtk-sharp-0.10.tar.gz">Gtk# 0.10</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
@@ -300,7 +44,7 @@
|
||||
</td>
|
||||
<td>
|
||||
<ul>
|
||||
<li><a href="archive/redhat-80-i386/mono-0.25-1.ximian.5.1.src.rpm">mono-0.25-1.src.rpm</a>
|
||||
<li><a href="archive/mono-0.25-1.ximian.5.src.rpm">mono-0.25-1.src.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
@@ -855,7 +599,7 @@
|
||||
<td>
|
||||
<ul>
|
||||
<li><a href="archive/libgc-6.1-1.src.rpm">libgc-6.1-1.src.rpm</a>
|
||||
<li><a href="archive/redhat-73-i386/mono-0.20-1.src.rpm">mono-0.20-1.src.rpm</a>
|
||||
<li><a href="archive/mono-0.20-1.src.rpm">mono-0.20-1.src.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
@@ -1169,6 +913,7 @@
|
||||
|
||||
<ul>
|
||||
* <a href="http://www.debianplanet.org/mono/">DebianPlanet</a>
|
||||
* <a href="http://www.superin.formativ.net/mono/mono.htm">Windows</a> (works without cygwin!)
|
||||
</ul>
|
||||
|
||||
* Snapshots
|
||||
@@ -1183,7 +928,256 @@
|
||||
The <a href="anoncvs.html">anoncvs</a> mirrors provided by
|
||||
Hispalinux are updated every six hours.
|
||||
|
||||
* Compilation
|
||||
* Compiling the code
|
||||
|
||||
For instructions on how to build Mono, please refer to the
|
||||
<a href="compiling.html">compiling</a> page.
|
||||
There are a number of ways of compiling Mono
|
||||
|
||||
<ul>
|
||||
<li>From the <a href="#scripts">scripts</A>
|
||||
|
||||
<LI><a href="#install">Manually</a> for the first time.
|
||||
|
||||
<li>Manually, <a href="#upgrade">while upgrading</a> to CVS
|
||||
</ul>
|
||||
|
||||
(which is an easy way to get the latest CVS information)
|
||||
|
||||
<a name="scripts">
|
||||
* Compiling with scripts
|
||||
|
||||
There are scripts to help build mono for both Unix and Windows. Get
|
||||
<a href="mono-build.sh">mono-build.sh</a> for Unix, or <a
|
||||
href="mono-build-w32.sh">mono-build-w32.sh</a> for Windows.
|
||||
These scripts automate the installation of GLIB and pkgconfig
|
||||
(building from source on Unix, and using binary packages
|
||||
provided by the GIMP for Windows project on Windows.) To use
|
||||
the script, follow these simple steps:
|
||||
|
||||
<ul>
|
||||
* Save the script for your platform somewhere (e.g. /usr/local/bin)
|
||||
* Make the script executable (i.e chmod 755 /usr/local/bin/mono-build.sh)
|
||||
* Create a directory to hold the mono source, and the compiled binaries (e.g. mkdir ~/mono)
|
||||
* Change to the new directory (i.e. cd ~/mono)
|
||||
* run the script (i.e. /usr/local/bin/mono-build.sh)
|
||||
</ul>
|
||||
|
||||
The script requires wget on either platform, and building the
|
||||
software requires make, gcc, automake, autoconf, and libtool.
|
||||
You should install these packages from your distribution or
|
||||
with the cygwin installer. You should also take care of setting
|
||||
the right environment variables as the PKG_CONFIG_FLAGS, etc.
|
||||
|
||||
The script will download required packages from
|
||||
www.go-mono.com and do a cvs checkout of mono in the current
|
||||
directory. <b>IMPORTANT!:</b> The cvs server chosen defaults to
|
||||
anonymous cvs;
|
||||
set your CVSROOT environment variable before running the script to
|
||||
select a particular cvs server.
|
||||
|
||||
<a name="install">
|
||||
** Building the software manually
|
||||
|
||||
You will need to obtain the Mono dependencies first: <a
|
||||
href="http://www.gtk.org">glib 2.x</a> and
|
||||
<a href="http://www.freedesktop.org/software/pkgconfig">pkg-config</a>.
|
||||
|
||||
*** Building on Linux
|
||||
|
||||
<ul>
|
||||
Unpack the Mono runtime distribution:
|
||||
<pre>
|
||||
tar xzvf mono-X.XX.tar.gz
|
||||
cd mono-X.XX
|
||||
|
||||
</pre>
|
||||
<p>
|
||||
|
||||
Then configure, compile and install:
|
||||
|
||||
<pre>
|
||||
|
||||
./configure --prefix=/usr/local
|
||||
make
|
||||
make install</pre>
|
||||
|
||||
This will give you a runtime, C# compiler and runtime
|
||||
libraries.
|
||||
|
||||
If you want to recompile the runtime and the compiler,
|
||||
follow these steps, first unpack the MCS package:
|
||||
|
||||
<pre>
|
||||
tar xzvf mcs-X.XX.tar.gz
|
||||
|
||||
cd mcs-X.XX
|
||||
</pre>
|
||||
|
||||
Then use the following command to compile and install:
|
||||
|
||||
<pre>
|
||||
|
||||
make -f makefile.gnu install prefix=/usr/local
|
||||
</pre>
|
||||
|
||||
You can change /usr/local to something else if you want.
|
||||
</ul>
|
||||
|
||||
|
||||
*** On Windows, to install and work on the compiler and the class libraries:
|
||||
|
||||
**** Install Cygwin and the GNU build tools, Microsoft's .NET Framework SDK and the precompiled GLIB 2.0 and pkg-config libraries.
|
||||
|
||||
<ul>
|
||||
|
||||
* Install <a href="http://www.cygwin.com">Cygwin</a>.
|
||||
|
||||
* Install <a href="http://msdn.microsoft.com/downloads">
|
||||
Microsoft .NET Framework SDK</a>.
|
||||
|
||||
* Change to the /usr/local directory
|
||||
of your Cygwin installation.<br>
|
||||
Unzip the precompiled packages listed above.
|
||||
|
||||
</ul>
|
||||
<ul>
|
||||
|
||||
* If you downloaded the Mono
|
||||
<a href="http://www.go-mono.com/snapshots">nightly snapshot
|
||||
</a>, untar the snapshot.
|
||||
|
||||
* Change directories to "mcs".
|
||||
|
||||
* Compile:
|
||||
|
||||
<pre>
|
||||
make
|
||||
</pre>
|
||||
</ul>
|
||||
|
||||
*** On Windows, to compile the mono runtime:
|
||||
|
||||
<ul>
|
||||
|
||||
* If you downloaded the Mono
|
||||
<a href="http://www.go-mono.com/snapshots">nightly snapshot
|
||||
</a>, untar the snapshot.
|
||||
|
||||
* Change directories to "mono".
|
||||
|
||||
* Configure, compile and install:
|
||||
<pre>
|
||||
./configure --prefix=c:/mono
|
||||
make
|
||||
make install
|
||||
</pre>
|
||||
|
||||
</ul>
|
||||
|
||||
* Software resources and notes
|
||||
|
||||
The required and additional software can be downloaded here:
|
||||
|
||||
* Microsoft's .NET Framework SDK from
|
||||
<a href="http://msdn.microsoft.com/downloads">
|
||||
msdn.microsoft.com/downloads</a>.
|
||||
|
||||
* Cygwin and the GNU Make tools from
|
||||
<a href="http://www.cygwin.com">www.cygwin.com</a>.
|
||||
Some people observed problems with autoconf 2.52. Installing
|
||||
autoconf 2.13 helped in those cases.
|
||||
|
||||
* Precompiled GLIB 2.0 and pkg-config packages (and
|
||||
their dependencies) by the <a href="http://www.gimp.org/~tml/gimp/win32//index.html">GIMP for Windows</a> project from
|
||||
<a href="http://www.go-mono.com/archive/pkgconfig-0.11-20020310.zip">http://www.go-mono.com/archive/pkgconfig-0.11-20020310.zip</a><br>
|
||||
<a href="http://www.go-mono.com/archive/glib-2.0.4-20020703.zip">http://www.go-mono.com/archive/glib-2.0.4-20020703.zip</a> <br>
|
||||
<a href="http://www.go-mono.com/archive/glib-dev-2.0.4-20020703.zip">http://www.go-mono.com/archive/glib-dev-2.0.4-20020703.zip</a> <br>
|
||||
<a href="http://www.go-mono.com/archive/libiconv-1.7.zip">http://www.go-mono.com/archive/libiconv-1.7.zip</a> <br>
|
||||
<a href="http://www.go-mono.com/archive/libiconv-dev-1.7.zip">http://www.go-mono.com/archive/libiconv-dev-1.7-20020101.zip</a> <br>
|
||||
<a href="http://www.go-mono.com/archive/libintl-0.10.40-20020101.zip">http://www.go-mono.com/archive/libintl-0.10.40-20020101.zip</a><br>
|
||||
|
||||
|
||||
* Download the Mono source code from the
|
||||
<a href="#feb-11">packaged versions</a> or
|
||||
the <a href="http://www.go-mono.com/snapshots">
|
||||
nightly snapshots</a> or the <a href="anoncvs.html">
|
||||
Anonymous CVS</a>. The nightly snapshots are done every
|
||||
night at 10pm EST (Boston Time). The nightly snapshots are
|
||||
not guaranteed to build, but most of the time they should.
|
||||
|
||||
|
||||
</ul>
|
||||
|
||||
|
||||
*** Notes on compiling GLIB 2.0 and pkg-config from source:
|
||||
|
||||
|
||||
<ul>
|
||||
|
||||
* Some people observed problems with autoconf 2.52. Installing
|
||||
autoconf 2.13 helped in those cases (don't forget to do a
|
||||
`make maintainer-clean' after the update).
|
||||
|
||||
* Download, compile and install <a href="http://www.freedesktop.org/software/pkgconfig">pkg-config</a> from source.
|
||||
(I had to change line 674 of
|
||||
<nobr><tt>pkg-config-0.8.0/glib-1.2.8/gstrfuncs.c</tt></nobr> from
|
||||
<nobr><tt>extern char *strsignal (int sig);</tt></nobr> to
|
||||
<nobr><tt>extern const char *strsignal (int sig);</tt></nobr>.
|
||||
|
||||
<pre>
|
||||
tar xzvf pkg-config-0.8.0.tar.gz
|
||||
cd pkg-config-0.8.0
|
||||
./configure --prefix=/usr
|
||||
make
|
||||
make install
|
||||
</pre>
|
||||
|
||||
* Download, compile and install <a href="ftp://ftp.gnu.org/pub/gnu/libiconv/libiconv-1.7.tar.gz">libiconv</a> from source.<br>
|
||||
If you dont have MS Visual C/C++ 4.0 or 5.0 or 6.0 you can also try
|
||||
the binary package available at <a
|
||||
href="http://www.gimp.org/win32/libiconv-dev-20001007.zip">
|
||||
http://www.gimp.org/win32/libiconv-dev-20001007.zip</a>.
|
||||
|
||||
|
||||
* Download, compile and install the
|
||||
<a href="ftp://ftp.gtk.org/pub/gtk/v2.0/glib-2.0.6.tar.gz">
|
||||
glib 2.0</a> from source.
|
||||
|
||||
</ul>
|
||||
|
||||
<a name="upgrading">
|
||||
** Upgrading
|
||||
|
||||
To upgrade your Mono installation from CVS, it is very
|
||||
important that you update your Mono and MCS modules from CVS
|
||||
at the same time. Failure to do so might result in a
|
||||
problematic installation as the runtime and the class
|
||||
libraries will be out of sync.
|
||||
|
||||
Run the following commands to update your CVS tree (more
|
||||
details in <a href="ccvs.html">Cvs and Mono</a> and the <A
|
||||
href="anoncvs.html">AnonCVS and Mono</a> pages).
|
||||
|
||||
<pre>
|
||||
(cd mono; cvs update -dP .)
|
||||
(cd mcs; cvs update -dP .)
|
||||
</pre>
|
||||
|
||||
Once you have updated your sources, remove any cached
|
||||
assemblies or old binaries from the Mono "runtime" directory,
|
||||
and then compile each component:
|
||||
|
||||
<pre>
|
||||
(cd mono/runtime; rm *exe *dll)
|
||||
(cd mono; make)
|
||||
(cd mcs; make)
|
||||
</pre>
|
||||
|
||||
Now you can install the result:
|
||||
|
||||
<pre>
|
||||
(cd mono; make install)
|
||||
</pre>
|
||||
|
||||
Notice that following the above procedure does not require you
|
||||
to manually install the software in the `mcs' directory, as
|
||||
the relevant files will be copied by the `mono' makefiles.
|
||||
-51
@@ -1,51 +0,0 @@
|
||||
* Drawing
|
||||
|
||||
Mono provides two mechanism to draw. The first exposes the
|
||||
Microsoft System.Drawing API and the second exposes the <a
|
||||
href="http://www.cairographics.org">Cairo</a> API.
|
||||
|
||||
* System.Drawing
|
||||
|
||||
The System.Drawing implementation in Mono is designed to be
|
||||
compatible with the Microsoft API. The imaging model is very
|
||||
similar to the PDF 1.4 composition-based imaging model.
|
||||
|
||||
Our implementation is a C# wrapper around the GDI+ C API (also
|
||||
called the <a
|
||||
href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/gdicpp/GDIPlus/GDIPlusReference.asp">"GDI+
|
||||
Flat API"</a>).
|
||||
|
||||
This means that the C# code is the same for Windows and Unix
|
||||
systems. The following graph explains the situation:
|
||||
|
||||
<center>
|
||||
<img src="images/system-drawing.png">
|
||||
</center>
|
||||
|
||||
In Windows Mono uses the GDI+ library that is included with
|
||||
the operating system (<tt>GDIPLUS.DLL</tt>, while in Unix we
|
||||
provide an implementation of this API in the
|
||||
<tt>libgdiplus.so</tt> shared library. Our
|
||||
<tt>libgdiplus.so</tt> has the same C Flat API as the
|
||||
<tt>GDIPLUS.DLL</tt>. Our implementation uses Cairo to do
|
||||
the heavy lifting.
|
||||
|
||||
The implementation of GDI+ lives in mcs/class/System.Drawing
|
||||
in the gdiplus directory and requires <a
|
||||
href="http://www.cairographics.org">Cairo</a> to be installed
|
||||
to get the package built.
|
||||
|
||||
The C# code that implement System.Drawing is the same for
|
||||
Windows and Unix builds.
|
||||
|
||||
Since this is an implementation of an existing Microsoft API
|
||||
no architectural changes go here.
|
||||
|
||||
* Mono.Cairo
|
||||
|
||||
The Mono.Cairo.dll assembly exposes the Cairo API to managed
|
||||
applications. The mapping is a pretty straightforward one,
|
||||
and the programming model is very close to the C API.
|
||||
|
||||
This API is still unstable due to the nature of the underlying
|
||||
API being used and will be revisited as Cairo evolves.
|
||||
@@ -120,10 +120,6 @@
|
||||
layer, so in each file where you use pthread.h you should
|
||||
include the <gc/gc.h> file.
|
||||
|
||||
If you can not do this for any reasons, just remember that you
|
||||
can not store pointers to Mono Objects on the stack, you can
|
||||
store them safely in the heap, or in global variables though
|
||||
|
||||
* Exposing C code to the CIL universe
|
||||
|
||||
The Mono runtime provides two mechanisms to expose C code to
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
<a href="#basics">Basics</a><br>
|
||||
<a href="#novell">The Novell Role in the Mono project</a><br>
|
||||
<a href="#ximian">The Ximian Role in the Mono project</a><br>
|
||||
<a href="#gnome">Mono and GNOME</a><br>
|
||||
<a href="#gui">Building GUI applications with Mono</a><br>
|
||||
<a href="#msft">Mono and Microsoft</a><br>
|
||||
@@ -23,8 +23,8 @@
|
||||
<a href="#problems">Mono Common Problems</a><br>
|
||||
|
||||
A <a
|
||||
href="http://www.monohispano.org/tutoriales/mono-puf//">Spanish
|
||||
translation</a> is also available (it is outdated though)
|
||||
href="http://www.es.gnome.org/documentacion/articulos/mono-puf/mono-puf/">Spanish
|
||||
translation</a> is also available
|
||||
|
||||
<a name="basics"></a>
|
||||
** Basics
|
||||
@@ -39,55 +39,14 @@ A: The Mono Project is an open development initiative sponsored by
|
||||
implement various technologies developed by Microsoft that have now
|
||||
been submitted to the ECMA for standardization.
|
||||
|
||||
The Mono project has also sparked a lot of interest in developing
|
||||
C#-based components, libraries and frameworks. Today Mono is not
|
||||
limited to implement the .NET Framework, but also contains other
|
||||
components. Some of the components of the Mono platform were
|
||||
developed by the Mono team, and some others we have incorporated
|
||||
from other open source efforts, the most important ones:
|
||||
|
||||
<ul>
|
||||
<li><a
|
||||
href="http://remoting-corba.sourceforge.net/">Remoting.CORBA</a>: A
|
||||
CORBA implementation for Mono.
|
||||
|
||||
<li>Ginzu: An implementation on top of Remoting for the <a
|
||||
href="http://www.zeroc.com">ICE</a> stack
|
||||
|
||||
<li><a href="http://gtk-sharp.sf.net">Gtk#</a>: Bindings for
|
||||
the popular Gtk+ GUI toolkit for Unix and Windows systems.
|
||||
Other bindings are available: Diacanvas-Sharp and MrProject.
|
||||
|
||||
<li><a
|
||||
href="http://www.icsharpcode.net/OpenSource/SharpZipLib/Default.aspx">#ZipLib</a>:
|
||||
A library to manipulate various kinds of compressed files and
|
||||
archives (Zip and tar).
|
||||
|
||||
<li>GlGen (available from the Mono CVS): Bindings for OpenGL.
|
||||
|
||||
<li>Mono.LDAP: LDAP access for .NET apps.
|
||||
|
||||
<li>Mono.Data: We ship support for Postgress, MySql, Sybase,
|
||||
DB2, SqlLite, Tds (SQL server protocol) and Oracle databases.
|
||||
|
||||
<li>Mono.Cairo: Bindings for the <a
|
||||
href="http://www.cairographics.org">Cairo</a> rendering
|
||||
engine (Our System.Drawing is implemented on top of this).
|
||||
|
||||
<li>Mono.Posix: Bindings for building POSIX applications using
|
||||
C#.
|
||||
|
||||
<li>Mono.Http: Support for creating custom, embedded HTTP
|
||||
servers and common HTTP handlers for your applications.
|
||||
</ul>
|
||||
|
||||
Q: What is the difference between Mono and the .NET Initiative?
|
||||
|
||||
A: The ".NET Initiative" is a somewhat nebulous company-wide effort by
|
||||
Microsoft, one part of which is a cross-platform development
|
||||
framework. Mono is an implementation of the development framework,
|
||||
but not an implementation of anything else related to the .NET
|
||||
Initiative, such as Passport or software-as-a-service.
|
||||
Initiative, such as Passport, software-as-a-service, or
|
||||
corporate re-branding.
|
||||
|
||||
Q: What technologies are included in Mono?
|
||||
|
||||
@@ -100,9 +59,7 @@ A: Mono contains a number of components useful for building new
|
||||
compiler, and a garbage collecting runtime.
|
||||
|
||||
* A class library that can work with any language
|
||||
which works on the CLR. Both .NET compatible class
|
||||
libraries as well as Mono-provided class libraries
|
||||
are included.
|
||||
which works on the CLR.
|
||||
|
||||
* A compiler for the C# language. In the future we
|
||||
might work on other compilers that target the Common
|
||||
@@ -146,26 +103,49 @@ Q: Will you offer an ECMA-compliant set of class libraries?
|
||||
|
||||
A: Eventually we will. Our current focus is on inter-operating
|
||||
with the Microsoft SDK, but we will also offer an ECMA compliant
|
||||
subset of the libraries.
|
||||
set of libraries.
|
||||
|
||||
Q: What does the name "Mono" mean?
|
||||
|
||||
A: Mono is the word for `monkey' in Spanish. We like monkeys.
|
||||
A: Mono is the word for `monkey' in Spanish. We like monkeys.
|
||||
|
||||
Q: Does Mono work today?
|
||||
Q: Is Mono usable?
|
||||
|
||||
A: The execution engine works on various platforms, we support
|
||||
Just-in-Time and Ahead-of-Time compilations on Intel x86 machines
|
||||
(and soon PowerPC).
|
||||
A: The JIT engine is usable on Intel x86 machines. An interpreter
|
||||
can be used on other non-Intel x86 machines.
|
||||
|
||||
The class libraries are mature enough to run various real
|
||||
applications: our C# compiler, ASP.NET, and Gtk#-based
|
||||
applications.
|
||||
The class libraries are mature enough to run some real applications
|
||||
(the compiler for instance, and every day more and more applications
|
||||
are natively developed with Mono).
|
||||
|
||||
Q: When will you ship Mono?
|
||||
Q: When will you ship it?
|
||||
|
||||
A: Please see the <a href="mono-roadmap.html">Mono Roadmap</a> for
|
||||
more details on the release plans.
|
||||
A: Different parts of Mono will achieve usability at different stages,
|
||||
once we are comfortable with the compiler, we will release "Mono Core",
|
||||
which contains everything needed to develop applications with the base
|
||||
class libraries, this will happen soon and in the meantime you can
|
||||
download daily snapshots of our work. Also the full ASP.NET support is
|
||||
close to completion.
|
||||
|
||||
Other higher level class libraries (ASP.NET, ADO.NET, WinForms) will
|
||||
be released when they become stable.
|
||||
|
||||
Q: When will Mono 1.0 ship?
|
||||
|
||||
A: We are planning on releasing Mono 1.0 (Mono Core) which will ship all the
|
||||
components of Mono that are known to be stable in Q4 2003.
|
||||
|
||||
This release will lack System.Windows.Forms and
|
||||
Enterprise.Services, as they will not be production ready on this timeframe.
|
||||
|
||||
Mono 1.2 should come in Q2 2004 and include the missing components
|
||||
libraries that will make Mono feature-compatible with .NET 1.0
|
||||
|
||||
Q: What major components will you include in Mono?
|
||||
|
||||
A: Hopefully everything that Microsoft ships on their Framework
|
||||
(ADO.NET, ASP.NET, WinForms), and we encourage third party developers to
|
||||
create reusable components that work on both Mono and Windows.
|
||||
|
||||
Q: How can I contribute?
|
||||
|
||||
@@ -187,26 +167,26 @@ Q: Miguel said once that Mono was being implemented in COBOL. Is that true?.
|
||||
A: No. It was a joke.
|
||||
|
||||
|
||||
<a name="novell"></a>
|
||||
<a name="ximian"></a>
|
||||
|
||||
** The Novell Role in the Mono Project
|
||||
** The Ximian Role in the Mono Project
|
||||
|
||||
Q: Why is Novell working on .NET?
|
||||
Q: Why is Ximian working on .NET?
|
||||
|
||||
A: Novell is interested in providing the best tools for programmers to
|
||||
develop applications for Free Operating Systems.
|
||||
A: Ximian is interested in providing the best tools for programmers to
|
||||
develop applications for Free Operating Systems.
|
||||
|
||||
For more information, read the project <a
|
||||
href="rationale.html">rationale</a> page.
|
||||
|
||||
Q: Will Novell be able to take on a project of this size?
|
||||
Q: Will Ximian be able to take on a project of this size?
|
||||
|
||||
A: Of course not. Novell is a supporter of the Mono project, but the only way
|
||||
A: Of course not. Ximian a supporter of the Mono project, but the only way
|
||||
to implement something of this size is for the entire free software
|
||||
community to get involved. Visit the <a href="contributing.html">contributing</a>
|
||||
page if you'd like to help out.
|
||||
|
||||
Q: What pieces Novell be working on?
|
||||
Q: What pieces will Ximian be working on?
|
||||
|
||||
A: We will devote most of our resources to work on the pieces which are
|
||||
on the critical path to release a development and execution
|
||||
@@ -214,30 +194,25 @@ A: We will devote most of our resources to work on the pieces which are
|
||||
the real world, it will achieve a critical mass of developers to
|
||||
improve it further.
|
||||
|
||||
Q: Will Novell offer Mono commercially?
|
||||
Q: Will Ximian offer Mono commercially?
|
||||
|
||||
A: When Mono is ready to be shipped Ximian will offer a commercial
|
||||
support and services for Mono. Mono components are also
|
||||
available to be licensed commercially. For licensing details,
|
||||
contact <a
|
||||
href="mailto:[email protected]">[email protected]</a>
|
||||
support and services for Mono.
|
||||
|
||||
Q: Does Novell provide consulting services around Mono?
|
||||
Q: Does Ximian provide consulting services around Mono?
|
||||
|
||||
A: Yes, Novell does provide consulting services around Mono to
|
||||
A: Yes, Ximian does provide consulting services around Mono to
|
||||
make it suitable to your needs. Porting the runtime engine,
|
||||
customizing it, working on specific classes or tuning the code
|
||||
for your particular needs.
|
||||
|
||||
Please contact <a
|
||||
href="mailto:[email protected]">[email protected]</a>
|
||||
for consulting services information.
|
||||
|
||||
Q: Will you wait until Mono is finished?
|
||||
|
||||
A: Mono will ship on various stages as they mature. Some people
|
||||
require only a subset of the technologies, those will ship first,
|
||||
see the <a href="mono-roadmap.html">Mono Roadmap</a> for details
|
||||
require only a subset of the technologies, those will ship first.
|
||||
|
||||
More advanced features will take more time to develop. A support
|
||||
time line will be available in June 2002.
|
||||
|
||||
<a name="gnome"></a>
|
||||
** Mono and GNOME
|
||||
@@ -251,10 +226,6 @@ A: In a number of ways. This project was born out of the need of
|
||||
implement Winforms and the Drawing2D API and are considering
|
||||
GObject support.
|
||||
|
||||
Mono team members work actively on the <a
|
||||
href="http://gtk-sharp.sf.net">Gtk#</a> project: a binding of the
|
||||
GNOME class libraries for .NET and Mono.
|
||||
|
||||
Q: Has the GNOME Foundation or the GNOME team adopted Mono?
|
||||
|
||||
A: Mono is too new to be adopted by those groups. We hope that the
|
||||
@@ -283,8 +254,7 @@ A: Yes, we will provide a set of classes for implementing and using
|
||||
Q: Does Mono depend on GNOME?
|
||||
|
||||
A: No, Mono does not depend on GNOME. We use a few packages produced by
|
||||
the GNOME team like the `glib' library, we also use other
|
||||
third-party open source libraries like Cairo and ICU.
|
||||
the GNOME team like the `glib' library.
|
||||
|
||||
Q: But will I be able to build GNOME applications?
|
||||
|
||||
@@ -292,58 +262,50 @@ A: Yes, we will enable people to write GNOME applications using Mono.
|
||||
|
||||
Q: Do you have C# bindings for GNOME?.
|
||||
|
||||
A: Yes, the <a href="http://gtk-sharp.sf.net">Gtk# project</a>
|
||||
provides bindings for Gtk+, Gdk, Atk, libgnome, libgnomecanvas, and
|
||||
libgnomeui. Other libraries under the GNOME framework will be
|
||||
added on an as-needed (and as-requested) basis.
|
||||
A: Yes, we currently bind libgnome, libgnomecanvas, and libgnomeui --
|
||||
although I dare say I have no idea how functional the bindings are
|
||||
outside of what I tested in the sample app. I imagine other libraries
|
||||
under the GNOME framework will be added on an as-needed (and as-requested)
|
||||
basis...although a truly good bonobo binding will have to wait on the CORBA
|
||||
remoting support which has been started recently.
|
||||
|
||||
<a name="gui"></a>
|
||||
** GUI applications
|
||||
|
||||
Q: Will Mono enable GUI applications to be authored?
|
||||
|
||||
A: Yes, you will be able to build GUI applications. Indeed, that is
|
||||
our main focus. Today you can use Gtk# or #WT to develop GUI
|
||||
applications, and support for Windows.Forms is underway.
|
||||
A: Yes, you will be able to build GUI applications. Indeed, that is our
|
||||
main focus. We will provide both the Windows.Forms API and the Gtk# API.
|
||||
|
||||
Q: What is the difference between Gtk# and System.Windows.Forms?
|
||||
|
||||
A: Gtk# is a set of bindings for the Gtk+ toolkit for C# (and other
|
||||
CIL-enabled languages), it integrates natively with the Gnome
|
||||
desktop. System.Windows.Forms is an API defined by Microsoft to
|
||||
build GUI applications.
|
||||
|
||||
Windows.Forms is currently being implemented on top of a modified
|
||||
version of Wine that can be used as a library: WineLib.
|
||||
CIL-enabled languages). System.Windows.Forms is an API defined
|
||||
by Microsoft to build GUI applications.
|
||||
|
||||
Q: Why not implement System.Windows.Forms on top of Gtk# or Qt#?
|
||||
|
||||
A: Compatibility.
|
||||
A: There are several reasons for this.
|
||||
|
||||
Although it is possible to run simple Windows.Forms applications
|
||||
with the Gtk#-based backend of Windows.Forms, it is very unlikely
|
||||
that the implementation will ever implement everything needed for
|
||||
full compatibility with Windows.Forms.
|
||||
|
||||
The reason is that Windows.Forms is not a complete toolkit, and to
|
||||
work around this problem some of the underlying Win32 foundation is
|
||||
exposed to the programmer in the form of exposing the Windows
|
||||
message handler (WndProc). Any control can override this method.
|
||||
Also developers often P/Invoke into Win32 to get to functionality
|
||||
that was not wrapped.
|
||||
|
||||
To achieve full compatibility, we would have to emulate this, and
|
||||
it would take too long.
|
||||
|
||||
For more details see the <a href="winforms.html">winforms page</a>
|
||||
|
||||
Q: Wine applications do not look like native applications, what are
|
||||
you going to do about this?
|
||||
|
||||
A: We have already a few patches into our version of Windows.Forms
|
||||
that makes Wine use the colors and font settings from your desktop,
|
||||
improving the integration a lot. In the future, we will continue
|
||||
to improve this interoperability scenario.
|
||||
First of all, Gtk+ and Qt are standard toolkits on Linux, and their
|
||||
proponents want to use their favorite toolkits when writing
|
||||
applications.
|
||||
|
||||
Related to this is the idea that System.Windows.Forms is
|
||||
brain-dead in certain areas, such as internationalization.
|
||||
System.Windows.Forms uses explicit sizes for all controls, as opposed
|
||||
to Gtk+ and Qt which use a box/packing model, which can better deal with
|
||||
the different string lengths different languages will have.
|
||||
|
||||
Next is compatibility. It is not possible to implement
|
||||
System.Windows.Forms on top of Gtk+/Qt and have 100% compatibility,
|
||||
because System.Windows.Forms exposes some Win32-isms, such as the
|
||||
Win32 message loop. In order to maintain compatibility, Wine must be used,
|
||||
and this is being done; see the
|
||||
<a href="/winforms.html">System.Windows.Forms effort page</a>.
|
||||
|
||||
Additionally, Wine apps don't currently fit in -- visually -- with
|
||||
Gtk+ or Qt apps.
|
||||
|
||||
Q: Will I be able to run my smart clients on systems powered by Mono?
|
||||
|
||||
@@ -353,7 +315,7 @@ A: As long as your applications are 100% .NET and do not make use
|
||||
|
||||
Q: Where can I learn more about Gtk#?
|
||||
|
||||
A: The following <a href="http://gtk-sharp.sourceforge.net">link</a> sends you to the page of the project.
|
||||
A: The following <a href="http://gtk-sharp.sourceforge.net>link</a> sends you to the page of the project.
|
||||
|
||||
Q: What can I do with Gtk#?.
|
||||
|
||||
@@ -363,7 +325,9 @@ A: Gtk# is becoming very usable and you can create applications and
|
||||
|
||||
Q: How can I compile my HelloWorld.cs which uses Gtk#?.
|
||||
|
||||
A: Try: mcs -r:gtk-sharp HelloWorld.cs
|
||||
A: Try: mcs --unsafe -o HelloWorld.exe -r glib-sharp -r pango-sharp -r
|
||||
atk-sharp -r gdk-sharp -r gtk-sharp -r gdk-imaging-sharp
|
||||
HelloWorld.cs
|
||||
|
||||
Q: Is there any way how to connect DataAdapter to some GTK# controls?
|
||||
|
||||
@@ -378,14 +342,9 @@ A: There is a sample file called `DbClient' in gtk-sharp/samples that you
|
||||
|
||||
Q: Do you have an estimate for when Windows.Forms will be released?
|
||||
|
||||
A: The plan currently is aimed at Q3/2004.
|
||||
|
||||
|
||||
Q: Do you have a comparission chart about the various toolkit
|
||||
offerings?
|
||||
|
||||
A: A document explaining this is available at: <a
|
||||
href="http://primates.ximian.com/~miguel/toolkits.html">http://primates.ximian.com/~miguel/toolkits.html</a>.
|
||||
A: We do not know, volunteers are working on this, but there is no set
|
||||
date yet. The current approach is using the Wine Library to implement
|
||||
it.
|
||||
|
||||
<a name="msft"></a>
|
||||
** Mono and Microsoft
|
||||
@@ -403,7 +362,7 @@ A: There is no high level communication between Ximian and Microsoft
|
||||
Ximian was also invited to participate in the ECMA committee
|
||||
meetings for C# and the CLI.
|
||||
|
||||
Q: Are Microsoft or Corel paying Ximian to do this?
|
||||
Q: Is Microsoft or Corel paying Ximian to do this?
|
||||
|
||||
A: No.
|
||||
|
||||
@@ -442,6 +401,13 @@ A: No. MS Passport is unrelated to running .NET compatible applications
|
||||
produced with the Mono tools. The only thing you will need is a
|
||||
just-in-time compiler (JIT).
|
||||
|
||||
Q: What is a 100% .NET application?
|
||||
|
||||
A: A `100% .NET application' is one that only uses the APIs defined
|
||||
under the System namespace and does not use PInvoke. These
|
||||
applications would in theory run unmodified on Windows, Linux,
|
||||
HP-UX, Solaris, MacOS X and others.
|
||||
|
||||
Q: If Microsoft will release a port of their .NET platform under the
|
||||
`Shared Source' license, why should I bother with anything else?
|
||||
|
||||
@@ -479,6 +445,12 @@ A: No, it will not. Microsoft Office is a Windows application. To
|
||||
learn more about running Windows applications on Intel Unix systems
|
||||
refer to <a href="http://www.winehq.com">the Wine Project</a>.
|
||||
|
||||
Q: Will I be able to compile a Microsoft VB.NET application and execute
|
||||
the resultant MSIL file under MONO on Linux without converting to C#
|
||||
and recompiling?
|
||||
|
||||
A: Once we have a complete VisualBasic runtime, yes.
|
||||
|
||||
Q: Can mono run the WebMatrix?
|
||||
|
||||
A: No. That requires System.Windows.Forms support which is not
|
||||
@@ -529,33 +501,12 @@ A: Mono requires Unicode versions of Win32 APIs to run,
|
||||
Win32 libs. This is achieved by inserting -lunimono before
|
||||
-lkerner32/user32 in the linker's specs file.
|
||||
|
||||
Q: Why support Windows, when you can run the real thing?
|
||||
|
||||
A: There are various reasons:
|
||||
|
||||
<ul>
|
||||
<li> About half the contributors to Mono are Windows developers.
|
||||
They have many different for contributing to the effort, and
|
||||
we find it very important to let those developers run the runtime on Windows without forcing
|
||||
them to use a new operating system.
|
||||
|
||||
<li> Supporting Windows helps us identify the portable portions
|
||||
of Mono from the non-portable versions of it, helping Mono
|
||||
become more portable in the future.
|
||||
|
||||
<li> Mono does not heavily modify the windows registry, update system DLLs,
|
||||
install DLLs to the Windows/System32 path. Another words, I knew Mono would
|
||||
not cause any legacy enterprise applications to stop working - and it
|
||||
hasn't. However, our CIO er is againt it because of the changes that would
|
||||
be made to Windows 2000, such as, affecting security.
|
||||
</ul>
|
||||
|
||||
<a name="compatibility"></a>
|
||||
** Compatibility
|
||||
|
||||
Q: Can Mono run applications developed with the Microsoft.NET framework?
|
||||
Q: Can Mono run applications developed with the Microsoft.NET fraemwork?
|
||||
|
||||
A: Yes, Mono can run applications developed with the Microsoft .NET Framework
|
||||
A: Yes, Mono can run applications developed with the Microsft .NET Framework
|
||||
on Unix. There are a few caveats to keep in mind: Mono has not
|
||||
been completed yet, so a few API calls might be missing; And in
|
||||
some cases the Mono behavior *might* be incorrect.
|
||||
@@ -589,71 +540,6 @@ A: Sometimes they will. But sometimes a .NET application might invoke
|
||||
Win32 API calls, or assume certain patterns that are not correct
|
||||
for cross-platform applications.
|
||||
|
||||
Q: What is a 100% .NET application?
|
||||
|
||||
A: A `100% .NET application' is one that only uses the APIs defined
|
||||
under the System namespace and does not use P/Invoke. These
|
||||
applications would in theory run unmodified on Windows, Linux,
|
||||
HP-UX, Solaris, MacOS X and others.
|
||||
|
||||
Note that this requirement also holds for all assemblies used by the
|
||||
application. If one of them is Windows-specific, then the entire program
|
||||
is not a 100% .NET application.
|
||||
|
||||
Furthermore, a 100% .NET application must not contain non-standard data
|
||||
streams in the assembly. For example, Visual Studio .NET will insert a
|
||||
<tt>#-</tt> stream into assemblies built under the "Debug" target.
|
||||
This stream contains debugging information for use by Visual Studio .NET;
|
||||
however, this stream can not be interpreted by Mono (unless you're willing
|
||||
to donate support).
|
||||
|
||||
Thus, it is recommended that all Visual Studio .NET-compiled code be
|
||||
compiled under the Release target before it is executed under Mono.
|
||||
|
||||
Q: Can I execute my Visual Studio .NET program (Visual Basic .NET, Visual C#,
|
||||
Managed Extensions for C++, etc.) under Mono?
|
||||
|
||||
A: Yes, with some reservations.
|
||||
|
||||
The .NET program must either be a 100% .NET application, or (somehow) have
|
||||
all dependent assemblies available on all desired platforms. (How to do so
|
||||
is outside the bounds of this FAQ.)
|
||||
|
||||
Mono must also have an implementation for the .NET assemblies used. For
|
||||
example the System.EnterpriseServices namespace is part of .NET, but it
|
||||
has not been implemented in Mono. Thus, any applications using this
|
||||
namespace will not run under Mono.
|
||||
|
||||
With regards to languages, C# applications tend to be most portable.
|
||||
|
||||
Visual Basic .NET applications are portable, but Mono's
|
||||
Microsoft.VisualBasic.dll implementation is incomplete. It is recommended
|
||||
to either avoid using this assembly in your own code, only use the
|
||||
portions that Mono has implemented, or to help implement the missing
|
||||
features. Additionally, you can set 'Option Strict On', which
|
||||
eliminates the implicit calls to the unimplemented
|
||||
Microsoft.VisualBasic.CompilerServices.ObjectType class.
|
||||
(Thanks to Jörg Rosenkranz.)
|
||||
|
||||
Managed Extensions for C++ is least likely to operate under Mono. Mono
|
||||
does not support mixed mode assemblies (that is, assemblies containing both
|
||||
managed and unmanaged code, which Managed C++ can produce). You need a
|
||||
fully-managed assembly to run under Mono, and getting the Visual C++ .NET
|
||||
compiler to generate such an executable can be difficult. You need to use
|
||||
only the .NET-framework assemblies, not the C libraries (you can't use
|
||||
<b>printf</b>(3) for example.), and you need to use
|
||||
the linker options <tt>/nodefaultlib /entry:main mscoree.lib</tt> in
|
||||
addition to the <tt>/clr</tt> compiler flag. You can still use certain
|
||||
compiler intrinsic functions (such as <b>memcpy</b>(3)) and the STL.
|
||||
You should also see <a
|
||||
href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vcmex/html/vcgrfconvertingmanagedextensionsforcprojectsfrommixed-modetopureil.asp"
|
||||
>Converting Managed Extensions for C++ Projects from Mixed Mode to Pure
|
||||
Intermediate Language</a> at MSDN.
|
||||
Finally, you can use PEVERIFY.EXE from the .NET SDK to determine if the
|
||||
assembly is fully managed.
|
||||
|
||||
Thanks to Serge Chaban for the linker flags to use.
|
||||
|
||||
<a name="pnpproject"></a>
|
||||
** Mono and Portable.NET
|
||||
|
||||
@@ -760,7 +646,7 @@ Q: What about Soup? Can I use Soup without Mono?
|
||||
A: Soup is a library for GNOME applications to create SOAP servers and
|
||||
SOAP clients, and can be used without Mono. You can browse the
|
||||
source code for soup using <a
|
||||
href="http://cvs.gnome.org/bonsai/">GNOME's Bonsai</a>.
|
||||
href="http://cvs.gnome.org/bonsai">GNOME's Bonsai</a>.
|
||||
|
||||
Q: Can I use CORBA?
|
||||
|
||||
@@ -805,8 +691,10 @@ A: MonoDoc is a graphical documentation browser for the Mono class
|
||||
Q: I am having trouble compiling a new version of Mono from CVS, it
|
||||
complains about my runtime being out of sync.
|
||||
|
||||
A: To upgrade your class libraries and compiler, see the
|
||||
INSTALL.txt in the MCS directory.
|
||||
A: Jonathan Pryor has provided the following answer:
|
||||
|
||||
To upgrade your class libraries and compiler, see the See
|
||||
README.building in the MCS directory.
|
||||
|
||||
The single biggest source of confusion seems to be the "Your
|
||||
runtime is out of sync" messages. Realize that this is *normal*
|
||||
@@ -822,18 +710,6 @@ A: To upgrade your class libraries and compiler, see the
|
||||
Once this is done, you can continue building your entire
|
||||
environment.
|
||||
|
||||
For instance you just need to:
|
||||
1.- Upgrade your Mono runtime (you might better do it with the
|
||||
mono-build.sh script available in the <a
|
||||
href="http://www.go-mono.com">download</a> page.
|
||||
2.- Get the latest mono-lite tarball from the daily snapshots
|
||||
<a href="http://www.go-mono.com/daily/">page</a>, unzip and
|
||||
untar and copy all the dll files to your install path lib
|
||||
directory (typically pointed by the $MONO_PATH variable).
|
||||
Copy all the exe files to the install path bin directory.
|
||||
3.- Then checkout or update your mcs CVS copy. Then follow
|
||||
the steps described in mcs/INSTALL.txt.
|
||||
|
||||
Q: Will it be possible to use the CLI features without using byte codes
|
||||
or the JIT?
|
||||
|
||||
@@ -942,7 +818,7 @@ A: Replace the __stdcall attribute with the STDCALL macro, and include this
|
||||
Q: I want to be able to execute Mono binaries, without having to use the "mono"
|
||||
command. How can I do this?
|
||||
|
||||
A: From Carlos Perelló:
|
||||
A: From Carlos Perelló:
|
||||
|
||||
<i>I think that the best solution is the binfmt feature with the
|
||||
wrapper that exists with Debian packages at:
|
||||
@@ -1011,7 +887,7 @@ A: Modules developed for Apache 2 are not compatible with Apache 1.3
|
||||
|
||||
Q: Can I run Apache 1 and Apache 2 on the same machine?
|
||||
|
||||
You can always keep a copy of Apache 2 running in parallel with your Apache
|
||||
You can always keep a copy of Apache 2 running in paralell with your Apache
|
||||
1.3 (either different port or using a reverse proxy).
|
||||
|
||||
You can also bind the two servers to different IP addresses on the
|
||||
@@ -1053,13 +929,12 @@ Q: Why don't you use Java? After all, there are many languages that
|
||||
A: You can get very good tools for doing Java development on free
|
||||
systems right now. <a href="http://www.redhat.com">Red Hat</a> has
|
||||
contributed a <a href="http://gcc.gnu.org">GCC</a> <a
|
||||
href="http://gcc.gnu.org/java/">front-end for Java</a> that can take
|
||||
href="http://gcc.gnu.org/java">front-end for Java</a> that can take
|
||||
Java sources or Java byte codes and generate native executables; <a
|
||||
href="http://www.google.com/search?q=transvirtual">Transvirtual</a>
|
||||
implemented
|
||||
href="http://www.transvirtual.com">Transvirtual</a> has implemented
|
||||
<a href="http://www.kaffe.org">Kaffe</a> a JIT engine for Java;
|
||||
Intel also has a Java VM called <a
|
||||
href="http://www.intel.com/research/mrl/orp/">ORP</a>.
|
||||
href="http://www.intel.com/research/mrl/orp">ORP</a>.
|
||||
|
||||
The JVM is not designed to be a general purpose virtual machine.
|
||||
The Common Intermediate Language (CIL), on the other hand, is
|
||||
@@ -1078,11 +953,37 @@ A: Yes, Java could target the CLI, Microsoft's J# compiler does that.
|
||||
|
||||
Q: Is it possible to write a JVM byte code to CIL converter?
|
||||
|
||||
A: Yes, this is what <a href="http://weblog.ikvm.net">IKVM</a> does.
|
||||
A: Yes, it is possible. Here are a few starting point:
|
||||
|
||||
<ul>
|
||||
* A byte code representation is really a flattened forest of
|
||||
trees. Look at the Mono JIT engine to see how we compute
|
||||
the basic blocks (this is used to figure out the "trees").
|
||||
|
||||
The forest is just an array of trees.
|
||||
|
||||
Indeed, run the JIT engine with -d (mono -d prog.exe) and
|
||||
you will see how these trees look like.
|
||||
|
||||
You will have to do something similar for Java.
|
||||
|
||||
* Each "forest of trees" has a meaning. This meaning can now
|
||||
be translated into the equivalent "meaning" in CLR-land.
|
||||
</ul>
|
||||
|
||||
See also the <a href="http://weblog.ikvm.net/">IKVM project</a>
|
||||
|
||||
Q: Could mono become a hybrid CIL/java platform?
|
||||
|
||||
A: This can be obtained easily with IKVM.
|
||||
A: No. It is quite far from the philosophy of the project. The idea of Mono
|
||||
is, to have only _one_ VM, on which all can run. And if there existing a
|
||||
binary-converter from Java-.class to IL and if there existing something
|
||||
like J-Sharp on Mono, you can write programs in Java, which than can run
|
||||
on Mono. You do not need two bindings (like your example: GTK-Sharp _and_
|
||||
Java-Gnome). You need only _one_ of it (GTK-Sharp). Thats the idea of Mono.
|
||||
An other point is, that there are no people, who use Open Source-JVMs. They
|
||||
all prefer Suns original. But for Unix there don't exist a .NET-Framework.
|
||||
So it is possible, that in the future Mono is the standard .NET for Unixes.
|
||||
|
||||
Q: Do you plan to implement a Javascript compiler?
|
||||
|
||||
@@ -1123,7 +1024,7 @@ Q: Do you plan to Embrace and Extend .NET?
|
||||
|
||||
A: Embracing a good technology is good. Extending technologies in
|
||||
incompatible ways is bad for the users, so we do not plan on
|
||||
making incompatible changes to the technologies.
|
||||
extending the technologies.
|
||||
|
||||
If you have innovative ideas, and want to create new classes, we
|
||||
encourage you to make those classes operate correctly well in both
|
||||
@@ -1133,11 +1034,6 @@ A: Embracing a good technology is good. Extending technologies in
|
||||
developed either by members of the Mono community, or other
|
||||
groups.
|
||||
|
||||
In some cases, we have found the bits from Microsoft to be
|
||||
incomplete, but we avoid breaking the API, instead we expose the
|
||||
missing functionality in new assemblies (See Mono.Security and
|
||||
System.Security).
|
||||
|
||||
Q: Is there any way I can develop the class libraries using Linux yet?
|
||||
|
||||
A: Yes. Mono has been selfhosting since March 2002.
|
||||
@@ -1169,14 +1065,11 @@ A: Our main intention at Ximian is to be able to develop GNOME
|
||||
|
||||
Q: What operating systems/CPUs do you support
|
||||
|
||||
A: Mono currently runs on Linux, Windows, Solaris, FreeBSD, HP-UX and
|
||||
MacOS X.
|
||||
|
||||
A: Mono currently runs on Linux, Windows, Solaris and FreeBSD.
|
||||
There is a JIT engine available for x86 processors that can
|
||||
generate code and optimizations tailored for a particular CPU.
|
||||
|
||||
Interpreters exist for the SPARC v8, SPARC v9, Itanium, HP-PA,
|
||||
PowerPC and StrongARM CPUs.
|
||||
Interpreters exist for the SPARC, PowerPC and StrongARM CPUs.
|
||||
|
||||
Q: Does Mono run on Windows?
|
||||
|
||||
@@ -1199,6 +1092,17 @@ A: It will depend only if you are using a particular assembly (for
|
||||
in Mono for implementing a `Hello World Enterprise P2P Web
|
||||
Service', you will not need any GNOME components.
|
||||
|
||||
Q: Is anyone working on porting Mono to IA-64?
|
||||
|
||||
A: Nobody is working on such port.
|
||||
|
||||
Q: If I were about to start a Mono port to IA-64,would the same lburg code
|
||||
generator work for IA-64 also? or anything else need to be used for code
|
||||
generation(as the processor architecture is totally different from IA32)
|
||||
|
||||
A: The lburg approach can be use for any processor architecture. But you might
|
||||
think in another better approach.
|
||||
|
||||
Q: Do you plan to port Rhino to C#?.
|
||||
|
||||
A: Eto Demerzal has started a Rhino port to C#.
|
||||
@@ -1218,17 +1122,34 @@ Q: What projects will you reuse or build upon?
|
||||
A: We want to get Mono in the hands of programmers soon. We are
|
||||
interested in reusing existing open source software.
|
||||
|
||||
Q: What about Intel's research JIT framework, ORP?
|
||||
|
||||
A: At this time, we are investigating whether we can use elements of
|
||||
ORP for Mono. ORP is a research JIT engine that has a clearly
|
||||
defined API that splits the JIT from the GC system and the actual
|
||||
byte code implementation.
|
||||
|
||||
We are using some pieces of ORP (Their code generation interface)
|
||||
and we use it as a source of inspiration for optimizations. Paolo
|
||||
and Dietmar consider ORP as being one of the best JIT engines out
|
||||
there (and their research work and papers are very useful if you are
|
||||
interested in JIT technology).
|
||||
|
||||
Q: What about using GNU Lightning?
|
||||
|
||||
A: We are not using GNU Lightning. Our JIT is using an instruction
|
||||
selector based on tree-pattern matching, and a code generation
|
||||
interface that is very tied to the current architecture.
|
||||
|
||||
Q: Will I be able to use Microsoft SQL Server 2000 or will I need to switch
|
||||
to a specific Open Source Database. Will I need to recode?
|
||||
|
||||
A: There is no need to rewrite your code as long as you keep using
|
||||
Microsoft SQL Server. If you want to use an open source database,
|
||||
you might need to make changes to your code.
|
||||
A: There should not be any need to recode.
|
||||
|
||||
Q: What do I need to watch out for when programming in VB.NET so that I'm
|
||||
sure to be able to run those apps on Linux?
|
||||
|
||||
A: Not making any P/Invoke or DLL calls should and not using anything in
|
||||
A: Not making any PInvoke or DLL calls should and not using anything in
|
||||
the Microsoft.* namespaces should suffice. Also do not use any
|
||||
Methods/Classes marked as "This type/method supports the .NET Framework
|
||||
infrastructure and is not intended to be used directly from your code."
|
||||
@@ -1237,7 +1158,7 @@ A: Not making any P/Invoke or DLL calls should and not using anything in
|
||||
Q: Will built-in reporting be supported for crystal reports? This is a
|
||||
heavily used part of our system.
|
||||
|
||||
A: . Crystal Reports are propriety. Someone may try to emulate
|
||||
A: Probably not. Crystal Reports are propriety. Someone may try to emulate
|
||||
the behavior, but no-one has yet volunteered.
|
||||
|
||||
Q: Who about writing to the registry? As I understand it, Linux does not have
|
||||
@@ -1253,22 +1174,19 @@ A: Try to avoid it. Although there would be a emulation for registry in
|
||||
Q: System.Data.SqlClient with FreeTDS, will you port parts of these to C# and
|
||||
use them?
|
||||
|
||||
A: This has been done.
|
||||
A: if their license is compatible with mono's, yes, we'd think about porting
|
||||
them. If not, we'll continue with the plan of using FreeTDS.
|
||||
|
||||
<a name="gcc"></a>
|
||||
** Mono and GCC
|
||||
|
||||
Q: Are you working on a GCC front-end to C#? A GCC back-end that will
|
||||
generate CIL images?
|
||||
generate CIL images? What about making a front-end to GCC that
|
||||
takes CIL images and generates native code?
|
||||
|
||||
A: We would love to see a GCC modification that would generate CIL
|
||||
images, but there is nothing at this point.
|
||||
|
||||
Q: What about making a front-end to GCC that takes CIL images and
|
||||
generates native code?
|
||||
|
||||
A: There is no active work on this area, but Mono already provides
|
||||
pre-compilation services (Ahead-of-Time compilation).
|
||||
A: We are currently seeking volunteers for those projects.
|
||||
Visit the <a href="contributing.html">contributing</a> section if
|
||||
you are interested.
|
||||
|
||||
Q: But would this work around the GPL in the GCC compiler and allow
|
||||
people to work on non-free front-ends?
|
||||
@@ -1276,6 +1194,12 @@ Q: But would this work around the GPL in the GCC compiler and allow
|
||||
A: People can already do this by targeting the JVM byte codes (there
|
||||
are about 130 compilers for various languages that target the JVM).
|
||||
|
||||
Q: Why are you writing a JIT engine instead of a front-end to GCC?
|
||||
|
||||
A: We want the JIT engine and runtime engine because they will be able
|
||||
to execute CIL executables generated on Windows, and so no recompilation
|
||||
will be necessary.
|
||||
|
||||
<a name="performance"></a>
|
||||
** Performance
|
||||
|
||||
@@ -1284,9 +1208,11 @@ Q: How fast will Mono be?
|
||||
A: We can not predict the future, but a conservative estimate is that
|
||||
it would be at least `as fast as other JIT engines'.
|
||||
|
||||
Mono's JIT engine has been recently re-architected, and it provides
|
||||
many new features, and layers suitable for optimization. It is
|
||||
relatively easy to add new optimizations to Mono.
|
||||
We would like to ship various JIT engines with Mono, just like
|
||||
Microsoft has done with their .NET development platform. We could
|
||||
provide a faster, JIT for fast load times but lower performance,
|
||||
and an and an optimizing JIT that would be slower at generating
|
||||
code but produce more optimal output.
|
||||
|
||||
The CIL has some advantages over the Java byte code: it is really
|
||||
an intermediate representation and there are a number of
|
||||
@@ -1380,7 +1306,7 @@ A: First some background information.
|
||||
|
||||
The Mono strategy for dealing with these technologies is as
|
||||
follows: (1) work around the patent by using a different
|
||||
implementation technique that retains the API, but changes the
|
||||
implementation techinque that retains the API, but changes the
|
||||
mechanism; if that is not possible, we would (2) remove the pieces
|
||||
of code that were covered by those patents, and also (3) find prior
|
||||
art that would render the patent useless.
|
||||
@@ -1397,17 +1323,6 @@ A: First some background information.
|
||||
components, and things that we have developed (like Gtk#) or Apache
|
||||
integration.
|
||||
|
||||
Q: Is Mono only an implementation of the .NET Framework?
|
||||
|
||||
A: Mono implements both the .NET Framework, as well as plenty of class
|
||||
libraries that are either Unix specific, <a
|
||||
href="http://www.gnome.org">Gnome</a> specific, or that are not
|
||||
part of the .NET Framework but people find useful.
|
||||
|
||||
The following map shows the relationship between the components:
|
||||
|
||||
<img src="http://primates.ximian.com/~miguel/tmp/map.png">
|
||||
|
||||
<a name="etc"></a>
|
||||
** Miscellaneous Questions
|
||||
|
||||
@@ -1436,12 +1351,17 @@ Q: Will Ximian offer certifications on Mono or related technologies?.
|
||||
|
||||
A: It's possible. But there is no plan about this. So the short answer is no.
|
||||
|
||||
Q: Are there any Boehm's GC binaries?
|
||||
|
||||
A: Yes. You can find RPMs <a href="http://java.thn.htu.se/~toor/">here</a>, though
|
||||
if your distribution provides the correct packages, you should use those.
|
||||
The suggested version of the Boehm GC is 6.1.
|
||||
|
||||
Q: How can I report a bug?
|
||||
|
||||
A: The best thing is to track down the bug and provide a simple test
|
||||
to reproduce the bug. You can then add the bug to our bug tracking
|
||||
system. You can use our <a href="bugs.html">Bug Form</a> to enter
|
||||
bugs for the appropriate component.
|
||||
A: The best thing is to track down the bug and provide a simple test to
|
||||
reproduce the bug. You can then add the bug to the
|
||||
<a href="http://bugzilla.ximian.com/enter_bug.cgi">bugtracking system</a>.
|
||||
|
||||
Please provide information about what version of mono you're using
|
||||
and any relevant details to be able to reproduce the bug. Note that
|
||||
@@ -1492,18 +1412,13 @@ Q: Is it possible to use Visual C++ with Mono?.
|
||||
A: It's possible to run VC++ generated apps under Mono, but we do not
|
||||
provide a Manager C++ compiler ourselves.
|
||||
|
||||
Q: Does Mono support generics?.
|
||||
|
||||
A: Mono doesn't support generics currently but a lot of work is being
|
||||
done towards it.
|
||||
|
||||
<a name="problems"></a>
|
||||
** Mono Common Problems
|
||||
|
||||
If you are having problems compiling or running Mono software
|
||||
or if you think that you found a bug, etc. Please visit the
|
||||
<a href="http://monoevo.sf.net/mono-common-problems.html">Mono Common Problems</a> document and try there.
|
||||
<a href="http://geneura.ugr.es/~jaime/deploy/mono-common-problems.html">Mono Common Problems</a> document and try there.
|
||||
|
||||
** Credits
|
||||
|
||||
The FAQ contains material contributed by Miguel de Icaza, Jaime Anguiano, Lluis Sánchez.
|
||||
The FAQ contains material contributed by Miguel de Icaza, Jaime Anguiano, Lluis Sánchez.
|
||||
+80
-37
@@ -19,18 +19,19 @@
|
||||
<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>
|
||||
and easy to
|
||||
create one <a href="http://bugzilla.ximian.com/createaccount.cgi">here</a>.</li>
|
||||
|
||||
</ul>
|
||||
|
||||
** Current Status
|
||||
|
||||
<ul>
|
||||
<li>Current stable version: 1.0</li>
|
||||
|
||||
<li>Current developement version: 1.5</li>
|
||||
|
||||
<li>The new data provider/driver is written in C# and provides a high-performance native
|
||||
<ul>
|
||||
<li>Currently, it is able to connect to Firebird and Interbase databases
|
||||
and execute commands</li>
|
||||
|
||||
<li>The new data
|
||||
provider/driver is written in C# and provides a high-performance native
|
||||
implementation of the GDS32/API functions. This means that .Net developers
|
||||
will be able to access Firebird databases without the need of Firebird
|
||||
client install</li>
|
||||
@@ -38,31 +39,74 @@
|
||||
<li>In support of the new module, a new mailing list
|
||||
<a href="http://lists.sourceforge.net/lists/listinfo/firebird-net-provider">firebird-net-provider</a> has
|
||||
been created. Please use this list for any
|
||||
questions that you may have about the provider</li>
|
||||
questions that you may have about the provider</li>
|
||||
|
||||
<li>Stuff that works:
|
||||
<ul>
|
||||
<li>Currently implemented classes:
|
||||
<ul>
|
||||
<li>Connection and Connection Pooling</li>
|
||||
<li>Command</li>
|
||||
<li>Transaction</li>
|
||||
<li>CommandBuilder</li>
|
||||
<li>DataAdapter</li>
|
||||
<li>DataReader</li>
|
||||
<li>Error</li>
|
||||
<li>ErrorCollection</li>
|
||||
<li>Exception</li>
|
||||
<li>Parameter</li>
|
||||
<li>ParameterCollection</li>
|
||||
<li>Transaction</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
|
||||
** New features & enhancements in 1.5 version
|
||||
|
||||
** Action Plan
|
||||
|
||||
<ul>
|
||||
<li>Better fit to ADO.NET</li>
|
||||
|
||||
<li>New GDS implementation</li>
|
||||
|
||||
<li>Implicit transaction support</li>
|
||||
|
||||
<li>Array datatype support</li>
|
||||
|
||||
<li>Firebird services API support</li>
|
||||
|
||||
<li>Firebird events API support</li>
|
||||
|
||||
<li>Stored procedure calls using Sql Server style</li>
|
||||
|
||||
<li>Support for retrieve database schema information ( FbConnection.GetDbSchema )</li>
|
||||
|
||||
<li>Improved Commandbuilder implementation</li>
|
||||
</ul>
|
||||
|
||||
<li>Bug fixing</li>
|
||||
<li>Improving API reference documentation</li>
|
||||
<li>Full testing with Firebird 1.5</li>
|
||||
<li>Test with Mono ( http://www.go-mono.com )
|
||||
<ul>
|
||||
<li>Status : Started</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
<li>Support for array datatype
|
||||
<ul>
|
||||
<li>Status : Started</li>
|
||||
<li>Comments: See Interbase API reference documentation</li>
|
||||
<li>Add new file FbArray.cs for array fields management</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
<li>Support for Stored Procs calls that have returns values
|
||||
<ul>
|
||||
<li>Status : Pending.</li>
|
||||
<li>Comments: Modify the isc_dsql_prepare method of GDS implementation for
|
||||
allow to return the output parameters.</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
<li>Implementation of FbClientPermission and FbClientPermissionAttribute
|
||||
<ul>
|
||||
<li>Status : Pending</li>
|
||||
<li>Comments: See if these are really needed for Firebird</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
<li>Improve Logger implementation
|
||||
<ul>
|
||||
<li>Status: Pending</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
|
||||
** Testing
|
||||
|
||||
<ul>
|
||||
@@ -95,13 +139,12 @@
|
||||
{
|
||||
public static void Main(string[] args)
|
||||
{
|
||||
string connectionString =
|
||||
"Database=C:\\PROGRAM FILES\\FIREBIRD\\EXAMPLES\\EMPLOYEE.GDB;" +
|
||||
"User=SYSDBA;" +
|
||||
"Password=masterkey;" +
|
||||
"Dialect=3;" +
|
||||
"Server=localhost";
|
||||
|
||||
string connectionString =
|
||||
"Database=C:\\PROGRAM FILES\\FIREBIRD\\EXAMPLES\\EMPLOYEE.GDB;" +
|
||||
"User=SYSDBA;" +
|
||||
"Password=masterkey;" +
|
||||
"Dialect=3;" +
|
||||
"Server=localhost";
|
||||
IDbConnection dbcon = new FbConnection(connectionString);
|
||||
dbcon.Open();
|
||||
IDbCommand dbcmd = dbcon.CreateCommand();
|
||||
@@ -109,7 +152,7 @@
|
||||
dbcmd.CommandText = sql;
|
||||
IDataReader reader = dbcmd.ExecuteReader();
|
||||
while(reader.Read()) {
|
||||
object dataValue = reader.GetValue(0);
|
||||
object dataValue = myReader.GetValue(0);
|
||||
string sValue = dataValue.ToString();
|
||||
Console.WriteLine("Value: " + sValue);
|
||||
}
|
||||
|
||||
@@ -1,72 +0,0 @@
|
||||
* Novell Forge
|
||||
|
||||
Novell Forge (<a
|
||||
href="http://forge.novell.com/">http://forge.novell.com/</a>)
|
||||
is a website managed by Novell to promote the development of
|
||||
open source applications and solutions. Novell Forge features
|
||||
communities, akin to foundries on SourceForge.net, which exist
|
||||
for the purpose of facilitating collaboration and information
|
||||
exchange about certain technologies or solutions. At Miguel's
|
||||
request, we have created a Mono community on Novell Forge that
|
||||
is administered by Miguel. This community, located at
|
||||
http://forge.novell.com/modules/xfmod/community/?monocomm,
|
||||
provides a resource for interaction and collaboration on Mono
|
||||
and associated solutions. Each community has the ability to
|
||||
provide forums, mailing lists, FAQs, news, documentation,
|
||||
surveys, sample code, and links to related applications. The
|
||||
Mono community has been created for anyone interested in Mono
|
||||
to use, and the exact set of features offered at the community
|
||||
is determined by Miguel.
|
||||
|
||||
Any individual or group that wishes to provide Mono-based solutions in
|
||||
an open source fashion is encouraged to host their solution on the
|
||||
Novell Forge website, free of charge. Once the project is hosted on
|
||||
Novell Forge, you can send Miguel an e-mail requesting that your project
|
||||
be associated with the Mono project. This promotes a symbiotic
|
||||
relationship where the growth of Mono applications helps to improve
|
||||
Mono, and the growth of Mono likewise helps to increase the visibility
|
||||
and usefulness of your applications.
|
||||
|
||||
* Creating an Account
|
||||
|
||||
A Novell Forge account is required in order to create a project on
|
||||
Novell Forge as well as for certain levels of participation within a
|
||||
community like the Mono community. In order to create an account, do
|
||||
the following:
|
||||
|
||||
<ul>
|
||||
|
||||
<li>Go to http://forge.novell.com/ and click on the "Register" link.
|
||||
|
||||
<li>You will be redirected to the Novell Login page. This one resource
|
||||
is used by all of Novell's websites that require authentication, so if
|
||||
you already have a Novell login you may use that login here. Otherwise,
|
||||
simply create a login account.
|
||||
|
||||
<li>You will be redirected back to the Novell Forge page. Click on the
|
||||
"create my Novell Forge account" link, near the top left of the page.
|
||||
|
||||
<li>A form should be filled in with the correct information for you.
|
||||
If you like, choose an avatar and then submit the form.
|
||||
|
||||
<li>Confirm the creation of your account.
|
||||
</ul>
|
||||
|
||||
|
||||
You should be good to go at this point. Now, to create a project,
|
||||
simply choose the "Start New Project" link from the left menu and follow
|
||||
the steps.
|
||||
|
||||
Novell Forge offers a limited set of context-sensitive help links and a
|
||||
full help section. If you have trouble, go to the help section at
|
||||
http://forge.novell.com/modules/xfmod/help/about.php.
|
||||
|
||||
|
||||
* Important Links:
|
||||
|
||||
Novell Forge - <a href="http://forge.novell.com/">http://forge.novell.com/</a>
|
||||
|
||||
Mono Community - <a href="http://forge.novell.com/modules/xfmod/community/?monocomm">http://forge.novell.com/modules/xfmod/community/?monocomm</a>
|
||||
|
||||
Novell Forge Help - <a href="http://forge.novell.com/modules/xfmod/help/about.php">http://forge.novell.com/modules/xfmod/help/about.php</a>
|
||||
|
||||
+6
-1
@@ -21,7 +21,7 @@
|
||||
** Where to learn more.
|
||||
|
||||
Visit the official site for the <a href="http://gtk-sharp.sourceforge.net">Gtk# Project</a>.
|
||||
The <a href="http://www.go-mono.org/faq.html">Mono FAQ</a> has some useful
|
||||
The <a href="http://www.go-mono.org/faq">Mono FAQ</a> has some useful
|
||||
information too.
|
||||
|
||||
** GTK# On Linux
|
||||
@@ -75,6 +75,11 @@ following:
|
||||
<li>Microsoft .NET Framework at
|
||||
<a href="http://msdn.microsoft.com/downloads/default.asp?url=/downloads/sample.asp?url=/msdn-files/027/000/976/msdncompositedoc.xml&frame=true">here</a> </li>
|
||||
|
||||
<p>If you are running Windows 95/98/ME, then you will need Unicode support.
|
||||
Look in
|
||||
mono-list archives for information about how to get
|
||||
Mono to work on Windows 9x.
|
||||
<a href="http://lists.ximian.com/archives/public/mono-list/2002-December/004158.html">here</a>
|
||||
|
||||
<p>Environment Variables to set:
|
||||
<ul>
|
||||
|
||||
+2
-2
@@ -49,14 +49,14 @@ In order to test.
|
||||
<li>Have working mono and mcs setup</li>
|
||||
|
||||
<li>Have access to an IBM DB2 database. If you do not have access, download the
|
||||
<a href="http://www-306.ibm.com/software/data/db2/">IBM DB2</a> software. There
|
||||
<a href="http://www-3.ibm.com/software/data/db2/">IBM DB2</a> software. There
|
||||
are versions for Windows, Linux, AIX, and Sun Solaris.</li>
|
||||
|
||||
<li>Make sure the assembly Mono.Data.DB2Client.dll was built and installed
|
||||
where the other class libraries are installed.</li>
|
||||
|
||||
<li>If you do not have the source to mcs, get the source from
|
||||
<a href="http://www.go-mono.com/download.html">here</a></li>
|
||||
<a href="http://www.go-mono.com/download">here</a></li>
|
||||
|
||||
<li>Has a ConnectionString format like ODBC</li>
|
||||
|
||||
|
||||
@@ -15,13 +15,25 @@
|
||||
<a name="runtime">
|
||||
** Runtime
|
||||
|
||||
We need a verifier that can be run on an executable (assembly)
|
||||
and tells whether the metadata for the executable is correct
|
||||
or not. It should report any anomalies.
|
||||
|
||||
For a list of anomalies in assemblies, check the various assertions
|
||||
that are described on the ECMA documentation.
|
||||
|
||||
This will help test our generated executables and can be also
|
||||
used as an external verifier.
|
||||
|
||||
<a name="classes">
|
||||
** Classes
|
||||
|
||||
<ul>
|
||||
TODO=jxta,The JXTA Peer to Peer foundation
|
||||
* Implement a JXTA protocol implementation:
|
||||
<a href="http://www.jxta.org">http://www.jxta.org</a>
|
||||
|
||||
TODO=camel,Mail API
|
||||
* Implement a Mail API, similar to Camel or JavaMail (Camel has
|
||||
significant architecture features that are required on a real
|
||||
mailer).
|
||||
@@ -33,6 +45,7 @@
|
||||
Such an implementation could be used both with
|
||||
Microsoft .NET and Mono.
|
||||
|
||||
TODO=multimedia
|
||||
* Interfacing to Multimedia systems. You might want
|
||||
to look into the Quicktime API. I know <a
|
||||
href="mailto:[email protected]">Vladimir</a> has
|
||||
@@ -45,10 +58,23 @@
|
||||
|
||||
This list of projects ideas is outdated
|
||||
|
||||
TODO=guavac,Java compiler for .NET
|
||||
* You could take one of the existing Java compilers
|
||||
(Guavac comes to mind as it is so nice) and modify
|
||||
it to generate .NET code rather than JVM byte
|
||||
codes.
|
||||
|
||||
This should be a pretty straightforward task.
|
||||
Guavac has the advantage of being written in C++ and
|
||||
it could be compiled with the Microsoft Managed C++
|
||||
compiler and produce a .NET executable with it.
|
||||
|
||||
TODO=Bonobo,Bonobo for Mono
|
||||
* Once <a href="http://remoting-corba.sourceforge.net/">CORBA</a> is done, implement the Bonobo interfaces
|
||||
to allow people to use Bonobo components in Mono and
|
||||
Mono components with Bonobo. The best of both worlds!
|
||||
|
||||
TODO=moniker,Object Naming System with Monikers
|
||||
* A naming space for Mono. An object naming space is
|
||||
a very powerful tool. Bonobo implements a moniker
|
||||
system that is more powerful than the original
|
||||
|
||||
+1
-29
@@ -13,34 +13,6 @@
|
||||
Notice that the program will need to be compiled with the -g
|
||||
flag and that running with --debug will slow down the execution.
|
||||
|
||||
* Debugging with GDB
|
||||
|
||||
If you use GDB to debug your mono process, you can use the function
|
||||
print_method_from_ip(void *address) to obtain the name of a method
|
||||
given an address.
|
||||
|
||||
For example:
|
||||
|
||||
<pre>
|
||||
(gdb) where
|
||||
#0 ves_icall_System_String_GetHashCode (me=0x80795d0) at string-icalls.c:861
|
||||
#1 0x0817f490 in ?? ()
|
||||
#2 0x0817f42a in ?? ()
|
||||
#3 0x0817f266 in ?? ()
|
||||
#4 0x0817f1a5 in ?? ()
|
||||
</pre>
|
||||
|
||||
You can now use:
|
||||
|
||||
<pre>
|
||||
(gdb) p print_method_from_ip (0x0817f490)
|
||||
IP 0x817f490 at offset 0x28 of method (wrapper managed-to-native) System.String:GetHashCode () (0x817f468 0x817f4a4)
|
||||
$1 = void
|
||||
(gdb) p print_method_from_ip (0x0817f42a)
|
||||
IP 0x817f42a at offset 0x52 of method System.Collections.Hashtable:GetHash (object) (0x817f3d8 0x817f43b)
|
||||
$2 = void
|
||||
</pre>
|
||||
|
||||
* Mono Debugger
|
||||
|
||||
The Mono debugger is written in C# and can debug both managed
|
||||
@@ -66,4 +38,4 @@ $2 = void
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
+12
-13
@@ -34,7 +34,7 @@
|
||||
* <a href="#python">Python</a>
|
||||
</ul>
|
||||
|
||||
<a name="Java"></a>
|
||||
<a name="Java">
|
||||
** Java
|
||||
|
||||
There is a very interesting project to make a JavaVM for .NET
|
||||
@@ -78,6 +78,9 @@
|
||||
Examples:
|
||||
<a href="http://www.oberon.ethz.ch/oberon.net/examples/">http://www.oberon.ethz.ch/oberon.net/examples/</a>
|
||||
|
||||
|
||||
<a href="http://www.superin.formativ.net/mono/oberon/oberon.zip">http://www.superin.formativ.net/mono/oberon/oberon.zip</a>
|
||||
|
||||
<a name="ComponentPascal">
|
||||
** Component Pascal
|
||||
|
||||
@@ -90,8 +93,9 @@
|
||||
<a name="Forth">
|
||||
** Delta Forth
|
||||
|
||||
The Delta Forth.NET project: <a href="http://www.dataman.ro/dforth">Home
|
||||
Page</a> and <a href="http://www.dataman.ro/dforth">more
|
||||
The Delta Forth.NET project: <a
|
||||
href="www.dataman.ro/dforth">Home
|
||||
Page</a> and <a href="http://www.dataman.ro/dforth/index.html">more
|
||||
details here</a>.
|
||||
|
||||
|
||||
@@ -101,15 +105,17 @@
|
||||
A subset of Scheme language called <a
|
||||
href="http://radio.weblogs.com/0101156/stories/2002/03/19/tachy.html">Tachy</a>
|
||||
|
||||
<a name="Python"></a>
|
||||
<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>.
|
||||
href="http://www.zope.org/Members/Brian/PythonNet/index_html">here</a>.
|
||||
An FAQ document is available <a
|
||||
href="http://www.zope.org/Members/Brian/PythonNet/FAQ.html">here</a>.
|
||||
|
||||
<a name="dotlisp"></a>
|
||||
<a name="dotlisp">
|
||||
** dotLisp
|
||||
|
||||
DotLisp is available from: <a
|
||||
@@ -143,13 +149,6 @@
|
||||
LCC is not an open source compiler, but it is free as long as you
|
||||
do not profit from selling it.
|
||||
|
||||
<a name="ada"></a>
|
||||
* ADA
|
||||
|
||||
A# is an ADA compiler for the CIL platform, it can be downloaded from:
|
||||
<a
|
||||
href="http://www.usafa.af.mil/dfcs/bios/mcc_html/a_sharp.html">http://www.usafa.af.mil/dfcs/bios/mcc_html/a_sharp.html</a>
|
||||
|
||||
<a name="Java">
|
||||
* Java
|
||||
|
||||
|
||||
+1
-10
@@ -126,15 +126,6 @@
|
||||
Used to discuss the Gtk bindings for Mono (<a href="http://gtk-sharp.sf.net">Gtk#</a>).
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<b><a
|
||||
href="http://lists.ximian.com/mailman/listinfo/mono-vb">mono-vb</a></b>
|
||||
</td>
|
||||
<td>
|
||||
Mono's implementation of Visual Basic.NET.
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
Other mailing lists of interest:
|
||||
@@ -159,7 +150,7 @@
|
||||
|
||||
<table>
|
||||
<tr>
|
||||
<td><a href="http://www.google.com/search"><img src="images/Logo_40wht.gif" border="0" alt="Google" align="middle"></a></td>
|
||||
<td><a href="http://www.google.com/search"><img src="mailing-lists_files/Logo_40wht.gif" border="0" alt="Google" align="middle"></a></td>
|
||||
|
||||
<td>
|
||||
<table>
|
||||
|
||||
@@ -1,91 +0,0 @@
|
||||
<html>
|
||||
<head>
|
||||
<title>Mono 1.0 assemblies</title>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<h1>Assemblies</h1>
|
||||
<pre>
|
||||
Stable:
|
||||
Commons.RelaxNG
|
||||
Cscompmgd
|
||||
Mono.Data
|
||||
Mono.Data.Tds
|
||||
Mono.Posix
|
||||
Mono.Security
|
||||
Mono.Security.Win32
|
||||
System.Web
|
||||
System.Configuration.Install
|
||||
System.Data
|
||||
System.Data.OracleClient
|
||||
System.DirectoryServices
|
||||
System
|
||||
System.Drawing
|
||||
System.Runtime.Remoting
|
||||
System.Security
|
||||
System.Web.Services
|
||||
System.XML
|
||||
|
||||
Unstable:
|
||||
Accessibility
|
||||
Mono.Cairo
|
||||
Mono.CSharp.Debugger
|
||||
Mono.Data.DB2Client
|
||||
Mono.Data.SqlLite
|
||||
Mono.Data.SybaseClient
|
||||
Mono.GetOptions
|
||||
System.Web.Mobile
|
||||
System.Design
|
||||
System.Drawing.Design
|
||||
System.Windows.Forms
|
||||
Formatters.Soap
|
||||
Mono.Data.TdsClient (older Sybase and MS SQL)
|
||||
|
||||
Missing:
|
||||
System.EnterpriseServices
|
||||
System.Management
|
||||
System.Messaging
|
||||
System.ServiceProcess
|
||||
System.Web.RegularExpressions
|
||||
|
||||
Third party assemblies.
|
||||
ByteFX.Data
|
||||
Npgsql
|
||||
PEAPI
|
||||
SharpZipLib.
|
||||
|
||||
Java integration with IKVM.NET
|
||||
|
||||
</pre>
|
||||
|
||||
<h1>Languages</h1>
|
||||
|
||||
<pre>
|
||||
Stable:
|
||||
C#
|
||||
|
||||
Unstable:
|
||||
VB.NET
|
||||
|
||||
Not ready:
|
||||
JScript
|
||||
</pre>
|
||||
|
||||
<h1>Virtual Machine</h1>
|
||||
|
||||
<pre>
|
||||
JIT, 32 bits:
|
||||
PPC
|
||||
x86
|
||||
|
||||
Interpreter, 32 bits:
|
||||
s390
|
||||
HPPA
|
||||
StrongARM
|
||||
SPARC v8
|
||||
|
||||
Interpreter, 64 bits:
|
||||
ia64
|
||||
SPARC v9
|
||||
</body>
|
||||
</html>
|
||||
+13
-28
@@ -59,13 +59,11 @@ else
|
||||
echo "Automake version new enough."
|
||||
fi
|
||||
|
||||
# This causes libgc-not-found problem
|
||||
#
|
||||
## Select the stable version anyway...
|
||||
#if [ ! -z "${AUTO_STABLE}" -o -e /usr/autotool/stable ]; then
|
||||
# export AUTO_STABLE=${AUTO_STABLE:-/usr/autotool/stable}
|
||||
# export AUTO_DEVEL=${AUTO_STABLE}
|
||||
#fi
|
||||
# Select the stable version anyway...
|
||||
if [ ! -z "${AUTO_STABLE}" -o -e /usr/autotool/stable ]; then
|
||||
export AUTO_STABLE=${AUTO_STABLE:-/usr/autotool/stable}
|
||||
export AUTO_DEVEL=${AUTO_STABLE}
|
||||
fi
|
||||
|
||||
# Need to install pkgconfig and set ACLOCAL_FLAGS if there is not a
|
||||
# pkgconfig installed already. Otherwise set PKG_CONFIG_PATH to the
|
||||
@@ -100,15 +98,6 @@ function aclocal_scan () {
|
||||
return 1
|
||||
}
|
||||
|
||||
function install_icuconfig() {
|
||||
if [ ! -f $here/install/bin/icu-config ]; then
|
||||
wget http://www.go-mono.com/archive/icu-config
|
||||
mv icu-config $here/install/bin
|
||||
chmod 755 $here/install/bin/icu-config
|
||||
fi
|
||||
}
|
||||
|
||||
|
||||
function install_package() {
|
||||
zipfile=$1
|
||||
markerfile=$2
|
||||
@@ -134,13 +123,11 @@ else
|
||||
install_pkgconfig=yes
|
||||
fi
|
||||
|
||||
# This causes libgc-not-found problem
|
||||
#
|
||||
## But we still need to use the mingw libs for glib & co
|
||||
#ACLOCAL_FLAGS="-I $here/install/share/aclocal $ACLOCAL_FLAGS"
|
||||
# But we still need to use the mingw libs for glib & co
|
||||
ACLOCAL_FLAGS="-I $here/install/share/aclocal $ACLOCAL_FLAGS"
|
||||
|
||||
#export PATH
|
||||
#export ACLOCAL_FLAGS
|
||||
export PATH
|
||||
export ACLOCAL_FLAGS
|
||||
|
||||
# Grab pkg-config, glib etc
|
||||
if [ ! -d $here/install ]; then
|
||||
@@ -159,9 +146,6 @@ install_package glib-dev-2.0.4-20020703.zip lib/glib-2.0.lib glib-dev
|
||||
install_package libiconv-1.7.zip lib/iconv.dll iconv
|
||||
install_package libintl-0.10.40-20020101.zip lib/libintl-1.dll intl
|
||||
install_package libgc-dev.zip lib/gc.dll gc-dev
|
||||
install_package icu-2.6.1-Win32_msvc7.zip icu/bin/icuuc26.dll icu
|
||||
|
||||
install_icuconfig
|
||||
|
||||
if [ $install_pkgconfig = "no" ]; then
|
||||
echo "Fixing up the pkgconfig paths"
|
||||
@@ -174,9 +158,10 @@ if [ $install_pkgconfig = "no" ]; then
|
||||
fi
|
||||
|
||||
# Needed to find the libgc bits
|
||||
export CFLAGS="-I $here/install/include -I $here/install/icu/include"
|
||||
export LDFLAGS="-L$here/install/lib -L$here/install/icu/lib"
|
||||
export PATH="$here/install/icu/bin:$PATH"
|
||||
CPPFLAGS="$CPPFLAGS -I$here/install/include"
|
||||
LDFLAGS="$LDFLAGS -L$here/install/lib"
|
||||
export CPPFLAGS
|
||||
export LDFLAGS
|
||||
|
||||
# Make sure we build native w32, not cygwin
|
||||
#CC="gcc -mno-cygwin"
|
||||
|
||||
@@ -1,271 +0,0 @@
|
||||
<html>
|
||||
<head><title>Mono Hacking Roadmap</title>
|
||||
<style type="text/css">
|
||||
h1 {
|
||||
color: #efefef;
|
||||
font-size: 18pt;
|
||||
font-family: "Trebuchet MS";
|
||||
border: 0;
|
||||
margin: 0;
|
||||
padding: 1em;
|
||||
background: #666666;
|
||||
}
|
||||
|
||||
h2, h3, h4, h5, h6 {
|
||||
font-family: Verdana,sans-serif;
|
||||
font-weight: bold;
|
||||
margin: 9pt;
|
||||
}
|
||||
|
||||
h2, h3 {
|
||||
font-size: 18px;
|
||||
}
|
||||
|
||||
h2 {
|
||||
padding: 3px;
|
||||
color: #000000;
|
||||
}
|
||||
|
||||
h3 {
|
||||
font-size: 13px;
|
||||
border-bottom: 2px solid #dddddd;
|
||||
}
|
||||
|
||||
h4 {
|
||||
border-bottom: 2px solid #dddddd;
|
||||
}
|
||||
|
||||
body, table {
|
||||
background-color: #ffffff;
|
||||
font-family: Verdana, sans-serif; font-size: 12px;
|
||||
color: black;
|
||||
margin: 0;
|
||||
padding: 0;
|
||||
border: 0;
|
||||
margin-left: 20%;
|
||||
margin-right: 20%;
|
||||
}
|
||||
|
||||
p {
|
||||
margin-left: 2em;
|
||||
margin-right: 2em;
|
||||
}
|
||||
|
||||
ul li {
|
||||
margin-left: 2em;
|
||||
}
|
||||
|
||||
img {
|
||||
border: 0;
|
||||
vertical-align: top;
|
||||
}
|
||||
|
||||
</style>
|
||||
</head>
|
||||
<body>
|
||||
<center>
|
||||
<h1>
|
||||
Mono Hacking Roadmap
|
||||
<br>
|
||||
|
||||
<font size=1>Miguel de Icaza (<a href="mailto:[email protected]">[email protected]</a>)</font>
|
||||
|
||||
</h1>
|
||||
<p>
|
||||
</center>
|
||||
|
||||
<h3>Introductory notes</h3>
|
||||
|
||||
<p>The intention of this document and the <a
|
||||
href="http://www.go-mono.com/mono-roadmap.html">Mono
|
||||
Roadmap</a> is to be a basis for discussion. I want to build
|
||||
on these two documents, and update as we get more insight into
|
||||
the release process and the technologies we want to ship.
|
||||
|
||||
<h3>Background</h3>
|
||||
|
||||
<p>At the 2003 PDC Microsoft introduced many new technologies,
|
||||
which many of us are very excited about. To me, it underlined
|
||||
the importance of having a roadmap for users of Mono
|
||||
technologies. That way they know precisely what to expect
|
||||
from us when. We have been working on Mono for more than two
|
||||
years, and it is important that we release a stable product to
|
||||
the public.
|
||||
|
||||
<p>We have various degrees of maturity and feature
|
||||
completeness in our code base, and I do not believe that we
|
||||
should aim to be full implementation .NET 1.0 or .NET 1.1 in
|
||||
our 1.0 release, that would just push the release at least for
|
||||
another year . The <a
|
||||
href="http://www.go-mono.com/mono-roadmap.html">Mono
|
||||
Roadmap</a> emphasizes this assumption.
|
||||
|
||||
<p>The 1.0 release is critical for the adoption of Mono on the
|
||||
Linux environment, even if it is not as complete as the
|
||||
Framework, lets get something stable, and fun to people to
|
||||
use.
|
||||
|
||||
<h3>Mono 1.0: missing functionality.</h3>
|
||||
|
||||
<p>For the 1.0 release, there are a number of features that we
|
||||
will have to complete, in no particular order:
|
||||
|
||||
<ul>
|
||||
<li>We need to fix corcompare and our cor-compare
|
||||
pages to support both 1.0 and 1.1 API API compares.
|
||||
|
||||
We might want to move this outside of the Mono site,
|
||||
to reduce the complexity of the HTML hackage, and use
|
||||
ASP.NET to implement this. Bonus points if we use
|
||||
Piers' nice dynamic tree to load the CorCompare data
|
||||
dynamically.
|
||||
|
||||
<li>Global Assembly Cache: Needed to support the
|
||||
parallel installation of .NET 1.0 and 1.1 assemblies,
|
||||
and to fix the various Assembly loading routines.
|
||||
|
||||
<li>PowerPC port.
|
||||
|
||||
<li>ECMA profile: We will like take care of this one
|
||||
at Novell.
|
||||
|
||||
<li>Assembly signing: I do not know what is the state
|
||||
of this feature currently in Mono, maybe Sebastien and
|
||||
Zoltan could give us an update here.
|
||||
|
||||
<li>ASP.NET caching: Non-existant at this point, this
|
||||
needs to be implemented.
|
||||
|
||||
<li>Stability of ASP.NET and Mod_Mono. They are both
|
||||
functional, but they fail under load. Much debugging
|
||||
and testing must go into these components. As we use
|
||||
more of it, we have found more little problems surface
|
||||
on it.
|
||||
|
||||
<li>Codebase audit: Duncan did an audit of Corlib, but
|
||||
we must do an audit of all the assemblies that we we
|
||||
are going to ship, just to get an idea of the major
|
||||
areas missing.
|
||||
</ul>
|
||||
|
||||
<p>The team at Novell will focus on these areas. We of course
|
||||
welcomes the contribution of the rest of the Mono team and
|
||||
encourage the developers to focus on 1.0, to have a solid
|
||||
release, and a solid foundation that can lead to 1.2
|
||||
|
||||
<p>We will use Bugzilla milestones to track these issues.
|
||||
|
||||
<h3>Synchronized releases</h3>
|
||||
|
||||
<p>It would be great if we can ship Mono 1.0 with Gtk# 1.0 and
|
||||
a preview of Monodoc with the early documentation.
|
||||
|
||||
<h3>Alpha components.</h3>
|
||||
|
||||
<p>Various Mono developers are working on areas that will not
|
||||
make it into the 1.0 timeframe: JScript, WSE, VB.NET,
|
||||
Windows.Forms, Generics. We should continue to work on
|
||||
those components, as they will come shortly after, and they
|
||||
are probably more fun to develop than stabilizing the core.
|
||||
|
||||
<h3>New components: Whidbey and Longhorn features</h3>
|
||||
|
||||
<p>Everyone is probably very excited about the new features in
|
||||
the Whidbey release of .NET, and most importantly the Longhorn
|
||||
features. I am sure that many of us will not resist the urge
|
||||
to put some of the new assemblies on CVS.
|
||||
|
||||
<p>We will likely add a profile for those of you that want to
|
||||
work on this, and can not wait to get your hands in the code,
|
||||
although keep in mind that your contributions wont reach the
|
||||
general audience until we successfully ship 1.0.
|
||||
|
||||
<p>The things to keep in mind while adding code which is not
|
||||
in .NET 1.0 and .NET 1.1:
|
||||
|
||||
<ul>
|
||||
<li>Make sure you surround new classes and methods
|
||||
with the appropriate define: NET_1_2 for things
|
||||
available on the .NET 1.2 SDK (Whidbey) and NET_3
|
||||
define for things only available on the Longhorn API.
|
||||
We need this so that these methods do not appear on
|
||||
the 1.0 and 1.1 builds.
|
||||
|
||||
<li>If you add generic types or methods, also surround
|
||||
the method with GENERICS for now, since our compiler
|
||||
can not currently build this code yet. This is
|
||||
redundant with the NET_1_2 define but important.
|
||||
|
||||
<li>For every assembly you update, make sure that you
|
||||
also add the relevant AssemblyInfo versioning
|
||||
information. If possible, when you add methods from
|
||||
.NET 1.2 to the build, also update the AssemblyInfo.cs
|
||||
for the library.
|
||||
</ul>
|
||||
|
||||
<p>There are three areas of new hot features:
|
||||
|
||||
<ul>
|
||||
<li>Class library improvements (Whidbey, Mono 1.2
|
||||
time frames).
|
||||
|
||||
<li>Indigo: They will release this in 2005 or 2006 and
|
||||
wont make it into the 2004 Whidbey .NET 1.2 release.
|
||||
|
||||
<li>Avalon: Definitely a Longhorn-bound feature.
|
||||
</ul>
|
||||
|
||||
<p>Most code that will reach the users in the short time frame
|
||||
(next year) will be related to the Whidbey improvements, so I
|
||||
encourage developers to work on those pieces, as they are the
|
||||
ones that will help Mono the most.
|
||||
|
||||
<h3>ASP.NET 2.0 plans</h3>
|
||||
|
||||
<p>Gonzalo will continue to coordinate this effort; At this
|
||||
time ASP.NET 2.0 features will not make it into Mono 1.0.
|
||||
|
||||
<h3>Avalon plans</h3>
|
||||
|
||||
<p>On the surface Avalaon seems like it uses something like
|
||||
GdiPlus/Cairo for rendering. That was my initial feeling, but
|
||||
it turns out that they had to rewrite everything to have a
|
||||
performing rendering engine, and implement some very advanced
|
||||
rendering features that include compositing with video
|
||||
streams, also their brushes seem to be fairly powerful.
|
||||
|
||||
<p>XAML, a new markup language that binds tags to .NET classes
|
||||
was also presented, but this is the least interesting part. A
|
||||
tiny compiler translates the XAML source files into C# code.
|
||||
The whole process is just like Glade, and should be easy to
|
||||
do.
|
||||
|
||||
<p>The really elaborate parts are the rendering engine, and the
|
||||
composition model for widgets. It is a complete new toolkit,
|
||||
and if we want to implement this one, we will have to have a
|
||||
new toolkit on Unix, incompatible with everything else, maybe
|
||||
stressing the importance of working with other open source
|
||||
projects in defining a cross-toolkit theming strategy to
|
||||
address this particular problem.
|
||||
|
||||
<p>A Mini-Avalon is easy to do, but a complete one will
|
||||
require much interaction with other groups: the Cairo folks
|
||||
are probably the most qualified to assist us.
|
||||
|
||||
<h3>Indigo Plans</h3>
|
||||
|
||||
<p>Indigo is still an early product (<a
|
||||
href="http://msdn.microsoft.com/Longhorn/understanding/pillars/Indigo/default.aspx?pull=/library/en-us/dnlong/html/indigofaq1.asp">FAQ</a>),
|
||||
but it could benefit from continued development of our WSE1
|
||||
and WSE2 components, later to bring some of the code to it.
|
||||
|
||||
<p>Again, since people are visibly excited about this
|
||||
technology, we will lay down in the next few days a framework
|
||||
to contribute to it.
|
||||
|
||||
|
||||
<p>
|
||||
<i>Last Updated: Nov 1st, 2003</i>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -1,396 +0,0 @@
|
||||
<html>
|
||||
<head><title>Mono Roadmap</title>
|
||||
<style type="text/css">
|
||||
h1 {
|
||||
color: #efefef;
|
||||
font-size: 18pt;
|
||||
font-family: "Trebuchet MS";
|
||||
border: 0;
|
||||
margin: 0;
|
||||
padding: 1em;
|
||||
background: #666666;
|
||||
}
|
||||
|
||||
h2, h3, h4, h5, h6 {
|
||||
font-family: Verdana,sans-serif;
|
||||
font-weight: bold;
|
||||
margin: 9pt;
|
||||
}
|
||||
|
||||
h2, h3 {
|
||||
font-size: 18px;
|
||||
}
|
||||
|
||||
h2 {
|
||||
padding: 3px;
|
||||
color: #000000;
|
||||
}
|
||||
|
||||
h3 {
|
||||
font-size: 13px;
|
||||
border-bottom: 2px solid #dddddd;
|
||||
}
|
||||
|
||||
h4 {
|
||||
border-bottom: 2px solid #dddddd;
|
||||
}
|
||||
|
||||
body, table {
|
||||
background-color: #ffffff;
|
||||
font-family: Verdana, sans-serif; font-size: 12px;
|
||||
color: black;
|
||||
margin: 0;
|
||||
padding: 0;
|
||||
border: 0;
|
||||
margin-left: 20%;
|
||||
margin-right: 20%;
|
||||
}
|
||||
|
||||
p {
|
||||
margin-left: 2em;
|
||||
margin-right: 2em;
|
||||
}
|
||||
|
||||
ul li {
|
||||
margin-left: 2em;
|
||||
}
|
||||
|
||||
img {
|
||||
border: 0;
|
||||
vertical-align: top;
|
||||
}
|
||||
|
||||
</style>
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<center>
|
||||
<h1>
|
||||
Mono Project Roadmap
|
||||
<br>
|
||||
<font size=1>Miguel de Icaza ([email protected])</font>
|
||||
</h1>
|
||||
<p>
|
||||
</center>
|
||||
|
||||
<i>Last update: Jan 18th, 2004</i>
|
||||
|
||||
<h3>Introduction</h3>
|
||||
|
||||
<p>This document describes the high-level roadmap for <a
|
||||
href="http://www.go-mono.com">Mono</a>.
|
||||
|
||||
<p>The Mono project started in 2001 as an effort to implement
|
||||
the .NET Framework to Unix. To bring both the new programming
|
||||
model based on the Common Language Infrastructure and C# as
|
||||
well as helping people migrate their existing knowledge and
|
||||
applications to Unix. Mono today supports a wide variety of
|
||||
operating systems, CPUs and a large chunk of the functionality
|
||||
available in the .NET Framework.
|
||||
|
||||
<p>At the October 2003 PDC conference a number of new
|
||||
technologies were announced. From the Mono release schedule
|
||||
perspective, we should think about these technologies from
|
||||
their release time standpoint, and the features that must be
|
||||
supported.
|
||||
|
||||
<p>This document outlines the roadmap for the Mono project
|
||||
from my perspective: what we can effectively deliver on the
|
||||
dates outlined. Since Mono is a large open source project,
|
||||
things might change and new features can be incorporated
|
||||
into the plan if external sources devote enough attention to
|
||||
those problems.
|
||||
|
||||
<p>This is the timeline:
|
||||
<p>
|
||||
<center>
|
||||
<img src="roadmap.png">
|
||||
</center>
|
||||
|
||||
<h3>Background</h3>
|
||||
|
||||
<p>So far Microsoft has published two versions of the .NET
|
||||
Framework: 1.0 and 1.1, the later with incremental updates to
|
||||
the changes in 1.0
|
||||
|
||||
<p>The Mono project has been tracking some of the
|
||||
improvements available in those two releases, some of the
|
||||
highlights of our work so far are:
|
||||
|
||||
<ul>
|
||||
<li> Core: mscorlib, System, System.Security and
|
||||
System.XML assemblies.
|
||||
|
||||
<li> ADO.NET: System.Data and various other database
|
||||
providers.
|
||||
|
||||
<li> ASP.NET: WebForms and Web Services are
|
||||
supported. Work on WSE1/WSE2 has also started.
|
||||
|
||||
<li> Compilers: C#, VB.NET and various command line tools
|
||||
that are part of the SDK.
|
||||
|
||||
<li> Open Source, Unix and Gnome specific libraries.
|
||||
</ul>
|
||||
|
||||
<p>Other components like Windows.Forms, Directory.Services,
|
||||
Enterprise Services and JScript are being developed but are not
|
||||
as mature as the other components but are under development by
|
||||
various people.
|
||||
|
||||
<p>Some other smaller and less used components do not have yet
|
||||
a Mono equivalent (System.Management, System.Drawing.Design).
|
||||
|
||||
<h3>Mono release strategy</h3>
|
||||
|
||||
<p>The levels of maturity of Mono fluctuate depending on the
|
||||
development effort we have put into it, and the use we have
|
||||
given to them. For example, the virtual machine and the C#
|
||||
compiler very mature, while less commonly used functionality
|
||||
in Mono like Windows.Forms or VB.NET are still under heavy
|
||||
development.
|
||||
|
||||
<p>Our strategy is to release the mature components as Mono
|
||||
1.0, and have upcoming versions of Mono add extra
|
||||
functionality.
|
||||
|
||||
<h3>Mono 1.0 goals</h3>
|
||||
|
||||
<p>The Mono 1.0 release would include the following
|
||||
components:
|
||||
|
||||
<ul>
|
||||
<li>C# compiler.
|
||||
|
||||
<li>VM, with JIT and pre-compiler.
|
||||
|
||||
<li>IL assembler, disassembler.
|
||||
|
||||
<li>Development and security tools.
|
||||
|
||||
<li>Core libraries: mscorlib, System, System.XML.
|
||||
|
||||
<li>System.Data and Mono database providers.
|
||||
|
||||
<li>System.Web: Web applications platform and Apache
|
||||
integration module.
|
||||
|
||||
<li>System.Web.Services: client and server support.
|
||||
|
||||
<li>System.Drawing.
|
||||
|
||||
<li>System.DirectoryServices
|
||||
|
||||
<li>JIT support: x86 and PPC architectures
|
||||
(interpreter available for other architectures).
|
||||
|
||||
<li>ECMA profiles: special build options to build
|
||||
Mono as an implementation of the various ECMA profiles
|
||||
will be available.
|
||||
|
||||
<li>Java integration through IKVM.
|
||||
|
||||
<li>Embedding interface for the runtime.
|
||||
</ul>
|
||||
|
||||
<p>Packaging:
|
||||
|
||||
<ul>
|
||||
<li>mono: will contain the above features implementing
|
||||
the .NET 1.1 API.
|
||||
|
||||
<li>mono-1.0-compat: Will include a build of the
|
||||
libraries with the .NET 1.0 API, this is a
|
||||
compatibility build for people running .NET 1.0
|
||||
applications.
|
||||
|
||||
<li>mono-unstable: Will contain a snapshot of the
|
||||
other technologies under development for developer's
|
||||
convenience, but will be unsupported at this time.
|
||||
These include the Generics edition of the C#
|
||||
compiler.
|
||||
|
||||
<li>mono-ecma: A build that only includes the ECMA
|
||||
components.
|
||||
</ul>
|
||||
|
||||
<p>Release target: Q2/2004.
|
||||
|
||||
<p>Bug fix releases would be done on a monthly basis.
|
||||
|
||||
<p>For a detailed list, see the <a
|
||||
href="mono-1.0.html">mono-1.0 feature list.</a>
|
||||
|
||||
<h3>Microsoft's Whidbey</h3>
|
||||
|
||||
<p>To understand post 1.0 editions of Mono, it is important to
|
||||
put it into perspective with the Microsoft Whidbey product, to
|
||||
be released in 2004.
|
||||
|
||||
<p>The new features in the Whidbey release of the .NET Framework
|
||||
include:
|
||||
|
||||
<ul>
|
||||
<li><b>Generic types</b><br>
|
||||
These introduce changes to the compiler, runtime and
|
||||
class libraries.
|
||||
|
||||
<li><b>ASP.NET 2</b><br>
|
||||
Many tools to simplify web application development:
|
||||
Master pages, new controls for common operations,
|
||||
personalization and themes.
|
||||
|
||||
<li><b>Remoting</b><br>
|
||||
New security channels and version-resistant remoting
|
||||
(good news in the interop department).
|
||||
|
||||
<li><b>XML</b><br>
|
||||
XQuery debuts on this release as well as an improved
|
||||
XmlDocument system based on XPath: XPathDocument.
|
||||
|
||||
<li><b>Networking</b><br>
|
||||
FTP client, Ssl streams.
|
||||
|
||||
<li><b>Console and Serial ports:</b></br>
|
||||
Console terminal input/output is available as well as
|
||||
serial port handling.
|
||||
|
||||
<li><b>Windows.Forms</b><br>
|
||||
Layout containers finally appeared on Windows.Forms as
|
||||
well as various new controls.
|
||||
|
||||
<li><b>ObjectSpaces</b><br>
|
||||
An API for simpler data-base access.
|
||||
</ul>
|
||||
|
||||
<h3>Mono 1.2</h3>
|
||||
|
||||
<p>The Mono team is developing in parallel some features that
|
||||
wont make it to the 1.0 release in stable form. These will be
|
||||
the foundation for the 1.2 release. The focus of this release
|
||||
is to track the core API for the .NET Framework 1.2, but
|
||||
again, only a subset of the total framework will be
|
||||
available.
|
||||
|
||||
<p>Mostly, Mono 1.2 consists of components that were not
|
||||
stable enough for Mono 1.0, but that would be mature at this
|
||||
point, plus the incorporation of some new features from
|
||||
Whidbey. In addition to the Mono 1.0 components, this release
|
||||
will add:
|
||||
|
||||
<ul>
|
||||
<li>Generic types support: C# compiler, execution
|
||||
system and core class libraries.
|
||||
|
||||
<li>ASP.NET 2.0 improvements.
|
||||
|
||||
<li>Remoting improvements from Whidbey.
|
||||
|
||||
<li>System.XML: simpler improvements from Whidbey,
|
||||
lacking the large additions (XQuery for example).
|
||||
|
||||
<li>Console and Serial ports support.
|
||||
|
||||
<li>New compilers: VB.NET and JScript support.
|
||||
|
||||
<li>WSE1/WSE2 implementations.
|
||||
|
||||
<li>System.Windows.Forms officially debuts with .NET
|
||||
1.0 API; 1.2 API available as an unstable addition.
|
||||
</ul>
|
||||
|
||||
<p>This release will by default provide .NET 1.2 APIs, but
|
||||
compatibility libraries for 1.0 and 1.1 will be distributed in
|
||||
the mono-compat package. The unstable components of Mono will
|
||||
be distributed on the `mono-unstable' package, the libraries
|
||||
in this release will be unsupported.
|
||||
|
||||
<p>Release target: Q4/2004.
|
||||
|
||||
<h3>Mono 1.4</h3>
|
||||
|
||||
<p>A refresh update on the Mono 1.2 release containing the
|
||||
missing components from the previous release and complete any
|
||||
under performing pieces. Updates to System.Xml, ASP.NET and
|
||||
Windows.Forms to match the .NET 1.2 API.
|
||||
|
||||
<p>Release target: Q2/2005.
|
||||
|
||||
<h3>Peer projects</h3>
|
||||
|
||||
<p>Other projects like the debugger, the documentation
|
||||
browser, Java integration through IKVM and Gtk# will remain on
|
||||
their own schedules. This page will be updated to contain
|
||||
that information when it becomes available.
|
||||
|
||||
<h3>Unscheduled activities</h3>
|
||||
|
||||
<p>A missing component of Mono is the Code Access Security
|
||||
(CAS). This functionality is not needed in today's Mono as
|
||||
currently Mono is being used to run fully trusted
|
||||
applications, and we are not using it on embedded scenarios
|
||||
where assemblies would have different trust levels.
|
||||
|
||||
<p>This is an important component, but requires three major
|
||||
pieces of work:
|
||||
|
||||
<ul>
|
||||
<li>Runtime support for implementing the security
|
||||
demands.
|
||||
|
||||
<li>A guidelines document outlining what and where
|
||||
must have security demands in place.
|
||||
|
||||
<li>A full audit of our class libraries: method by
|
||||
method
|
||||
</ul>
|
||||
|
||||
<p>All of these are major pieces of work, and we currently
|
||||
have no plans to implement any of those. A volunteer effort might be
|
||||
able to help with the runtime requirements and the document,
|
||||
but until those are done, we are unlikely to start doing any
|
||||
work on the actual class library audit and instrumentation.
|
||||
|
||||
<h3>Mono and WinFX: 2006</h3>
|
||||
|
||||
<p>WinFX is the name given to the new set of libraries that
|
||||
makes up .NET in the Longhorn operating system: the existing
|
||||
.NET set of class libraries, plus the new functionality
|
||||
available in the OS.
|
||||
|
||||
<p>WinFX adds things like storage facilities (WinFS), a
|
||||
new versatile communications stack (Indigo) and a new
|
||||
eye-candy packed GUI programming system (Avalon).
|
||||
|
||||
<p>Although WinFS, Avalon and Indigo are very exciting
|
||||
components, at this time it is too early to tell when those
|
||||
components will be available for Mono. Open source developers
|
||||
will very likely start work on these, but since they are still
|
||||
far from being officially released, they are not in the radar
|
||||
at this point.
|
||||
|
||||
<h3>Unsupported technologies</h3>
|
||||
|
||||
<p>Some technologies are very hard to implement or are being
|
||||
phased out by components in the Longhorn time frame. In some
|
||||
cases, we feel that they are not crucial to the future of the
|
||||
open source desktop.
|
||||
|
||||
<p>System.EnterpriseServices and System.Management come to
|
||||
mind, and we are unlikely to put any resources into the task.
|
||||
We would gladly host the code if someone cares to implement
|
||||
it, but they would likely remain unsupported features of Mono.
|
||||
|
||||
<h3>Mono Developer Strategy</h3>
|
||||
|
||||
<p>Mono Developers should read the <a
|
||||
href="mono-hacking-roadmap.html">Mono Hacking Roadmap</a>
|
||||
|
||||
<h3>Comments</h3>
|
||||
|
||||
<p>Feel free to send your comments or questions the roadmap to
|
||||
<a href="mailto:[email protected]">[email protected]</a>
|
||||
|
||||
|
||||
<p>
|
||||
<i>Last Updated: Nov 1st, 2003</i>
|
||||
+8
-109
@@ -4,10 +4,10 @@
|
||||
on the mailing list what they can help with. The generic
|
||||
answer is always:
|
||||
<ul>
|
||||
<li> Write documentation.
|
||||
<li> Write regression tests.
|
||||
<li> Complete the implementations of the class libraries.
|
||||
<li> Help fix the bugs filed in our bugzilla database.
|
||||
* 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
|
||||
@@ -91,7 +91,7 @@ Happy hacking!
|
||||
by the MS runtime.
|
||||
<td>Medium-hard (thesis subject)
|
||||
<td>2-4 months
|
||||
<td><a href="http://bugzilla.ximian.com/show_bug.cgi?id=52605">52605</a>
|
||||
<td>not assigned
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
@@ -126,13 +126,13 @@ Happy hacking!
|
||||
support the generics requirements.
|
||||
<td>Medium-hard
|
||||
<td>2-3 months
|
||||
<td>lupus and Martin
|
||||
<td>not assigned
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>JIT (mono/mini/)
|
||||
<td>Port the JIT to additional architectures.
|
||||
Currently ports are in the works for mips, arm, sparc, s390. None of the ports
|
||||
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
|
||||
@@ -162,7 +162,7 @@ Happy hacking!
|
||||
stack walking to collect security info.
|
||||
<td>Medium-hard (thesis subject)
|
||||
<td>4-5 months
|
||||
<td><a href="http://bugzilla.ximian.com/show_bug.cgi?id=52606">52606</a>
|
||||
<td>not assigned
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
@@ -190,106 +190,5 @@ Happy hacking!
|
||||
<td>not assigned
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Tools
|
||||
<td>Write an implementation of the MSBuild compilation tool available in .NET 1.2
|
||||
<td>Medium
|
||||
<td>4-6 months
|
||||
<td>not assigned
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Build tools.
|
||||
<td>Currently it is easy for people doing daily
|
||||
updates from CVS to break their installation. Design a mechanism by
|
||||
which Mono never fails to compile.
|
||||
<td>Easy
|
||||
<td>1-2 weeks
|
||||
<td>not assigned
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Documentation.
|
||||
<td>Editorial review of the Monkeyguide: The monkeyguide is known to contain outdated
|
||||
statements, it needs to be reviewed and it needs an
|
||||
editor to take control over it. Some simple tasks
|
||||
include flattening out the Monkeyguide, since it is
|
||||
too nested today.
|
||||
<td>Easy
|
||||
<td>Ongoing work.
|
||||
<td>not assigned
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Documentation
|
||||
<td>GNOME.NET Chapter should probably be separated
|
||||
from the Monkeyguide. This is probably the most
|
||||
complete chapter, but it is burried in various nested
|
||||
levels of stuff, and because of this, it is not being
|
||||
updated. Write a chapter on custom control
|
||||
authoring and common patterns of app development.
|
||||
<td>Easy
|
||||
<td>Ongoing work.
|
||||
<td>not assigned
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Documentation Tools
|
||||
<td>The Monodoc collaborative service needs a better
|
||||
administration tool than it has today; Someone needs
|
||||
to redo the UI and streamline its process.
|
||||
<td>Easy
|
||||
<td>2-3 months.
|
||||
<td>not assigned
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Comment Service API
|
||||
<td>Design a full system for comments and ratings so
|
||||
people can annotate the documentation in Monodoc.
|
||||
<td>Easy
|
||||
<td>2-3 months.
|
||||
<td>not assigned
|
||||
</tr>
|
||||
<tr>
|
||||
<td>POSIX bindings.
|
||||
<td>The Mono.POSIX assembly is a project to create a binding to
|
||||
the various low-level calls in Unix which are not available
|
||||
thought he regular assemblies in .NET.
|
||||
|
||||
The work should be done in two steps: one step is doing the
|
||||
low-level binding for the system call, and another possibly is
|
||||
to expose .NET-level objects like Streams for common patterns:
|
||||
for example Streams for socketpairs.
|
||||
|
||||
<ul>
|
||||
<li>Complete the bindings for all POSIX calls.
|
||||
|
||||
<li>Design a glue layer, because the various low-level
|
||||
structures and values differ from operating system to
|
||||
operating system, so we must do the translation from
|
||||
our own set of definitions to the OS definitions.
|
||||
|
||||
The details are availble on bug <a
|
||||
href="http://bugzilla.ximian.com/show_bug.cgi?id=51849">51849</a>
|
||||
for details.
|
||||
</ul>
|
||||
|
||||
<td>Medium
|
||||
<td>2-3 months + QA.
|
||||
<td>not assigned
|
||||
</tr>
|
||||
<tr>
|
||||
<td>System.Drawing CODECs
|
||||
<td>Complete the JPEG and PNG codecs to be fully
|
||||
finished; Implement EXIF data loading; Implement the missing image codecs.
|
||||
<td>Medium
|
||||
<td>2-3 months.
|
||||
<td>not assigned
|
||||
</tr>
|
||||
<tr>
|
||||
<td>System.Data updates
|
||||
<td>.NET 1.2 introduced many new updates to the
|
||||
System.Data namespace: MARS and ObjectSpaces are the
|
||||
big ones.
|
||||
<td>Medium
|
||||
<td>6-9 months.
|
||||
<td>Work with the mono-devel-list to keep track of things.
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
@@ -43,7 +43,7 @@
|
||||
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.
|
||||
<p>Testing for Mono's Mono.Data.MySql and ByteFX's ByteFX.Data.MySQLClient is below.
|
||||
|
||||
** Current Status
|
||||
|
||||
@@ -51,7 +51,7 @@
|
||||
|
||||
<ul>
|
||||
|
||||
<li>ByteFX.Data.MySqlClient
|
||||
<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>
|
||||
@@ -109,7 +109,7 @@
|
||||
The current plan for the MySQL data providers:
|
||||
|
||||
<ul>
|
||||
<li>ByteFX.Data.MySqlClient
|
||||
<li>ByteFX.Data.MySQLClient
|
||||
<ul>
|
||||
<li>Testing and fixes</li>
|
||||
<li>Implement missing features</li>
|
||||
@@ -163,7 +163,7 @@
|
||||
<pre>
|
||||
using System;
|
||||
using System.Data;
|
||||
using ByteFX.Data.MySqlClient;
|
||||
using ByteFX.Data.MySQLClient;
|
||||
|
||||
public class Test
|
||||
{
|
||||
@@ -175,7 +175,7 @@
|
||||
"User ID=myuserid;" +
|
||||
"Password=mypassword;";
|
||||
IDbConnection dbcon;
|
||||
dbcon = new MySqlConnection(connectionString);
|
||||
dbcon = new MySQLConnection(connectionString);
|
||||
dbcon.Open();
|
||||
IDbCommand dbcmd = dbcon.CreateCommand();
|
||||
// requires a table to be created named employee
|
||||
@@ -283,8 +283,8 @@ mono TestExample.exe
|
||||
dbcmd.CommandText = sql;
|
||||
IDataReader reader = dbcmd.ExecuteReader();
|
||||
while(reader.Read()) {
|
||||
string FirstName = (string) reader["firstname"];
|
||||
string LastName = (string) reader["lastname"];
|
||||
string FirstName = reader["firstname"];
|
||||
string LastName = reader["lastname"];
|
||||
Console.WriteLine("Name: " +
|
||||
FirstName + " " + LastName);
|
||||
}
|
||||
|
||||
@@ -25,7 +25,7 @@
|
||||
|
||||
<li>List of unixODBC <a href="http://www.unixodbc.org/drivers.html">drivers</a>
|
||||
|
||||
<li>List of <a href="http://www.sqlsummit.com/odbcvend.htm">ODBC Vendors</a>
|
||||
<li>List of <a href="http://ourworld.compuserve.com/homepages/Ken_North/odbcvend.htm">ODBC Vendors</a>
|
||||
|
||||
<li>ODBC can connect to various databases which has an ODBC driver installed:
|
||||
<ul>
|
||||
@@ -38,7 +38,7 @@
|
||||
<li><a href="http://www.microsoft.com/sql/default.asp">Microsoft SQL Server</a> (
|
||||
via <a href="http://www.freetds.org/">FreeTDS</a> on UNIX)</li>
|
||||
<li><a href="http://www-3.ibm.com/software/data/db2/">IBM DB2 Universal Database</a></li>
|
||||
<li><a href="http://www.microsoft.com/office/access">MS Access</a>
|
||||
<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>
|
||||
|
||||
@@ -105,14 +105,14 @@
|
||||
|
||||
<li>For Unix, you will need unixODBC or iODBC installed</li>
|
||||
|
||||
<li>Have acess to a <a href="http://www-306.ibm.com/software/data/db2/">IBM DB2 Universal Database</a> or
|
||||
<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-306.ibm.com/software/data/db2/udb/ad/v8/cli/t0010406.htm">IBM web page about unixODBC and 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>
|
||||
|
||||
@@ -175,8 +175,8 @@
|
||||
dbcmd.CommandText = sql;
|
||||
IDataReader reader = dbcmd.ExecuteReader();
|
||||
while(reader.Read()) {
|
||||
string FirstName = (string) reader["firstname"];
|
||||
string LastName = (string) reader["lastname"];
|
||||
string FirstName = reader["firstname"];
|
||||
string LastName = reader["lastname"];
|
||||
Console.WriteLine("Name: " +
|
||||
FirstName + " " + LastName);
|
||||
}
|
||||
|
||||
-978
@@ -1,981 +1,3 @@
|
||||
@item Jul 9th, 2003: ASP.NET web services, coverage tools.
|
||||
|
||||
Web Services keep advancing: now we also support server-side
|
||||
authoring of Web Services as well as web service clients
|
||||
(which shipped in Mono 0.25). This works using our ASP.NET
|
||||
runtime, so it works with either XSP or the Apache module. The
|
||||
new Web Services work from Lluis added the missing bits:
|
||||
<ul>
|
||||
<li> .asmx files.
|
||||
<li> Method calls with complex parameters (whatever XmlSerializer can currently serialize, which is a quite a lot).
|
||||
<li> ref and out parameters.
|
||||
<li> Soap headers (In, Out and InOut).
|
||||
<li> Soap extensions, both global (configured in web.config) and particular to methods (configured using attributes).
|
||||
</ul>
|
||||
|
||||
For more details, see Lluis <a href="http://lists.ximian.com/archives/public/mono-devel-list/2003-July/001449.html">post</a>
|
||||
|
||||
GUI-wise: Work on <a href="http://xr.xwin.org">Xr</a> to
|
||||
implement System.Drawing continues. This will provide a full
|
||||
GDI+ implementation for Mono, and this will be hooked up into
|
||||
Gtk# and System.Windows.Forms.
|
||||
|
||||
MonoDoc keeps moving along, with a new web-based version
|
||||
coming up next, and we are also exploring a collaborative
|
||||
extension to allow people to contribute documentation through
|
||||
their web browsers.
|
||||
|
||||
Zoltan's Coverage analysis tool has been checked into CVS.
|
||||
With this tool it is now possible to find which class library
|
||||
code paths are missing regression tests. The module is
|
||||
`monocov'. Details are <a
|
||||
href="http://www.nexus.hu/vargaz/">here</a>. A fresh Gtk#
|
||||
version is available now.
|
||||
|
||||
Jean's remoting-based Soap implenentation is also maturing.
|
||||
|
||||
@item Jun 26th: Mono 0.25 has been released.
|
||||
|
||||
We have released Mono 0.25. A list of the new features is
|
||||
available <a href="archive/mono-0.25.html">here</a>.
|
||||
|
||||
Packages for Windows, and various Linux distributions are
|
||||
available on our <a href="download.html">download</a> page.
|
||||
|
||||
@item Jun 17th, 2003: Web Services client; Profiling hooks
|
||||
|
||||
Lluis and Gonzalo have checked into CVS the support for web
|
||||
services in the Mono runtime. This allows Mono to work as a
|
||||
web services client. We still require a WSDL compiler to
|
||||
compile the initial stub, but Erik has the beginning of a WSDL
|
||||
compiler ready and Atsushi has continued work on his
|
||||
experimental Xml Schema to C# class generator.
|
||||
|
||||
As part of this, the Mono Http runtime has been rewritten to
|
||||
increase reliability, scalability and conformance to the
|
||||
specs. Also our io-layer has been extended to not have
|
||||
arbitrary limits. This was done as part of our collaboration
|
||||
with SourceGear.
|
||||
|
||||
Paolo has commited the new pluggable profiling API to the Mono
|
||||
runtime: now the profiler is built as a module, and a new code
|
||||
coverage analysis has been checked in (and Zoltan already
|
||||
added improvements to it).
|
||||
|
||||
Mark's Mozilla bindings continue to improve, and we will shortly
|
||||
migrate the Mono documentation browser to use Mozilla, to take
|
||||
advantage of the tutorial's use of CSS.
|
||||
|
||||
Jackson's work on the IL assembler and Ben on running
|
||||
regression tests have provided us with a very needed tool in
|
||||
the Mono toolkit. One of the last missing pieces on the SDK.
|
||||
|
||||
On the crypto world, we got Sebastien's certificate viewer
|
||||
checked into CVS and the crypto code keeps advancing by leaps
|
||||
and bounds.
|
||||
|
||||
Alexandre and Aleksey Work continues on Windows.Forms on top
|
||||
of Wine and Gtk# (the former for full compatibility, the later
|
||||
for ease-of-authoring).
|
||||
|
||||
Cesar checked in the beginning of the semantic analysis code
|
||||
for his JScript compiler, and will be working on it full time.
|
||||
|
||||
@item Jun 11th, 2003: SourceGear and Ximian announce partnership
|
||||
|
||||
Ximian, Inc., the leading provider of desktop and server
|
||||
solutions enabling enterprise Linux adoption, today announced
|
||||
that SourceGear Corporation will use Mono\x{2122} Project
|
||||
technology to offer cross-platform versions of its
|
||||
products. In addition, the companies have entered into a
|
||||
development partnership under which Ximian will provide
|
||||
custom Mono development to enable delivery of SourceGear
|
||||
products later this year. As a result, SourceGear will offer
|
||||
both UNIX and Linux clients for its SourceGear Vault source
|
||||
code management tool, enabling broader use of its solutions in
|
||||
mixed-platform development organizations.
|
||||
|
||||
<a href="http://www.ximian.com/about_us/press_center/press_releases/index.html?pr=sourcegear">Read more...</a>
|
||||
|
||||
Some technical details are available <a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2003-June/014334.html">here</a>.
|
||||
|
||||
@item May 20th, 2003: OpenLink releases WineLib patches.
|
||||
|
||||
OpenLink <a
|
||||
href="http://lists.ximian.com/archives/public/mono-winforms-list/2003-May/000284.html">announced</a>
|
||||
the release of Vladimir's work to turn Wine into a library
|
||||
that can be used dynamically from Mono. This work simplifies
|
||||
the work on System.Windows.Forms as it is no longer necessary
|
||||
have a special version of the GC, nor have a stub program.
|
||||
The patches are available <a
|
||||
href="http://www.openlinksw.com/mono/">here</a>.
|
||||
|
||||
Mono packages for the Linux/s390 are available now in the <a
|
||||
href="download.html">download page</a>.
|
||||
|
||||
@item May 10th, 2003: Eclipse runs on Mono
|
||||
|
||||
Today Zoltan Varga announced that he got the <a
|
||||
href="http://www.eclipse.org">Eclipse IDE</a> running on top
|
||||
of Mono+<a href="http://www.ikvm.net">IKVM</a>.
|
||||
|
||||
A screenshot of Eclipse running with Mono can be found <a
|
||||
href="images/ikvm-screenshot.png">here</a>
|
||||
|
||||
@item May 6th, 2003: Mono 0.24 ships
|
||||
|
||||
We have released Mono 0.24 which includes our new code
|
||||
generation engine. A list of the new features is available <a
|
||||
href="archive/mono-0.24.html">here</a>.
|
||||
|
||||
Packages for Windows, and various Linux distributions are
|
||||
available on our <a href="download.html">download</a> page.
|
||||
We are shipping Gtk# and MonoDoc packages for the first time.
|
||||
|
||||
@item Apr 21st, 2003: Virtuoso 3.0 ships.
|
||||
|
||||
<a href="http://www.openlinksw.com">OpenLink's</a> released
|
||||
their <a href="http://www.openlinksw.com/press/virt3rel.htm">Virtuoso
|
||||
3.0</a> database system. Virtuoso ships on Windows and Linux.
|
||||
On Linux they use Mono as their runtime to host C#, .NET and
|
||||
ASP.NET. Congratulations to OpenLink for their release.
|
||||
|
||||
Virtuoso can be downloaded <a
|
||||
href="http://oplweb2.openlinksw.com:8080/download/virtuoso.vsp">here</a>
|
||||
and a demo is available <a
|
||||
href="http://demo.openlinksw.com:8890/tutorial/hosting/ho_s_2/ho_s_2.vsp">here</a>.
|
||||
|
||||
OpenLink is contributing fixes and code to the Mono project on
|
||||
an ongoing basis.
|
||||
|
||||
Jon Udell wrote a small <a
|
||||
href="http://www.infoworld.com/article/03/03/14/11stratdev_1.html">entry</a>
|
||||
|
||||
@item Apr 19th, 2003: RelaxNG validating reader; Activities.
|
||||
|
||||
Atsushi has created a <a
|
||||
href="http://www24.brinkster.com/ginga/RelaxngValidatingReader/">RelaxNG</a>
|
||||
validating XML reader.
|
||||
|
||||
There is activity on the <a
|
||||
href="http://www.gotmono.com">GotMono forums</a> and the <a
|
||||
href="http://www.nullenvoid.com/gtksharp/wiki/">Gtk# Wiki</a>
|
||||
|
||||
@item Apr 11th, 2003: First Mono Book is out; Team pages.
|
||||
|
||||
The first book to cover Mono is out. This book is currently
|
||||
only available in German, you can find it <a
|
||||
href="http://www.amazon.de/exec/obidos/ASIN/3827264928/qid=1050051051/sr=2-1/ref=sr_2_3_1/028-2755135-1623712">here</a>
|
||||
|
||||
We now have a page for the <a href="team.html">Mono Team</a>
|
||||
where we include a list of some of the people who have made
|
||||
Mono possible. If you have CVS access, please update the page
|
||||
to include your information.
|
||||
|
||||
@item Apr 5th, 2003: New compilation engine.
|
||||
|
||||
The new Mono compilation engine has been placed on CVS, the
|
||||
details are <a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2003-April/013269.html">here</a>
|
||||
|
||||
Zoltan has commited his <a
|
||||
href="http://lists.ximian.com/archives/public/mono-devel-list/2003-April/000274.html">typed
|
||||
allocation</a> patches to CVS as well.
|
||||
|
||||
@item Apr 3rd, 2003: NUnit 2.0 GTK# GUI; GtkMozEmbed; SWT#
|
||||
|
||||
Gonzalo has checked in his <a href="http://gtk-sharp.sf.net">Gtk#</a>-based
|
||||
<a href="http://nunit.org">NUnit</a> tool. Screenshots are <a
|
||||
href="http://primates.ximian.com/~gonzalo/mono/shots/running.png">here</a>
|
||||
and <a
|
||||
href="http://primates.ximian.com/~gonzalo/mono/shots/finished.png">here</a>
|
||||
|
||||
Mark has checked his bindings for Gtk-based Mozilla into CVS,
|
||||
module name: `GtkMozEmbed'. Read the <a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2003-April/013247.html">details</a>
|
||||
|
||||
The SWT port to C# using Gtk is <a
|
||||
href="http://lists.ximian.com/archives/public/sd-mono-port/2003-March/000114.html">progressing</a>. Screenshots are
|
||||
<a href="http://www.roboto.ch/swt">here</a>.
|
||||
|
||||
@item Mar 28th: Mono community site.
|
||||
|
||||
<a href="http://www.gotmono.com">www.gotmono.com</a> has
|
||||
openend its door: Got Mono is a Mono Community site.
|
||||
|
||||
@item Mar 25th: Second Mono Survey
|
||||
|
||||
<table width="100%" cellpadding="0" cellspacing="1" border="0" bgcolor="blue">
|
||||
<tr>
|
||||
<td valign="top">
|
||||
<div style="background: #c0d0ff; margin: 0px 0px 0px 0px; padding: 1px;">
|
||||
What do you think about Mono?
|
||||
|
||||
Is your company involved with the development and
|
||||
deployment of web applications? Is Linux becoming an
|
||||
important part of your company's business application
|
||||
strategy? Are you considering Mono for your next
|
||||
project? Would you like to shape the future of Mono
|
||||
and the use of Linux in business critical
|
||||
applications?
|
||||
|
||||
If you answered yes to any of these questions, we
|
||||
would like to talk with you. If interested, please
|
||||
email us at <a
|
||||
href="mailto:[email protected]">[email protected]</a>.
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
@item Mar 20th: Windows.Forms and Wine.
|
||||
|
||||
Alexandre has provided a modified version of the GC system
|
||||
that will work with and Mono. See the mono-winforms-list. It
|
||||
is now possible to run our Win32-based implementation of
|
||||
Windows.Forms with Mono on Linux.
|
||||
|
||||
@item Mar 7th: Mono 0.23
|
||||
|
||||
A new freshly baked release of Mono is available. Release
|
||||
notes are <a href="archive/mono-0.23">here</a>. This is mostly a
|
||||
bug fix release. No new features.
|
||||
|
||||
@item Mar 5th, 2003: Mono 0.22; MonoDoc 0.2; Debugger 0.2.1: Release-o-Rama.
|
||||
|
||||
Mono 0.22 has been released. See the <a
|
||||
href="archive/mono-0.22">release notes</a>. This is a bug fix
|
||||
release.
|
||||
|
||||
A new preview of MonoDoc 0.2, the Mono Documentation browser
|
||||
has been <a href="http://lists.ximian.com/archives/public/gtk-sharp-list/2003-March/001266.html">released</a>.
|
||||
|
||||
Martin also announced a <a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2003-March/012756.html">new
|
||||
release</a> of the Mono Debugger (both GUI and command line).
|
||||
|
||||
@item Mar 3rd, 2003: The Mono Hackers Hall Of Fame welcomes Zoltan Varga
|
||||
|
||||
The <a href="hackers.html">Mono Hackers Hall Of Fame</a>
|
||||
continues to show our appreciation to the excellent
|
||||
contributors that make <b>mono::</b> a successful free
|
||||
software project.
|
||||
|
||||
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 <a href="http://www.ikvm.net">IKVM</a> Java virtual
|
||||
machine.
|
||||
|
||||
@item Mar 2nd, 2003: New Mono mailing list.
|
||||
|
||||
A new mailing list for <a
|
||||
href="http://lists.ximian.com/mailman/listinfo/mono-devel-list">Mono
|
||||
Development</a> has been created.
|
||||
|
||||
@item Feb 27th, 2003: Mono 0.21 released
|
||||
|
||||
Mono 0.21 has been released. This is only a bug fix release.
|
||||
The <a href="archive/mono-0.21">release notes</a> are available.
|
||||
|
||||
Windows binary is available <a href="archive/mono-0.21-win32-1.exe">here</a>
|
||||
|
||||
@item Feb 25th, 2003: Mono 0.20 for Windows released; New Apache module released.
|
||||
|
||||
Packages of Mono for Windows have been <a
|
||||
href="archive/mono-0.20-stable-win32-2.exe">released</a>.
|
||||
Thanks to Daniel, Johannes and Paolo for setting this up.
|
||||
|
||||
Daniel has released a new version of his Mono Apache module that
|
||||
handles ASP.NET. The code is available at <a
|
||||
href="http://apacheworld.org/modmono/">here</a>
|
||||
|
||||
Nick has posted an update on the progress on our <a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2003-February/012467.html">regression
|
||||
tests</a>. We are looking for more tests, and more volunteers to write them.
|
||||
|
||||
Also, remember to contribute to the Gtk# documentation effort,
|
||||
momentum is picking up! See the entry for Feb 18th for more details.
|
||||
|
||||
@item Feb, 23rd, 2003: Mono 0.20 released; Gtk# 0.8 released.
|
||||
|
||||
Mono 0.20 has been released. Check out the <a
|
||||
href="archive/mono-0.20">release notes</a> for an overview of
|
||||
the changes. You can get it <a href="download.html">here</a>.
|
||||
There are no major features in this release, mostly bug fixes
|
||||
and performance improvements.
|
||||
|
||||
Gtk# 0.8 has been <a
|
||||
href="http://lists.ximian.com/archives/public/gtk-sharp-list/2003-February/001114.html">released</a>
|
||||
|
||||
<b>Important</b>: The contributed binaries for Windows
|
||||
binaries of Mono 0.20 contain a virus. Please read <a
|
||||
href="virus.html">this</a> if you installed the binary.
|
||||
|
||||
@item Feb 18th, 2003: Volunteers to document Gtk#
|
||||
|
||||
With the availability of a documentation browser, we are
|
||||
looking for volunteers to help us complete the documentation
|
||||
of the Gtk# binding for Mono.
|
||||
|
||||
Experience with Gtk is useful, but not mandatory. We have
|
||||
checked in stubs, and we have instructions, and resources to
|
||||
how to complete this process <a
|
||||
href="documentation.html">here</a>. Mail the <a
|
||||
href="mailto:[email protected]">[email protected]</a>
|
||||
for further discussion.
|
||||
|
||||
@item Feb 14th, 2003: OpenGL# bindings for Mono; Mono Basic updates.
|
||||
|
||||
Mark Crichton has completed his OpenGL/GLUT bindings for
|
||||
Gnome. A screenshot can be seen <a
|
||||
href="sshots/oglcs.png">here</a>. The bindings are available
|
||||
on the Mono CVS repository on the module `glgen'. This is a
|
||||
straight binding to the C API.
|
||||
|
||||
Marco has <a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2003-February/011752.html">posted
|
||||
an update</a> on the current state of the free VB.NET compiler
|
||||
for Mono.
|
||||
|
||||
We are looking for contributors and maintainers to the
|
||||
JavaScript compiler as well (Janet)
|
||||
|
||||
@item Feb 12th, 2003: New assemblies, Gtk# stub documentation, Authenticode, Polish site
|
||||
|
||||
Mono now distributes a few new assemblies: Mono.Security.Win32
|
||||
as a layer to use the crypto functionality on Win32. The
|
||||
Mono.Posix assembly which contains functionality for taking
|
||||
advantage of Unix facilities.
|
||||
|
||||
A <a href="http://www.go-mono.pl/">Mono site in Poland</a>.
|
||||
|
||||
Stubs for the Gtk# documentation have been checked into CVS.
|
||||
If you want to contribute please read <a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2003-February/012108.html">this
|
||||
message</a>
|
||||
|
||||
Mono development is moving quickly: Tim and Daniel have been
|
||||
improving the Oracle database provider and Sebastien Pouliot
|
||||
has got code signing to work using Authenticode with pure open
|
||||
source and managed code. Plenty of new VB.NET work from Marco
|
||||
(compiler) and Daniel (runtime). Also Jackson has resumed
|
||||
work on the IL assembler and the fully managed library to
|
||||
generate CIL images (Sergey wrote the first Mono.PEToolkit).
|
||||
|
||||
@item Feb 11th, 2003: Mono Weekly News, New assemblies.
|
||||
|
||||
<a href="http://monoevo.sourceforge.net/mwn/index.html">Mono
|
||||
Weekly News</a>: Includes a new interview, software
|
||||
announcements and the PHP/Mono integration.
|
||||
|
||||
@item Feb 5th, 2003: MonoDoc 0.1
|
||||
|
||||
A <a
|
||||
href="http://www.go-mono.com/archive/monodoc-0.1.tar.gz">preliminary
|
||||
release</a> of the Mono Documentation Browser is now availble.
|
||||
Release <a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2003-February/011935.html">notes</a>
|
||||
|
||||
@item Jan, 22th, 2003: Mono wins award, OpenLink releases Virtuoso.
|
||||
|
||||
Mono won the `Best Open Source Project' award at the Linux
|
||||
World Expo. A description is <a
|
||||
href="http://linuxtoday.com/news_story.php3?ltsn=2003-01-23-024-26-OP-EV">here</a>
|
||||
|
||||
Open Link has a <a
|
||||
href="http://biz.yahoo.com/prnews/030123/neth013_1.html">press
|
||||
release</a> about Virtuoso 3.0: the first commercial product
|
||||
shipping that uses Mono.
|
||||
|
||||
@item Jan, 20th, 2003: Mono 0.19 released; Screenshots page; Gtk# 0.7
|
||||
|
||||
Mono 0.19 has been released. Check out the <a
|
||||
href="archive/mono-0.19">release notes</a> for an overview of
|
||||
the changes. You can get it <a href="download.html">here</a>.
|
||||
There are no major features in this release, mostly bug fixes
|
||||
and performance improvements.
|
||||
|
||||
We have now a new section <a href="screenshots.html">with
|
||||
screenshots</a> of various Mono applications. You can see
|
||||
there the new released Debugger, as well as the work in
|
||||
progress on the documentation browser.
|
||||
|
||||
<a href="http://gtk-sharp.sf.net">Gtk# 0.7</a> has been <a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2003-January/005222.html">released</a>
|
||||
|
||||
@item Jan, 19th, 2003: Mono Debugger released.
|
||||
|
||||
After six month of extensive development, Martin Baulig has
|
||||
released the first version of the Mono debugger. The Mono
|
||||
debugger is written in C# and can debug both managed and
|
||||
unmanaged applications, support for multiple-threaded
|
||||
applications and should be relatively easy to port to new
|
||||
platforms.
|
||||
|
||||
Details of the release are available in <a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2003-January/005192.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).
|
||||
|
||||
@item Jan, 17th, 2003: DB2 provider, MacOS X
|
||||
|
||||
Christopher Bockner has contributed a DB2 System.Data client.
|
||||
|
||||
MacOS X support on the runtime has been integrated into the
|
||||
distribution, and MCS works with it.
|
||||
|
||||
Zoltan has managed to get <a
|
||||
href="http://radio.weblogs.com/0109845/">IKVM</a> (a Java VM
|
||||
for .NET) to run with Mono. The HelloWorld.class runs with
|
||||
the Mono runtime.
|
||||
|
||||
@item Jan, 13th, 2003: Mono 0.18 released
|
||||
|
||||
Mono 0.18 has been released. Check out the <a
|
||||
href="archive/mono-0.18">release notes</a> for an overview of
|
||||
the changes. You can get it <a href="download.html">here</a>.
|
||||
|
||||
@item Jan 10th, 2003: Mono Weekly News.
|
||||
|
||||
A new issue of the <a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2003-January/004903.html">Mono
|
||||
Weekly News</a> has been published.
|
||||
|
||||
Check out the <a href="crypto.html">Crypto status</a> page
|
||||
that Sebastien has put together.
|
||||
|
||||
@item Jan 3rd, 2003: Glade#, Code Coverage, Apache, MBas, Debugger.
|
||||
|
||||
Rachel has made Glade# use attributes so binding C# widgets to
|
||||
the designed widgets is now easier than ever. Alp has
|
||||
improved this to use implicit names as well.
|
||||
|
||||
Martin's Mono debugger now has support for multi-thread
|
||||
debugging. Special feature: breakpoints can be defined in a
|
||||
per-thread basis now.
|
||||
|
||||
Daniel López has checked in his Apache module to integrate
|
||||
Mono and Mono's ASP.NET support as an Apache module. Gonzalo
|
||||
has folded his new Mono hosting classes into this module (they
|
||||
are now shared between XSP and mod_mono). You can get the
|
||||
mod_apache from CVS (module name: mod_mono).
|
||||
|
||||
Mono Basic improvements: Marco has added support for more
|
||||
statements on the grammar.
|
||||
|
||||
Zoltan has <a href="http://www.nexus.hu/vargaz2/">posted</a>
|
||||
his Code Coverage analysis tool for Mono.
|
||||
|
||||
@item Dec 17th, 2002: Mono: Commercial uses.
|
||||
|
||||
<a href="http://www.tipic.com">Tipic</a> today <a
|
||||
href="http://www.ximian.com/about_us/press_center/press_releases/index.html?pr=tipic_mono">announced</a>
|
||||
their work on porting their Instant Messaging Server platform
|
||||
to run on Mono.
|
||||
|
||||
<a href="http://www.winfessor.com">Winfessor</a> also <a
|
||||
href="http://www.winfessor.com/press.asp">announced</a> the
|
||||
availability of their Jabber SDK to run on Mono.
|
||||
|
||||
Also two weeks ago we mentioned <a
|
||||
href="http://www.openlinksw.com">OpenLink Software's</a> <a
|
||||
href="http://www.ximian.com/about_us/press_center/press_releases/index.html?pr=openlink_mono">announcement</a>
|
||||
of their product, also using Mono.
|
||||
|
||||
@item Dec 10th, 2002: Gtk# 0.6 released; Mono 0.17 packages for Windows and Debian.
|
||||
|
||||
Mike Kestner <a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2002-December/003961.html">announced
|
||||
Gtk# 0.6</a>. This new release includes many new features and
|
||||
bug fixes, and is the perfect companion to the <a
|
||||
href="archive/mono-0.17">Mono 0.17</a> release.
|
||||
|
||||
Johannes has contributed a Windows-ready package of Mono 0.17,
|
||||
and its available from our <a
|
||||
href="download.html">download</a> page.
|
||||
|
||||
Alp Toker has <a href="http://www.atoker.com/mono/">Debian packages</a>
|
||||
|
||||
@item Dec 9th, 2002: Mono 0.17 has been released
|
||||
|
||||
Mono 0.17 has been released. Check out the <a
|
||||
href="archive/mono-0.17">release notes</a> for a more detailed
|
||||
list. You can get it <a href="download.html">here</a>.
|
||||
|
||||
Many new features as well as plenty of bug fixes. Many new
|
||||
System.Data providers and a more mature System.Web (ASP.NET)
|
||||
which can now be hosted in any web server. A simple <a
|
||||
href="archive/xsp-0.2.tar.gz">test web server</a> to host
|
||||
asp.net has been released as well.
|
||||
|
||||
This version also integrates Neale's s390 port.
|
||||
|
||||
This release also includes a new exception handling system
|
||||
that uses the gcc exception information that vastly improves
|
||||
our internalcall speed (15% faster mcs compilation times).
|
||||
|
||||
@item Dec 8th, 2002: VB.NET, Oracle Provider.
|
||||
|
||||
Marco has got the Mono Basic compiler up to speed (support for
|
||||
classes, modules, expressions, object creation, method
|
||||
invocation, local variables, and some statements). The
|
||||
compiler is based on the work from Rafael Teixeira on MCS.
|
||||
|
||||
Screenshots: <a
|
||||
href="http://modgb.sourceforge.net/monobasic_snap.png">in
|
||||
Windows doing Windows.Forms</a> and in Linux doing <a
|
||||
href="images/gtk-vb.png">VB with Gtk#</a> (courtesy of Alp).
|
||||
|
||||
Daniel Morgan has checked in his Oracle provider to the CVS
|
||||
repository as well.
|
||||
|
||||
@item Nov 27th, 2002: Press release, tutorials, Windows Forms, ADO.NET, Magazine.
|
||||
|
||||
<a
|
||||
href="http://www.business2.com/articles/mag/0,1640,45454,FF.html">The
|
||||
Penguin Takes Flight</a>: an article written by Erick
|
||||
Schonfeld appears on the December issue of <a
|
||||
href="http://www.business2.com/">Business 2.0</a> magazine.
|
||||
|
||||
<a href="http://www.openlinksw.com">OpenLink</a> and <a
|
||||
href="http://www.ximian.com">Ximian</a> made <a
|
||||
href="http://www.ximian.com/about_us/press_center/press_releases/index.html?pr=openlink_mono">joint
|
||||
announcement</a> on the plans of OpenLink to ship their <a
|
||||
href="http://www.openlinksw.com/virtuoso/index.htm">Virtuoso</a>
|
||||
server on Unix using Mono.
|
||||
|
||||
Martin Willemoes's <a href="gnometutorial">GNOME.NET
|
||||
tutorial</a> is now available from the main Mono site. This
|
||||
tutorial is a collaborative effort to teach developers how to
|
||||
use Mono to create Mono applications using <a href="http://gtk-sharp.sf.net">Gtk#</a>
|
||||
|
||||
Dennis Hayes has posted and <a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2002-December/003800.html">update</a>
|
||||
on the work to get Windows.Forms working on Mono. There is a
|
||||
new test application that people can use to test their
|
||||
controls. If you are interested in working on Windows.Forms,
|
||||
you can participate in the <a
|
||||
href="http://lists.ximian.com/mailman/listinfo/mono-winforms-list">mono-winforms
|
||||
mailing list</a>
|
||||
|
||||
Brian Ritchie has been working on an ADO.NET <a
|
||||
href="http://brianritchie.webhop.net/ideas/adocodegen.aspx">data
|
||||
layer</a> and an <a
|
||||
href="http://brianritchie.webhop.net/ideas/appserver.aspx">application
|
||||
server</a> for Mono.
|
||||
|
||||
Dan Morgan has checked in his Oracle provider, and Tim Coleman
|
||||
continues to work on the TDS implementation of the data classes.
|
||||
|
||||
The rest of the team has been working on bug fixing in the
|
||||
runtime, the compiler, and the class libraries. Also,
|
||||
compilation speed has increased recently by performing a
|
||||
number of simple optimizations in the compiler.
|
||||
|
||||
@item Nov 19th, 2002: Crypto update; Books; Gtk# Datagrid; .NET ONE Slides
|
||||
|
||||
Sebastien has got DSA and RSA signatures <a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2002-November/003497.html">working</a>
|
||||
as well as RSA <a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2002-November/003502.html">encryption</a>.
|
||||
We now distribute Chew Keong TAN's BigInteger classes.
|
||||
|
||||
Brian has contributed a System.Data multiplexor in Mono, it
|
||||
can be found in the Mono.Data assembly. The details of this
|
||||
new technology are <a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2002-November/003400.html">here</a>.
|
||||
It works in Mono and the .NET Framework.
|
||||
|
||||
Larry O'Brien has announced the candidate book for <a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2002-November/003500.html">
|
||||
Thinking in C#</a>. The book is Mono-friendly.
|
||||
|
||||
Another book that covers mono (available in German only) is <a
|
||||
href="http://www.databecker.de/frames.php?PHPSESSD=4948515556575049525459495248485949485348&PHPSESSID=6cc68dbcfbcbacd7b82a984b0700d5d6&t=2">
|
||||
here</a>.
|
||||
|
||||
Dan Morgan has implemented a DataGrid widget for Gtk#, you can
|
||||
see Windows screenshots for it <a
|
||||
href="images/GtkSharpDataGridScreenshot.png">here</a> and <a
|
||||
href="images/SqlSharpGtkScreenshot4.png">here</a>.
|
||||
|
||||
Slides from the Mono developers for the .NET ONE conference are available now:
|
||||
<ul>
|
||||
<li><a
|
||||
href="http://primates.ximian.com/~miguel/slides-europe-nov-2002/DotNetOneKeynote.sxi">
|
||||
Mono Keynote presentation</a>
|
||||
|
||||
<li><a href="http://primates.ximian.com/~lupus/slides/embed/">Hosting the Mono Runtime</a><br>
|
||||
The simple embedding of Mono in Perl is available <a
|
||||
href="http://primates.ximian.com/~lupus/slides/embed/Mono-0.01.tar.gz">here</a>
|
||||
|
||||
<li><a href="http://primates.ximian.com/~lupus/slides/jit/">The Mono JIT compiler</a>
|
||||
|
||||
<li><a href="http://primates.ximian.com/~miguel/slides-europe-nov-2002/Mono_C_Sharp_Overview_1007.sxi">
|
||||
Mono C# Compiler Overview</a>
|
||||
</ul>
|
||||
|
||||
A couple of other presentations from Miguel's trip to Europe
|
||||
are available <a
|
||||
href="http://primates.ximian.com/~miguel/slides-europe-nov-2002/">here</a>
|
||||
in Open Office file format.
|
||||
|
||||
@item Nov 8th, 2002: Mono s390, Database work, new JIT updates.
|
||||
|
||||
Neale Ferguson has contributed <a href="download.html">RPM
|
||||
packages</a> of Mono for the Linux/s390.
|
||||
|
||||
Tim Coleman posted an <a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2002-November/003329.html">update</a>
|
||||
on the improvements in the System.Data
|
||||
|
||||
The new JIT engine can run 72 out of our 154 tests for the
|
||||
virtual machine, and it also got exception support this week.
|
||||
|
||||
@item Nov 1st, 2002: TDS, Crypto, Gtk#, Winforms, bug fixes.
|
||||
|
||||
Tim's SqlClient is <a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2002-November/003161.html">now
|
||||
capable</a> of communicating with the Microsoft SQL server
|
||||
using the TDS protocol. A screenshot showing a sample client
|
||||
running with <a href="http://gtk-sharp.sf.net">Gtk#</a> on
|
||||
Windows is shown <a
|
||||
href="images/SqlSharpGtkSceenshot3.png">here</a>
|
||||
|
||||
Sebastien has made all symetric ciphers functional on all
|
||||
supported modes; All the classes in Security.Cryptography are
|
||||
present and the X590 certificates are now in too. Jackson has
|
||||
been working on the Security classes.
|
||||
|
||||
Many bug fixes all over the place: class libraries (Dick,
|
||||
Piers, Ville, Zoltan, Gonzalo, Dan, Atsushi, Nick, Phillip),
|
||||
compiler, runtime engine. A big thank goes for everyone who
|
||||
has been providing bug reports for us to track down.
|
||||
|
||||
Gaurav has been working on multiple WebControls. Gonzalo migrated
|
||||
the ASP.NET engine to use POST for interaction.
|
||||
|
||||
In the Gtk# land saw the integration of gda, gnome-db and GStreamer
|
||||
bindings.
|
||||
|
||||
Windows.Forms classes now build on Linux and Windows, check
|
||||
out the status pages for areas of collaboration.
|
||||
|
||||
@item Oct 24th, 2002: S390 support, XSP/ASP.NET, Win32 contributors, TDS.
|
||||
|
||||
Today Neal Ferguson's support for the IBM S390 was checked
|
||||
into CVS.
|
||||
|
||||
The XSP processor has been fully integrated into the
|
||||
System.Web assembly, and Gonzalo has finished the hosting
|
||||
interfaces in Mono. This means that it is possible to embed
|
||||
ASP.NET with the same APIs used in Windows, and is possible to
|
||||
easily embed it with Apache for example. The XSP module has
|
||||
now become a shell for testing the System.Web classes.
|
||||
|
||||
We are looking for contributors that know Win32 to contribute
|
||||
to the Windows.Forms implementation. If you want to help
|
||||
write some controls using the Win32 API, get in touch with our new <a
|
||||
href="http://lists.ximian.com/mailman/listinfo/mono-winforms-list">[email protected]
|
||||
list</a> mailing list.
|
||||
|
||||
Tim's TDS System.Data set of classes can now talk to SQL
|
||||
servers using the TDS protocol (version 4.2) with
|
||||
connection pooling. Currently it can connect, run
|
||||
transactions, update/insert/delete, and read some types. A
|
||||
data adapter is also coming soon.
|
||||
|
||||
@item Oct 21th, 2002: Crypto, Winforms list, Database, GConf, Debugger.
|
||||
|
||||
Sebastien Poliot has made a lot of progress, he reports that
|
||||
DES and TripleDES have been fixed; Rijndael and CFB modes
|
||||
still have problems in some configurations and some areas that
|
||||
are not supported by the .NET framework.
|
||||
|
||||
Last week we created a new <a
|
||||
href="http://lists.ximian.com/mailman/listinfo/mono-winforms-list">mailing
|
||||
list</a> to discuss the Mono Winforms implementation.
|
||||
|
||||
Tim has started a full C# implementation of the TDS protocol
|
||||
and the providers, and Brian continues his work on his ODBC
|
||||
binding.
|
||||
|
||||
Rachel Hestilow has also checked in a binding for GConf. This
|
||||
binding <a
|
||||
href="http://toxic.magnesium.net/~hestilow/gconfsharp/intro.html">is
|
||||
unique</a> in that it uses some features in the CLI to support
|
||||
complex data types, and allows the user to keep only one
|
||||
representation of the types instead of two (the master types
|
||||
is defined in CLI-land). Also Property Editors (<a
|
||||
href="http://primates.ximian.com/~miguel/shots/gconf-shot.png">shot</a>)
|
||||
simplify the creation of user interfaces that bind their
|
||||
configuration to backend keys, following the <a
|
||||
href="http://developer.gnome.org/projects/gup/hig/1.0/">GNOME
|
||||
Human Interface Guidelines.</a>
|
||||
|
||||
Martin is now on vacation, but before leaving he produced a
|
||||
number of documents detailing the state of the debugger. The
|
||||
major missing feature is full support for debugging unmanaged
|
||||
applications (it requires dwarf-2 handlers for types). We
|
||||
will do some polishing of the user interface (<a
|
||||
href="http://primates.ximian.com/~miguel/shots/debugger-4.png">new
|
||||
shot</a>) to expose the existing and rich functionality to the
|
||||
users and try to release a preview of the debugger at the same
|
||||
time as Mono 0.17.
|
||||
|
||||
@item Oct 14th, 2002: Crypto, Database work, Debugger, Documentation.
|
||||
|
||||
Brian, Daniel and Rodrigo have been busy working on the ODBC
|
||||
provider for Mono. Daniel posted some <a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2002-October/002755.html">updates</a>.
|
||||
Brian posted <a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2002-October/002758.html">details
|
||||
about the ODBC.NET</a> provider.
|
||||
|
||||
Also Sebastien Pouliot has been improving the various
|
||||
cryptographic classes in Mono, something that we had not done
|
||||
in quite some time. We are looking for a way to handle
|
||||
big-nums. We need either a managed or unmanaged set of
|
||||
classes for handling large numbers, and some volunteers to
|
||||
expose this functionality to C# (Either as an internal
|
||||
assembly, or as a set of P/Invoke, Internal call wrappers).
|
||||
|
||||
Martin has got our debugger to support adding breakpoints at
|
||||
file/line combos. This was more complex than generic
|
||||
breakpoints in routines, because these breakpoints are set on
|
||||
routines that probably have not been JITed just yet. Martin's
|
||||
focus now is on stabilizing our debugger and aim for a public
|
||||
release of it.
|
||||
|
||||
We have also imported the ECMA documentation into a separate
|
||||
module, and with the help from Scott Bronson we will have the
|
||||
necessary XSLT tools to finish our native documentation
|
||||
browser for Mono. This together with the work from Adam will
|
||||
be the foundation for the <a href="classlib-doc.html">Mono
|
||||
Documentation Tools</a>.
|
||||
|
||||
@item Oct 9th, 2002: Various Mono updates.
|
||||
|
||||
Brian Ritchie, Daniel Morgan, Rodrigo Moya and Ville Palo have
|
||||
been working on various database providers. The MySQL has
|
||||
seen a lot of work, and a new ODBC provider is now on CVS and
|
||||
more extensive regression tests have been checked in.
|
||||
|
||||
Dick Porter is our background hero and keeps fixing the
|
||||
low-level bugs in the portability layer. Now the Mono handle
|
||||
daemon should be a lot more robust and will no longer leave IPC
|
||||
regions. Gonzalo Paniagua has initiated the migration of XSP
|
||||
into the System.Web class libraries now that we have a
|
||||
complete HttpRuntime implementation. This means that you are
|
||||
able to embed the ASP.NET processor into any web server you
|
||||
want. This also includes support for the system-wide
|
||||
configuration file `machine.config'.
|
||||
|
||||
Martin Baulig has been busy with the Mono Debugger, you can see how
|
||||
it looks <a
|
||||
href="http://primates.ximian.com/~miguel/debugger-1.png">here</a>
|
||||
and <a
|
||||
href="http://primates.ximian.com/~miguel/debugger-2.png">here</a>.
|
||||
Now local variables and breakpoints are supported, and we are
|
||||
working on the UI elements to simplify their use (as seen on
|
||||
the screenshot).
|
||||
|
||||
<a href="http://gtk-sharp.sf.net">Gtk#</a> has seen a lot of
|
||||
activity specially as we start to build larger applications.
|
||||
Vladimir Vukicevic, Kristian Rietveld, Rachel Hestilow, Mike
|
||||
Kestner and Miguel de Icaza have been busy improving it.
|
||||
mPhoto which is a Photo management application for Mono and
|
||||
Gtk# is seen <a
|
||||
href="http://primates.ximian.com/~miguel/shots/mphoto-2.jpg">here</a>.
|
||||
|
||||
Chris Toshok the man behind LDAP in Evolution continues to
|
||||
work on the Mono.LDAP# implementation.
|
||||
|
||||
Dietmar Maurer and Paolo Molaro are still busy working on our
|
||||
new optimized JIT/ATC engine and are making great progress.
|
||||
The code base has been designed to ease the implementation of
|
||||
more advanced compiler optimizations, and optimizations can be
|
||||
chosen individually so they can be tuned for a particular
|
||||
processor, or use profile-based information to improve the
|
||||
performance.
|
||||
|
||||
@item Oct 1st, 2002: Mono 0.16 released; Debugger updates.
|
||||
|
||||
Mono 0.16 has been released. Source and RPMs are <a
|
||||
href="download.html">available</a>. The release notes are <a
|
||||
href="archive/mono-0.16">here</a>.
|
||||
|
||||
Martin's debugger can debug both managed and unmanaged code.
|
||||
Recently Martin added support for locals, parameters, and
|
||||
breakpoints on top of the existing infrastructure (his
|
||||
debugger supported instruction-level and source-code level
|
||||
single-stepping).
|
||||
|
||||
@item Sep 19th, 2002: Mono Survey.
|
||||
|
||||
Help us plan for the future of Mono by filing out the <a
|
||||
href="http://primates.ximian.com/~miguel/monosurvey">First Mono
|
||||
Survey</a>
|
||||
|
||||
@item Sep 17th, 2002: Mono Hackers Hall of Fame: Sergey Chaban
|
||||
|
||||
The <a href="hackers.html">Mono Hackers Hall Of Fame</a>
|
||||
continues to show our appreciation to the excellent
|
||||
contributors that made <b>mono::</b> a successful free
|
||||
software project.
|
||||
|
||||
This time the Hall of Fame welcomes 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.
|
||||
|
||||
|
||||
@item Sep 16th, 2002: Documentation Tools, ILASM, Debugger, Mono LDAP, Winforms
|
||||
|
||||
Adam Treat has started moving the documentation universe again. We
|
||||
have a new strategy to document our APIs (given that we have
|
||||
chosen <a href="classlib-doc.html">not to document the code
|
||||
inline</a>). This includes the use of a master reference file
|
||||
that will hold the entry points to document. All master files
|
||||
for our assemblies have been checked into CVS now.
|
||||
|
||||
Sergey Chaban's Mono.PEToolkit and ILASM tools have been
|
||||
checked into CVS. Although ILASM is old and will soon be
|
||||
updated, we wanted to get the build issues sorted out.
|
||||
|
||||
Martin Baulig's Mono Debugger is still on its early stages,
|
||||
but you can run and run step by step your C# code and C code
|
||||
(including the Mono runtime). Dwarf-2 is required to compile
|
||||
your code. The regular step, step-into, and assembly-level
|
||||
step and step-into are supported. And comes with a Gtk#
|
||||
UI. The debugger is written mostly in C# with some C glue
|
||||
code. Most of the work is on the engine, we will be working
|
||||
on making a good UI in the future.
|
||||
|
||||
Chris Toshok of the Hungry Programmer's fame has checked in
|
||||
Mono.Directory.LDAP, a C# wrapper for the LDAP libraries.
|
||||
This is the substrate for implementing the
|
||||
System.DirectoryServices assembly.
|
||||
|
||||
Andrew has also continued with some of the cryptographic
|
||||
classes implementation.
|
||||
|
||||
After much public debate, we have chosen a new <a
|
||||
href="winforms.html">strategy to implement winforms</a>.
|
||||
Implementing a Gtk, Qt or Aqua based version of Winforms was
|
||||
going to be almost as complex as implementing Wine itself. So
|
||||
the new strategy is to only roll out a WineLib-based
|
||||
implementation.
|
||||
|
||||
@item Sep 4th, 2002: .NET One 2002 Program available
|
||||
|
||||
The <a
|
||||
href="http://www.sigs-datacom.de/sd/kongresse/dotnet_2002/index.htm">.NET
|
||||
ONE 2002</a> conference in Frankfurt is now available. Paolo
|
||||
will be talking about the Mono JIT and embedding the Mono
|
||||
runtime in your Windows and Linux applications. Mike Kestner
|
||||
will talk about <a href="http://gtk-sharp.sf.net">Gtk#</a> and
|
||||
the automatic binding generator used by Gtk# and Miguel will
|
||||
be talking about the Mono project on Monday's keynote and on
|
||||
the Mono C# compiler on Tuesday.
|
||||
|
||||
@item Sep 3rd, 2002: Apache integration
|
||||
|
||||
<a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2002-September/001862.html">Sterling</a>
|
||||
announced an Apache module that hosts
|
||||
Mono, and allows CIL code to run from within Apache, giving the
|
||||
module access to the Apache runtime. This uses the Mono embedding
|
||||
API.
|
||||
|
||||
@item Aug 24th, 2002: Gtk# 0.4 released
|
||||
|
||||
Shortly after <a href="download.html">Mono 0.15</a> was
|
||||
released a fresh version of <a
|
||||
href="http://gtk-sharp.sf.net">Gtk#</a> was <a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2002-August/001702.html">announced</a>.
|
||||
|
||||
@item Aug 23rd, 2002: Mono 0.15 released
|
||||
|
||||
Mono 0.15 has been released. Source and RPMs are <a
|
||||
href="download.html">available</a>. The release notes are <a
|
||||
href="archive/mono-0.15">here</a>
|
||||
|
||||
@item Aug 21th, 2002: Portable.NET encodings integrated into Mono.
|
||||
|
||||
Rhys Weatherley has contributed the Portable.NET encoders to
|
||||
the Mono class libraries. This is a great step towards
|
||||
cooperation between these projects. Thanks to Paolo for doing the
|
||||
merger on our side.
|
||||
|
||||
His encoders are more complete than the iconv-based approach
|
||||
that mono used, which was unreliable under certain
|
||||
circumstances.
|
||||
|
||||
@item Aug 20th, 2002: Remoting work, Resources, SPARC checkins, ADO.NET
|
||||
|
||||
<b>San Francisco</b>: August 14th. Linux World Expo.
|
||||
|
||||
Mark Crichton has checked in his patches to get the SPARC port
|
||||
on par with the PPC port.
|
||||
|
||||
Dick has checked-in the resource reader and resource writers
|
||||
to the class libraries, and Dietmar checked in the C# support
|
||||
code for the remoting infrastructure.
|
||||
|
||||
More work on System.Data: the LibGDA (our OleDB backend) based
|
||||
providers are quickly maturing, and recently they executed
|
||||
their first query.
|
||||
|
||||
@item Aug 13th, 2002: MCS news, Gtk# progress, Windows.Forms, ADO.NET
|
||||
|
||||
Martin Baulig has been fixing all the known bugs in the C#
|
||||
compiler and now has moved into improving the compilation
|
||||
speed and the generated code quality of MCS. Today we got a
|
||||
50% speedup in the bootstrap of MCS going from 24 seconds to 12 seconds.
|
||||
|
||||
Gtk# has been making a lot of progress, some interesting
|
||||
corner cases are now supported:, you can now create canvas items as
|
||||
well as using the tree widget. Here is a shot of <a
|
||||
href="images/mocil.png">MonoCIL</a>.
|
||||
|
||||
On the runtime front, focus has been on improving remoting
|
||||
support, exception handling, as well as completing the support
|
||||
for structure marshaling.
|
||||
|
||||
Patrik is also back in action: the HttpRuntime infrastructure
|
||||
is rapidly improving, and Gonzalo is working into moving XSP
|
||||
into our main class library and providing the missing pieces
|
||||
to integrate with Patrik's code.
|
||||
|
||||
Dennis and his team are working on a WineLib-based
|
||||
implementation of Windows Forms to guarantee that the corner
|
||||
cases of Windows.Forms can be handled, and we are back on track again.
|
||||
|
||||
A lot more work on the ADO.NET and WebServices has also been
|
||||
checked into CVS.
|
||||
|
||||
@item Aug 1st, 2002: Mono Hackers Hall of Fame
|
||||
|
||||
The <a href="hackers.html">Mono Hackers Hall Of Fame</a> has been started
|
||||
to show our appreciation to the excellent contributors that made <b>mono::</b>
|
||||
a successful free software project.
|
||||
|
||||
The first, deserved, entry goes to
|
||||
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.
|
||||
|
||||
@item Looking for volunteers
|
||||
|
||||
We are looking for volunteers to help complete various pieces
|
||||
|
||||
@@ -109,8 +109,8 @@
|
||||
dbcmd.CommandText = sql;
|
||||
IDataReader reader = dbcmd.ExecuteReader();
|
||||
while(reader.Read()) {
|
||||
string FirstName = (string) reader["firstname"];
|
||||
string LastName = (string) reader["lastname"];
|
||||
string FirstName = reader["firstname"];
|
||||
string LastName = reader["lastname"];
|
||||
Console.WriteLine("Name: " +
|
||||
FirstName + " " + LastName);
|
||||
}
|
||||
|
||||
+34
-16
@@ -8,7 +8,9 @@
|
||||
|
||||
<li>Works on Windows and Linux</li>
|
||||
|
||||
<li>Works with Oracle 8i and 9i.</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>
|
||||
@@ -17,6 +19,8 @@
|
||||
|
||||
<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
|
||||
@@ -28,15 +32,23 @@
|
||||
** Current Status
|
||||
|
||||
<ul>
|
||||
<li>OracleConnection can connect and disconnect to an Oracle 8i or 9i database on
|
||||
<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
|
||||
@@ -52,11 +64,14 @@
|
||||
|
||||
<li>Handling of various data types need to be added.</li>
|
||||
|
||||
<li>Data Adapter exists, and a DataSet can be filled using it.</li>
|
||||
<li>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# GUI versions.</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>
|
||||
|
||||
@@ -68,12 +83,11 @@
|
||||
<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 (WORKING)</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>
|
||||
<li>Once Oracle 10g is released, make sure Mono works with Oracle 10g.</li>
|
||||
|
||||
</ul>
|
||||
|
||||
@@ -82,13 +96,15 @@
|
||||
<ul>
|
||||
<li>Have a working mono and mcs</li>
|
||||
|
||||
<li>Have access to an Oracle 8i or 9i database or download it from
|
||||
<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.</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>
|
||||
|
||||
@@ -113,16 +129,16 @@
|
||||
"Data Source=testdb;" +
|
||||
"User ID=scott;" +
|
||||
"Password=tiger;";
|
||||
OracleConnection dbcon = null;
|
||||
IDbConnection dbcon;
|
||||
dbcon = new OracleConnection (connectionString);
|
||||
dbcon.Open ();
|
||||
OracleCommand dbcmd = dbcon.CreateCommand ();
|
||||
IDbCommand dbcmd = dbcon.CreateCommand ();
|
||||
string sql = "SELECT ename, job FROM scott.emp";
|
||||
dbcmd.CommandText = sql;
|
||||
OracleDataReader reader = dbcmd.ExecuteReader ();
|
||||
IDataReader reader = dbcmd.ExecuteReader ();
|
||||
while (reader.Read ()) {
|
||||
string employeeName = (string) reader["ename"];
|
||||
string job = (string) reader["job"];
|
||||
string employeeName = reader["ename"];
|
||||
string job = reader["job"];
|
||||
Console.WriteLine ("Employee Name: {0} Job: {1}",
|
||||
employeeName, job);
|
||||
}
|
||||
@@ -148,10 +164,12 @@
|
||||
-r System.Data.OracleClient.dll
|
||||
</pre>
|
||||
</li>
|
||||
<li>Build on Windows:
|
||||
<li>Build on Windows via Cygwin:
|
||||
<pre>
|
||||
mcs TestExample.cs /r:System.Data.dll \
|
||||
/r:System.Data.OracleClient.dll
|
||||
mono C:/cygwin/home/MyHome/mono/install/bin/mcs.exe \
|
||||
TestExample.cs \
|
||||
-lib:C:/cygwin/home/MyHome/mono/install/lib \
|
||||
-r System.Data.dll -r System.Data.OracleClient.dll
|
||||
</pre>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
@@ -10,8 +10,6 @@
|
||||
<li><a href="http://www.go-mono.pl">Mono Poland</a>:
|
||||
Mono site for polish users.
|
||||
|
||||
<li><a href="http://primates.ximian.com/~atsushi/mono-jp/">Mono Japanese Translation</a>:
|
||||
Mono site Japanese translation pages. Translated sources are maintained at <a href="http://forge.novell.com/modules/xfmod/project/?mono-jp">Novell Forge</a>.
|
||||
</ul>
|
||||
|
||||
* User sites
|
||||
|
||||
@@ -94,8 +94,3 @@
|
||||
href="http://citeseer.nj.nec.com/seligmann95incremental.html">
|
||||
Incremental Collection of Mature Objects: Richard Hudson, Eliot Moss</a>
|
||||
|
||||
* Threads
|
||||
|
||||
<a
|
||||
href="http://research.microsoft.com/~birrell/papers/ThreadsCSharp.pdf">
|
||||
Programming with Threads in C#: Andrew Birrell</a>
|
||||
@@ -1,246 +0,0 @@
|
||||
System.Object
|
||||
System.Exception
|
||||
System.ValueType
|
||||
System.Delegate
|
||||
System.MulticastDelegate
|
||||
System.Enum
|
||||
System.Activator
|
||||
System.ArgIterator
|
||||
System.__ComObject
|
||||
System.TypedReference
|
||||
System.Security.AllowPartiallyTrustedCallersAttribute
|
||||
System.Runtime.Serialization.Formatter
|
||||
System.Runtime.Serialization.FormatterConverter
|
||||
System.Runtime.Serialization.FormatterServices
|
||||
System.Runtime.Serialization.ObjectIDGenerator
|
||||
System.Runtime.Serialization.ObjectManager
|
||||
System.Reflection.ModuleResolveEventHandler
|
||||
System.Reflection.Pointer
|
||||
System.Globalization.CompareInfo
|
||||
System.Globalization.HebrewCalendar
|
||||
System.Globalization.HijriCalendar
|
||||
System.Globalization.JapaneseCalendar
|
||||
System.Globalization.KoreanCalendar
|
||||
System.Globalization.SortKey
|
||||
System.Globalization.StringInfo
|
||||
System.Globalization.TaiwanCalendar
|
||||
System.Globalization.TextElementEnumerator
|
||||
System.Globalization.TextInfo
|
||||
System.Globalization.ThaiBuddhistCalendar
|
||||
System.IO.IsolatedStorage.IsolatedStorageFile
|
||||
System.Reflection.Emit.MethodRental
|
||||
System.Runtime.CompilerServices.AccessedThroughPropertyAttribute
|
||||
System.Runtime.CompilerServices.CallConvCdecl
|
||||
System.Runtime.CompilerServices.CallConvStdcall
|
||||
System.Runtime.CompilerServices.CallConvThiscall
|
||||
System.Runtime.CompilerServices.CallConvFastcall
|
||||
System.Runtime.CompilerServices.CustomConstantAttribute
|
||||
System.Runtime.CompilerServices.DateTimeConstantAttribute
|
||||
System.Runtime.CompilerServices.DiscardableAttribute
|
||||
System.Runtime.CompilerServices.DecimalConstantAttribute
|
||||
System.Runtime.CompilerServices.CompilationRelaxationsAttribute
|
||||
System.Runtime.CompilerServices.CompilerGlobalScopeAttribute
|
||||
System.Runtime.CompilerServices.IDispatchConstantAttribute
|
||||
System.Runtime.CompilerServices.IsVolatile
|
||||
System.Runtime.CompilerServices.IUnknownConstantAttribute
|
||||
System.Runtime.CompilerServices.RequiredAttributeAttribute
|
||||
System.Runtime.InteropServices.ArrayWithOffset
|
||||
System.Runtime.InteropServices.DispIdAttribute
|
||||
System.Runtime.InteropServices.ClassInterfaceType
|
||||
System.Runtime.InteropServices.ClassInterfaceAttribute
|
||||
System.Runtime.InteropServices.ComVisibleAttribute
|
||||
System.Runtime.InteropServices.LCIDConversionAttribute
|
||||
System.Runtime.InteropServices.ComRegisterFunctionAttribute
|
||||
System.Runtime.InteropServices.ComUnregisterFunctionAttribute
|
||||
System.Runtime.InteropServices.ProgIdAttribute
|
||||
System.Runtime.InteropServices.ImportedFromTypeLibAttribute
|
||||
System.Runtime.InteropServices.IDispatchImplType
|
||||
System.Runtime.InteropServices.IDispatchImplAttribute
|
||||
System.Runtime.InteropServices.ComSourceInterfacesAttribute
|
||||
System.Runtime.InteropServices.ComConversionLossAttribute
|
||||
System.Runtime.InteropServices.TypeLibTypeFlags
|
||||
System.Runtime.InteropServices.TypeLibFuncFlags
|
||||
System.Runtime.InteropServices.TypeLibVarFlags
|
||||
System.Runtime.InteropServices.TypeLibTypeAttribute
|
||||
System.Runtime.InteropServices.TypeLibFuncAttribute
|
||||
System.Runtime.InteropServices.TypeLibVarAttribute
|
||||
System.Runtime.InteropServices.ComImportAttribute
|
||||
System.Runtime.InteropServices.PreserveSigAttribute
|
||||
System.Runtime.InteropServices.ComAliasNameAttribute
|
||||
System.Runtime.InteropServices.AutomationProxyAttribute
|
||||
System.Runtime.InteropServices.PrimaryInteropAssemblyAttribute
|
||||
System.Runtime.InteropServices.CoClassAttribute
|
||||
System.Runtime.InteropServices.ComEventInterfaceAttribute
|
||||
System.Runtime.InteropServices.COMException
|
||||
System.Runtime.InteropServices.ComMemberType
|
||||
System.Runtime.InteropServices.CurrencyWrapper
|
||||
System.Runtime.InteropServices.DispatchWrapper
|
||||
System.Runtime.InteropServices.ErrorWrapper
|
||||
System.Runtime.InteropServices.ExtensibleClassFactory
|
||||
System.Runtime.InteropServices.HandleRef
|
||||
System.Runtime.InteropServices.InvalidComObjectException
|
||||
System.Runtime.InteropServices.InvalidOleVariantTypeException
|
||||
System.Runtime.InteropServices.TypeLibImporterFlags
|
||||
System.Runtime.InteropServices.ExporterEventKind
|
||||
System.Runtime.InteropServices.ITypeLibExporterNotifySink
|
||||
System.Runtime.InteropServices.ITypeLibConverter
|
||||
System.Runtime.InteropServices.MarshalDirectiveException
|
||||
System.Runtime.InteropServices.ObjectCreationDelegate
|
||||
System.Runtime.InteropServices.RuntimeEnvironment
|
||||
System.Runtime.InteropServices.RegistrationServices
|
||||
System.Runtime.InteropServices.SafeArrayRankMismatchException
|
||||
System.Runtime.InteropServices.SafeArrayTypeMismatchException
|
||||
System.Runtime.InteropServices.SEHException
|
||||
System.Runtime.InteropServices.TypeLibConverter
|
||||
System.Runtime.InteropServices.BIND_OPTS
|
||||
System.Runtime.InteropServices.UCOMIBindCtx
|
||||
System.Runtime.InteropServices.UCOMIConnectionPointContainer
|
||||
System.Runtime.InteropServices.UCOMIConnectionPoint
|
||||
System.Runtime.InteropServices.UCOMIEnumMoniker
|
||||
System.Runtime.InteropServices.CONNECTDATA
|
||||
System.Runtime.InteropServices.UCOMIEnumConnections
|
||||
System.Runtime.InteropServices.UCOMIEnumConnectionPoints
|
||||
System.Runtime.InteropServices.UCOMIEnumString
|
||||
System.Runtime.InteropServices.UCOMIEnumVARIANT
|
||||
System.Runtime.InteropServices.FILETIME
|
||||
System.Runtime.InteropServices.UCOMIMoniker
|
||||
System.Runtime.InteropServices.UCOMIPersistFile
|
||||
System.Runtime.InteropServices.UCOMIRunningObjectTable
|
||||
System.Runtime.InteropServices.STATSTG
|
||||
System.Runtime.InteropServices.UCOMIStream
|
||||
System.Runtime.InteropServices.DESCKIND
|
||||
System.Runtime.InteropServices.BINDPTR
|
||||
System.Runtime.InteropServices.UCOMITypeComp
|
||||
System.Runtime.InteropServices.TYPEKIND
|
||||
System.Runtime.InteropServices.TYPEFLAGS
|
||||
System.Runtime.InteropServices.IMPLTYPEFLAGS
|
||||
System.Runtime.InteropServices.TYPEATTR
|
||||
System.Runtime.InteropServices.FUNCDESC
|
||||
System.Runtime.InteropServices.IDLFLAG
|
||||
System.Runtime.InteropServices.IDLDESC
|
||||
System.Runtime.InteropServices.PARAMFLAG
|
||||
System.Runtime.InteropServices.PARAMDESC
|
||||
System.Runtime.InteropServices.TYPEDESC
|
||||
System.Runtime.InteropServices.ELEMDESC
|
||||
System.Runtime.InteropServices.VARDESC
|
||||
System.Runtime.InteropServices.DISPPARAMS
|
||||
System.Runtime.InteropServices.EXCEPINFO
|
||||
System.Runtime.InteropServices.FUNCKIND
|
||||
System.Runtime.InteropServices.INVOKEKIND
|
||||
System.Runtime.InteropServices.CALLCONV
|
||||
System.Runtime.InteropServices.FUNCFLAGS
|
||||
System.Runtime.InteropServices.VARFLAGS
|
||||
System.Runtime.InteropServices.UCOMITypeInfo
|
||||
System.Runtime.InteropServices.SYSKIND
|
||||
System.Runtime.InteropServices.LIBFLAGS
|
||||
System.Runtime.InteropServices.TYPELIBATTR
|
||||
System.Runtime.InteropServices.UCOMITypeLib
|
||||
System.Runtime.InteropServices.UnknownWrapper
|
||||
System.Runtime.Remoting.IObjectHandle
|
||||
System.Runtime.Remoting.IRemotingTypeInfo
|
||||
System.Runtime.Remoting.IChannelInfo
|
||||
System.Runtime.Remoting.IEnvoyInfo
|
||||
System.Runtime.Remoting.RemotingConfiguration
|
||||
System.Runtime.Remoting.TypeEntry
|
||||
System.Runtime.Remoting.ActivatedClientTypeEntry
|
||||
System.Runtime.Remoting.ActivatedServiceTypeEntry
|
||||
System.Runtime.Remoting.WellKnownClientTypeEntry
|
||||
System.Runtime.Remoting.WellKnownServiceTypeEntry
|
||||
System.Runtime.Remoting.RemotingException
|
||||
System.Runtime.Remoting.ServerException
|
||||
System.Runtime.Remoting.RemotingTimeoutException
|
||||
System.Runtime.Remoting.RemotingServices
|
||||
System.Runtime.Remoting.InternalRemotingServices
|
||||
System.Runtime.Remoting.SoapServices
|
||||
System.Runtime.Remoting.Activation.UrlAttribute
|
||||
System.Runtime.Remoting.Messaging.IMessageSink
|
||||
System.Runtime.Remoting.Messaging.AsyncResult
|
||||
System.Runtime.Remoting.Messaging.CallContext
|
||||
System.Runtime.Remoting.Messaging.ILogicalThreadAffinative
|
||||
System.Runtime.Remoting.Messaging.InternalMessageWrapper
|
||||
System.Runtime.Remoting.Messaging.IMethodCallMessage
|
||||
System.Runtime.Remoting.Messaging.MethodCallMessageWrapper
|
||||
System.Runtime.Remoting.Messaging.HeaderHandler
|
||||
System.Runtime.Remoting.Messaging.IMessageCtrl
|
||||
System.Runtime.Remoting.Messaging.IRemotingFormatter
|
||||
System.Runtime.Remoting.Messaging.ReturnMessage
|
||||
System.Runtime.Remoting.Messaging.MethodCall
|
||||
System.Runtime.Remoting.Messaging.ConstructionCall
|
||||
System.Runtime.Remoting.Messaging.MethodResponse
|
||||
System.Runtime.Remoting.Messaging.ConstructionResponse
|
||||
System.Runtime.Remoting.Messaging.MethodReturnMessageWrapper
|
||||
System.Runtime.Remoting.Messaging.OneWayAttribute
|
||||
System.Runtime.Remoting.Messaging.MessageSurrogateFilter
|
||||
System.Runtime.Remoting.Messaging.RemotingSurrogateSelector
|
||||
System.Runtime.Remoting.Contexts.CrossContextDelegate
|
||||
System.Runtime.Remoting.Contexts.ContextProperty
|
||||
System.Runtime.Remoting.Contexts.IContextPropertyActivator
|
||||
System.Runtime.Remoting.Contexts.IContributeClientContextSink
|
||||
System.Runtime.Remoting.Contexts.IContributeDynamicSink
|
||||
System.Runtime.Remoting.Contexts.IContributeEnvoySink
|
||||
System.Runtime.Remoting.Contexts.IContributeObjectSink
|
||||
System.Runtime.Remoting.Contexts.IContributeServerContextSink
|
||||
System.Runtime.Serialization.Formatters.InternalRM
|
||||
System.Runtime.Serialization.Formatters.InternalST
|
||||
System.Runtime.Serialization.Formatters.SoapMessage
|
||||
System.Runtime.Serialization.Formatters.SoapFault
|
||||
System.Runtime.Serialization.Formatters.ServerFault
|
||||
System.Runtime.Serialization.Formatters.Binary.BinaryFormatter
|
||||
System.Security.Cryptography.CryptoConfig
|
||||
System.Security.Cryptography.KeyedHashAlgorithm
|
||||
System.Security.Cryptography.HMACSHA1
|
||||
System.Security.Cryptography.MACTripleDES
|
||||
System.Security.Cryptography.MaskGenerationMethod
|
||||
System.Security.Cryptography.PasswordDeriveBytes
|
||||
System.Security.Cryptography.PKCS1MaskGenerationMethod
|
||||
System.Security.Cryptography.RC2
|
||||
System.Security.Cryptography.RC2CryptoServiceProvider
|
||||
System.Security.Cryptography.RSACryptoServiceProvider
|
||||
System.Security.Cryptography.RSAOAEPKeyExchangeDeformatter
|
||||
System.Security.Cryptography.RSAOAEPKeyExchangeFormatter
|
||||
System.Security.Cryptography.RSAPKCS1KeyExchangeDeformatter
|
||||
System.Security.Cryptography.RSAPKCS1KeyExchangeFormatter
|
||||
System.Security.Cryptography.RSAPKCS1SignatureDeformatter
|
||||
System.Security.Cryptography.RSAPKCS1SignatureFormatter
|
||||
System.Security.Cryptography.SHA1Managed
|
||||
System.Security.Cryptography.TripleDES
|
||||
System.Security.Cryptography.TripleDESCryptoServiceProvider
|
||||
System.Security.Permissions.EnvironmentPermission
|
||||
System.Security.Permissions.FileDialogPermission
|
||||
System.Security.Permissions.IsolatedStorageFilePermission
|
||||
System.Security.Permissions.PrincipalPermissionAttribute
|
||||
System.Security.Permissions.SecurityPermissionAttribute
|
||||
System.Security.Permissions.PublisherIdentityPermissionAttribute
|
||||
System.Security.Permissions.PublisherIdentityPermission
|
||||
System.Security.Permissions.ReflectionPermission
|
||||
System.Security.Permissions.RegistryPermission
|
||||
System.Security.Permissions.PrincipalPermission
|
||||
System.Security.Permissions.SiteIdentityPermission
|
||||
System.Security.Permissions.StrongNameIdentityPermission
|
||||
System.Security.Permissions.StrongNamePublicKeyBlob
|
||||
System.Security.Permissions.UIPermission
|
||||
System.Security.Permissions.UrlIdentityPermission
|
||||
System.Security.Permissions.ZoneIdentityPermission
|
||||
System.Security.Policy.ApplicationDirectory
|
||||
System.Security.Policy.ApplicationDirectoryMembershipCondition
|
||||
System.Security.Policy.FirstMatchCodeGroup
|
||||
System.Security.Policy.Hash
|
||||
System.Security.Policy.HashMembershipCondition
|
||||
System.Security.Policy.NetCodeGroup
|
||||
System.Security.Policy.PermissionRequestEvidence
|
||||
System.Security.Policy.Publisher
|
||||
System.Security.Policy.PublisherMembershipCondition
|
||||
System.Security.Policy.Site
|
||||
System.Security.Policy.SiteMembershipCondition
|
||||
System.Security.Policy.StrongName
|
||||
System.Security.Policy.StrongNameMembershipCondition
|
||||
System.Security.Policy.UnionCodeGroup
|
||||
System.Security.Policy.Url
|
||||
System.Security.Policy.UrlMembershipCondition
|
||||
System.Security.Policy.Zone
|
||||
System.Security.Policy.ZoneMembershipCondition
|
||||
System.Security.Principal.WindowsIdentity
|
||||
System.Security.Principal.WindowsImpersonationContext
|
||||
System.Security.Principal.WindowsPrincipal
|
||||
System.Threading.CompressedStack
|
||||
|
||||
-204
@@ -1,204 +0,0 @@
|
||||
* Writing performant .NET and Mono applications
|
||||
|
||||
The following document contains a few hints on how to improve
|
||||
the performance of your Mono/.NET applications.
|
||||
|
||||
These are just guidelines, and you should still profile your
|
||||
code to find the actual performance problems in your
|
||||
application. It is never a smart idea to make a change with the
|
||||
hopes of improving the performance of your code without first
|
||||
measuring. In general, these guidelines should serve as ideas
|
||||
to help you figure out `how can I make this method run faster'.
|
||||
|
||||
It is up to you to figure out, `Which method is running slowly.'
|
||||
|
||||
** Using the Mono profiler
|
||||
|
||||
So, how does one measure what method are running slowly? A profiler
|
||||
helps with this task. Mono includes a profiler that is built
|
||||
into the runtime system. You can invoke this profiler on your program
|
||||
by running with the --profile flag.
|
||||
|
||||
<pre>
|
||||
mono --profile program.exe
|
||||
</pre>
|
||||
|
||||
The above will instruct Mono to instrument your application
|
||||
for profiling. The default Mono profiler will record the time
|
||||
spent on a routine, the number of times the routine called,
|
||||
the memory consumed by each method broken down by invoker, and
|
||||
the total amount of memory consumed.
|
||||
|
||||
It does this by asking the JIT to insert a call to the profiler
|
||||
every time a method is entered or left. The profiler times the
|
||||
amount of time elapsed between the beginning and the end of the
|
||||
call. The profiler is also notified of allocations.
|
||||
|
||||
When the program has finished executing, the profiler prints the
|
||||
data in human readable format. It looks like:
|
||||
|
||||
<pre>
|
||||
Total time spent compiling 227 methods (sec): 0.07154
|
||||
Slowest method to compile (sec): 0.01893: System.Console::.cctor()
|
||||
Time(ms) Count P/call(ms) Method name
|
||||
########################
|
||||
91.681 1 91.681 .DebugOne::Main()
|
||||
Callers (with count) that contribute at least for 1%:
|
||||
1 100 % .DebugOne::Main(object,intptr,intptr)
|
||||
...
|
||||
Total number of calls: 3741
|
||||
...
|
||||
Allocation profiler
|
||||
Total mem Method
|
||||
########################
|
||||
406 KB .DebugOne::Main()
|
||||
406 KB 1000 System.Int32[]
|
||||
Callers (with count) that contribute at least for 1%:
|
||||
1 100 % .DebugOne::Main(object,intptr,intptr)
|
||||
Total memory allocated: 448 KB
|
||||
</pre>
|
||||
|
||||
At the top, it shows each method that is called. The data is sorted
|
||||
by the total time that the program spent within the method. Then
|
||||
it shows how many times the method was called, and the average time
|
||||
per call.
|
||||
|
||||
Below this, it shows the top callers of the method. This is very useful
|
||||
data. If you find, for example, that the method Data::Computate () takes
|
||||
a very long time to run, you can look to see if any of the calls can be
|
||||
avoided.
|
||||
|
||||
Two warnings must be given about the method data. First,
|
||||
the profiler has an overhead associated with it. As such,
|
||||
a high number of calls to a method may show up as comsuming
|
||||
lots of time, when in reality they do not consume much time
|
||||
at all. If you see a method that has a very high number of
|
||||
calls, you may be able to ignore it. However, do consider
|
||||
removing calls if possible, as that will sometimes help
|
||||
performance. This problem is often seen with the use
|
||||
of built in collection types.
|
||||
|
||||
Secondly, due to the nature of the profiler, recursive calls
|
||||
have extermely large times (because the profiler double counts
|
||||
when the method calls itself). One easy way to see this problem
|
||||
is that if a method is shown as taking more time than the Main
|
||||
method, it is very likely recursive, and causing this problem.
|
||||
|
||||
Below the method data, allocation data is shown. This shows
|
||||
how much memory each method allocates. The number beside
|
||||
the method is the total amount of memory. Below that, it
|
||||
is broken down into types. Then, the caller data is given. This
|
||||
data is again useful when you want to figure out how to eliminate calls.
|
||||
|
||||
You might want to keep a close eye on the memory consumption
|
||||
and on the method invocation counts. A lot of the
|
||||
performance gains in MCS for example came from reducing its
|
||||
memory usage, as opposed to changes in the execution path.
|
||||
|
||||
** Memory Management in the .NET/Mono world.
|
||||
|
||||
Since Mono and .NET offer automatic garbage collection, the
|
||||
programmer is freed from having to track and dispose the
|
||||
objects it consumes (except for IDispose-like classes). This
|
||||
is a great productivity gain, but if you create thousands of
|
||||
objects, that will make the garbage collector do more work,
|
||||
and it might slow down your application.
|
||||
|
||||
Remember, each time you allocate an object, the GC is forced
|
||||
to find space for the object. Each object has an 8 byte overhead
|
||||
(4 to tell what type it is, then 4 for a sync block). If
|
||||
the GC finds that it is running out of room, it will scan every
|
||||
object for pointers, looking for unreferenced objects. If you allocate
|
||||
extra objects, the GC then must take the effort to free the objects.
|
||||
|
||||
Mono uses the Boehm GC, which is a conservative collector,
|
||||
and this might lead to some memory fragmentation and unlike
|
||||
generational GC systems, it has to scan the entire allocated
|
||||
memory pool.
|
||||
|
||||
*** Boxing
|
||||
The .NET framework provides a rich hierchy of object types.
|
||||
Each object not only has value information, but also type
|
||||
information associated with it. This type information makes
|
||||
many types of programs easier to write. It also has a cost
|
||||
associated with it. The type information takes up space.
|
||||
|
||||
In order to reduce the cost of type information, almost every
|
||||
Object Oriented language has the concept of `primitatives'.
|
||||
They usually map to types such as integers and bools. These
|
||||
types do not have any type information associated with them.
|
||||
|
||||
However, the language also must be able to treat primitatives
|
||||
as first class datums -- in the class with objects. Languages
|
||||
handle this issue in different ways. Some choose to make a
|
||||
special class for each primative, and force the user to do an
|
||||
operation such as:
|
||||
<pre>
|
||||
// This is Java
|
||||
list.add (new Integer (1));
|
||||
System.out.println (list.get (1).intValue ());
|
||||
</pre>
|
||||
|
||||
The C# design team was not satisfied with this type
|
||||
of construct. They added a notion of `boxing' to the language.
|
||||
|
||||
Boxing preforms the same thing as Java's <code>new Integer (1)</code>.
|
||||
The user is not forced to write the extra code. However,
|
||||
behind the scenes the <em>same thing</em> is being done
|
||||
by the runtime. Each time a primative is cast to an object,
|
||||
a new object is allocated.
|
||||
|
||||
You must be careful when casting a primative to an object.
|
||||
Note that because it is an implicit conversion, you will
|
||||
not see it in your code. For example, boxing is happening here:
|
||||
|
||||
<pre>
|
||||
ArrayList foo = new ArrayList ();
|
||||
foo.Add (1);
|
||||
</pre>
|
||||
|
||||
In high performance code, this operation can be very costly.
|
||||
|
||||
*** Using structs instead of classes for small objects
|
||||
|
||||
For small objects, you might want to consider using value
|
||||
types (structs) instead of object (classes).
|
||||
|
||||
However, you must be careful that you do not use the struct
|
||||
as an object, in that case it will actually be more costly.
|
||||
|
||||
As a rule of thumb, only use structs if you have a small
|
||||
number of fields (totaling less than 32 bytes), and
|
||||
need to pass the item `by value'. You should not box the object.
|
||||
|
||||
*** Assisting the Garbage Collector
|
||||
|
||||
Although the Garbage Collector will do the right thing in
|
||||
terms of releasing and finalizing objects on time, you can
|
||||
assist the garbage collector by clearing the fields that
|
||||
points to objects. This means that some objects might be
|
||||
elegible for collection earlier than they would, this can help
|
||||
reduce the memory consumption and reduce the work that the GC
|
||||
has to do.
|
||||
|
||||
** foreach
|
||||
|
||||
The <tt>foreach</tt> C# statement handles various kinds of
|
||||
different constructs (about seven different code patterns are
|
||||
generated). Typically foreach generates more efficient code
|
||||
than loops constructed manually, and also ensures that objects
|
||||
which implement IDispose are properly released.
|
||||
|
||||
But foreach sometimes might generate code that under stress
|
||||
performs badly. Foreach performs badly when its used in tight
|
||||
loops, and its use leads to the creation of many enumerators.
|
||||
Although technically obtaining an enumerator for some objects
|
||||
like ArrayList is more efficient than using the ArrayList
|
||||
indexer, the pressure introduced due to the extra memory
|
||||
requirements and the demands on the garbage collector make it
|
||||
more inneficient.
|
||||
|
||||
There is no straight-forward rule on when to use foreach, and
|
||||
when to use a manual loop. The best thing to do is to always
|
||||
use foreach, and only when profile shows a problem, replace
|
||||
foreach with for loops.
|
||||
@@ -8,7 +8,7 @@
|
||||
|
||||
Currently you can read our plans for <a
|
||||
href="ado-net.html">ADO.NET</a>, <a
|
||||
href="asp-net.html">ASP.NET</a>, <a href="java.html">Java</a> and
|
||||
href="asp-net">ASP.NET</a>, <a href="java.html">Java</a> and
|
||||
<a href="winforms.html">WinForms</a>.
|
||||
|
||||
|
||||
|
||||
+8
-34
@@ -1,30 +1,12 @@
|
||||
* PostgreSQL and Mono
|
||||
* PostgreSQL Data Provider
|
||||
|
||||
When it comes to Mono and PostgreSQL, there are many ways
|
||||
you can handle your data. You have many Mono Data Providers which can be used
|
||||
to access data from a application written for Mono.
|
||||
Then there is the future goal of having the ability to host Mono within PostgreSQL to
|
||||
have the applications run on the server which makes things much faster.
|
||||
|
||||
* Hosting Mono in PostgreSQL
|
||||
|
||||
There is a project to <a href="http://gborg.postgresql.org/project/plmono/projdisplay.php">host Mono within PostgreSQL</a>.
|
||||
|
||||
plMono is a PostgreSQL language using the embedded Mono runtime. It provides support for writing functions in C#, or any other language that supports .NET.
|
||||
|
||||
* Data Providers
|
||||
|
||||
There are many ADO.NET data providers for <a href="http://www.postgresql.org/">PostgreSQL</a>:
|
||||
|
||||
There are two providers created specifically for PostgreSQL included with Mono:
|
||||
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>included with Mono</li>
|
||||
|
||||
<li>a .NET Managed Data Provider for PostgreSQL</li>
|
||||
<li>a .NET Managed Data Provider for PostgreSQL
|
||||
|
||||
<li>Written in 100% C#</li>
|
||||
|
||||
@@ -43,8 +25,6 @@
|
||||
|
||||
<li>Mono.Data.PostgreSQL (deprecated)
|
||||
<ul>
|
||||
<li>included with Mono</li>
|
||||
|
||||
<li>Deprecated in favor of Npgsql</li>
|
||||
|
||||
<li>Exists in namespace Mono.Data.PostgreSql and assembly Mono.Data.PostgreSql</li>
|
||||
@@ -57,12 +37,6 @@
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
<li><a href="http://sourceforge.net/projects/mysqlnet/">ByteFX.Data</a> has a provider for PostgreSQL too, but I do not know how well it works with Mono.</li>
|
||||
|
||||
<li>There is another .NET data provider for PostgreSQL named <a href="http://sourceforge.net/projects/pgsqlclient/">PgSqlClient</a>, but I do not know if it works with Mono.</li>
|
||||
|
||||
<li>If none of the above providers meet your needs. There is the ODBC and OLEDB providers included with Mono.</li>
|
||||
|
||||
<li>Bugs with Mono or the data provider should be reported
|
||||
in Mono's Bugzilla <a href="http://bugzilla.ximian.com/">here</a>. If you
|
||||
do not have Bugzilla user account, it is free
|
||||
@@ -476,8 +450,8 @@ mono PostgresTest.exe
|
||||
dbcmd.CommandText = sql;
|
||||
IDataReader reader = dbcmd.ExecuteReader();
|
||||
while(reader.Read()) {
|
||||
string FirstName = (string) reader["firstname"];
|
||||
string LastName = (string) reader["lastname"];
|
||||
string FirstName = reader["firstname"];
|
||||
string LastName = reader["lastname"];
|
||||
Console.WriteLine("Name: " +
|
||||
FirstName + " " + LastName);
|
||||
}
|
||||
@@ -545,8 +519,8 @@ mono TestExample.exe
|
||||
"User ID=postgres;" +
|
||||
"Password=fun2db;";
|
||||
IDbConnection dbcon;
|
||||
dbcon = new NpgsqlConnection(connectionString);
|
||||
dbcon.Open();
|
||||
dbcon = new NpgsqlConnection(connectionString);
|
||||
IDbCommand dbcmd = dbcon.CreateCommand();
|
||||
// requires a table to be created named employee
|
||||
// with columns firstname and lastname
|
||||
@@ -560,8 +534,8 @@ mono TestExample.exe
|
||||
dbcmd.CommandText = sql;
|
||||
IDataReader reader = dbcmd.ExecuteReader();
|
||||
while(reader.Read()) {
|
||||
string FirstName = (string) reader["firstname"];
|
||||
string LastName = (string) reader["lastname"];
|
||||
string FirstName = reader["firstname"];
|
||||
string LastName = reader["lastname"];
|
||||
Console.WriteLine("Name: " +
|
||||
FirstName + " " + LastName);
|
||||
}
|
||||
|
||||
@@ -13,9 +13,7 @@
|
||||
|
||||
*** Jitter
|
||||
|
||||
Works on MacOS X 10.2 and Linux/PPC.
|
||||
|
||||
There are known problems on MacOS 10.3
|
||||
Start the port
|
||||
|
||||
** Documentation
|
||||
|
||||
@@ -30,6 +28,6 @@
|
||||
|
||||
*** Calling conventions:
|
||||
|
||||
<a href="http://refspecs.freestandards.org/elf/elfspec_ppc.pdf">The PowerPC SystemV ABI specification</a>
|
||||
<a href="http://www.esofta.com/softspecs.html">The PowerPC SystemV ABI specification</a>
|
||||
|
||||
|
||||
@@ -10,6 +10,8 @@
|
||||
|
||||
** EOG component
|
||||
|
||||
** XmlStorageSystem component
|
||||
|
||||
* Gtk# related projects
|
||||
|
||||
Gnome Canvas Bindings.
|
||||
|
||||
+17
-4
@@ -9,7 +9,7 @@
|
||||
|
||||
** Microsoft .NET
|
||||
|
||||
The <a href="http://msdn.microsoft.com/netframework">Microsoft.NET site.</a>
|
||||
The <a href="http://msdn.microsoft.com/net">Microsoft.NET site.</a>
|
||||
|
||||
The Microsoft .NET Framework can be downloaded <a
|
||||
href="http://msdn.microsoft.com/library/default.asp?url=/downloads/list/netdevframework.asp">here</a>
|
||||
@@ -74,13 +74,21 @@
|
||||
<li><a href="http://www.gotdotnet.com/userarea/keywordsrch.aspx?keyword=winchurn">http://www.gotdotnet.com/userarea/keywordsrch.aspx?keyword=winchurn</a>
|
||||
</ul>
|
||||
|
||||
** Presentations
|
||||
|
||||
Currently the <a href="Presentations/O-Reilly">O'Reilly</a>
|
||||
presentation on Mono is available. Arturo Espinosa has given
|
||||
a talk on Mono in Mexico and made <a
|
||||
href="http://construct.ximian.com/~arturo/Presentations/Mono.OLS/html">spanish
|
||||
slides</a>
|
||||
|
||||
** ECMA Documentation.
|
||||
|
||||
You can get the documentation for the ECMA specs from:
|
||||
|
||||
<ul>
|
||||
* <a href="http://www.ecma-international.org/publications/standards/Ecma-334.HTM">C# Language Specification</a>
|
||||
* <a href="http://www.ecma-international.org/publications/standards/Ecma-335.HTM">Common Language Infrastructure</a>
|
||||
* <a href="http://www.ecma-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>
|
||||
</ul>
|
||||
|
||||
|
||||
@@ -89,6 +97,7 @@
|
||||
<ul>
|
||||
* <a href="http://msdn.microsoft.com/net/ecma">At MSDN</a>
|
||||
* <a href="http://www.dotnetexperts.com">Dot Net Experts</a>
|
||||
* <a href="http://developer.intel.com/software/idap/ecma">Intel</a>
|
||||
* <a href="http://lightning.csse.monash.edu.au/.net/CLI">Monash University</a>
|
||||
</ul>
|
||||
|
||||
@@ -144,7 +153,7 @@
|
||||
|
||||
<li><b>Class Libraries</b></li>
|
||||
<ul>
|
||||
* <a href="http://cs-sdl.sourceforge.net/">SDL for
|
||||
* <a href="http://9mm.com/~ogl/sdldotnet/">SDL for
|
||||
.NET:</a> Bindings for the popular SDL graphics library.
|
||||
|
||||
|
||||
@@ -184,6 +193,10 @@
|
||||
* <a
|
||||
href="http://www.southern-storm.com.au/portable_net.html">Portable.NET:</a>
|
||||
Another implementation of the CLI and C# compiler.
|
||||
|
||||
* A Free (GFDL) tutorial on C# in Spanish with
|
||||
examples, slides, and extras (under development). Get it <a
|
||||
href="http://geneura.ugr.es/~jaime/csharp/">here</a>.
|
||||
</ul>
|
||||
|
||||
** GNOME Documentation
|
||||
|
||||
+1
-1
@@ -19,7 +19,7 @@
|
||||
We are using the Boehm conservative garbage collector.
|
||||
|
||||
The Mono runtime can be used as a stand-alone process, or it
|
||||
can be <a href="embedded-api.html">embedded into applications</a> (see
|
||||
can be <a href="embedded-api">embedded into applications</a> (see
|
||||
the documentation in mono/samples/embed for more details).
|
||||
|
||||
Embedding the Mono runtime allows applications to be extended
|
||||
|
||||
+11
-19
@@ -31,14 +31,11 @@
|
||||
|
||||
|
||||
<ul>
|
||||
<li>Thanks to Sebastien Pouliot, we now have NT Authentication (Integrated Security) support. This support was
|
||||
added after the release of Mono 0.29. So, you either get it from cvs or wait for the Mono 0.30 release.</li>
|
||||
|
||||
<li>Able to connect to Microsoft SQL Server 7/2000 databases via SQL Server authentication and NT Authentication.</li>
|
||||
<li>Able to connect to Microsoft SQL Server 7/2000 databases</li>
|
||||
|
||||
<li>Connection pooling works.</li>
|
||||
|
||||
<li>Stored Procedures work.</li>
|
||||
<li>Stored Procedures work</li>
|
||||
|
||||
<li>Parameters work.</li>
|
||||
|
||||
@@ -62,6 +59,8 @@
|
||||
|
||||
<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>
|
||||
|
||||
@@ -72,9 +71,9 @@
|
||||
|
||||
<li>Needs more testing</li>
|
||||
|
||||
<li>Start work on TDS Protocol Version 8.0 support</li>
|
||||
<li>Would like to figure out how to connect via Trusted_Connection or Integrated Security</li>
|
||||
|
||||
<li>Add support for .NET 1.2 and 2.0 and Microsoft SQL Server (Yukon) support</li>
|
||||
<li>Start work on TDS Protocol Version 8.0 support</li>
|
||||
|
||||
</ul>
|
||||
|
||||
@@ -90,10 +89,9 @@
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
<li><b>IMPORTANT:</b> If using Microsoft SQL Server 2000, make sure
|
||||
<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. You
|
||||
can get it from <a href="http://www.microsoft.com/sql/downloads/2000/sp3.asp">here</a></li>
|
||||
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)
|
||||
@@ -123,17 +121,11 @@
|
||||
to explicitly use a User ID and Password
|
||||
authenticated by SQL Server.</li>
|
||||
|
||||
<li>Has a connection string format for SQL Server Authentication:
|
||||
<li>Has a connection string format:
|
||||
<pre>
|
||||
Server=hostname;Database=databaseName;User ID=userid;Password=password
|
||||
</pre>
|
||||
</li>
|
||||
<li>Has a connection string format for NT Authentication:
|
||||
<pre>
|
||||
Server=hostname;Database=databaseName;User ID=windowsUserid;Password=windowsPassword;Integrated Security=SSPI
|
||||
</pre>
|
||||
</li>
|
||||
|
||||
<li>The Server part can be used three ways:
|
||||
|
||||
<table border=1>
|
||||
@@ -180,8 +172,8 @@
|
||||
dbcmd.CommandText = sql;
|
||||
IDataReader reader = dbcmd.ExecuteReader();
|
||||
while(reader.Read()) {
|
||||
string FirstName = (string) reader["fname"];
|
||||
string LastName = (string) reader["lname"];
|
||||
string FirstName = reader["fname"];
|
||||
string LastName = reader["lname"];
|
||||
Console.WriteLine("Name: " +
|
||||
FirstName + " " + LastName);
|
||||
}
|
||||
|
||||
+4
-4
@@ -25,7 +25,7 @@
|
||||
<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>
|
||||
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
|
||||
@@ -82,7 +82,7 @@
|
||||
{
|
||||
string connectionString = "URI=file:SqliteTest.db";
|
||||
IDbConnection dbcon;
|
||||
dbcon = new SqliteConnection(connectionString);
|
||||
dbcon = new MySQLConnection(connectionString);
|
||||
dbcon.Open();
|
||||
IDbCommand dbcmd = dbcon.CreateCommand();
|
||||
// requires a table to be created named employee
|
||||
@@ -97,8 +97,8 @@
|
||||
dbcmd.CommandText = sql;
|
||||
IDataReader reader = dbcmd.ExecuteReader();
|
||||
while(reader.Read()) {
|
||||
string FirstName = (string) reader[0];
|
||||
string LastName = (string) reader[1];
|
||||
string FirstName = reader[0];
|
||||
string LastName = reader[1];
|
||||
Console.WriteLine("Name: " +
|
||||
FirstName + " " + LastName);
|
||||
}
|
||||
|
||||
+4
-2
@@ -17,6 +17,8 @@
|
||||
<li>Requires the assembly Mono.Data.Tds.dll which implements the TDS protocol in 100% C#.</li>
|
||||
|
||||
<li>Uses TDS Protocol Version 5.0</li>
|
||||
|
||||
<li>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
|
||||
@@ -108,8 +110,8 @@
|
||||
dbcmd.CommandText = sql;
|
||||
IDataReader reader = dbcmd.ExecuteReader();
|
||||
while(reader.Read()) {
|
||||
string FirstName = (string) reader["fname"];
|
||||
string LastName = (string) reader["lname"];
|
||||
string FirstName = reader["fname"];
|
||||
string LastName = reader["lname"];
|
||||
Console.WriteLine("Name: " +
|
||||
FirstName + " " + LastName);
|
||||
}
|
||||
|
||||
+4
-2
@@ -18,6 +18,8 @@
|
||||
|
||||
<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
|
||||
@@ -113,8 +115,8 @@
|
||||
dbcmd.CommandText = sql;
|
||||
IDataReader reader = dbcmd.ExecuteReader();
|
||||
while(reader.Read()) {
|
||||
string FirstName = (string) reader["fname"];
|
||||
string LastName = (string) reader["lname"];
|
||||
string FirstName = reader["fname"];
|
||||
string LastName = reader["lname"];
|
||||
Console.WriteLine("Name: " +
|
||||
FirstName + " " + LastName);
|
||||
}
|
||||
|
||||
+4
-126
@@ -6,26 +6,7 @@
|
||||
is very common to introduce bugs in existing code. A test suite
|
||||
helps us fix the bugs as soon as they are introduced.
|
||||
|
||||
There are various kinds of tests in Mono:
|
||||
<ul>
|
||||
<li><a href="#unit"><b>Class Library Unit
|
||||
Tests:</b></a> These are used to test the class
|
||||
libraries.
|
||||
|
||||
<li><a href="#compiler"><b>Compiler tests</b></a>: Both
|
||||
tests that should pass and tests that should fail are included.
|
||||
|
||||
<li><a href="#runtime"><b>Runtime tests</b></a>: Tests for
|
||||
the virtual machine.
|
||||
|
||||
<li><a href="#aspnet"><b>ASP.NET tests</b></a>: ASP.NET tests.
|
||||
|
||||
<li><a href="#ws"><b>Web Services tests</b></a>: Web Services
|
||||
client/server tests.
|
||||
</ul>
|
||||
|
||||
<a name="unit"></a>
|
||||
* Class Library Tests
|
||||
** Class Library Tests
|
||||
|
||||
All classes in Mono libraries should have comprehensive unit test
|
||||
suites to go with them. Unit testing is a software engineering
|
||||
@@ -34,29 +15,6 @@
|
||||
that they work correctly. Mono also needs a testing framework
|
||||
to make it easy to write and run lots of tests.
|
||||
|
||||
In some classes, we might also provide standalone tests because of
|
||||
some reasons such as too huge testcases, another downloading and so on.
|
||||
(For example, managed XSLT has standalone test which downloads and
|
||||
expands some megabytes of OASIS test suite.)
|
||||
|
||||
Here I list them up as long as I know. If you are going to add another
|
||||
standalone tests, please add one line here. It is also recommended that
|
||||
you add some notes on how to build and run tests.
|
||||
|
||||
<ul>
|
||||
|
||||
* Mono.Data/test/
|
||||
* System.Data/Test, and some individual ADO.NET libraries:
|
||||
there are some standalone tests. See the bottom of <a href="ado-net.html">
|
||||
ADO.NET page</a> for detail.
|
||||
* System.Web/Test/TestMonoWeb : see README
|
||||
* System.Web.Services/Test/standalone : see README
|
||||
* System.Windows.Forms/SWFTest/
|
||||
* System.XML/Tests/System.Xml.Schema/standalone_tests : see README
|
||||
* System.XML/System.Xml.Serialization/standalone_tests/
|
||||
* System.XML/Tests/System.Xml.Xsl/standalone_tests : see README
|
||||
|
||||
</ul>
|
||||
|
||||
** Getting started
|
||||
|
||||
@@ -84,8 +42,8 @@
|
||||
testing.
|
||||
|
||||
Once all of that is done, you can do a 'make test' from the top mcs
|
||||
directory. Your test class needs also to be listed in the
|
||||
.sources file at the top of the Test directory.
|
||||
directory. Your test class will be automagically included in the
|
||||
build and the tests will be run along with all the others.
|
||||
|
||||
* Tips on writing Unit tests.
|
||||
|
||||
@@ -154,7 +112,7 @@
|
||||
bug in their runtime or something is misleading or wrong in their
|
||||
documentation. In this case, please put a detailed description of the
|
||||
problem to mcs/class/doc/API-notes and do also report it to the
|
||||
<a href="mailing-lists.html">mailing list</a> - we'll forward this to the
|
||||
<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.
|
||||
|
||||
@@ -187,83 +145,3 @@
|
||||
Normally, after you send a couple of well-written new files
|
||||
and/or patches to the list, you will be given cvs access.
|
||||
|
||||
<a name="compiler"></a>
|
||||
* Compiler tests
|
||||
|
||||
Mono ships with three compilers: C#, VB.NET and JScript. The
|
||||
tests are ran by running the makefile target `make
|
||||
run-test-local' in the appropriate directory.
|
||||
|
||||
The C# compilation tests live in mcs/tests, and the C# error
|
||||
tests live in mcs/errors.
|
||||
|
||||
The VB.NET compilation tests live in mcs/btests.
|
||||
|
||||
<a name="runtime"></a>
|
||||
* Runtime Tests
|
||||
|
||||
These tests verify the virtual machine, to run these tests, do:
|
||||
|
||||
<pre>
|
||||
cd mono/mono/tests
|
||||
make test
|
||||
</pre>
|
||||
|
||||
<a name="aspnet"></a>
|
||||
* ASP.NET tests
|
||||
|
||||
XSP, the Mono ASP.NET server has tests for ASP.NET pages. It uses
|
||||
<a href="http://nunitasp.sourceforge.net">NUnitAsp</a>. Right now
|
||||
it only has standalone tests, ie., tests that do not need their own
|
||||
global.asax or web.config files.
|
||||
|
||||
If you want to run them, get the xsp CVS module and install it. Then:
|
||||
<pre>
|
||||
cd xsp/nunit-tests
|
||||
make
|
||||
cd standalone
|
||||
xsp
|
||||
</pre>
|
||||
|
||||
And from another terminal:
|
||||
<pre>
|
||||
cd xsp/nunit-tests/standalone
|
||||
nunit-console standalone-tests.dll
|
||||
</pre>
|
||||
|
||||
<a name="ws"></a>
|
||||
* Web Services tests
|
||||
|
||||
The Test directory for the System.Web.Services assembly contains a
|
||||
standalone test suite for testing web services. It tests:
|
||||
|
||||
<ul>
|
||||
<li>Proxy generation using the wsdl tool</li>
|
||||
<li>Access to web services using the generated client proxies</li>
|
||||
<li>Execution of web services in the server</li>
|
||||
</ul>
|
||||
|
||||
This suite not only tests web services running on XSP, but it can also test
|
||||
services running on other platforms and that are available in internet. This
|
||||
will help track down interoperability issues.
|
||||
|
||||
To build the test suite, just run:
|
||||
|
||||
<pre>
|
||||
cd mcs/class/System.Web.Services/Test/standalone
|
||||
xsp --root server
|
||||
</pre>
|
||||
|
||||
And from another terminal:
|
||||
<pre>
|
||||
cd mcs/class/System.Web.Services/Test/standalone
|
||||
make
|
||||
nunit-console testclient.dll
|
||||
</pre>
|
||||
|
||||
This will download the wsdl documents, generate the proxies, build a dll with
|
||||
the proxies, and build the nunit tests. Then you can use nunit-console or
|
||||
gnunit to run the tests (the nunit dll is testclient.dll).
|
||||
|
||||
Read the README file in mcs/class/System.Web.Services/Test/standalone for
|
||||
more info.
|
||||
@@ -1,53 +1 @@
|
||||
** System.Windows.Forms
|
||||
|
||||
Progress on Windows.Forms has been good, but we need more work
|
||||
on this area. Currently redrawing of controls is not
|
||||
funcional.
|
||||
|
||||
** Languages work
|
||||
|
||||
Mono has work-in-progress implementations of JScript and the
|
||||
VB.NET languages
|
||||
|
||||
<ul>
|
||||
<li>Write positive tests for those languages.
|
||||
|
||||
<li>Write negative tests for those languages.
|
||||
|
||||
<li>Mono-devel-list is the mailing list to discuss
|
||||
improvements and fixes to those compilers.
|
||||
</ul>
|
||||
|
||||
** Debugger
|
||||
|
||||
<ul>
|
||||
<li>The Mono debugger needs some better widgets to
|
||||
provide a useful environment, many of those have been
|
||||
authored for Anjuta/gIDE, we should wrap those for the
|
||||
debugger
|
||||
|
||||
<li>Design a small tool-command-language like Tcl to
|
||||
build the debugger on top of it.
|
||||
|
||||
<li>Design work: a new UI design must be done
|
||||
for the debugger and later implemented.
|
||||
</ul>
|
||||
|
||||
** Research topics
|
||||
|
||||
<ul>
|
||||
<li>Design and implement a command processor like the
|
||||
Unix shell, but which uses .NET objects as commands.
|
||||
This shell would be a CLS consumer ideally, and only
|
||||
later a CLS producer. This should make it simple for
|
||||
people to explore the .NET API interactively.
|
||||
</ul>
|
||||
|
||||
** IDE development
|
||||
|
||||
Mono lacks an IDE, and we depend on third-parties to work on
|
||||
these.
|
||||
|
||||
<ul>
|
||||
Sharp
|
||||
</ul>
|
||||
Discuss with write new JIT
|
||||
+1
-9
@@ -1,12 +1,10 @@
|
||||
0,Home,index.html,index.src
|
||||
1,Roadmap,mono-roadmap.html
|
||||
1,FAQ,faq.html,faq.src
|
||||
1,News archive,http://monoevo.sf.net/mwn/archives.html
|
||||
1,Screenshots,screenshots.html,screenshots.src
|
||||
1,Team,team.html,team.src
|
||||
1,Other sites,other.html,other.src
|
||||
1,Old News,oldnews.html,oldnews.src
|
||||
1,Bug Reporting,bugs.html,bugs.src
|
||||
0,Mono,rationale.html,rationale.src
|
||||
1,Runtime,runtime.html,runtime.src
|
||||
2,Embedding,embedded-api.html,embedded-api.src
|
||||
@@ -19,8 +17,6 @@
|
||||
0,Download,download.html,download.src
|
||||
1,CVS access,ccvs.html,ccvs.src
|
||||
1,AnonCVS access,anoncvs.html,anoncvs.src
|
||||
1,Forge,forge.html,forge.src
|
||||
1,Compiling,compiling.html,compiling.src
|
||||
0,Contributing,contributing.html,contributing.src
|
||||
1,Hackers,hackers.html,hackers.src
|
||||
1,Documentation,documentation.html,documentation.src
|
||||
@@ -34,7 +30,6 @@
|
||||
0,Resources,resources.html,resources.src
|
||||
1,Beginning,mono-beginning.html,mono-beginning.src
|
||||
1,Mailing Lists,mailing-lists.html,mailing-lists.src
|
||||
1,Blogs,http://www.go-mono.com/monologue/
|
||||
1,Ideas,ideas.html,ideas.src
|
||||
1,Passport,passport.html,passport.src
|
||||
1,Books,books.html,books.src
|
||||
@@ -42,7 +37,6 @@
|
||||
1,Languages,languages.html,languages.src
|
||||
1,Debugging,jit-debug.html,jit-debug.src
|
||||
0,Plans,plans.html,plans.src
|
||||
1,Drawing,drawing.html,drawing.src
|
||||
1,ADO.NET,ado-net.html,ado-net.src
|
||||
2,ProviderFactory,provider-factory.html,provider-factory.src
|
||||
2,Firebird Interbase,firebird.html,firebird.src
|
||||
@@ -56,11 +50,9 @@
|
||||
2,SQL Lite,sqlite.html,sqlite.src
|
||||
2,Sybase,sybase.html,sybase.src
|
||||
2,TDS Generic,tdsclient.html,tdsclient.src
|
||||
2,TDS Providers,tds-providers.html,tds-providers.src
|
||||
1,Crypto,crypto.html,crypto.src
|
||||
1,Java,java.html,java.src
|
||||
1,Windows.Forms,winforms.html,winforms.src
|
||||
1,XML Classes,xml-classes.html,xml-classes.src
|
||||
0,Class Status,class-status.html,class-status.src,cm/cormissing.css,cm/cormissing.js
|
||||
1,corlib,class-status-corlib.html,class-status-corlib.src,cm/cormissing.css,cm/cormissing.js
|
||||
1,System,class-status-System.html,class-status-System.src,cm/cormissing.css,cm/cormissing.js
|
||||
@@ -71,7 +63,7 @@
|
||||
1,Web.Services,class-status-System.Web.Services.html,class-status-System.Web.Services.src,cm/cormissing.css,cm/cormissing.js
|
||||
1,Microsoft.VisualBasic,class-status-Microsoft.VisualBasic.html,class-status-Microsoft.VisualBasic.src,cm/cormissing.css,cm/cormissing.js
|
||||
1,Windows.Forms,class-status-System.Windows.Forms.html,class-status-System.Windows.Forms.src,cm/cormissing.css,cm/cormissing.js
|
||||
1,DirectoryServices,class-status-System.DirectoryServices.html,class-status-System.DirectoryServices.src,cm/cormissing.css,cm/cormissing.js
|
||||
1,EnterpriseServices,class-status-System.EnterpriseServices.html,class-status-System.EnterpriseServices.src,cm/cormissing.css,cm/cormissing.js
|
||||
1,Formatters.Soap,class-status-System.Runtime.Serialization.Formatters.Soap.html,class-status-System.Runtime.Serialization.Formatters.Soap.src,cm/cormissing.css,cm/cormissing.js
|
||||
1,Cscompmgd,class-status-Cscompmgd.html,class-status-Cscompmgd.src,cm/cormissing.css,cm/cormissing.js
|
||||
1,System.Security,class-status-System.Security.html,class-status-System.Security.src,cm/cormissing.css,cm/cormissing.js
|
||||
|
||||
@@ -216,9 +216,6 @@ function clickHandler (evt)
|
||||
|
||||
if (strAssembly)
|
||||
{
|
||||
if (strAssembly == 'mscorlib')
|
||||
strAssembly = 'corlib';
|
||||
|
||||
strRoot = strRoot + strAssembly + '/';
|
||||
if (strNamespace)
|
||||
{
|
||||
|
||||
@@ -1 +0,0 @@
|
||||
*.xml
|
||||
+38
-71
@@ -9,24 +9,29 @@ CORCOMPARE=../../../mcs/tools/corcompare
|
||||
|
||||
OBJECTS= \
|
||||
deploy/ado-net.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/blogs.html \
|
||||
deploy/books.html \
|
||||
deploy/bugs.html \
|
||||
deploy/contributing.html \
|
||||
deploy/contact.html \
|
||||
deploy/c-sharp.html \
|
||||
deploy/ccvs.html \
|
||||
deploy/documentation.html \
|
||||
deploy/download.html \
|
||||
deploy/drawing.html \
|
||||
deploy/compiling.html \
|
||||
deploy/crypto.html \
|
||||
deploy/embedded-api.html \
|
||||
deploy/faq.html \
|
||||
deploy/firebird.html \
|
||||
deploy/forge.html \
|
||||
deploy/gcc-frontend.html \
|
||||
deploy/gtk-sharp.html \
|
||||
deploy/hackers.html \
|
||||
@@ -41,53 +46,40 @@ OBJECTS= \
|
||||
deploy/mbas.html \
|
||||
deploy/mono-beginning.html \
|
||||
deploy/mono-contribution-howto.html \
|
||||
deploy/mono-todo.html \
|
||||
deploy/mono-todo.html \
|
||||
deploy/monodoc-xml.html \
|
||||
deploy/mysql.html \
|
||||
deploy/odbc.html \
|
||||
deploy/oledb.html \
|
||||
deploy/oracle.html \
|
||||
deploy/other.html \
|
||||
deploy/papers.html \
|
||||
deploy/passport.html \
|
||||
deploy/plans.html \
|
||||
deploy/porting.html \
|
||||
deploy/postgresql.html \
|
||||
deploy/ppc.html \
|
||||
deploy/provider-factory.html \
|
||||
deploy/rationale.html \
|
||||
deploy/resources.html \
|
||||
deploy/roadmap.html \
|
||||
deploy/runtime.html \
|
||||
deploy/screenshots.html \
|
||||
deploy/sqlclient.html \
|
||||
deploy/sqlite.html \
|
||||
deploy/status.html \
|
||||
deploy/sybase.html \
|
||||
deploy/tdsclient.html \
|
||||
deploy/tds-providers.html \
|
||||
deploy/team.html \
|
||||
deploy/testing.html \
|
||||
deploy/tools.html \
|
||||
deploy/winforms.html \
|
||||
deploy/xml-classes.html \
|
||||
deploy/class-library.html \
|
||||
deploy/classlib-doc.html \
|
||||
deploy/class-status.html \
|
||||
deploy/class-status-corlib.html \
|
||||
deploy/class-status-System.html \
|
||||
deploy/class-status-System.Xml.html \
|
||||
deploy/class-status-System.Data.html \
|
||||
deploy/class-status-System.Security.html \
|
||||
deploy/class-status-System.Web.html \
|
||||
deploy/class-status-System.Web.Services.html \
|
||||
deploy/class-status-System.Drawing.html \
|
||||
deploy/class-status.html \
|
||||
deploy/class-status-corlib.html \
|
||||
deploy/class-status-System.html \
|
||||
deploy/class-status-System.Xml.html \
|
||||
deploy/class-status-System.Drawing.html \
|
||||
deploy/class-status-System.Data.html \
|
||||
deploy/class-status-System.Web.html \
|
||||
deploy/class-status-System.Web.Services.html \
|
||||
deploy/class-status-Microsoft.VisualBasic.html \
|
||||
deploy/class-status-System.EnterpriseServices.html \
|
||||
deploy/class-status-System.Runtime.Serialization.Formatters.Soap.html \
|
||||
deploy/class-status-System.Security.html \
|
||||
deploy/class-status-System.Windows.Forms.html \
|
||||
deploy/class-status-System.DirectoryServices.html \
|
||||
deploy/class-status-Cscompmgd.html \
|
||||
deploy/class-status-System.Runtime.Serialization.Formatters.Soap.html
|
||||
|
||||
HTML_SOURCES = ../mono-roadmap.html
|
||||
deploy/class-library.html \
|
||||
deploy/classlib-doc.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
|
||||
@@ -101,8 +93,7 @@ NON_HTML_SOURCES= \
|
||||
|
||||
all: $(OBJECTS) deploy/index.rss ../team
|
||||
perl process.pl commands template.html.in deploy
|
||||
cp $(HTML_SOURCES) deploy
|
||||
test -d deploy/team || mkdir deploy/team
|
||||
-mkdir deploy/team
|
||||
cp team/*png deploy/team
|
||||
|
||||
tutorial: mono-beginning.html.stamp mono-beginning.pdf
|
||||
@@ -131,15 +122,12 @@ render-team-page.exe: render-team-page.cs
|
||||
$(CSC) render-team-page.cs
|
||||
|
||||
clean:
|
||||
rm -f $(OBJECTS) $(patsubst deploy/%.html,src/%.src, $(OBJECTS)) src/*.xml src/*.html.in ../class-status-* ../class-status infos/*.xml
|
||||
rm -f $(OBJECTS) $(patsubst deploy/%.html,src/%.src, $(OBJECTS)) src/*.xml src/*.html.in ../class-status-* ../class-status
|
||||
|
||||
push:
|
||||
cp -f $(NON_HTML_SOURCES) deploy
|
||||
cp ../mono-roadmap.html deploy
|
||||
#echo scp -P 2200 -r deploy/* [email protected]:/web/cvsmodules/mono
|
||||
#(cd deploy; rsync --verbose --recursive --checksum --update --rsh='ssh' . [email protected]:/web/cvsmodules/mono )
|
||||
(cd deploy; rsync --verbose --recursive --checksum --update --rsh='ssh' . [email protected]:/web/cvsmodules/mono )
|
||||
|
||||
echo scp -P 2200 -r deploy/* [email protected]:/web/cvsmodules/mono
|
||||
(cd deploy; rsync --verbose --recursive --checksum --update --rsh='ssh' . [email protected]:/web/cvsmodules/mono )
|
||||
|
||||
push2:
|
||||
scp -r deploy/* primates:public_html/xxx
|
||||
@@ -153,7 +141,7 @@ transform.exe: transform.cs
|
||||
|
||||
|
||||
.PRECIOUS: src/%.src
|
||||
src/%.src: ../% commands template.html.in makefile
|
||||
src/%.src: ../% commands template.html.in #makefile
|
||||
perl htmlify $< > $@
|
||||
|
||||
.PRECIOUS: ../class-status-%
|
||||
@@ -162,41 +150,20 @@ src/%.src: ../% commands template.html.in makefile
|
||||
|
||||
|
||||
.PRECIOUS: src/%.html.in
|
||||
src/%.html.in: src/%.xml transform.exe $(CORCOMPARE)/mono-api.xsl
|
||||
$(RUN_MONO) ./transform.exe $< $(CORCOMPARE)/mono-api.xsl > $@ || (rm -f $@ && exit 1)
|
||||
src/%.html.in: src/%.xml transform.exe $(CORCOMPARE)/cormissing.xsl
|
||||
$(RUN_MONO) ./transform.exe $< $(CORCOMPARE)/cormissing.xsl > $@
|
||||
|
||||
|
||||
.PRECIOUS: infos/%.xml
|
||||
infos/%.xml: ../../../mcs/class/lib/%.dll $(CORCOMPARE)/mono-api-info.exe
|
||||
$(RUN_MONO) $(CORCOMPARE)/mono-api-info.exe $< > $@ || (rm -f $@ && exit 1)
|
||||
|
||||
.PRECIOUS: src/%.xml
|
||||
src/%.xml: infos/%.xml $(CORCOMPARE)/mono-api-diff.exe
|
||||
$(RUN_MONO) $(CORCOMPARE)/mono-api-diff.exe masterinfos/$(notdir $<) $< > $@ || (rm -f $@ && exit 1)
|
||||
src/%.xml: ../../../mcs/class/lib/%.dll $(CORCOMPARE)/CorCompare.exe
|
||||
$(RUN_MONO) $(CORCOMPARE)/CorCompare.exe -x $@ $<
|
||||
|
||||
# corlib, corlib...
|
||||
infos/mscorlib.xml: ../../../mcs/class/lib/mscorlib.dll $(CORCOMPARE)/mono-api-info.exe
|
||||
$(RUN_MONO) $(CORCOMPARE)/mono-api-info.exe $(notdir $(basename $<)) > $@ || (rm -f $@ && exit 1)
|
||||
src/corlib.xml: ../../../mcs/class/lib/corlib_cmp.dll $(CORCOMPARE)/CorCompare.exe
|
||||
$(RUN_MONO) $(CORCOMPARE)/CorCompare.exe -f corlib -ms mscorlib -x $@ $<
|
||||
|
||||
src/corlib.xml: infos/mscorlib.xml $(CORCOMPARE)/mono-api-diff.exe
|
||||
$(RUN_MONO) $(CORCOMPARE)/mono-api-diff.exe masterinfos/mscorlib.xml $< > $@ || (rm -f $@ && exit 1)
|
||||
|
||||
# System
|
||||
infos/System.xml: ../../../mcs/class/lib/System.dll $(CORCOMPARE)/mono-api-info.exe
|
||||
$(RUN_MONO) $(CORCOMPARE)/mono-api-info.exe $(notdir $(basename $<)) > $@ || (rm -f $@ && exit 1)
|
||||
|
||||
src/System.xml: infos/System.xml $(CORCOMPARE)/mono-api-diff.exe
|
||||
$(RUN_MONO) $(CORCOMPARE)/mono-api-diff.exe masterinfos/System.xml $< > $@ || (rm -f $@ && exit 1)
|
||||
|
||||
# System.Xml
|
||||
infos/System.Xml.xml: ../../../mcs/class/lib/System.Xml.dll $(CORCOMPARE)/mono-api-info.exe
|
||||
$(RUN_MONO) $(CORCOMPARE)/mono-api-info.exe $(notdir $(basename $<)) > $@ || (rm -f $@ && exit 1)
|
||||
|
||||
src/System.Xml.xml: infos/System.Xml.xml $(CORCOMPARE)/mono-api-diff.exe
|
||||
$(RUN_MONO) $(CORCOMPARE)/mono-api-diff.exe masterinfos/System.Xml.xml $< > $@ || (rm -f $@ && exit 1)
|
||||
|
||||
src/System.DirectoryServices.xml: infos/System.DirectoryServices.xml $(CORCOMPARE)/mono-api-diff.exe
|
||||
$(RUN_MONO) $(CORCOMPARE)/mono-api-diff.exe masterinfos/System.DirectoryServices.xml $< > $@ || (rm -f $@ && exit 1)
|
||||
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 $< $@
|
||||
|
||||
@@ -1 +0,0 @@
|
||||
*.xml
|
||||
@@ -1,60 +0,0 @@
|
||||
# Note that you will need Microsoft.NET to generate those masterinfos
|
||||
|
||||
# Customize to indicate your own installation dir.
|
||||
DLL_PATH=c:/WINDOWS/Microsoft.NET/Framework/v1.1.4322
|
||||
|
||||
all: \
|
||||
mscorlib.xml \
|
||||
System.xml \
|
||||
System.Xml.xml \
|
||||
System.Data.xml \
|
||||
System.Web.xml \
|
||||
System.Web.Services.xml \
|
||||
System.Runtime.Serialization.Formatters.Soap.xml \
|
||||
System.Drawing.xml \
|
||||
System.Security.xml \
|
||||
System.DirectoryServices.xml \
|
||||
System.Windows.Forms.xml \
|
||||
Cscompmgd.xml
|
||||
|
||||
mscorlib.xml :
|
||||
mono-api-info $(DLL_PATH)/mscorlib.dll > mscorlib.xml
|
||||
|
||||
System.xml :
|
||||
mono-api-info $(DLL_PATH)/System.dll > System.xml
|
||||
|
||||
System.Xml.xml :
|
||||
mono-api-info $(DLL_PATH)/System.Xml.dll > System.Xml.xml
|
||||
|
||||
System.Data.xml :
|
||||
mono-api-info $(DLL_PATH)/System.Data.dll > System.Data.xml
|
||||
|
||||
System.Web.xml :
|
||||
mono-api-info $(DLL_PATH)/System.Web.dll > System.Web.xml
|
||||
|
||||
System.Web.Services.xml :
|
||||
mono-api-info $(DLL_PATH)/System.Web.Services.dll > System.Web.Services.xml
|
||||
|
||||
System.Runtime.Serialization.Formatters.Soap.xml :
|
||||
mono-api-info $(DLL_PATH)/System.Runtime.Serialization.Formatters.Soap.dll > System.Runtime.Serialization.Formatters.Soap.xml
|
||||
|
||||
System.Drawing.xml :
|
||||
mono-api-info $(DLL_PATH)/System.Drawing.dll > System.Drawing.xml
|
||||
|
||||
System.Security.xml :
|
||||
mono-api-info $(DLL_PATH)/System.Security.dll > System.Security.xml
|
||||
|
||||
System.DirectoryServices.xml :
|
||||
mono-api-info $(DLL_PATH)/System.DirectoryServices.dll > System.DirectoryServices.xml
|
||||
|
||||
System.Windows.Forms.xml :
|
||||
mono-api-info $(DLL_PATH)/System.Windows.Forms.dll > System.Windows.Forms.xml
|
||||
|
||||
Cscompmgd.xml :
|
||||
mono-api-info $(DLL_PATH)/Cscompmgd.dll > Cscompmgd.xml
|
||||
|
||||
|
||||
clean:
|
||||
rm mscorlib.xml System.xml System.Xml.xml System.Data.xml System.Web.xml System.Web.Services.xml System.Runtime.Serialization.Formatters.Soap.xml System.Drawing.xml System.Security.xml System.DirectoryServices.xml System.Windows.Forms.xml Cscompmgd.xml
|
||||
|
||||
|
||||
+2
-12
@@ -6,21 +6,18 @@
|
||||
using System;
|
||||
using System.IO;
|
||||
using System.Xml;
|
||||
using System.Text;
|
||||
using RSS;
|
||||
|
||||
class X {
|
||||
static RSS.RSS rss;
|
||||
static Channel c;
|
||||
static int item_count;
|
||||
static int line;
|
||||
|
||||
|
||||
static void PopulateRSS (StreamReader input)
|
||||
{
|
||||
string s;
|
||||
|
||||
while ((s = input.ReadLine ()) != null){
|
||||
line++;
|
||||
if (s.StartsWith ("@item "))
|
||||
break;
|
||||
}
|
||||
@@ -52,11 +49,9 @@ class X {
|
||||
i = c.NewItem ();
|
||||
i.Title = title;
|
||||
i.Link = link;
|
||||
i.PubDate = s.Substring (6, s.IndexOf (":") - 6) + ", 2003";
|
||||
} else {
|
||||
description += "\n" + (s == "\n" ? "<p>" : s);
|
||||
}
|
||||
line++;
|
||||
} while ((s = input.ReadLine ()) != null);
|
||||
|
||||
if (i != null){
|
||||
@@ -81,12 +76,7 @@ class X {
|
||||
|
||||
using (FileStream fs = new FileStream (input, FileMode.Open)){
|
||||
using (StreamReader input_stream = new StreamReader (fs)){
|
||||
try {
|
||||
PopulateRSS (input_stream);
|
||||
} catch {
|
||||
Console.WriteLine ("{0} failure while loading: {1}", line, input);
|
||||
throw;
|
||||
}
|
||||
PopulateRSS (input_stream);
|
||||
}
|
||||
}
|
||||
|
||||
|
||||
+1
-16
@@ -13,7 +13,7 @@ namespace RSS {
|
||||
public class Item {
|
||||
XmlDocument doc;
|
||||
XmlNode item;
|
||||
XmlText title, link, description, pubdate;
|
||||
XmlText title, link, description;
|
||||
|
||||
public Item (XmlDocument doc, XmlNode item)
|
||||
{
|
||||
@@ -76,21 +76,6 @@ namespace RSS {
|
||||
description.Value = value;
|
||||
}
|
||||
}
|
||||
|
||||
public string PubDate {
|
||||
get {
|
||||
if (pubdate == null)
|
||||
return null;
|
||||
|
||||
return pubdate.Value;
|
||||
}
|
||||
|
||||
set {
|
||||
if (pubdate == null)
|
||||
pubdate = MakeTextElement ("pubDate");
|
||||
pubdate.Value = value;
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
public class Channel {
|
||||
|
||||
+13
-135
@@ -418,7 +418,7 @@
|
||||
|
||||
<image>timc.png</image>
|
||||
|
||||
<location>Waterloo, Ontario, Canada</location>
|
||||
<location>Kitchener-Waterloo, Canada</location>
|
||||
|
||||
<tasks>
|
||||
|
||||
@@ -648,7 +648,7 @@
|
||||
|
||||
</name>
|
||||
|
||||
<e-mail>jackson@ximian.com</e-mail>
|
||||
<e-mail>jackson@latitudegeo.com</e-mail>
|
||||
|
||||
<image>jackson.png</image>
|
||||
|
||||
@@ -658,12 +658,12 @@
|
||||
|
||||
<tasks>
|
||||
|
||||
<task>Misc Bug fixes</task>
|
||||
|
||||
<task>Cscompmgd</task>
|
||||
|
||||
<task>IL Assembler</task>
|
||||
|
||||
<task>System.Web</task>
|
||||
|
||||
<task>Bug Fix0r</task>
|
||||
|
||||
</tasks>
|
||||
|
||||
</contributor>
|
||||
@@ -678,7 +678,7 @@
|
||||
|
||||
</name>
|
||||
|
||||
<e-mail>ndrochak AT ieee.org</e-mail>
|
||||
<e-mail>ndrochak AT gol.com</e-mail>
|
||||
|
||||
<image>nickd.png</image>
|
||||
|
||||
@@ -915,7 +915,7 @@
|
||||
|
||||
</name>
|
||||
|
||||
<e-mail>[email protected]</e-mail>
|
||||
<e-mail>[email protected]</e-mail>
|
||||
|
||||
<image>none.png</image>
|
||||
|
||||
@@ -1017,23 +1017,17 @@
|
||||
|
||||
</name>
|
||||
|
||||
<e-mail>[email protected]</e-mail>
|
||||
<e-mail>[email protected]</e-mail>
|
||||
|
||||
<image>none.png</image>
|
||||
|
||||
<location>Tokyo, Japan</location>
|
||||
|
||||
<organization>Ximian</organization>
|
||||
|
||||
<description>Mono Hacker</description>
|
||||
<description>MIDI Programmer</description>
|
||||
|
||||
<tasks>
|
||||
|
||||
<task>System.Xml</task>
|
||||
|
||||
<task>RELAX NG</task>
|
||||
|
||||
<task>Japanese Website Translation</task>
|
||||
<task>XML</task>
|
||||
|
||||
</tasks>
|
||||
|
||||
@@ -1428,7 +1422,7 @@
|
||||
|
||||
<e-mail>[email protected]</e-mail>
|
||||
|
||||
<image>jluke.png</image>
|
||||
<image>none.png</image>
|
||||
|
||||
<location>Daytona, FL</location>
|
||||
|
||||
@@ -1459,7 +1453,7 @@
|
||||
|
||||
<e-mail>[email protected]</e-mail>
|
||||
|
||||
<image>peterw.png</image>
|
||||
<image>none.png</image>
|
||||
|
||||
<location>Cambridge, MA</location>
|
||||
|
||||
@@ -1474,120 +1468,4 @@
|
||||
</tasks>
|
||||
|
||||
</contributor>
|
||||
<contributor>
|
||||
|
||||
<name>
|
||||
|
||||
<first-name>Todd</first-name>
|
||||
|
||||
<last-name>Berman</last-name>
|
||||
|
||||
</name>
|
||||
|
||||
<e-mail>[email protected]</e-mail>
|
||||
|
||||
<image>tberman.png</image>
|
||||
|
||||
<location>Toronto, ON, CA</location>
|
||||
|
||||
<organization></organization>
|
||||
|
||||
<description>hacker</description>
|
||||
|
||||
<tasks>
|
||||
|
||||
<task>WSE2</task>
|
||||
|
||||
<task>gacutil</task>
|
||||
|
||||
<task>MonoDevelop</task>
|
||||
|
||||
</tasks>
|
||||
|
||||
</contributor>
|
||||
<contributor>
|
||||
|
||||
<name>
|
||||
|
||||
<first-name>Carlos</first-name>
|
||||
|
||||
<last-name>Guzmán Álvarez</last-name>
|
||||
|
||||
</name>
|
||||
|
||||
<e-mail>[email protected]</e-mail>
|
||||
|
||||
<image>none.png</image>
|
||||
|
||||
<location>Vigo, Spain</location>
|
||||
|
||||
<organization></organization>
|
||||
|
||||
<description>Contributor</description>
|
||||
|
||||
<tasks>
|
||||
|
||||
<task>TLS protocol</task>
|
||||
|
||||
</tasks>
|
||||
|
||||
</contributor>
|
||||
|
||||
<contributor>
|
||||
|
||||
<name>
|
||||
|
||||
<first-name>Jordi</first-name>
|
||||
|
||||
<last-name>Mas i Hernàndez</last-name>
|
||||
|
||||
</name>
|
||||
|
||||
<e-mail>jordi [at] ximian.com</e-mail>
|
||||
|
||||
<image>jordi.png</image>
|
||||
|
||||
<location>Barcelona, Spain</location>
|
||||
|
||||
<organization></organization>
|
||||
|
||||
<description>Developer</description>
|
||||
|
||||
<tasks>
|
||||
|
||||
<task>System.Drawing implementation</task>
|
||||
<task>Windows.Forms implementation</task>
|
||||
|
||||
</tasks>
|
||||
|
||||
</contributor>
|
||||
|
||||
<contributor>
|
||||
|
||||
<name>
|
||||
|
||||
<first-name>Pedro</first-name>
|
||||
|
||||
<last-name>Abelleira Seco</last-name>
|
||||
|
||||
</name>
|
||||
|
||||
<e-mail>[email protected]</e-mail>
|
||||
|
||||
<image>pedroas.png</image>
|
||||
|
||||
<location>Galicia, Spain</location>
|
||||
|
||||
<organization></organization>
|
||||
|
||||
<description>Developer</description>
|
||||
|
||||
<tasks>
|
||||
|
||||
<task>MonoDevelop</task>
|
||||
|
||||
</tasks>
|
||||
|
||||
</contributor>
|
||||
|
||||
</contributors>
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 4.5 KiB After Width: | Height: | Size: 4.3 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 4.7 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 4.1 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 4.4 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 4.3 KiB |
@@ -2,7 +2,7 @@
|
||||
<html>
|
||||
<head>
|
||||
<title>#TITLE#</title>
|
||||
<link rel="icon" href="MonoIcon.png" type="image/png">
|
||||
<link rel="icon" href="../MonoIcon.png" type="image/png">
|
||||
<!-- background-image: url("images/bgsquares.gif"); -->
|
||||
<style type="text/css">
|
||||
<!--
|
||||
@@ -15,7 +15,6 @@
|
||||
.navi0 { font-size: 14px; font-weight: bold; background: #444444; }
|
||||
.navi1 { font-size: 14px; font-weight: bold; left-margin: 10pt}
|
||||
.navi2 { font-size: 10px; font-weight: bold; left-margin: 20pt}
|
||||
.topmenu { font-size: 14px; font-weight: bold; }
|
||||
.footnote { font-size: 12px; color: #aaaaaa; }
|
||||
|
||||
a.navi0 { color: #ffffff; text-decoration: none}
|
||||
@@ -30,20 +29,6 @@
|
||||
a.navi2:visited { color: #cccccc; }
|
||||
a.navi2:hover { color: #ee9900; text-decoration: underline; }
|
||||
|
||||
a.topmenu { color: #ffffff; text-decoration: none; margin-left: 7px;}
|
||||
a.topmenu:visited { color: #cccccc; }
|
||||
a.topmenu:hover { color: #ee9900; text-decoration: underline; }
|
||||
|
||||
h1 {
|
||||
border-bottom: 2px solid #dddddd;
|
||||
}
|
||||
|
||||
.shell {
|
||||
border-style: solid; background: #000000; color: #bbbbbb;
|
||||
#777777; border-width:
|
||||
1px; padding: 2pt;
|
||||
margin:15px;
|
||||
}
|
||||
// -->
|
||||
</style>
|
||||
#CSS#
|
||||
@@ -53,28 +38,11 @@
|
||||
|
||||
<table cellpadding="0" cellspacing="0" border="0" width="100%">
|
||||
<tr>
|
||||
<td><img src="images/pixel.gif" alt=""></td><!-- left border
|
||||
-->
|
||||
<td colspan="4">
|
||||
<table>
|
||||
<tr>
|
||||
<td>
|
||||
<a href="http://www.go-mono.com"><img
|
||||
src="images/mono-new.gif" alt="mono-logo" border="0"></a>
|
||||
</td>
|
||||
<td>
|
||||
<a class="topmenu" href="download.html">Downloads</a> |
|
||||
<a class="topmenu" href="http://go-mono.com/daily/">Daily snapshots</a> |
|
||||
<a class="topmenu" href="screenshots.html">Screenshots</a> |
|
||||
<a class="topmenu" href="http://www.go-mono.com:8080">Documentation</a> |
|
||||
<a class="topmenu" href="bugs.html">Bugs</a> |
|
||||
<a class="topmenu" href="http://www.go-mono.com/monologue/">Blogs</a>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</td>
|
||||
<td><img src="images/pixel.gif" alt=""></td><!-- right border
|
||||
-->
|
||||
<td><img src="images/pixel.gif" alt=""></td><!-- left border -->
|
||||
<td colspan="4">
|
||||
<a href="http://www.go-mono.com"><img src="images/mono-new.gif"
|
||||
alt="mono-logo" border="0"></a></td>
|
||||
<td><img src="images/pixel.gif" alt=""></td><!-- right border -->
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img src="images/pixel.gif" width="1" height="1" alt=""></td>
|
||||
|
||||
+76
-4
@@ -48,7 +48,7 @@
|
||||
calls to Win32 and we will then just run the result on Unix.
|
||||
|
||||
In terms of integrating visually with the desktop, we are
|
||||
hoping to contribute to the Wine project a mechanism to make
|
||||
hoping to contribute to the Wine project an mechanism to make
|
||||
it use the Gtk+ themes on X11 and Cocoa on MacOS to render the
|
||||
widgets, and get the native look and feel on each of these
|
||||
platforms.
|
||||
@@ -90,7 +90,79 @@
|
||||
|
||||
* System.Drawing
|
||||
|
||||
For details, see the <a
|
||||
href="drawing.html">System.Drawing implementation notes</a>
|
||||
section of the web site.
|
||||
Using existing libraries to implement some of the
|
||||
functionality required:
|
||||
|
||||
<ul>
|
||||
* gdk-pixbuf is a generic image loader that loads an image
|
||||
and leaves it into an RGB buffer. It hides all the details
|
||||
about what image file format is being loaded.
|
||||
|
||||
* Libart is a general framework for rendering RGB/RGBA
|
||||
buffers into RGB buffers and rendering postscript-like paths into
|
||||
RGB/RGBA buffers.
|
||||
</ul>
|
||||
|
||||
We want to use gdk-pixbuf as the image loader for the image
|
||||
classes, and then we need operations to render that into the
|
||||
windowing system (Gtk+, MacOS, etc). But notice how there is
|
||||
very little dependnecies in Gdk-pixbuf on gtk, and libart has
|
||||
none.
|
||||
|
||||
They are pretty independent from a windowing system
|
||||
(gdk-pixbuf comes with some "helper" routines for rendering
|
||||
data into a pixmap and to load pixmaps into RGB buffers).
|
||||
|
||||
A few things to keep in mind:
|
||||
|
||||
<ul>
|
||||
|
||||
* gdk-pixbuf can be used to load images for Gtk+,
|
||||
MacOS X and Windows, it should be pretty portable,
|
||||
although we might need in the future to back-port
|
||||
some new features from Gtk head.
|
||||
|
||||
* Libart is probably only going to be used with X11,
|
||||
as the MacOS X provides the same features in Quartz,
|
||||
and Win32 *probably* has that in GDI+. If not, we
|
||||
should use libart in Win32 as well (or for older
|
||||
Windows systems).
|
||||
</ul>
|
||||
|
||||
* Directory Layout
|
||||
|
||||
<pre>
|
||||
System.Drawing (assembly directory)
|
||||
System.Drawing.Blah
|
||||
Common code for "Blah"
|
||||
Stubs for "Blah" to ease ports.
|
||||
|
||||
Gtk
|
||||
System.Drawing.Blah.
|
||||
Gtk ports of "System.Drawing.Blah"
|
||||
MacOS
|
||||
System.Drawing.Blah
|
||||
MacOS ports of "System.Drawing.Blah"
|
||||
WineLIB
|
||||
System.Drawing.Blah
|
||||
Win32 ports of "System.Drawing.Blah"
|
||||
</pre>
|
||||
|
||||
Notice that there is a proof of concept Gtk-backend for
|
||||
Windows.Forms, but nobody is working on it, and for the
|
||||
reasons stated before it is not a long term strategy.
|
||||
|
||||
* Open questions:
|
||||
|
||||
I believe that the graphics contexts that are used to render
|
||||
can accept either libart-like rendering operations and
|
||||
X11-like rendering operations. This complicates matters, but
|
||||
I am not sure. Someone needs to investigate this.
|
||||
|
||||
* Historical
|
||||
|
||||
Although the original plans were to use Gtk on X and Cocoa on
|
||||
MacOS X, it would be very hard to emulate the event model in
|
||||
which some Winforms applications depend, and it would be very
|
||||
hard to implement the Wndproc method.
|
||||
|
||||
-310
@@ -1,310 +0,0 @@
|
||||
* XML Classes
|
||||
|
||||
** Abstract
|
||||
|
||||
XML library is used by several field of Mono such as ADO.NET and XML
|
||||
Digital Signature (xmldsig). Here I write about System.Xml.dll and
|
||||
related tools. This page won't include any classes which are in other
|
||||
assemblies such as XmlDataDocument.
|
||||
|
||||
Note that current corlib has its own XML parser class named Mono.Xml.MiniParser.
|
||||
|
||||
Basically System.XML.dll feature has finished, or almost finished, so
|
||||
I write this page mainly for bugs and improvement hints.
|
||||
|
||||
|
||||
** System.Xml namespace
|
||||
|
||||
|
||||
*** Document Object Model (Core)
|
||||
|
||||
DOM feature has already implemented. There is still missing feature.
|
||||
|
||||
<ul>
|
||||
* ID constraint support is problematic because W3C DOM does not
|
||||
specify handling of ID attributes into non-adapted element.
|
||||
(MS.NET also looks incomplete in this area).
|
||||
* I think, event feature is not fully tested. There are no
|
||||
concrete desctiption on which events are risen, so we have to
|
||||
do some experiment on MS.NET.
|
||||
</ul>
|
||||
|
||||
*** Xml Writer
|
||||
|
||||
Here XmlWriter almost equals to XmlTextWriter. If you want to see
|
||||
another implementation, check XmlNodeWriter.cs used in monodoc.
|
||||
|
||||
XmlTextWriter is completed. However, it looks nearly twice as slow as
|
||||
MS.NET (I tried 1.1)
|
||||
|
||||
*** XmlResolver
|
||||
|
||||
Currently XmlTextReader uses specified XmlResolver. If nothing was supplied,
|
||||
then it uses XmlUrlResolver. XmlResolver is used to parse external DTD,
|
||||
importing XSL stylesheets and schemas etc.
|
||||
|
||||
However, XmlUrlResolver is still buggy (mainly because System.Uri is also
|
||||
incomplete yet) and this results in several loading error.
|
||||
|
||||
XmlSecureResolver, which is introduced in MS .NET Framework 1.1 is basically
|
||||
implemented, but it requires CAS (code access security) feature. We need to
|
||||
fixup this class after ongoing CAS effort works.
|
||||
|
||||
You might also be interested in an improved <a href="http://codeblogs.ximian.com/blogs/benm/archives/000039.html">XmlCachingResolver</a> by Ben Maurer.
|
||||
|
||||
*** XmlNameTable
|
||||
|
||||
XmlNameTable itself is implemented. However, it should be actually used in
|
||||
several classes. Currently it makes sense if compared names are both in
|
||||
the table, they should be simply compared using ReferenceEquals(). We
|
||||
have partially done in XmlNamespaceManager (in .NET 1.2 methods; if the
|
||||
build is not NET_1_2 then it is internal use only).
|
||||
|
||||
*** Xml Stream Reader
|
||||
|
||||
When we are using ASCII document, we don't care which encoding we are using.
|
||||
However, XmlTextReader must be aware of the specified encoding in XML
|
||||
declaration. So we have internal XmlStreamReader class (and currently
|
||||
XmlInputStream class. This may disappear since XmlStreamReader is enough to
|
||||
handle this problem).
|
||||
|
||||
However, there seems some problems in these classes on reading network
|
||||
stream (especially on Linux). This should be fixed soon, if we found the
|
||||
actual reason.
|
||||
|
||||
*** XML Reader
|
||||
|
||||
XmlTextReader, XmlNodeReader and XmlValidatingReader are almost finished.
|
||||
|
||||
<ul>
|
||||
* Most of the OASIS conformance test passes as Microsoft
|
||||
does, but about W3C tests, it is still not perfect.
|
||||
* I won't add any XDR support on XmlValidatingReader. (I haven't
|
||||
ever seen XDR used other than Microsoft's BizTalk Server 2000,
|
||||
and Now they have 2002 with XML Schema support)
|
||||
</ul>
|
||||
|
||||
XmlTextReader and XmlValidatingReader should be faster than now. Currently
|
||||
XmlTextReader looks nearly twice as slow as MS.NET, and XmlValidatingReader
|
||||
(which uses this slow XmlTextReader) looks nearly three times slower. (Note
|
||||
that XmlValidatingReader won't be slow as itself. It uses schema validating
|
||||
reader and dtd validating reader.)
|
||||
|
||||
|
||||
**** Some Advantages
|
||||
|
||||
The design of Mono's XmlValidatingReader is radically different from
|
||||
that of Microsoft's implementation. Under MS.NET, DTD content validation
|
||||
engine is in fact simple replacement of XML Schema validation engine.
|
||||
Mono's DTD validation is designed fully separate and does validation
|
||||
as normal XML parser does. For example, Mono allows non-deterministic DTD.
|
||||
|
||||
Another advantage of this XmlValidatingReader is support for *any* XmlReader.
|
||||
Microsoft supports only XmlTextReader.
|
||||
|
||||
I added extra support interface named "IHasXmlParserContext", which is
|
||||
considered in XmlValidatingReader.ResolveEntity(). Microsoft failed to
|
||||
design XmlReader to support pluggable use of XmlReader (i.e. wrapping use
|
||||
of other XmlReader) since XmlParserContext is required to support both
|
||||
entity resolution and namespace manager. (In .NET 1.2, Microsoft also
|
||||
supported similar to IHasXmlParserContext, named IXmlNamespaceResolver,
|
||||
but it still does not provide any DTD information.)
|
||||
|
||||
We also have RELAX NG validating reader. See mcs/class/Commons.Xml.Relaxng.
|
||||
|
||||
|
||||
** System.Xml.Schema
|
||||
|
||||
*** Summary
|
||||
|
||||
Basically it is completed. We can compile complex and simple types, refer to
|
||||
external schemas, extend or restrict other types, or use substitution groups.
|
||||
You can test how current schema validation engine is (in)complete by using
|
||||
standalone test module
|
||||
(see mcs/class/System.XML/Test/System.Xml.Schema/standalone_tests).
|
||||
At least in my box, msxsdtest fails only 30 cases with bugfixed catalog.
|
||||
|
||||
*** Schema Object Model
|
||||
|
||||
Completed, except for some things to be fixed:
|
||||
|
||||
<ul>
|
||||
* Complete facet support. Currently some of them is missing.
|
||||
Recently David Sheldon is doing several fixes on them.
|
||||
* ContentTypeParticle for pointless xs:choice is incomplete
|
||||
(It is because fixing this arose another bugs in
|
||||
compilation. Interestingly, MS.NET also fails around here,
|
||||
so it might be nature of ContentTypeParticle design)
|
||||
* Some derivation by restriction (DBR) handling is incorrect.
|
||||
</ul>
|
||||
|
||||
*** Validating Reader
|
||||
|
||||
XML Schema validation feature is (currently) implemented on
|
||||
Mono.Xml.Schema.XsdValidatingReader, which is internally used in
|
||||
XmlValidatingReader.
|
||||
|
||||
Basically this is implemented and actually its feature is almost complete,
|
||||
but I have only did validation feature testing. So we have to write more
|
||||
tests on properties, methods, and events (validation errors).
|
||||
|
||||
|
||||
** System.Xml.Serialization
|
||||
|
||||
Lluis rules ;-)
|
||||
|
||||
Well, in fact XmlSerializer is almost finished and is on bugfix phase.
|
||||
|
||||
However, we appliciate more tests. Please try
|
||||
|
||||
<ul>
|
||||
* System.Web.Services to invoke SOAP services.
|
||||
* xsd.exe and wsdl.exe to create classes.
|
||||
</ul>
|
||||
|
||||
And if any problems were found, please file it to bugzilla.
|
||||
|
||||
Lluis also built interesting standalone test system placed under
|
||||
mcs/class/System.Web.Services/Test/standalone.
|
||||
|
||||
You might also interested in genxs, which enables you to create custom
|
||||
XML serializer. This is not included in Microsoft.NET.
|
||||
See mcs/tools/genxs for the details.
|
||||
|
||||
|
||||
** System.Xml.XPath and System.Xml.Xsl
|
||||
|
||||
There are two implementations for XSLT. One (and historical) implementation
|
||||
is based on libxslt. Now we uses fully implemented managed XSLT.
|
||||
|
||||
As for Managed XSLT, we support msxsl:script.
|
||||
|
||||
It would be nice if we can support <a href="http://www.exslt.org/">EXSLT</a>.
|
||||
<a href="http://msdn.microsoft.com/WebServices/default.aspx?pull=/library/en-us/dnexxml/html/xml05192003.asp">Microsoft has already done it</a>, but it
|
||||
is not good code since it depends on internal concrete derivatives of
|
||||
XPathNodeIterator classes. In general, .NET's "extension objects" is not
|
||||
usable to return node-sets, so if we support EXSLT, it has to be done
|
||||
internally inside our System.XML.dll. Volunteers are welcome.
|
||||
|
||||
Our managed XSLT implementation is still inefficient. XslTransform.Load()
|
||||
and .Transform() looks three times slower (However it depends on
|
||||
XmlTextReader which is also slow, so we are starting optimization from
|
||||
that class, not XSLT itself). These number are only for specific cases,
|
||||
and there might be more critical point on XSLT engine (mainly
|
||||
XPathNodeIterator).
|
||||
|
||||
|
||||
** System.Xml and ADO.NET v2.0
|
||||
|
||||
Microsoft introduced the first beta version of .NET Framework 1.2 runtime
|
||||
and sdk (and Visual Studio Whidbey). They are now available on MSDN
|
||||
_subscriber_ download (i.e. it is not publicly downloadable yet). It
|
||||
contains several new classes.
|
||||
|
||||
There are two assemblies related to System.Xml v2.0; System.Xml.dll and
|
||||
System.Data.SqlXml.dll (here I treat sqlxml.dll as part of System.Xml v2.0,
|
||||
but note that it is also one of the ADO.NET 2.0 feature). There are several
|
||||
namespaces such as MS.Internal.Xml and System.Xml. Note that .NET Framework
|
||||
is pre-release version and MS.Internal.Xml namespace apparently shows that
|
||||
it is not in stable status as yet.
|
||||
|
||||
System.Xml 2.0 contains several features such as:
|
||||
|
||||
<ul>
|
||||
* XPathNavigator2 and XPathDocument2
|
||||
* XML Query
|
||||
* XmlAdapter
|
||||
* XSLT IL generator (similar to Apache XSLTC) - it is
|
||||
internal use
|
||||
</ul>
|
||||
|
||||
Tim Coleman started ADO.NET 2.0 related works. Currently I have no plan to
|
||||
implement System.Xml v2.0 classes and won't touch with them immediately,
|
||||
but will start in next some months. If any of you wants to try this
|
||||
frontier, we welcome your effort.
|
||||
|
||||
*** XPathNavigator2
|
||||
|
||||
System.Xml v2.0 implementation will be started from XPathDocument2 and
|
||||
XPathNavigator2 implementations. Firstly, its document structure and
|
||||
basic navigation feature will be implemented. And next, XPath2 engine
|
||||
should be implemented (XPathNavigator2 looks very different from
|
||||
XPathNavigator). Another requirement is schema based validation feature.
|
||||
It needs some schema improvements, such like IXmlInfosetReader support.
|
||||
(IXmlInfosetReader is in MS.Internal.Xml.)
|
||||
|
||||
*** XML Query
|
||||
|
||||
XML Query is a new face XML data manipulation language (well, at least new
|
||||
to .NET world). It is similar to SQL, but intended to manipulate and to
|
||||
support XML. It is similar to XSLT, but extended to support new features
|
||||
such as XML Schema based datatypes.
|
||||
|
||||
XML Query implementation can be found mainly in System.Xml.Query and
|
||||
MS.Internal.Xml.Query namespaces. Note that they are in
|
||||
System.Data.SqlXml.dll.
|
||||
|
||||
MSDN documentation says that there are two kind of API for XML Query: High
|
||||
Level API and Low Level API. At the time of this beta version, the Low Level
|
||||
API is described not released yet (though it may be MS.Internal.Xml.*
|
||||
classes). However, to implement the High Level API, the Low Level API will
|
||||
be used. They looks to have interesting class structures in MS.Internal.Xml
|
||||
related stuff, so it would be nice (and I will) start to learn about them.
|
||||
|
||||
They looks to have IL generator classes, but it would be difficult to
|
||||
start from them.
|
||||
|
||||
*** System.Data.Mapping
|
||||
|
||||
System.Data.Mapping and System.Data.Mapping.RelationalSchema are the
|
||||
namespaces for mapping support between database and xml. This is at
|
||||
stubbing phase (incomplete as yet).
|
||||
|
||||
*** XmlAdapter
|
||||
|
||||
XmlAdapter is used to support XML based query and update using
|
||||
XPathDocument2 and XPathNavigator2. This class is designed to synthesize
|
||||
ADO.NET and System.Xml. It connects to databases, and querys data however
|
||||
in XML shape into XPathDocument2, using Mapping schema above. This must be
|
||||
done after several classes such as XPathDocument2 and MappingSchema.
|
||||
|
||||
|
||||
** Miscellaneous Class Libraries
|
||||
|
||||
*** RELAX NG
|
||||
|
||||
I implemented an experimental RelaxngValidatingReader. It is far from
|
||||
complete, especially simplification stuff (see RELAX NG spec chapter 4),
|
||||
some constraints (in chapter 7), and datatype handling.
|
||||
|
||||
I am planning improvements (starts with renaming classes, giving more
|
||||
kind error messages, supporting compact syntax and even object mapping),
|
||||
but it is still my wishlist.
|
||||
|
||||
|
||||
** Tools
|
||||
|
||||
*** xsd.exe
|
||||
|
||||
See <a href="ado-net.html">ADO.NET page</a>.
|
||||
|
||||
Microsoft has another inference class from XmlReader to XmlSchemaCollection
|
||||
(Microsoft.XsdInference). It may be useful, but it won't be so easy.
|
||||
|
||||
|
||||
** Miscellaneous
|
||||
|
||||
Sometimes I hear complain about System.dll and System.Xml.dll mutual
|
||||
dependency: System.dll references to System.Xml.dll (e.g.
|
||||
System.Configuration.ConfigXmlDocument extended from XmlDocument), while
|
||||
System.Xml.dll vice versa (e.g. XmlUrlResolver.ResolveUri takes System.Uri).
|
||||
Since they are in public method signatures, so at least we cannot get rid
|
||||
of these mutual references.
|
||||
|
||||
However, for those who really want to build System.Xml.dll without System.dll,
|
||||
I created <a href="http://primates.ximian.com/~atsushi/System_DummyClasses.cs">dummy classes in System.dll</a>. To build System.Xml.dll in such way, remove
|
||||
<code>/r:System.dll</code> from Makefile, and add this source to
|
||||
System.Xml.dll.sources. Note that this is at the point of Mono 0.30 release.
|
||||
|
||||
Also note that you still need System.dll to run mcs.
|
||||
|
||||
+36
-51
@@ -1,57 +1,42 @@
|
||||
|
||||
HOWTO bundle assemblies inside the mono runtime.
|
||||
Paolo Molaro ([email protected])
|
||||
HOWTO bundle assemblies inside the mono runtime.
|
||||
|
||||
* Intent
|
||||
Bundling assemblies inside the mono runtime may be useful for a number
|
||||
of reasons:
|
||||
* creating a standalone complete runtime that can be more easily
|
||||
distributed
|
||||
* having an application run against a known set of assemblies
|
||||
that has been tested
|
||||
|
||||
Bundling assemblies inside the mono runtime may be useful for a number
|
||||
of reasons:
|
||||
Of course, there are drawbacks, too: if there has been fixes to the assemblies,
|
||||
replacing them means recompiling the runtime as well and if there are other mono apps,
|
||||
unless they use the same mono binary, there will be less opportunities for
|
||||
the operating system to optimize memory usage. So use this feature only
|
||||
when really needed.
|
||||
|
||||
* creating a standalone complete runtime that can be more easily
|
||||
distributed
|
||||
|
||||
* having an application run against a known set of assemblies
|
||||
that has been tested
|
||||
|
||||
Of course, there are drawbacks, too: if there has been fixes
|
||||
to the assemblies, replacing them means recompiling the
|
||||
runtime as well and if there are other mono apps, unless they
|
||||
use the same mono binary, there will be less opportunities for
|
||||
the operating system to optimize memory usage. So use this
|
||||
feature only when really needed.
|
||||
|
||||
* Creating the Bundle
|
||||
|
||||
To bundle a set of assemblies, you need to create a file that
|
||||
lists the assembly names and the relative files. Empty lines
|
||||
and lines starting with # are ignored:
|
||||
|
||||
== cut cut ==
|
||||
# Sample bundle template
|
||||
mscorlib: /path/to/mscorlib/assembly.dll
|
||||
myapp: /path/to/myapp.exe
|
||||
== cut cut ==
|
||||
|
||||
Next you need to build the mono runtime using a special configure option:
|
||||
|
||||
./configure --with-bundle=/path/to/bundle/template
|
||||
|
||||
The path to the template should be an absolute path.
|
||||
|
||||
The script metadata/make-bundle.pl will take the specifie
|
||||
assemblies and embed them inside the runtime where the loading
|
||||
routines can find them before searching for them on disk.
|
||||
|
||||
* Open Issues
|
||||
|
||||
There are still two issues to solve:
|
||||
|
||||
* config files: sometimes they are needed but they are
|
||||
not yet bundled inside the library ()
|
||||
|
||||
* building with the included libgc makes it not
|
||||
possible to build a mono binary statically linked to
|
||||
libmono: this needs to be fixed to make bundles
|
||||
really useful.
|
||||
To bundle a set of assemblies, you need to create a file that lists the assembly
|
||||
names and the relative files. Empty lines and lines starting with # are ignored:
|
||||
|
||||
== cut cut ==
|
||||
# Sample bundle template
|
||||
mscorlib: /path/to/mscorlib/assembly.dll
|
||||
myapp: /path/to/myapp.exe
|
||||
== cut cut ==
|
||||
|
||||
Next you need to build the mono runtime using a special configure option:
|
||||
|
||||
./configure --with-bundle=/path/to/bundle/template
|
||||
|
||||
The path to the template should be an absolute path.
|
||||
|
||||
The script metadata/make-bundle.pl will take the specifie assemblies and embed
|
||||
them inside the runtime where the loading routines can find them before
|
||||
searching for them on disk.
|
||||
|
||||
There are still two issues to solve:
|
||||
* config files: sometimes they are needed but they are not yet bundled
|
||||
inside the library ()
|
||||
* building with the included libgc makes it not possible to build a mono
|
||||
binary statically linked to libmono: this needs to be fixed to make bundles
|
||||
really useful
|
||||
|
||||
+5
-34
@@ -1,13 +1,11 @@
|
||||
|
||||
Embedding the Mono runtime, preliminary version
|
||||
Miguel de Icaza ([email protected]),
|
||||
Paolo Molaro ([email protected])
|
||||
|
||||
Miguel de Icaza, Paolo Molaro.
|
||||
|
||||
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. Both the JIT and interpreter can be
|
||||
embedded in very similar ways so most of what is described
|
||||
here can be used in either case.
|
||||
invoke C code from CIL.
|
||||
|
||||
* Embedding the runtime.
|
||||
|
||||
@@ -29,12 +27,6 @@
|
||||
|
||||
pkg-config --cflags --libs mono
|
||||
|
||||
is used to get the flags for the JIT runtime and
|
||||
|
||||
pkg-config --cflags --libs mint
|
||||
|
||||
for the interpreted runtime.
|
||||
|
||||
Like this:
|
||||
|
||||
gcc sample.c `pkg-config --cflags --libs mono`
|
||||
@@ -47,22 +39,12 @@
|
||||
|
||||
** Initializing the Mono runtime
|
||||
|
||||
To initialize the JIT runtime, call mono_jit_init, like this:
|
||||
|
||||
#include <mono/mini/jit.h>
|
||||
To initialize the runtime, call mono_jit_init, like this:
|
||||
|
||||
MonoDomain *domain;
|
||||
|
||||
domain = mono_jit_init ("domain-name");
|
||||
|
||||
For the interpreted runtime use mono_interp_init instead:
|
||||
|
||||
#include <mono/interpreter/embed.h>
|
||||
|
||||
MonoDomain *domain;
|
||||
|
||||
domain = mono_interp_init ("domain-name");
|
||||
|
||||
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
|
||||
@@ -88,10 +70,6 @@
|
||||
|
||||
retval = mono_jit_exec (domain, assembly, argc - 1, argv + 1);
|
||||
|
||||
or when using the interpreter use:
|
||||
|
||||
retval = mono_interp_exec (domain, assembly, argc - 1, argv + 1);
|
||||
|
||||
If you want to invoke a different method, look at the
|
||||
`Invoking Methods in the CIL universe' section later on.
|
||||
|
||||
@@ -102,10 +80,6 @@
|
||||
|
||||
mono_jit_cleanup (domain);
|
||||
|
||||
Or in the case of the interpreted runtime use:
|
||||
|
||||
mono_interp_cleanup (domain);
|
||||
|
||||
** Applications that use threads.
|
||||
|
||||
The Boehm GC system needs to catch your calls to the pthreads
|
||||
@@ -209,9 +183,6 @@
|
||||
methods, a MonoObject* for object instances and a pointer to
|
||||
the value type for value types.
|
||||
|
||||
These functions can be used in both the JIT and the interpreted
|
||||
environments.
|
||||
|
||||
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
|
||||
@@ -265,7 +236,7 @@
|
||||
|
||||
* Samples
|
||||
|
||||
See the sample programs in mono/sample/embed for examples of
|
||||
See the sample programs inmono/sample/embed for examples of
|
||||
embedding the Mono runtime in your application.
|
||||
|
||||
|
||||
+2
-3
@@ -1,6 +1,5 @@
|
||||
Exception Implementation in the Mono Runtime
|
||||
Dietmar Maurer ([email protected])
|
||||
(C) 2001 Ximian, Inc.
|
||||
Author: Dietmar Maurer ([email protected])
|
||||
(C) 2001 Ximian, Inc.
|
||||
|
||||
Exception implementation (jit):
|
||||
===============================
|
||||
|
||||
+32
-57
@@ -1,19 +1,7 @@
|
||||
Internal Call Topics
|
||||
|
||||
* Introduction
|
||||
|
||||
The Common Language Infrastructure allows for methods to be
|
||||
implemented in unmanaged code. Unlike the Platform Invocation
|
||||
services which provide marshalling and unmarshalling of data
|
||||
from managed to unmanaged and viceversa the Internal calls do
|
||||
not perform any kind of marshalling.
|
||||
|
||||
* Basic Type mapping
|
||||
|
||||
The following lists how the C# types are exposed to the C API.
|
||||
* How to map C# types for use in the C implementation of internal calls
|
||||
|
||||
C# type C type
|
||||
-----------------------------
|
||||
char gunichar2
|
||||
bool MonoBoolean
|
||||
sbyte signed char
|
||||
@@ -28,57 +16,44 @@
|
||||
object MonoObject*
|
||||
string MonoString*
|
||||
|
||||
* Pointers
|
||||
For ref and out paramaters you'll use the corresponding pointer type.
|
||||
Arrays of any type must be described with a MonoArray* and the elements
|
||||
must be accessed with the mono_array_* macros.
|
||||
Any other type that has a matching C structure representation, should use
|
||||
a pointer to the struct instead of a generic MonoObject pointer.
|
||||
|
||||
For ref and out paramaters you'll use the corresponding
|
||||
pointer type.
|
||||
Instance methods that are internal calls will receive as first argument
|
||||
the instance object, so you must account for it in the C method signature:
|
||||
|
||||
So if you have a C# type listed as "ref int", you should use
|
||||
"int *" in your implementation.
|
||||
[MethodImplAttribute(MethodImplOptions.InternalCall)]
|
||||
public extern override int GetHashCode ();
|
||||
|
||||
* Arrays
|
||||
becaomes:
|
||||
|
||||
Arrays of any type must be described with a MonoArray* and the
|
||||
elements must be accessed with the mono_array_* macros.
|
||||
gint32 ves_icall_System_String_GetHashCode (MonoString *this);
|
||||
|
||||
* Other Structures
|
||||
|
||||
Any other type that has a matching C structure representation,
|
||||
should use a pointer to the struct instead of a generic
|
||||
MonoObject pointer.
|
||||
|
||||
* Instance Methods.
|
||||
|
||||
Instance methods that are internal calls will receive as first argument
|
||||
the instance object, so you must account for it in the C method signature:
|
||||
|
||||
[MethodImplAttribute(MethodImplOptions.InternalCall)]
|
||||
public extern override int GetHashCode ();
|
||||
|
||||
becomes:
|
||||
|
||||
gint32 ves_icall_System_String_GetHashCode (MonoString *this);
|
||||
|
||||
* How to hook internal calls with the runtime
|
||||
|
||||
Once you require an internal call in corlib, you need to
|
||||
create a C implementation for it and register it in a static
|
||||
table in metadata/icall.c. Add an entry in the table like:
|
||||
|
||||
"System.String::GetHashCode", ves_icall_System_String_GetHashCode,
|
||||
|
||||
Note that you need to include the full namespace.name of the
|
||||
class. If there are overloaded methods, you need also to
|
||||
specify the signature of _all_ of them:
|
||||
|
||||
[MethodImplAttribute(MethodImplOptions.InternalCall)]
|
||||
public extern override void DoSomething ();
|
||||
[MethodImplAttribute(MethodImplOptions.InternalCall)]
|
||||
public extern override void DoSomething (bool useful);
|
||||
|
||||
should be mapped with:
|
||||
|
||||
"Namespace.ClassName::DoSomething()", ves_icall_Namespace_ClassName_DoSomething,
|
||||
"Namespace.ClassName::DoSomething(bool)", ves_icall_Namespace_ClassName_DoSomething_bool,
|
||||
|
||||
Once you require an internal call in corlib, you need to create a C
|
||||
implementation for it and register it in a static table in metadata/icall.c.
|
||||
Add an entry in the table like:
|
||||
|
||||
"System.String::GetHashCode", ves_icall_System_String_GetHashCode,
|
||||
|
||||
Note that you need to include the full namespace.name of the class.
|
||||
If there are overloaded methods, you need also to specify the signature
|
||||
of _all_ of them:
|
||||
|
||||
[MethodImplAttribute(MethodImplOptions.InternalCall)]
|
||||
public extern override void DoSomething ();
|
||||
[MethodImplAttribute(MethodImplOptions.InternalCall)]
|
||||
public extern override void DoSomething (bool useful);
|
||||
|
||||
should be mapped with:
|
||||
|
||||
"Namespace.ClassName::DoSomething()", ves_icall_Namespace_ClassName_DoSomething,
|
||||
"Namespace.ClassName::DoSomething(bool)", ves_icall_Namespace_ClassName_DoSomething_bool,
|
||||
|
||||
|
||||
@@ -1,30 +0,0 @@
|
||||
Mono Intermediate Representation Documentation
|
||||
|
||||
Operation: OP_LOCALLOC
|
||||
inst_left:
|
||||
The value
|
||||
ins->inst_left = *sp;
|
||||
ins->cil_code = ip;
|
||||
|
||||
This is the equivalent of alloca() in a C implementation: it
|
||||
allocates a bunch of bytes on the stack dynamically. Local
|
||||
variables are allocated statically in the stack instead.
|
||||
|
||||
It is implemented by moving the stack pointer according to the
|
||||
platform ABI: you may need to keep a specific frame register
|
||||
to address local variables when LOCALLOC is used (the PPC code
|
||||
does this, for example: ifyou're doing the s390 port I suggest
|
||||
starting from that)
|
||||
|
||||
Operation: OP_CALL_HANDLER.
|
||||
|
||||
cil_code:
|
||||
Points to the CIL where the LEAVE or LEAVE_S
|
||||
instruction was found.
|
||||
|
||||
inst_target_bb:
|
||||
The target basic block for this invocation.
|
||||
|
||||
This instruction must call the target basic block.
|
||||
|
||||
|
||||
+297
-372
@@ -1,424 +1,349 @@
|
||||
Mono JIT porting guide.
|
||||
Paolo Molaro ([email protected])
|
||||
Mono JIT porting guide.
|
||||
Paolo Molaro ([email protected])
|
||||
|
||||
* Introduction
|
||||
|
||||
This documents describes the process of porting the mono JIT
|
||||
to a new CPU architecture. The new mono JIT has been designed
|
||||
to make porting easier though at the same time enable the port
|
||||
to take full advantage from the new architecture features and
|
||||
instructions. Knowledge of the mini architecture (described in
|
||||
the mini-doc.txt file) is a requirement for understanding this
|
||||
guide, as well as an earlier document about porting the mono
|
||||
interpreter (available on the web site).
|
||||
|
||||
There are six main areas that a port needs to implement to
|
||||
have a fully-functional JIT for a given architecture:
|
||||
|
||||
1) instruction selection
|
||||
2) native code emission
|
||||
3) call conventions and register allocation
|
||||
4) method trampolines
|
||||
5) exception handling
|
||||
6) minor helper methods
|
||||
|
||||
To take advantage of some not-so-common processor features
|
||||
(for example conditional execution of instructions as may be
|
||||
found on ARM or ia64), it may be needed to develop an
|
||||
high-level optimization, but doing so is not a requirement for
|
||||
getting the JIT to work.
|
||||
|
||||
We'll see in more details each of the steps required, note,
|
||||
though, that a new port may just as well start from a
|
||||
cut&paste of an existing port to a similar architecture (for
|
||||
example from x86 to amd64, or from powerpc to sparc).
|
||||
|
||||
The architecture specific code is split from the rest of the
|
||||
JIT, for example the x86 specific code and data is all
|
||||
included in the following files in the distribution:
|
||||
|
||||
mini-x86.h mini-x86.c
|
||||
inssel-x86.brg
|
||||
cpu-pentium.md
|
||||
tramp-x86.c
|
||||
exceptions-x86.c
|
||||
|
||||
I suggest a similar split for other architectures as well.
|
||||
|
||||
Note that this document is still incomplete: some sections are
|
||||
only sketched and some are missing, but the important info to
|
||||
get a port going is already described.
|
||||
This documents describes the process of porting the mono JIT
|
||||
to a new CPU architecture. The new mono JIT has been designed
|
||||
to make porting easier though at the same time enable the port
|
||||
to take full advantage from the new architecture features and
|
||||
instructions. Knowledge of the mini architecture (described in the
|
||||
mini-doc.txt file) is a requirement for understanding this guide,
|
||||
as well as an earlier document about porting the mono interpreter
|
||||
(available on the web site).
|
||||
|
||||
There are six main areas that a port needs to implement to
|
||||
have a fully-functional JIT for a given architecture:
|
||||
|
||||
1) instruction selection
|
||||
2) native code emission
|
||||
3) call conventions and register allocation
|
||||
4) method trampolines
|
||||
5) exception handling
|
||||
6) minor helper methods
|
||||
|
||||
To take advantage of some not-so-common processor features (for example
|
||||
conditional execution of instructions as may be found on ARM or ia64), it may
|
||||
be needed to develop an high-level optimization, but doing so is not a
|
||||
requirement for getting the JIT to work.
|
||||
|
||||
We'll see in more details each of the steps required, note, though,
|
||||
that a new port may just as well start from a cut&paste of an existing
|
||||
port to a similar architecture (for example from x86 to amd64, or from
|
||||
powerpc to sparc).
|
||||
The architecture specific code is split from the rest of the JIT,
|
||||
for example the x86 specific code and data is all included in the
|
||||
following files in the distribution:
|
||||
|
||||
mini-x86.h mini-x86.c
|
||||
inssel-x86.brg
|
||||
cpu-pentium.md
|
||||
tramp-x86.c
|
||||
exceptions-x86.c
|
||||
|
||||
I suggest a similar split for other architectures as well.
|
||||
|
||||
Note that this document is still incomplete: some sections are only
|
||||
sketched and some are missing, but the important info to get a port
|
||||
going is already described.
|
||||
|
||||
|
||||
* Architecture-specific instructions and instruction selection.
|
||||
|
||||
The JIT already provides a set of instructions that can be
|
||||
easily mapped to a great variety of different processor
|
||||
instructions. Sometimes it may be necessary or advisable to
|
||||
add a new instruction that represent more closely an
|
||||
instruction in the architecture. Note that a mini instruction
|
||||
can be used to represent also a short sequence of CPU
|
||||
low-level instructions, but note that each instruction
|
||||
represents the minimum amount of code the instruction
|
||||
scheduler will handle (i.e., the scheduler won't schedule the
|
||||
instructions that compose the low-level sequence as individual
|
||||
instructions, but just the whole sequence, as an indivisible
|
||||
block).
|
||||
The JIT already provides a set of instructions that can be easily
|
||||
mapped to a great variety of different processor instructions.
|
||||
Sometimes it may be necessary or advisable to add a new instruction
|
||||
that represent more closely an instruction in the architecture.
|
||||
Note that a mini instruction can be used to represent also a short
|
||||
sequence of CPU low-level instructions, but note that each
|
||||
instruction represents the minimum amount of code the instruction
|
||||
scheduler will handle (i.e., the scheduler won't schedule the instructions
|
||||
that compose the low-level sequence as individual instructions, but just
|
||||
the whole sequence, as an indivisible block).
|
||||
New instructions are created by adding a line in the mini-ops.h file,
|
||||
assigning an opcode and a name. To specify the input and output for
|
||||
the instruction, there are two different places, depending on the context
|
||||
in which the instruction gets used.
|
||||
If the instruction is used in the tree representation, the input and output
|
||||
types are defined by the BURG rules in the *.brg files (the usual
|
||||
non-terminals are 'reg' to represent a normal register, 'lreg' to
|
||||
represent a register or two that hold a 64 bit value, freg for a
|
||||
floating point register).
|
||||
If an instruction is used as a low-level CPU instruction, the info
|
||||
is specified in a machine description file. The description file is
|
||||
processed by the genmdesc program to provide a data structure that
|
||||
can be easily used from C code to query the needed info about the
|
||||
instruction.
|
||||
As an example, let's consider the add instruction for both x86 and ppc:
|
||||
|
||||
New instructions are created by adding a line in the
|
||||
mini-ops.h file, assigning an opcode and a name. To specify
|
||||
the input and output for the instruction, there are two
|
||||
different places, depending on the context in which the
|
||||
instruction gets used.
|
||||
x86 version:
|
||||
add: dest:i src1:i src2:i len:2 clob:1
|
||||
ppc version:
|
||||
add: dest:i src1:i src2:i len:4
|
||||
|
||||
If the instruction is used in the tree representation, the
|
||||
input and output types are defined by the BURG rules in the
|
||||
*.brg files (the usual non-terminals are 'reg' to represent a
|
||||
normal register, 'lreg' to represent a register or two that
|
||||
hold a 64 bit value, freg for a floating point register).
|
||||
Note that the instruction takes two input integer registers on both CPU,
|
||||
but on x86 the first source register is clobbered (clob:1) and the length
|
||||
in bytes of the instruction differs.
|
||||
Note that integer adds and floating point adds use different opcodes, unlike
|
||||
the IL language (64 bit add is done with two instructions on 32 bit architectures,
|
||||
using a add that sets the carry and an add with carry).
|
||||
A specific CPU port may assign any meaning to the clob field for an instruction
|
||||
since the value will be processed in an arch-specific file anyway.
|
||||
See the top of the existing cpu-pentium.md file for more info on other fields:
|
||||
the info may or may not be applicable to a different CPU, in this latter case
|
||||
the info can be ignored.
|
||||
The code in mini.c together with the BURG rules in inssel.brg, inssel-float.brg
|
||||
and inssel-long32.brg provides general purpose mappings from the tree representation
|
||||
to a set of instructions that should be easily implemented in any architecture.
|
||||
To allow for additional arch-specific functionality, an arch-specific BURG file
|
||||
can be used: in this file arch-specific instructions can be selected that provide
|
||||
better performance than the general instructions or that provide functionality
|
||||
that is needed by the JIT but that cannot be expressed in a general enough way.
|
||||
As an example, x86 has the special instruction "push" to make it easier to
|
||||
implement the default call convention (passing arguments on the stack): almost
|
||||
all the other architectures don't have such an instruction (and don't need it anyway),
|
||||
so we added a special rule in the inssel-x86.brg file for it.
|
||||
|
||||
If an instruction is used as a low-level CPU instruction, the
|
||||
info is specified in a machine description file. The
|
||||
description file is processed by the genmdesc program to
|
||||
provide a data structure that can be easily used from C code
|
||||
to query the needed info about the instruction.
|
||||
So, one of the first things needed in a port is to write a cpu-$(arch).md machine
|
||||
description file and fill it with the needed info. As a start, only a few
|
||||
instructions can be specified, like the ones required to do simple integer
|
||||
operations. The default rules of the instruction selector will emit the common
|
||||
instructions and so we're ready to go for the next step in porting the JIT.
|
||||
|
||||
As an example, let's consider the add instruction for both x86
|
||||
and ppc:
|
||||
|
||||
x86 version:
|
||||
add: dest:i src1:i src2:i len:2 clob:1
|
||||
ppc version:
|
||||
add: dest:i src1:i src2:i len:4
|
||||
|
||||
Note that the instruction takes two input integer registers on
|
||||
both CPU, but on x86 the first source register is clobbered
|
||||
(clob:1) and the length in bytes of the instruction differs.
|
||||
|
||||
Note that integer adds and floating point adds use different
|
||||
opcodes, unlike the IL language (64 bit add is done with two
|
||||
instructions on 32 bit architectures, using a add that sets
|
||||
the carry and an add with carry).
|
||||
|
||||
A specific CPU port may assign any meaning to the clob field
|
||||
for an instruction since the value will be processed in an
|
||||
arch-specific file anyway.
|
||||
|
||||
See the top of the existing cpu-pentium.md file for more info
|
||||
on other fields: the info may or may not be applicable to a
|
||||
different CPU, in this latter case the info can be ignored.
|
||||
|
||||
The code in mini.c together with the BURG rules in inssel.brg,
|
||||
inssel-float.brg and inssel-long32.brg provides general
|
||||
purpose mappings from the tree representation to a set of
|
||||
instructions that should be easily implemented in any
|
||||
architecture. To allow for additional arch-specific
|
||||
functionality, an arch-specific BURG file can be used: in this
|
||||
file arch-specific instructions can be selected that provide
|
||||
better performance than the general instructions or that
|
||||
provide functionality that is needed by the JIT but that
|
||||
cannot be expressed in a general enough way.
|
||||
|
||||
As an example, x86 has the special instruction "push" to make
|
||||
it easier to implement the default call convention (passing
|
||||
arguments on the stack): almost all the other architectures
|
||||
don't have such an instruction (and don't need it anyway), so
|
||||
we added a special rule in the inssel-x86.brg file for it.
|
||||
|
||||
So, one of the first things needed in a port is to write a
|
||||
cpu-$(arch).md machine description file and fill it with the
|
||||
needed info. As a start, only a few instructions can be
|
||||
specified, like the ones required to do simple integer
|
||||
operations. The default rules of the instruction selector will
|
||||
emit the common instructions and so we're ready to go for the
|
||||
next step in porting the JIT.
|
||||
|
||||
|
||||
*) Native code emission
|
||||
|
||||
Since the first step in porting mono to a new CPU is to port
|
||||
the interpreter, there should be already a file that allows
|
||||
the emission of binary native code in a buffer for the
|
||||
architecture. This file should be placed in the
|
||||
Since the first step in porting mono to a new CPU is to port the interpreter,
|
||||
there should be already a file that allows the emission of binary native code
|
||||
in a buffer for the architecture. This file should be placed in the
|
||||
mono/arch/$(arch)/
|
||||
directory.
|
||||
|
||||
mono/arch/$(arch)/
|
||||
The bulk of the code emission happens in the mini-$(arch).c file, in a function
|
||||
called mono_arch_output_basic_block (). This function takes a basic block, walks the
|
||||
list of instructions in the block and emits the binary code for each.
|
||||
Optionally a peephole optimization pass is done on the basic block, but this can be
|
||||
left for later, when the port actually works.
|
||||
This function is very simple, there is just a big switch on the instruction opcode
|
||||
and in the corresponding case the functions or macros to emit the binary native code
|
||||
are used. Note that in this function the lengths of the instructions are used to
|
||||
determine if the buffer for the code needs enlarging.
|
||||
|
||||
directory.
|
||||
To complete the code emission for a method, a few other functions need
|
||||
implementing as well:
|
||||
|
||||
The bulk of the code emission happens in the mini-$(arch).c
|
||||
file, in a function called mono_arch_output_basic_block
|
||||
(). This function takes a basic block, walks the list of
|
||||
instructions in the block and emits the binary code for each.
|
||||
Optionally a peephole optimization pass is done on the basic
|
||||
block, but this can be left for later, when the port actually
|
||||
works.
|
||||
mono_arch_emit_prolog ()
|
||||
mono_arch_emit_epilog ()
|
||||
mono_arch_patch_code ()
|
||||
|
||||
This function is very simple, there is just a big switch on
|
||||
the instruction opcode and in the corresponding case the
|
||||
functions or macros to emit the binary native code are
|
||||
used. Note that in this function the lengths of the
|
||||
instructions are used to determine if the buffer for the code
|
||||
needs enlarging.
|
||||
|
||||
To complete the code emission for a method, a few other
|
||||
functions need implementing as well:
|
||||
|
||||
mono_arch_emit_prolog ()
|
||||
mono_arch_emit_epilog ()
|
||||
mono_arch_patch_code ()
|
||||
|
||||
mono_arch_emit_prolog () will emit the code to setup the stack
|
||||
frame for a method, optionally call the callbacks used in
|
||||
profiling and tracing, and move the arguments to their home
|
||||
location (in a caller-save register if the variable was
|
||||
allocated to one, or in a stack location if the argument was
|
||||
passed in a volatile register and wasn't allocated a
|
||||
non-volatile one). caller-save registers used by the function
|
||||
are saved in the prolog as well.
|
||||
|
||||
mono_arch_emit_epilog () will emit the code needed to return
|
||||
from the function, optionally calling the profiling or tracing
|
||||
callbacks. At this point the basic blocks or the code that was
|
||||
moved out of the normal flow for the function can be emitted
|
||||
as well (this is usually done to provide better info for the
|
||||
static branch predictor). In the epilog, caller-save
|
||||
registers are restored if they were used.
|
||||
mono_arch_emit_prolog () will emit the code to setup the stack frame for a method,
|
||||
optionally call the callbacks used in profiling and tracing, and move the
|
||||
arguments to their home location (in a caller-save register if the variable was
|
||||
allocated to one, or in a stack location if the argument was passed in a volatile
|
||||
register and wasn't allocated a non-volatile one). caller-save registers used by the
|
||||
function are saved in the prolog as well.
|
||||
|
||||
Note that, to help exception handling and stack unwinding,
|
||||
when there is a transition from managed to unmanaged code,
|
||||
some special processing needs to be done (basically, saving
|
||||
all the registers and setting up the links in the Last Managed
|
||||
Frame structure).
|
||||
|
||||
When the epilog has been emitted, the upper level code
|
||||
arranges for the buffer of memory that contains the native
|
||||
code to be copied in an area of executable memory and at this
|
||||
point, instructions that use relative addressing need to be
|
||||
patched to have the right offsets: this work is done by
|
||||
mono_arch_patch_code ().
|
||||
mono_arch_emit_epilog () will emit the code needed to return from the function,
|
||||
optionally calling the profiling or tracing callbacks. At this point the basic blocks
|
||||
or the code that was moved out of the normal flow for the function can be emitted
|
||||
as well (this is usually done to provide better info for the static branch predictor).
|
||||
In the epilog, caller-save registers are restored if they were used.
|
||||
Note that, to help exception handling and stack unwinding, when there is a transition
|
||||
from managed to unmanaged code, some special processing needs to be done (basically,
|
||||
saving all the registers and setting up the links in the Last Managed Frame
|
||||
structure).
|
||||
|
||||
When the epilog has been emitted, the upper level code arranges for the buffer of
|
||||
memory that contains the native code to be copied in an area of executable memory
|
||||
and at this point, instructions that use relative addressing need to be patched
|
||||
to have the right offsets: this work is done by mono_arch_patch_code ().
|
||||
|
||||
|
||||
* Call conventions and register allocation
|
||||
|
||||
To account for the differences in the call conventions, a few functions need to
|
||||
be implemented.
|
||||
|
||||
mono_arch_allocate_vars () assigns to both arguments and local
|
||||
variables the offset relative to the frame register where they
|
||||
are stored, dead variables are simply discarded. The total
|
||||
amount of stack needed is calculated.
|
||||
|
||||
mono_arch_call_opcode () is the function that more closely
|
||||
deals with the call convention on a given system. For each
|
||||
argument to a function call, an instruction is created that
|
||||
actually puts the argument where needed, be it the stack or a
|
||||
specific register. This function can also re-arrange th order
|
||||
of evaluation when multiple arguments are involved if needed
|
||||
(like, on x86 arguments are pushed on the stack in reverse
|
||||
order). The function needs to carefully take into accounts
|
||||
platform specific issues, like how structures are returned as
|
||||
well as the differences in size and/or alignment of managed
|
||||
and corresponding unmanaged structures.
|
||||
|
||||
The other chunk of code that needs to deal with the call
|
||||
convention and other specifics of a CPU, is the local register
|
||||
allocator, implemented in a function named
|
||||
mono_arch_local_regalloc (). The local allocator deals with a
|
||||
basic block at a time and basically just allocates registers
|
||||
for temporary values during expression evaluation, spilling
|
||||
and unspilling as necessary.
|
||||
To account for the differences in the call conventions, a few functions need to
|
||||
be implemented.
|
||||
|
||||
The local allocator needs to take into account clobbering
|
||||
information, both during simple instructions and during
|
||||
function calls and it needs to deal with other
|
||||
architecture-specific weirdnesses, like instructions that take
|
||||
inputs only in specific registers or output only is some.
|
||||
mono_arch_allocate_vars () assigns to both arguments and local variables
|
||||
the offset relative to the frame register where they are stored, dead
|
||||
variables are simply discarded. The total amount of stack needed is calculated.
|
||||
|
||||
mono_arch_call_opcode () is the function that more closely deals with the call
|
||||
convention on a given system. For each argument to a function call, an instruction
|
||||
is created that actually puts the argument where needed, be it the stack or a
|
||||
specific register. This function can also re-arrange th order of evaluation
|
||||
when multiple arguments are involved if needed (like, on x86 arguments are pushed
|
||||
on the stack in reverse order). The function needs to carefully take into accounts
|
||||
platform specific issues, like how structures are returned as well as the
|
||||
differences in size and/or alignment of managed and corresponding unmanaged
|
||||
structures.
|
||||
|
||||
The other chunk of code that needs to deal with the call convention and other
|
||||
specifics of a CPU, is the local register allocator, implemented in a function
|
||||
named mono_arch_local_regalloc (). The local allocator deals with a basic block
|
||||
at a time and basically just allocates registers for temporary
|
||||
values during expression evaluation, spilling and unspilling as necessary.
|
||||
The local allocator needs to take into account clobbering information, both
|
||||
during simple instructions and during function calls and it needs to deal
|
||||
with other architecture-specific weirdnesses, like instructions that take
|
||||
inputs only in specific registers or output only is some.
|
||||
Some effort will be put later in moving most of the local register allocator to
|
||||
a common file so that the code can be shared more for similar, risc-like CPUs.
|
||||
The register allocator does a first pass on the instructions in a block, collecting
|
||||
liveness information and in a backward pass on the same list performs the
|
||||
actual register allocation, inserting the instructions needed to spill values,
|
||||
if necessary.
|
||||
|
||||
When this part of code is implemented, some testing can be done with the generated
|
||||
code for the new architecture. Most helpful is the use of the --regression
|
||||
command line switch to run the regression tests (basic.cs, for example).
|
||||
Note that the JIT will try to initialize the runtime, but it may not be able yet to
|
||||
compile and execute complex code: commenting most of the code in the mini_init()
|
||||
function in mini.c is needed to let the JIT just compile the regression tests.
|
||||
Also, using multiple -v switches on the command line makes the JIT dump an
|
||||
increasing amount of information during compilation.
|
||||
|
||||
Some effort will be put later in moving most of the local
|
||||
register allocator to a common file so that the code can be
|
||||
shared more for similar, risc-like CPUs. The register
|
||||
allocator does a first pass on the instructions in a block,
|
||||
collecting liveness information and in a backward pass on the
|
||||
same list performs the actual register allocation, inserting
|
||||
the instructions needed to spill values, if necessary.
|
||||
|
||||
When this part of code is implemented, some testing can be
|
||||
done with the generated code for the new architecture. Most
|
||||
helpful is the use of the --regression command line switch to
|
||||
run the regression tests (basic.cs, for example).
|
||||
|
||||
Note that the JIT will try to initialize the runtime, but it
|
||||
may not be able yet to compile and execute complex code:
|
||||
commenting most of the code in the mini_init() function in
|
||||
mini.c is needed to let the JIT just compile the regression
|
||||
tests. Also, using multiple -v switches on the command line
|
||||
makes the JIT dump an increasing amount of information during
|
||||
compilation.
|
||||
|
||||
|
||||
* Method trampolines
|
||||
|
||||
To get better startup performance, the JIT actually compiles a
|
||||
method only when needed. To achieve this, when a call to a
|
||||
method is compiled, we actually emit a call to a magic
|
||||
trampoline. The magic trampoline is a function written in
|
||||
assembly that invokes the compiler to compile the given method
|
||||
and jumps to the newly compiled code, ensuring the arguments
|
||||
it received are passed correctly to the actual method.
|
||||
To get better startup performance, the JIT actually compiles a method only when
|
||||
needed. To achieve this, when a call to a method is compiled, we actually emit a
|
||||
call to a magic trampoline. The magic trampoline is a function written in assembly
|
||||
that invokes the compiler to compile the given method and jumps to the newly compiled
|
||||
code, ensuring the arguments it received are passed correctly to the actual method.
|
||||
Before jumping to the new code, though, the magic trampoline takes care of patching
|
||||
the call site so that next time the call will go directly to the method instead of the
|
||||
trampoline. How does this all work?
|
||||
mono_arch_create_jit_trampoline () creates a small function that just
|
||||
preserves the arguments passed to it and adds an additional argument (the method
|
||||
to compile) before calling the generic trampoline. This small function is called
|
||||
the specific trampoline, because it is method-specific (the method to compile
|
||||
is hard-code in the instruction stream).
|
||||
The generic trampoline saves all the arguments that could get clobbered
|
||||
and calls a C function that will do two things:
|
||||
|
||||
Before jumping to the new code, though, the magic trampoline
|
||||
takes care of patching the call site so that next time the
|
||||
call will go directly to the method instead of the
|
||||
trampoline. How does this all work?
|
||||
*) actually call the JIT to compile the method
|
||||
*) identify the calling code so that it can be patched to call directly
|
||||
the actual method
|
||||
|
||||
mono_arch_create_jit_trampoline () creates a small function
|
||||
that just preserves the arguments passed to it and adds an
|
||||
additional argument (the method to compile) before calling the
|
||||
generic trampoline. This small function is called the specific
|
||||
trampoline, because it is method-specific (the method to
|
||||
compile is hard-code in the instruction stream).
|
||||
If the 'this' argument to a method is a boxed valuetype that is passed to
|
||||
a method that expects just a pointer to the data, an additional unboxing
|
||||
trampoline will need to be inserted as well.
|
||||
|
||||
The generic trampoline saves all the arguments that could get
|
||||
clobbered and calls a C function that will do two things:
|
||||
|
||||
*) actually call the JIT to compile the method
|
||||
*) identify the calling code so that it can be patched to call directly
|
||||
the actual method
|
||||
|
||||
If the 'this' argument to a method is a boxed valuetype that
|
||||
is passed to a method that expects just a pointer to the data,
|
||||
an additional unboxing trampoline will need to be inserted as
|
||||
well.
|
||||
|
||||
|
||||
* Exception handling
|
||||
|
||||
Exception handling is likely the most difficult part of the
|
||||
port, as it needs to deal with unwinding (both managed and
|
||||
unmanaged code) and calling catch and filter blocks. It also
|
||||
needs to deal with signals, because mono takes advantage of
|
||||
the MMU in the CPU and of the operation system to handle
|
||||
dereferences of the NULL pointer. Some of the function needed
|
||||
to implement the mechanisms are:
|
||||
|
||||
mono_arch_get_throw_exception () returns a function that takes
|
||||
an exception object and invokes an arch-specific function that
|
||||
will enter the exception processing. To do so, all the
|
||||
relevant registers need to be saved and passed on.
|
||||
|
||||
mono_arch_handle_exception () this function takes the
|
||||
exception thrown and a context that describes the state of the
|
||||
CPU at the time the exception was thrown. The function needs
|
||||
to implement the exception handling mechanism, so it makes a
|
||||
search for an handler for the exception and if none is found,
|
||||
it follows the unhandled exception path (that can print a
|
||||
trace and exit or just abort the current thread). The
|
||||
difficulty here is to unwind the stack correctly, by restoring
|
||||
the register state at each call site in the call chain,
|
||||
calling finally, filters and handler blocks while doing so.
|
||||
|
||||
As part of exception handling a couple of internal calls need
|
||||
to be implemented as well.
|
||||
Exception handling is likely the most difficult part of the port, as it needs
|
||||
to deal with unwinding (both managed and unmanaged code) and calling
|
||||
catch and filter blocks. It also needs to deal with signals, because mono
|
||||
takes advantage of the MMU in the CPU and of the operation system to
|
||||
handle dereferences of the NULL pointer. Some of the function needed
|
||||
to implement the mechanisms are:
|
||||
|
||||
ves_icall_get_frame_info () returns info about a specific
|
||||
frame.
|
||||
mono_arch_get_throw_exception () returns a function that takes an exception object
|
||||
and invokes an arch-specific function that will enter the exception processing.
|
||||
To do so, all the relevant registers need to be saved and passed on.
|
||||
|
||||
mono_jit_walk_stack () walks the stack and calls a callback with info for
|
||||
each frame found.
|
||||
mono_arch_handle_exception () this function takes the exception thrown and
|
||||
a context that describes the state of the CPU at the time the exception was
|
||||
thrown. The function needs to implement the exception handling mechanism,
|
||||
so it makes a search for an handler for the exception and if none is found,
|
||||
it follows the unhandled exception path (that can print a trace and exit or
|
||||
just abort the current thread). The difficulty here is to unwind the stack
|
||||
correctly, by restoring the register state at each call site in the call chain,
|
||||
calling finally, filters and handler blocks while doing so.
|
||||
|
||||
As part of exception handling a couple of internal calls need to be implemented
|
||||
as well.
|
||||
ves_icall_get_frame_info () returns info about a specific frame.
|
||||
mono_jit_walk_stack () walks the stack and calls a callback with info for
|
||||
each frame found.
|
||||
ves_icall_get_trace () return an array of StackFrame objects.
|
||||
|
||||
ves_icall_get_trace () return an array of StackFrame objects.
|
||||
|
||||
** Code generation for filter/finally handlers
|
||||
|
||||
Filter and finally handlers are called from 2 different locations:
|
||||
|
||||
1.) from within the method containing the exception clauses
|
||||
2.) from the stack unwinding code
|
||||
|
||||
To make this possible we implement them like subroutines,
|
||||
ending with a "return" statement. The subroutine does not save
|
||||
the base pointer, because we need access to the local
|
||||
variables of the enclosing method. Its is possible that
|
||||
instructions inside those handlers modify the stack pointer,
|
||||
thus we save the stack pointer at the start of the handler,
|
||||
and restore it at the end. We have to use a "call" instruction
|
||||
to execute such finally handlers.
|
||||
|
||||
The MIR code for filter and finally handlers looks like:
|
||||
|
||||
OP_START_HANDLER
|
||||
...
|
||||
OP_END_FINALLY | OP_ENDFILTER(reg)
|
||||
|
||||
OP_START_HANDLER: should save the stack pointer somewhere
|
||||
OP_END_FINALLY: restores the stack pointers and returns.
|
||||
OP_ENDFILTER (reg): restores the stack pointers and returns the value in "reg".
|
||||
|
||||
Filter and finally handlers are called from 2 different locations:
|
||||
|
||||
1.) from within the method containing the exception clauses
|
||||
2.) from the stack unwinding code
|
||||
|
||||
To make this possible we implement them like subroutines, ending with a
|
||||
"return" statement. The subroutine does not save the base pointer, because we
|
||||
need access to the local variables of the enclosing method. Its is possible
|
||||
that instructions inside those handlers modify the stack pointer, thus we save
|
||||
the stack pointer at the start of the handler, and restore it at the end. We
|
||||
have to use a "call" instruction to execute such finally handlers.
|
||||
|
||||
The MIR code for filter and finally handlers looks like:
|
||||
|
||||
OP_START_HANDLER
|
||||
...
|
||||
OP_END_FINALLY | OP_ENDFILTER(reg)
|
||||
|
||||
OP_START_HANDLER: should save the stack pointer somewhere
|
||||
OP_END_FINALLY: restores the stack pointers and returns.
|
||||
OP_ENDFILTER (reg): restores the stack pointers and returns the value in "reg".
|
||||
|
||||
** Calling finally/filter handlers
|
||||
|
||||
There is a special opcode to call those handler, its called
|
||||
OP_CALL_HANDLER. It simple emits a call instruction.
|
||||
|
||||
Its a bit more complex to call handler from outside (in the
|
||||
stack unwinding code), because we have to restore the whole
|
||||
context of the method first. After that we simply emit a call
|
||||
instruction to invoke the handler. Its usually possible to use
|
||||
the same code to call filter and finally handlers (see
|
||||
arch_get_call_filter).
|
||||
|
||||
There is a special opcode to call those handler, its called OP_CALL_HANDLER. It
|
||||
simple emits a call instruction.
|
||||
|
||||
Its a bit more complex to call handler from outside (in the stack unwinding
|
||||
code), because we have to restore the whole context of the method first. After that
|
||||
we simply emit a call instruction to invoke the handler. Its usually
|
||||
possible to use the same code to call filter and finally handlers (see
|
||||
arch_get_call_filter).
|
||||
|
||||
** Calling catch handlers
|
||||
|
||||
Catch handlers are always called from the stack unwinding
|
||||
code. Unlike finally clauses or filters, catch handler never
|
||||
return. Instead we simply restore the whole context, and
|
||||
restart execution at the catch handler.
|
||||
|
||||
Catch handlers are always called from the stack unwinding code. Unlike finally clauses
|
||||
or filters, catch handler never return. Instead we simply restore the whole
|
||||
context, and restart execution at the catch handler.
|
||||
|
||||
** Passing Exception objects to catch handlers and filters.
|
||||
|
||||
We use a local variable to store exception objects. The stack
|
||||
unwinding code must store the exception object into this
|
||||
variable before calling catch handler or filter.
|
||||
|
||||
We use a local variable to store exception objects. The stack unwinding code
|
||||
must store the exception object into this variable before calling catch handler
|
||||
or filter.
|
||||
|
||||
* Minor helper methods
|
||||
|
||||
A few minor helper methods are referenced from the arch-independent code.
|
||||
Some of them are:
|
||||
|
||||
*) mono_arch_cpu_optimizations ()
|
||||
This function returns a mask of optimizations that
|
||||
should be enabled for the current CPU and a mask of
|
||||
optimizations that should be excluded, instead.
|
||||
|
||||
*) mono_arch_regname ()
|
||||
Returns the name for a numeric register.
|
||||
|
||||
*) mono_arch_get_allocatable_int_vars ()
|
||||
Returns a list of variables that can be allocated to
|
||||
the integer registers in the current architecture.
|
||||
|
||||
*) mono_arch_get_global_int_regs ()
|
||||
Returns a list of caller-save registers that can be
|
||||
used to allocate variables in the current method.
|
||||
|
||||
*) mono_arch_instrument_mem_needs ()
|
||||
*) mono_arch_instrument_prolog ()
|
||||
*) mono_arch_instrument_epilog ()
|
||||
Functions needed to implement the profiling interface.
|
||||
|
||||
|
||||
A few minor helper methods are referenced from the arch-independent code.
|
||||
Some of them are:
|
||||
|
||||
*) mono_arch_cpu_optimizations ()
|
||||
This function returns a mask of optimizations that should be enabled for the
|
||||
current CPU and a mask of optimizations that should be excluded, instead.
|
||||
|
||||
*) mono_arch_regname ()
|
||||
Returns the name for a numeric register.
|
||||
|
||||
*) mono_arch_get_allocatable_int_vars ()
|
||||
Returns a list of variables that can be allocated to the integer registers
|
||||
in the current architecture.
|
||||
|
||||
*) mono_arch_get_global_int_regs ()
|
||||
Returns a list of caller-save registers that can be used to allocate variables
|
||||
in the current method.
|
||||
|
||||
*) mono_arch_instrument_mem_needs ()
|
||||
*) mono_arch_instrument_prolog ()
|
||||
*) mono_arch_instrument_epilog ()
|
||||
Functions needed to implement the profiling interface.
|
||||
|
||||
|
||||
* Writing regression tests
|
||||
|
||||
Regression tests for the JIT should be written for any bug
|
||||
found in the JIT in one of the *.cs files in the mini
|
||||
directory. Eventually all the operations of the JIT should be
|
||||
tested (including the ones that get selected only when some
|
||||
specific optimization is enabled).
|
||||
|
||||
Regression tests for the JIT should be written for any bug found in the JIT
|
||||
in one of the *.cs files in the mini directory. Eventually all the operations
|
||||
of the JIT should be tested (including the ones that get selected only when
|
||||
some specific optimization is enabled).
|
||||
|
||||
|
||||
* Platform specific optimizations
|
||||
|
||||
An example of a platform-specific optimization is the peephole
|
||||
optimization: we look at a small window of code at a time and
|
||||
we replace one or more instructions with others that perform
|
||||
better for the given architecture or CPU.
|
||||
|
||||
An example of a platform-specific optimization is the peephole optimization:
|
||||
we look at a small window of code at a time and we replace one or more
|
||||
instructions with others that perform better for the given architecture or CPU.
|
||||
|
||||
+2
-1
@@ -1,4 +1,5 @@
|
||||
man_MANS = mcs.1 mono.1 monostyle.1 mono-config.5 sqlsharp.1 oldmono.1 ilasm.1 \
|
||||
cert2spc.1 cilc.1 genxs.1 wsdl.1 disco.1 soapsuds.1
|
||||
cert2spc.1 cilc.1
|
||||
|
||||
EXTRA_DIST = $(man_MANS)
|
||||
|
||||
@@ -1,37 +0,0 @@
|
||||
.\"
|
||||
.\" chktrust manual page.
|
||||
.\" Copyright 2003 Motus Technologies
|
||||
.\" Author:
|
||||
.\" Sebastien Pouliot ([email protected])
|
||||
.\"
|
||||
.TH Mono "chktrust"
|
||||
.SH NAME
|
||||
chktrust \- Check the trust of a PE executable.
|
||||
.SH SYNOPSIS
|
||||
.PP
|
||||
.B chktrust [options] filename
|
||||
.SH DESCRIPTION
|
||||
Verify if an PE executable (CLR assembly, Win32 EXE or DLL) has a valid
|
||||
Authenticode(r) signature that can be traced back to a trusted certificate
|
||||
authority (CA).
|
||||
.SH OPTIONS
|
||||
.TP
|
||||
.I "-q", "-quiet"
|
||||
Limited display on console.
|
||||
.TP
|
||||
.I "-v", "-verbose"
|
||||
More details displayed on the console.
|
||||
.TP
|
||||
.I "-help", "-h", "-?", "/?"
|
||||
Display help about this tool.
|
||||
.SH AUTHOR
|
||||
Written by Sebastien Pouliot
|
||||
.SH COPYRIGHT
|
||||
Copyright (C) 2003 Motus Technologies.
|
||||
Released under BSD license.
|
||||
.SH MAILING LISTS
|
||||
Visit http://mail.ximian.com/mailman/mono-list for details.
|
||||
.SH WEB SITE
|
||||
Visit: http://www.go-mono.com for details
|
||||
.SH SEE ALSO
|
||||
.BR signcode(1), makecert(1)
|
||||
-68
@@ -1,68 +0,0 @@
|
||||
.\"
|
||||
.\" disco manual page.
|
||||
.\" (C) 2003 Novell, Inc.
|
||||
.\" Author:
|
||||
.\" Lluis Sanchez Gual ([email protected])
|
||||
.\"
|
||||
.TH disco 1
|
||||
.SH NAME
|
||||
disco \- Mono's Web Service Discovery Tool
|
||||
.SH SYNOPSIS
|
||||
.PP
|
||||
.B disco
|
||||
[options] url
|
||||
.SH DESCRIPTION
|
||||
.I disco
|
||||
is a tool for discovering web services and for retireving the documents that
|
||||
describe those services.
|
||||
.PP
|
||||
.I url
|
||||
is the location of a DISCO document, which includes a list of WSDL documents,
|
||||
XML schemas and references to other DISCO documents.
|
||||
.PP
|
||||
.I disco
|
||||
downloads the DISCO document and all referenced documents (unless
|
||||
the
|
||||
.I "-nosave"
|
||||
option is specified), and saves them to disk.
|
||||
.SH OPTIONS
|
||||
The following options are available:
|
||||
.TP
|
||||
.I "-nologo"
|
||||
Supress the startup logo.
|
||||
.TP
|
||||
.I "-nosave"
|
||||
Do not save the discovered documents to disk. The default is to save the documents.
|
||||
.TP
|
||||
.I "-o:directory", "-out:directory"
|
||||
The directory where to save the discovered documents.
|
||||
By default, documents are saved in the current directory.
|
||||
.TP
|
||||
.I "-u:username", "-user:username"
|
||||
The user name to use when connecting to the server.
|
||||
.TP
|
||||
.I "-p:password", "-password:password"
|
||||
The password to use when connecting to the server.
|
||||
.TP
|
||||
.I "-d:domain", "-domain:domain"
|
||||
The domain to use when connecting to the server.
|
||||
.TP
|
||||
.I "-proxy:url"
|
||||
The url of the proxy server to use for http requests.
|
||||
.TP
|
||||
.I "-proxyusername:username"
|
||||
The user name to use when connecting to the proxy.
|
||||
.TP
|
||||
.I "-proxypassword:password"
|
||||
The password to use when connecting to the proxy.
|
||||
.TP
|
||||
.I "-proxydomain:domain"
|
||||
The domain to use when connecting to the proxy.
|
||||
.SH AUTHORS
|
||||
Lluis Sanchez Gual ([email protected])
|
||||
.PP
|
||||
.SH LICENSE
|
||||
disco is released under the terms of the GNU GPL.
|
||||
.PP
|
||||
.SH SEE ALSO
|
||||
wsdl(1), soapsuds(1), mono(1), mcs(1)
|
||||
-294
@@ -1,294 +0,0 @@
|
||||
.\"
|
||||
.\" genxs manual page.
|
||||
.\" (C) Lluis Sanchez Gual ([email protected])
|
||||
.\"
|
||||
.TH genxs 1
|
||||
.SH NAME
|
||||
genxs \- Mono's Xml Serializer Generator
|
||||
.SH SYNOPSIS
|
||||
.PP
|
||||
.B genxs
|
||||
configurationFile [destinationFolder]
|
||||
.SH DESCRIPTION
|
||||
.I genxs
|
||||
is a tool for generating custom XML serialization writers and readers for
|
||||
classes.
|
||||
.PP
|
||||
.I configurationFile
|
||||
is configuration file which specifies several
|
||||
information, such as the class for which to generate the reader and writer, the
|
||||
name and namespace of the classes to generate, and a collection of hooks to
|
||||
apply. By using hooks it is possible to customize the
|
||||
behavior of the serializer without needing to modify the generated file, so you
|
||||
can safely regenerate it if the source class is modified.
|
||||
.PP
|
||||
.I destinationFolder
|
||||
specifies the folder where the files will be generated.
|
||||
.PP
|
||||
.B NOTE:
|
||||
This tool only runs in the Mono runtime, since it uses some internal
|
||||
classes not available in other runtimes.
|
||||
.SH CONFIGURATION FILE FORMAT
|
||||
The configuration file is an xml document based on the following grammar
|
||||
("?" means optional, "*" 0 or more):
|
||||
.PP
|
||||
.nf
|
||||
<configuration>
|
||||
<serializer class="name" assembly="name"> *
|
||||
<reader>name</reader> ?
|
||||
<writer>name</writer> ?
|
||||
<namespace>name</namespace> ?
|
||||
<outFileName>name</outFileName> ?
|
||||
<readerHooks> ?
|
||||
<hook ...> *
|
||||
</readerHooks>
|
||||
<writerHooks> ?
|
||||
<hook ...> *
|
||||
</writerHooks>
|
||||
</serializer>
|
||||
</configuration>
|
||||
.fi
|
||||
.PP
|
||||
A configuration file can have multiple "serializer" elements, each of which
|
||||
specifies the class for which to generate a serializer together with several
|
||||
generation options. The source class is specified in the following attributes:
|
||||
.PP
|
||||
.IP " *" 5
|
||||
.I class
|
||||
: name of the class (including namespace).
|
||||
.IP " *" 5
|
||||
.I assembly
|
||||
: assembly name. It can include the complete path.
|
||||
.PP
|
||||
Generation options are specified in child elements:
|
||||
.PP
|
||||
.IP " *" 5
|
||||
.I reader
|
||||
: name of the reader class.
|
||||
.IP " *" 5
|
||||
.I writer
|
||||
: name of the writer class.
|
||||
.IP " *" 5
|
||||
.I namespace
|
||||
: namespace of the reader and writer classes.
|
||||
.IP " *" 5
|
||||
.I outFileName
|
||||
: name of the generated file.
|
||||
.IP " *" 5
|
||||
.I readerHooks
|
||||
: a list of hooks to apply to the reader.
|
||||
.IP " *" 5
|
||||
.I writerHooks
|
||||
: a list of hooks to apply to the writer.
|
||||
.SH SPECIFYING HOOKS
|
||||
Using hooks you can customize the behavior of readers and writers.
|
||||
A hook specification follows this grammar:
|
||||
.PP
|
||||
.nf
|
||||
<hook type="name">
|
||||
<select> ?
|
||||
<typeName>name</typeName> ?
|
||||
<typeAttribute>name</typeAttribute> *
|
||||
<typeMember>name</typeMember> ?
|
||||
</select>
|
||||
<replace>source code</replace> ?
|
||||
<insertBefore>source code</insertBefore> ?
|
||||
<insertAfter>source code</insertAfter> ?
|
||||
</hook>
|
||||
.fi
|
||||
.PP
|
||||
The "type" attribute specifies the context in which the hook is applied. It can
|
||||
be one of the following:
|
||||
.PP
|
||||
.IP " *" 5
|
||||
.I attributes
|
||||
: hook is applied where attributes are serialized/deserialized.
|
||||
.IP " *" 5
|
||||
.I elements
|
||||
: hook is applied where elements are serialized/deserialized.
|
||||
.IP " *" 5
|
||||
.I unknownAttribute
|
||||
: hook is applied where unknown attributes are processed.
|
||||
.IP " *" 5
|
||||
.I unknownElement
|
||||
: hook is applied where unknown elements are processed.
|
||||
.IP " *" 5
|
||||
.I member
|
||||
: hook is applied where a member is serialized/deserialized.
|
||||
.IP " *" 5
|
||||
.I type
|
||||
: hook is applied for the whole type.
|
||||
.PP
|
||||
The "select" element specifies the classes and members to which the hook has
|
||||
to be added. It can contain the following elements:
|
||||
.PP
|
||||
.IP " *" 5
|
||||
.I typeName
|
||||
: the class with that name will be selected (must include namespace)
|
||||
.IP " *" 5
|
||||
.I typeAttribute
|
||||
: all classes which have that attribute applied will be selected (specify the
|
||||
full attribute class name, including namespace). Several attribute names can be
|
||||
specified.
|
||||
.IP " *" 5
|
||||
.I typeMember
|
||||
: name of the class member for which the hook must be added.
|
||||
.PP
|
||||
The hook source code can be specified using any of the following elements:
|
||||
.PP
|
||||
.IP " *" 5
|
||||
.I replace
|
||||
: the provided source code will replace all serialization/deserialization
|
||||
operations in the hook context.
|
||||
.IP " *" 5
|
||||
.I insertBefore
|
||||
: the source code will be added before the hook context.
|
||||
.IP " *" 5
|
||||
.I insertAfter
|
||||
: the source code will be added after the hook context.
|
||||
.PP
|
||||
When writing the code for a hook you can use some special variables that are
|
||||
defined during the code generation process. The variables are the following:
|
||||
.PP
|
||||
.IP " *" 5
|
||||
.I $TYPE:
|
||||
name of the class being generated, without namespace.
|
||||
.IP " *" 5
|
||||
.I $FULLTYPE:
|
||||
full name of the class being generated, including namespace.
|
||||
.IP " *" 5
|
||||
.I $OBJECT:
|
||||
the object being serialized or deserialized. When using a replace
|
||||
reader hook of type "type", the hook code must assign the deserialized object
|
||||
to this variable.
|
||||
.IP " *" 5
|
||||
-I $ELEMENT:
|
||||
name of the element of the object being serialized/deserialized.
|
||||
.IP " *" 5
|
||||
.I $NAMESPACE:
|
||||
namespace of the element of the object being serialized/deserialized.
|
||||
.IP " *" 5
|
||||
.I $MEMBER:
|
||||
name of the member being serialized/deserialized. Only valid in the "member"
|
||||
context.
|
||||
.SH HOOK EXAMPLES
|
||||
The following example adds a call to a Validate method after the deserialization
|
||||
of any object:
|
||||
.PP
|
||||
.nf
|
||||
<hook type="type">
|
||||
<insertAfter>
|
||||
System.Xml.Schema.XmlSchema.Validate$TYPE ($OBJECT);
|
||||
</insertAfter>
|
||||
</hook>
|
||||
.fi
|
||||
.PP
|
||||
This example specifies the code to be used to deserialize the XmlSchema class:
|
||||
.PP
|
||||
.nf
|
||||
<hook type="type">
|
||||
<select>
|
||||
<typeName>System.Xml.Schema.XmlSchema</typeName>
|
||||
</select>
|
||||
<replace>
|
||||
$OBJECT = System.Xml.Schema.XmlSchema.Read (Reader, null);
|
||||
</replace>
|
||||
</hook>
|
||||
.fi
|
||||
.PP
|
||||
That one specifies the code to be used to read XmlSchema instances:
|
||||
.PP
|
||||
.nf
|
||||
<hook type="type">
|
||||
<select>
|
||||
<typeName>System.Xml.Schema.XmlSchema</typeName>
|
||||
</select>
|
||||
<replace>$OBJECT.Write (Writer);</replace>
|
||||
</hook>
|
||||
.fi
|
||||
.PP
|
||||
With this two hooks the serializer will print some information when serializing
|
||||
the class "MyClass":
|
||||
.PP
|
||||
.nf
|
||||
<hook type="type">
|
||||
<select>
|
||||
<typeName>MyNamespace.MyClass</typeName>
|
||||
</select>
|
||||
<insertBefore>Console.WriteLine ("Serializing MyClass");</replace>
|
||||
<insertAfter>Console.WriteLine ("MyClass serialized");</insertAfter>
|
||||
</hook>
|
||||
<hook type="member">
|
||||
<select>
|
||||
<typeName>MyNamespace.MyClass</typeName>
|
||||
</select>
|
||||
<insertAfter>
|
||||
Console.WriteLine ("Serialized member $MEMBER");
|
||||
</insertAfter>
|
||||
</hook>
|
||||
.fi
|
||||
.PP
|
||||
This hook writes an additional element for all types that have the custom
|
||||
attribute "MyAttribute":
|
||||
.PP
|
||||
.nf
|
||||
<hook type="elements">
|
||||
<select>
|
||||
<typeAttribute>MyNamespace.MyAttribute</typeAttribute>
|
||||
</select>
|
||||
<insertAfter>
|
||||
Writer.WriteStartElement ("privateData");
|
||||
Writer.WriteString ($OBJECT.PrivateData);
|
||||
Writer.WriteEndElement ();
|
||||
</insertAfter>
|
||||
</hook>
|
||||
.fi
|
||||
.SH CONFIGURATION FILE EXAMPLE
|
||||
This is the configuration file used to generate the serializer for ServiceDescription:
|
||||
.PP
|
||||
.nf
|
||||
<configuration>
|
||||
<serializer class="System.Web.Services.Description.ServiceDescription" assembly="System.Web.Services">
|
||||
<reader>ServiceDescriptionReaderBase</reader>
|
||||
<writer>ServiceDescriptionWriterBase</writer>
|
||||
<namespace>System.Web.Services.Description</namespace>
|
||||
<outFileName>ServiceDescriptionSerializerBase.cs</outFileName>
|
||||
<readerHooks>
|
||||
<hook type="unknownElement">
|
||||
<select>
|
||||
<typeAttribute>System.Web.Services.Configuration.XmlFormatExtensionPointAttribute</typeAttribute>
|
||||
</select>
|
||||
<replace>ServiceDescription.ReadExtension (Reader, $OBJECT);</replace>
|
||||
</hook>
|
||||
<hook type="type">
|
||||
<select>
|
||||
<typeName>System.Xml.Schema.XmlSchema</typeName>
|
||||
</select>
|
||||
<replace>$OBJECT = System.Xml.Schema.XmlSchema.Read (Reader, null);</replace>
|
||||
</hook>
|
||||
</readerHooks>
|
||||
<writerHooks>
|
||||
<hook type="elements">
|
||||
<select>
|
||||
<typeAttribute>System.Web.Services.Configuration.XmlFormatExtensionPointAttribute</typeAttribute>
|
||||
</select>
|
||||
<insertBefore>ServiceDescription.WriteExtensions (Writer, $OBJECT);</insertBefore>
|
||||
</hook>
|
||||
<hook type="type">
|
||||
<select>
|
||||
<typeName>System.Xml.Schema.XmlSchema</typeName>
|
||||
</select>
|
||||
<replace>$OBJECT.Write (Writer);</replace>
|
||||
</hook>
|
||||
</writerHooks>
|
||||
</serializer>
|
||||
</configuration>
|
||||
.fi
|
||||
.SH AUTHORS
|
||||
Lluis Sanchez Gual ([email protected])
|
||||
.PP
|
||||
.SH LICENSE
|
||||
GenXS is released under the terms of the GNU GPL.
|
||||
.PP
|
||||
.SH SEE ALSO
|
||||
mono(1), mcs(1)
|
||||
+1
-9
@@ -9,13 +9,5 @@
|
||||
<manpage name="Sql#" page="sqlsharp.1" />
|
||||
<manpage name="SecUtil" page="secutil.1" />
|
||||
<manpage name="MonoStyle" page="monostyle.1" />
|
||||
<manpage name="genxs" page="genxs.1" />
|
||||
<manpage name="cert2spc" page="cert2spc.1" />
|
||||
<manpage name="makecert" page="makecert.1" />
|
||||
<manpage name="chktrust" page="chktrust.1" />
|
||||
<manpage name="signcode" page="signcode.1" />
|
||||
<manpage name="sn" page="sn.1" />
|
||||
<manpage name="wsdl" page="wsdl.1" />
|
||||
<manpage name="disco" page="disco.1" />
|
||||
<manpage name="soapsuds" page="soapsuds.1" />
|
||||
|
||||
</manpages>
|
||||
@@ -36,9 +36,6 @@ Executables are not bound to a specific CPU or operating system.
|
||||
.I \-\-about
|
||||
Displays information about the Mono C# compiler
|
||||
.TP
|
||||
.I \-\-addmodule:MODULE1[,MODULE2]
|
||||
Includes the specified modules in the resulting assembly.
|
||||
.TP
|
||||
.I -checked, -checked+
|
||||
Sets the default compilation mode to `checked'. This makes all
|
||||
the math operations checked (the default is unchecked).
|
||||
@@ -117,15 +114,6 @@ name will be the file name.
|
||||
Links to the specified RESOURCE. The optional ID can be used to give
|
||||
a name to the linked resource.
|
||||
.TP
|
||||
.I -r:ASSEMBLY1[,ASSEMBLY2], \-r ASSEMBLY1[,ASSEMBLY2]
|
||||
Reference the named assemblies. Use this to use classes from the named
|
||||
assembly in your program. The assembly will be loaded from either the
|
||||
system directory where all the assemblies live, or from the path
|
||||
explicitly given with the -L option.
|
||||
.PP
|
||||
You can also use a semicolon to separate the assemblies instead of a
|
||||
comma.
|
||||
.TP
|
||||
.I \-recurse:PATTERN, --recurse PATTERN
|
||||
Does recursive compilation using the specified pattern. In Unix the
|
||||
shell will perform globbing, so you migth want to use it like this:
|
||||
@@ -135,9 +123,8 @@ shell will perform globbing, so you migth want to use it like this:
|
||||
.fi
|
||||
.TP
|
||||
.I \-target:KIND, \-t:KIND
|
||||
Used to specify the desired target. The possible values are: exe
|
||||
(plain executable), winexe (Windows.Forms executable), library
|
||||
(component libraries) and module (partial library).
|
||||
Used to specify the desired target. The possible values are: exe,
|
||||
winexe, library and module.
|
||||
.TP
|
||||
.I \-\-timestamp
|
||||
Another debugging flag. Used to display the times at various points
|
||||
@@ -146,6 +133,22 @@ in the compilation process.
|
||||
.I \-unsafe, -unsafe+
|
||||
Enables compilation of unsafe code.
|
||||
.TP
|
||||
.I \-warnaserror, \-warnaserror+
|
||||
Treat warnings as errors.
|
||||
.TP
|
||||
.I \-warn:LEVEL
|
||||
Sets the warning level. 0 is the lowest warning level, and 4 is the
|
||||
highest. The default is 2.
|
||||
.TP
|
||||
.I -r:ASSEMBLY1[,ASSEMBLY2], \-r ASSEMBLY1[,ASSEMBLY2]
|
||||
Reference the named assemblies. Use this to use classes from the named
|
||||
assembly in your program. The assembly will be loaded from either the
|
||||
system directory where all the assemblies live, or from the path
|
||||
explicitly given with the -L option.
|
||||
.PP
|
||||
You can also use a semicolon to separate the assemblies instead of a
|
||||
comma.
|
||||
.TP
|
||||
.I \-v
|
||||
Debugging. Turns on verbose yacc parsing.
|
||||
.TP
|
||||
@@ -155,21 +158,6 @@ Turns on C# 2.0 language features.
|
||||
.I \-\-version
|
||||
Shows the compiler version.
|
||||
.TP
|
||||
.I \-warnaserror, \-warnaserror+
|
||||
Treat warnings as errors.
|
||||
.TP
|
||||
.I \-warn:LEVEL
|
||||
Sets the warning level. 0 is the lowest warning level, and 4 is the
|
||||
highest. The default is 2.
|
||||
.TP
|
||||
.I \-win32res:FILE
|
||||
Specifies a Win32 resource file (.res) to be bundled into the
|
||||
resulting assembly.
|
||||
.TP
|
||||
.I \-win32icon:FILE
|
||||
Attaches the icon specified in FILE on the output into the resulting
|
||||
assembly.
|
||||
.TP
|
||||
.I \-\-
|
||||
Use this to stop option parsing, and allow option-looking parameters
|
||||
to be passed on the command line.
|
||||
@@ -207,9 +195,7 @@ for details on how to use this file.
|
||||
.SH NOTES
|
||||
During compilation the MCS compiler defines the __MonoCS__ symbol,
|
||||
this can be used by pre-processor instructions to compile Mono C#
|
||||
compiler specific code. Please note that this symbol is only to test
|
||||
for the compiler, and is not useful to distinguish compilation or
|
||||
deployment platforms.
|
||||
compiler specific code.
|
||||
.SH AUTHORS
|
||||
The Mono C# Compiler was written by Miguel de Icaza, Ravi Pratap and
|
||||
Martin Baulig at Ximian.
|
||||
|
||||
+10
-88
@@ -115,9 +115,8 @@ Instructs the runtime to collect profiling information about execution
|
||||
times and memory allocation, and dump it at the end of the execution.
|
||||
If a profiler is not specified, the default profiler is used. profiler_args
|
||||
is a profiler-specific string of options for the profiler itself.
|
||||
.PP
|
||||
The default profiler accepts -time and -alloc to options to disable
|
||||
the time profiling or the memory allocation profilng.
|
||||
|
||||
|
||||
.SH JIT MAINTAINER OPTIONS
|
||||
The maintainer options are only used by those developing the runtime
|
||||
itself, and not typically of interest to runtime users or developers.
|
||||
@@ -168,45 +167,10 @@ breakpoint on the application's main method.
|
||||
Inserts a breakpoint on exceptions. This allows you to debug your
|
||||
application with a native debugger when an exception is thrown.
|
||||
.TP
|
||||
.I "--trace[=expression]"
|
||||
Shows method names as they are invoked. By default all methods are
|
||||
traced.
|
||||
.TP
|
||||
The trace can be customized to include or exclude methods, classes or
|
||||
assemblies. A trace expression is a comma separated list of targets,
|
||||
each target can be prefixed with a minus sign to turn off a particular
|
||||
target. The words `program' and `all' have special meaning.
|
||||
`program' refers to the main program being executed, and `all' means
|
||||
all the method calls.
|
||||
.TP
|
||||
Assemblies are specified by their name, for example, to trace all
|
||||
calls in the System assembly, use:
|
||||
.nf
|
||||
mono --trace=System app.exe
|
||||
.fi
|
||||
Classes are specified with the T: prefix. For example, to trace all
|
||||
calls to the System.String class, use:
|
||||
.nf
|
||||
mono --trace=T:System.String app.exe
|
||||
.fi
|
||||
And individual methods are referenced with the M: prefix, and the
|
||||
standar method notation:
|
||||
.nf
|
||||
mono --trace=M:System.Console.WriteLine app.exe
|
||||
.fi
|
||||
As previously noted, various rules can be specified at once:
|
||||
.nf
|
||||
mono --trace=T:System.String,T:System.Random app.exe
|
||||
.fi
|
||||
You can exclude pieces, the next example traces calls to
|
||||
System.String except for the System.String:Concat method.
|
||||
.nf
|
||||
mono --trace=T:System.String,-M:System.String:Concat
|
||||
.fi
|
||||
Finally, namespaces can be specified using the N: prefix:
|
||||
.nf
|
||||
mono --trace=N:System.Xml
|
||||
.fi
|
||||
.I "--trace"
|
||||
Shows method names as they are invoked.
|
||||
|
||||
|
||||
.SH ENVIRONMENT VARIABLES
|
||||
.TP
|
||||
.I "GC_DONT_GC"
|
||||
@@ -219,10 +183,9 @@ Directories are separated by the platform path separator (colons on unix). Examp
|
||||
.B /home/username/lib:/usr/local/mono/lib
|
||||
.TP
|
||||
.I "MONO_DISABLE_SHM"
|
||||
If this variable is set, it disables the shared memory part of the
|
||||
Windows I/O Emulation layer, and handles (files, events, mutexes,
|
||||
pipes) will not be shared across processes. Process creation is also
|
||||
disabled. This option is only available on Unix.
|
||||
If this variable is set, it disables the Windows I/O Emulation layer,
|
||||
and handles (files, events, mutexes, pipes) will not be shared across
|
||||
processes. This option is only available on Unix.
|
||||
.TP
|
||||
.I "MONO_CFG_DIR"
|
||||
If set, this variable overrides the default system configuration directory
|
||||
@@ -232,45 +195,6 @@ If set, this variable overrides the default system configuration directory
|
||||
If set, this variable overrides the default runtime configuration file
|
||||
($PREFIX/etc/mono/config). The --config command line options overrides the
|
||||
environment variable.
|
||||
.TP
|
||||
.I "MONO_DEBUG"
|
||||
If set, enables some features of the runtime useful for debugging.
|
||||
Currently it only makes the runtime display the stack traces for all the
|
||||
threads running and exit. It may not exit cleanly. Use at your own risk.
|
||||
.TP
|
||||
.I "MONO_EXTERNAL_ENCODINGS"
|
||||
If set, contains a colon-separated list of text encodings to try when
|
||||
turning externally-generated text (e.g. command-line arguments or
|
||||
filenames) into unicode. The encoding names come from the list
|
||||
provided by iconv, and the special case "default_locale" which refers
|
||||
to the current locale's default encoding.
|
||||
.TP
|
||||
When reading externally-generated text strings UTF-8 is tried first,
|
||||
and then this list is tried in order with the first successful
|
||||
conversion ending the search. When writing external text (e.g. new
|
||||
filenames or arguments to new processes) the first item in this list
|
||||
is used, or UTF-8 if the environment variable is not set.
|
||||
.TP
|
||||
.I "MONO_SHARED_DIR"
|
||||
If set its the directory where the ".wapi" handle state is stored.
|
||||
This is the directory where the Windows I/O Emulation layer stores its
|
||||
shared state data (files, events, mutexes, pipes). By default Mono
|
||||
will store the ".wapi" directory in the users's home directory.
|
||||
.TP
|
||||
.I "MONO_UNMANAGED_XSLT"
|
||||
If set any value, System.Xml.Xsl.XslTransform uses libxslt-based
|
||||
transformation engine (a.k.a Unmanaged XSLT). Unmanaged XSLT has
|
||||
long been used for XSLT engine while Managed XSLT engine is so
|
||||
new and might have some bugs. Basically we recommend Managed XSLT
|
||||
solution, but if it contains some blocking bugs, then you can also
|
||||
use traditional libxslt. If you want to use msxsl:script, you have
|
||||
to select Managed XSLT.
|
||||
.TP
|
||||
.I "MONO_MANAGED_WATCHER"
|
||||
If set to any value, System.IO.FileSystemWatcher will use the default
|
||||
managed implementation (slow). If unset, mono will try to use FAM under
|
||||
Unix systems and native API calls on Windows, falling back to the
|
||||
managed implementation on error.
|
||||
.SH FILES
|
||||
On Unix assemblies are loaded from the installation lib directory. If you set
|
||||
`prefix' to /usr, the assemblies will be located in /usr/lib. On
|
||||
@@ -286,8 +210,6 @@ Visit http://mail.ximian.com/mailman/mono-list for details.
|
||||
.SH WEB SITE
|
||||
Visit: http://www.go-mono.com for details
|
||||
.SH SEE ALSO
|
||||
.BR mcs(1), mint(1), monodis(1), mono-config(5).
|
||||
.PP
|
||||
For ASP.NET-related documentation, see the xsp(1) manual page
|
||||
.BR mcs(1), mint(1), monodis(1), mono-config(5)
|
||||
|
||||
|
||||
@@ -1,81 +0,0 @@
|
||||
.\"
|
||||
.\" signcode manual page.
|
||||
.\" Copyright 2003 Motus Technologies
|
||||
.\" Author:
|
||||
.\" Sebastien Pouliot ([email protected])
|
||||
.\"
|
||||
.TH Mono "signcode"
|
||||
.SH NAME
|
||||
signcode \- Digitally sign an PE executable using an X.509 certificate.
|
||||
.SH SYNOPSIS
|
||||
.PP
|
||||
.B signcode [options] filename
|
||||
.SH DESCRIPTION
|
||||
Digitally sign an PE executable (CLR assembly, Win32 EXE or DLL) using an
|
||||
X.509 certificate and it's associated private key. The signature is compatible
|
||||
with Authenticode(r) and can be validated with chktrust.
|
||||
.SH OPTIONS
|
||||
.TP
|
||||
.I "-spc spcfile"
|
||||
The Software Publisher File (spc) that contains the X.509 certificate chain
|
||||
used to digitally sign the PE executable.
|
||||
.TP
|
||||
.I "-v pvkfile"
|
||||
The Private Key File (pvk) that contains the private key used to digitally
|
||||
sign the PE executable. This private key must match the public key inside the
|
||||
publisher X.509 certificate.
|
||||
.TP
|
||||
.I "-a md5 | sha1"
|
||||
The hash algorithm used in the digital signature of the PE executable. The
|
||||
default algorithm is MD5.
|
||||
.TP
|
||||
.I "-$ individual | commercial"
|
||||
Add information about the publisher, i.e. if the signature is generated by an
|
||||
individual or a commercial entity.
|
||||
.TP
|
||||
.I "-n description"
|
||||
Add a textual description of the signed file.
|
||||
.TP
|
||||
.I "-i url"
|
||||
Add a URL associated to the publisher or the signed file.
|
||||
.TP
|
||||
.I "-t url"
|
||||
URL to a timestamp service to countersign the PE executable. Countersignature
|
||||
is required if you want the PE executable signature to be valid after the
|
||||
publisher certificate expires. The countersignature proves that the publisher
|
||||
had a valid (non-expired) certificate when the PE executable was signed.
|
||||
.TP
|
||||
.I "-tr #"
|
||||
Number of retries to get a timestamp for the countersignature.
|
||||
.TP
|
||||
.I "-td #"
|
||||
Delay (in seconds) between the retries to get a timestamp for the countersignature.
|
||||
.TP
|
||||
.I "-k name"
|
||||
CryptoAPI key container name (when not using -v).
|
||||
.TP
|
||||
.I "-p name"
|
||||
CryptoAPI provider name (when not using -v).
|
||||
.TP
|
||||
.I "-y #"
|
||||
CryptoAPI provider type (when not using -v or -p).
|
||||
.TP
|
||||
.I "-ky signature | exchange | #"
|
||||
CryptoAPI key type (when not using -v).
|
||||
.TP
|
||||
.I "-r localMachine | currentUser"
|
||||
CryptoAPI key location (when not using -v).
|
||||
.TP
|
||||
.I "-help", "-h", "-?", "/?"
|
||||
Display help about this tool.
|
||||
.SH AUTHOR
|
||||
Written by Sebastien Pouliot
|
||||
.SH COPYRIGHT
|
||||
Copyright (C) 2003 Motus Technologies.
|
||||
Released under BSD license.
|
||||
.SH MAILING LISTS
|
||||
Visit http://mail.ximian.com/mailman/mono-list for details.
|
||||
.SH WEB SITE
|
||||
Visit: http://www.go-mono.com for details
|
||||
.SH SEE ALSO
|
||||
.BR chktrust(1), makecert(1), cert2spc(1)
|
||||
@@ -1,117 +0,0 @@
|
||||
.\"
|
||||
.\" sn manual page.
|
||||
.\" Copyright 2003 Motus Technologies
|
||||
.\" Author:
|
||||
.\" Sebastien Pouliot ([email protected])
|
||||
.\"
|
||||
.TH Mono "sn"
|
||||
.SH NAME
|
||||
sn \- Digitally sign/verify/compare strongname on CLR assemblies.
|
||||
.SH SYNOPSIS
|
||||
.PP
|
||||
.B sn [-q | -quiet] [options] [parameters]
|
||||
.SH DESCRIPTION
|
||||
Digitally sign, verify or compare, CLR assemblies using strongnames.
|
||||
.SH CONFIGURATION OPTIONS
|
||||
.TP
|
||||
.I "-c provider"
|
||||
Change the default CSP (Crypto Service Provider).
|
||||
.TP
|
||||
.I "-m [y|n]"
|
||||
Use a machine [y] key container or a user [n] key container.
|
||||
.TP
|
||||
.I "-Vl"
|
||||
List the verification options.
|
||||
.TP
|
||||
.I "-Vr assembly [userlist]"
|
||||
Exempt the specified assembly from verification for the specified user list.
|
||||
.TP
|
||||
.I "-Vu assembly"
|
||||
Remove the exemption entry for the specified assembly.
|
||||
.TP
|
||||
.I "-Vx"
|
||||
Remove all exemptions entries.
|
||||
.SH CSP RELATED OPTIONS
|
||||
.TP
|
||||
.I "-d container"
|
||||
Delete the keypair present in the specified key container.
|
||||
.TP
|
||||
.I "-i keypair.snk container"
|
||||
Import the specified strongname file into the specified container.
|
||||
.TP
|
||||
.I "-pc container publickey"
|
||||
Export the public key from the specified CSP container to the specified file.
|
||||
.SH CONVERTION OPTIONS
|
||||
.TP
|
||||
.I "-e assembly output.pub"
|
||||
Export the assembly public key to the specified output file.
|
||||
.TP
|
||||
.I "-p keypair.snk output.pub"
|
||||
Export the public key from the specified strongname key file (SNK) to the
|
||||
specified output file.
|
||||
.TP
|
||||
.I "-o input output.txt"
|
||||
Convert the input file to a CSV file (using decimal).
|
||||
.TP
|
||||
.I "-oh input output.txt"
|
||||
Convert the input file to a CSV file (using hexadecimal).
|
||||
.SH STRONGNAME SIGNING OPTIONS
|
||||
.TP
|
||||
.I "-D assembly1 assembly2"
|
||||
Compare if assembly1 and assembly are the same exception for their signature.
|
||||
This is done by comparing the hash of the metadata of both assembly.
|
||||
.TP
|
||||
.I "-k keypair.snk"
|
||||
Create a new strongname keypair in the specified file.
|
||||
.TP
|
||||
.I "-R assembly keypair.snk"
|
||||
Resign the specified assembly using the specified strongname keypair file
|
||||
(SNK).
|
||||
.TP
|
||||
.I "-Rc assembly container"
|
||||
Resign the specified assembly using the specified strongname container.
|
||||
.TP
|
||||
.I "-t file"
|
||||
Show the public key from the specified file.
|
||||
.TP
|
||||
.I "-tp file"
|
||||
Show the public key and the public key token from the specified file.
|
||||
.TP
|
||||
.I "-T assembly"
|
||||
Show the public key from the specified assembly.
|
||||
.TP
|
||||
.I "-Tp assembly"
|
||||
Show the public key and the public key token from the specified assembly.
|
||||
.TP
|
||||
.I "-V assembly"
|
||||
Verify the specified assembly signature.
|
||||
.TP
|
||||
.I "-Vf assembly"
|
||||
Verify the specified assembly signature (even if disabled).
|
||||
.SH HELP OPTIONS
|
||||
.TP
|
||||
.I "-h", "-?"
|
||||
Display basic help about this tool.
|
||||
.TP
|
||||
.I "-h config", "-? config"
|
||||
Display configuration related help about this tool.
|
||||
.TP
|
||||
.I "-h csp", "-? csp"
|
||||
Display Cryptographic Service Provider related help about this tool.
|
||||
.TP
|
||||
.I "-h convert", "-? convert"
|
||||
Display convertion related help about this tool.
|
||||
.TP
|
||||
.I "-h sn", "-? sn"
|
||||
Display strongname related help about this tool.
|
||||
.SH AUTHOR
|
||||
Written by Sebastien Pouliot
|
||||
.SH COPYRIGHT
|
||||
Copyright (C) 2003 Motus Technologies.
|
||||
Released under BSD license.
|
||||
.SH MAILING LISTS
|
||||
Visit http://mail.ximian.com/mailman/mono-list for details.
|
||||
.SH WEB SITE
|
||||
Visit: http://www.go-mono.com for details
|
||||
.SH SEE ALSO
|
||||
.BR secutil(1)
|
||||
-126
@@ -1,126 +0,0 @@
|
||||
.\"
|
||||
.\" soapsuds manual page.
|
||||
.\" (C) 2003 Novell, Inc.
|
||||
.\" Author:
|
||||
.\" Lluis Sanchez Gual ([email protected])
|
||||
.\"
|
||||
.TH soapsuds 1
|
||||
.SH NAME
|
||||
soapsuds \- Mono's Remoting Proxy Generator
|
||||
.SH SYNOPSIS
|
||||
.PP
|
||||
.B soapsuds
|
||||
[options] [inputs] [outputs]
|
||||
.SH DESCRIPTION
|
||||
.I soapsuds
|
||||
is a tool for generating WSDL documents and client proxies for remoting services.
|
||||
A WSDL document describes the methods that a service provides together with XML schemas
|
||||
of all referenced data structures. A client proxy is a class which offers the same methods
|
||||
as the service it represents, but provides no implementation, it just forwards calls to the
|
||||
remote service.
|
||||
.PP
|
||||
Generated client proxies are not strictly necessary, since the runtime can
|
||||
automatically generate proxies from the original service types. However, it implies the need
|
||||
of distributing the service class to all clients. In some scenarios a better approach is
|
||||
to use soapsuds to generate a proxy class which has the same interface as the service,
|
||||
but without any implementation.
|
||||
.PP
|
||||
.I soapsuds
|
||||
can generate a WSDL document from a set of types specified with the option
|
||||
.I -types
|
||||
or can extract the types from an assembly specified with
|
||||
.I -inputassemblyfile.
|
||||
In this last case, soapsuds will include schemas for all serializable classes in
|
||||
the WSDL document.
|
||||
.PP
|
||||
Taking as input a WSDL document (or anything from which such document can be generated)
|
||||
the tool can generate source code for the client proxy (using the
|
||||
.I -gc
|
||||
option) or it can directly generate an assembly that implements the proxy (with the
|
||||
.I -outputassemblyfile
|
||||
option). soapsuds will also generate fake serializable classes for all types defined
|
||||
in the schema. However, beware that those classes will lack the semantics of the
|
||||
original classes, since only data structure is generated.
|
||||
.PP
|
||||
.SH INPUT SOURCES
|
||||
The following sources are available (only one can be specified):
|
||||
.TP
|
||||
.I "-urltoschema:url" "-url:url"
|
||||
Url from which to retrieve the WSDL document.
|
||||
.TP
|
||||
.I "-types:type1,assembly[,serviceEndPoint][;type2,assembly[,serviceEndPoint]]..."
|
||||
Specifies types for which to generate a schema or proxy. If no service endpoint is
|
||||
provided, the one provided with the
|
||||
.I -serviceendpoint
|
||||
option is used.
|
||||
.TP
|
||||
.I "-inputassemblyfile:file", "-ia:file"
|
||||
Assembly that contains the types to export.
|
||||
.TP
|
||||
.I "-inputschemafile:schena", "-is:schema"
|
||||
Schema from which to generate proxy classes.
|
||||
.SH INPUT OPTIONS
|
||||
The following options are available:
|
||||
.TP
|
||||
.I "-inputdirectory:directory", "-id:directory"
|
||||
Directory where DLLs are located.
|
||||
.TP
|
||||
.I "-serviceendpoint:url", "-se:url"
|
||||
Url of the service to be placed in the WSDL document.
|
||||
.SH OUTPUTS
|
||||
The following output options are available (more than one can be specified):
|
||||
.TP
|
||||
.I "-outputassemblyfile:file", "-oa:file"
|
||||
Generates the proxy code and compiles it into an assembly with the provided name.
|
||||
.TP
|
||||
.I "-outputschemafile:file", "-os:file"
|
||||
Generates a WSDL document that represents the provided types.
|
||||
.TP
|
||||
.I "-generatecode", "-gc"
|
||||
Generates proxy source code for the provided WSDL document or types.
|
||||
.SH OUTPUT OPTIONS
|
||||
The following options are available:
|
||||
.TP
|
||||
.I "-outputdirectory:directory", "-od:directory"
|
||||
Directory where generated files will be placed.
|
||||
.TP
|
||||
.I "-proxynamespace:namespace", "-pn:namespace"
|
||||
Namespace of the generated proxy.
|
||||
.TP
|
||||
.I "-nowrappedproxy", "-nowp"
|
||||
Do not generate a wrapped proxy.
|
||||
.TP
|
||||
.I "-wrappedproxy", "-wp"
|
||||
Generate a wrapped proxy.
|
||||
.TP
|
||||
.I "-strongnamefile:file", "-sn:file"
|
||||
Strong name file.
|
||||
.SH GENERAL OPTIONS
|
||||
The following options are available:
|
||||
.TP
|
||||
.I "-nologo"
|
||||
Supress the startup logo.
|
||||
.TP
|
||||
.I "-u:username", "-user:username"
|
||||
The user name to use when connecting to the server.
|
||||
.TP
|
||||
.I "-p:password", "-password:password"
|
||||
The password to use when connecting to the server.
|
||||
.TP
|
||||
.I "-d:domain", "-domain:domain"
|
||||
The domain to use when connecting to the server.
|
||||
.TP
|
||||
.I "-httpproxyname:name", "-hpn:name"
|
||||
Name of the http proxy.
|
||||
.TP
|
||||
.I "-httpproxyport:port", "-hpp:port"
|
||||
Port of the http proxy.
|
||||
.PP
|
||||
.SH AUTHORS
|
||||
Lluis Sanchez Gual ([email protected])
|
||||
.PP
|
||||
.SH LICENSE
|
||||
wsdl is released under the terms of the GNU GPL.
|
||||
.PP
|
||||
.SH SEE ALSO
|
||||
wsdl(1), disco(1), mono(1), mcs(1)
|
||||
Loaded 100 of 4525 files, more files were not shown because too many files have changed in this diff.
Show more
Reference in new issue
Block a user