mirror of
https://github.com/BepInEx/mono.git
synced 2026-11-17 19:10:23 -10:00
Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
23631f018a |
No files matched your search
@@ -1,330 +1,3 @@
|
||||
2003-11-26 Zoltan Varga <[email protected]>
|
||||
|
||||
* configure.in: Add -fno-strict-aliasing to CFLAGS.
|
||||
|
||||
* configure.in: Applied patch from [email protected]. Avoid linking in
|
||||
librt if not neccesary.
|
||||
|
||||
2003-11-24 Zoltan Varga <[email protected]>
|
||||
|
||||
* configure.in: Fix signbit check. Fixes #51315.
|
||||
|
||||
2003-11-20 Jackson Harper <[email protected]>
|
||||
|
||||
* data/machine.config: Add OutputCacheModule
|
||||
|
||||
2003-11-19 Jackson Harper <[email protected]>
|
||||
|
||||
* doc/web/team.xml: New email address and job description
|
||||
* doc/web/team/jackson.png: Picture of me debugging...seems appropriate
|
||||
|
||||
2003-11-14 Jackson Harper <[email protected]>
|
||||
|
||||
* Makefile.am: delete mscorlib.dll
|
||||
|
||||
2003-11-12 Jackson Harper <[email protected]>
|
||||
|
||||
* Makefile.am: corlib is now named mscorlib.dll
|
||||
|
||||
2003-11-12 Zoltan Varga <[email protected]>
|
||||
|
||||
* configure.in acconfig.h: Add check for signbit, which is missing in
|
||||
FreeBSD 4.x.
|
||||
|
||||
2003-11-07 Zoltan Varga <[email protected]>
|
||||
|
||||
* configure.in: Remove debugging junk accidently checked in.
|
||||
|
||||
* configure.in: Add new --with-nptl option to enable NPTL only
|
||||
features since auto-detection is not reliable.
|
||||
|
||||
* autogen.sh: Fix previous patch and silence noisy GNU which.
|
||||
|
||||
2003-11-07 Bernie Solomon <[email protected]>
|
||||
|
||||
* autogen.sh: tweak glibtool check so it works
|
||||
if which doesn't set return code properly
|
||||
|
||||
2003-11-07 Zoltan Varga <[email protected]>
|
||||
|
||||
* autogen.sh: Silence noisy GNU which.
|
||||
|
||||
* autogen.sh: Applied patch from Peter Teichman ([email protected]).
|
||||
Use 'glibtool' instead of 'libtool' on OSX.
|
||||
|
||||
2003-11-06 Zoltan Varga <zovarga@ws-zovarga2>
|
||||
|
||||
* mono/benchmark/pinvoke.cs: New benchmark for testing the performance
|
||||
of the managed/unmanaged boundary.
|
||||
|
||||
2003-11-06 Zoltan Varga <[email protected]>
|
||||
|
||||
* configure.in acconfig.h: Add check for __thread keyword in gcc.
|
||||
|
||||
2003-10-29 Dick Porter <[email protected]>
|
||||
|
||||
* man/mono.1: Document MONO_EXTERNAL_ENCODINGS variable
|
||||
|
||||
2003-10-16 Miguel de Icaza <[email protected]>
|
||||
|
||||
* man/mono.1: Document new --trace options
|
||||
|
||||
2003-10-13 Bernie Solomon <[email protected]>
|
||||
|
||||
* configure.in: add hppa support (64bit only)
|
||||
make solaris build work with Forte compiler
|
||||
|
||||
2003-10-13 Zoltan Varga <[email protected]>
|
||||
|
||||
* configure.in: Added check for pthread_attr_setstacksize.
|
||||
|
||||
* mono/tests/ChangeLog: New file.
|
||||
|
||||
2003-10-13 Zoltan Varga <[email protected]>
|
||||
|
||||
* mono/tests/Makefile.am: Link the tests with the test driver program
|
||||
used for the mini tests.
|
||||
|
||||
2003-10-10 Zoltan Varga <[email protected]>
|
||||
|
||||
* mono/tests/libtest.c (mono_test_marshal_delegate): Added test for
|
||||
stdcall calling convention.
|
||||
|
||||
2003-10-09 Dick Porter <[email protected]>
|
||||
|
||||
* acconfig.h:
|
||||
* configure.in: Check for ICU availability
|
||||
|
||||
2003-10-09 Bernie Solomon <[email protected]>
|
||||
|
||||
* mono/tests/libtest.c: fix after merge of pinvoke2.cs
|
||||
|
||||
2003-10-07 Bernie Solomon <[email protected]>
|
||||
|
||||
* mono/tests/Makefile.am mono/tests/libtest.c
|
||||
mono/tests/pinvoke18.cs: new test for bool marshalling.
|
||||
|
||||
2003-10-07 Bernie Solomon <[email protected]>
|
||||
|
||||
* mono/scripts/Makefile.am mono/scripts/*.in: fix
|
||||
managed .exe paths so they are found under cygwin.
|
||||
|
||||
2003-10-07 Zoltan Varga <[email protected]>
|
||||
|
||||
* mono/tests/pinvoke2.cs mono/tests/libtest.c: Fix array of structs
|
||||
test.
|
||||
|
||||
2003-10-06 Bernie Solomon <[email protected]>
|
||||
|
||||
* mono/tests/pinvoke2.cs mono/tests/pinvoke11.cs
|
||||
mono/tests/libtest.c: Add more pass by value struct
|
||||
tests for platforms with more complex calling conventions
|
||||
(Sparc V9, HPPA 64 bit).
|
||||
|
||||
2003-10-06 Zoltan Varga <[email protected]>
|
||||
|
||||
* mono/tests/pinvoke2.cs mono/tests/libtest.c: Add array of structs
|
||||
marshalling test.
|
||||
|
||||
2003-10-04 Bernie Solomon <[email protected]>
|
||||
|
||||
* mono/tests/libtest.c: remove warnings except
|
||||
"no previous prototype"
|
||||
|
||||
2003-10-03 Bernie Solomon <[email protected]>
|
||||
|
||||
* mono/tests/libtest.c: (test_lpwstr_marshal) remove undefined
|
||||
behaviour of increment, (mono_test_marshal_char) = should be ==
|
||||
|
||||
2003-09-30 Zoltan Varga <[email protected]>
|
||||
|
||||
* mono/tests/remoting1.cs: Added test for interface casts on
|
||||
TransparentProxies.
|
||||
|
||||
2003-09-24 Bernie Solomon <[email protected]>
|
||||
|
||||
* mono/tests/pinvoke*.cs, delegate4.cs, marshal10.cs, marshal4.cs
|
||||
marshal5.cs: remove .so from DllImport of libtest to aid portability.
|
||||
|
||||
2003-09-08 Zoltan Varga <[email protected]>
|
||||
|
||||
* configure.in: Added check for valgrind headers.
|
||||
|
||||
2003-09-03 Zoltan Varga <[email protected]>
|
||||
|
||||
* Makefile.am: Use $(MAKE) in even more places. Patch by Bernie Solomon
|
||||
([email protected]).
|
||||
|
||||
2003-08-27 Zoltan Varga <[email protected]>
|
||||
|
||||
* Makefile.am: Use $(MAKE) instead of make. Patch by Bernie Solomon
|
||||
([email protected]).
|
||||
|
||||
2003-08-25 Zoltan Varga <[email protected]>
|
||||
|
||||
* mono.pc.in: Added gthread-2.0.
|
||||
|
||||
2003-08-22 Zoltan Varga <[email protected]>
|
||||
|
||||
* configure.in: Added gthread-2.0 to GLIB_CFLAGS and GLIB_LIBS, so we
|
||||
can call g_thread_init ().
|
||||
|
||||
2003-08-21 Zoltan Varga <[email protected]>
|
||||
|
||||
* mono/tests/threadpool.cs mono/tests/threadpool1.cs: Make increments
|
||||
of static variables atomic. Fixes bug #47683.
|
||||
|
||||
2003-08-21 Johannes Roith <[email protected]>
|
||||
|
||||
* mono/Makefile.am: small update. make sure, glib makes it in the build, add optional target for dependencies
|
||||
|
||||
2003-08-18 Johannes Roith <[email protected]>
|
||||
|
||||
* mono/Makefile.am: add windows build option
|
||||
* mono/monowiz.win32.nsi: add windows build script
|
||||
* mono/mono-win32-light.bmp: add bitmap
|
||||
|
||||
2003-08-16 Zoltan Varga <[email protected]>
|
||||
|
||||
* mono/tests/checked.cs: Added mul.ovf tests.
|
||||
|
||||
2003-08-15 Duncan Mak <[email protected]>
|
||||
|
||||
* doc/mysql: Change references to ByteFX.Data.MySQLClient to the
|
||||
correct ByteFX.Data.MySqlClient (note the change in
|
||||
capitalization). Thanks to Tom Wagner <[email protected]> for
|
||||
spotting the error.
|
||||
|
||||
2003-08-15 Zoltan Varga <[email protected]>
|
||||
|
||||
* mono/tests/bug-47295.cs: Regression test for bug #47295.
|
||||
|
||||
2003-08-11 Duncan Mak <[email protected]>
|
||||
|
||||
* runtime/Makefile.am (assemblies_DATA): Add Mono.Cairo.dll.
|
||||
|
||||
Sun Aug 3 21:12:13 BST 2003 Malte Hildingson <[email protected]>
|
||||
|
||||
* configure.in: added FPU test for ARM.
|
||||
|
||||
Thu Jul 31 16:19:07 CEST 2003 Paolo Molaro <[email protected]>
|
||||
|
||||
* configure.in, etc.: portability fixes and support for
|
||||
buidling outside the srcdir from Laurent Morichetti <[email protected]>.
|
||||
|
||||
2003-07-22 Duncan Mak <[email protected]>
|
||||
|
||||
* runtime/Makefile.am: Remove sqlsharp as we no longer distribute it.
|
||||
|
||||
2003-07-22 Zoltan Varga <[email protected]>
|
||||
|
||||
* mono/tests/Makefile.am: Add missing test. Make tests interruptable
|
||||
by Ctrl-C. Add testinterp target to run the tests with the interpreter.
|
||||
Do not try to build vararg.cs under mcs.
|
||||
|
||||
* configure.in: Fix detection of GC_gcj_malloc.
|
||||
|
||||
2003-07-14 Jerome Laban <[email protected]>
|
||||
|
||||
* acconfig.h:
|
||||
* configure.in: Check for gethostbyname2_r availability.
|
||||
* data/machine.config: Added section system.net/settings. Added
|
||||
option for IPv6 availability.
|
||||
|
||||
2003-07-13 Zoltan Varga <[email protected]>
|
||||
|
||||
* mono/tests/cattr-object.cs: Make it run under both mono and MS.NET.
|
||||
|
||||
* mono/tests/struct.cs: Add test for unboxing trampolines.
|
||||
|
||||
* mono/tests/bug-27420.cs: new regression test.
|
||||
|
||||
* mono/tests/Makefile.am: skip vararg test since it does not compile
|
||||
under mono. Add testinterp target. Add new tests.
|
||||
|
||||
2003-07-10 Martin Willemoes Hansen
|
||||
|
||||
* doc/web/team.xml : Modified my tasks a bit.
|
||||
|
||||
2003-07-01 Paolo Molaro <[email protected]>
|
||||
|
||||
* acconfig.h, configure.in: added bundle support.
|
||||
|
||||
2003-06-10 Dick Porter <[email protected]>
|
||||
|
||||
* acconfig.h:
|
||||
* configure.in: Check for struct ip_mreq if struct ip_mreqn isn't
|
||||
available.
|
||||
|
||||
2003-06-10 Zoltan Varga <[email protected]>
|
||||
|
||||
* configure.in: Define HAVE_GC_GCJ_MALLOC for included libgc.
|
||||
|
||||
2003-06-10 Martin Baulig <[email protected]>
|
||||
|
||||
* configure.in: Fall back to boehm if we don't have a libgc
|
||||
subdirectory.
|
||||
|
||||
2003-06-10 Martin Baulig <[email protected]>
|
||||
|
||||
* configure.in: Make the libgc stuff actually work; we now create
|
||||
a shared libmonogc.so when using the included libgc.
|
||||
|
||||
2003-06-09 Martin Baulig <[email protected]>
|
||||
|
||||
* configure.in: Only check for gc if --with-gc=boehm.
|
||||
|
||||
2003-06-08 Martin Baulig <[email protected]>
|
||||
|
||||
* configure.in: Tell libgc's configure about our threads library.
|
||||
|
||||
2003-06-08 Martin Baulig <[email protected]>
|
||||
|
||||
* libgc/: Integrate the libgc module here.
|
||||
|
||||
[Note: A simple `cvs update' won't work this time; you either need
|
||||
to re-checkout the `mono' module or manually move the `libgc'
|
||||
module here.]
|
||||
|
||||
* configure.in (--with-gc): Added `included' option to use the
|
||||
included libgc. This is now also the default.
|
||||
(LIBGC_CFLAGS, LIBGC_LIBS): Put the libgc stuff here and AC_SUBST it.
|
||||
(INCLUDED_LIBGC): New automake conditional.
|
||||
(USE_INCLUDED_LIBGC): #define this if appropriate.
|
||||
|
||||
* autogen.sh: Run libgc/autogen.sh.
|
||||
|
||||
* Makefile.am (SUBDIRS): Added libgc.
|
||||
|
||||
2003-06-05 Duncan Mak <[email protected]>
|
||||
|
||||
* mono.spec.in (Requires): Add libxml2 and libxslt dependency on
|
||||
the package.
|
||||
|
||||
2003-05-19 Dick Porter <[email protected]>
|
||||
|
||||
* configure.in: Netbsd build fix by [email protected].
|
||||
|
||||
2003-05-10 Martin Willemoes Hansen <[email protected]>
|
||||
|
||||
* scripts/Makefile.am: Added monoresgen secutil sqlsharp
|
||||
shell wrapper scripts.
|
||||
|
||||
2003-05-08 Zoltan Varga <[email protected]>
|
||||
|
||||
* mono/tests/Makefile.am:
|
||||
- Compile with mcs.
|
||||
- Disable some warnings.
|
||||
- Added executables to clean target.
|
||||
- Make testjit the default target.
|
||||
- Print list of failed tests at the end of a test run.
|
||||
- Abort tests when Ctrl-C is pressed.
|
||||
|
||||
* mono/tests/test-driver: Return with a special exit code when
|
||||
SIGINT is detected.
|
||||
|
||||
* mono/tests/checked.cs: Make it compile.
|
||||
|
||||
2003-05-02 Miguel de Icaza <[email protected]>
|
||||
|
||||
* runtime/Makefile.am ($(monobins_DATA)): Use explicit file names
|
||||
|
||||
+1
-54
@@ -1,62 +1,9 @@
|
||||
AUTOMAKE_OPTIONS = foreign
|
||||
|
||||
SUBDIRS = @libgc_dir@ mono doc docs runtime scripts man data samples
|
||||
|
||||
dnl EXTRA_SUBDIRS = libgc
|
||||
SUBDIRS = mono doc docs runtime scripts man data
|
||||
|
||||
EXTRA_DIST= mono.pc.in mono.spec.in
|
||||
|
||||
pkgconfigdir = $(libdir)/pkgconfig
|
||||
pkgconfig_DATA= mono.pc
|
||||
DISTCLEANFILES= mono.pc
|
||||
|
||||
#
|
||||
# The following target is used to compile and install
|
||||
# mono and mcs without running into the out-of-sync
|
||||
# problems by doing the compilation in the right order.
|
||||
#
|
||||
|
||||
fullbuild: remove-binaries mcs-tree-safe-build xinstall-runtime mcs-rest install
|
||||
|
||||
mcs-tree-safe-build:
|
||||
(cd ../mcs/jay; $(MAKE))
|
||||
(cd ../mcs/mcs; $(MAKE) MCS=mcs)
|
||||
(cd ../mcs/class/corlib; $(MAKE) MCS=mcs)
|
||||
cp ../mcs/class/lib/mscorlib.dll runtime
|
||||
cp ../mcs/mcs/mcs.exe runtime
|
||||
|
||||
xinstall-runtime:
|
||||
if echo $(SUBDIRS) | grep "libgc " > /dev/null; then (cd libgc; $(MAKE) && $(MAKE) install); fi
|
||||
(cd mono; $(MAKE) && $(MAKE) install)
|
||||
|
||||
mcs-rest:
|
||||
(cd ../mcs/class; $(MAKE))
|
||||
|
||||
remove-binaries:
|
||||
rm ../mcs/class/lib/mscorlib.dll ../mcs/mcs/mcs.exe runtime/*dll runtime/*.exe >& /dev/null; echo
|
||||
|
||||
|
||||
win32getdeps:
|
||||
wget http://www.go-mono.com/archive/pkgconfig-0.11-20020310.zip
|
||||
wget http://www.go-mono.com/archive/glib-2.0.4-20020703.zip
|
||||
wget http://www.go-mono.com/archive/glib-dev-2.0.4-20020703.zip
|
||||
wget http://www.go-mono.com/archive/libiconv-1.7.zip
|
||||
wget http://www.go-mono.com/archive/libiconv-dev-1.7.zip
|
||||
wget http://www.go-mono.com/archive/libintl-0.10.40-20020101.zip
|
||||
wget http://www.jroith.de/nsis4cygwin.zip
|
||||
unzip -n -d / pkgconfig-0.11-20020310.zip
|
||||
unzip -n -d / glib-2.0.4-20020703.zip
|
||||
unzip -n -d / glib-dev-2.0.4-20020703.zip
|
||||
unzip -n -d / libiconv-1.7.zip
|
||||
unzip -n -d / libiconv-dev-1.7.zip
|
||||
unzip -n -d / libintl-0.10.40-20020101.zip
|
||||
unzip -n -d / nsis4cygwin.zip
|
||||
|
||||
win32setup:
|
||||
cp /usr/lib/libglib-2.0-0.dll @prefix@/lib
|
||||
cp /usr/lib/iconv.dll @prefix@/lib
|
||||
cp /usr/lib/libgmodule-2.0-0.dll @prefix@/lib
|
||||
cp /usr/lib/libgobject-2.0-0.dll @prefix@/lib
|
||||
cp /usr/lib/libgthread-2.0-0.dll @prefix@/lib
|
||||
cp /usr/lib/libintl-1.dll @prefix@/lib
|
||||
makensis /DMILESTONE=@VERSION@ /DSOURCE_INSTALL_DIR=`cygpath -a -w @prefix@`\\* monowiz.win32.nsi
|
||||
@@ -1,28 +1,14 @@
|
||||
|
||||
This is Mono.
|
||||
|
||||
1. Installation
|
||||
2. Using Mono
|
||||
3. Directory Roadmap
|
||||
Installation:
|
||||
|
||||
1. Compilation and Installation
|
||||
===============================
|
||||
Read doc/download for installation instructions,
|
||||
or read the HTML version:
|
||||
|
||||
If you obtained this package as an officially released tarball,
|
||||
this is very simple, use configure and make:
|
||||
http://www.go-mono.com/download.html
|
||||
|
||||
./configure --prefix=/usr/local
|
||||
make
|
||||
make install
|
||||
|
||||
If you obtained this as a snapshot, you will need an existing
|
||||
Mono installation. To upgrade your installation do:
|
||||
|
||||
./autogen --prefix=/usr/local
|
||||
make fullbuild
|
||||
|
||||
2. Using Mono
|
||||
=============
|
||||
* Using Mono
|
||||
|
||||
Once you have installed the software, you can run a few programs:
|
||||
|
||||
@@ -43,8 +29,7 @@ This is Mono.
|
||||
See the man pages for mono(1), mint(1), monodis(1) and mcs(2)
|
||||
for further details.
|
||||
|
||||
3. Directory Roadmap
|
||||
====================
|
||||
* A directory roadmap:
|
||||
|
||||
doc/
|
||||
Contains documentation and the web site contents.
|
||||
|
||||
-11
@@ -3,10 +3,8 @@
|
||||
#undef HAVE_MSG_NOSIGNAL
|
||||
#undef HAVE_SOL_IP
|
||||
#undef HAVE_SOL_TCP
|
||||
#undef HAVE_SOL_IPV6
|
||||
#undef HAVE_IP_PKTINFO
|
||||
#undef HAVE_STRUCT_IP_MREQN
|
||||
#undef HAVE_STRUCT_IP_MREQ
|
||||
#undef HAVE_PTHREAD_MUTEX_TIMEDLOCK
|
||||
#undef USE_MONO_MUTEX
|
||||
#undef HAVE_LARGE_FILE_SUPPORT
|
||||
@@ -15,18 +13,9 @@
|
||||
#undef NAME_DEV_RANDOM
|
||||
#undef HAVE_CRYPT_RNG
|
||||
#undef HAVE_BOEHM_GC
|
||||
#undef USE_INCLUDED_LIBGC
|
||||
#undef DISABLE_SHARED_HANDLES
|
||||
#undef HAVE_TIMEZONE
|
||||
#undef HAVE_TM_GMTOFF
|
||||
#undef MONO_SIZEOF_SUNPATH
|
||||
#undef MONO_ZERO_ARRAY_LENGTH
|
||||
#undef NEED_LINK_UNLINK
|
||||
#undef PTHREAD_POINTER_ID
|
||||
#undef HAVE_GC_H
|
||||
#undef HAVE_GC_GCJ_MALLOC
|
||||
#undef WITH_BUNDLE
|
||||
#undef HAVE_GETHOSTBYNAME2_R
|
||||
#undef HAVE_ICU
|
||||
#undef HAVE_KW_THREAD
|
||||
#undef HAVE_SIGNBIT
|
||||
+2
-15
@@ -30,15 +30,8 @@ fi
|
||||
DIE=1
|
||||
}
|
||||
|
||||
if [ -z "$LIBTOOL" ]; then
|
||||
LIBTOOL=`which glibtool 2>/dev/null`
|
||||
if [ ! -x "$LIBTOOL" ]; then
|
||||
LIBTOOL=`which libtool`
|
||||
fi
|
||||
fi
|
||||
|
||||
(grep "^AM_PROG_LIBTOOL" $srcdir/configure.in >/dev/null) && {
|
||||
($LIBTOOL --version) < /dev/null > /dev/null 2>&1 || {
|
||||
(libtool --version) < /dev/null > /dev/null 2>&1 || {
|
||||
echo
|
||||
echo "**Error**: You must have \`libtool' installed to compile Mono."
|
||||
echo "Get ftp://ftp.gnu.org/pub/gnu/libtool-1.2d.tar.gz"
|
||||
@@ -98,7 +91,7 @@ esac
|
||||
if grep "^AM_PROG_LIBTOOL" configure.in >/dev/null; then
|
||||
if test -z "$NO_LIBTOOLIZE" ; then
|
||||
echo "Running libtoolize..."
|
||||
${LIBTOOL}ize --force --copy
|
||||
libtoolize --force --copy
|
||||
fi
|
||||
fi
|
||||
|
||||
@@ -124,12 +117,6 @@ automake --add-missing --gnu $am_opt ||
|
||||
echo "Running autoconf ..."
|
||||
autoconf || { echo "**Error**: autoconf failed."; exit 1; }
|
||||
|
||||
if test -d $srcdir/libgc; then
|
||||
echo Running libgc/autogen.sh ...
|
||||
(cd $srcdir/libgc ; NOCONFIGURE=1 ./autogen.sh "$@")
|
||||
echo Done running libgc/autogen.sh ...
|
||||
fi
|
||||
|
||||
|
||||
conf_flags="--enable-maintainer-mode --enable-compile-warnings" #--enable-iso-c
|
||||
|
||||
|
||||
-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
|
||||
|
||||
+43
-378
@@ -1,23 +1,9 @@
|
||||
AC_INIT(README)
|
||||
AC_CANONICAL_SYSTEM
|
||||
AM_CONFIG_HEADER(config.h)
|
||||
AM_INIT_AUTOMAKE(mono,0.29)
|
||||
AM_INIT_AUTOMAKE(mono,0.24)
|
||||
AM_MAINTAINER_MODE
|
||||
|
||||
dnl
|
||||
dnl libgc checks
|
||||
dnl
|
||||
|
||||
gc_headers=no
|
||||
gc=included
|
||||
use_included_gc=no
|
||||
|
||||
if test -d $srcdir/libgc ; then
|
||||
gc_default=included
|
||||
else
|
||||
gc_default=boehm
|
||||
fi
|
||||
|
||||
#
|
||||
# These are the flags that need to be stored in the mono.pc file for
|
||||
# compiling code that will embed Mono
|
||||
@@ -29,31 +15,16 @@ AC_SUBST(libmono_ldflags)
|
||||
|
||||
# Thread configuration inspired by sleepycat's db
|
||||
AC_MSG_CHECKING([host platform characteristics])
|
||||
libgc_threads=no
|
||||
case "$host" in
|
||||
*-*-mingw*|*-*-cygwin*)
|
||||
platform_win32=yes
|
||||
AC_DEFINE(PLATFORM_WIN32)
|
||||
CC="gcc -mno-cygwin"
|
||||
HOST_CC="gcc"
|
||||
# latest libgc already defines GC_WIN32_THREADS
|
||||
# CPPFLAGS="$CPPFLAGS -DGC_WIN32_THREADS -DWIN32_THREADS"
|
||||
CPPFLAGS="$CPPFLAGS -DWIN32_THREADS"
|
||||
CPPFLAGS="$CPPFLAGS -DGC_WIN32_THREADS -DWIN32_THREADS"
|
||||
libdl=
|
||||
libgc_threads=win32
|
||||
gc_default=boehm
|
||||
;;
|
||||
*-*-*netbsd*)
|
||||
platform_win32=no
|
||||
CPPFLAGS="$CPPFLAGS -D_REENTRANT"
|
||||
libmono_cflags="-D_REENTRANT"
|
||||
LDFLAGS="$LDFLAGS -pthread"
|
||||
libmono_ldflags="-pthread"
|
||||
AC_DEFINE(NEED_LINK_UNLINK)
|
||||
libdl=
|
||||
libgc_threads=pthreads
|
||||
;;
|
||||
*-*-*freebsd*|*-*-*openbsd*)
|
||||
*-*-*bsd*)
|
||||
platform_win32=no
|
||||
CPPFLAGS="$CPPFLAGS -D_THREAD_SAFE"
|
||||
libmono_cflags="-D_THREAD_SAFE"
|
||||
@@ -62,7 +33,6 @@ case "$host" in
|
||||
AC_DEFINE(NEED_LINK_UNLINK)
|
||||
AC_DEFINE(PTHREAD_POINTER_ID)
|
||||
libdl=
|
||||
libgc_threads=pthreads
|
||||
;;
|
||||
*-*-linux*)
|
||||
platform_win32=no
|
||||
@@ -70,24 +40,12 @@ case "$host" in
|
||||
libmono_cflags="-DMONO_USE_EXC_TABLES -fexceptions -D_REENTRANT"
|
||||
libmono_ldflags="-lpthread"
|
||||
libdl="-ldl"
|
||||
libgc_threads=pthreads
|
||||
;;
|
||||
*-*-hpux*)
|
||||
platform_win32=no
|
||||
CPPFLAGS="$CPPFLAGS -DGC_HPUX_THREADS -D_HPUX_SOURCE -D_XOPEN_SOURCE_EXTENDED -D_REENTRANT"
|
||||
CFLAGS="$CFLAGS +ESdbgasm"
|
||||
LDFLAGS="$LDFLAGS -z"
|
||||
libmono_cflags="-D_REENTRANT"
|
||||
libmono_ldflags="-lpthread"
|
||||
libgc_threads=pthreads
|
||||
AC_DEFINE(NEED_LINK_UNLINK)
|
||||
;;
|
||||
*-*-solaris*)
|
||||
platform_win32=no
|
||||
CPPFLAGS="$CPPFLAGS -DGC_SOLARIS_THREADS -DGC_SOLARIS_PTHREADS -D_REENTRANT"
|
||||
AC_DEFINE(NEED_LINK_UNLINK)
|
||||
libmono_cflags="-D_REENTRANT"
|
||||
libgc_threads=pthreads
|
||||
;;
|
||||
*-*-darwin*)
|
||||
platform_win32=no
|
||||
@@ -98,8 +56,6 @@ case "$host" in
|
||||
AC_DEFINE(NEED_LINK_UNLINK)
|
||||
AC_DEFINE(PTHREAD_POINTER_ID)
|
||||
libdl=
|
||||
libgc_threads=no
|
||||
gc_default=none
|
||||
;;
|
||||
*)
|
||||
AC_MSG_WARN([*** Please add $host to configure.in checks!])
|
||||
@@ -114,12 +70,6 @@ AC_CHECK_TOOL(CC, gcc, gcc)
|
||||
AC_PROG_CC
|
||||
AM_PROG_CC_STDC
|
||||
AC_PROG_INSTALL
|
||||
dnl We should use AM_PROG_AS, but it's not available on automake/aclocal 1.4
|
||||
: ${CCAS='$(CC)'}
|
||||
# Set ASFLAGS if not already set.
|
||||
: ${CCASFLAGS='$(CFLAGS)'}
|
||||
AC_SUBST(CCAS)
|
||||
AC_SUBST(CCASFLAGS)
|
||||
|
||||
AC_CHECK_PROG(BISON, bison,yes,no)
|
||||
if test "x$BISON" = "xno";
|
||||
@@ -147,9 +97,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)
|
||||
|
||||
@@ -159,21 +106,7 @@ AC_CHECK_HEADERS(wchar.h)
|
||||
# not 64 bit clean in cross-compile
|
||||
AC_CHECK_SIZEOF(void *, 4)
|
||||
|
||||
WARN=''
|
||||
if test x"$GCC" = xyes; then
|
||||
WARN='-Wall -Wunused -Wmissing-prototypes -Wmissing-declarations -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-cast-qual -Wcast-align -Wwrite-strings'
|
||||
# The runtime code does not respect ANSI C strict aliasing rules
|
||||
CFLAGS="$CFLAGS -fno-strict-aliasing"
|
||||
else
|
||||
# The Sun Forte compiler complains about inline functions that access static variables
|
||||
# so disable all inlining.
|
||||
case "$host" in
|
||||
*-*-solaris*)
|
||||
CFLAGS="$CFLAGS -Dinline="
|
||||
;;
|
||||
esac
|
||||
fi
|
||||
CFLAGS="$CFLAGS -g $WARN"
|
||||
CFLAGS='-g -Wall -Wunused -Wmissing-prototypes -Wmissing-declarations -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-cast-qual -Wcast-align -Wwrite-strings'
|
||||
|
||||
AC_PATH_PROG(PKG_CONFIG, pkg-config, no)
|
||||
if test "x$PKG_CONFIG" = "xno"; then
|
||||
@@ -182,8 +115,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)
|
||||
|
||||
@@ -205,8 +138,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`
|
||||
|
||||
@@ -215,31 +148,16 @@ AC_SUBST(GLIB_LIBS)
|
||||
AC_SUBST(GMODULE_CFLAGS)
|
||||
AC_SUBST(GMODULE_LIBS)
|
||||
|
||||
AC_ARG_WITH(gc, [ --with-gc=boehm,included,none],[gc=$with_gc],[gc=$gc_default])
|
||||
gc_headers=no
|
||||
AC_CHECK_HEADERS(gc.h gc/gc.h, gc_headers=yes)
|
||||
AC_CHECK_LIB(gc, GC_malloc, found_boehm="yes",,$libdl)
|
||||
gc=auto
|
||||
AC_ARG_WITH(gc, [ --with-gc=boehm,none],[gc=$with_gc])
|
||||
|
||||
# Enable support for NPTL only features like fast thread-local storage
|
||||
# We can't reliably detect nptl at compile & run time
|
||||
# so this option will stay until nptl becomes more widespread
|
||||
AC_ARG_WITH(nptl, [ --with-nptl Enable support for NPTL])
|
||||
|
||||
# assembly bundle support, see metadata/make-bundle.pl for more info
|
||||
AC_ARG_WITH(bundle, [ --with-bundle=bundle_template],[
|
||||
BUNDLE_FILE=$with_bundle
|
||||
AC_SUBST(BUNDLE_FILE)
|
||||
AC_DEFINE(WITH_BUNDLE)
|
||||
],[with_bundle=no])
|
||||
AM_CONDITIONAL(WITH_BUNDLE, test x$with_bundle != xno)
|
||||
|
||||
LIBGC_CFLAGS=
|
||||
LIBGC_LIBS=
|
||||
libgc_dir=
|
||||
case "x$gc" in
|
||||
xboehm|xbohem|xyes)
|
||||
AC_CHECK_HEADERS(gc.h gc/gc.h, gc_headers=yes)
|
||||
AC_CHECK_LIB(gc, GC_malloc, found_boehm="yes",,$libdl)
|
||||
|
||||
if test "x$found_boehm" != "xyes"; then
|
||||
AC_MSG_ERROR("GC requested but libgc not found! Install libgc or run configure with --with-gc=none.")
|
||||
AC_MSG_ERROR("GC requested but libgc not found!")
|
||||
fi
|
||||
if test "x$gc_headers" != "xyes"; then
|
||||
AC_MSG_ERROR("GC requested but header files not found! You may need to install them by hand.")
|
||||
@@ -247,56 +165,30 @@ case "x$gc" in
|
||||
|
||||
AC_DEFINE(HAVE_BOEHM_GC)
|
||||
AC_SUBST(HAVE_BOEHM_GC)
|
||||
LIBGC_LIBS="-lgc $libdl"
|
||||
|
||||
# AC_CHECK_FUNCS does not work for some reason...
|
||||
AC_CHECK_LIB(gc, GC_gcj_malloc, found_gcj_malloc="yes",,$libdl)
|
||||
if test "x$found_gcj_malloc" = "xyes"; then
|
||||
AC_DEFINE(HAVE_GC_GCJ_MALLOC)
|
||||
fi
|
||||
LIBS="$LIBS -lgc $libdl"
|
||||
;;
|
||||
|
||||
xincluded)
|
||||
AC_CONFIG_SUBDIRS(libgc)
|
||||
|
||||
found_boehm=yes
|
||||
gc_headers=yes
|
||||
use_included_gc=yes
|
||||
libgc_dir=libgc
|
||||
|
||||
LIBGC_CFLAGS='-I$(top_srcdir)/libgc/include'
|
||||
LIBGC_LIBS='$(top_builddir)/libgc/libmonogc.la'
|
||||
|
||||
AC_DEFINE(HAVE_BOEHM_GC)
|
||||
AC_SUBST(HAVE_BOEHM_GC)
|
||||
|
||||
AC_DEFINE(HAVE_GC_H)
|
||||
AC_DEFINE(USE_INCLUDED_LIBGC)
|
||||
|
||||
# The included libgc contains GCJ support
|
||||
AC_DEFINE(HAVE_GC_GCJ_MALLOC)
|
||||
;;
|
||||
|
||||
xnone)
|
||||
AC_MSG_WARN("Compiling mono without GC.")
|
||||
;;
|
||||
*)
|
||||
AC_MSG_ERROR([Invalid argument to --with-gc.])
|
||||
# If libgc was found, use it. Otherwise just warn.
|
||||
if test "x$found_boehm" != "xyes"; then
|
||||
AC_MSG_WARN("Compiling mono without GC.")
|
||||
else
|
||||
if test "x$gc_headers" != "xyes"; then
|
||||
AC_MSG_ERROR("Found libgc but not its header files! You may need to install them by hand.")
|
||||
fi
|
||||
AC_DEFINE(HAVE_BOEHM_GC)
|
||||
AC_SUBST(HAVE_BOEHM_GC)
|
||||
LIBS="$LIBS -lgc $libdl"
|
||||
gc="boehm"
|
||||
fi
|
||||
;;
|
||||
esac
|
||||
|
||||
we_are_embedded_in_mono=yes
|
||||
export we_are_embedded_in_mono
|
||||
export libgc_threads
|
||||
|
||||
AM_CONDITIONAL(INCLUDED_LIBGC, test x$use_included_gc = xyes)
|
||||
AC_SUBST(LIBGC_CFLAGS)
|
||||
AC_SUBST(LIBGC_LIBS)
|
||||
AC_SUBST(libgc_dir)
|
||||
|
||||
dnl
|
||||
dnl End of libgc checks
|
||||
dnl
|
||||
if test "x$gc" = xboehm; then
|
||||
AC_CHECK_FUNCS(GC_gcj_malloc)
|
||||
fi
|
||||
|
||||
if test x$platform_win32 = xno; then
|
||||
dnl ******************************************************************
|
||||
@@ -381,21 +273,6 @@ if test x$platform_win32 = xno; then
|
||||
AC_MSG_RESULT(no)
|
||||
])
|
||||
|
||||
dnl *****************************
|
||||
dnl *** Checks for SOL_IPV6 ***
|
||||
dnl *****************************
|
||||
AC_MSG_CHECKING(for SOL_IPV6)
|
||||
AC_TRY_COMPILE([#include <netdb.h>], [
|
||||
int level = SOL_IPV6;
|
||||
], [
|
||||
# Yes, we have it...
|
||||
AC_MSG_RESULT(yes)
|
||||
AC_DEFINE(HAVE_SOL_IPV6)
|
||||
], [
|
||||
# We'll have to use getprotobyname
|
||||
AC_MSG_RESULT(no)
|
||||
])
|
||||
|
||||
dnl *****************************
|
||||
dnl *** Checks for SOL_TCP ***
|
||||
dnl *****************************
|
||||
@@ -437,32 +314,8 @@ if test x$platform_win32 = xno; then
|
||||
AC_MSG_RESULT(yes)
|
||||
AC_DEFINE(HAVE_STRUCT_IP_MREQN)
|
||||
], [
|
||||
# We'll just have to try and use struct ip_mreq
|
||||
# We'll just have to use struct ip_mreq
|
||||
AC_MSG_RESULT(no)
|
||||
AC_MSG_CHECKING(for struct ip_mreq)
|
||||
AC_TRY_COMPILE([#include <netinet/in.h>], [
|
||||
struct ip_mreq mreq;
|
||||
mreq.imr_interface.s_addr = 0;
|
||||
], [
|
||||
# Yes, we have it...
|
||||
AC_MSG_RESULT(yes)
|
||||
AC_DEFINE(HAVE_STRUCT_IP_MREQ)
|
||||
], [
|
||||
# No multicast support
|
||||
AC_MSG_RESULT(no)
|
||||
])
|
||||
])
|
||||
|
||||
dnl **********************************
|
||||
dnl *** Check for gethostbyname2_r ***
|
||||
dnl **********************************
|
||||
AC_MSG_CHECKING(for gethostbyname2_r)
|
||||
AC_TRY_LINK([#include <netdb.h>], [
|
||||
gethostbyname2_r(NULL,0,NULL,NULL,0,NULL,NULL);
|
||||
], [
|
||||
# Yes, we have it...
|
||||
AC_MSG_RESULT(yes)
|
||||
AC_DEFINE(HAVE_GETHOSTBYNAME2_R)
|
||||
])
|
||||
|
||||
dnl *****************************
|
||||
@@ -496,23 +349,6 @@ if test x$platform_win32 = xno; then
|
||||
AC_MSG_RESULT($cv_mono_sizeof_sunpath)
|
||||
AC_DEFINE_UNQUOTED(MONO_SIZEOF_SUNPATH, $cv_mono_sizeof_sunpath)
|
||||
|
||||
dnl *************************************
|
||||
dnl *** Checks for zero length arrays ***
|
||||
dnl *************************************
|
||||
AC_MSG_CHECKING(whether $CC supports zero length arrays)
|
||||
AC_TRY_COMPILE([
|
||||
struct s {
|
||||
int length;
|
||||
char data [0];
|
||||
};
|
||||
], [], [
|
||||
AC_MSG_RESULT(yes)
|
||||
AC_DEFINE_UNQUOTED(MONO_ZERO_ARRAY_LENGTH, 0)
|
||||
], [
|
||||
AC_MSG_RESULT(no)
|
||||
AC_DEFINE_UNQUOTED(MONO_ZERO_ARRAY_LENGTH, 1)
|
||||
])
|
||||
|
||||
dnl *****************************
|
||||
dnl *** Checks for libxnet ***
|
||||
dnl *****************************
|
||||
@@ -539,7 +375,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>], [
|
||||
@@ -552,59 +387,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 **
|
||||
@@ -631,40 +418,6 @@ if test x$platform_win32 = xno; then
|
||||
AC_ERROR(unable to find a way to determine timezone)
|
||||
fi
|
||||
fi
|
||||
|
||||
dnl *********************************
|
||||
dnl *** Checks for math functions ***
|
||||
dnl *********************************
|
||||
LIBS="$LIBS -lm";
|
||||
AC_CHECK_FUNCS(finite, , AC_MSG_CHECKING(for finite in math.h)
|
||||
AC_TRY_LINK([#include <math.h>],
|
||||
[ finite(0.0); ],
|
||||
AC_DEFINE(HAVE_FINITE) AC_MSG_RESULT(yes),
|
||||
AC_MSG_RESULT(no)))
|
||||
AC_CHECK_FUNCS(isfinite, , AC_MSG_CHECKING(for isfinite in math.h)
|
||||
AC_TRY_LINK([#include <math.h>],
|
||||
[ isfinite(0.0); ],
|
||||
AC_DEFINE(HAVE_ISFINITE) AC_MSG_RESULT(yes),
|
||||
AC_MSG_RESULT(no)))
|
||||
|
||||
dnl ****************************************************************
|
||||
dnl *** Checks for working poll() (macosx defines it but doesn't ***
|
||||
dnl *** have it in the library (duh)) ***
|
||||
dnl ****************************************************************
|
||||
AC_CHECK_FUNCS(poll)
|
||||
|
||||
dnl *************************
|
||||
dnl *** Check for signbit ***
|
||||
dnl *************************
|
||||
AC_MSG_CHECKING(for signbit)
|
||||
AC_TRY_LINK([#include <math.h>], [
|
||||
int s = signbit(1.0);
|
||||
], [
|
||||
AC_MSG_RESULT(yes)
|
||||
AC_DEFINE(HAVE_SIGNBIT)
|
||||
], [
|
||||
AC_MSG_RESULT(no)
|
||||
])
|
||||
else
|
||||
AC_CHECK_LIB(ws2_32, main, LIBS="$LIBS -lws2_32", AC_ERROR(bad mingw install?))
|
||||
AC_CHECK_LIB(psapi, main, LIBS="$LIBS -lpsapi", AC_ERROR(bad mingw install?))
|
||||
@@ -743,101 +496,20 @@ if test "x$try_shared_handles" != "xyes"; then
|
||||
AC_SUBST(DISABLE_SHARED_HANDLES)
|
||||
fi
|
||||
|
||||
ICU_CFLAGS=""
|
||||
ICU_LIBS=""
|
||||
enable_icu=no
|
||||
AC_PATH_PROG(ICU_CONFIG, icu-config, no)
|
||||
if test "x$ICU_CONFIG" = "xno" -o ! -x "$ICU_CONFIG"; then
|
||||
AC_MSG_WARN([Only invariant locale available; install ICU for I18N support])
|
||||
else
|
||||
enable_icu="yes. Version: `$ICU_CONFIG --version`"
|
||||
AC_DEFINE(HAVE_ICU)
|
||||
ICU_CFLAGS=`$ICU_CONFIG --cppflags`
|
||||
ICU_LIBS=`$ICU_CONFIG --ldflags`
|
||||
fi
|
||||
AC_SUBST(ICU_CFLAGS)
|
||||
AC_SUBST(ICU_LIBS)
|
||||
|
||||
TARGET="unknown"
|
||||
ACCESS_UNALIGNED="yes"
|
||||
|
||||
JIT_SUPPORTED=no
|
||||
LIBC="libc.so.6"
|
||||
|
||||
case "$host" in
|
||||
# mips-sgi-irix5.* | mips-sgi-irix6.*)
|
||||
# TARGET=MIPS;
|
||||
# ACCESS_UNALIGNED="no"
|
||||
# ;;
|
||||
i*86-*-*)
|
||||
TARGET=X86;
|
||||
arch_target=x86;
|
||||
JIT_SUPPORTED=yes
|
||||
;;
|
||||
sparc*-*-*)
|
||||
TARGET=SPARC;
|
||||
arch_target=sparc;
|
||||
ACCESS_UNALIGNED="no"
|
||||
;;
|
||||
# alpha*-*-linux* | alpha*-*-osf*)
|
||||
# TARGET=ALPHA;
|
||||
# ACCESS_UNALIGNED="no"
|
||||
# ;;
|
||||
# ia64-*-linux* | ia64-*-hpux*)
|
||||
# TARGET=IA64;
|
||||
# arch_target=ia64;
|
||||
# JIT_SUPPORTED=no;
|
||||
# ACCESS_UNALIGNED="no";
|
||||
# case "$host_os" in
|
||||
# linux*) LIBC="libc.so.6.1";;
|
||||
# hpux*) LIBC="libc.so.1";;
|
||||
# esac
|
||||
# ;;
|
||||
# m68k-*-linux*)
|
||||
# TARGET=M68K
|
||||
# ;;
|
||||
hppa2.0w-hp-hpux11.00 | hppa64-hp-hpux11.00)
|
||||
TARGET=HPPA;
|
||||
arch_target=hppa;
|
||||
ACCESS_UNALIGNED="no"
|
||||
;;
|
||||
macppc-*-openbsd* | powerpc-*-linux* | powerpc-*-openbsd* | \
|
||||
powerpc-*-sysv* | powerpc-*-darwin*)
|
||||
TARGET=POWERPC;
|
||||
arch_target=ppc;
|
||||
JIT_SUPPORTED=yes
|
||||
;;
|
||||
arm-*-linux-* | armv4l-*-linux-*)
|
||||
TARGET=ARM;
|
||||
arch_target=arm;
|
||||
ACCESS_UNALIGNED="no"
|
||||
;;
|
||||
s390-*-linux*)
|
||||
TARGET=S390;
|
||||
arch_target=s390;
|
||||
ACCESS_UNALIGNED="no"
|
||||
;;
|
||||
#mips-sgi-irix5.* | mips-sgi-irix6.*) TARGET=MIPS; ACCESS_UNALIGNED="no";;
|
||||
i*86-*-*) TARGET=X86; arch_target=x86;;
|
||||
sparc*-*-*) TARGET=SPARC; arch_target=sparc; ACCESS_UNALIGNED="no";;
|
||||
#alpha*-*-linux* | alpha*-*-osf*) TARGET=ALPHA; ACCESS_UNALIGNED="no";;
|
||||
#m68k-*-linux*) TARGET=M68K;;
|
||||
macppc-*-openbsd* | powerpc-*-linux* | powerpc-*-openbsd* | powerpc-*-sysv* | powerpc-*-darwin*) TARGET=POWERPC; arch_target=ppc;;
|
||||
arm-*-linux-* | armv4l-*-linux-*) TARGET=ARM; arch_target=arm; ACCESS_UNALIGNED="no";;
|
||||
s390-*-linux*) TARGET=S390; arch_target=s390; ACCESS_UNALIGNED="no";;
|
||||
esac
|
||||
|
||||
if test ${TARGET} = ARM; then
|
||||
dnl ******************************************
|
||||
dnl *** Check to see what FPU is available ***
|
||||
dnl ******************************************
|
||||
AC_MSG_CHECKING(which FPU to use)
|
||||
|
||||
AC_TRY_COMPILE([], [
|
||||
__asm__ ("ldfd f0, [r0]");
|
||||
], fpu=FPA, [
|
||||
AC_TRY_COMPILE([], [
|
||||
__asm__ ("fldd d0, [r0]");
|
||||
], fpu=VFP, fpu=NONE)
|
||||
])
|
||||
|
||||
AC_MSG_RESULT($fpu)
|
||||
CPPFLAGS="$CPPFLAGS -DARM_FPU_$fpu"
|
||||
unset fpu
|
||||
fi
|
||||
|
||||
if test ${TARGET} = unknown; then
|
||||
CPPFLAGS="$CPPFLAGS -DNO_PORT"
|
||||
AC_MSG_WARN("mono has not been ported to $host: some things may not work.")
|
||||
@@ -852,15 +524,12 @@ AM_CONDITIONAL(MIPS_SGI, test ${TARGET}${ac_cv_prog_gcc} = MIPSno)
|
||||
AM_CONDITIONAL(SPARC, test x$TARGET = xSPARC)
|
||||
AM_CONDITIONAL(X86, test x$TARGET = xX86)
|
||||
AM_CONDITIONAL(ALPHA, test x$TARGET = xALPHA)
|
||||
AM_CONDITIONAL(IA64, test x$TARGET = xIA64)
|
||||
AM_CONDITIONAL(M68K, test x$TARGET = xM68K)
|
||||
AM_CONDITIONAL(POWERPC, test x$TARGET = xPOWERPC)
|
||||
AM_CONDITIONAL(ARM, test x$TARGET = xARM)
|
||||
AM_CONDITIONAL(S390, test x$TARGET = xS390)
|
||||
AM_CONDITIONAL(HPPA, test x$TARGET = xHPPA)
|
||||
|
||||
AM_CONDITIONAL(JIT_SUPPORTED, test x$JIT_SUPPORTED = xyes)
|
||||
|
||||
LIBC="libc.so.6"
|
||||
AC_SUBST(LIBC)
|
||||
|
||||
AC_SUBST(arch_target)
|
||||
@@ -881,7 +550,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
|
||||
@@ -889,27 +557,24 @@ mono/arch/arm/Makefile
|
||||
mono/arch/alpha/Makefile
|
||||
mono/interpreter/Makefile
|
||||
mono/tests/Makefile
|
||||
mono/tests/tests-config
|
||||
mono/benchmark/Makefile
|
||||
mono/monoburg/Makefile
|
||||
mono/monograph/Makefile
|
||||
mono/jit/Makefile
|
||||
mono/io-layer/Makefile
|
||||
mono/handles/Makefile
|
||||
mono/mini/Makefile
|
||||
mono/profiler/Makefile
|
||||
runtime/Makefile
|
||||
scripts/Makefile
|
||||
man/Makefile
|
||||
doc/Makefile
|
||||
docs/Makefile
|
||||
data/Makefile
|
||||
samples/Makefile
|
||||
data/config
|
||||
mono.spec
|
||||
])
|
||||
|
||||
echo "
|
||||
|
||||
GC: $gc
|
||||
ICU: $enable_icu
|
||||
|
||||
"
|
||||
@@ -1,4 +0,0 @@
|
||||
Makefile.in
|
||||
Makefile
|
||||
config
|
||||
.cvsignore
|
||||
@@ -1,927 +0,0 @@
|
||||
<%
|
||||
//
|
||||
// DefaultWsdlHelpGenerator.aspx:
|
||||
//
|
||||
// Author:
|
||||
// Lluis Sanchez Gual ([email protected])
|
||||
//
|
||||
// (C) 2003 Ximian, Inc. http://www.ximian.com
|
||||
//
|
||||
%>
|
||||
|
||||
<%@ Import Namespace="System.Collections" %>
|
||||
<%@ Import Namespace="System.IO" %>
|
||||
<%@ Import Namespace="System.Xml.Serialization" %>
|
||||
<%@ Import Namespace="System.Xml" %>
|
||||
<%@ Import Namespace="System.Xml.Schema" %>
|
||||
<%@ Import Namespace="System.Web.Services.Description" %>
|
||||
<%@ Import Namespace="System" %>
|
||||
<%@ Import Namespace="System.Net" %>
|
||||
<%@ Import Namespace="System.Globalization" %>
|
||||
<%@ Import Namespace="System.Resources" %>
|
||||
<%@ Import Namespace="System.Diagnostics" %>
|
||||
<%@ Import Namespace="System.CodeDom" %>
|
||||
<%@ Import Namespace="System.CodeDom.Compiler" %>
|
||||
<%@ Import Namespace="Microsoft.CSharp" %>
|
||||
<%@ Import Namespace="Microsoft.VisualBasic" %>
|
||||
<%@ Import Namespace="System.Text.RegularExpressions" %>
|
||||
<%@ Assembly name="System.Web.Services" %>
|
||||
<%@ Page debug="true" %>
|
||||
|
||||
<html>
|
||||
<script language="C#" runat="server">
|
||||
|
||||
ServiceDescriptionCollection descriptions;
|
||||
XmlSchemas schemas;
|
||||
|
||||
string WebServiceName;
|
||||
string WebServiceDescription;
|
||||
string PageName;
|
||||
|
||||
string DefaultBinding;
|
||||
ArrayList ServiceProtocols;
|
||||
|
||||
string CurrentOperationName;
|
||||
string CurrentOperationBinding;
|
||||
string OperationDocumentation;
|
||||
string CurrentOperationFormat;
|
||||
bool CurrentOperationSupportsTest;
|
||||
ArrayList InParams;
|
||||
ArrayList OutParams;
|
||||
string CurrentOperationProtocols;
|
||||
int CodeTextColumns = 95;
|
||||
|
||||
void Page_Load(object sender, EventArgs e)
|
||||
{
|
||||
descriptions = (ServiceDescriptionCollection) Context.Items["wsdls"];
|
||||
schemas = (XmlSchemas) Context.Items["schemas"];
|
||||
|
||||
ServiceDescription desc = descriptions [0];
|
||||
if (schemas.Count == 0) schemas = desc.Types.Schemas;
|
||||
|
||||
Service service = desc.Services[0];
|
||||
WebServiceName = service.Name;
|
||||
DefaultBinding = desc.Bindings[0].Name;
|
||||
WebServiceDescription = service.Documentation;
|
||||
ServiceProtocols = FindServiceProtocols (null);
|
||||
|
||||
CurrentOperationName = Request.QueryString["op"];
|
||||
CurrentOperationBinding = Request.QueryString["bnd"];
|
||||
if (CurrentOperationName != null) BuildOperationInfo ();
|
||||
|
||||
PageName = HttpUtility.UrlEncode (Path.GetFileName(Request.Path), Encoding.UTF8);
|
||||
|
||||
ArrayList list = new ArrayList ();
|
||||
foreach (ServiceDescription sd in descriptions) {
|
||||
foreach (Binding bin in sd.Bindings)
|
||||
if (bin.Extensions.Find (typeof(SoapBinding)) != null) list.Add (bin);
|
||||
}
|
||||
|
||||
BindingsRepeater.DataSource = list;
|
||||
Page.DataBind();
|
||||
}
|
||||
|
||||
void BuildOperationInfo ()
|
||||
{
|
||||
InParams = new ArrayList ();
|
||||
OutParams = new ArrayList ();
|
||||
|
||||
Binding binding = FindBinding (CurrentOperationBinding);
|
||||
PortType portType = descriptions.GetPortType (binding.Type);
|
||||
Operation oper = FindOperation (portType, CurrentOperationName);
|
||||
|
||||
OperationDocumentation = oper.Documentation;
|
||||
if (OperationDocumentation == null || OperationDocumentation == "")
|
||||
OperationDocumentation = "No additional remarks";
|
||||
|
||||
foreach (OperationMessage opm in oper.Messages)
|
||||
{
|
||||
if (opm is OperationInput)
|
||||
BuildParameters (InParams, opm);
|
||||
else if (opm is OperationOutput)
|
||||
BuildParameters (OutParams, opm);
|
||||
}
|
||||
|
||||
// Protocols supported by the operation
|
||||
CurrentOperationProtocols = "";
|
||||
ArrayList prots = FindServiceProtocols (CurrentOperationName);
|
||||
for (int n=0; n<prots.Count; n++) {
|
||||
if (n != 0) CurrentOperationProtocols += ", ";
|
||||
CurrentOperationProtocols += (string) prots[n];
|
||||
}
|
||||
|
||||
CurrentOperationSupportsTest = prots.Contains ("HttpGet") || prots.Contains ("HttpPost");
|
||||
|
||||
// Operation format
|
||||
OperationBinding obin = FindOperation (binding, CurrentOperationName);
|
||||
if (obin != null)
|
||||
CurrentOperationFormat = GetOperationFormat (obin);
|
||||
|
||||
InputParamsRepeater.DataSource = InParams;
|
||||
InputFormParamsRepeater.DataSource = InParams;
|
||||
OutputParamsRepeater.DataSource = OutParams;
|
||||
}
|
||||
|
||||
void BuildParameters (ArrayList list, OperationMessage opm)
|
||||
{
|
||||
Message msg = descriptions.GetMessage (opm.Message);
|
||||
if (msg.Parts.Count > 0 && msg.Parts[0].Name == "parameters")
|
||||
{
|
||||
MessagePart part = msg.Parts[0];
|
||||
XmlSchemaComplexType ctype;
|
||||
if (part.Element == XmlQualifiedName.Empty)
|
||||
{
|
||||
ctype = (XmlSchemaComplexType) schemas.Find (part.Type, typeof(XmlSchemaComplexType));
|
||||
}
|
||||
else
|
||||
{
|
||||
XmlSchemaElement elem = (XmlSchemaElement) schemas.Find (part.Element, typeof(XmlSchemaElement));
|
||||
ctype = (XmlSchemaComplexType) elem.SchemaType;
|
||||
}
|
||||
XmlSchemaSequence seq = ctype.Particle as XmlSchemaSequence;
|
||||
if (seq == null) return;
|
||||
|
||||
foreach (XmlSchemaObject ob in seq.Items)
|
||||
{
|
||||
Parameter p = new Parameter();
|
||||
p.Description = "No additional remarks";
|
||||
|
||||
if (ob is XmlSchemaElement)
|
||||
{
|
||||
XmlSchemaElement selem = GetRefElement ((XmlSchemaElement)ob);
|
||||
p.Name = selem.Name;
|
||||
p.Type = selem.SchemaTypeName.Name;
|
||||
}
|
||||
else
|
||||
{
|
||||
p.Name = "Unknown";
|
||||
p.Type = "Unknown";
|
||||
}
|
||||
list.Add (p);
|
||||
}
|
||||
}
|
||||
else
|
||||
{
|
||||
foreach (MessagePart part in msg.Parts)
|
||||
{
|
||||
Parameter p = new Parameter ();
|
||||
p.Description = "No additional remarks";
|
||||
p.Name = part.Name;
|
||||
if (part.Element == XmlQualifiedName.Empty)
|
||||
p.Type = part.Type.Name;
|
||||
else
|
||||
{
|
||||
XmlSchemaElement elem = (XmlSchemaElement) schemas.Find (part.Element, typeof(XmlSchemaElement));
|
||||
p.Type = elem.SchemaTypeName.Name;
|
||||
}
|
||||
list.Add (p);
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
string GetOperationFormat (OperationBinding obin)
|
||||
{
|
||||
string format = "";
|
||||
SoapOperationBinding sob = obin.Extensions.Find (typeof(SoapOperationBinding)) as SoapOperationBinding;
|
||||
if (sob != null) {
|
||||
format = sob.Style.ToString ();
|
||||
SoapBodyBinding sbb = obin.Input.Extensions.Find (typeof(SoapBodyBinding)) as SoapBodyBinding;
|
||||
if (sbb != null)
|
||||
format += " / " + sbb.Use;
|
||||
}
|
||||
return format;
|
||||
}
|
||||
|
||||
XmlSchemaElement GetRefElement (XmlSchemaElement elem)
|
||||
{
|
||||
if (!elem.RefName.IsEmpty)
|
||||
return (XmlSchemaElement) schemas.Find (elem.RefName, typeof(XmlSchemaElement));
|
||||
else
|
||||
return elem;
|
||||
}
|
||||
|
||||
ArrayList FindServiceProtocols(string operName)
|
||||
{
|
||||
ArrayList table = new ArrayList ();
|
||||
Service service = descriptions[0].Services[0];
|
||||
foreach (Port port in service.Ports)
|
||||
{
|
||||
string prot = null;
|
||||
Binding bin = descriptions.GetBinding (port.Binding);
|
||||
if (bin.Extensions.Find (typeof(SoapBinding)) != null)
|
||||
prot = "Soap";
|
||||
else
|
||||
{
|
||||
HttpBinding hb = (HttpBinding) bin.Extensions.Find (typeof(HttpBinding));
|
||||
if (hb != null && hb.Verb == "POST") prot = "HttpPost";
|
||||
else if (hb != null && hb.Verb == "GET") prot = "HttpGet";
|
||||
}
|
||||
|
||||
if (prot != null && operName != null)
|
||||
{
|
||||
if (FindOperation (bin, operName) == null)
|
||||
prot = null;
|
||||
}
|
||||
|
||||
if (prot != null && !table.Contains (prot))
|
||||
table.Add (prot);
|
||||
}
|
||||
return table;
|
||||
}
|
||||
|
||||
Binding FindBinding (string portName)
|
||||
{
|
||||
Service service = descriptions[0].Services[0];
|
||||
foreach (Port port in service.Ports)
|
||||
if (port.Name == portName)
|
||||
return descriptions.GetBinding (port.Binding);
|
||||
return null;
|
||||
}
|
||||
|
||||
Operation FindOperation (PortType portType, string name)
|
||||
{
|
||||
foreach (Operation oper in portType.Operations) {
|
||||
if (oper.Messages.Input.Name != null) {
|
||||
if (oper.Messages.Input.Name == name) return oper;
|
||||
}
|
||||
else
|
||||
if (oper.Name == name) return oper;
|
||||
}
|
||||
|
||||
return null;
|
||||
}
|
||||
|
||||
OperationBinding FindOperation (Binding binding, string name)
|
||||
{
|
||||
foreach (OperationBinding oper in binding.Operations) {
|
||||
if (oper.Input.Name != null) {
|
||||
if (oper.Input.Name == name) return oper;
|
||||
}
|
||||
else
|
||||
if (oper.Name == name) return oper;
|
||||
}
|
||||
|
||||
return null;
|
||||
}
|
||||
|
||||
string FormatBindingName (string name)
|
||||
{
|
||||
if (name == DefaultBinding) return "Methods";
|
||||
else return "Methods for binding<br>" + name;
|
||||
}
|
||||
|
||||
string GetOpName (object op)
|
||||
{
|
||||
OperationBinding ob = op as OperationBinding;
|
||||
if (ob == null) return "";
|
||||
if (ob.Input.Name != null) return ob.Input.Name;
|
||||
else return ob.Name;
|
||||
}
|
||||
|
||||
bool HasFormResult
|
||||
{
|
||||
get { return Request.QueryString ["ext"] == "testform"; }
|
||||
}
|
||||
|
||||
string GetTestResult ()
|
||||
{
|
||||
if (!HasFormResult) return null;
|
||||
|
||||
bool fill = false;
|
||||
string qs = "";
|
||||
for (int n=0; n<Request.QueryString.Count; n++)
|
||||
{
|
||||
if (fill) {
|
||||
if (qs != "") qs += "&";
|
||||
qs += Request.QueryString.GetKey(n) + "=" + Request.QueryString [n];
|
||||
}
|
||||
if (Request.QueryString.GetKey(n) == "ext") fill = true;
|
||||
}
|
||||
|
||||
string location = null;
|
||||
ServiceDescription desc = descriptions [0];
|
||||
Service service = desc.Services[0];
|
||||
foreach (Port port in service.Ports)
|
||||
if (port.Name == CurrentOperationBinding)
|
||||
{
|
||||
SoapAddressBinding sbi = (SoapAddressBinding) port.Extensions.Find (typeof(SoapAddressBinding));
|
||||
if (sbi != null)
|
||||
location = sbi.Location;
|
||||
}
|
||||
|
||||
if (location == null)
|
||||
return "Could not locate web service";
|
||||
|
||||
try
|
||||
{
|
||||
WebRequest req = WebRequest.Create (location + "/" + CurrentOperationName + "?" + qs);
|
||||
WebResponse resp = req.GetResponse();
|
||||
StreamReader sr = new StreamReader (resp.GetResponseStream());
|
||||
string s = sr.ReadToEnd ();
|
||||
sr.Close ();
|
||||
return "<div class='code-xml'>" + ColorizeXml(WrapText(s,CodeTextColumns)) + "</div>";
|
||||
}
|
||||
catch (Exception ex)
|
||||
{
|
||||
string res = "<b style='color:red'>" + ex.Message + "</b>";
|
||||
WebException wex = ex as WebException;
|
||||
if (wex != null)
|
||||
{
|
||||
WebResponse resp = wex.Response;
|
||||
if (resp != null) {
|
||||
StreamReader sr = new StreamReader (resp.GetResponseStream());
|
||||
string s = sr.ReadToEnd ();
|
||||
sr.Close ();
|
||||
res += "<div class='code-xml'>" + ColorizeXml(WrapText(s,CodeTextColumns)) + "</div>";
|
||||
}
|
||||
}
|
||||
return res;
|
||||
}
|
||||
}
|
||||
|
||||
//
|
||||
// Proxy code generation
|
||||
//
|
||||
|
||||
string GetProxyCode ()
|
||||
{
|
||||
CodeNamespace codeNamespace = new CodeNamespace();
|
||||
CodeCompileUnit codeUnit = new CodeCompileUnit();
|
||||
|
||||
codeUnit.Namespaces.Add (codeNamespace);
|
||||
|
||||
ServiceDescriptionImporter importer = new ServiceDescriptionImporter();
|
||||
|
||||
foreach (ServiceDescription sd in descriptions)
|
||||
importer.AddServiceDescription(sd, null, null);
|
||||
|
||||
foreach (XmlSchema sc in schemas)
|
||||
importer.Schemas.Add (sc);
|
||||
|
||||
importer.Import(codeNamespace, codeUnit);
|
||||
|
||||
string langId = Request.QueryString ["lang"];
|
||||
if (langId == null || langId == "") langId = "cs";
|
||||
CodeDomProvider provider = GetProvider (langId);
|
||||
ICodeGenerator generator = provider.CreateGenerator();
|
||||
CodeGeneratorOptions options = new CodeGeneratorOptions();
|
||||
|
||||
StringWriter sw = new StringWriter ();
|
||||
generator.GenerateCodeFromCompileUnit(codeUnit, sw, options);
|
||||
|
||||
return Colorize (WrapText (sw.ToString (), CodeTextColumns), langId);
|
||||
}
|
||||
|
||||
public string CurrentLanguage
|
||||
{
|
||||
get {
|
||||
string langId = Request.QueryString ["lang"];
|
||||
if (langId == null || langId == "") langId = "cs";
|
||||
return langId;
|
||||
}
|
||||
}
|
||||
|
||||
public string CurrentProxytName
|
||||
{
|
||||
get {
|
||||
string lan = CurrentLanguage == "cs" ? "C#" : "Visual Basic";
|
||||
return lan + " Client Proxy";
|
||||
}
|
||||
}
|
||||
|
||||
private CodeDomProvider GetProvider(string langId)
|
||||
{
|
||||
switch (langId.ToUpper())
|
||||
{
|
||||
case "CS": return new CSharpCodeProvider();
|
||||
case "VB": return new VBCodeProvider();
|
||||
default: return null;
|
||||
}
|
||||
}
|
||||
|
||||
//
|
||||
// Document generation
|
||||
//
|
||||
|
||||
string GenerateDocument ()
|
||||
{
|
||||
StringWriter sw = new StringWriter ();
|
||||
|
||||
if (CurrentDocType == "wsdl")
|
||||
descriptions [CurrentDocInd].Write (sw);
|
||||
else if (CurrentDocType == "schema")
|
||||
schemas [CurrentDocInd].Write (sw);
|
||||
|
||||
return Colorize (WrapText (sw.ToString (), CodeTextColumns), "xml");
|
||||
}
|
||||
|
||||
public string CurrentDocType
|
||||
{
|
||||
get { return Request.QueryString ["doctype"] != null ? Request.QueryString ["doctype"] : "wsdl"; }
|
||||
}
|
||||
|
||||
public int CurrentDocInd
|
||||
{
|
||||
get { return Request.QueryString ["docind"] != null ? int.Parse (Request.QueryString ["docind"]) : 0; }
|
||||
}
|
||||
|
||||
public string CurrentDocumentName
|
||||
{
|
||||
get {
|
||||
if (CurrentDocType == "wsdl")
|
||||
return "WSDL document for namespace \"" + descriptions [CurrentDocInd].TargetNamespace + "\"";
|
||||
else
|
||||
return "Xml Schema for namespace \"" + schemas [CurrentDocInd].TargetNamespace + "\"";
|
||||
}
|
||||
}
|
||||
|
||||
//
|
||||
// Pages and tabs
|
||||
//
|
||||
|
||||
bool firstTab = true;
|
||||
ArrayList disabledTabs = new ArrayList ();
|
||||
|
||||
string CurrentTab
|
||||
{
|
||||
get { return Request.QueryString["tab"] != null ? Request.QueryString["tab"] : "main" ; }
|
||||
}
|
||||
|
||||
string CurrentPage
|
||||
{
|
||||
get { return Request.QueryString["page"] != null ? Request.QueryString["page"] : "main" ; }
|
||||
}
|
||||
|
||||
void WriteTabs ()
|
||||
{
|
||||
if (CurrentOperationName != null)
|
||||
{
|
||||
WriteTab ("main","Overview");
|
||||
WriteTab ("test","Test Form");
|
||||
WriteTab ("msg","Message Layout");
|
||||
}
|
||||
}
|
||||
|
||||
void WriteTab (string id, string label)
|
||||
{
|
||||
if (!firstTab) Response.Write(" | ");
|
||||
firstTab = false;
|
||||
|
||||
string cname = CurrentTab == id ? "tabLabelOn" : "tabLabelOff";
|
||||
Response.Write ("<a href='" + PageName + "?" + GetPageContext(null) + GetDataContext() + "tab=" + id + "' style='text-decoration:none'>");
|
||||
Response.Write ("<span class='" + cname + "'>" + label + "</span>");
|
||||
Response.Write ("</a>");
|
||||
}
|
||||
|
||||
string GetTabContext (string pag, string tab)
|
||||
{
|
||||
if (tab == null) tab = CurrentTab;
|
||||
if (pag == null) pag = CurrentPage;
|
||||
if (pag != CurrentPage) tab = "main";
|
||||
return "page=" + pag + "&tab=" + tab + "&";
|
||||
}
|
||||
|
||||
string GetPageContext (string pag)
|
||||
{
|
||||
if (pag == null) pag = CurrentPage;
|
||||
return "page=" + pag + "&";
|
||||
}
|
||||
|
||||
class Tab
|
||||
{
|
||||
public string Id;
|
||||
public string Label;
|
||||
}
|
||||
|
||||
//
|
||||
// Syntax coloring
|
||||
//
|
||||
|
||||
static string keywords_cs =
|
||||
"(\\babstract\\b|\\bevent\\b|\\bnew\\b|\\bstruct\\b|\\bas\\b|\\bexplicit\\b|\\bnull\\b|\\bswitch\\b|\\bbase\\b|\\bextern\\b|" +
|
||||
"\\bobject\\b|\\bthis\\b|\\bbool\\b|\\bfalse\\b|\\boperator\\b|\\bthrow\\b|\\bbreak\\b|\\bfinally\\b|\\bout\\b|\\btrue\\b|" +
|
||||
"\\bbyte\\b|\\bfixed\\b|\\boverride\\b|\\btry\\b|\\bcase\\b|\\bfloat\\b|\\bparams\\b|\\btypeof\\b|\\bcatch\\b|\\bfor\\b|" +
|
||||
"\\bprivate\\b|\\buint\\b|\\bchar\\b|\\bforeach\\b|\\bprotected\\b|\\bulong\\b|\\bchecked\\b|\\bgoto\\b|\\bpublic\\b|" +
|
||||
"\\bunchecked\\b|\\bclass\\b|\\bif\\b|\\breadonly\\b|\\bunsafe\\b|\\bconst\\b|\\bimplicit\\b|\\bref\\b|\\bushort\\b|" +
|
||||
"\\bcontinue\\b|\\bin\\b|\\breturn\\b|\\busing\\b|\\bdecimal\\b|\\bint\\b|\\bsbyte\\b|\\bvirtual\\b|\\bdefault\\b|" +
|
||||
"\\binterface\\b|\\bsealed\\b|\\bvolatile\\b|\\bdelegate\\b|\\binternal\\b|\\bshort\\b|\\bvoid\\b|\\bdo\\b|\\bis\\b|" +
|
||||
"\\bsizeof\\b|\\bwhile\\b|\\bdouble\\b|\\block\\b|\\bstackalloc\\b|\\belse\\b|\\blong\\b|\\bstatic\\b|\\benum\\b|" +
|
||||
"\\bnamespace\\b|\\bstring\\b)";
|
||||
|
||||
static string keywords_vb =
|
||||
"(\\bAddHandler\\b|\\bAddressOf\\b|\\bAlias\\b|\\bAnd\\b|\\bAndAlso\\b|\\bAnsi\\b|\\bAs\\b|\\bAssembly\\b|" +
|
||||
"\\bAuto\\b|\\bBoolean\\b|\\bByRef\\b|\\bByte\\b|\\bByVal\\b|\\bCall\\b|\\bCase\\b|\\bCatch\\b|" +
|
||||
"\\bCBool\\b|\\bCByte\\b|\\bCChar\\b|\\bCDate\\b|\\bCDec\\b|\\bCDbl\\b|\\bChar\\b|\\bCInt\\b|" +
|
||||
"\\bClass\\b|\\bCLng\\b|\\bCObj\\b|\\bConst\\b|\\bCShort\\b|\\bCSng\\b|\\bCStr\\b|\\bCType\\b|" +
|
||||
"\\bDate\\b|\\bDecimal\\b|\\bDeclare\\b|\\bDefault\\b|\\bDelegate\\b|\\bDim\\b|\\bDirectCast\\b|\\bDo\\b|" +
|
||||
"\\bDouble\\b|\\bEach\\b|\\bElse\\b|\\bElseIf\\b|\\bEnd\\b|\\bEnum\\b|\\bErase\\b|\\bError\\b|" +
|
||||
"\\bEvent\\b|\\bExit\\b|\\bFalse\\b|\\bFinally\\b|\\bFor\\b|\\bFriend\\b|\\bFunction\\b|\\bGet\\b|" +
|
||||
"\\bGetType\\b|\\bGoSub\\b|\\bGoTo\\b|\\bHandles\\b|\\bIf\\b|\\bImplements\\b|\\bImports\\b|\\bIn\\b|" +
|
||||
"\\bInherits\\b|\\bInteger\\b|\\bInterface\\b|\\bIs\\b|\\bLet\\b|\\bLib\\b|\\bLike\\b|\\bLong\\b|" +
|
||||
"\\bLoop\\b|\\bMe\\b|\\bMod\\b|\\bModule\\b|\\bMustInherit\\b|\\bMustOverride\\b|\\bMyBase\\b|\\bMyClass\\b|" +
|
||||
"\\bNamespace\\b|\\bNew\\b|\\bNext\\b|\\bNot\\b|\\bNothing\\b|\\bNotInheritable\\b|\\bNotOverridable\\b|\\bObject\\b|" +
|
||||
"\\bOn\\b|\\bOption\\b|\\bOptional\\b|\\bOr\\b|\\bOrElse\\b|\\bOverloads\\b|\\bOverridable\\b|\\bOverrides\\b|" +
|
||||
"\\bParamArray\\b|\\bPreserve\\b|\\bPrivate\\b|\\bProperty\\b|\\bProtected\\b|\\bPublic\\b|\\bRaiseEvent\\b|\\bReadOnly\\b|" +
|
||||
"\\bReDim\\b|\\bREM\\b|\\bRemoveHandler\\b|\\bResume\\b|\\bReturn\\b|\\bSelect\\b|\\bSet\\b|\\bShadows\\b|" +
|
||||
"\\bShared\\b|\\bShort\\b|\\bSingle\\b|\\bStatic\\b|\\bStep\\b|\\bStop\\b|\\bString\\b|\\bStructure\\b|" +
|
||||
"\\bSub\\b|\\bSyncLock\\b|\\bThen\\b|\\bThrow\\b|\\bTo\\b|\\bTrue\\b|\\bTry\\b|\\bTypeOf\\b|" +
|
||||
"\\bUnicode\\b|\\bUntil\\b|\\bVariant\\b|\\bWhen\\b|\\bWhile\\b|\\bWith\\b|\\bWithEvents\\b|\\bWriteOnly\\b|\\bXor\\b)";
|
||||
|
||||
string Colorize (string text, string lang)
|
||||
{
|
||||
if (lang == "xml") return ColorizeXml (text);
|
||||
else if (lang == "cs") return ColorizeCs (text);
|
||||
else if (lang == "vb") return ColorizeVb (text);
|
||||
else return text;
|
||||
}
|
||||
|
||||
string ColorizeXml (string text)
|
||||
{
|
||||
text = text.Replace (" ", " ");
|
||||
Regex re = new Regex ("\r\n|\r|\n");
|
||||
text = re.Replace (text, "_br_");
|
||||
|
||||
re = new Regex ("<\\s*(\\/?)\\s*([\\s\\S]*?)\\s*(\\/?)\\s*>");
|
||||
text = re.Replace (text,"{blue:<$1}{maroon:$2}{blue:$3>}");
|
||||
|
||||
re = new Regex ("\\{(\\w*):([\\s\\S]*?)\\}");
|
||||
text = re.Replace (text,"<span style='color:$1'>$2</span>");
|
||||
|
||||
re = new Regex ("\"(.*?)\"");
|
||||
text = re.Replace (text,"\"<span style='color:purple'>$1</span>\"");
|
||||
|
||||
|
||||
text = text.Replace ("\t", " ");
|
||||
text = text.Replace ("_br_", "<br>");
|
||||
return text;
|
||||
}
|
||||
|
||||
string ColorizeCs (string text)
|
||||
{
|
||||
text = text.Replace (" ", " ");
|
||||
|
||||
text = text.Replace ("<", "<");
|
||||
text = text.Replace (">", ">");
|
||||
|
||||
Regex re = new Regex ("\"((((?!\").)|\\\")*?)\"");
|
||||
text = re.Replace (text,"<span style='color:purple'>\"$1\"</span>");
|
||||
|
||||
re = new Regex ("//(((.(?!\"</span>))|\"(((?!\").)*)\"</span>)*)(\r|\n|\r\n)");
|
||||
text = re.Replace (text,"<span style='color:green'>//$1</span><br/>");
|
||||
|
||||
re = new Regex (keywords_cs);
|
||||
text = re.Replace (text,"<span style='color:blue'>$1</span>");
|
||||
|
||||
text = text.Replace ("\t"," ");
|
||||
text = text.Replace ("\n","<br/>");
|
||||
|
||||
return text;
|
||||
}
|
||||
|
||||
string ColorizeVb (string text)
|
||||
{
|
||||
text = text.Replace (" ", " ");
|
||||
|
||||
/* Regex re = new Regex ("\"((((?!\").)|\\\")*?)\"");
|
||||
text = re.Replace (text,"<span style='color:purple'>\"$1\"</span>");
|
||||
|
||||
re = new Regex ("'(((.(?!\"\\<\\/span\\>))|\"(((?!\").)*)\"\\<\\/span\\>)*)(\r|\n|\r\n)");
|
||||
text = re.Replace (text,"<span style='color:green'>//$1</span><br/>");
|
||||
|
||||
re = new Regex (keywords_vb);
|
||||
text = re.Replace (text,"<span style='color:blue'>$1</span>");
|
||||
*/
|
||||
text = text.Replace ("\t"," ");
|
||||
text = text.Replace ("\n","<br/>");
|
||||
return text;
|
||||
}
|
||||
|
||||
//
|
||||
// Helper methods and classes
|
||||
//
|
||||
|
||||
string GetDataContext ()
|
||||
{
|
||||
return "op=" + CurrentOperationName + "&bnd=" + CurrentOperationBinding + "&";
|
||||
}
|
||||
|
||||
string GetOptionSel (string v1, string v2)
|
||||
{
|
||||
string op = "<option ";
|
||||
if (v1 == v2) op += "selected ";
|
||||
return op + "value='" + v1 + "'>";
|
||||
}
|
||||
|
||||
string WrapText (string text, int maxChars)
|
||||
{
|
||||
text = text.Replace(" />","/>");
|
||||
|
||||
string linspace = null;
|
||||
int lincount = 0;
|
||||
int breakpos = 0;
|
||||
int linstart = 0;
|
||||
bool inquotes = false;
|
||||
char lastc = ' ';
|
||||
string sublineIndent = "";
|
||||
System.Text.StringBuilder sb = new System.Text.StringBuilder ();
|
||||
for (int n=0; n<text.Length; n++)
|
||||
{
|
||||
char c = text [n];
|
||||
|
||||
if (c=='\r' || c=='\n' || n==text.Length-1)
|
||||
{
|
||||
sb.Append (linspace + sublineIndent + text.Substring (linstart, n-linstart+1));
|
||||
linspace = null;
|
||||
lincount = 0;
|
||||
linstart = n+1;
|
||||
breakpos = linstart;
|
||||
sublineIndent = "";
|
||||
lastc = c;
|
||||
continue;
|
||||
}
|
||||
|
||||
if (lastc==',' || lastc=='(')
|
||||
{
|
||||
if (!inquotes) breakpos = n;
|
||||
}
|
||||
|
||||
if (lincount > maxChars && breakpos >= linstart)
|
||||
{
|
||||
if (linspace != null)
|
||||
sb.Append (linspace + sublineIndent);
|
||||
sb.Append (text.Substring (linstart, breakpos-linstart));
|
||||
sb.Append ("\n");
|
||||
sublineIndent = " ";
|
||||
lincount = linspace.Length + sublineIndent.Length + (n-breakpos);
|
||||
linstart = breakpos;
|
||||
}
|
||||
|
||||
if (c==' ' || c=='\t')
|
||||
{
|
||||
if (!inquotes)
|
||||
breakpos = n;
|
||||
}
|
||||
else if (c=='"')
|
||||
{
|
||||
inquotes = !inquotes;
|
||||
}
|
||||
else
|
||||
if (linspace == null) {
|
||||
linspace = text.Substring (linstart, n-linstart);
|
||||
linstart = n;
|
||||
}
|
||||
|
||||
lincount++;
|
||||
lastc = c;
|
||||
}
|
||||
return sb.ToString ();
|
||||
}
|
||||
|
||||
class Parameter
|
||||
{
|
||||
string name;
|
||||
string type;
|
||||
string description;
|
||||
|
||||
public string Name { get { return name; } set { name = value; } }
|
||||
public string Type { get { return type; } set { type = value; } }
|
||||
public string Description { get { return description; } set { description = value; } }
|
||||
}
|
||||
|
||||
</script>
|
||||
|
||||
<head>
|
||||
<title><%=WebServiceName%> Web Service</title>
|
||||
<style type="text/css">
|
||||
BODY { font-family: Arial; margin-left: 20px; margin-top: 20px; font-size: x-small}
|
||||
TABLE { font-size: x-small }
|
||||
.title { color:dimgray; font-family: Arial; font-size:20pt; font-weight:900}
|
||||
.operationTitle { color:dimgray; font-family: Arial; font-size:15pt; font-weight:900}
|
||||
.method { font-size: x-small }
|
||||
.bindingLabel { font-size: x-small; font-weight:bold; color:darkgray; line-height:8pt; display:block; margin-bottom:3px }
|
||||
.label { font-size: small; font-weight:bold; color:darkgray }
|
||||
.paramTable { font-size: x-small }
|
||||
.paramTable TR { background-color: gainsboro }
|
||||
.paramFormTable { font-size: x-small; padding: 10px; background-color: gainsboro }
|
||||
.paramFormTable TR { background-color: gainsboro }
|
||||
.paramInput { border: solid 1px gray }
|
||||
.button {border: solid 1px gray }
|
||||
.smallSeparator { height:3px; overflow:hidden }
|
||||
.panel { background-color:whitesmoke; border: solid 1px silver; border-top: solid 1px silver }
|
||||
.codePanel { background-color: white; font-size:x-small; padding:7px; border:solid 1px silver}
|
||||
.code-xml { font-size:10pt; font-family:courier }
|
||||
.code-cs { font-size:10pt; font-family:courier }
|
||||
.code-vb { font-size:10pt; font-family:courier }
|
||||
.tabLabelOn { font-weight:bold }
|
||||
.tabLabelOff {color: darkgray }
|
||||
A:link { color: black; }
|
||||
A:visited { color: black; }
|
||||
A:active { color: black; }
|
||||
A:hover { color: blue }
|
||||
</style>
|
||||
|
||||
<script>
|
||||
function clearForm ()
|
||||
{
|
||||
document.getElementById("testFormResult").style.display="none";
|
||||
}
|
||||
</script>
|
||||
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<div class="title" style="margin-left:20px">
|
||||
<span class="label">Web Service</span><br>
|
||||
<%=WebServiceName%>
|
||||
</div>
|
||||
|
||||
<!--
|
||||
**********************************************************
|
||||
Left panel
|
||||
-->
|
||||
|
||||
<table border="0" width="100%" cellpadding="15px" cellspacing="15px">
|
||||
<tr valign="top"><td width="150px" class="panel">
|
||||
<div style="width:150px"></div>
|
||||
<a class="method" href='<%=PageName%>'>Overview</a><br>
|
||||
<div class="smallSeparator"></div>
|
||||
<a class="method" href='<%=PageName + "?" + GetPageContext("wsdl")%>'>Service Description</a>
|
||||
<div class="smallSeparator"></div>
|
||||
<a class="method" href='<%=PageName + "?" + GetPageContext("proxy")%>'>Client proxy</a>
|
||||
<br><br>
|
||||
<asp:repeater id="BindingsRepeater" runat=server>
|
||||
<itemtemplate name="itemtemplate">
|
||||
<span class="bindingLabel"><%#FormatBindingName(DataBinder.Eval(Container.DataItem, "Name").ToString())%></span>
|
||||
<asp:repeater id="OperationsRepeater" runat=server datasource='<%# ((Binding)Container.DataItem).Operations %>'>
|
||||
<itemtemplate>
|
||||
<a class="method" href="<%#PageName%>?<%#GetTabContext("op",null)%>op=<%#GetOpName(Container.DataItem)%>&bnd=<%#DataBinder.Eval(Container.DataItem, "Binding.Name")%>"><%#GetOpName(Container.DataItem)%></a>
|
||||
<div class="smallSeparator"></div>
|
||||
</itemtemplate>
|
||||
</asp:repeater>
|
||||
<br>
|
||||
</itemtemplate>
|
||||
</asp:repeater>
|
||||
|
||||
</td><td class="panel">
|
||||
|
||||
<% if (CurrentPage == "main") {%>
|
||||
|
||||
<!--
|
||||
**********************************************************
|
||||
Web service overview
|
||||
-->
|
||||
|
||||
<p class="label">Web Service Overview</p>
|
||||
<%#WebServiceDescription%>
|
||||
|
||||
<%} if (CurrentPage == "op") {%>
|
||||
|
||||
<!--
|
||||
**********************************************************
|
||||
Operation description
|
||||
-->
|
||||
|
||||
<span class="operationTitle"><%#CurrentOperationName%></span>
|
||||
<br><br>
|
||||
<% WriteTabs (); %>
|
||||
<br><br><br>
|
||||
|
||||
<% if (CurrentTab == "main") { %>
|
||||
<span class="label">Input Parameters</span>
|
||||
<div class="smallSeparator"></div>
|
||||
<% if (InParams.Count == 0) { %>
|
||||
No input parameters<br>
|
||||
<% } else { %>
|
||||
<table class="paramTable" cellspacing="1" cellpadding="5">
|
||||
<asp:repeater id="InputParamsRepeater" runat=server>
|
||||
<itemtemplate>
|
||||
<tr>
|
||||
<td width="150"><%#DataBinder.Eval(Container.DataItem, "Name")%></td>
|
||||
<td width="150"><%#DataBinder.Eval(Container.DataItem, "Type")%></td>
|
||||
</tr>
|
||||
</itemtemplate>
|
||||
</asp:repeater>
|
||||
</table>
|
||||
<% } %>
|
||||
<br>
|
||||
|
||||
<% if (OutParams.Count > 0) { %>
|
||||
<span class="label">Output Parameters</span>
|
||||
<div class="smallSeparator"></div>
|
||||
<table class="paramTable" cellspacing="1" cellpadding="5">
|
||||
<asp:repeater id="OutputParamsRepeater" runat=server>
|
||||
<itemtemplate>
|
||||
<tr>
|
||||
<td width="150"><%#DataBinder.Eval(Container.DataItem, "Name")%></td>
|
||||
<td width="150"><%#DataBinder.Eval(Container.DataItem, "Type")%></td>
|
||||
</tr>
|
||||
</itemtemplate>
|
||||
</asp:repeater>
|
||||
</table>
|
||||
<br>
|
||||
<% } %>
|
||||
|
||||
<span class="label">Remarks</span>
|
||||
<div class="smallSeparator"></div>
|
||||
<%#OperationDocumentation%>
|
||||
<br><br>
|
||||
<span class="label">Technical information</span>
|
||||
<div class="smallSeparator"></div>
|
||||
Format: <%#CurrentOperationFormat%>
|
||||
<br>Supported protocols: <%#CurrentOperationProtocols%>
|
||||
<% } %>
|
||||
|
||||
<% if (CurrentTab == "test") {
|
||||
if (CurrentOperationSupportsTest) {%>
|
||||
Enter values for the parameters and click the 'Invoke' button to test this method:<br><br>
|
||||
<form action="<%#PageName%>" method="GET">
|
||||
<input type="hidden" name="page" value="<%#CurrentPage%>">
|
||||
<input type="hidden" name="tab" value="<%#CurrentTab%>">
|
||||
<input type="hidden" name="op" value="<%#CurrentOperationName%>">
|
||||
<input type="hidden" name="bnd" value="<%#CurrentOperationBinding%>">
|
||||
<input type="hidden" name="ext" value="testform">
|
||||
<table class="paramFormTable" cellspacing="0" cellpadding="3">
|
||||
<asp:repeater id="InputFormParamsRepeater" runat=server>
|
||||
<itemtemplate>
|
||||
<tr>
|
||||
<td><%#DataBinder.Eval(Container.DataItem, "Name")%>: </td>
|
||||
<td width="150"><input class="paramInput" type="text" size="20" name="<%#DataBinder.Eval(Container.DataItem, "Name")%>"></td>
|
||||
</tr>
|
||||
</itemtemplate>
|
||||
</asp:repeater>
|
||||
<tr><td></td><td><input class="button" type="submit" value="Invoke"> <input class="button" type="button" onclick="clearForm()" value="Clear"></td></tr>
|
||||
</table>
|
||||
</form>
|
||||
<div id="testFormResult" style="display:<%# (HasFormResult?"block":"none") %>">
|
||||
The web service returned the following result:<br/><br/>
|
||||
<div class="codePanel"><%#GetTestResult()%></div>
|
||||
</div>
|
||||
<% } else {%>
|
||||
The test form is not available for this operation because it has parameters with a complex structure.
|
||||
<% } %>
|
||||
<% } %>
|
||||
<% if (CurrentTab == "msg") { %>
|
||||
TODO
|
||||
<% } %>
|
||||
<%}%>
|
||||
|
||||
<% if (CurrentPage == "proxy") {%>
|
||||
<!--
|
||||
**********************************************************
|
||||
Client Proxy
|
||||
-->
|
||||
<form action="<%#PageName%>" name="langForm" method="GET">
|
||||
Select the language for which you want to generate a proxy
|
||||
<input type="hidden" name="page" value="<%#CurrentPage%>">
|
||||
<SELECT name="lang" onchange="langForm.submit()">
|
||||
<%#GetOptionSel("cs",CurrentLanguage)%>C#</option>
|
||||
<%#GetOptionSel("vb",CurrentLanguage)%>Visual Basic</option>
|
||||
</SELECT>
|
||||
|
||||
</form>
|
||||
<br>
|
||||
<span class="label"><%#CurrentProxytName%></span>
|
||||
<a href="<%#PageName + "?code=" + CurrentLanguage%>">Download</a>
|
||||
<br><br>
|
||||
<div class="codePanel">
|
||||
<div class="code-<%#CurrentLanguage%>"><%#GetProxyCode ()%></div>
|
||||
</div>
|
||||
<%}%>
|
||||
|
||||
<% if (CurrentPage == "wsdl") {%>
|
||||
<!--
|
||||
**********************************************************
|
||||
Service description
|
||||
-->
|
||||
<% if (descriptions.Count > 1 || schemas.Count > 1) {%>
|
||||
The description of this web service is composed by several documents. Click on the document you want to see:
|
||||
|
||||
<ul>
|
||||
<%
|
||||
for (int n=0; n<descriptions.Count; n++)
|
||||
Response.Write ("<li><a href='" + PageName + "?" + GetPageContext(null) + "doctype=wsdl&docind=" + n + "'>WSDL document " + descriptions[n].TargetNamespace + "</a></li>");
|
||||
for (int n=0; n<schemas.Count; n++)
|
||||
Response.Write ("<li><a href='" + PageName + "?" + GetPageContext(null) + "doctype=schema&docind=" + n + "'>Xml Schema " + schemas[n].TargetNamespace + "</a></li>");
|
||||
%>
|
||||
</ul>
|
||||
|
||||
<%} else {%>
|
||||
<%}%>
|
||||
<br>
|
||||
<span class="label"><%#CurrentDocumentName%></span>
|
||||
<a href="<%=PageName + "?" + CurrentDocType + "=" + CurrentDocInd %>">Download</a>
|
||||
<br><br>
|
||||
<div class="codePanel">
|
||||
<div class="code-xml"><%#GenerateDocument ()%></div>
|
||||
</div>
|
||||
|
||||
<%}%>
|
||||
|
||||
<br><br><br><br><br><br><br><br><br><br><br><br><br><br><br>
|
||||
</td>
|
||||
<td withd="20px"></td>
|
||||
</tr>
|
||||
|
||||
</table>
|
||||
</body>
|
||||
</html>
|
||||
+7
-2
@@ -1,6 +1,11 @@
|
||||
monodir = $(sysconfdir)/mono
|
||||
|
||||
EXTRA_DIST = config.in machine.config DefaultWsdlHelpGenerator.aspx
|
||||
EXTRA_DIST = config.in machine.config
|
||||
|
||||
mono_DATA = config machine.config DefaultWsdlHelpGenerator.aspx
|
||||
mono_DATA = config machine.config
|
||||
|
||||
DISTCLEANFILES = config
|
||||
|
||||
config: config.in Makefile
|
||||
sed -e 's^\@LIBC\@^libc.so.6^g' < $(srcdir)/config.in > config.tmp \
|
||||
&& mv config.tmp config
|
||||
@@ -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" />
|
||||
@@ -15,6 +14,4 @@
|
||||
<dllmap dll="libgtk-win32-2.0-0.dll" target="libgtk-x11-2.0.so" />
|
||||
<dllmap dll="libglade-2.0-0.dll" target="libglade-2.0.so" />
|
||||
<dllmap dll="oci" target="clntsh" />
|
||||
<dllmap dll="gtkhtml-3.0" target="libgtkhtml-3.0.so.2" />
|
||||
<dllmap dll="db2cli" target="libdb2_36.so"/>
|
||||
</configuration>
|
||||
+7
-123
@@ -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,71 +21,21 @@
|
||||
type="System.Web.Configuration.GlobalizationConfigurationHandler, System.Web" />
|
||||
<section name="sessionState"
|
||||
type="System.Web.SessionState.SessionStateSectionHandler, System.Web" />
|
||||
<section name="webServices"
|
||||
type="System.Web.Services.Configuration.WebServicesConfigurationSectionHandler, System.Web.Services" />
|
||||
<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" />
|
||||
</sectionGroup>
|
||||
<sectionGroup name="system.net">
|
||||
<section name="settings"
|
||||
type="System.Net.Configuration.NetConfigurationHandler, System" />
|
||||
<section name="connectionManagement"
|
||||
type="System.Net.Configuration.ConnectionManagementHandler, System" />
|
||||
<section name="authenticationModules"
|
||||
type="System.Net.Configuration.NetAuthenticationModuleHandler, System" />
|
||||
<section name="defaultProxy"
|
||||
type="System.Net.Configuration.DefaultProxyHandler, System" />
|
||||
<section name="webRequestModules"
|
||||
type="System.Net.Configuration.WebRequestModuleHandler, System" />
|
||||
</sectionGroup>
|
||||
<section name="system.drawing" type="System.Configuration.NameValueSectionHandler" />
|
||||
</configSections>
|
||||
<system.net>
|
||||
<connectionManagement>
|
||||
<add address="*" maxconnection="2" />
|
||||
</connectionManagement>
|
||||
<authenticationModules>
|
||||
<add type="System.Net.BasicClient" />
|
||||
</authenticationModules>
|
||||
<defaultProxy>
|
||||
<proxy />
|
||||
<!-- bypassonlocal and proxyaddress are ok -->
|
||||
<!-- usessystemdefault is not supported -->
|
||||
</defaultProxy>
|
||||
<webRequestModules>
|
||||
<add prefix="http" type="System.Net.HttpRequestCreator, System" />
|
||||
<add prefix="https" type="System.Net.HttpRequestCreator, System" />
|
||||
<add prefix="file" type="System.Net.FileWebRequestCreator, System" />
|
||||
</webRequestModules>
|
||||
<settings>
|
||||
<ipv6 enabled="false"/>
|
||||
</settings>
|
||||
</system.net>
|
||||
<system.web>
|
||||
<httpHandlers>
|
||||
<add verb="*" path="*.aspx" type="System.Web.UI.PageHandlerFactory, System.Web" />
|
||||
<add verb="*" path="*.asmx" validate="false"
|
||||
type="System.Web.Services.Protocols.WebServiceHandlerFactory, System.Web.Services" />
|
||||
<add verb="*" path="*.ashx" type="System.Web.UI.SimpleHandlerFactory, System.Web" />
|
||||
<add verb="GET" path="WebResource.axd" type="System.Web.Handlers.AssemblyResourceLoader, System.Web" />
|
||||
<add verb="*" path="*.asax" type="System.Web.HttpForbiddenHandler, System.Web" />
|
||||
<add verb="*" path="*.ascx" type="System.Web.HttpForbiddenHandler, System.Web" />
|
||||
<add verb="*" path="*.config" type="System.Web.HttpForbiddenHandler, System.Web" />
|
||||
<add verb="*" path="*.cs" type="System.Web.HttpForbiddenHandler, System.Web" />
|
||||
<add verb="*" path="*.rem" type="System.Runtime.Remoting.Channels.Http.HttpRemotingHandlerFactory, System.Runtime.Remoting" validate="false" />
|
||||
<add verb="*" path="*.soap" type="System.Runtime.Remoting.Channels.Http.HttpRemotingHandlerFactory, System.Runtime.Remoting" validate="false" />
|
||||
<add verb="GET,HEAD" path="*" type="System.Web.StaticFileHandler, System.Web" />
|
||||
<add verb="*" path="*" type="System.Web.HttpMethodNotAllowedHandler, System.Web" />
|
||||
</httpHandlers>
|
||||
<httpModules>
|
||||
<add name="FormsAuthentication" type="System.Web.Security.FormsAuthenticationModule, System.Web" />
|
||||
<add name="UrlAuthorization" type="System.Web.Security.UrlAuthorizationModule, System.Web" />
|
||||
<add name="Session" type="System.Web.SessionState.SessionStateModule, System.Web" />
|
||||
<add name="OutputCache" type="System.Web.Caching.OutputCacheModule, System.Web" />
|
||||
<add name="SessionStateModule" type="System.Web.SessionState.SessionStateModule, System.Web" />
|
||||
</httpModules>
|
||||
<authentication mode="Forms">
|
||||
<forms name=".MONOAUTH" loginUrl="login.aspx" protection="All" timeout="30" path="/">
|
||||
@@ -95,79 +45,16 @@
|
||||
</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" />
|
||||
-->
|
||||
<sessionState mode="InProc" />
|
||||
<webServices>
|
||||
<protocols>
|
||||
<add name="HttpSoap"/>
|
||||
<add name="HttpPost"/>
|
||||
<add name="HttpGet"/>
|
||||
<add name="Documentation"/>
|
||||
</protocols>
|
||||
<wsdlHelpGenerator href="DefaultWsdlHelpGenerator.aspx" />
|
||||
</webServices>
|
||||
<webControls clientScriptsLocation="/web_scripts" />
|
||||
<compilation debug="false" defaultLanguage="c#">
|
||||
<compilers>
|
||||
<compiler language="cs;c#;csharp" extension=".cs" warningLevel="1" compilerOptions=""
|
||||
type="Microsoft.CSharp.CSharpCodeProvider, System" />
|
||||
<compiler language="vb;vbs;visualbasic;vbscript" extension=".vb"
|
||||
warningLevel="1" compilerOptions=""
|
||||
type="Microsoft.VisualBasic.VBCodeProvider, System" />
|
||||
</compilers>
|
||||
<assemblies>
|
||||
<!--<add assembly="mscorlib" /> -->
|
||||
<add assembly="System" />
|
||||
<add assembly="System.Xml" />
|
||||
<add assembly="System.Data" />
|
||||
<add assembly="System.Web" />
|
||||
<add assembly="System.Web.Services" />
|
||||
<add assembly="System.Drawing" />
|
||||
<add assembly="*" /> <!-- Add assemblies in bin directory -->
|
||||
</assemblies>
|
||||
</compilation>
|
||||
<httpRuntime executionTimeout="90"
|
||||
maxRequestLength="4096"
|
||||
useFullyQualifiedRedirectUrl="false"
|
||||
minFreeThreads="8"
|
||||
minLocalRequestFreeThreads="4"
|
||||
appRequestQueueLimit="100" />
|
||||
</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" /> -->
|
||||
@@ -176,8 +63,5 @@
|
||||
<system.diagnostics>
|
||||
<trace autoflush="false" indentsize="4" />
|
||||
</system.diagnostics>
|
||||
<system.drawing>
|
||||
</system.drawing>
|
||||
</configuration>
|
||||
|
||||
|
||||
+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:
|
||||
|
||||
|
||||
+99
-38
@@ -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>
|
||||
@@ -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>
|
||||
|
||||
+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
|
||||
|
||||
|
||||
+61
-51
@@ -7,81 +7,56 @@
|
||||
* Web Services (the SOAP-based rpc system).
|
||||
</ul>
|
||||
|
||||
Both are functional at this point, and applications like
|
||||
"IBuySpy" run with Mono.
|
||||
There is work underway for both systems. The Web Forms
|
||||
support is more advanced at this point, and various ".aspx"
|
||||
programs can be run using the Mono runtime, including IBuySpy.
|
||||
|
||||
ASP.NET works either embedded into
|
||||
our XSP server test server or the mod_mono Apache module.
|
||||
|
||||
We are now working on bug fixing and adding missing features
|
||||
We are now working bug fixing and adding missing features
|
||||
after making the whole pipeline compatible with MS.
|
||||
|
||||
Tim started work on the Web Services. After that, Lluis is in
|
||||
charge and has been working hard on them as part of our
|
||||
<a href="http://www.ximian.com/about_us/press_center/press_releases/index.html?pr=sourcegear">SourceGear</a> contract.
|
||||
|
||||
Web services are now supported and there are some samples in the
|
||||
XSP set of tests.
|
||||
Tim started work on the Web Services. Although we have a
|
||||
SoapFormatter as part of the remoting infrastructure already
|
||||
(contributed by Jesus), most people will be using the ASP.NET
|
||||
Web Services support. Work for the supporting class libraries
|
||||
just started recently.
|
||||
|
||||
** Hosting
|
||||
The major missing element is a complete XmlSerializer.
|
||||
|
||||
ASP.NET provides a hosting interface. Today we ship support
|
||||
for two different hosting mechanisms:
|
||||
<ul>
|
||||
* <a href="#xsp">XSP</a>: A light-weight C# web server.
|
||||
** HttpRuntime
|
||||
|
||||
* <a href="#mod_mono">mod_mono</a>: An apache module
|
||||
that can host the Mono runtime and the ASP.NET runtime
|
||||
</ul>
|
||||
Patrik has authored most of the HttpRuntime support (both on
|
||||
the System.Web and on the foundation).
|
||||
|
||||
<a name="xsp">
|
||||
** XSP
|
||||
|
||||
XSP is a simple web server written in C# that can be used to
|
||||
run your ASP.NET applications. The code is available from our
|
||||
<a href="download.html">download page</a> or from the <a
|
||||
href="anoncvs.html">Anonymous CVS</a> repository (module name:
|
||||
xsp)/.
|
||||
|
||||
This is where initial development of the .aspx/.ascx/.asax
|
||||
compiler to C# took place. That compiler is now integrated in
|
||||
System.Web classes mostly under System.Web.Compilation
|
||||
namespace. We added a new web server that works with mono and
|
||||
MS runtime and is being used to debug our classes. It resides
|
||||
in xsp/server.
|
||||
This is where initial development of the .aspx/.ascx/.asax compiler
|
||||
to C# took place. That compiler is now integrated in System.Web classes
|
||||
mostly under System.Web.Compilation namespace.
|
||||
|
||||
A couple of classes of this new server can be reused/extended
|
||||
to make an apache module/cgi using mono (MonoWorkerRequest and
|
||||
MonoApplicationHost). This server also uses a couple of
|
||||
plugins distributed with Mono to support gzip HTTP transfers.
|
||||
We added a new web server that works with mono and MS runtime and is
|
||||
being used to debug our classes. It resides in xsp/server. A couple of
|
||||
classes of this new server can be reused/extended to make an apache
|
||||
module/cgi using mono (MonoWorkerRequest and MonoApplicationHost).
|
||||
|
||||
There is also a set of .aspx pages to test the server along with
|
||||
a few user controls under xsp/test.
|
||||
|
||||
You can check it out from CVS and run 'make install' to test it.
|
||||
|
||||
<a name="mod_mono">
|
||||
* mod_mono
|
||||
|
||||
This Apache module is available from our <a
|
||||
href="download.html">download page</a>. The <a href="anoncvs.html">
|
||||
cvs</a> module name is mod_mono. It works with both 1.3 and 2.0
|
||||
versions of the <a href="http://httpd.apache.org">apache server</a>.
|
||||
|
||||
It allows apache to serve ASP.NET pages.
|
||||
|
||||
Work is underway to improve it.
|
||||
|
||||
** Controls
|
||||
|
||||
A lot of work has been put in the various classes that
|
||||
implement the controls (UI.HtmlControls and UI.WebControls).
|
||||
They have been coded mostly in the dark, and without being
|
||||
implement the controls (UI.HtmlControls and UI.WebControls),
|
||||
but they have been coded mostly in the dark, and without being
|
||||
able to test them in real life: Gaurav and Leen worked very
|
||||
hard on this namespace. After that, we keep fixing bugs on
|
||||
them.
|
||||
hard on this namespace.
|
||||
|
||||
We can now render all HtmlControls and all WebControls.
|
||||
We can now render all HtmlControls and almost all WebControls.
|
||||
DataGrid and DataList controls are being finished by Gaurav.
|
||||
Xml control needs some work on System.Xml related to XSL.
|
||||
|
||||
Help in making the controls better is appreciated.
|
||||
|
||||
@@ -90,6 +65,41 @@
|
||||
We want to encourage developers to create open source controls
|
||||
that can be used both on Mono's ASP.NET and Microsoft's ASP.NET.
|
||||
|
||||
* Web Forms: The pieces (historical)
|
||||
|
||||
There are a couple of components to the puzzle:
|
||||
|
||||
<ul>
|
||||
* .aspx page parser (converts .aspx to C# code).
|
||||
|
||||
* System.Web.HttpRuntime support.
|
||||
|
||||
* Web controls (System.Web.UI.HtmlControls and
|
||||
System.Web.UI.WebControls).
|
||||
|
||||
* Underlying infrastructure for the controls (System.Web.UI).
|
||||
|
||||
* HttpRuntime.ProcessRequest is the core of the ASP.NET
|
||||
implementation.
|
||||
</ul>
|
||||
|
||||
|
||||
Gonzalo has been working on an ASP.NET parser that takes .aspx
|
||||
files and generated the code required to run them (the code lives in
|
||||
module `xsp' along with a little web server for testing).
|
||||
|
||||
Most of the runtime support was written by Patrik Torstensson
|
||||
(now at Intel). This was interesting, because in order to implement
|
||||
some of its features, Patrik had to go into the runtime/JIT engine and
|
||||
he spent a few weeks doing work there.
|
||||
|
||||
The classes for running ASP.NET are being actively written.
|
||||
Gaurav, Leen and Patrik worked in the core of the classes
|
||||
required to run ASP.NET web application as well as a small
|
||||
embeddable web server.
|
||||
|
||||
Duncan got our System.Web assembly to compile.
|
||||
|
||||
** How to Help
|
||||
|
||||
Testing and fixing HtmlControls, WebControls and validators is an
|
||||
|
||||
@@ -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/miguel2.rss"><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>
|
||||
|
||||
@@ -8,12 +8,6 @@
|
||||
|
||||
A Programmer's Introduction to C# - Second Edition: Eric Gunnerson
|
||||
|
||||
* .NET Framework
|
||||
|
||||
Avery good techincal book about .NET is Don Box's <a
|
||||
href="http://service.bfast.com/bfast/click?bfmid=2181&sourceid=39391960&isbn=0201734117">Essential
|
||||
.NET</a>
|
||||
|
||||
* Remoting
|
||||
|
||||
<a href="http://www.dotnetremoting.cc/book/AdvancedDotNetRemoting.asp">
|
||||
|
||||
@@ -1,69 +0,0 @@
|
||||
* Bug reporting
|
||||
|
||||
To report bugs you need to create a <a
|
||||
href="http://bugzilla.ximian.com/createaccount.cgi">Bugzilla
|
||||
Account</a>.
|
||||
|
||||
Here are some convenient shortcuts to browse or add bug reports.
|
||||
|
||||
<ul>
|
||||
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FClass+Libraries&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&newqueryname=&form_name=query&order=bugs.priority%2C%20bugs.bug_id">[Query]</> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FClass%20Libraries">[Add]</a> Class Libraries
|
||||
|
||||
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FAssembler&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FAssembler">[Add]</a> IL Assembler.
|
||||
|
||||
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FMCS&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FMCS">[Add]</a> C# Compiler.
|
||||
|
||||
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FRuntime&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FRuntime">[Add]</a> Runtime
|
||||
|
||||
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FDoctools&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FDoctools">[Add]</a> Documentation system.
|
||||
|
||||
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=gtk%23&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=gtk%23">[Add]</a> Gtk#
|
||||
|
||||
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FDebugger&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FDebugger">[Add]</a> Debugger.
|
||||
|
||||
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FClass+Libraries&product=Mono%2FMCS&product=Mono%2FRuntime&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&order=%27Importance%27&form_name=query">[Query]</a> All core components.
|
||||
</ul>
|
||||
|
||||
<a name="goodbugreport"/>
|
||||
** How to make good bug reports
|
||||
|
||||
<ol>
|
||||
* Submit a test case, the smaller it is, the better
|
||||
|
||||
* Use <a href="http://bugzilla.ximian.com">
|
||||
http://bugzilla.ximian.com</a> to report the bug.
|
||||
|
||||
<p>In <b>addition</b> to bugzilla, posting to the list is
|
||||
fine if the bug merits larger exposure or design
|
||||
discussions to solve; posting to the list twice or more
|
||||
is just a way to annoy people and make them waste time,
|
||||
specially when you start a new thread about it.
|
||||
|
||||
* If the test involves libraries or assemblies that are
|
||||
not part of mono, add info about where to download all
|
||||
the dependencies, and how to compile/install them.
|
||||
|
||||
* If compiling the test case requires more than:
|
||||
<pre> mcs test.cs </pre>
|
||||
provide the <b>full command line</b> you used to compile
|
||||
the test.
|
||||
|
||||
* If running the test requires more than:
|
||||
<pre> mono test.exe </pre>
|
||||
provide the <b>full command line</b> needed to replicate
|
||||
the bug.
|
||||
|
||||
* Provide info about the version of the software you're
|
||||
using (both mono and the operating system or relevant
|
||||
libraries).
|
||||
|
||||
* Provide the output you expect the test case to produce.
|
||||
|
||||
* Provide the actual output <b>you</b> get from the test case.
|
||||
</ol>
|
||||
|
||||
A good bug report complies with at least 6 items from the list.
|
||||
If your bug report complies with 3 or less items, it is very
|
||||
poor and it means it will take much more time to fix (when it's
|
||||
not ignored).
|
||||
|
||||
@@ -1,54 +1,25 @@
|
||||
* CVS Access
|
||||
|
||||
Here we describe how one obtains commit access to the Mono CVS
|
||||
repository and the responsibilities that come with that access
|
||||
privilege.
|
||||
If you are an active Mono developer, you can get a CVS account
|
||||
that hosts the Mono source code. This web page contains
|
||||
details about how to use the CVS server as well as the
|
||||
policies to use it.
|
||||
|
||||
These only apply to the Mono CVS repository, and not to the <a
|
||||
href="http://forge.novell.com/modules/xfmod/community/?monocomm">Mono
|
||||
Community</a> repositories at Novell Forge.
|
||||
If you are not a developer, but want to track the development, please
|
||||
see the <a href="anoncvs.html">AnonCVS</a> instructions.
|
||||
|
||||
** What is CVS?
|
||||
|
||||
Briefly, CVS is a system tool used to store and maintain files and
|
||||
a history of their changes over time. The Mono source code and related
|
||||
files are kept on a CVS server at Ximian.
|
||||
|
||||
** What Access?
|
||||
|
||||
We mean "commit" access. This is the privilege to make permanent
|
||||
changes to the Mono source code and related files. You need an account
|
||||
created by the CVS server administrator in order to commit changes to
|
||||
the files on that server.
|
||||
|
||||
** How Does One Obtain Access?
|
||||
|
||||
Any active Mono developer can get a CVS account. Normally one is
|
||||
considered an 'active' developer after sending several patches to the
|
||||
mailing lists and/or bugzilla for review.
|
||||
|
||||
If you are not a developer, but want to access the latest sources,
|
||||
please see the <a href="anoncvs.html">AnonCVS</a>
|
||||
instructions. If you are not a direct contributor to Mono,
|
||||
but want to host your .NET or Mono-based project, you can use
|
||||
<a href="forge.html">Novell Forge</a>.
|
||||
|
||||
|
||||
If you feel you are ready for a CVS account send an e-mail to
|
||||
<a href="mailto:[email protected]">miguel</a> with your public OpenSSH
|
||||
key for this purpose. Please specify if the key was generated with SSH
|
||||
version 1 or version 2. Detailed instructions are below.
|
||||
Send an e-mail to miguel with your public OpenSSH key for this
|
||||
purpose. Please specify if the key was generated with SSH version 1
|
||||
or version 2.
|
||||
|
||||
* Policies
|
||||
|
||||
It is necessary that everyone with CVS commit access respect and
|
||||
adhere to the following rules. If you ask for and are granted CVS
|
||||
access, you are agreeing to follow these policies.
|
||||
|
||||
Here are some policies about the use of the Mono CVS server.
|
||||
|
||||
** Code License
|
||||
|
||||
If you are about to commit code to a module, the code that is
|
||||
being committed should be released under the same license as
|
||||
being commited should be released under the same license as
|
||||
the code that the module has.
|
||||
|
||||
Check the license if you are unsure, but it is basically:
|
||||
@@ -57,105 +28,25 @@
|
||||
If in doubt, check with the maintainers of the module, or send
|
||||
mail to [email protected].
|
||||
|
||||
** Changing code
|
||||
** Commiting code.
|
||||
|
||||
Even if you have CVS commit access, that doesn't mean you can change
|
||||
code at will in any directory or module. Directories and Namespaces
|
||||
have a sort of unofficial ownership. If you are not the owner of a
|
||||
piece of code and you want to make changes/fixes to it, there are two
|
||||
cases.
|
||||
1) The change is a typo fix or a one-liner build or trivial fix. In
|
||||
this case almost anyone can commit (always remembering to add the
|
||||
proper changelog entry to explain the change). We say "almost anyone",
|
||||
because changes to certain directories almost always should be reviewed
|
||||
first. Such as changes to core stuff: corlib/System, System.Collections,
|
||||
mini/, metadata/, System.IO.
|
||||
If you are the maintainer for a piece of code, feel free to
|
||||
commit code, and delegate the work to others.
|
||||
|
||||
2) The change is larger. In this case the patch *must* be sent to
|
||||
mono-devel-list for review by the owner of the code and by the other
|
||||
hackers. Always submit such patches to the list or bugzilla, although
|
||||
you may put the owner of the code in the CC header. Hackers come and go.
|
||||
Mailing a patch to only a personal address is a good way to get the
|
||||
patch forgotten and missed. Plus, getting the patches reviewed as well
|
||||
as reviewing them, is a good thing, so try to get used to it.
|
||||
Use ChangeLog entries so we can keep textual descriptions of
|
||||
your work, and use the contents of your ChangeLog file as the
|
||||
CVS commit message (ie, paste the contents of this into the
|
||||
editor buffer).
|
||||
|
||||
Note: If the patch is an addition of code and doesn't change any of the
|
||||
existing code, the rules are slightly relaxed: there is more freedom
|
||||
in committing such changes, if they don't interfere with the existing
|
||||
codebase.
|
||||
If you are making changes to someone else's code, please make
|
||||
sure you get in touch with the maintainer of that code before
|
||||
applying patches. You want to avoid commiting conflicting
|
||||
work to someone else's code.
|
||||
|
||||
** Owning Code
|
||||
|
||||
Now, how do you get to be the owner of a chunk of code? The answer is
|
||||
simple. You wrote the code, so you're the unofficial owner. There is
|
||||
also another way. After sending a few patches for the code, the
|
||||
owner (or the core developers of mono, if the owner somehow disappeared)
|
||||
trusts you and tells you you're free to commit without getting his
|
||||
review first.
|
||||
|
||||
|
||||
Here is a (partial) list of namespaces/directories with their owners:
|
||||
<ul>
|
||||
<li>Debugger module and debug code in mono: martin
|
||||
<li>mcs compiler: miguel, martin, ravi
|
||||
<li>Reflection/Reflection.Emit: lupus, zoltan
|
||||
<li>IO-layer: dick
|
||||
<li>mini: lupus, dietmar
|
||||
<li>test suite: nickd (though anyone should feel free to add test cases)
|
||||
<li>System.IO: dick, ville
|
||||
<li>security stuff: spouliot
|
||||
<li>ilasm: jackson
|
||||
<li>System.Web and related: gonzalo
|
||||
<li>System.Xml: eno, piers
|
||||
<li>Remoting: dietmar, lluis
|
||||
<li>interop/marshal: dietmar
|
||||
<li>threads: dick
|
||||
</ul>
|
||||
|
||||
If you are the owner of a piece of code, feel free to commit code, and
|
||||
delegate the work to others.
|
||||
|
||||
But, if you're not the owner of the code, committing a rewrite without
|
||||
getting a review first is not good cvsitizenship (especially when the
|
||||
rewrite claimed to fix bugs, but not a single regression test has been
|
||||
added to the suite).
|
||||
|
||||
** Commit Rules
|
||||
|
||||
Once you know you can commit a patch (because of the rules above) there
|
||||
are a few other small rules to follow:
|
||||
<ul>
|
||||
<li>Always add a changelog entry with a meaningful explanation
|
||||
<li>If you fix a bug, add a regression test for it in the regression
|
||||
suite
|
||||
<li>Don't commit unrelated changes together with a fix: do fine-grained
|
||||
commits
|
||||
<li>Always check what you're committing: make sure you're only committing
|
||||
what you need and make sure you don't change line endings and
|
||||
whitespace. Do a 'cvs diff -u' of the files you're going to commit and
|
||||
check the changes.
|
||||
<li>Don't do reformatting commits, unless you're the original author of
|
||||
the code
|
||||
<li>When fixing bugs, don't follow the documentation blindly, it may
|
||||
well be wrong. Test the behavior on the MS runtime or ask on the list
|
||||
for discussion if unsure. Don't be afraid of having your changes
|
||||
reviewed.
|
||||
<li>Never remove copyright notices from the code
|
||||
<li>Never remove licensing info from code
|
||||
<li>Never commit code you didn't write yourself or code that doesn't
|
||||
have a suitable license
|
||||
<li>Follow the style conventions
|
||||
<li>Keep an eye on performance considerations, especially for code in
|
||||
core classes, ask on the list for guidance
|
||||
<li>Do a regression test run and a bootstrapping build if making changes
|
||||
to core functionality before committing. Do not commit code that would
|
||||
break the compile, because that wastes everybody's time. Two things
|
||||
Please do not commit code that would break the compile to the
|
||||
CVS, because that normally wastes everybody's time. Two things
|
||||
are important in this step: trying to build your sources and making
|
||||
sure that you add all the new files before you do a commit.
|
||||
</ul>
|
||||
|
||||
Also, remember to pat yourself on the back after the commit, smile and
|
||||
think we're a step closer to a better free software world.
|
||||
|
||||
|
||||
* Using CVS.
|
||||
@@ -170,16 +61,14 @@
|
||||
ssh-keygen -t rsa
|
||||
</pre>
|
||||
|
||||
And mail <a href="mailto:[email protected]">miguel</a> the
|
||||
id_rsa.pub file.
|
||||
And mail me the id_rsa.pub file.
|
||||
|
||||
If you are using SSH version 1, run:
|
||||
<pre>
|
||||
ssh-keygen
|
||||
</pre>
|
||||
|
||||
And mail <a href="mailto:[email protected]">miguel</a> your
|
||||
identity.pub file.
|
||||
And mail me your identity.pub file.
|
||||
|
||||
If you are using SSH from SSH Communications Security (they offer
|
||||
a free SSH client for personal use), you have to use OpenSSH to
|
||||
@@ -192,8 +81,7 @@
|
||||
|
||||
where the file id_XXX.pub is your public key file,
|
||||
normally located under ~/.ssh/ or ~/.ssh2/.
|
||||
Send to <a href="mailto:[email protected]">miguel</a> the
|
||||
my_public_key.pub file.
|
||||
Send to miguel the my_public_key.pub file.
|
||||
|
||||
The *exact* format for this file must be:
|
||||
|
||||
@@ -235,7 +123,7 @@
|
||||
** Making patches
|
||||
|
||||
Usually you will want to make a patch to contribute, and let
|
||||
other people review it before committing it. To obtain such a
|
||||
other people review it before commiting it. To obtain such a
|
||||
"patch", you type:
|
||||
|
||||
<pre>
|
||||
@@ -244,25 +132,7 @@
|
||||
mail [email protected] < file.diff
|
||||
</pre>
|
||||
|
||||
** Committing your work
|
||||
|
||||
Once you get approval to commit to the CVS, or if you are
|
||||
committing code that you are the maintainer of, you will want
|
||||
to commit your code to CVS.
|
||||
|
||||
To do this, you have to "add" any new files that you created:
|
||||
|
||||
<pre>
|
||||
cvs add new-file.cs
|
||||
</pre>
|
||||
|
||||
And then commit your changes to the repository:
|
||||
|
||||
<pre>
|
||||
cvs commit file-1.cs file-2.cs
|
||||
</pre>
|
||||
|
||||
* Keeping track of changes.
|
||||
** Keeping track of changes.
|
||||
|
||||
We provide two e-mail based mechanisms to keep track of
|
||||
changes to the code base:
|
||||
@@ -281,6 +151,28 @@
|
||||
|
||||
We hope to offer LXR and Bonsai in the future as well.
|
||||
|
||||
** Commiting your work
|
||||
|
||||
Once you get approval to commit to the CVS, or if you are
|
||||
commiting code that you are the maintainer of, you will want
|
||||
to commit your code to CVS.
|
||||
|
||||
To do this, you have to "add" any new files that you created:
|
||||
|
||||
<pre>
|
||||
cvs add new-file.cs
|
||||
</pre>
|
||||
|
||||
And then commit your changes to the repository:
|
||||
|
||||
<pre>
|
||||
cvs commit file-1.cs file-2.cs
|
||||
</pre>
|
||||
|
||||
* The Mailing Lists
|
||||
|
||||
To keep track of the various development and changes to the
|
||||
CVS tree, you can subscribe to the [email protected].
|
||||
To subscribe, send an email message to
|
||||
[email protected] and in the body of the
|
||||
message put `subscribe'.
|
||||
@@ -293,3 +185,10 @@
|
||||
the <a
|
||||
href="mailto:[email protected]">[email protected]</a>
|
||||
to receive the patches as they are checked into CVS.
|
||||
|
||||
** Recommendations
|
||||
|
||||
To build the sources, most of the type trying the `make' command
|
||||
is enough. In some cases (the class libraries) we use nant, so
|
||||
you need to run nant manually.
|
||||
|
||||
+11
-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>
|
||||
|
||||
+4
-9
@@ -17,7 +17,6 @@
|
||||
|
||||
<ul>
|
||||
<li><a href="#monodoc">monodoc - A graphical documentation viewer.</a></li>
|
||||
|
||||
<li>xmllint: a tool used to validate a proper XML document.
|
||||
</ul>
|
||||
|
||||
@@ -28,15 +27,11 @@
|
||||
|
||||
*** <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
|
||||
|
||||
|
||||
+1
-49
@@ -16,8 +16,7 @@
|
||||
the source code for Mono, you can start tracking down the
|
||||
problem. Depending on how much time you have to devote to the
|
||||
problem you could: <a href="http://bugzilla.ximian.com">File a
|
||||
bug report</a> (read <a href="#goodbugreport">this</a>); track
|
||||
down the problem and provide a better
|
||||
bug report</a>; track down the problem and provide a better
|
||||
<a href="http://bugzilla.ximian.com">bug report</a>; fix the
|
||||
bug and provide a patch (you can <a
|
||||
href="mailto:[email protected]">post it</a> to the <a
|
||||
@@ -128,53 +127,6 @@
|
||||
|
||||
You can review the list of current bugs by going <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FClass+Libraries&product=Mono%2FMCS&product=Mono%2FRuntime&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&order=%27Importance%27&form_name=query">here</a>
|
||||
|
||||
Check our <a href="bugs.html">Bugs</a> that contains links to
|
||||
easily add a bug report, or to query the existing bugs.
|
||||
|
||||
<a name="goodbugreport"/>
|
||||
** How to make good bug reports
|
||||
|
||||
A mail from Paolo to mono-devel-list contained this check list:
|
||||
<ol>
|
||||
* Submit a test case, the smaller it is, the better
|
||||
|
||||
* Use <a href="http://bugzilla.ximian.com">
|
||||
http://bugzilla.ximian.com</a> to report the bug.
|
||||
|
||||
<p>In <b>addition</b> to bugzilla, posting to the list is
|
||||
fine if the bug merits larger exposure or design
|
||||
discussions to solve; posting to the list twice or more
|
||||
is just a way to annoy people and make them waste time,
|
||||
specially when you start a new thread about it.
|
||||
|
||||
* If the test involves libraries or assemblies that are
|
||||
not part of mono, add info about where to download all
|
||||
the dependencies, and how to compile/install them.
|
||||
|
||||
* If compiling the test case requires more than:
|
||||
<pre> mcs test.cs </pre>
|
||||
provide the <b>full command line</b> you used to compile
|
||||
the test.
|
||||
|
||||
* If running the test requires more than:
|
||||
<pre> mono test.exe </pre>
|
||||
provide the <b>full command line</b> needed to replicate
|
||||
the bug.
|
||||
|
||||
* Provide info about the version of the software you're
|
||||
using (both mono and the operating system or relevant
|
||||
libraries).
|
||||
|
||||
* Provide the output you expect the test case to produce.
|
||||
|
||||
* Provide the actual output <b>you</b> get from the test case.
|
||||
</ol>
|
||||
|
||||
A good bug report complies with at least 6 items from the list.
|
||||
If your bug report complies with 3 or less items, it is very
|
||||
poor and it means it will take much more time to fix (when it's
|
||||
not ignored).
|
||||
|
||||
** Small tasks
|
||||
|
||||
A few smaller tasks are here, dropped in no particular order:
|
||||
|
||||
+98
-132
@@ -14,16 +14,21 @@
|
||||
* 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).
|
||||
SymmetricAlgorithmTest</code> are generated by an external
|
||||
tool.
|
||||
</ul>
|
||||
|
||||
**** TODO
|
||||
<ul>
|
||||
* The current implementation of <code>CryptoStream</code> is
|
||||
very limited and contain known bugs (<a
|
||||
href="http://bugzilla.ximian.com/show_bug.cgi?id=40689">
|
||||
40689</a>). The class need to be re-designed.
|
||||
|
||||
* Support for adding/modifying OID using the
|
||||
<code>machine.config</code> configuration file (algorithms
|
||||
are done).
|
||||
|
||||
* 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
|
||||
@@ -39,6 +44,13 @@
|
||||
algorithm can be different for every CSP (Crypto Service
|
||||
Provider). However for compatibility we should provide an
|
||||
implementation compatible with the MS CSP (most likely used).
|
||||
|
||||
* Analyse the current coverage of the unit tests on the
|
||||
cryptographic classes and complete the unit tests.
|
||||
|
||||
* Optimizations (performance) on most class are possible. Some
|
||||
have been done using the Community Edition of BoundChecker
|
||||
(a free VisualStudio addon) - recommanded!
|
||||
</ul>
|
||||
|
||||
**** Notes
|
||||
@@ -46,12 +58,7 @@
|
||||
* All cryptographic algorithms are entirely managed, including
|
||||
classes named <code>*CryptoServiceProvider</code>, with the
|
||||
exception of <code>RNGCryptoServiceProvider</code> (which
|
||||
implementation resides in the runtime).
|
||||
|
||||
* There is a bug in the <code>PKCS1MaskGenerationMethod</code>
|
||||
class (in both framework 1.0 and 1.1). This means our
|
||||
implementation isn't compatible with MS (but is compatible with
|
||||
PKCS#1 v.2.1). However we get OAEP padding for every platform!
|
||||
resides in the runtime).
|
||||
|
||||
* Look at assembly Mono.Security.Win32 if you require more
|
||||
compatiblity with the Microsoft implementation (like accessing
|
||||
@@ -67,14 +74,26 @@
|
||||
(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
|
||||
set of certificates (more than 700) are used for a more
|
||||
set of certificates (more than 300) are used for a more
|
||||
complete test (but isn't part of the standard test suite for
|
||||
size and time consideration, i.e. a 7.5Mb C# source file).
|
||||
size and time consideration, i.e. a 3.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.
|
||||
|
||||
* Integration with CryptoAPI (on Windows) isn't possible as
|
||||
long as the <code>X509Certificate(IntPtr)</code> constructor
|
||||
isn't completed.
|
||||
</ul>
|
||||
|
||||
**** Notes
|
||||
@@ -96,8 +115,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>
|
||||
@@ -111,27 +130,29 @@
|
||||
|
||||
**** Status
|
||||
<ul>
|
||||
* All classes are present but some Transforms are only stubbed.
|
||||
|
||||
* We now have a fully managed C14N implementation.
|
||||
* All classes are present but some (most Transforms) are only
|
||||
stubbed.
|
||||
|
||||
* Most classes have their unit tests.
|
||||
</ul>
|
||||
|
||||
**** TODO
|
||||
<ul>
|
||||
* Complete all Transform derived classes.
|
||||
* All the transforms needs to be done. But this requires far
|
||||
more XML knowledge than crypto. Note: Most tests runs because
|
||||
the feeded XML is pre-c14n (by hand in the code) before
|
||||
signing (not because the transforms works). In the short
|
||||
term <code>libxml2</code> could be used to provide C14N, but
|
||||
in the long term a fully managed class would be much better.
|
||||
</ul>
|
||||
|
||||
<hr>
|
||||
** Assembly: Mono.Security
|
||||
|
||||
<b>Rational: </b>
|
||||
<b>Rational</b>
|
||||
This assembly provides the missing pieces to .NET security. On Windows
|
||||
CryptoAPI is often used to provide much needed functionalities (like
|
||||
some cryptographic algorithms, code signing, X.509 certificates). Mono,
|
||||
for platform independance, implements these functionalities in 100%
|
||||
managed code.
|
||||
some cryptographic algorithms, code signing, X.509 certificates).
|
||||
|
||||
*** Namespace: Mono.Security
|
||||
<ul>
|
||||
@@ -140,32 +161,29 @@
|
||||
*** Namespace: Mono.Security.Authenticode
|
||||
<ul>
|
||||
* Code signing and verification.
|
||||
* Support for SPC (Software Publisher Certificate) files and
|
||||
PVK (Private Key) files.
|
||||
* Support for SPC files and PVK files.
|
||||
</ul>
|
||||
*** Namespace: Mono.Security.Cryptography
|
||||
<ul>
|
||||
* Additional algorithms: MD2, ARCFOUR (required for SSL)
|
||||
* Convertion helpers
|
||||
</ul>
|
||||
*** Namespace: Mono.Security.Protocol.Tls
|
||||
<ul>
|
||||
* An 100% managed TLS implementation from Carlos Guzman Alvarez.
|
||||
</ul>
|
||||
*** Namespace: Mono.Security.X509
|
||||
<ul>
|
||||
* X.509 structures (certificate, CRL...) building and decoding.
|
||||
* X.509 certificate building and decoding.
|
||||
</ul>
|
||||
*** Namespace: Mono.Security.X509.Extensions
|
||||
<ul>
|
||||
* X.509 extensions (from public X.509 to private PKIX, Netsapce,
|
||||
Microsoft, Entrust...).
|
||||
* X.509 extensions (from X.509, PKIX, Netsapce, Microsoft,
|
||||
Entrust...).
|
||||
</ul>
|
||||
|
||||
**** Status
|
||||
<ul>
|
||||
* Some part of the work has not yet been commited (cleaning up).
|
||||
|
||||
* A big part of this assembly is also included inside Mono's
|
||||
corlib. The classes are duplicated in this assembly so the
|
||||
corlib. The class are duplicated in this assembly so the
|
||||
functionalities can be used without a dependency on Mono's
|
||||
corlib (which depends on Mono's runtime).
|
||||
|
||||
@@ -175,19 +193,18 @@
|
||||
<hr>
|
||||
** Assembly: Mono.Security.Win32
|
||||
|
||||
<b>Rational: </b>
|
||||
<b>Rational</b>
|
||||
This assembly goal is to provide maximum compatibility with CryptoAPI
|
||||
to application running with Mono's runtime on the Windows operating
|
||||
system.
|
||||
|
||||
<b>This assembly should NEVER be used directly by any application</b>
|
||||
(e.g. referecing the assembly from a project).
|
||||
<b>This assembly should NEVER be used directly by any application</b>.
|
||||
The classes should only be used by modifying the <code>machine.config
|
||||
</code> configuration file (and then only if this increased
|
||||
compatibility is required by an application).
|
||||
|
||||
See the file <code><a href="http://cvs.hispalinux.es/cgi-bin/cvsweb/~checkout~/mcs/class/Mono.Security.Win32/README?rev=1.1&content-type=text/plain&cvsroot=mono">/mcs/class/Mono.Security.Win32/README</a></code>
|
||||
for complete instructions.
|
||||
See the file <code>/mcs/class/Mono.Security.Win32/README</code> for
|
||||
complete instructions.
|
||||
|
||||
*** Namespace: Mono.Security.Cryptography
|
||||
|
||||
@@ -199,11 +216,10 @@
|
||||
|
||||
* Wrapper classes for unmanaged versions of hash algorithms:
|
||||
MD2, MD4, MD5 and SHA1 are supported. <b>note</b>: some
|
||||
algorithms shouldn't be used in new design (MD4 is broken,
|
||||
MD2 and MD5 aren't considered safe for some usage). They are
|
||||
included to preserve interoperability with older applications
|
||||
(e.g. some old, but still valid, X.509 certificates use MD2,
|
||||
MD4 is required for NTLM authentication ...).
|
||||
algorithms shouldn't be used in new design (MD4 is broken and
|
||||
MD2 isn't considered safe). They are included to preserve
|
||||
interoperability with older applications (e.g. some old, but
|
||||
still valid, X.509 certificates use MD2).
|
||||
</ul>
|
||||
|
||||
**** TODO
|
||||
@@ -219,13 +235,9 @@
|
||||
|
||||
**** Ideas
|
||||
<ul>
|
||||
* Similar assemblies (e.g. <code>Mono.Security.XXX</code>)
|
||||
could be created for <a href="http://www.openssl.org">OpenSSL</a>,
|
||||
<a href="http://www.mozilla.org/projects/security/pki/nss/">NSS</a>,
|
||||
<a href="http://www.eskimo.com/~weidai/cryptlib.html">crypto++</a>,
|
||||
<a href="http://www.cryptlib.orion.co.nz/">cryptlib</a> ... for
|
||||
improved performance and/or HSM (Hardware Security Module) support
|
||||
under Linux and/or Windows.
|
||||
* Similar assembly could be created for <a href="http://www.openssl.org">
|
||||
OpenSSL</a>, NSS, crypto++, cryptlib ... for improved
|
||||
performance and/or HSM support under Linux.
|
||||
</ul>
|
||||
<hr>
|
||||
** Assembly: Microsoft.Web.Services
|
||||
@@ -242,36 +254,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 stating to
|
||||
implement WS-Security. All contributors must sign an agreement with
|
||||
Microsoft before commiting anything related to WS-Security into CVS.
|
||||
</b>
|
||||
|
||||
*** Namespace: Microsoft.Web.Services.Security [*]
|
||||
*** 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, could be done without signing any agreements.
|
||||
</ul>
|
||||
|
||||
**** TODO
|
||||
@@ -281,14 +283,6 @@
|
||||
keypairs. This could also be used to store the SPC roots.
|
||||
</ul>
|
||||
|
||||
*** Notes
|
||||
<ul>
|
||||
* Microsoft has <a href="http://microsoft.com/downloads/details.aspx?FamilyId=21FB9B9A-C5F6-4C95-87B7-FC7AB49B3EDD&displaylang=en">released</a>
|
||||
a technical preview of WSE 2. <b>Note that WSDK (the technical
|
||||
preview of WSE) had A LOT of changes before it's initial
|
||||
release!</b>
|
||||
</ul>
|
||||
|
||||
<hr>
|
||||
** Tools
|
||||
|
||||
@@ -299,7 +293,7 @@
|
||||
|
||||
**** Status
|
||||
|
||||
The following tools are complete (or mostly complete):
|
||||
The following tools are complete:
|
||||
<ul>
|
||||
* <code>secutil</code> is a tool to extract certificates and
|
||||
strongnames from assemblies in a format that can be easily
|
||||
@@ -310,36 +304,20 @@
|
||||
(SPC) file - which is a long name for a simple PKCS#7 file.
|
||||
|
||||
* <code>makecert</code> to create X.509 test certificates that
|
||||
can be used (once transformed in SPC) to sign assemblies. It's
|
||||
now possible to generate SSL certificates for web servers.
|
||||
|
||||
* <code>sn</code> is a clone of the <code>sn</code> to manage
|
||||
strongnames. Current version can create, convert, sign and
|
||||
verify strongnames signatures. Some configuration options
|
||||
are still missing.
|
||||
|
||||
* <code>signcode</code> and <code>chktrust</code> for signing
|
||||
and validating Authenticode(tm) signatures on assemblies (or
|
||||
any PE file) are now working (signature and timestamps) but
|
||||
some options aren't yet supported.
|
||||
can be used (once transformed in SPC) to sign assemblies.
|
||||
</ul>
|
||||
|
||||
Somewhat usable, somewhat incomplete:
|
||||
**** TODO
|
||||
The following tools are still missing or incomplete:
|
||||
<ul>
|
||||
* <code>certview</code> is a certificate viewer for
|
||||
<code>System.Windows.Forms</code> (right now only working on
|
||||
Windows), while <code>gcertview</code> is the same viewer
|
||||
implemented for GTK# (working on both Windows and Linux).
|
||||
|
||||
* <code>monosn</code> is a clone of the <code>sn</code> to manage
|
||||
strongnames. This tools is part of the runtime (not the class
|
||||
library) and as such is written in C and won't run without Mono.
|
||||
</ul>
|
||||
|
||||
* <code>signcode</code> and <code>chktrust</code> (in progress)
|
||||
for signing and validating Authenticode(tm) signatures on
|
||||
assemblies (or any PE file).
|
||||
|
||||
**** TODO
|
||||
The following tools are still missing or largely incomplete:
|
||||
<ul>
|
||||
* Other tools like a, GUI-based, certificate manager...
|
||||
</ul>
|
||||
|
||||
@@ -348,45 +326,33 @@
|
||||
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).
|
||||
</ul>
|
||||
|
||||
<hr>
|
||||
|
||||
<hr>
|
||||
** How to Help
|
||||
|
||||
<ul>
|
||||
* Complete any of the TODO (and feel good about it ;-).
|
||||
Complete any of the TODO (and feel good about it ;-).
|
||||
|
||||
* Analyse the current coverage of the unit tests on the
|
||||
cryptographic classes and complete the unit tests. <b><code>
|
||||
monocov</code> does a great job at this! Now we just need to
|
||||
complete the missing unit tests.</b>
|
||||
Add missing unit tests to classes or methods.
|
||||
|
||||
* Optimization can also be done on most algorithms as crypto
|
||||
is never fast enough. Some have been done using the
|
||||
Community Edition of BoundChecker (a free VisualStudio
|
||||
addon) - recommanded! Just be sure to test every optimization
|
||||
(using the unit tests) carefully - it's so fast to break an
|
||||
algorithm ;-).
|
||||
Write some documentation on the cryptographic classes for the
|
||||
<a href="http://go-mono.com/tutorial/html/en/index.html">Mono
|
||||
Handbook</a> as I'm not a very good writer (at least in English).
|
||||
|
||||
* Write some documentation on the cryptographic classes for
|
||||
<b>monodoc</b> as I'm not a very good writer (at least in English).
|
||||
</ul>
|
||||
Optimization can also be done on algorithms as crypto is never fast
|
||||
enough. Just be sure to test every optimization (using the unit test)
|
||||
carefully - it's so fast to break an algorithm ;-).
|
||||
|
||||
Contact Sebastien Pouliot (<a href="mailto:[email protected]">home</a>
|
||||
, <a href="mailto:[email protected]">work</a>) if you need additional
|
||||
informations about the status of the cryptographic classes.
|
||||
|
||||
<hr>
|
||||
Last reviewed: October 26, 2003 (post mono 0.28)
|
||||
Last reviewed: April 7, 2003 (post mono 0.23)
|
||||
+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>
|
||||
|
||||
+4
-501
@@ -13,507 +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.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.5.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.5.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.2.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">
|
||||
<td>
|
||||
<b>Release 0.25</b><br>
|
||||
<a href="archive/mono-0.25.html">Release notes</a><br>
|
||||
Jun 26, 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.25.tar.gz">Mono Class Libraries and C# Compiler.</a>
|
||||
<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>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr bgcolor="#BBBBBB">
|
||||
<td>
|
||||
<b>Source RPMs</b><br>
|
||||
(No RPMS for XSP).
|
||||
</td>
|
||||
<td>
|
||||
<ul>
|
||||
<li><a href="archive/mono-0.25-1.ximian.5.src.rpm">mono-0.25-1.src.rpm</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.25-1.ximian.6.1.i386.rpm">mono-0.25-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/mono-devel-0.25-1.ximian.6.1.i386.rpm">mono-devel-0.25-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/mono-debuginfo-0.25-1.ximian.6.1.i386.rpm">mono-debuginfo-0.25-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/gtk-sharp-0.10-1.ximian.6.1.i386.rpm">gtk-sharp-0.10-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/gtk-sharp-gapi-0.10-1.ximian.6.1.i386.rpm">gtk-sharp-gapi-0.10-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/gtk-sharp-debuginfo-0.10-1.ximian.6.1.i386.rpm">gtk-sharp-debuginfo-0.10-1.ximian.6.1.i386.rpm</a>
|
||||
<br>
|
||||
<li><a href="archive/redhat-90-i386/monodoc-0.5-1.ximian.6.1.i386.rpm">monodoc-0.5-1.ximian.6.1.i386.rpm</a>
|
||||
<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/mono-wine-20030318-1.ximian.6.2.i386.rpm">mono-wine-20030318-1.ximian.6.2.i386.rpm</a>
|
||||
<li><a href="archive/mono-wine-debuginfo-20030318-1.ximian.6.2.i386.rpm">mono-wine-debuginfo-20030318-1.ximian.6.2.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.25-1.ximian.5.1.i386.rpm">mono-0.25-1.ximian.5.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-80-i386/mono-devel-0.25-1.ximian.5.1.i386.rpm">mono-devel-0.25-1.ximian.5.1.i386.rpm</a>
|
||||
<br>
|
||||
<li><a href="archive/redhat-80-i386/gtk-sharp-0.10-1.ximian.5.1.i386.rpm">gtk-sharp-0.10-1.ximian.5.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-80-i386/gtk-sharp-gapi-0.10-1.ximian.5.1.i386.rpm">gtk-sharp-gapi-0.10-1.ximian.5.1.i386.rpm</a>
|
||||
<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>
|
||||
<li><a href="archive/mono-wine-20030318-1.ximian.5.2.i386.rpm">mono-wine-20030318-1.ximian.5.2.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/windows-36.gif"><b>Windows Setup Wizard (XP, 2000, NT)</b>
|
||||
<ul>
|
||||
<li><a href="archive/mono-0.25-win32-1.exe">Setup program.</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/redhat-36.gif"><b>Red Hat 7.3/x86</b>
|
||||
<ul>
|
||||
<li><a href="archive/redhat-73-i386/mono-0.25-1.ximian.4.1.i386.rpm">mono-0.25-1.ximian.4.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-73-i386/mono-devel-0.25-1.ximian.4.1.i386.rpm">mono-devel-0.25-1.ximian.4.1.i386.rpm</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.25-1.ximian.6.1.i586.rpm">mono-0.25-1.ximian.6.1.i586.rpm</a>
|
||||
<li><a href="archive/mandrake-91-i586/mono-devel-0.25-1.ximian.6.1.i586.rpm">mono-devel-0.25-1.ximian.6.1.i586.rpm</a>
|
||||
<li><a href="archive/mandrake-91-i586/gtk-sharp-0.10-1.ximian.6.1.i586.rpm">gtk-sharp-0.10-1.ximian.6.1.i586.rpm</a>
|
||||
<li><a href="archive/mandrake-91-i586/gtk-sharp-gapi-0.10-1.ximian.6.1.i586.rpm">gtk-sharp-gapi-0.10-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>
|
||||
|
||||
<!--
|
||||
We don't have SuSE packages right now
|
||||
-->
|
||||
<!-- <tr> -->
|
||||
<!-- <td bgcolor="#999999"> -->
|
||||
<!-- <img src="images/suse-36.gif"><b>SuSE 8.2/x86</b> -->
|
||||
<!-- <ul> -->
|
||||
<!-- <li><a href="archive/suse-80-i386/mono-0.25-1.i386.rpm">mono-0.25-1.i386.rpm</a> -->
|
||||
<!-- <li><a href="archive/suse-80-i386/mono-devel-0.25-1.i386.rpm">mono-devel-0.25-1.i386.rpm</a> -->
|
||||
<!-- </ul> -->
|
||||
<!-- </td> -->
|
||||
<!-- </tr> -->
|
||||
</table>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<tr bgcolor="#CCCCC">
|
||||
<td>
|
||||
<b>Regression Tests</b><br>
|
||||
</td>
|
||||
<td>
|
||||
You can get binaries for the Mono Regression Test
|
||||
Suite <a href="archive/mono-tests.tar.gz">here</a>
|
||||
</td>
|
||||
</tr>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
* Older Releases:
|
||||
|
||||
We provide binaries for older releases until we have packages for the new release.
|
||||
|
||||
|
||||
<table>
|
||||
<tbody>
|
||||
<tr bgcolor="#DDDDDD">
|
||||
<td>
|
||||
<b>Release 0.24</b><br>
|
||||
<a href="archive/mono-0.24.html">Release notes</a><br>
|
||||
May 6, 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.24.tar.gz">Mono Class Libraries and C# Compiler.</a>
|
||||
<li><a href="archive/mono-0.24.tar.gz">Mono Runtime</a>
|
||||
<li><a href="archive/gc6.1.tar.gz">Boehm GC 6.1</a>
|
||||
<li><a href="archive/xsp-0.4.tar.gz">XSP web server (0.4)</a>
|
||||
<li><a href="archive/monodoc-0.4.tar.gz">MonoDoc 0.4</a>
|
||||
<li><a href="archive/gtk-sharp-0.9.tar.gz">Gtk# 0.9</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr bgcolor="#BBBBBB">
|
||||
<td>
|
||||
<b>Source RPMs</b><br>
|
||||
(No RPMS for XSP).
|
||||
</td>
|
||||
<td>
|
||||
<ul>
|
||||
<li><a href="archive/libgc-6.1-1.src.rpm">libgc-6.1-1.src.rpm</a>
|
||||
<li><a href="archive/mono-0.24-1.src.rpm">mono-0.24-1.src.rpm</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/libgc-6.1-1.i386.rpm">libgc-6.1-1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/libgc-devel-6.1-1.i386.rpm">libgc-devel-6.1-1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/mono-0.24-1.i386.rpm">mono-0.24-1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/mono-devel-0.24-1.i386.rpm">mono-devel-0.24-1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/mono-debuginfo-0.24-1.i386.rpm">mono-debuginfo-0.24-1.i386.rpm</a>
|
||||
<br>
|
||||
<li><a href="archive/redhat-90-i386/gtk-sharp-0.9-1.i386.rpm">gtk-sharp-0.9-1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/gtk-sharp-debuginfo-0.9-1.i386.rpm">gtk-sharp-debuginfo-0.9-1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/monodoc-0.4-1.i386.rpm">monodoc-0.4-1.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/libgc-6.1-1.i386.rpm">libgc-6.1-1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-80-i386/libgc-devel-6.1-1.i386.rpm">libgc-devel-6.1-1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-80-i386/mono-0.24-2.i386.rpm">mono-0.24-2.i386.rpm</a>
|
||||
<li><a href="archive/redhat-80-i386/mono-devel-0.24-2.i386.rpm">mono-devel-0.24-2.i386.rpm</a>
|
||||
<br>
|
||||
<li><a href="archive/redhat-80-i386/gtk-sharp-0.9-1.i386.rpm">gtk-sharp-0.9-1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-80-i386/monodoc-0.4-1.i386.rpm">monodoc-0.4-1.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/windows-36.gif"><b>Windows Setup Wizard (XP, 2000, NT)</b>
|
||||
<ul>
|
||||
<li><a href="archive/mono-0.24-win32-1.exe">Setup program.</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/redhat-36.gif"><b>Red Hat 7.3/x86</b>
|
||||
<ul>
|
||||
<li><a href="archive/redhat-73-i386/libgc-6.1-1.i386.rpm">libgc-6.1-1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-73-i386/libgc-devel-6.1-1.i386.rpm">libgc-devel-6.1-1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-73-i386/mono-0.24-1.i386.rpm">mono-0.24-1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-73-i386/mono-devel-0.24-1.i386.rpm">mono-devel-0.24-1.i386.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/mandrake-36.gif"><b>Mandrake 8.2/x86</b>
|
||||
<ul>
|
||||
<li><a href="archive/mandrake-82-i386/libgc-6.1-1.i586.rpm">libgc-6.1-1.i586.rpm</a>
|
||||
<li><a href="archive/mandrake-82-i386/libgc-devel-6.1-1.i586.rpm">libgc-devel-6.1-1.i586.rpm</a>
|
||||
<li><a href="archive/mandrake-82-i386/mono-0.24-1.i586.rpm">mono-0.24-1.i586.rpm</a>
|
||||
<li><a href="archive/mandrake-82-i386/mono-devel-0.24-1.i586.rpm">mono-devel-0.24-1.i586.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/suse-36.gif"><b>SuSE 8.0/x86</b>
|
||||
<ul>
|
||||
<li><a href="archive/suse-80-i386/libgc-6.1-1.i386.rpm">libgc-6.1-1.i386.rpm</a>
|
||||
<li><a href="archive/suse-80-i386/libgc-devel-6.1-1.i386.rpm">libgc-devel-6.1-1.i386.rpm</a>
|
||||
<li><a href="archive/suse-80-i386/mono-0.24-1.i386.rpm">mono-0.24-1.i386.rpm</a>
|
||||
<li><a href="archive/suse-80-i386/mono-devel-0.24-1.i386.rpm">mono-devel-0.24-1.i386.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
<td bgcolor="#999999">
|
||||
<b>Linux s/390</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.24-1.s390.rpm">mono-0.24-1.s390.rpm</a>
|
||||
<li><a href="archive/s390/mono-devel-0.24-1.s390.rpm">mono-devel-0.24-1.s390.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
</table>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<tr bgcolor="#CCCCC">
|
||||
<td>
|
||||
<b>Regression Tests</b><br>
|
||||
</td>
|
||||
<td>
|
||||
You can get binaries for the Mono Regression Test
|
||||
Suite <a href="archive/mono-tests.tar.gz">here</a>
|
||||
</td>
|
||||
</tr>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
<table>
|
||||
<tbody>
|
||||
<tr bgcolor="#DDDDDD">
|
||||
@@ -649,6 +148,10 @@
|
||||
|
||||
|
||||
|
||||
* Older Releases:
|
||||
|
||||
We provide binaries for older releases until we have packages for the new release.
|
||||
|
||||
<table>
|
||||
<tbody>
|
||||
<tr bgcolor="#DDDDDD">
|
||||
|
||||
-43
@@ -1,43 +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 "GDI+ Flat API").
|
||||
|
||||
<center>
|
||||
<img src="images/system-drawing.png">
|
||||
</center>
|
||||
|
||||
In Windows Mono uses the GDI+ library that is included
|
||||
with the operating system, while in Unix we provide an
|
||||
implementation of this API which 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.
|
||||
+1
-16
@@ -68,20 +68,9 @@
|
||||
not interfere with code in other domains. This is useful if
|
||||
you want to host different applications in your program.
|
||||
|
||||
Now, it is necessary to transfer control to Mono, and setup
|
||||
the threading infrastructure, you do this like this:
|
||||
Then you can load an assembly containing code into the domain:
|
||||
|
||||
<pre>
|
||||
void *user_data = NULL;
|
||||
|
||||
mono_runtime_exec_managed_code (domain, main_thread_handler, user_data);
|
||||
</pre>
|
||||
|
||||
Where your main_thread_handler can load your assembly and execute it:
|
||||
|
||||
<pre>
|
||||
static void main_thread_handler (gpointer user_data)
|
||||
{
|
||||
MonoAssembly *assembly;
|
||||
|
||||
assembly = mono_domain_assembly_open (domain, "file.dll");
|
||||
@@ -120,10 +109,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
|
||||
|
||||
+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>
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -12,14 +12,15 @@
|
||||
Common Language Infrastructure (also referred as the CLR) and a
|
||||
set of <a href="class-library.html">class libraries</a>. The
|
||||
runtime can be <a href="embedded-api.html">embedded</a> into your
|
||||
application. It implements of both <a href="ado-net.html">ADO.NET</a>
|
||||
and <a href="asp-net.html">ASP.NET</a>.
|
||||
application.
|
||||
|
||||
Mono has implementations of both <a href="ado-net">ADO.NET</a>
|
||||
and <a href="asp-net">ASP.NET</a> as part of its distribution.
|
||||
|
||||
You can read our <a href="rationale.html">rationale</a> for
|
||||
this project. If you have questions about the project, please
|
||||
read our list of <a href="faq.html">Frequently Asked
|
||||
Questions</a> or <a href="mailto:[email protected]">contact
|
||||
us.</a> The project <a href="mono-roadmap.html">roadmap</a>.
|
||||
Questions</a> or <a href="mailto:[email protected]">contact us.</a>
|
||||
|
||||
You might also want to <a href="download.html">Download the
|
||||
source</a> for our work so far. Grab a <a
|
||||
@@ -33,9 +34,16 @@
|
||||
href="http://www.gotmono.com/cgi-bin/yabb/YaBB.pl">forum</a> at <a
|
||||
href="http://www.gotmono.com">GotMono</a>.
|
||||
|
||||
Wikis: <a href="http://www.nullenvoid.com/gtksharp/wiki">Gtk# Wiki</a>
|
||||
and <a href="http://www.nullenvoid.com/mono/wiki">Mono
|
||||
Wiki</a>
|
||||
You can contact the team at: <a
|
||||
href="mailto:mono-list@ximian.com">mono[email protected]</a>
|
||||
|
||||
In order to follow the process of the project and to learn more
|
||||
about the team members we have created the <a
|
||||
href="http://monoevo.sf.net/mwn/index.html">Mono Weekly News letter</a>.
|
||||
Which archives can be found <a
|
||||
href="http://monoevo.sf.net/mwn/archives.html">here</a>.
|
||||
We have a <a href="http://www.nullenvoid.com/gtksharp/wiki">Gtk# Wiki</a>
|
||||
and a <a href="http://www.nullenvoid.com/mono/wiki">Mono Wiki</a>
|
||||
|
||||
</td>
|
||||
<td>
|
||||
@@ -68,12 +76,14 @@
|
||||
</td>
|
||||
<td>
|
||||
Working:<br>
|
||||
Linux/x86, Linux/PPC, S390, StrongARM, SPARC, HPPA, SPARC v9 <br>
|
||||
Linux/x86, Linux/PPC, S390, StrongARM<br>
|
||||
In progress:<br>
|
||||
SPARC.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><b><a href="asp-net.html">ASP.NET</a></b></td>
|
||||
<td>Webforms and WebServices working<br></td>
|
||||
<td>Webforms working<br></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
@@ -97,590 +107,10 @@
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<table border=1>
|
||||
<tr>
|
||||
<td colspan="3">
|
||||
<b><center>In the news</center></b>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<img src="images/netmagazine.png">
|
||||
</td>
|
||||
<td>
|
||||
<a href="http://www.fawcette.com/dotnetmag/2003_TE/magazine/columns/trends/default.asp">May 31st, 2003</a>: CLI integration.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<img src="images/infoworld.png">
|
||||
</td>
|
||||
<td>
|
||||
<a href="http://www.infoworld.com/article/03/05/22/HNmono_1.html">May 22nd, 2003</a>: Mono 1.0 plans.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<img src="images/infoworld.png">
|
||||
</td>
|
||||
<td>
|
||||
<a href="http://www.infoworld.com/article/03/03/14/11stratdev_1.html">Mar 14th, 2003</a>: Whither Mono?
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<img src="images/b2.png">
|
||||
</td>
|
||||
<td>
|
||||
<a href="http://www.infoworld.com/article/03/05/22/HNmono_1.html">Dec, 2002</a>: The Penguin takes flight.
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
@item Nov 25th: Gtk# 0.14, System.DirectoryServices
|
||||
|
||||
Gtk# 0.14 has been released, and it is available from <a
|
||||
href="http://gtk-sharp.sf.net">the Gtk# web site</a>.
|
||||
|
||||
Sunil has checked in the implementation of
|
||||
System.DirectoryServices as well as the Novell.Directory.Ldap
|
||||
code into Mono CVS.
|
||||
|
||||
@item Nov 14th: Gtk# 0.13 released.
|
||||
|
||||
Mike Kestner has <a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2003-November/016943.html">announced</a>
|
||||
the release of the <a href="http://gtk-sharp.sf.net">Gtk#</a>
|
||||
GUI toolkit for .NET and Mono.
|
||||
|
||||
@item Nov 13th: Managed LDAP binding for Mono and .NET
|
||||
|
||||
Sunil Kumar at Novell has <a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2003-November/016907.html">announced</a>
|
||||
the availability of a fully managed implementation of LDAP for
|
||||
Mono and the .NET Framework.
|
||||
|
||||
You can obtain the library from <a
|
||||
href="http://forge.novell.com">Novell Forge's</a> <a
|
||||
href="http://forge.novell.com/modules/xfmod/cvs/cvsbrowse.php/ldapcsharp/CsharpLDAP">CSharpLDAP</a>
|
||||
module.
|
||||
|
||||
@item Nov 4th: Mono Roadmap announced.
|
||||
|
||||
The <a href="mono-roadmap.html">Mono Roadmap</a> and <a
|
||||
href="mono-hacking-roadmap.html">Mono Hackers Roadmap</a> have
|
||||
been released.
|
||||
|
||||
@item Oct 28th: Mono Get Together at the PDC. GTK# 0.12 Released.
|
||||
|
||||
We will be getting together at the West Tower Lobby on Tuesday
|
||||
28th at 6pm to talk about the Mono project. You have 24 hours to
|
||||
notify all of your friends, open source buddies and free software
|
||||
folks.
|
||||
|
||||
We will bring Mono t-shirts.
|
||||
|
||||
Mike Kestner released <a href="http://gtk-sharp.sourceforge.net">Gtk#</a> 0.12 today. GTK# source tar balls
|
||||
and RPMs are available. A windows installer was contributed by Johannes Roith.
|
||||
|
||||
@item Oct 26th: Last Minute Mono BOF
|
||||
|
||||
The first in a series of undercover Mono BOFs at the PDC will take
|
||||
place tonight at 7pm on the Academy meeting, in room 411. Come join us
|
||||
to plot the evolution.
|
||||
|
||||
|
||||
@item Oct 25th: GTK# 0.11+ Windows Installer available
|
||||
|
||||
Johannes created a <a href="http://java.thn.htu.se/~toor/gtk-sharp/gtk-sharp-0.11-cvs.exe">Windows Installer for GTK# 0.11+</a> and works
|
||||
with Mono 0.28 for Windows.
|
||||
|
||||
@item Oct 21st: Mono Community at Novell Forge
|
||||
|
||||
Mono Developers that are looking for a public repository for
|
||||
hosting their projects can now use <a
|
||||
href="http://forge.novell.com">Novell Forge's</a> which hosts
|
||||
a <a
|
||||
href="http://forge.novell.com/modules/xfmod/community/?monocomm">Mono
|
||||
Community</a>.
|
||||
|
||||
Novell Forge offers mailing lists, cvs repository, bug
|
||||
tracking and mailing list services and all the other services
|
||||
you expect. Mono will continue to be hosted in our own CVS
|
||||
repository, and using our <a href="anoncvs.html">anonymous CVS
|
||||
servers</a>
|
||||
|
||||
@item Oct 13th: SPARC V9, HPPA, Internationalization, GdiPlus
|
||||
|
||||
Dick Porter has checked in our rewrite of the international
|
||||
substrate in Mono that uses the <a
|
||||
href="http://oss.software.ibm.com/icu/">International
|
||||
Components for Unicode</a> library from IBM. This means that
|
||||
we got CultureInfo support through the whole code base now.
|
||||
|
||||
Alexandre Pigolkine has checked-in the new implementation of
|
||||
System.Drawing. We have now dropped the old implementation
|
||||
with multiple-backends that we had, and replaced it with an
|
||||
implementation that P/Invokes into GDI+. A GDI+
|
||||
implementation on top of <a
|
||||
href="http://www.cairographics.org">Cairo</a> is used on Unix
|
||||
systems. This step vastly simplifies the development and
|
||||
maintenance of System.Drawing.
|
||||
|
||||
There are plenty of updates to Mono as well, we encourage you
|
||||
to read the <a
|
||||
href="http://www.go-mono.com/monologue">Monologue</a> to keep
|
||||
an eye on recent developments.
|
||||
|
||||
Bernie Solomon just <a
|
||||
href="http://lists.ximian.com/archives/public/mono-devel-list/2003-October/002460.html">checked
|
||||
in</a> 64-bit support for SPARC v9 and HPPA into the Mono
|
||||
runtime. This also improves the SPARC-32 support.
|
||||
|
||||
@item Oct 6th: Linux s390 Mono packages available.
|
||||
|
||||
Neale Ferguson has contributed Mono packages for the
|
||||
Linux/s390. You can get them from the <a
|
||||
href="download.html">download</a> page.
|
||||
|
||||
@item Oct 5th: Monologue aggregates Mono Blogs
|
||||
|
||||
You can now read an aggregated view of the <a
|
||||
href="blogs.html">blogs</a> maintained by Mono developers in
|
||||
<a href="http://www.go-mono.com/monologue">Monologue</a>.
|
||||
Monologue is available as an HTML page or as an <a
|
||||
href="monologue/index.rss">RSS feed</a>.
|
||||
|
||||
@item Oct 2nd: Windows packages, MonoDoc 0.7
|
||||
|
||||
Windows packages for Mono 0.28 are now available from our <a
|
||||
href="download.html">download</a> page.
|
||||
|
||||
A new version of MonoDoc has been released. The new version
|
||||
is available <a href="archive/monodoc-0.7.tar.gz">here</a>
|
||||
|
||||
@item Oct 1st: Mono 0.28 has been released.
|
||||
|
||||
Check out the <a
|
||||
href="http://www.go-mono.com/archive/mono-0.28.html">Release
|
||||
notes</a> for details on Mono 0.28. This release marks the
|
||||
completion of the SourceGear project to add web services
|
||||
functionality to Mono and improve its reliability.
|
||||
|
||||
@item Sep 30th: Mono Kick Start book available
|
||||
|
||||
The Mono Kick Start book is now <a
|
||||
href="http://www.amazon.com/exec/obidos/tg/detail/-/0672325799/qid=1064937318/sr=8-1/ref=sr_8_1/103-9624440-8714218?v=glance&s=books&n=507846">available</a>
|
||||
in English. Originally available only in <a
|
||||
href="http://www.amazon.de/exec/obidos/ASIN/3827264928/qid=1050051051/sr=2-1/ref=sr_2_3_1/028-2755135-1623712">German</a>.
|
||||
The book technical review was done by <a
|
||||
href="http://www.maurer-it.com/">Dietmar Maurer</a> JIT
|
||||
architect at the Mono team.
|
||||
|
||||
@item Sep 26th, 2003: DiaCanvas# 0.1 released, Gtk# 0.11 released.
|
||||
|
||||
Mike Kestner has <a
|
||||
href="http://lists.ximian.com/archives/public/gtk-sharp-list/2003-September/002475.html">released</a>
|
||||
a new version of <a href="http://gtk-sharp.sf.net">Gtk#</a>.
|
||||
|
||||
Martin has also
|
||||
<a href="http://mwh.sysrq.dk/programs/announcements/diacanvas-sharp-0.1.0.html">released</a>
|
||||
his binding to <a href="http://diacanvas.sf.net">DiaCanvas</a> for C#.
|
||||
|
||||
@item Sep 16th, 2003: WineLib, Authenticode, Generics, Xslt updates, Wsdl compiler, WSE.
|
||||
|
||||
<b>WineLib:</b> Vladimir has added new libraries to the Wine
|
||||
process, which we will soon bring into our packages: the
|
||||
various Windows common dialogs can now be used (screenshots:
|
||||
<a href="images/colordlg.png">here</a>, <a
|
||||
href="images/fontdlg.png">here</a>, <a
|
||||
href="images/filedlg.png">here</a> and <a
|
||||
href="images/finddlg.png">here</a>.
|
||||
|
||||
Johannes has patches to have Wine track the Gtk theme,
|
||||
screenshot <a href="http://www.sport-huettn.de/jroith/swfsample.png">here</a>
|
||||
|
||||
<b>Security:</b> New authenticode support from Sebastien has
|
||||
been checked into CVS.
|
||||
|
||||
<b>Xslt:</b> Plenty of conformance updates to the managed
|
||||
implementation of Xslt, as well as breaking the libxslt speed
|
||||
barrier. Our managed implementation is now faster than the
|
||||
C-based libxslt that we used before.
|
||||
|
||||
<b>Generics:</b> Work continues on generics support, feel free
|
||||
to try it out. The compiler is currently on a separate
|
||||
directory until we stability it (gmcs) and you need to compile
|
||||
the class libraries with the `generics' profile to try it
|
||||
out. Sample generic programs are included in the CVS module.
|
||||
|
||||
<b>Wsdl:</b> We now have Wsdl support in Mono: a wsdl compiler
|
||||
command line tool, and support on ASP.NET to generate the wsdl
|
||||
file from an .asmx file.
|
||||
|
||||
<b>AOT:</b> Many robustness updates to the ahead-of-time
|
||||
compiler and a new locking and threading system that avoids
|
||||
having "big locks" around the mono kernel, and moves to a
|
||||
fine-grained locking system. The design includes a lattice to
|
||||
avoid deadlocks.
|
||||
|
||||
<b>Dogfooding:</b> We are now running Mono's ASP.NET on
|
||||
go-mono.com to find problems. It is currently hosting our
|
||||
Monodoc documentation. The <a
|
||||
href="http://www.go-mono.com/docs/index.html">Apache module
|
||||
version</a> and the <a href="http://www.go-mono.com:8080/">XSP
|
||||
version</a>.
|
||||
|
||||
<b>WSE:</b> The Web Services Enhancements season has begun.
|
||||
The Microsoft.Web.Services namespace and classes are now
|
||||
checked into CVS.
|
||||
|
||||
@item Sep 1st, 2003: Ice for Mono; XmlSerializer generators; Monodoc progress.
|
||||
|
||||
<b>Ice:</b> Vladimir has checked into CVS (Module ginzu) an
|
||||
implementation of <a href="http://www.zeroc.com">ZeroC's</a>
|
||||
<a href="http://www.zeroc.com/ice.html">ICE</a> protocol. It
|
||||
is implemented using Remoting. If you were looking for an
|
||||
efficient binary protocol to use with Remoting, this is it.
|
||||
|
||||
ICE is simpler to use than CORBA, and was created by people
|
||||
who were deeply involved in CORBA and wanted to fix its
|
||||
problems (you can see a <a
|
||||
href="http://www.zeroc.com/iceVsCorba.html">list of
|
||||
differences</a>).
|
||||
|
||||
<b>XmlSerializer</b>: Lluis has checked in a new technology
|
||||
for use in our XmlSerializer: the XmlSerializer code
|
||||
generator. Currently our XmlSerializer generates a
|
||||
description of instructions for serializing data, these
|
||||
instructions are later interpreted while using it: Reflection
|
||||
is used to pull all the data. The code generator is the first
|
||||
step into turning the Serializer from an intepreter into a
|
||||
compiler and improving the performance of it.
|
||||
|
||||
Currently was used internally to implement the WSDL
|
||||
serializer, in the future it will just be part of the standard
|
||||
serialization process.
|
||||
|
||||
<b>MonoDoc:</b> New providers! Thanks to <a
|
||||
href="http://www.jaggersoft.com/">Jon Jagger</a> for providing
|
||||
us with his master XML files for the C# specification we now
|
||||
have integrated the C# spec into Monodoc. Another provider is
|
||||
the Error provider: now we include all the C# compiler errors
|
||||
in the help system.
|
||||
|
||||
Alp has contributed various user interface improvement, and
|
||||
updated our list widget for key navigation; Ben made the
|
||||
matches window more useful and Joshua has helped us clean up
|
||||
the ECMA provider even more.
|
||||
|
||||
@item Aug 14th, 2003: Mono 0.26 has been released
|
||||
|
||||
A new version of Mono is available, the new features include:
|
||||
<a href="http://www.cairographics.org/">Cairo support</a>, <a
|
||||
href="http://remoting-corba.sf.net">Remoting.Corba</a>
|
||||
support, as well as a managed XSLT implementation.
|
||||
|
||||
Existing features have been improved vastly: better
|
||||
Windows.Forms, runtime, faster compiler, web services, better
|
||||
compliance to the spec and more.
|
||||
|
||||
Check out the <a
|
||||
href="http://www.go-mono.com/archive/mono-0.26.html">Release
|
||||
notes</a> for details.
|
||||
|
||||
@item Aug 9th, 2003: Python for .NET Preview 2 available; Mono Documentation site up.
|
||||
|
||||
Brian Lloyd has <a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2003-August/015313.html">announced</a>
|
||||
the availability of his Python binding to .NET. This works
|
||||
with .NET and Mono. For more information about it, see
|
||||
Brian's site at <a href="
|
||||
http://zope.org/Members/Brian/PythonNet/">http://zope.org/Members/Brian/PythonNet/</a>
|
||||
|
||||
We have uploaded the current Mono Documentation (core
|
||||
libraries and Gtk#) to <a
|
||||
href="http://mono.ximian.com:8080"/>http://mono.ximian.com:8080</a>.
|
||||
The site is running the ASP.NET edition of <a
|
||||
href="archive/monodoc-0.6.tar.gz">MonoDoc 0.6</a> on XSP.
|
||||
|
||||
@item Aug 6th, 2003: Winforms samples
|
||||
|
||||
Timothy Parez is coordinating the effort to create sample
|
||||
programs that exercise the various Windows.Forms controls. We
|
||||
are using this as graphical regression test suite for the Mono
|
||||
implementation.
|
||||
|
||||
The screenshots of the various widgets, together with the
|
||||
source code is available on the <a
|
||||
href="http://www.nullenvoid.com/mono/wiki/index.php/WineSamples">WineSamples</a>
|
||||
page on the <a
|
||||
href="http://www.nullenvoid.com/mono/wiki/">Mono Wiki</a>.
|
||||
|
||||
A new cvs module called `winforms' has been created that
|
||||
contains the source code for the samples. To run the samples,
|
||||
you can install the WineLib packages available from our <a
|
||||
href="download.html">download page</a>.
|
||||
|
||||
@item Aug 5th, 2003: New Apache Module architecture: 1.3 and 2.x supported
|
||||
|
||||
Gonzalo rearchitected our Apache module for hosting Mono and
|
||||
ASP.NET. The previous incarnation hosted a Mono runtime on
|
||||
each Apache process, which lead to a slow setup for webforms.
|
||||
The new setup uses a shared mono process for all the incoming
|
||||
requests. Daniel later improved up the new architecture and
|
||||
added dual support, so now in addition to Apache 2.x, we
|
||||
support Apache 1.3 with the same codebase.
|
||||
|
||||
The new code is available on CVS, on module `mod_mono', and
|
||||
now requires an XSP installation to be available.
|
||||
|
||||
@item Aug 4th, 2003: Ximian acquired by Novell.
|
||||
|
||||
Today <a href="http://www.novell.com">Novell</a> acquired <a
|
||||
href="http://www.ximian.com">Ximian</a>. The press release is
|
||||
available <a
|
||||
href="http://www.ximian.com./about_us/press_center/press_releases/index.html?pr=novell">here</a>.
|
||||
|
||||
Mono and Gnome form an integral part of the Novell strategy.
|
||||
|
||||
@item Jul 30th, 2003: Remoting.CORBA, Managed XSLT.
|
||||
|
||||
Today Lluis announced that Mono CVS contains all the fixes to
|
||||
run <a
|
||||
href="http://remoting-corba.sourceforge.net/">Remoting.CORBA</a>:
|
||||
both client and server channels work; We are interested in people
|
||||
testing it with other ORBs.
|
||||
|
||||
Ben checked-in today his managed implementation of Xslt that
|
||||
we mentioned on Jul 19th; This uncovered various limitations
|
||||
on the XPath implementation, which Piers has swifly removed.
|
||||
Monodoc, NUnit and our Corcompare work with it. Since this is
|
||||
implementation is not completed yet, we still support the
|
||||
libxslt-based version by default. For more details on how to
|
||||
try the new XSLT implementation, see <a
|
||||
href="http://lists.ximian.com/archives/public/mono-devel-list/2003-July/001681.html">Ben's
|
||||
post</a>
|
||||
|
||||
@item Jul 27th, 2003: Wine packages and Daily Snapshots
|
||||
|
||||
MonoWine packages (used to run System.Windows.Forms) software
|
||||
are now available from our (<a
|
||||
href="download.html">download</a> page). You can track the
|
||||
progress on our <a
|
||||
href="http://www.nullenvoid.com/mono/wiki/index.php/WineSamples">Wiki
|
||||
page.</a>
|
||||
|
||||
We're now building daily snapshots of Mono. They come in
|
||||
three distinct flavors:
|
||||
|
||||
<ul>
|
||||
* mono snapshot tarballs - These are 'release-style' tarballs and
|
||||
contain everything necessary to setup a new
|
||||
installation from scratch. This includes the Mono
|
||||
runtime and all the assemblies we distribute.
|
||||
|
||||
* monocharge tarballs - These tarballs contain only
|
||||
the assemblies built on that day.
|
||||
|
||||
* monolite tarballs - These tarballs contain a copy of
|
||||
'corlib.dll', 'mcs.exe', 'System.dll', 'System.Xml.dll' and
|
||||
'Mono.CSharp.Debugger.dll'. They can be used to
|
||||
re-bootstrap an out-of-sync installation.
|
||||
</ul>
|
||||
|
||||
The daily builds are availble here: <a href="http://go-mono.com/daily">http://go-mono.com/daily</a>
|
||||
|
||||
If you find that the builds are broken, please notify Duncan.
|
||||
|
||||
@item Jul 19th, 2003: Recent developments
|
||||
|
||||
Since Mono has matured, we have limited the news on the site
|
||||
to major accomplishments that are finished, but this week, it
|
||||
is worth devoting some time to talk about some of the
|
||||
work-in-progress projects that are progressing.
|
||||
|
||||
Jackson has added support to the IL assembler for generics as
|
||||
well as to the PEAPI library, and it has assembled its first
|
||||
generic program. Support for handling images with generics
|
||||
has been on our file format reader for a while, but the JIT
|
||||
engine is still incomplete.
|
||||
|
||||
On the XSLT world, Atsushi and Ben continue to make big
|
||||
improvements. Ben recently got the prototype managed XSLT
|
||||
implementation to run its first stylesheet. Although
|
||||
currently Mono uses libxslt to implement the System.Xml.Xsl
|
||||
namespace, to have a fully .NET compliant implementation we
|
||||
will need a managed version, and this is the beginning of it.
|
||||
|
||||
Lluis recently posted an update on the <a
|
||||
href="http://lists.ximian.com/archives/public/mono-devel-list/2003-July/001550.html">state
|
||||
of WSDL</a> in Mono. Now that the web services runtime is
|
||||
ready, the WSDL compiler becomes more important as a
|
||||
development tool.
|
||||
|
||||
Atsushi continues his work on the DTD validating reader in
|
||||
System.Xml, as well as improving our XML Schema support.
|
||||
|
||||
@item Jul 14th, 2003: New build system; IPV6 support.
|
||||
|
||||
Peter Williams has contributed a new build system that
|
||||
addresses many of the annoyance we had with our previous build
|
||||
system. He has worked on this for a few weeks, and Gonzalo
|
||||
helped test it and get it into CVS. We no longer have the
|
||||
historical dual build system: make for Unix and nant for
|
||||
Windows.
|
||||
|
||||
This system also offers the opportunity to compile our class
|
||||
libraries with different profiles (.NET 1.0, .NET 1.1 and the
|
||||
various ECMA subsets).
|
||||
|
||||
Peter explains the new build system <a
|
||||
href="http://lists.ximian.com/archives/public/mono-devel-list/2003-July/001506.html">here</a>
|
||||
|
||||
Jerome's IPV6 code has been checked into CVS; With Peter's new
|
||||
build system, we will be able to expose it (as part of the
|
||||
NET_1_1 build).
|
||||
|
||||
@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
|
||||
@@ -1526,6 +956,4 @@
|
||||
|
||||
<h2>Older News</h2>
|
||||
|
||||
Click <a href="oldnews.html">here</a> to see the olds news.
|
||||
|
||||
|
||||
Click <a href="oldnews.html">here</a> to see the olds news.
|
||||
+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
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
+16
-20
@@ -9,7 +9,6 @@
|
||||
* <a href="#Oberon">Oberon</a>
|
||||
* <a href="#Forth">Forth</a>
|
||||
* <a href="#mbas">Mono Basic</a> (Mono's VB.NET compiler)
|
||||
* <a href="#dotlist">dotLisp</a>
|
||||
</ul>
|
||||
|
||||
Languages which are known to run, but we have not done a
|
||||
@@ -85,9 +84,9 @@
|
||||
** Component Pascal
|
||||
|
||||
The Component Pascal compiler: <a
|
||||
href="http://www.citi.qut.edu.au/research/plas/projects/cp_files/cpnet.html">Home
|
||||
href="http://www2.fit.qut.edu.au/CompSci/PLAS/ComponentPascal">Home
|
||||
Page</a>, you can <a
|
||||
href="http://www.citi.qut.edu.au/research/plas/projects/cp_files/cpdownload.html">
|
||||
href="http://www2.fit.qut.edu.au/CompSci/PLAS/ComponentPascal/gpcp1.1.4-netRTM.zip">
|
||||
download it</a>
|
||||
|
||||
<a name="Forth">
|
||||
@@ -111,22 +110,10 @@
|
||||
<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">
|
||||
** dotLisp
|
||||
|
||||
DotLisp is available from: <a
|
||||
href="http://sourceforge.net/projects/dotlisp/">http://sourceforge.net/projects/dotlisp/</a>
|
||||
|
||||
<a name="JavaScript">
|
||||
* Java Script
|
||||
|
||||
Cesar is working on Mono's implementation of JScript, the code
|
||||
is available on CVS on module `mcs'.
|
||||
|
||||
* Missing languages
|
||||
|
||||
Here is a list of a few languages that we would like to see
|
||||
@@ -135,6 +122,19 @@
|
||||
implementing or adapting a compiler for any of these
|
||||
languages:
|
||||
|
||||
<a name="JavaScript">
|
||||
* Java Script
|
||||
|
||||
The Mozilla project has an implementation of JavaScript
|
||||
written in Java called <a
|
||||
href="http://www.mozilla.org/rhino/">Rhino</a>.
|
||||
|
||||
You could port this code from Java to C#.
|
||||
|
||||
Note that since JavaScript allows for evaluation at runtime,
|
||||
the compiler has to be built as a class that can be invoked at
|
||||
runtime.
|
||||
|
||||
<a name="c">
|
||||
* C
|
||||
|
||||
@@ -152,10 +152,6 @@
|
||||
<a name="Java">
|
||||
* Java
|
||||
|
||||
Java bytecode can run directly on Mono using the <a
|
||||
href="http://www.ikvm.net">IKVM</a> java virtual machine for
|
||||
.NET.
|
||||
|
||||
We have a <a href="java.html">separate page</a> for Java.
|
||||
|
||||
|
||||
@@ -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>
|
||||
@@ -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,394 +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>
|
||||
|
||||
<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>
|
||||
-194
@@ -1,194 +0,0 @@
|
||||
* Mono hacking TODO list
|
||||
|
||||
From time to time people that want to contribute to Mono ask
|
||||
on the mailing list what they can help with. The generic
|
||||
answer is always:
|
||||
<ul>
|
||||
* Write documentation.
|
||||
* Write regression tests.
|
||||
* Complete the implementations of the class libraries.
|
||||
* Help fix the bugs filed in our bugzilla database.
|
||||
</ul>
|
||||
|
||||
The proposed tasks are very important for the Mono project and
|
||||
are suitable for people that can dedicate even just an hour
|
||||
per week to contribute. But some people may need something
|
||||
more focused to work on, such as students that want to do a
|
||||
thesis on their contribution to Mono. For such people (and
|
||||
also for professors who want ideas for thesis regarding JIT or
|
||||
VM technologies), here is a list of tasks that need attention.
|
||||
|
||||
The estimated time to complete any of the tasks is between 1
|
||||
week to several months to accomodate for different hacking
|
||||
possibilities.
|
||||
|
||||
Note on the time estimates: they are very rough estimates, a
|
||||
smart and dedicated hacker can complete the tasks in half of
|
||||
the minimum time, a part-time hacker that also has a social
|
||||
life can take more than double the max time, but there's
|
||||
nothing to worry as long as progress is being done.
|
||||
|
||||
If some people (or group of people) want to take on a task,
|
||||
they should write to the mono-devel mailing list and in the
|
||||
relative bugzilla bug report. Discussions about how to
|
||||
implement a feature or additional information on the task
|
||||
should be mailed to the list or in the bugzilla report as well
|
||||
so that people can keep informed on the progress or have the
|
||||
information needed to start contributing.
|
||||
|
||||
Mono is an excellent platform for research on JITs, virtual
|
||||
machines and specifically the CLR because it provides an
|
||||
advanced free software implementation that can be used as a
|
||||
basis for more optimizations, new approaches to problems and
|
||||
new features.
|
||||
|
||||
There are different areas of interest where high-level
|
||||
contributions can be made:
|
||||
|
||||
<ul>
|
||||
* <b>JIT compiler</b>: tasks can be: adding more optimizations, reducing
|
||||
compile time, porting to different architectures.
|
||||
|
||||
* <b>AOT compiler</b>: optimizing the compiler output and the AOT loader,
|
||||
better support for multiple application domains.
|
||||
|
||||
* <b>VM runtime</b>: optimizing the runtime data structures, experimenting with
|
||||
different garbage collectors, integration with different component models.
|
||||
|
||||
* <b>Class library</b>: many opportunities in the implementation of regular
|
||||
expressions, Xml related technologies (XPath, XLST, etc).
|
||||
|
||||
* <b>Compilers</b>: writing compilers, interpreters and runtimes for langauges
|
||||
so that they run on the CLR (using Reflection.Emit support, for example).
|
||||
</ul>
|
||||
|
||||
Happy hacking!
|
||||
|
||||
<table border=1 cellspacing="0" cellpadding="0">
|
||||
<tr>
|
||||
<th>Area<th>Description<th>Difficulty<th>Time estimate<th>Bugzilla ID
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Runtime (mono/metadata)
|
||||
<td>Optimize method vtable. Currently all the methods in a class
|
||||
are added to the method vtable, including static and non-virtual methods.
|
||||
This makes vtables bigger and the instructions to access them are longer,
|
||||
increasing also code size. Some code in metadata/icall.c and maybe also some
|
||||
remoting code may depend on the current layout: such code should be fixed as well.
|
||||
<td>Medium
|
||||
<td>1-2 weeks
|
||||
<td>not assigned
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>System assembly (mcs/class/System/)
|
||||
<td>Implement the IL-based regular expression engine. Instead of
|
||||
intepreting the regular expression pattern, a method is created at runtime using
|
||||
Reflection.Emit. This makes for faster pattern matching because there is no
|
||||
intepreter overhead and the matching code is jitted to fast native code.
|
||||
Bonus points if the compiled regular expression is compatible with the ones generated
|
||||
by the MS runtime.
|
||||
<td>Medium-hard (thesis subject)
|
||||
<td>2-4 months
|
||||
<td>not assigned
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>JIT (mono/mini/)
|
||||
<td>Implement common subexpression elimination.
|
||||
Global and local common subexpression elimination needs to be implemented
|
||||
to achieve better performance. The local case is easier and may take just one month.
|
||||
It should be implemented in the context of the SSA framework (mini/ssa.c).
|
||||
<td>Hard (thesis subject)
|
||||
<td>2-4 months
|
||||
<td>not assigned
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>JIT (mono/mini/)
|
||||
<td>Optimize AOT compiler output.
|
||||
Currently the code generated by the AOT compiler may be significantly slower than
|
||||
jitted code. This is mostly because the AOT code supports multiple application domains
|
||||
and some values that are constant at JIT-time are not constant at AOT-time. It may be
|
||||
needed to write a simple dynamic linker and/or binary object writer. Bonus poinst if
|
||||
it supports ELF, PE/COFF and mach-O binary formats. A possible idea for improvements
|
||||
is also the use of appdomain ID-indexed tables to get at the appdomain specific data.
|
||||
<td>Medium-hard (thesis subject)
|
||||
<td>3-6 months
|
||||
<td>not assigned
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>JIT (mono/mini/)
|
||||
<td>Implement generics support.
|
||||
We need to add support for the additional instructions and change existing ones to
|
||||
support the generics requirements.
|
||||
<td>Medium-hard
|
||||
<td>2-3 months
|
||||
<td>not assigned
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>JIT (mono/mini/)
|
||||
<td>Port the JIT to additional architectures.
|
||||
Currently ports are in the works for ppc, arm, sparc, s390. None of the ports
|
||||
are as feature-complete as the x86 one, yet, so help is needed in getting them
|
||||
up to speed. Ports to more architectures are welcome as well.
|
||||
<td>Medium-hard
|
||||
<td>3-6 months per arch
|
||||
<td>not assigned
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Runtime and JIT (mono/metadata and mono/mini/)
|
||||
<td>Add support for COM and/or XPCOM and/or ORBit.
|
||||
We need a way to seamlessy use existing component technologies inside the mono runtime.
|
||||
The COM support needs to match the MS runtime behaviour and is targeted at windows systems.
|
||||
XPCOM and ORBit support are important on Unix platforms. Bonus points for developing
|
||||
the runtime support so that different component systems can be used at the same time.
|
||||
<td>Medium-hard (thesis subject)
|
||||
<td>3-4 months for each
|
||||
<td>not assigned
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Runtime and JIT (mono/metadata and mono/mini/)
|
||||
<td>Implement support for Code Access Security.
|
||||
Support needs to be added to the JIT and the runtime to ensure
|
||||
code that executes privileged operations is permitted to do so.
|
||||
The task includes loading the security information from metadata,
|
||||
collecting evidence, inserting calls to the permission objects,
|
||||
stack walking to collect security info.
|
||||
<td>Medium-hard (thesis subject)
|
||||
<td>4-5 months
|
||||
<td>not assigned
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Runtime and JIT (mono/metadata and mono/mini/)
|
||||
<td>Implement support for a generational GC.
|
||||
We're currently using a conservative non-moving GC.
|
||||
Support for a generational and moving GC requires changes to the JIT
|
||||
(to record locations in frames as well as registers that may contain
|
||||
pointers to GC-allocated memory) and to the runtime code (when
|
||||
objects are manipulated directly we should make sure they are pinned
|
||||
and reachable by the GC also in the C unmanaged code). Code from an existing
|
||||
precise GC such as the ORP one could be reused or a new GC may be developed
|
||||
(increasing the estimated development time).
|
||||
<td>Hard (thesis subject)
|
||||
<td>6-8 months
|
||||
<td>not assigned
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Compilers for dynamic languages
|
||||
<td>Write a IL compiler and runtime support for dynamic languages like
|
||||
Python, Perl, Ruby, PHP.
|
||||
<td>Medium-hard (thesis subject)
|
||||
<td>6-12 months
|
||||
<td>not assigned
|
||||
</tr>
|
||||
|
||||
</table>
|
||||
|
||||
@@ -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);
|
||||
}
|
||||
|
||||
@@ -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);
|
||||
}
|
||||
|
||||
@@ -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);
|
||||
}
|
||||
|
||||
+14
-11
@@ -10,7 +10,7 @@
|
||||
|
||||
<li>Works with Oracle 8i</li>
|
||||
|
||||
<li>May work with Oracle 9i</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>
|
||||
@@ -19,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
|
||||
@@ -62,12 +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# versions in cvs. Only works with
|
||||
simple character data though.</li>
|
||||
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>
|
||||
|
||||
@@ -79,8 +83,7 @@
|
||||
<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 (WORKING</li>
|
||||
<li>Support for Oracle 9i (UNKNOWN)</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>
|
||||
@@ -93,7 +96,7 @@
|
||||
<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,
|
||||
@@ -126,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);
|
||||
}
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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>.
|
||||
|
||||
|
||||
|
||||
+7
-33
@@ -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);
|
||||
}
|
||||
@@ -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);
|
||||
}
|
||||
|
||||
@@ -1,15 +0,0 @@
|
||||
#!/bin/sh
|
||||
|
||||
MANAGED_CALLS=`gdb -silent $1 -pid $2 << EOF | awk '/.* in \?\? \(\)/ {printf("call print_method_from_ip(%s)\n", $2);}'
|
||||
set height 0
|
||||
thread apply all bt
|
||||
quit
|
||||
EOF`
|
||||
|
||||
gdb -silent $1 -pid $2 << EOF
|
||||
set height 0
|
||||
thread apply all bt
|
||||
$MANAGED_CALLS
|
||||
quit
|
||||
EOF
|
||||
|
||||
@@ -10,6 +10,8 @@
|
||||
|
||||
** EOG component
|
||||
|
||||
** XmlStorageSystem component
|
||||
|
||||
* Gtk# related projects
|
||||
|
||||
Gnome Canvas Bindings.
|
||||
|
||||
+7
-33
@@ -18,7 +18,7 @@
|
||||
standard GNOME interfaces for easily creating reusable,
|
||||
language independent components, controls and compound
|
||||
documents. This technology is known as <a
|
||||
href="http://developer.ximian.com/articles/whitepapers/bonobo">Bonobo</a>.
|
||||
href="http://developer.ximian.com/tech/bonobo.html">Bonobo</a>.
|
||||
Interfaces to Bonobo exist for C, Perl, Python, and
|
||||
Java.
|
||||
|
||||
@@ -134,51 +134,25 @@
|
||||
|
||||
** What makes up Mono?
|
||||
|
||||
There are various pieces that make up Mono today:
|
||||
There are various pieces that will make up Mono:
|
||||
|
||||
<ul>
|
||||
* A C# compiler.
|
||||
|
||||
* The Virtual Execution System: that has the
|
||||
* The Virtual Execution System: that will have the
|
||||
Just-in-Time compiler, garbage collector, loader,
|
||||
threading engine.
|
||||
|
||||
A byte code interpreter is provided for quickly
|
||||
A byte code interpreter will be provided for quickly
|
||||
porting Mono to new systems and debugging the JIT
|
||||
purposes, but it is not intended to be the ideal
|
||||
execution environment.
|
||||
|
||||
* An implemenation of the .NET class libraries:
|
||||
Remoting, Reflection, Reflection.Emit, Xml, Xpath,
|
||||
Xslt, Xml Serialization, Web Services support.
|
||||
* An implemenation of the .NET class library.
|
||||
|
||||
* Cross platform class libraries for data access:
|
||||
Postgress, MySQL, DB2, TDS, Sybase, Oracle, ODBC and
|
||||
Gnome's GDA.
|
||||
* Visual development tools.
|
||||
|
||||
* Unix class libraries: Mono.Posix
|
||||
|
||||
* Gnome-specific class libraries: The Gtk# family.
|
||||
|
||||
* A code pre-compiler to generate native code ahead of
|
||||
time.
|
||||
|
||||
* Gtk# a toolkit to develop GNOME applications on Unix
|
||||
and Windows.
|
||||
|
||||
* An implementation of the Remoting infrastructure in
|
||||
.NET
|
||||
</ul>
|
||||
|
||||
Other work-in-progress components:
|
||||
|
||||
<ul>
|
||||
* A VB.NET compiler and JScript compilers are in the works.
|
||||
|
||||
* Web services on the server side.
|
||||
|
||||
* We are planning to include Remoting.CORBA as part of
|
||||
Mono standard distribution.
|
||||
* A CIL GCC frontend.
|
||||
</ul>
|
||||
|
||||
** Why use GNOME components?
|
||||
|
||||
+4
-4
@@ -11,8 +11,8 @@
|
||||
|
||||
The <a href="http://msdn.microsoft.com/net">Microsoft.NET site.</a>
|
||||
|
||||
The Microsoft .NET Framework can be downloaded <a
|
||||
href="http://msdn.microsoft.com/library/default.asp?url=/downloads/list/netdevframework.asp">here</a>
|
||||
The Microsoft .NET Framework 1.0 can be downloaded <a
|
||||
href="http://msdn.microsoft.com/downloads/default.asp?url=/downloads/sample.asp?url=/msdn-files/027/000/976/msdncompositedoc.xml&frame=true">here</a>
|
||||
|
||||
New methods that are not documented in 1.0, are documented <a
|
||||
href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/framewrkaddend.asp">here</a>
|
||||
@@ -87,8 +87,8 @@
|
||||
You can get the documentation for the ECMA specs from:
|
||||
|
||||
<ul>
|
||||
* <a href="http://www.ecma-international.org/publications/standards/ECMA-334.HTM">C# Language Specification</a>
|
||||
* <a href="http://www.ecma-international.org/publications/standards/ECMA-335.HTM">Common Language Infrastructure</a>
|
||||
* <a href="http://www.ecma.ch/ecma1/STAND/ecma-334.htm">C# Language Specification</a>
|
||||
* <a href="http://www.ecma.ch/ecma1/STAND/ecma-335.htm">Common Language Infrastructure</a>
|
||||
</ul>
|
||||
|
||||
|
||||
|
||||
+20
-60
@@ -9,17 +9,18 @@
|
||||
We currently have two runtimes:
|
||||
|
||||
<ul>
|
||||
* <b>mono:</b> Our Just-in-Time and Ahead-of-Time code
|
||||
generator for maximum performance.
|
||||
* <b>mono:</b> The Just In Time compiler implemented
|
||||
using a BURS instruction selector. We only support
|
||||
x86 machines in the JIT engine at this point.
|
||||
|
||||
* <b>mint:</b> The Mono interpreter. This is an
|
||||
easy-to-port runtime engine.
|
||||
</ul>
|
||||
|
||||
We are using the Boehm conservative garbage collector.
|
||||
We are using the Bohem conservative garbage collector.
|
||||
|
||||
The Mono runtime can be used as a stand-alone process, or it
|
||||
can be <a href="embedded-api.html">embedded into applications</a> (see
|
||||
can be <a href="embedded-api">embedded into applications</a> (see
|
||||
the documentation in mono/samples/embed for more details).
|
||||
|
||||
Embedding the Mono runtime allows applications to be extended
|
||||
@@ -30,52 +31,12 @@
|
||||
href="http://primates.ximian.com/~lupus/slides/jit/">slides
|
||||
here</a>
|
||||
|
||||
** Current JIT Engine: technical details (<b>updated, June 28th, 2003</b>)
|
||||
** Current JIT Engine: technical details (<b>updated, July 8th, 2002</b>)
|
||||
|
||||
We have re-written our JIT compiler. We wanted to support a
|
||||
number of features that were missing:
|
||||
|
||||
<ul>
|
||||
* Ahead-of-time compilation.
|
||||
|
||||
The idea is to allow developers to pre-compile their code
|
||||
to native code to reduce startup time, and the working
|
||||
set that is used at runtime in the just-in-time compiler.
|
||||
|
||||
Although in Mono this has not been a visible problem, we
|
||||
wanted to pro-actively address this problem.
|
||||
|
||||
When an assembly (a Mono/.NET executable) is installed in
|
||||
the system, it would then be possible to pre-compile the
|
||||
code, and have the JIT compiler tune the generated code
|
||||
to the particular CPU on which the software is
|
||||
installed.
|
||||
|
||||
This is done in the Microsoft.NET world with a tool
|
||||
called ngen.exe
|
||||
|
||||
* Have a good platform for doing code optimizations.
|
||||
|
||||
The design called for a good architecture that would
|
||||
enable various levels of optimizations: some
|
||||
optimizations are better performed on high-level
|
||||
intermediate representations, some on medium-level and
|
||||
some at low-level representations.
|
||||
|
||||
Also it should be possible to conditionally turn these on
|
||||
or off. Some optimizations are too expensive to be used
|
||||
in just-in-time compilation scenarios, but these
|
||||
expensive optimizations can be turned on for
|
||||
ahead-of-time compilations or when using profile-guided
|
||||
optimizations on a subset of the executed methods.
|
||||
|
||||
* Reduce the effort required to port the Mono code
|
||||
generator to new architectures.
|
||||
|
||||
For Mono to gain wide adoption in the Unix world, it is
|
||||
necessary that the JIT engine works in most of today's
|
||||
commercial hardware platforms.
|
||||
</ul>
|
||||
The JIT engine uses a code-generator generator approach for
|
||||
compilation. Given the properties of CIL byte codes, we can
|
||||
take full advantage of a real instruction selector for our
|
||||
code generator.
|
||||
|
||||
The JIT engine implements a number of optimizations:
|
||||
|
||||
@@ -86,7 +47,7 @@
|
||||
|
||||
* Inlining.
|
||||
|
||||
* Constant folding, copy propagation, dead code elimination.
|
||||
* Constant folding.
|
||||
|
||||
Although compilers typically do
|
||||
constant folding, the combination of inlining with
|
||||
@@ -95,9 +56,6 @@
|
||||
* Linear scan register allocation. In the past,
|
||||
register allocation was our achilles heel, but now
|
||||
we have left this problem behind.
|
||||
|
||||
* SSA-based framework. Various optimizations are
|
||||
implemented on top of this framework
|
||||
</ul>
|
||||
|
||||
There are a couple of books that deal with this technique: "A
|
||||
@@ -106,13 +64,7 @@
|
||||
technical description of <a
|
||||
href="http://research.microsoft.com/copyright/accept.asp?path=http://www.research.microsoft.com/~drh/pubs/iburg.pdf&pub=ACM">lbrug</a>.
|
||||
|
||||
The new JIT engines uses three intermediate representations:
|
||||
the source is the CIL which is transformed into a forest of
|
||||
trees; This is fed into a BURS instruction selector that
|
||||
generates the final low-level intermediate representation.
|
||||
|
||||
The instruction selector is documented in the following
|
||||
papers:
|
||||
A few papers that describe the instruction selector:
|
||||
|
||||
<ul>
|
||||
* <a href="http://research.microsoft.com/copyright/accept.asp?path=http://www.research.microsoft.com/~drh/pubs/interface.pdf&pub=wiley">A code generation interface for ANSI C</a>
|
||||
@@ -122,6 +74,14 @@
|
||||
|
||||
</ul>
|
||||
|
||||
** New JIT engine.
|
||||
|
||||
We are working on a new JIT engine. The new JIT engine
|
||||
focuses on portability and in two intermediate representations
|
||||
that simplify the development of optimizations. This together
|
||||
with the Ahead-of-Time compilation will allow developers to
|
||||
deploy applications that match the speed of natively compiled code.
|
||||
|
||||
** Garbage Collection
|
||||
|
||||
We are using the Boehm conservative GC. We might consider
|
||||
|
||||
+4
-45
@@ -51,14 +51,6 @@
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
** Eclipse running with Mono
|
||||
|
||||
Zoltan Varga made the Java VM for .NET <a
|
||||
href="http://www.ikvm.net">IKVM</a> run <a
|
||||
href="http://www.eclipse.org">Eclipse</a>, the IBM Open Source IDE.
|
||||
|
||||
<a href="images/ikvm-screenshot.png"><img src="images/ikvm-screenshot-thumb.png"></a>
|
||||
|
||||
** Mono Basic
|
||||
|
||||
The Mono Basic compiler ships with the Mono distribution.
|
||||
@@ -135,27 +127,14 @@
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
** Type Reflector
|
||||
** SkyNET
|
||||
|
||||
Type Reflector is a tool included in Mono to inspect your assemblies.
|
||||
SkyNET is written in C# and uses GTK# for displaying a star chart.
|
||||
|
||||
<table border=1>
|
||||
<tr>
|
||||
<td>
|
||||
<img src="images/type-reflector.png">
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
** Object Browser
|
||||
|
||||
Radek Doulik's Object Browser (in Mono CVS) is a useful tool
|
||||
to inspect existing assemblies and their source code:
|
||||
|
||||
<table border=1>
|
||||
<tr>
|
||||
<td>
|
||||
<img src="images/Screenshot-ObjectBrowserDemo.png">
|
||||
<img src="http://go-mono.com/images/skynet.png">
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
@@ -164,14 +143,6 @@
|
||||
|
||||
Windows.Forms running with Wine on Linux:
|
||||
|
||||
<table border=1>
|
||||
<tr>
|
||||
<td>
|
||||
<a href="http://go-mono.com/images/monomdi.jpg"><img src="http://go-mono.com/images/monomdi-thumb.jpg"></a>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<table border=1>
|
||||
<tr>
|
||||
<td>
|
||||
@@ -179,7 +150,7 @@
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
|
||||
** Mono running on the iPaq
|
||||
|
||||
<table border=1>
|
||||
@@ -215,15 +186,3 @@
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
** SkyNET
|
||||
|
||||
SkyNET is written in C# and uses GTK# for displaying a star chart.
|
||||
|
||||
<table border=1>
|
||||
<tr>
|
||||
<td>
|
||||
<img src="http://go-mono.com/images/skynet.png">
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
+2
-2
@@ -172,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);
|
||||
}
|
||||
|
||||
+3
-3
@@ -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);
|
||||
}
|
||||
|
||||
+2
-2
@@ -110,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);
|
||||
}
|
||||
|
||||
+2
-2
@@ -115,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);
|
||||
}
|
||||
|
||||
+49
-10
@@ -24,7 +24,7 @@
|
||||
<b>mcs/class/doc/TemplateTest.cs</b>
|
||||
|
||||
Save a copy of this file in the appropriate test subdirecty
|
||||
(see below), and replace all the {text} markers with
|
||||
(see below), and replace all the [text] markers with
|
||||
appropriate code. Comments in the template are there to guide
|
||||
you. You should also look at existing tests to see how other
|
||||
people have written them.
|
||||
@@ -41,22 +41,29 @@
|
||||
the appropriate sub-directory under Test for the class you are
|
||||
testing.
|
||||
|
||||
Once your test class is complete, you need to add it to the
|
||||
AllTests.cs file in the same directory as your new test. Add a
|
||||
call to "suite.AddTest()" passing the name of your new test
|
||||
class's suite property as the parameter. You will see
|
||||
examples in the AllTests.cs file, so just copy and paste
|
||||
inside there.
|
||||
|
||||
Once all of that is done, you can do a 'make test' from the top mcs
|
||||
directory. Your test class will be automagically included in the
|
||||
build and the tests will be run along with all the others.
|
||||
|
||||
* Tips on writing Unit tests.
|
||||
|
||||
You should look at the <a href="http://nunit.org">NUnit documentation</a>,
|
||||
as it is a fantastic product, and includes fantastic documentation,
|
||||
but here are some tips for those of you who are already reading
|
||||
You should look at the NUnit documentation, as it is a
|
||||
fantastic product, and includes fantastic documentation, but
|
||||
here are some tips for those of you who are already reading
|
||||
this web page.
|
||||
|
||||
|
||||
** Provide an unique error message for Assert()
|
||||
|
||||
Include an unique message for each Assert() so that when the assert
|
||||
fails, it is trivial to locate it in the source. Otherwise, it may be
|
||||
fails, it is trivial to locate the failing one. Otherwise, it may be
|
||||
difficult to determine which part of the test is failing. A good way
|
||||
to ensure unique messages is to use something like #A01, #A02 etc.
|
||||
|
||||
@@ -97,10 +104,43 @@
|
||||
AssertEquals ("A01", myTicks[0], t1.Ticks);
|
||||
</pre>
|
||||
|
||||
** Constructors
|
||||
|
||||
When writing your testcase, please make sure to provide a constructor
|
||||
which takes no arguments:
|
||||
|
||||
<pre>
|
||||
public class DateTimeTest : TestCase
|
||||
{
|
||||
|
||||
public DateTimeTest() : base ("[MonoTests.System.DateTimeTest]") {}
|
||||
public DateTimeTest (string name): base(name) {}
|
||||
|
||||
public static ITest Suite
|
||||
{
|
||||
get {
|
||||
TestSuite suite = new TestSuite ();
|
||||
return suite;
|
||||
}
|
||||
}
|
||||
}
|
||||
</pre>
|
||||
|
||||
** Namespace
|
||||
|
||||
Please keep the namespace within each test directory consistent - all
|
||||
tests which are referenced in the same AllTests.cs must be in the same
|
||||
namespace. Of course you can use subnamespaces as you like -
|
||||
especially for subdirectories of your testsuite.
|
||||
|
||||
For instance, if your AllTests.cs is in namespace "MonoTests" and you
|
||||
have a subdirectory called "System", you can put all the tests in that
|
||||
dir into namespace "MonoTests.System".
|
||||
|
||||
** Test your test with the Microsoft runtime
|
||||
|
||||
If possible, try to run your testsuite with the Microsoft runtime on
|
||||
.NET on Windows and make sure all tests in it pass. This is especially
|
||||
Windows and make sure all tests in it pass. This is especially
|
||||
important if you're writing a totally new testcase - without this
|
||||
check you can never be sure that your testcase contains no bugs ....
|
||||
|
||||
@@ -111,10 +151,9 @@
|
||||
result when run with the Microsoft runtime - either because there is a
|
||||
bug in their runtime or something is misleading or wrong in their
|
||||
documentation. In this case, please put a detailed description of the
|
||||
problem to mcs/class/doc/API-notes and do also report it to the
|
||||
<a href="mailing-lists">mailing list</a> - we'll forward this to the
|
||||
Microsoft people from time to time to help them fix their documentation
|
||||
and runtime.
|
||||
problem to mcs/class/doc/API-notes and do also report it to the list -
|
||||
we'll forward this to the Microsoft people from time to time to help
|
||||
them fix their documentation and runtime.
|
||||
|
||||
** Unit tests.
|
||||
|
||||
|
||||
+1
-8
@@ -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,13 +17,11 @@
|
||||
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
|
||||
0,Contributing,contributing.html,contributing.src
|
||||
1,Hackers,hackers.html,hackers.src
|
||||
1,Documentation,documentation.html,documentation.src
|
||||
1,Class Docs,classlib-doc.html,classlib-doc.src
|
||||
1,Test Suite,testing.html,testing.src
|
||||
1,Mono TODO,mono-todo.html,mono-todo.src
|
||||
1,Tools,tools.html,tools.src
|
||||
1,Porting,porting.html,porting.src
|
||||
2,PowerPC,ppc.html,ppc.src
|
||||
@@ -33,7 +29,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,Debugging,jit-debug.html,jit-debug.src
|
||||
0,Plans,plans.html,plans.src
|
||||
1,ADO.NET,ado-net.html,ado-net.src
|
||||
1,Drawing,drawing.html,drawing.src
|
||||
2,ProviderFactory,provider-factory.html,provider-factory.src
|
||||
2,Firebird Interbase,firebird.html,firebird.src
|
||||
2,IBM DB2,ibmdb2.html,ibmdb2.src
|
||||
@@ -55,7 +49,6 @@
|
||||
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
|
||||
@@ -69,7 +62,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
|
||||
|
||||
@@ -1 +0,0 @@
|
||||
*.xml
|
||||
+42
-78
@@ -1,31 +1,34 @@
|
||||
ifeq ($(findstring CYGWIN,$(shell uname)),)
|
||||
CSC=mcs
|
||||
RUN_MONO=mono
|
||||
else
|
||||
CSC=csc /nologo
|
||||
endif
|
||||
ROOT=C:/WINNT
|
||||
CSCRIPT = $(ROOT)/system32/cscript.exe
|
||||
CSC=csc
|
||||
|
||||
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/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 \
|
||||
@@ -40,51 +43,39 @@ OBJECTS= \
|
||||
deploy/mbas.html \
|
||||
deploy/mono-beginning.html \
|
||||
deploy/mono-contribution-howto.html \
|
||||
deploy/mono-todo.html \
|
||||
deploy/monodoc-xml.html \
|
||||
deploy/mysql.html \
|
||||
deploy/odbc.html \
|
||||
deploy/oledb.html \
|
||||
deploy/oracle.html \
|
||||
deploy/other.html \
|
||||
deploy/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/class-library.html \
|
||||
deploy/classlib-doc.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
|
||||
@@ -98,8 +89,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
|
||||
@@ -116,27 +106,24 @@ mono-beginning.xml: ../mono-beginning.xml
|
||||
cp ../mono-beginning.xml .
|
||||
|
||||
deploy/index.rss: mono-rss.exe ../index
|
||||
$(RUN_MONO) ./mono-rss.exe ../index deploy/index.rss
|
||||
./mono-rss.exe ../index deploy/index.rss
|
||||
|
||||
mono-rss.exe: mono-rss.cs rss.cs
|
||||
$(CSC) mono-rss.cs rss.cs
|
||||
|
||||
../team: render-team-page.exe team.xml
|
||||
$(RUN_MONO) ./render-team-page.exe team.xml "../team"
|
||||
./render-team-page.exe team.xml "../team"
|
||||
|
||||
render-team-page.exe: render-team-page.cs
|
||||
$(CSC) render-team-page.cs
|
||||
|
||||
clean:
|
||||
rm -f $(OBJECTS) $(patsubst deploy/%.html,src/%.src, $(OBJECTS)) src/*.xml src/*.html.in ../class-status-* ../class-status infos/*
|
||||
rm -f $(OBJECTS) $(patsubst deploy/%.html,src/%.src, $(OBJECTS)) src/*.xml src/*.html.in ../class-status-* ../class-status
|
||||
|
||||
push:
|
||||
cp -f $(NON_HTML_SOURCES) deploy
|
||||
cp ../mono-roadmap.html deploy
|
||||
#echo scp -P 2200 -r deploy/* www@www.go-mono.com:/web/cvsmodules/mono
|
||||
#(cd deploy; rsync --verbose --recursive --checksum --update --rsh='ssh' . [email protected]:/web/cvsmodules/mono )
|
||||
(cd deploy; rsync --verbose --recursive --checksum --update --rsh='ssh' . [email protected]:/web/cvsmodules/mono )
|
||||
|
||||
echo scp -P 2200 -r deploy/* [email protected]:/web/cvsmodules/mono
|
||||
(cd deploy; rsync --verbose --recursive --checksum --update --rsh='ssh -p 2200' . www@www.ximian.com:/web/cvsmodules/mono )
|
||||
|
||||
push2:
|
||||
scp -r deploy/* primates:public_html/xxx
|
||||
@@ -145,12 +132,10 @@ $(OBJECTS): $(patsubst deploy/%.html,src/%.src, $(OBJECTS))
|
||||
|
||||
#.PRECIOUS: $(patsubst deploy/%.html,src/%.src, $(OBJECTS))
|
||||
|
||||
transform.exe: transform.cs
|
||||
$(CSC) transform.cs
|
||||
|
||||
|
||||
.PRECIOUS: src/%.src
|
||||
src/%.src: ../% commands template.html.in makefile
|
||||
src/%.src: ../% commands makefile template.html.in
|
||||
perl htmlify $< > $@
|
||||
|
||||
.PRECIOUS: ../class-status-%
|
||||
@@ -159,41 +144,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 $(CORCOMPARE)/transform.js $(CORCOMPARE)/cormissing.xsl
|
||||
$(CSCRIPT) /nologo $(CORCOMPARE)/transform.js $< $(CORCOMPARE)/cormissing.xsl > $@
|
||||
|
||||
|
||||
.PRECIOUS: infos/%.xml
|
||||
infos/%.xml: ../../../mcs/class/lib/%.dll $(CORCOMPARE)/mono-api-info.exe
|
||||
$(RUN_MONO) $(CORCOMPARE)/mono-api-info.exe $< > $@ || (rm -f $@ && exit 1)
|
||||
|
||||
.PRECIOUS: src/%.xml
|
||||
src/%.xml: infos/%.xml $(CORCOMPARE)/mono-api-diff.exe
|
||||
$(RUN_MONO) $(CORCOMPARE)/mono-api-diff.exe masterinfos/$(notdir $<) $< > $@ || (rm -f $@ && exit 1)
|
||||
src/%.xml: ../../../mcs/class/lib/%.dll $(CORCOMPARE)/CorCompare.exe
|
||||
$(CORCOMPARE)/CorCompare.exe -x $@ $<
|
||||
|
||||
# corlib, corlib...
|
||||
infos/mscorlib.xml: ../../../mcs/class/lib/mscorlib.dll $(CORCOMPARE)/mono-api-info.exe
|
||||
$(RUN_MONO) $(CORCOMPARE)/mono-api-info.exe $(notdir $(basename $<)) > $@ || (rm -f $@ && exit 1)
|
||||
src/corlib.xml: ../../../mcs/class/lib/corlib_cmp.dll $(CORCOMPARE)/CorCompare.exe
|
||||
$(CORCOMPARE)/CorCompare.exe -f corlib -ms mscorlib -x $@ $<
|
||||
|
||||
src/corlib.xml: infos/mscorlib.xml $(CORCOMPARE)/mono-api-diff.exe
|
||||
$(RUN_MONO) $(CORCOMPARE)/mono-api-diff.exe masterinfos/mscorlib.xml $< > $@ || (rm -f $@ && exit 1)
|
||||
|
||||
# System
|
||||
infos/System.xml: ../../../mcs/class/lib/System.dll $(CORCOMPARE)/mono-api-info.exe
|
||||
$(RUN_MONO) $(CORCOMPARE)/mono-api-info.exe $(notdir $(basename $<)) > $@ || (rm -f $@ && exit 1)
|
||||
|
||||
src/System.xml: infos/System.xml $(CORCOMPARE)/mono-api-diff.exe
|
||||
$(RUN_MONO) $(CORCOMPARE)/mono-api-diff.exe masterinfos/System.xml $< > $@ || (rm -f $@ && exit 1)
|
||||
|
||||
# System.Xml
|
||||
infos/System.Xml.xml: ../../../mcs/class/lib/System.Xml.dll $(CORCOMPARE)/mono-api-info.exe
|
||||
$(RUN_MONO) $(CORCOMPARE)/mono-api-info.exe $(notdir $(basename $<)) > $@ || (rm -f $@ && exit 1)
|
||||
|
||||
src/System.Xml.xml: infos/System.Xml.xml $(CORCOMPARE)/mono-api-diff.exe
|
||||
$(RUN_MONO) $(CORCOMPARE)/mono-api-diff.exe masterinfos/System.Xml.xml $< > $@ || (rm -f $@ && exit 1)
|
||||
|
||||
src/System.DirectoryServices.xml: infos/System.DirectoryServices.xml $(CORCOMPARE)/mono-api-diff.exe
|
||||
$(RUN_MONO) $(CORCOMPARE)/mono-api-diff.exe masterinfos/System.DirectoryServices.xml $< > $@ || (rm -f $@ && exit 1)
|
||||
src/System.Security.xml: ../../../mcs/class/lib/System.Security_cmp.dll $(CORCOMPARE)/CorCompare.exe
|
||||
$(CORCOMPARE)/CorCompare.exe -f System.Security -ms System.Security -x $@ $<
|
||||
|
||||
../class-status: ../class-status.in
|
||||
cp -f $< $@
|
||||
|
||||
@@ -1 +0,0 @@
|
||||
*.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 {
|
||||
|
||||
+17
-185
@@ -12,34 +12,6 @@
|
||||
|
||||
<contributors xmlns="http://go-mono.org/team.xsd">
|
||||
|
||||
<contributor>
|
||||
|
||||
<name>
|
||||
|
||||
<first-name>Joel</first-name>
|
||||
|
||||
<last-name>Basson</last-name>
|
||||
|
||||
</name>
|
||||
|
||||
<e-mail>[email protected]</e-mail>
|
||||
|
||||
<image>none.png</image>
|
||||
|
||||
<location>Cape Town, South Africa</location>
|
||||
|
||||
<organization></organization>
|
||||
|
||||
<description>External Contributor</description>
|
||||
|
||||
<tasks>
|
||||
|
||||
<task>System.Windows.Forms Gtk</task>
|
||||
|
||||
</tasks>
|
||||
|
||||
</contributor>
|
||||
|
||||
<contributor>
|
||||
|
||||
<name>
|
||||
@@ -312,7 +284,7 @@
|
||||
|
||||
<e-mail>[email protected]</e-mail>
|
||||
|
||||
<location>Honolulu, Hawai`i</location>
|
||||
<location>Kansas City</location>
|
||||
|
||||
<tasks>
|
||||
|
||||
@@ -454,9 +426,9 @@
|
||||
|
||||
<task>NUnit1 -> NUnit2 conversion</task>
|
||||
|
||||
<task>Mono Handbook, Documentation</task>
|
||||
<task>Stubbing</task>
|
||||
|
||||
<task>DiaCanvas#</task>
|
||||
<task>Mono Handbook work</task>
|
||||
|
||||
<task>Various fixes</task>
|
||||
|
||||
@@ -648,7 +620,7 @@
|
||||
|
||||
</name>
|
||||
|
||||
<e-mail>jackson@ximian.com</e-mail>
|
||||
<e-mail>jackson@latitudegeo.com</e-mail>
|
||||
|
||||
<image>jackson.png</image>
|
||||
|
||||
@@ -658,12 +630,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 +650,7 @@
|
||||
|
||||
</name>
|
||||
|
||||
<e-mail>ndrochak AT ieee.org</e-mail>
|
||||
<e-mail>ndrochak AT gol.com</e-mail>
|
||||
|
||||
<image>nickd.png</image>
|
||||
|
||||
@@ -858,13 +830,13 @@
|
||||
|
||||
<e-mail>[email protected]</e-mail>
|
||||
|
||||
<image>jonpryor.png</image>
|
||||
<image>none.png</image>
|
||||
|
||||
<location>Richmond, Virginia</location>
|
||||
<location>Blacksburg, Virginia</location>
|
||||
|
||||
<organization>Cadmus Professional Communications</organization>
|
||||
<organization>Virginia Tech</organization>
|
||||
|
||||
<description>Mono Hacker</description>
|
||||
<description>Graduate Student</description>
|
||||
|
||||
<tasks>
|
||||
|
||||
@@ -915,13 +887,13 @@
|
||||
|
||||
</name>
|
||||
|
||||
<e-mail>justdandy43@hotmail.com</e-mail>
|
||||
<e-mail>[email protected].com</e-mail>
|
||||
|
||||
<image>none.png</image>
|
||||
|
||||
<location>Richmond, Virginia, USA</location>
|
||||
<location>Columbia, South Carolina, USA</location>
|
||||
|
||||
<organization>an insurance company</organization>
|
||||
<organization>Unemployed</organization>
|
||||
|
||||
<description>Mono hacker</description>
|
||||
|
||||
@@ -983,7 +955,7 @@
|
||||
|
||||
<image>none.png</image>
|
||||
|
||||
<location>São Paulo</location>
|
||||
<location>São Paulo</location>
|
||||
|
||||
<organization>WEBforAll.</organization>
|
||||
|
||||
@@ -1410,144 +1382,4 @@
|
||||
</tasks>
|
||||
|
||||
</contributor>
|
||||
<contributor>
|
||||
|
||||
<name>
|
||||
|
||||
<first-name>John</first-name>
|
||||
|
||||
<last-name>Luke</last-name>
|
||||
|
||||
</name>
|
||||
|
||||
<e-mail>[email protected]</e-mail>
|
||||
|
||||
<image>none.png</image>
|
||||
|
||||
<location>Daytona, FL</location>
|
||||
|
||||
<organization></organization>
|
||||
|
||||
<description>Contributor.</description>
|
||||
|
||||
<tasks>
|
||||
|
||||
<task>Documentation.</task>
|
||||
|
||||
<task>Monodoc.</task>
|
||||
|
||||
<task>Gtk#</task>
|
||||
|
||||
</tasks>
|
||||
|
||||
</contributor>
|
||||
<contributor>
|
||||
|
||||
<name>
|
||||
|
||||
<first-name>Peter</first-name>
|
||||
|
||||
<last-name>Williams</last-name>
|
||||
|
||||
</name>
|
||||
|
||||
<e-mail>[email protected]</e-mail>
|
||||
|
||||
<image>peterw.png</image>
|
||||
|
||||
<location>Cambridge, MA</location>
|
||||
|
||||
<organization></organization>
|
||||
|
||||
<description>Makefile Magician</description>
|
||||
|
||||
<tasks>
|
||||
|
||||
<task>MCS build system </task>
|
||||
|
||||
</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></description>
|
||||
|
||||
<tasks>
|
||||
|
||||
<task>WSE2</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>[email protected]</e-mail>
|
||||
|
||||
<image>jordi.png</image>
|
||||
|
||||
<location>Barcelona, Spain</location>
|
||||
|
||||
<organization></organization>
|
||||
|
||||
<description>Developer</description>
|
||||
|
||||
<tasks>
|
||||
|
||||
<task>Windows.Forms implementation</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.4 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 4.1 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 3.8 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 4.3 KiB |
@@ -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,14 +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;
|
||||
}
|
||||
|
||||
// -->
|
||||
</style>
|
||||
#CSS#
|
||||
@@ -47,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="blogs.html">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>
|
||||
|
||||
@@ -1,20 +0,0 @@
|
||||
using System;
|
||||
using System.Xml;
|
||||
using System.Xml.Xsl;
|
||||
|
||||
namespace Transform
|
||||
{
|
||||
class Transform
|
||||
{
|
||||
public static void Main (string [] rgstrArgs)
|
||||
{
|
||||
XmlDocument xml = new XmlDocument ();
|
||||
xml.Load (rgstrArgs [0]);
|
||||
|
||||
XslTransform xsl = new XslTransform ();
|
||||
xsl.Load (rgstrArgs [1]);
|
||||
|
||||
xsl.Transform (xml, null, Console.Out);
|
||||
}
|
||||
}
|
||||
}
|
||||
+76
-12
@@ -27,14 +27,6 @@
|
||||
|
||||
* Win32/Wine edition.
|
||||
|
||||
To get the Windows.Forms support working, you need a Mono
|
||||
installation from CVS, and you need to install Wine plus the
|
||||
<a href="http://www.openlinksw.com">OpenLink patch</a>, and
|
||||
define the environment variable "SWF" (export SWF=1 from your
|
||||
shell). For more information, see the <a
|
||||
href="http://www.nullenvoid.com/mono/wiki/index.php/MonoWinePackages">Mono
|
||||
Wine Packages</a> page in the Mono Wiki.
|
||||
|
||||
<table>
|
||||
<tr>
|
||||
<td>
|
||||
@@ -48,7 +40,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 +82,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.
|
||||
|
||||
+1
-2
@@ -1,4 +1,3 @@
|
||||
EXTRA_DIST = gc-issues jit-thoughts object-layout unmanaged-calls \
|
||||
exceptions jit-trampolines stack-alignment embedded-api \
|
||||
assembly-bundle
|
||||
exceptions jit-trampolines stack-alignment embedded-api
|
||||
|
||||
@@ -1,42 +0,0 @@
|
||||
|
||||
HOWTO bundle assemblies inside the mono runtime.
|
||||
|
||||
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
|
||||
|
||||
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.
|
||||
|
||||
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
|
||||
|
||||
+11
-12
@@ -56,20 +56,19 @@ leave: is simply translated into a branch to the target. If the leave
|
||||
instruction is inside a finally block (but not inside another handler)
|
||||
we call the finally handler before we branch to the target.
|
||||
|
||||
finally/endfinally, filter/endfilter: is translated into subroutine ending with
|
||||
a "return" statement. The subroutine does not save EBP, 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. This makes it
|
||||
also possible to execute them inside the stack unwinding code. The exception
|
||||
object for filters is passed in a local variable (cfg->exvar).
|
||||
finally/endfinally: is translated into subroutine ending with a "return"
|
||||
statement. The subroutine does not save EBP/ESP, because we need access to the
|
||||
local variables of the enclosing method. We have to use a "call"
|
||||
instruction to execute such finally handlers. This makes it possible to
|
||||
execute them inside the stack unwinding code.
|
||||
|
||||
throw: we first save all regs into a sigcontext struct and then call the stack
|
||||
unwinding code.
|
||||
throw: we first save all regs into a sigcontext struct (we pass the
|
||||
exception object in register ECX), and then call the stack unwinding
|
||||
code.
|
||||
|
||||
catch handler: receives the exception object in ECX. They store that
|
||||
object into a local variable, so that rethrow can access the object.
|
||||
|
||||
catch handler: catch hanlders are always called from the stack unwinding
|
||||
code. The exception object is passed in a local variable (cfg->exvar).
|
||||
|
||||
gcc support for Exceptions
|
||||
==========================
|
||||
|
||||
@@ -1,349 +0,0 @@
|
||||
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.
|
||||
|
||||
|
||||
* 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).
|
||||
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:
|
||||
|
||||
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
|
||||
mono/arch/$(arch)/
|
||||
directory.
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
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.
|
||||
|
||||
|
||||
* 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.
|
||||
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:
|
||||
|
||||
*) 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.
|
||||
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.
|
||||
|
||||
** 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".
|
||||
|
||||
** 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).
|
||||
|
||||
** 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.
|
||||
|
||||
** 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.
|
||||
|
||||
* 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.
|
||||
|
||||
|
||||
* 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).
|
||||
|
||||
|
||||
* 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.
|
||||
|
||||
+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
|
||||
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)
|
||||
-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,88 +0,0 @@
|
||||
.\"
|
||||
.\" makecert manual page.
|
||||
.\" Copyright 2003 Motus Technologies
|
||||
.\" Author:
|
||||
.\" Sebastien Pouliot ([email protected])
|
||||
.\"
|
||||
.TH Mono "MakeCert"
|
||||
.SH NAME
|
||||
MakeCert \- Create X.509 certificates for test purposes
|
||||
.SH SYNOPSIS
|
||||
.PP
|
||||
.B MakeCert [options] certificate
|
||||
.SH DESCRIPTION
|
||||
Create an X.509 certificate using the provided informations. This
|
||||
is useful for testing Authenticode signatures, SSL and S/MIME
|
||||
technologies.
|
||||
.SH PARAMETERS
|
||||
.TP
|
||||
.I "-# num"
|
||||
Certificate serial number
|
||||
.TP
|
||||
.I "-n dn"
|
||||
Subject Distinguished Name
|
||||
.TP
|
||||
.I "-in dn"
|
||||
Issuert Distinguished Name
|
||||
.TP
|
||||
.I "-r"
|
||||
Create a self-signed (root) certificate
|
||||
.TP
|
||||
.I "-sv pkvfile"
|
||||
Private key file (.PVK) for the subject (created if missing)
|
||||
.TP
|
||||
.I "-iv pvkfile"
|
||||
Private key file (.PVK) for the issuer
|
||||
.TP
|
||||
.I "-ic certfile"
|
||||
Extract the issuer's name from the specified certificate
|
||||
.TP
|
||||
.I "-?"
|
||||
Help (display this help message)
|
||||
.TP
|
||||
.I "-!"
|
||||
Extended help (for advanced options)
|
||||
.TP
|
||||
.I "-a hash"
|
||||
Select hash algorithm. Only MD5 and SHA1 are supported.
|
||||
.TP
|
||||
.I "-b date"
|
||||
The date since when the certificate is valid (notBefore).
|
||||
.TP
|
||||
.I "-cy [authority|end]"
|
||||
Basic constraints. Select Authority or End-Entity certificate.
|
||||
.TP
|
||||
.I "-e date"
|
||||
The date until when the certificate is valid (notAfter).
|
||||
.TP
|
||||
.I "-eku oid[,oid]"
|
||||
Add some extended key usage OID to the certificate.
|
||||
.TP
|
||||
.I "-h number"
|
||||
Add a path length restriction to the certificate chain.
|
||||
.TP
|
||||
.I "-ic cert"
|
||||
Take the issuer's name from the specified certificate.
|
||||
.TP
|
||||
.I "-in name"
|
||||
Take the issuer's name from the specified parameter.
|
||||
.TP
|
||||
.I "-iv pvkfile"
|
||||
Sign the certificate using the private key inside the PVK file.
|
||||
.TP
|
||||
.I "-m number"
|
||||
Certificate validity period (in months).
|
||||
.TP
|
||||
.I "-sv pvkfile"
|
||||
Create a new PVK file if non-existant, otherwise use the PVK file as the subject public key.
|
||||
.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)
|
||||
-18
@@ -1,18 +0,0 @@
|
||||
<?xml version="1.0"?>
|
||||
<manpages>
|
||||
<manpage name="Mono" page="mono.1" />
|
||||
<manpage name="Mint" page="mono.1" />
|
||||
<manpage name="Mcs" page="mcs.1" />
|
||||
<manpage name="Ilasm" page="ilasm.1" />
|
||||
<manpage name="Monodis" page="mono.1" />
|
||||
<manpage name="Cilc" page="cilc.1" />
|
||||
<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" />
|
||||
</manpages>
|
||||
@@ -1,4 +0,0 @@
|
||||
<?xml version="1.0"?>
|
||||
<monodoc>
|
||||
<source provider="man" basefile="tree" path="manpages"/>
|
||||
</monodoc>
|
||||
@@ -195,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.
|
||||
|
||||
+34
-95
@@ -10,7 +10,7 @@
|
||||
..
|
||||
.TH Mono "Mono 1.0"
|
||||
.SH NAME
|
||||
mono \- Mono's ECMA-CLI native code generator (Just-in-Time and Ahead-of-Time)
|
||||
mono \- Mono's code ECMA-CLI code generator (Just-in-Time and Ahead-of-Time)
|
||||
.SH SYNOPSIS
|
||||
.PP
|
||||
.B mono [options] file [arguments...]
|
||||
@@ -85,11 +85,9 @@ The following optimizations are implemented:
|
||||
cmov Conditional moves
|
||||
shared Emit per-domain code
|
||||
sched Instruction scheduling
|
||||
intrins Intrinsic method implementations
|
||||
instrins Intrinsic method implementations
|
||||
tailc Tail recursion and tail calls
|
||||
loop Loop related optimizations
|
||||
leaf Leaf procedures optimizations
|
||||
profile Use profiling information
|
||||
.fi
|
||||
.Sp
|
||||
For example, to enable all the optimization but dead code
|
||||
@@ -97,28 +95,41 @@ elimination and inlining, you can use:
|
||||
.nf
|
||||
-O=all,-deadce,-inline
|
||||
.fi
|
||||
.SH DEVELOPMENT OPTIONS
|
||||
.TP
|
||||
.I "-V", "--version"
|
||||
Prints JIT version information.
|
||||
.I "--break method"
|
||||
Inserts a breakpoint before the method whose name is `method'
|
||||
(namespace.class:methodname). Use `Main' as method name to insert a
|
||||
breakpoint on the application's main method.
|
||||
.TP
|
||||
.I "--breakonex"
|
||||
Inserts a breakpoint on exceptions. This allows you to debug your
|
||||
application with a native debugger when an exception is thrown.
|
||||
.TP
|
||||
.I "--coverage"
|
||||
Performs coverage analysis on the underlying IL code.
|
||||
.TP
|
||||
.I "--trace"
|
||||
Shows method names as they are invoked.
|
||||
|
||||
|
||||
|
||||
.SH DEVELOPMENT OPTIONS
|
||||
The following options are used to help when developing a JITed application.
|
||||
The following options are used to debug a JITed application. They're
|
||||
only useful when running the JIT in a debugger:
|
||||
.TP
|
||||
.I "--debug"
|
||||
Turns on the debugging mode in the runtime. If an assembly was
|
||||
compiled with debugging information, it will produce line number
|
||||
information for stack traces.
|
||||
.TP
|
||||
.I "--profile[=profiler[:profiler_args]]"
|
||||
.I "--profile"
|
||||
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
|
||||
|
||||
|
||||
|
||||
.SH MAINTAINER OPTIONS
|
||||
The maintainer options are only used by those developing the runtime
|
||||
itself, and not typically of interest to runtime users or developers.
|
||||
.TP
|
||||
@@ -156,57 +167,12 @@ compiled. This is used for testing the code generator performance.
|
||||
.TP
|
||||
.I "-v", "--verbose"
|
||||
Increases the verbosity level, each time it is listed, increases the
|
||||
verbosity level to include more information (including, for example,
|
||||
a disassembly of the native code produced, code selector info etc.).
|
||||
verbosity level to include more information.
|
||||
.TP
|
||||
.I "--break method"
|
||||
Inserts a breakpoint before the method whose name is `method'
|
||||
(namespace.class:methodname). Use `Main' as method name to insert a
|
||||
breakpoint on the application's main method.
|
||||
.TP
|
||||
.I "--breakonex"
|
||||
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 "-V", "--version"
|
||||
Prints JIT version information.
|
||||
|
||||
|
||||
.SH ENVIRONMENT VARIABLES
|
||||
.TP
|
||||
.I "GC_DONT_GC"
|
||||
@@ -219,10 +185,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,30 +197,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.
|
||||
.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
|
||||
@@ -271,8 +212,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)
|
||||
-481
@@ -1,481 +0,0 @@
|
||||
GNU LIBRARY GENERAL PUBLIC LICENSE
|
||||
Version 2, June 1991
|
||||
|
||||
Copyright (C) 1991 Free Software Foundation, Inc.
|
||||
675 Mass Ave, Cambridge, MA 02139, USA
|
||||
Everyone is permitted to copy and distribute verbatim copies
|
||||
of this license document, but changing it is not allowed.
|
||||
|
||||
[This is the first released version of the library GPL. It is
|
||||
numbered 2 because it goes with version 2 of the ordinary GPL.]
|
||||
|
||||
Preamble
|
||||
|
||||
The licenses for most software are designed to take away your
|
||||
freedom to share and change it. By contrast, the GNU General Public
|
||||
Licenses are intended to guarantee your freedom to share and change
|
||||
free software--to make sure the software is free for all its users.
|
||||
|
||||
This license, the Library General Public License, applies to some
|
||||
specially designated Free Software Foundation software, and to any
|
||||
other libraries whose authors decide to use it. You can use it for
|
||||
your libraries, too.
|
||||
|
||||
When we speak of free software, we are referring to freedom, not
|
||||
price. Our General Public Licenses are designed to make sure that you
|
||||
have the freedom to distribute copies of free software (and charge for
|
||||
this service if you wish), that you receive source code or can get it
|
||||
if you want it, that you can change the software or use pieces of it
|
||||
in new free programs; and that you know you can do these things.
|
||||
|
||||
To protect your rights, we need to make restrictions that forbid
|
||||
anyone to deny you these rights or to ask you to surrender the rights.
|
||||
These restrictions translate to certain responsibilities for you if
|
||||
you distribute copies of the library, or if you modify it.
|
||||
|
||||
For example, if you distribute copies of the library, whether gratis
|
||||
or for a fee, you must give the recipients all the rights that we gave
|
||||
you. You must make sure that they, too, receive or can get the source
|
||||
code. If you link a program with the library, you must provide
|
||||
complete object files to the recipients so that they can relink them
|
||||
with the library, after making changes to the library and recompiling
|
||||
it. And you must show them these terms so they know their rights.
|
||||
|
||||
Our method of protecting your rights has two steps: (1) copyright
|
||||
the library, and (2) offer you this license which gives you legal
|
||||
permission to copy, distribute and/or modify the library.
|
||||
|
||||
Also, for each distributor's protection, we want to make certain
|
||||
that everyone understands that there is no warranty for this free
|
||||
library. If the library is modified by someone else and passed on, we
|
||||
want its recipients to know that what they have is not the original
|
||||
version, so that any problems introduced by others will not reflect on
|
||||
the original authors' reputations.
|
||||
|
||||
Finally, any free program is threatened constantly by software
|
||||
patents. We wish to avoid the danger that companies distributing free
|
||||
software will individually obtain patent licenses, thus in effect
|
||||
transforming the program into proprietary software. To prevent this,
|
||||
we have made it clear that any patent must be licensed for everyone's
|
||||
free use or not licensed at all.
|
||||
|
||||
Most GNU software, including some libraries, is covered by the ordinary
|
||||
GNU General Public License, which was designed for utility programs. This
|
||||
license, the GNU Library General Public License, applies to certain
|
||||
designated libraries. This license is quite different from the ordinary
|
||||
one; be sure to read it in full, and don't assume that anything in it is
|
||||
the same as in the ordinary license.
|
||||
|
||||
The reason we have a separate public license for some libraries is that
|
||||
they blur the distinction we usually make between modifying or adding to a
|
||||
program and simply using it. Linking a program with a library, without
|
||||
changing the library, is in some sense simply using the library, and is
|
||||
analogous to running a utility program or application program. However, in
|
||||
a textual and legal sense, the linked executable is a combined work, a
|
||||
derivative of the original library, and the ordinary General Public License
|
||||
treats it as such.
|
||||
|
||||
Because of this blurred distinction, using the ordinary General
|
||||
Public License for libraries did not effectively promote software
|
||||
sharing, because most developers did not use the libraries. We
|
||||
concluded that weaker conditions might promote sharing better.
|
||||
|
||||
However, unrestricted linking of non-free programs would deprive the
|
||||
users of those programs of all benefit from the free status of the
|
||||
libraries themselves. This Library General Public License is intended to
|
||||
permit developers of non-free programs to use free libraries, while
|
||||
preserving your freedom as a user of such programs to change the free
|
||||
libraries that are incorporated in them. (We have not seen how to achieve
|
||||
this as regards changes in header files, but we have achieved it as regards
|
||||
changes in the actual functions of the Library.) The hope is that this
|
||||
will lead to faster development of free libraries.
|
||||
|
||||
The precise terms and conditions for copying, distribution and
|
||||
modification follow. Pay close attention to the difference between a
|
||||
"work based on the library" and a "work that uses the library". The
|
||||
former contains code derived from the library, while the latter only
|
||||
works together with the library.
|
||||
|
||||
Note that it is possible for a library to be covered by the ordinary
|
||||
General Public License rather than by this special one.
|
||||
|
||||
GNU LIBRARY GENERAL PUBLIC LICENSE
|
||||
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
|
||||
|
||||
0. This License Agreement applies to any software library which
|
||||
contains a notice placed by the copyright holder or other authorized
|
||||
party saying it may be distributed under the terms of this Library
|
||||
General Public License (also called "this License"). Each licensee is
|
||||
addressed as "you".
|
||||
|
||||
A "library" means a collection of software functions and/or data
|
||||
prepared so as to be conveniently linked with application programs
|
||||
(which use some of those functions and data) to form executables.
|
||||
|
||||
The "Library", below, refers to any such software library or work
|
||||
which has been distributed under these terms. A "work based on the
|
||||
Library" means either the Library or any derivative work under
|
||||
copyright law: that is to say, a work containing the Library or a
|
||||
portion of it, either verbatim or with modifications and/or translated
|
||||
straightforwardly into another language. (Hereinafter, translation is
|
||||
included without limitation in the term "modification".)
|
||||
|
||||
"Source code" for a work means the preferred form of the work for
|
||||
making modifications to it. For a library, complete source code means
|
||||
all the source code for all modules it contains, plus any associated
|
||||
interface definition files, plus the scripts used to control compilation
|
||||
and installation of the library.
|
||||
|
||||
Activities other than copying, distribution and modification are not
|
||||
covered by this License; they are outside its scope. The act of
|
||||
running a program using the Library is not restricted, and output from
|
||||
such a program is covered only if its contents constitute a work based
|
||||
on the Library (independent of the use of the Library in a tool for
|
||||
writing it). Whether that is true depends on what the Library does
|
||||
and what the program that uses the Library does.
|
||||
|
||||
1. You may copy and distribute verbatim copies of the Library's
|
||||
complete source code as you receive it, in any medium, provided that
|
||||
you conspicuously and appropriately publish on each copy an
|
||||
appropriate copyright notice and disclaimer of warranty; keep intact
|
||||
all the notices that refer to this License and to the absence of any
|
||||
warranty; and distribute a copy of this License along with the
|
||||
Library.
|
||||
|
||||
You may charge a fee for the physical act of transferring a copy,
|
||||
and you may at your option offer warranty protection in exchange for a
|
||||
fee.
|
||||
|
||||
2. You may modify your copy or copies of the Library or any portion
|
||||
of it, thus forming a work based on the Library, and copy and
|
||||
distribute such modifications or work under the terms of Section 1
|
||||
above, provided that you also meet all of these conditions:
|
||||
|
||||
a) The modified work must itself be a software library.
|
||||
|
||||
b) You must cause the files modified to carry prominent notices
|
||||
stating that you changed the files and the date of any change.
|
||||
|
||||
c) You must cause the whole of the work to be licensed at no
|
||||
charge to all third parties under the terms of this License.
|
||||
|
||||
d) If a facility in the modified Library refers to a function or a
|
||||
table of data to be supplied by an application program that uses
|
||||
the facility, other than as an argument passed when the facility
|
||||
is invoked, then you must make a good faith effort to ensure that,
|
||||
in the event an application does not supply such function or
|
||||
table, the facility still operates, and performs whatever part of
|
||||
its purpose remains meaningful.
|
||||
|
||||
(For example, a function in a library to compute square roots has
|
||||
a purpose that is entirely well-defined independent of the
|
||||
application. Therefore, Subsection 2d requires that any
|
||||
application-supplied function or table used by this function must
|
||||
be optional: if the application does not supply it, the square
|
||||
root function must still compute square roots.)
|
||||
|
||||
These requirements apply to the modified work as a whole. If
|
||||
identifiable sections of that work are not derived from the Library,
|
||||
and can be reasonably considered independent and separate works in
|
||||
themselves, then this License, and its terms, do not apply to those
|
||||
sections when you distribute them as separate works. But when you
|
||||
distribute the same sections as part of a whole which is a work based
|
||||
on the Library, the distribution of the whole must be on the terms of
|
||||
this License, whose permissions for other licensees extend to the
|
||||
entire whole, and thus to each and every part regardless of who wrote
|
||||
it.
|
||||
|
||||
Thus, it is not the intent of this section to claim rights or contest
|
||||
your rights to work written entirely by you; rather, the intent is to
|
||||
exercise the right to control the distribution of derivative or
|
||||
collective works based on the Library.
|
||||
|
||||
In addition, mere aggregation of another work not based on the Library
|
||||
with the Library (or with a work based on the Library) on a volume of
|
||||
a storage or distribution medium does not bring the other work under
|
||||
the scope of this License.
|
||||
|
||||
3. You may opt to apply the terms of the ordinary GNU General Public
|
||||
License instead of this License to a given copy of the Library. To do
|
||||
this, you must alter all the notices that refer to this License, so
|
||||
that they refer to the ordinary GNU General Public License, version 2,
|
||||
instead of to this License. (If a newer version than version 2 of the
|
||||
ordinary GNU General Public License has appeared, then you can specify
|
||||
that version instead if you wish.) Do not make any other change in
|
||||
these notices.
|
||||
|
||||
Once this change is made in a given copy, it is irreversible for
|
||||
that copy, so the ordinary GNU General Public License applies to all
|
||||
subsequent copies and derivative works made from that copy.
|
||||
|
||||
This option is useful when you wish to copy part of the code of
|
||||
the Library into a program that is not a library.
|
||||
|
||||
4. You may copy and distribute the Library (or a portion or
|
||||
derivative of it, under Section 2) in object code or executable form
|
||||
under the terms of Sections 1 and 2 above provided that you accompany
|
||||
it with the complete corresponding machine-readable source code, which
|
||||
must be distributed under the terms of Sections 1 and 2 above on a
|
||||
medium customarily used for software interchange.
|
||||
|
||||
If distribution of object code is made by offering access to copy
|
||||
from a designated place, then offering equivalent access to copy the
|
||||
source code from the same place satisfies the requirement to
|
||||
distribute the source code, even though third parties are not
|
||||
compelled to copy the source along with the object code.
|
||||
|
||||
5. A program that contains no derivative of any portion of the
|
||||
Library, but is designed to work with the Library by being compiled or
|
||||
linked with it, is called a "work that uses the Library". Such a
|
||||
work, in isolation, is not a derivative work of the Library, and
|
||||
therefore falls outside the scope of this License.
|
||||
|
||||
However, linking a "work that uses the Library" with the Library
|
||||
creates an executable that is a derivative of the Library (because it
|
||||
contains portions of the Library), rather than a "work that uses the
|
||||
library". The executable is therefore covered by this License.
|
||||
Section 6 states terms for distribution of such executables.
|
||||
|
||||
When a "work that uses the Library" uses material from a header file
|
||||
that is part of the Library, the object code for the work may be a
|
||||
derivative work of the Library even though the source code is not.
|
||||
Whether this is true is especially significant if the work can be
|
||||
linked without the Library, or if the work is itself a library. The
|
||||
threshold for this to be true is not precisely defined by law.
|
||||
|
||||
If such an object file uses only numerical parameters, data
|
||||
structure layouts and accessors, and small macros and small inline
|
||||
functions (ten lines or less in length), then the use of the object
|
||||
file is unrestricted, regardless of whether it is legally a derivative
|
||||
work. (Executables containing this object code plus portions of the
|
||||
Library will still fall under Section 6.)
|
||||
|
||||
Otherwise, if the work is a derivative of the Library, you may
|
||||
distribute the object code for the work under the terms of Section 6.
|
||||
Any executables containing that work also fall under Section 6,
|
||||
whether or not they are linked directly with the Library itself.
|
||||
|
||||
6. As an exception to the Sections above, you may also compile or
|
||||
link a "work that uses the Library" with the Library to produce a
|
||||
work containing portions of the Library, and distribute that work
|
||||
under terms of your choice, provided that the terms permit
|
||||
modification of the work for the customer's own use and reverse
|
||||
engineering for debugging such modifications.
|
||||
|
||||
You must give prominent notice with each copy of the work that the
|
||||
Library is used in it and that the Library and its use are covered by
|
||||
this License. You must supply a copy of this License. If the work
|
||||
during execution displays copyright notices, you must include the
|
||||
copyright notice for the Library among them, as well as a reference
|
||||
directing the user to the copy of this License. Also, you must do one
|
||||
of these things:
|
||||
|
||||
a) Accompany the work with the complete corresponding
|
||||
machine-readable source code for the Library including whatever
|
||||
changes were used in the work (which must be distributed under
|
||||
Sections 1 and 2 above); and, if the work is an executable linked
|
||||
with the Library, with the complete machine-readable "work that
|
||||
uses the Library", as object code and/or source code, so that the
|
||||
user can modify the Library and then relink to produce a modified
|
||||
executable containing the modified Library. (It is understood
|
||||
that the user who changes the contents of definitions files in the
|
||||
Library will not necessarily be able to recompile the application
|
||||
to use the modified definitions.)
|
||||
|
||||
b) Accompany the work with a written offer, valid for at
|
||||
least three years, to give the same user the materials
|
||||
specified in Subsection 6a, above, for a charge no more
|
||||
than the cost of performing this distribution.
|
||||
|
||||
c) If distribution of the work is made by offering access to copy
|
||||
from a designated place, offer equivalent access to copy the above
|
||||
specified materials from the same place.
|
||||
|
||||
d) Verify that the user has already received a copy of these
|
||||
materials or that you have already sent this user a copy.
|
||||
|
||||
For an executable, the required form of the "work that uses the
|
||||
Library" must include any data and utility programs needed for
|
||||
reproducing the executable from it. However, as a special exception,
|
||||
the source code distributed need not include anything that is normally
|
||||
distributed (in either source or binary form) with the major
|
||||
components (compiler, kernel, and so on) of the operating system on
|
||||
which the executable runs, unless that component itself accompanies
|
||||
the executable.
|
||||
|
||||
It may happen that this requirement contradicts the license
|
||||
restrictions of other proprietary libraries that do not normally
|
||||
accompany the operating system. Such a contradiction means you cannot
|
||||
use both them and the Library together in an executable that you
|
||||
distribute.
|
||||
|
||||
7. You may place library facilities that are a work based on the
|
||||
Library side-by-side in a single library together with other library
|
||||
facilities not covered by this License, and distribute such a combined
|
||||
library, provided that the separate distribution of the work based on
|
||||
the Library and of the other library facilities is otherwise
|
||||
permitted, and provided that you do these two things:
|
||||
|
||||
a) Accompany the combined library with a copy of the same work
|
||||
based on the Library, uncombined with any other library
|
||||
facilities. This must be distributed under the terms of the
|
||||
Sections above.
|
||||
|
||||
b) Give prominent notice with the combined library of the fact
|
||||
that part of it is a work based on the Library, and explaining
|
||||
where to find the accompanying uncombined form of the same work.
|
||||
|
||||
8. You may not copy, modify, sublicense, link with, or distribute
|
||||
the Library except as expressly provided under this License. Any
|
||||
attempt otherwise to copy, modify, sublicense, link with, or
|
||||
distribute the Library is void, and will automatically terminate your
|
||||
rights under this License. However, parties who have received copies,
|
||||
or rights, from you under this License will not have their licenses
|
||||
terminated so long as such parties remain in full compliance.
|
||||
|
||||
9. You are not required to accept this License, since you have not
|
||||
signed it. However, nothing else grants you permission to modify or
|
||||
distribute the Library or its derivative works. These actions are
|
||||
prohibited by law if you do not accept this License. Therefore, by
|
||||
modifying or distributing the Library (or any work based on the
|
||||
Library), you indicate your acceptance of this License to do so, and
|
||||
all its terms and conditions for copying, distributing or modifying
|
||||
the Library or works based on it.
|
||||
|
||||
10. Each time you redistribute the Library (or any work based on the
|
||||
Library), the recipient automatically receives a license from the
|
||||
original licensor to copy, distribute, link with or modify the Library
|
||||
subject to these terms and conditions. You may not impose any further
|
||||
restrictions on the recipients' exercise of the rights granted herein.
|
||||
You are not responsible for enforcing compliance by third parties to
|
||||
this License.
|
||||
|
||||
11. If, as a consequence of a court judgment or allegation of patent
|
||||
infringement or for any other reason (not limited to patent issues),
|
||||
conditions are imposed on you (whether by court order, agreement or
|
||||
otherwise) that contradict the conditions of this License, they do not
|
||||
excuse you from the conditions of this License. If you cannot
|
||||
distribute so as to satisfy simultaneously your obligations under this
|
||||
License and any other pertinent obligations, then as a consequence you
|
||||
may not distribute the Library at all. For example, if a patent
|
||||
license would not permit royalty-free redistribution of the Library by
|
||||
all those who receive copies directly or indirectly through you, then
|
||||
the only way you could satisfy both it and this License would be to
|
||||
refrain entirely from distribution of the Library.
|
||||
|
||||
If any portion of this section is held invalid or unenforceable under any
|
||||
particular circumstance, the balance of the section is intended to apply,
|
||||
and the section as a whole is intended to apply in other circumstances.
|
||||
|
||||
It is not the purpose of this section to induce you to infringe any
|
||||
patents or other property right claims or to contest validity of any
|
||||
such claims; this section has the sole purpose of protecting the
|
||||
integrity of the free software distribution system which is
|
||||
implemented by public license practices. Many people have made
|
||||
generous contributions to the wide range of software distributed
|
||||
through that system in reliance on consistent application of that
|
||||
system; it is up to the author/donor to decide if he or she is willing
|
||||
to distribute software through any other system and a licensee cannot
|
||||
impose that choice.
|
||||
|
||||
This section is intended to make thoroughly clear what is believed to
|
||||
be a consequence of the rest of this License.
|
||||
|
||||
12. If the distribution and/or use of the Library is restricted in
|
||||
certain countries either by patents or by copyrighted interfaces, the
|
||||
original copyright holder who places the Library under this License may add
|
||||
an explicit geographical distribution limitation excluding those countries,
|
||||
so that distribution is permitted only in or among countries not thus
|
||||
excluded. In such case, this License incorporates the limitation as if
|
||||
written in the body of this License.
|
||||
|
||||
13. The Free Software Foundation may publish revised and/or new
|
||||
versions of the Library General Public License from time to time.
|
||||
Such new versions will be similar in spirit to the present version,
|
||||
but may differ in detail to address new problems or concerns.
|
||||
|
||||
Each version is given a distinguishing version number. If the Library
|
||||
specifies a version number of this License which applies to it and
|
||||
"any later version", you have the option of following the terms and
|
||||
conditions either of that version or of any later version published by
|
||||
the Free Software Foundation. If the Library does not specify a
|
||||
license version number, you may choose any version ever published by
|
||||
the Free Software Foundation.
|
||||
|
||||
14. If you wish to incorporate parts of the Library into other free
|
||||
programs whose distribution conditions are incompatible with these,
|
||||
write to the author to ask for permission. For software which is
|
||||
copyrighted by the Free Software Foundation, write to the Free
|
||||
Software Foundation; we sometimes make exceptions for this. Our
|
||||
decision will be guided by the two goals of preserving the free status
|
||||
of all derivatives of our free software and of promoting the sharing
|
||||
and reuse of software generally.
|
||||
|
||||
NO WARRANTY
|
||||
|
||||
15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
|
||||
WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
|
||||
EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
|
||||
OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
|
||||
KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
|
||||
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
|
||||
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
|
||||
LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
|
||||
THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
|
||||
|
||||
16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
|
||||
WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
|
||||
AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
|
||||
FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
|
||||
CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
|
||||
LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
|
||||
RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
|
||||
FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
|
||||
SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
|
||||
DAMAGES.
|
||||
|
||||
END OF TERMS AND CONDITIONS
|
||||
|
||||
Appendix: How to Apply These Terms to Your New Libraries
|
||||
|
||||
If you develop a new library, and you want it to be of the greatest
|
||||
possible use to the public, we recommend making it free software that
|
||||
everyone can redistribute and change. You can do so by permitting
|
||||
redistribution under these terms (or, alternatively, under the terms of the
|
||||
ordinary General Public License).
|
||||
|
||||
To apply these terms, attach the following notices to the library. It is
|
||||
safest to attach them to the start of each source file to most effectively
|
||||
convey the exclusion of warranty; and each file should have at least the
|
||||
"copyright" line and a pointer to where the full notice is found.
|
||||
|
||||
<one line to give the library's name and a brief idea of what it does.>
|
||||
Copyright (C) <year> <name of author>
|
||||
|
||||
This library is free software; you can redistribute it and/or
|
||||
modify it under the terms of the GNU Library General Public
|
||||
License as published by the Free Software Foundation; either
|
||||
version 2 of the License, or (at your option) any later version.
|
||||
|
||||
This library is distributed in the hope that it will be useful,
|
||||
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
|
||||
Library General Public License for more details.
|
||||
|
||||
You should have received a copy of the GNU Library General Public
|
||||
License along with this library; if not, write to the Free
|
||||
Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
|
||||
|
||||
Also add information on how to contact you by electronic and paper mail.
|
||||
|
||||
You should also get your employer (if you work as a programmer) or your
|
||||
school, if any, to sign a "copyright disclaimer" for the library, if
|
||||
necessary. Here is a sample; alter the names:
|
||||
|
||||
Yoyodyne, Inc., hereby disclaims all copyright interest in the
|
||||
library `Frob' (a library for tweaking knobs) written by James Random Hacker.
|
||||
|
||||
<signature of Ty Coon>, 1 April 1990
|
||||
Ty Coon, President of Vice
|
||||
|
||||
That's all there is to it!
|
||||
@@ -1,102 +1,3 @@
|
||||
2003-10-28 Jackson Harper <[email protected]>
|
||||
|
||||
* INSTALL.txt: Tell users where to find monocharges, do not
|
||||
reference README.building.
|
||||
|
||||
2003-07-22 Peter Williams <[email protected]>
|
||||
|
||||
* README: INSTALL.txt, not INSTALL.
|
||||
|
||||
2003-07-20 Peter Williams <[email protected]>
|
||||
|
||||
* nunit20/nunit-console/Makefile (PROGRAM): Put nunit-console.exe
|
||||
in $(topdir)/class/lib so we can find our DLL's.
|
||||
|
||||
2003-07-18 Peter Williams <[email protected]>
|
||||
|
||||
* build/library.make (dist-local): Fancy make dist magic gives
|
||||
way to boring old 'for'.
|
||||
|
||||
* build/executable.make (dist-local): Ditto.
|
||||
|
||||
2003-07-17 Peter Williams <[email protected]>
|
||||
|
||||
* build/profiles/default.make: Actually fix this. Use the platform
|
||||
compiler all the way.
|
||||
|
||||
2003-07-17 Peter Williams <[email protected]>
|
||||
|
||||
* build/profiles/default.make: Try to make this smarter so
|
||||
that we can build on Windows. Specifically, don't require
|
||||
the mono runtime. Combined with the corlib $(BOOT_COMPILE) change,
|
||||
this should make corlib build out of the box, I think.
|
||||
|
||||
2003-07-16 Peter Williams <[email protected]>
|
||||
|
||||
A whole passel of build system changes. Doc updates:
|
||||
|
||||
* build/README.makefiles: Doc updates.
|
||||
|
||||
* build/profiles/net_1_0.make: Doc changes.
|
||||
|
||||
* INSTALL.txt: A few more touchups.
|
||||
|
||||
Better defaults:
|
||||
|
||||
* build/config-default.make (prefix): Default install prefix
|
||||
should be /usr/local.
|
||||
|
||||
* build/profiles/bootstrap.make: This profile ...
|
||||
|
||||
* build/profiles/default.make: ... is now the default.
|
||||
|
||||
* build/profiles/atomic.make: And the default is now this.
|
||||
|
||||
Fixes for pre-build checks:
|
||||
|
||||
* Makefile: Do the platform and (new) profile checks
|
||||
before the build, which took some infrastructure changes.
|
||||
|
||||
* build/rules.make: Allow a Makefile to specify its own all/install/etc
|
||||
targets.
|
||||
|
||||
* build/profiles/default.make (profile-check): Add a blank
|
||||
target here.
|
||||
|
||||
* build/profiles/atomic.make: Check for a full MCS install to
|
||||
build against.
|
||||
|
||||
HP/UX fixes with help from Bernie Solomon:
|
||||
|
||||
* build/config-default.make (ECHO_ESCAPE): HP/UX 'echo'
|
||||
doesn't need a -e parameter to interpret escape codes. Test for
|
||||
that and define a configuration parameter.
|
||||
|
||||
* build/library.make ($(makefrag)): Use $(ECHO_ESCAPE)
|
||||
instead of assuming that 'echo -e' will interpret escape
|
||||
codes.
|
||||
|
||||
* build/executable.make ($(makefrag)): Here too.
|
||||
|
||||
A make distcheck fix:
|
||||
|
||||
* Makefile: Inherit the current prefix so that the build can
|
||||
find the right System.Xml.dll.
|
||||
|
||||
And Windows build fixes with the invaluable help of Sebastian
|
||||
Pouliot (in various subdirectories).
|
||||
|
||||
2003-07-14 Peter Williams <[email protected]>
|
||||
|
||||
* build/rules.make (dist-recursive): Fix recursive rules
|
||||
to work on HP/UX /bin/sh. Patch from Bernie Solomon
|
||||
<[email protected]>.
|
||||
|
||||
2003-05-10 Gonzalo Paniagua Javier <[email protected]>
|
||||
|
||||
* makefile:
|
||||
* makefile.gnu: don't use -C when running make.
|
||||
|
||||
2003-05-05 Ben Maurer <[email protected]>
|
||||
* AUTHORS: Added self.
|
||||
|
||||
|
||||
+29
-137
@@ -1,161 +1,53 @@
|
||||
Basic Installation
|
||||
==================
|
||||
|
||||
The Mono project has developed mono, a CLI runtime. The build process
|
||||
of each of these depends on nothing more than a C compiler and glib2.
|
||||
The Mono project has developed mono, an x86-specific CL JIT compiler and
|
||||
mint, a portable CLI interpreter. The build process of each of these
|
||||
depends on nothing more than a C compiler, glib2 and libgc.
|
||||
|
||||
However, to provide a working runtime environment, these programs must
|
||||
be supplemented by the class libraries, which are written in C#. This
|
||||
package contains the components written in C#: class libraries,
|
||||
compilers and tools.
|
||||
be supplemented by corlib, a CLR assembly to which they are closely
|
||||
tied. This package provides the C# sources for corlib as well as some
|
||||
additional assemblies and mcs, the Mono C# compiler.
|
||||
|
||||
Build Process for Users.
|
||||
========================
|
||||
To build this package, you must already have a C# compiler installed.
|
||||
Build instructions for *NIX and Microsoft Windows follow.
|
||||
|
||||
If you only want to build a snapshot or a fresh CVS checkout of the
|
||||
sources, you should go into the `mono' sibling directory and issue the
|
||||
following command:
|
||||
Building mcs on *NIX
|
||||
====================
|
||||
|
||||
./autogen --prefix=/usr/local
|
||||
make fullbuild
|
||||
|
||||
That will build and install the code in a single pass. The
|
||||
compilation is bundled with the build due to dependencies on the class
|
||||
libraries on the runtime.
|
||||
|
||||
Build Features for Developers.
|
||||
==============================
|
||||
|
||||
These instructions apply to both Linux and Windows. To build this
|
||||
package, you must already have a C# compiler installed. This means
|
||||
that to build on Linux, you need to get a distribution of the MCS
|
||||
binaries; these are called monocharges. They can be found at
|
||||
www.go-mono.com/daily. On Windows, you can just use the
|
||||
Microsoft compiler. You also need GNU make to build the software (on
|
||||
Windows, you will need for example the Cygwin environment setup).
|
||||
mcs provides a set of makefiles which make it easy to build and install
|
||||
mcs on *NIX systems like Linux or FreeBSD where mcs is already
|
||||
installed.
|
||||
|
||||
To build the compiler and class libraries, run:
|
||||
|
||||
make
|
||||
make -f makefile.gnu
|
||||
|
||||
The libraries will be placed in the directory class/lib/ and the mcs
|
||||
compiler executable in mcs/.
|
||||
|
||||
To install them, run the following:
|
||||
To install them, run the following, where prefix identifies where you
|
||||
want the files installed:
|
||||
|
||||
make install
|
||||
|
||||
The default prefix is /usr/local. To change this configuration option type:
|
||||
|
||||
echo prefix=/your-prefix >> build/config.make
|
||||
|
||||
If you get "corlib out of sync" errors, try
|
||||
|
||||
make PROFILE="atomic"
|
||||
|
||||
The difference between the two modes is explained farther down.
|
||||
|
||||
Troubleshooting
|
||||
===============
|
||||
|
||||
Occasionally, something in the compiler or runtime changes enough that
|
||||
an existing installation cannot complete a full build from cvs. In this case,
|
||||
go to http://go-mono.com/daily and download a monocharge or monolite tarball.
|
||||
Unpack and copy the .dlls to $prefix/lib and .exes to $prefix/bin/. Then
|
||||
you should be able to complete the build normally (i.e. using make fullbuild).
|
||||
|
||||
wget http://go-mono.com/daily/monolite-20031028.tar.gz
|
||||
tar -zxvf monolite-20031028.tar.gz
|
||||
cd monolite-20031028
|
||||
cp *.exe /usr/local/bin/.
|
||||
cp *.dll /usr/local/lib/.
|
||||
|
||||
Monocharges
|
||||
===========
|
||||
make -f makefile.gnu install prefix=/usr/local
|
||||
|
||||
If you are tracking Mono's development, you may sometimes need to share
|
||||
the compiled libraries with others, you can do:
|
||||
the compiled libraries with others. If you want to produce an easily
|
||||
distributable tarball, run:
|
||||
|
||||
make monocharge
|
||||
make -f makefile.gnu dist
|
||||
|
||||
Or a light version, which contains only the essential libraries and
|
||||
results in a much smaller file:
|
||||
Building mcs on Windows
|
||||
=======================
|
||||
|
||||
make monocharge-lite
|
||||
It is also possible to build mcs on Windows using the Microsoft .NET
|
||||
framework. This may be convenient if you do not have access to a working
|
||||
mcs setup. To build the compiler and class libraries, run:
|
||||
|
||||
Configuration
|
||||
=============
|
||||
make
|
||||
|
||||
If you want to change the configuration options for the build process,
|
||||
place your configuration options in build/config.make
|
||||
The libraries will be placed in the directory class/lib/ and the mcs
|
||||
compiler executable in mcs/. They can then be copied to /usr/lib and
|
||||
/usr/bin or wherever desired on the target system.
|
||||
|
||||
A list of variables that control the build are listed in the file
|
||||
build/config-default.make.
|
||||
|
||||
Build profiles? What?
|
||||
======================
|
||||
|
||||
Don't worry about them too much. If you're wondering which to use:
|
||||
use the default if you can (that's why it's the default!) and use
|
||||
the atomic if you have to.
|
||||
|
||||
The default profile uses the C# compiler and class libaries as they
|
||||
are built. This lets you build MCS without needing to have already
|
||||
installed it, but can fail if the libraries change significantly.
|
||||
(This is the source of the dreaded "corlib out of sync" warning, most
|
||||
of the time.)
|
||||
|
||||
The atomic profile tries to use the system compiler and preexisting
|
||||
MCS libraries. New libaries are built against this constant reference
|
||||
point, so if a newly built library has a binary incompatibility, the
|
||||
rest of your build can proceed.
|
||||
|
||||
If you want to always use the atomic profile, run this command:
|
||||
|
||||
echo PROFILE=atomic >> build/config.make
|
||||
|
||||
More About the Build System
|
||||
===========================
|
||||
|
||||
More information is found in build/README.*. Here's a quick rundown
|
||||
of the features:
|
||||
|
||||
* Unified build system for Windows and Linux. Windows is still
|
||||
fairly untested, but "should work." Unfortunately I don't
|
||||
have a Windows machine to test on, but Gonzalo can get
|
||||
corlib to build I think and that's about as complicated as
|
||||
it gets.
|
||||
|
||||
* Profile support. 'make PROFILE=profilename' or 'export
|
||||
PROFILE=profilename ; make' will work. Profiles are defined
|
||||
in build/profiles/profilename.make ; right now there isn't
|
||||
too much going on. The 'bootstrap' profile will build the
|
||||
way makefile.gnu did on Linux, by setting MONO_PATH and
|
||||
using mcs/mcs.exe; the default profile will build against
|
||||
the existing system libraries and compile with 'mcs', which
|
||||
should reduce a lot of 'corlib out of sync' warnings.
|
||||
|
||||
* Important variables are shared among makefiles now; you can
|
||||
edit build/config.make (see build/config-default.make for a
|
||||
template) and give global settings, or just have a much
|
||||
saner time of writing new makefiles.
|
||||
|
||||
* Response files, stamps, and other build trivia now all land
|
||||
in build/deps/, making the library build directories
|
||||
cleaner.
|
||||
|
||||
* Test libraries now live in class/Library/Library_test.dll,
|
||||
not class/Library/Test. 'make test' will build the test DLL,
|
||||
'make run-test' will actually run the nunit tests. Set the
|
||||
variable TEST_HARNESS to run with a program other than
|
||||
nunit-console (for example, nunit-gtk).
|
||||
|
||||
* Standardized recursive targets: all, clean, install, test,
|
||||
run-test. Read build/README.makefiles for definitions of
|
||||
what they should do
|
||||
|
||||
* (Relatively) sane 'make dist' target; 'make distcheck'
|
||||
support; cute 'make monocharge' and 'make monocharge-lite'
|
||||
targets. They're made possible because 'make install' now
|
||||
supports DESTDIR a la automake, which I'm sure someone cares
|
||||
about.
|
||||
-29
@@ -1,29 +0,0 @@
|
||||
|
||||
The Mono code is licensed under various different licenses.
|
||||
|
||||
GNU GPL: details avaliable in the file LICENSE.GPL
|
||||
GNU LGPL: details available in the file LICENSE.LGPL
|
||||
MIT X11: text available in the file MIT.X11
|
||||
|
||||
For your convenience copies of the GNU GPL and GNU LGPL are
|
||||
located in the file COPYING and COPYING.LIB.
|
||||
|
||||
* Class Libraries:
|
||||
|
||||
All of the core classes licensed under the terms of
|
||||
the MIT X11 license.
|
||||
|
||||
Third party libraries that we distribute for
|
||||
convenience reasons are distributed under their own
|
||||
terms (all of them allow development of proprietary
|
||||
applications with them).
|
||||
|
||||
Third party libraries include: ByteFX.Data,
|
||||
ICSharpCode.SharpZipLib, Npgsql.
|
||||
|
||||
* Mono C# compiler: GNU GPL
|
||||
|
||||
* Mono Basic compiler: GNU GPL.
|
||||
|
||||
* Various tools in the `tools' directory: GNU GPL.
|
||||
|
||||
@@ -1,15 +0,0 @@
|
||||
Mono compilers and tools.
|
||||
Copyright (C) 2001, 2002, 2003, Ximian and contributors.
|
||||
|
||||
This program is free software; you can redistribute it and/or modify
|
||||
it under the terms of the GNU General Public License as published by
|
||||
the Free Software Foundation;
|
||||
|
||||
This program is distributed in the hope that it will be useful,
|
||||
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
||||
GNU General Public License for more details.
|
||||
|
||||
You should have received a copy of the GNU General Public License
|
||||
along with this program; if not, write to the Free Software
|
||||
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
|
||||
@@ -1,15 +0,0 @@
|
||||
Mono class libraries
|
||||
Copyright (C) Mono project (authors listed in individual ChangeLog entries)
|
||||
|
||||
This library is free software; you can redistribute it and/or
|
||||
modify it under the terms of the GNU Library General Public
|
||||
License as published by the Free Software Foundation.
|
||||
|
||||
This library is distributed in the hope that it will be useful,
|
||||
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
|
||||
Library General Public License for more details.
|
||||
|
||||
You should have received a copy of the GNU Library General Public
|
||||
License along with this library; if not, write to the Free
|
||||
Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
|
||||
-21
@@ -1,21 +0,0 @@
|
||||
Copyright (c) 2001, 2002, 2003 Ximian, Inc and the individuals listed
|
||||
on the ChangeLog entries.
|
||||
|
||||
Permission is hereby granted, free of charge, to any person obtaining
|
||||
a copy of this software and associated documentation files (the
|
||||
"Software"), to deal in the Software without restriction, including
|
||||
without limitation the rights to use, copy, modify, merge, publish,
|
||||
distribute, sublicense, and/or sell copies of the Software, and to
|
||||
permit persons to whom the Software is furnished to do so, subject to
|
||||
the following conditions:
|
||||
|
||||
The above copyright notice and this permission notice shall be
|
||||
included in all copies or substantial portions of the Software.
|
||||
|
||||
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
|
||||
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
|
||||
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
|
||||
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
|
||||
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
|
||||
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
|
||||
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
|
||||
-108
@@ -1,108 +0,0 @@
|
||||
thisdir := .
|
||||
SUBDIRS := build jay mcs class mbas nunit20 monoresgen ilasm tools tests errors docs
|
||||
OVERRIDE_BARE_TARGETS = hells yeah
|
||||
include build/rules.make
|
||||
|
||||
# Define these ourselves to that the platform checks come first
|
||||
|
||||
all: platform-check profile-check all-recursive #all-local
|
||||
|
||||
install: platform-check profile-check install-recursive #install-local
|
||||
|
||||
uninstall: platform-check profile-check uninstall-recursive #uninstall-local
|
||||
|
||||
test: platform-check profile-check test-recursive #test-local
|
||||
|
||||
run-test: run-test-recursive #run-test-local
|
||||
|
||||
clean: clean-recursive #clean-local
|
||||
|
||||
# fun specialty targets
|
||||
|
||||
testcorlib:
|
||||
@cd class/corlib && $(MAKE) test run-test
|
||||
|
||||
# Disting. We need to override $(distdir) here.
|
||||
|
||||
package := mcs-$(VERSION)
|
||||
top_distdir = $(dots)/$(package)
|
||||
distdir = $(top_distdir)
|
||||
export package
|
||||
|
||||
DISTFILES = \
|
||||
AUTHORS \
|
||||
ChangeLog \
|
||||
COPYING \
|
||||
COPYING.LIB \
|
||||
INSTALL.txt \
|
||||
LICENSE \
|
||||
LICENSE.GPL \
|
||||
LICENSE.LGPL \
|
||||
Makefile \
|
||||
mkinstalldirs \
|
||||
MIT.X11 \
|
||||
MonoIcon.png \
|
||||
README \
|
||||
ScalableMonoIcon.svg \
|
||||
winexe.in
|
||||
|
||||
dist-pre:
|
||||
rm -rf $(package)
|
||||
|
||||
dist-post:
|
||||
tar cvzf $(package).tar.gz $(package)
|
||||
|
||||
dist-local: dist-default
|
||||
|
||||
dist-tarball: dist-pre dist-recursive dist-post
|
||||
|
||||
dist: dist-tarball
|
||||
rm -rf $(package)
|
||||
|
||||
# the egrep -v is kind of a hack (to get rid of the makefrags)
|
||||
# but otherwise we have to make dist then make clean which
|
||||
# is sort of not kosher. And it breaks with DIST_ONLY_SUBDIRS.
|
||||
#
|
||||
# We need to set prefix on make so class/System/Makefile can find
|
||||
# the installed System.Xml to build properly
|
||||
|
||||
distcheck:
|
||||
rm -rf InstallTest Distcheck-MCS ; \
|
||||
mkdir InstallTest ; \
|
||||
destdir=`cd InstallTest && pwd` ; \
|
||||
$(MAKE) dist-tarball || exit 1 ; \
|
||||
mv $(package) Distcheck-MCS ; \
|
||||
(cd Distcheck-MCS && \
|
||||
$(MAKE) prefix=$(prefix) && $(MAKE) test && $(MAKE) install DESTDIR="$$destdir" && \
|
||||
$(MAKE) clean && $(MAKE) dist || exit 1) || exit 1 ; \
|
||||
mv Distcheck-MCS $(package) ; \
|
||||
tar tzf $(package)/$(package).tar.gz |sed -e 's,/$$,,' |sort >distdist.list ; \
|
||||
rm $(package)/$(package).tar.gz ; \
|
||||
tar tzf $(package).tar.gz |sed -e 's,/$$,,' |sort >before.list ; \
|
||||
find $(package) |egrep -v '(makefrag|response)' |sed -e 's,/$$,,' |sort >after.list ; \
|
||||
cmp before.list after.list || exit 1 ; \
|
||||
cmp before.list distdist.list || exit 1 ; \
|
||||
rm -f before.list after.list distdist.list ; \
|
||||
rm -rf $(package) InstallTest
|
||||
|
||||
monocharge:
|
||||
chargedir=monocharge-`date -u +%Y%m%d` ; \
|
||||
mkdir "$$chargedir" ; \
|
||||
DESTDIR=`cd "$$chargedir" && pwd` ; \
|
||||
$(MAKE) install DESTDIR="$$DESTDIR" || exit 1 ; \
|
||||
tar cvzf "$$chargedir".tgz "$$chargedir" ; \
|
||||
rm -rf "$$chargedir"
|
||||
|
||||
# A bare-bones monocharge.
|
||||
|
||||
monocharge-lite:
|
||||
chargedir=monocharge-lite-`date -u +%Y%m%d` ; \
|
||||
mkdir "$$chargedir" ; \
|
||||
DESTDIR=`cd "$$chargedir" && pwd` ; \
|
||||
$(MAKE) -C mcs install DESTDIR="$$DESTDIR" || exit 1; \
|
||||
$(MAKE) -C class/corlib install DESTDIR="$$DESTDIR" || exit 1; \
|
||||
$(MAKE) -C class/System install DESTDIR="$$DESTDIR" || exit 1; \
|
||||
$(MAKE) -C class/System.XML install DESTDIR="$$DESTDIR" || exit 1; \
|
||||
$(MAKE) -C class/Mono.CSharp.Debugger install DESTDIR="$$DESTDIR" || exit 1; \
|
||||
tar cvzf "$$chargedir".tgz "$$chargedir" ; \
|
||||
rm -rf "$$chargedir"
|
||||
+2
-1
@@ -1,7 +1,8 @@
|
||||
|
||||
This contains the Mono C# compiler as well as the Mono runtime
|
||||
library.
|
||||
|
||||
See INSTALL.txt for a guide to building and installing mcs.
|
||||
See INSTALL for a guide to building and installing mcs.
|
||||
|
||||
Layout:
|
||||
|
||||
|
||||
@@ -0,0 +1,33 @@
|
||||
|
||||
[1] Building mono + mcs from CVS on *NIX. The Easy Way (tm)
|
||||
-------------------------------------------------------------
|
||||
1. Get mono and mcs from CVS (http://www.go-mono.com/download.html)
|
||||
|
||||
2. Use the script to build mono (mono/doc/mono-build.sh).
|
||||
|
||||
3. Copy the dlls and mcs.exe from the latest monocharge tarball
|
||||
(http://www.gnome-db.org/~gonzalo/mono/) to /where/you/installed/mono/lib and
|
||||
..../bin respectively.
|
||||
|
||||
|
||||
|
||||
[2] Keeping the stuff up to date
|
||||
----------------------------------
|
||||
Once you have followed the above steps, do these ones to keep your installation
|
||||
up to date:
|
||||
|
||||
1. In mcs directory,
|
||||
|
||||
cvs -z3 update -Pd
|
||||
make -f makefile.gnu
|
||||
|
||||
2. Use the mono-build.sh script to update, rebuild and install mono from CVS.
|
||||
Doing a cvs update of mono/doc/mono-build.sh file is also a good idea.
|
||||
|
||||
3. In mcs directory:
|
||||
|
||||
make -f makefile.gnu install prefix=/prefix/of/your/installation/path
|
||||
|
||||
4. In case of troubles (ie, unable to compile mcs/* sources) go to [1].
|
||||
|
||||
-Gonzalo
|
||||
@@ -1,2 +0,0 @@
|
||||
pre-config.make
|
||||
config.make
|
||||
@@ -1,93 +0,0 @@
|
||||
2003-11-12 Jackson Harper <[email protected]>
|
||||
|
||||
* rules.make:
|
||||
* platforms/linux.make: corlib name is now mscorlib.
|
||||
|
||||
2003-11-09 Ben Maurer <[email protected]>
|
||||
|
||||
* profiles/generics.make: add the -2 flag.
|
||||
|
||||
2003-10-28 Jackson Harper <[email protected]>
|
||||
|
||||
* platforms/linux.make: Tell users to read INSTALL.txt not the
|
||||
non-existant README.building.
|
||||
|
||||
2003-10-22 Dick Porter <[email protected]>
|
||||
|
||||
* platforms/win32.make:
|
||||
* platforms/linux.make:
|
||||
* rules.make: Added RESGEN platform-specific tool.
|
||||
|
||||
2003-08-03 Gonzalo Paniagua Javier <[email protected]>
|
||||
|
||||
* config-default.make: the /nowarn arguments are now set on a per
|
||||
library basis.
|
||||
|
||||
2003-07-29 Gonzalo Paniagua Javier <[email protected]>
|
||||
|
||||
* executable.make: install-local depends on the program too.
|
||||
|
||||
2003-07-25 Peter Williams <[email protected]>
|
||||
|
||||
* rules.make (run-test): Make it depend on 'test-local'
|
||||
then 'run-test-local' after 'run-test-recursive'. This way,
|
||||
'make run-test' from the toplevel doesn't recurse through all
|
||||
the directories doing a make test before we run anything.
|
||||
|
||||
2003-07-24 Gonzalo Paniagua Javier <[email protected]>
|
||||
|
||||
* rules.make: run-test depends now on 'test'.
|
||||
|
||||
2003-07-24 Gonzalo Paniagua Javier <[email protected]>
|
||||
|
||||
* rules.make: set corlib to PLATFORM_CORLIB if this is defined.
|
||||
|
||||
2003-07-22 Peter Williams <[email protected]>
|
||||
|
||||
* rules.make (withmcs): Add this developer utility target.
|
||||
|
||||
2003-07-20 Peter Williams <[email protected]>
|
||||
|
||||
* README.platforms: Update docs for changes below.
|
||||
|
||||
* platforms/win32.make (PLATFORM_CORLIB): Set this variable
|
||||
to 'mscorlib.dll', instead of $(corlib) which everything links
|
||||
against. *Almost* everything should link against our corlib --
|
||||
with the exception of corlib_cmp and corlib_res.
|
||||
|
||||
* platforms/linux.make: Same here: corlib.dll
|
||||
|
||||
* rules.make: Define $(corlib) here.
|
||||
|
||||
2003-07-20 Peter Williams <[email protected]>
|
||||
|
||||
* config-default.make (TEST_RUNTIME): Use the platform runtime
|
||||
to run tests, by default.
|
||||
|
||||
* profiles/default.make (TEST_RUNTIME): If our test runtime is
|
||||
mono, use the --debug flag.
|
||||
|
||||
* executable.make (sourcefile): Add a basename so that we can
|
||||
find the nunit sources and so we behave a bit more like
|
||||
library.make
|
||||
|
||||
* config-default.make (TEST_HARNESS): Find nunit-console in its
|
||||
new home.
|
||||
|
||||
2003-07-20 Peter Williams <[email protected]>
|
||||
|
||||
* library.make ($(response)): Do a "Creating ..." line here.
|
||||
|
||||
* executable.make ($(response)): Same.
|
||||
|
||||
* config-default.make: Make warning more forceful.
|
||||
|
||||
* rules.make: Define a useful 'PLATFORM_MONO_NATIVE' that is
|
||||
set if the platform does not have a native runtime (ie, linux).
|
||||
Also reorder some definitions.
|
||||
|
||||
2003-07-20 Peter Williams <[email protected]>
|
||||
|
||||
* Created. See ../ChangeLog for entries earlier than
|
||||
this.
|
||||
|
||||
@@ -1,22 +0,0 @@
|
||||
thisdir = build
|
||||
SUBDIRS =
|
||||
include ../build/rules.make
|
||||
|
||||
all-local install-local test-local run-test-local clean-local uninstall-local:
|
||||
|
||||
DISTFILES = \
|
||||
README.makefiles \
|
||||
README.platforms \
|
||||
README.configury \
|
||||
config-default.make \
|
||||
executable.make \
|
||||
library.make \
|
||||
rules.make \
|
||||
platforms/linux.make \
|
||||
platforms/win32.make \
|
||||
profiles/default.make \
|
||||
profiles/atomic.make \
|
||||
profiles/net_1_0.make
|
||||
|
||||
dist-local: dist-default
|
||||
mkdir $(distdir)/deps
|
||||
Loaded 100 of 4994 files, more files were not shown because too many files have changed in this diff.
Show more
Reference in new issue
Block a user