Compare commits

..
1 Commits
Author SHA1 Message Date
nobody b0784aa131 This commit was manufactured by cvs2svn to create tag 'MCS_0_4'.
svn path=/tags/MCS_0_4/mcs/; revision=171
2001-07-16 01:07:36 +00:00
1882 changed files with 11484 additions and 242850 deletions

No files matched your search

+8 -14
View File
@@ -1,17 +1,11 @@
aclocal.m4
config.cache
config.guess
config.h
config.h.in
config.log
config.status
config.sub
configure
libtool
ltmain.sh
ltconfig
Makefile
Makefile.in
mono-*.tar.gz
stamp-h
config.cache
stamp-h.in
config.status
aclocal.m4
configure
stamp-h
libtool
Makefile.in
config.log
-1
View File
@@ -1,2 +1 @@
Miguel de Icaza ([email protected])
Paolo Molaro ([email protected])
-231
View File
@@ -1,234 +1,3 @@
2002-02-05 Dietmar Maurer <[email protected]>
* mono/tests/enum2.cs: new file with more enum tests.
2002-02-01 Dietmar Maurer <[email protected]>
* mono/tests/jit-long.cs: added some SHL/SHR tests
Fri Feb 1 15:32:36 CET 2002 Paolo Molaro <[email protected]>
* configure.in: allow PKG_CONFIG_PATH for the build-platform
pkg-config invocation.
Fri Feb 1 15:13:25 CET 2002 Paolo Molaro <[email protected]>
* configure.in: add some support/fixes for cross-compilation.
2002-01-14 Dietmar Maurer <[email protected]>
* mono/tests/exception6.cs: new tests for ADD_OVF, MUL_OVF
added tests for SUB_OVF, SUB_OVF_UN
2001-12-21 Dietmar Maurer <[email protected]>
* mono/tests/Makefile.am (TESTSRC): disabled stream-writer test
2001-12-21 Aaron Weber <[email protected]>
* doc/faq (A): added a linebreak that was missing and was causing
a heading to appear badly.
2001-12-20 Aaron Weber <[email protected]>
* doc/faq: added <a name=""> nav links, and moved all MSFT-related
questions into a single section.
2001-12-17 Aaron Weber <[email protected]>
* doc/faq (Q): Question-by-question, line-by-line revision.
2001-12-17 Dietmar Maurer <[email protected]>
* mono/tests/time.cs: new test
2001-11-30 Radek Doulik <[email protected]>
* configure.in: remove ACCESS_UNALIGNED="no" from ppc
2001-11-29 Radek Doulik <[email protected]>
* configure.in (ACCESS_UNALIGNED): uncommented and modified
powerpc-*-linux*
generate mono/arch/ppc/Makefile
2001-11-26 Dietmar Maurer <[email protected]>
* mono/tests/exception3.cs: modified the test to show a bug in the
current exception handling implementation.
2001-11-13 Dick Porter <[email protected]>
* configure.in: Some more tests for pthread features
(specifically, glibc 2.1 doesnt define pthread_mutex_timedlock but
still needs _GNU_SOURCE for PTHREAD_MUTEX_RECURSIVE)
2001-11-09 Dick Porter <[email protected]>
* configure.in: Try and get large file support, but it's not fatal
if it's not there (the io-layer just ignores the high word in that
case.)
Check for windows builds, and only bother to look for pthreads and
large files if we're not building for cygwin or native win32. Not
having pthread support on Posix systems is now a fatal error.
* autogen.sh: Fix ACLOCAL_FLAGS - it wasn't being passed to
aclocal
2001-10-15 Dietmar Maurer <[email protected]>
* mono/tests/Makefile.am: removed JITTESTS, simply run all tests for
target testjit.
2001-10-11 Dietmar Maurer <[email protected]>
* docs/object-layout: more documentation
Mon Oct 8 20:27:50 CEST 2001 Paolo Molaro <[email protected]>
* configure.in: define NO_UNALIGNED_ACCESS for platforms that
can't read on unaligned boundaries
2001-10-04 Dick Porter <[email protected]>
* configure.in: Do some deeper checks on pthreads for some of the
more interesting functions
2001-09-24 Dietmar Maurer <[email protected]>
* mono/tests/Makefile.am (testjit): a new target to test the JITer
* mono/tests/jit-*: added some test for the JITer
2001-09-23 Dick Porter <[email protected]>
* configure.in: Arrange to compile dummy thread support routines
if pthread isnt available
2001-09-23 Dick Porter <[email protected]>
* configure.in: Check for pthread.h, so that we can check for the
HAVE_PTHREAD_H define in config.h
2001-09-21 Dick Porter <[email protected]>
* configure.in: Check for libpthread
2001-09-19 Dietmar Maurer <[email protected]>
* mono/tests/test-ops.cs: added more tests
Mon Sep 10 20:19:00 CEST 2001 Paolo Molaro <[email protected]>
* configure.in: check for sizeof(void*) and for the architecture.
2001-09-05 Dick Porter <[email protected]>
* autogen.sh: Fixed the section that adds $ACLOCAL_FLAGS to the
aclocal invocation, so putting aclocal files in /usr/local works
2001-08-30 Dietmar Maurer <[email protected]>
* *: removed the libffi dependency, mono now compiles on cygwin
* mono/wrapper/build-dll: new file.
2001-08-28 Dietmar Maurer <[email protected]>
* mono/tests/console.cs: impl.
* mono/tests/box.cs: impl.
* mono/tests/stream-writer.cs: impl.
Mon Aug 27 20:24:26 CEST 2001 Paolo Molaro <[email protected]>
* mono/tests/*: New test cases, mostly for virtual method dispatch.
Use make testb for the slow benchmarking programs,
make test for the usual regression test checks.
2001-08-22 Rodrigo Moya <[email protected]>
* mono/cil/Makefile.am:
* mono/wrapper/Makefile.am: use correct variables for installation
directories
Tue Aug 21 18:54:06 CEST 2001 Paolo Molaro <[email protected]>
* mono/tests/exceptions*: enhanced and added more tests for
exceptions.
2001-08-20 Miguel de Icaza <[email protected]>
* mono/Makefile.am (SUBDIRS): Remove `test' from here to allow us
to pass make distcheck
* mono/wrapper/Makefile.am (EXTRA_DIST): Include genwrapper.pl
* configure.in, Makefile.am, runtime/Makefile.am (dist-hook,
install-data-hook): Added mechanism to distribute and install the
dll files.
2001-08-20 Dietmar Maurer <[email protected]>
* mono/tests/stream.cs: new tests for the Stream class
* configure.in: I really need LIBTOOL for libmonowrapper.so, so I
added it again.
2001-08-16 Alex Graveley <[email protected]>
* configure.in: Replace AM_PROG_LIBTOOL with AC_PROG_RANLIB. This
removes libtool dependency on all of Mono.
2001-08-10 Dietmar Maurer <[email protected]>
* mono/tests/array.cs: more array tests
2001-08-09 Dietmar Maurer <[email protected]>
* mono/tests/array.cs: more array tests
2001-08-06 Dietmar Maurer <[email protected]>
* mono/tests/pinvoke.cs: we can now print strings ;-)
* mono/tests/array.cs: new test for arrays
2001-08-02 Alex Graveley <[email protected]>
* libffi/*: Import libffi CVS version, with minor changes to make it
compile.
* mono/interpreter/Makefile.am: Link against
../../libffi/.libs/libffi.a.
* Makefile.am: Add libffi
* autogen.sh: Replace with adapted gnome autogen.sh
* configure.in: Add AC_CONFIG_SUBDIRS(libffi).
2001-08-02 Dietmar Maurer <[email protected]>
* mono/tests/pinvoke.cs: impl.
Wed Aug 1 22:34:52 CEST 2001 Paolo Molaro <[email protected]>
* configure.in, mono/tests: added some tests for the interpreter.
2001-07-15 Sean MacIsaac <[email protected]>
* doc/download: added instructions for cygwin
* doc/c-sharp: removed bit about compiling
* status/compare-assembly.cs: basedir should be there if
parameters are provided.
* status/makefile: made targets to dump info.
2001-07-15 Joe Shaw <[email protected]>
* configure.in: Don't create doc/Makefile as there's nothing there
+1 -1
View File
@@ -1 +1 @@
SUBDIRS = mono doc runtime scripts man
SUBDIRS = mono doc
-10
View File
@@ -1,13 +1,3 @@
2002-Feb-11 Miguel de Icaza <[email protected]>
New release, functional x86-JIT, x86 interpreter, ppc interpreter
Class libraries ship.
Limited compiler ships.
Too many changes to list
2001-07-12 Miguel de Icaza <[email protected]>
New XSLT file from Sergey Chaban for CIL opcodes
+4 -48
View File
@@ -1,52 +1,8 @@
This is MonoNet.
This is Mono.
Installation:
Read doc/download for installation instructions,
or read the HTML version:
http://www.go-mono.com/download.html
A directory roadmap:
doc/
Contains documentation and the web site contents.
mono/
The core of the executable.
metadata/
The library to deal with executables and libraries for
.NET
dis/
CIL executable Disassembler
cli/
Common code for the JIT and the interpreter.
cil/
Common Intermediate Representation, XML
definition of the CIL bytecodes.
interp/
Interpreter for CLI executables.
* Using Mono
Once you have installed the software, you can run a few programs:
monodis program.exe
That will dump the bytecodes for program.exe. Monodis support
a number of options that dumps various metadata tables
(chapter 23 of the Partition III).
You can try the interpreter like this:
mint program.exe
Ximian's portable implementation of .NET
----------
To edit the go-mono website, see doc/README.
-6
View File
@@ -1,6 +0,0 @@
#undef HAVE_PTHREAD
#undef HAVE_PTHREAD_MUTEX_TIMEDLOCK
#undef HAVE_LARGE_FILE_SUPPORT
#undef PLATFORM_WIN32
#undef PLATFORM_WIN32_NATIVE
#undef HAVE_NEW_ICONV
+6 -120
View File
@@ -1,120 +1,6 @@
#!/bin/sh
# Run this to generate all the initial makefiles, etc.
# Ripped off from GNOME macros version
DIE=0
srcdir=`dirname $0`
test -z "$srcdir" && srcdir=.
if [ -n "$MONO_PATH" ]; then
ACLOCAL_FLAGS="-I $MONO_PATH/share/aclocal $ACLOCAL_FLAGS"
PATH="$MONO_PATH/bin:$PATH"
export PATH
fi
(autoconf --version) < /dev/null > /dev/null 2>&1 || {
echo
echo "**Error**: You must have \`autoconf' installed to compile Mono."
echo "Download the appropriate package for your distribution,"
echo "or get the source tarball at ftp://ftp.gnu.org/pub/gnu/"
DIE=1
}
(grep "^AM_PROG_LIBTOOL" $srcdir/configure.in >/dev/null) && {
(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"
echo "(or a newer version if it is available)"
DIE=1
}
}
grep "^AM_GNU_GETTEXT" $srcdir/configure.in >/dev/null && {
grep "sed.*POTFILES" $srcdir/configure.in >/dev/null || \
(gettext --version) < /dev/null > /dev/null 2>&1 || {
echo
echo "**Error**: You must have \`gettext' installed to compile Mono."
echo "Get ftp://alpha.gnu.org/gnu/gettext-0.10.35.tar.gz"
echo "(or a newer version if it is available)"
DIE=1
}
}
(automake --version) < /dev/null > /dev/null 2>&1 || {
echo
echo "**Error**: You must have \`automake' installed to compile Mono."
echo "Get ftp://ftp.gnu.org/pub/gnu/automake-1.3.tar.gz"
echo "(or a newer version if it is available)"
DIE=1
NO_AUTOMAKE=yes
}
# if no automake, don't bother testing for aclocal
test -n "$NO_AUTOMAKE" || (aclocal --version) < /dev/null > /dev/null 2>&1 || {
echo
echo "**Error**: Missing \`aclocal'. The version of \`automake'"
echo "installed doesn't appear recent enough."
echo "Get ftp://ftp.gnu.org/pub/gnu/automake-1.3.tar.gz"
echo "(or a newer version if it is available)"
DIE=1
}
if test "$DIE" -eq 1; then
exit 1
fi
if test -z "$*"; then
echo "**Warning**: I am going to run \`configure' with no arguments."
echo "If you wish to pass any to it, please specify them on the"
echo \`$0\'" command line."
echo
fi
case $CC in
xlc )
am_opt=--include-deps;;
esac
if grep "^AM_PROG_LIBTOOL" configure.in >/dev/null; then
if test -z "$NO_LIBTOOLIZE" ; then
echo "Running libtoolize..."
libtoolize --force --copy
fi
fi
echo "Running aclocal $ACLOCAL_FLAGS ..."
aclocal $ACLOCAL_FLAGS || {
echo
echo "**Error**: aclocal failed. This may mean that you have not"
echo "installed all of the packages you need, or you may need to"
echo "set ACLOCAL_FLAGS to include \"-I \$prefix/share/aclocal\""
echo "for the prefix where you installed the packages whose"
echo "macros were not found"
exit 1
}
if grep "^AM_CONFIG_HEADER" configure.in >/dev/null; then
echo "Running autoheader..."
autoheader || { echo "**Error**: autoheader failed."; exit 1; }
fi
echo "Running automake --gnu $am_opt ..."
automake --add-missing --gnu $am_opt ||
{ echo "**Error**: automake failed."; exit 1; }
echo "Running autoconf ..."
autoconf || { echo "**Error**: autoconf failed."; exit 1; }
conf_flags="--enable-maintainer-mode --enable-compile-warnings" #--enable-iso-c
if test x$NOCONFIGURE = x; then
echo Running $srcdir/configure $conf_flags "$@" ...
$srcdir/configure $conf_flags "$@" \
&& echo Now type \`make\' to compile $PKG_NAME || exit 1
else
echo Skipping configure process.
fi
libtoolize --automake
automake -a
autoheader
aclocal $ACLOCAL_FLAGS
autoconf
./configure $*
-17
View File
@@ -1,17 +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
/* The number of bytes in a void *. */
#undef SIZEOF_VOID_P
/* Define if you have the <dlfcn.h> header file. */
#undef HAVE_DLFCN_H
/* Name of package */
#undef PACKAGE
/* Version number of package */
#undef VERSION
+10 -289
View File
@@ -1,296 +1,29 @@
AC_INIT(README)
AC_CANONICAL_SYSTEM
AM_CONFIG_HEADER(config.h)
AM_INIT_AUTOMAKE(mono, 0.8)
AM_INIT_AUTOMAKE(mono, 0.3)
AM_MAINTAINER_MODE
AC_CHECK_TOOL(CC, gcc, gcc)
AC_PROG_CC
AM_PROG_CC_STDC
AC_PROG_INSTALL
dnl may require a specific autoconf version
dnl AC_PROG_CC_FOR_BUILD
dnl CC_FOR_BUILD not automatically detected
CC_FOR_BUILD=$CC
BUILD_EXEEXT=
if test "x$cross_compiling" = "xyes"; then
CC_FOR_BUILD=cc
BUILD_EXEEXT=""
fi
AC_SUBST(CC_FOR_BUILD)
AC_SUBST(HOST_CC)
AC_SUBST(BUILD_EXEEXT)
# Set STDC_HEADERS
AC_HEADER_STDC
AC_LIBTOOL_WIN32_DLL
AM_PROG_LIBTOOL
# not 64 bit clean in cross-compile
AC_CHECK_SIZEOF(void *, 4)
dnl ***************************
dnl *** Checks for glib 1.2 ***
dnl ***************************
AM_PATH_GLIB(1.2.0,,
AC_MSG_ERROR([Cannot find GLIB: Is glib-config in path?]))
CFLAGS='-g -Wall -Wunused -Wmissing-prototypes -Wmissing-declarations'
AC_PATH_PROG(PKG_CONFIG, pkg-config, no)
if test "x$PKG_CONFIG" = "xno"; then
AC_MSG_ERROR([You need to install pkg-config])
fi
dnl for use on the build system
dnl pkg-config is stupid
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)
PKG_PATH=
AC_ARG_WITH(crosspkgdir, [ --with-crosspkgdir=/path/to/pkg-config/dir],
if test x$with_crosspkgdir = "x"; then
if test -s $PKG_CONFIG_PATH; then
PKG_PATH=$PKG_CONFIG_PATH
fi
else
PKG_PATH=$with_crosspkgdir
PKG_CONFIG_PATH=$PKG_PATH
export PKG_CONFIG_PATH
fi
)
## Versions of dependencies
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`
GLIB_LIBS=`$PKG_CONFIG --libs glib-2.0`
GMODULE_CFLAGS=`$PKG_CONFIG --cflags gmodule-2.0`
GMODULE_LIBS=`$PKG_CONFIG --libs gmodule-2.0`
GLIB_CFLAGS=`glib-config --cflags glib`
GLIB_LIBS=`glib-config --libs glib`
AC_SUBST(GLIB_CFLAGS)
AC_SUBST(GLIB_LIBS)
AC_SUBST(GMODULE_CFLAGS)
AC_SUBST(GMODULE_LIBS)
dnl ****************************************
dnl *** Check if we're building on win32 ***
dnl ****************************************
AC_MSG_CHECKING([if building for some Win32 platform])
case "$host" in
*-*-mingw*|*-*-cygwin*)
platform_win32=yes
AC_DEFINE(PLATFORM_WIN32)
;;
*)
platform_win32=no
;;
esac
AC_MSG_RESULT($platform_win32)
AM_CONDITIONAL(PLATFORM_WIN32, test x$platform_win32 = xyes)
if test x$platform_win32 = xyes; then
AC_MSG_CHECKING([if building for native Win32])
case "$host" in
*-*-mingw*)
platform_win32_native=yes
AC_DEFINE(PLATFORM_WIN32_NATIVE)
;;
*)
platform_win32_native=no
;;
esac
AC_MSG_RESULT($platform_win32_native)
AM_CONDITIONAL(PLATFORM_WIN32_NATIVE,
test x$platform_win32_native = xyes)
fi
if test x$platform_win32 = xno; then
dnl ******************************************************************
dnl *** Check for large file support ***
dnl *** (If we were using autoconf 2.50 we'd use AC_SYS_LARGEFILE) ***
dnl ******************************************************************
# Check that off_t can represent 2**63 - 1 correctly, working around
# potential compiler bugs. Defines LARGE_FILE_SUPPORT, adds $1 to
# CFLAGS and sets $large_offt to yes if the test succeeds
large_offt=no
AC_DEFUN(LARGE_FILES, [
large_CPPFLAGS=$CPPFLAGS
CPPFLAGS="$CPPFLAGS $1"
AC_TRY_RUN([
#include <sys/types.h>
#define BIG_OFF_T (((off_t)1<<62)-1+((off_t)1<<62))
int main(void) {
int big_off_t=((BIG_OFF_T%2147483629==721) &&
(BIG_OFF_T%2147483647==1));
if(big_off_t) {
exit(0);
} else {
exit(1);
}
}
], [
AC_MSG_RESULT(ok)
AC_DEFINE(HAVE_LARGE_FILE_SUPPORT)
CFLAGS="$CFLAGS $1"
large_offt=yes
], [
AC_MSG_RESULT(no)
], "")
CPPFLAGS=$large_CPPFLAGS
])
AC_MSG_CHECKING(if off_t is 64 bits wide)
LARGE_FILES("")
if test $large_offt = no; then
AC_MSG_CHECKING(if _FILE_OFFSET_BITS=64 gives 64 bit off_t)
LARGE_FILES("-D_FILE_OFFSET_BITS=64")
fi
if test $large_offt = no; then
AC_MSG_WARN([No 64 bit file size support available])
fi
dnl *****************************
dnl *** Checks for libpthread ***
dnl *****************************
AC_SEARCH_LIBS(pthread_create, pthread, [
AM_CONDITIONAL(THREADS_PTHREAD, true)
AC_DEFINE(HAVE_PTHREAD)
# Need pthread_mutex_timedlock
pthread_CFLAGS=""
orig_CPPFLAGS=$CPPFLAGS
# This is a gcc-specific error, but we already set
# gcc-specific options in CFLAGS
CPPFLAGS="$CPPFLAGS -Werror-implicit-function-declaration"
AC_MSG_CHECKING(for pthread_mutex_timedlock)
AC_TRY_COMPILE([ #include <pthread.h>], [
pthread_mutex_t mut=PTHREAD_MUTEX_INITIALIZER;
pthread_mutex_timedlock(&mut, NULL);
], [
# Works!
AC_MSG_RESULT(ok)
AC_DEFINE(HAVE_PTHREAD_MUTEX_TIMEDLOCK)
], [
AC_MSG_RESULT(no)
# glibc requires -D_GNU_SOURCE before it will declare
# this function
AC_MSG_CHECKING(whether _GNU_SOURCE is needed for pthread_mutex_timedlock)
CPPFLAGS="$CPPFLAGS -D_GNU_SOURCE"
AC_TRY_COMPILE([ #include <pthread.h>], [
pthread_mutex_t mut=PTHREAD_MUTEX_INITIALIZER;
pthread_mutex_timedlock(&mut, NULL);
], [
AC_MSG_RESULT(ok)
pthread_CFLAGS="-D_GNU_SOURCE"
AC_DEFINE(HAVE_PTHREAD_MUTEX_TIMEDLOCK)
], [
AC_MSG_RESULT(no)
dnl Add other variants here
AC_MSG_WARN(Working around pthread_mutex_timedlock)
])
])
CPPFLAGS=$orig_CPPFLAGS
CFLAGS="$CFLAGS $pthread_CFLAGS"
# Need PTHREAD_MUTEX_RECURSIVE
pthread_CFLAGS=""
orig_CPPFLAGS=$CPPFLAGS
# This is a gcc-specific error, but we already set
# gcc-specific options in CFLAGS
CPPFLAGS="$CPPFLAGS -Werror-implicit-function-declaration"
AC_MSG_CHECKING(for PTHREAD_MUTEX_RECURSIVE)
AC_TRY_COMPILE([ #include <pthread.h>], [
pthread_mutexattr_t attr;
pthread_mutexattr_settype(&attr, PTHREAD_MUTEX_RECURSIVE);
], [
# Works!
AC_MSG_RESULT(ok)
], [
AC_MSG_RESULT(no)
# glibc requires -D_GNU_SOURCE before it will declare
# this macro
AC_MSG_CHECKING(whether _GNU_SOURCE is needed for PTHREAD_MUTEX_RECURSIVE)
CPPFLAGS="$CPPFLAGS -D_GNU_SOURCE"
AC_TRY_COMPILE([ #include <pthread.h>], [
pthread_mutexattr_t attr;
pthread_mutexattr_settype(&attr, PTHREAD_MUTEX_RECURSIVE);
], [
AC_MSG_RESULT(ok)
pthread_CFLAGS="-D_GNU_SOURCE"
], [
AC_MSG_RESULT(no)
dnl Add other variants here
AC_MSG_ERROR([PTHREAD_MUTEX_RECURSIVE not found])
])
])
CPPFLAGS=$orig_CPPFLAGS
CFLAGS="$CFLAGS $pthread_CFLAGS"
], [
AC_MSG_ERROR([libpthread is required on non-win32 hosts])
])
fi
if test "x$cross_compiling" = "xno"; then
# check for new iconv version
AC_MSG_CHECKING(for new iconv)
AC_CACHE_VAL(new_iconv,[
AC_TRY_RUN([#include <stdio.h>
#include <iconv.h>
int main()
{
exit (iconv_open ("UTF-16le", "UTF-8") == (iconv_t)-1);
}
],
new_iconv=yes,new_iconv=)])
if test -n "$new_iconv"; then
AC_MSG_RESULT(yes)
AC_DEFINE(HAVE_NEW_ICONV)
else
AC_MSG_RESULT(no)
fi
fi
TARGET="unknown"
ACCESS_UNALIGNED="yes"
case "$host" in
#mips-sgi-irix5.* | mips-sgi-irix6.*) TARGET=MIPS; ACCESS_UNALIGNED="no";;
i*86-*-*) TARGET=X86; arch_target=x86;;
sparc*-*-*) TARGET=SPARC; ACCESS_UNALIGNED="no";;
#alpha*-*-linux* | alpha*-*-osf*) TARGET=ALPHA; ACCESS_UNALIGNED="no";;
#m68k-*-linux*) TARGET=M68K;;
powerpc-*-linux* | powerpc-*-sysv*) TARGET=POWERPC; arch_target=ppc;;
#arm-*-linux-*) TARGET=ARM; ACCESS_UNALIGNED="no";;
esac
if test ${TARGET} = unknown; then
CFLAGS="$CFLAGS -DNO_PORT"
AC_MSG_WARN("mono has not been ported to $host: some things may not work.")
fi
if test ${ACCESS_UNALIGNED} = no; then
CPPFLAGS="$CPPFLAGS -DNO_UNALIGNED_ACCESS"
fi
AM_CONDITIONAL(MIPS_GCC, test ${TARGET}${ac_cv_prog_gcc} = MIPSyes)
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(M68K, test x$TARGET = xM68K)
AM_CONDITIONAL(POWERPC, test x$TARGET = xPOWERPC)
AM_CONDITIONAL(ARM, test x$TARGET = xARM)
AC_SUBST(arch_target)
CFLAGS='-g -Wall -Wunused -Wmissing-prototypes -Wmissing-declarations'
AC_SUBST(CFLAGS)
AC_OUTPUT([
@@ -299,18 +32,6 @@ mono/Makefile
mono/metadata/Makefile
mono/dis/Makefile
mono/cil/Makefile
mono/arch/Makefile
mono/arch/x86/Makefile
mono/arch/ppc/Makefile
mono/arch/sparc/Makefile
mono/interpreter/Makefile
mono/tests/Makefile
mono/wrapper/Makefile
mono/monoburg/Makefile
mono/jit/Makefile
mono/io-layer/Makefile
runtime/Makefile
scripts/Makefile
man/Makefile
doc/Makefile
mono/doc/Makefile
])
+4 -15
View File
@@ -1,7 +1,7 @@
WEB_FILES= \
WEB_FILES=
c-sharp class-library contact contributing documentation download \
faq gcc-frontend ideas index passport rationale resources \
roadmap runtime status team testing thanks tools porting anoncvs
faq gcc-frontend ideas index makefile passport rationale resources \
roadmap runtime status team testing thanks tools
OTHERS= pending resources-pending todo
@@ -12,16 +12,5 @@ all-docs: $(WEB_FILES)
runtime documentation download faq contributing \
resources status > all-docs
class-status: class-status.in pending-classes Makefile.am
cat class-status.in pending-classes > class-status
pending-classes: pending-classes.in Makefile.am
echo "This is a list of pending classes, and links to their documentation on MSDN.Microsoft.com<p><p>" > pending-classes
for i in `cat pending-classes.in`; do x=`echo $$i | sed s/\\\.//g`; link=`echo http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrf@@@ClassTopic.asp | sed "s/@@@/$$x/"`; echo " <a href=\"$$link\">$$i</a><br>" >> pending-classes; done
webit: class-status
webit:
(cd web; make && make push)
push-notes:
scp release-notes/mono* www@www:/web/cvsmodules/mono/archive
-54
View File
@@ -1,54 +0,0 @@
* Anonymous CVS access
Anonymous access to the Mono is available currently from the
HispaLinux CVS server (later I will provide a nice
anoncvs.go-mono.com alias).
Sources are currently being updated every hour.
The server is currently located in Spain. If you want to
become an AnonCVS mirror, go <a href="#mirror">here</a>
** Checking out the sources
To check out the sources for the first time from the
repository, use this command:
<pre>
export CVSROOT=:pserver:[email protected]:/mono
cvs -z3 co mcs mono gtk-sharp
</pre>
That will get you the compiler and class libraries (mcs), the
interpreter and JITer (mono) and the Gtk# bindings.
The server is located in Spain.
** Updating the sources
To update your sources every day, you use this command:
<pre>
export CVSROOT=:pserver:[email protected]:/mono
cvs -z3 update -dP mcs mono gtk-sharp
</pre>
** Thanks
Thanks to <a href="http://www.hispalinux.es">HispaLinux</a>
for providing this Anon CVS server. The server is located in
Spain.
Special thanks to Jesus Climent, Rodrigo Moya, Juantomás
García and Ismael Olea for making this happen.
<a name="#mirror">
** Becoming an AnonCVS mirror
To become an AnonCVS mirror, you currently need about 20
megabytes of free disk space and bandwidth that you do not
mind sharing (you probably want enough to spare).
I need to be able to rsync to your machine from the main CVS
server. The preferred method to rsync is to setup ssh in your
machine.
+57 -127
View File
@@ -1,44 +1,15 @@
* MCS: The Ximian C# compiler
MCS is currently able to compile itself and many more C#
programs (there is a test suite included that you can use).
MCS began as an experiment to learn the features of C# by
writing a large C# program. MCS is currently able to parse C#
programs and create an internal tree representation of the
program. MCS can parse itself.
We are in feature completion mode right now. There are still
a couple of areas that are not covered by the Mono compiler, but
they are very very few at this point.
MCS was able to parse itself on April 2001, MCS compiled itself
for the first time on December 28 2001. MCS became self hosting
on January 3rd, 2002.
A test suite is maintained to track the progress of
the compiler and various programs are routinely compiled and
ran.
** Obtaining MCS
The Mono C# compiler is part of the `mcs' module in the Mono CVS
you can get it from our <a href="anoncvs.html">Anonymous CVS</a> server,
or you can get nightly <a href="download.html">download page</a>.
** Running MCS
MCS is written in C# and uses heavily the .NET APIs. At this point
MCS only runs on Windows with the .NET Framework SDK installed. Work
is progressing rapidly in our JIT engine and our class libraries to
allow MCS to be ran in non-Windows systems.
** Reporting Bugs in MCS
When you report a bug, try to provide a small test case that would
show the error so we can include this as part of the Mono C# regression
test suite.
If the bug is an error or a warning that we do not flag, write
a sample program called `csXXXX.cs' where XXXX is the code number
that is used by the Microsoft C# compiler that illustrates the
problem. That way we can also do regression tests on the invalid
input.
Work is progressing quickly on various fronts in the C#
compiler. Recently I started using the System.Reflection API
to load system type definitions and avoid self-population of
types in the compiler and dropped my internal Type
representation in favor of using the CLI's System.Type.
** Phases of the compiler
@@ -71,62 +42,59 @@
have to postpone this decision until the above steps
are finished.
* Code generation: The code generation is done through
the System.Reflection.Emit API.
* Code generation: nothing done so far, but I do not
expect this to be hard, as I will just use
System.Reflection.Emit to generate the code.
</ul>
** CIL Optimizations.
The compiler performs a number of simple optimizations on its input:
constant folding (this is required by the C# language spec) and
can perform dead code elimination.
Other more interesting optimizations like hoisting are not possible
at this point since the compiler output at this point does not
generate an intermediate representation that is suitable to
perform basic block computation.
Adding an intermediate layer to enable the basic block
computation to the compiler should be a simple task, but we
are considering having a generic CIL optimizer. Since all the
information that is required to perform basic block-based
optimizations is available at the CIL level, we might just skip
this step altogether and have just a generic IL optimizer that
would perform hoisting on arbitrary CIL programs, not only
those produced by MCS.
If this tool is further expanded to perform constant folding
(not needed for our C# compiler, as it is already in there)
and dead code elimination, other compiler authors might be
able to use this generic CIL optimizer in their projects
reducing their time to develop a production compiler.
<a name="tasks">
** Current pending tasks
Simple tasks:
<ul>
* Redo the way we deal with built-in operators.
</ul>
* Array declarations are currently being ignored,
Larger tasks:
<ul>
* PInvoke declarations are not supported.
* Pre-processing is not supported.
* Attribute declarations and passing currently ignored.
* Compiler does not pass around line/col information from tokenizer for error reporting.
* Jay does not work correctly with `error'
productions, making parser errors hard to point. It
would be best to port the Bison-To-Java compiler to
become Bison-to-C# compiler.
Nick Drochak has started a project on SourceForge for this.
You can find the project at: <a href="http://sourceforge.net/projects/jb2csharp/">
http://sourceforge.net/projects/jb2csharp/</a>
become Bison-to-C# compiler ([email protected]
might have more information)
</ul>
* Semantic Analysis: Return path coverage and
initialization before use coverage are two great
features of C# that help reduce the number of bugs
in applications. It is one interesting hack.
Critical tasks:
<ul>
* Resolve "base" classes and "base" interfaces for
classes, structs and interfaces.
Once this is done, we can actually do the semantic
analysis, because otherwise we do not know who our
parents are.
</ul>
Interesting tasks:
<ul>
* Finishing the JB port from Java to C#. If you are
interested in working on this, please contact Brian
Jepson (bjepson at oreilly d-o-t com).
More on JB at: <a href="http://www.cs.colorado.edu/~dennis/software/jb.html">
http://www.cs.colorado.edu/~dennis/software/jb.html</a>
JB will allow us to move from the Berkeley Yacc
based Jay to a Bison-based compiler (better error
reporting and recovery).
</ul>
** Questions and Answers
@@ -155,10 +123,6 @@ Q: If your C# compiler is written in C#, how do you plan on getting
We will do this through an implementation of the CLI Virtual
Execution System for Unix (our JIT engine).
Our JIT engine is working for the purposes of using the compiler.
The supporting class libraries are being worked on to fully support
the compiler.
Q: Do you use Bison?
A: No, currently I am using Jay which is a port of Berkeley Yacc to
@@ -169,53 +133,19 @@ A: No, currently I am using Jay which is a port of Berkeley Yacc to
In the future I want to port one of the Bison/Java ports to C# for
the parser.
Q: Should someone work on a GCC front-end to C#?
Q: How do I compile it?
A: I would love if someone does, and we would love to help anyone that
takes on that task, but we do not have the time or expertise to
build a C# compiler with the GCC engine. I find it a lot more fun
personally to work on C# on a C# compiler, which has an intrinsic
beauty.
A: Compiling MCS currently requires you to run my port of <a
href="http://primates.ximian.com/~miguel/code/jay.cs.tar.gz">Jay to
C#</a> on a Unix system to generate the parser, and then you need
to use Microsoft's .NET csc.exe compiler to compile the compiler.
We can provide help and assistance to anyone who would like to work
on this task.
You only need to compile the compiler compiler (C code), the
samples are Java samples that I did not port, and you do not need
them.
Q: Should someone make a GCC backend that will generate CIL images?
A: I would love to see a backend to GCC that generates CIL images. It
would provide a ton of free compilers that would generate CIL
code. This is something that people would want to look into
anyways for Windows interoperation in the future.
Again, we would love to provide help and assistance to anyone
interested in working in such a project.
Q: What about making a front-end to GCC that takes CIL images and
generates native code?
A: I would love to see this, specially since GCC supports this same
feature for Java Byte Codes. You could use the metadata library
from Mono to read the byte codes (ie, this would be your
"front-end") and generate the trees that get passed to the
optimizer.
Ideally our implementation of the CLI will be available as a shared
library that could be linked with your application as its runtime
support.
Again, we would love to provide help and assistance to anyone
interested in working in such a project.
Q: But would this work around the GPL in the GCC compiler and allow
people to work on non-free front-ends?
A: People can already do this by targeting the JVM byte codes (there
are about 130 compilers for various languages that target the JVM).
Q: Why are you writing a JIT engine instead of a front-end to GCC?
A: The JIT engine and runtime engine will be able to execute CIL
executables generated on Windows.
It might be simple to port Jay.cs to Windows, but I have not tried
this.
You might also want to look at the <a href="faq.html#gcc">GCC</a>
section on the main FAQ
-138
View File
@@ -1,138 +0,0 @@
* CVS Access
If you are an active Mono developer, you can get a CVS account
that hosts the Mono source code.
If you are not a developer, but want to track the development, please
see the <a href="anoncvs.html">AnonCVS</a> instructions.
Send an e-mail to miguel with your public SSH key for this
purpose. Please specify if the key was generated with SSH1 or SSH2.
If you are using SSH2, please generate your key using:
<pre>
ssh-keygen -t rsa
</pre>
And mail me the id_rsa.pub file.
If you are using SSH1, run:
<pre>
ssh-keygen
</pre>
And mail me your identity.pub file.
You will need CVS and SSH. Windows users can get both by
installing Cygwin (<a
href="http://www.cygwin.com">http://www.cygwin.com</a>)
Unix users will probably have those tools installed already.
** Checking out the sources
To check out the sources for the first time from the
repository, use this command:
<pre>
export CVS_RSH=ssh
export [email protected]:/cvs/public
cvs -z3 co mcs mono
</pre>
** Updating your sources
Every day people will be making changes, to get your latest
updated sources, use:
<pre>
cvs -z3 update -Pd mcs mono
</pre>
Note: The '-z3' enables compression for the whole cvs action.
The '-Pd' makes the update operation (P)rune directories that
have been deleted and get new (d)irectories added to the
repository.
** Making patches
Usually you will want to make a patch to contribute, and let
other people review it before commiting it. To obtain such a
"patch", you type:
<pre>
cd directory-you-want-to-diff
cvs -z3 diff -u > file.diff
mail [email protected] < file.diff
</pre>
** Keeping track of changes.
We provide two e-mail based mechanisms to keep track of
changes to the code base:
<ul>
* <a href="mailto:[email protected]">
[email protected]</a>: This mailing list receives
in patch form all the changes that are being made to the
CVS.
* <a href="mailto:[email protected]">
[email protected]</a>: This mailing list only
receives the CVS commit logs with a list of files
modified.
</ul>
We hope to offer LXR and Bonsai in the future as well.
** Commiting your work
Once you get approval to commit to the CVS, or if you are
commiting code that you are the maintainer of, you will want
to commit your code to CVS.
To do this, you have to "add" any new files that you created:
<pre>
cvs add new-file.cs
</pre>
And then commit your changes to the repository:
<pre>
cvs commit file-1.cs file-2.cs
</pre>
** The Mailing List
To keep track of the various development and changes to the
CVS tree, you can subscribe to the [email protected].
To subscribe, send an email message to
[email protected] and in the body of the
message put `subscribe'.
This will send you an email message every time a change is
made to the CVS repository, together with the information that
the author of the changes submitted.
** Recommendations
Please do not commit code that would break the compile to the
CVS, because that normally wastes everybody's time. Two things
are important in this step: trying to build your sources and making
sure that you add all the new files before you do a commit.
To build the sources, most of the type trying the `make' command
is enough. In some cases (the class libraries) we use nant, so
you need to run nant manually.
Use ChangeLog entries so we can keep textual descriptions of
your work, and use the contents of your ChangeLog file as the
CVS commit message (ie, paste the contents of this into the
editor buffer).
If you are making changes to someone else's code, please make
sure you get in touch with the maintainer of that code before
applying patches. You want to avoid commiting conflicting
work to someone else's code.
+28 -44
View File
@@ -26,22 +26,7 @@
If nobody is working on it, mail <a
href="mailto:[email protected]">[email protected]</a>
with the class you want to implement and CC <a
href="mailto:[email protected]">[email protected]</a>.
You can also track live the activities of the Mono CVS module
by subscribing to the <a
href="http://lists.ximian.com/mailman/listinfo/mono-cvs-list">mono-cvs-list</a>
** Missing features
Our class libraries miss some features, for example, most classes
do not implement the serialization bits at all, it would be a good
contribution to add this to each class.
This is a simple task, but it needs to be done in a compatible way
with the Microsoft.NET classes: using the same arguments to serialize
and reincarnate data.
href="mailto:[email protected]">[email protected]</a>
** Layout
@@ -106,11 +91,33 @@
** Licensing
The class library is being licensed under the terms of the
<a
href="http://www.opensource.org/licenses/mit-license.html">MIT
license.</a> This is the same license used by the X11 window
system.
The class library will be licensed under the terms of the GNU
LGPL. Some people have pointed out that the plain LGPL is
troublesome for embedded use of the Mono class libraries. So
we are considering to use the GPL with a special exception
(like the <a
href="http://www.gnu.org/software/classpath/classpath.html">GNU
Classpath</a> project did.
The exception to the GPL would be:
<i>The library is distributed under the terms of the GNU General
Public License with the following exception:
If you link this library against your own program, then you do not
need to release the source code for that program. However, any
changes that you make to the library itself, or to any native
methods upon which the library relies, must be re-distributed in
accordance with the terms of the GPL.</i>
If you are going to contribute, please keep in mind that we
might require you to agree that Ximian might adjust the
license to enable the use of the class libraries on embedded
systems or to develop proprietary applications using Mono.
We suggest that you assign the copyright of your work to the
GNOME Foundation or the Free Software Foundation to simplify
defending the code in case it is used inappropiately.
** Class Library testing
@@ -118,9 +125,6 @@
the correctness of the class library, compiler, and JIT
engine.
Please write your regression tests using <a
href="http://nunit.sourceforge.net">NUnit</a>
** Coding conventions
Please follow the conventions on the ECMA specification (On
@@ -156,26 +160,6 @@
In those cases, use the keyword "LAMESPEC".
** Namespaces
We are using a number of namespaces in the class libraries for
private classes when we need them, you are encouraged to use these:
<pre>
Mono
.Languages // General Compiler classes
.CSharp // Specific C# parsing/tokenizing classes
.MonoBASIC // Specific VB.NET/MonoBASIC parsing/tokenizing classes
.Python // Specific Python parsing/tokenizing classes
.Runtime
.LateBind // General latebinding-support for MonoBASIC/Python
.MonoBASIC // Specific runtime classes for MonoBASIC programs
.Python // Specific runtime classes for Python programs
.Web
.UI
.Utils // Gaurav utility classes
</pre>
** FAQ
Frequently asked questions about the class library:
+15 -395
View File
@@ -4,404 +4,24 @@
registered to work on what parts of the system. These list
work-in-progress components currently.
Browse the current <a href="class-status/index.html">status</a>.
<ul>
* Per <a href="class-status/per-assembly.html">Assembly</a>
* Per <a href="class-status/per-completion.html">Completion</a>
* Per <a href="class-status/per-maintainer.html">Maintainer</a>
* Per <a href="class-status/per-unimplemented.html">Unimplemented</a>
</ul>
A better mechanism will soon be in place, I just did this
really quickly, as we already got one duplicated implementation.
You can also download the XML <a
href="class-status/maintainers.xml">maintainers</a> file that
contains the actual maintainers list.
You can also download the master <a
href="class-status/class.xml">Class Status XML</a> file.
I am sure we can generate better reports, if you are
interested in contributing, let <a
href="mailto:[email protected]">me</a> know.
* List of not-implemented classes
These classes are only classes pending from the CORLIB assembly
other assemblies are not yet listed. We are going to be working
on an improved status display for pending classes.
Please bear with us in the meantime.
This is a list of pending classes, and links to their documentation on MSDN.Microsoft.com<p><p>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfMicrosoftWin32Registry␍ClassTopic.asp">Microsoft.Win32.Registry␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfMicrosoftWin32RegistryHive␍ClassTopic.asp">Microsoft.Win32.RegistryHive␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfMicrosoftWin32RegistryKey␍ClassTopic.asp">Microsoft.Win32.RegistryKey␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystem__ComObject␍ClassTopic.asp">System.__ComObject␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemActivator␍ClassTopic.asp">System.Activator␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemArgIterator␍ClassTopic.asp">System.ArgIterator␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemAssemblyLoadEventHandler␍ClassTopic.asp">System.AssemblyLoadEventHandler␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemAsyncCallback␍ClassTopic.asp">System.AsyncCallback␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemCrossAppDomainDelegate␍ClassTopic.asp">System.CrossAppDomainDelegate␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemDBNull␍ClassTopic.asp">System.DBNull␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemDiagnosticsSymbolStoreSymDocumentType␍ClassTopic.asp">System.Diagnostics.SymbolStore.SymDocumentType␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemDiagnosticsSymbolStoreSymLanguageType␍ClassTopic.asp">System.Diagnostics.SymbolStore.SymLanguageType␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemDiagnosticsSymbolStoreSymLanguageVendor␍ClassTopic.asp">System.Diagnostics.SymbolStore.SymLanguageVendor␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemEventHandler␍ClassTopic.asp">System.EventHandler␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemGlobalizationCompareInfo␍ClassTopic.asp">System.Globalization.CompareInfo␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemGlobalizationHebrewCalendar␍ClassTopic.asp">System.Globalization.HebrewCalendar␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemGlobalizationHijriCalendar␍ClassTopic.asp">System.Globalization.HijriCalendar␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemGlobalizationJapaneseCalendar␍ClassTopic.asp">System.Globalization.JapaneseCalendar␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemGlobalizationKoreanCalendar␍ClassTopic.asp">System.Globalization.KoreanCalendar␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemGlobalizationRegionInfo␍ClassTopic.asp">System.Globalization.RegionInfo␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemGlobalizationSortKey␍ClassTopic.asp">System.Globalization.SortKey␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemGlobalizationStringInfo␍ClassTopic.asp">System.Globalization.StringInfo␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemGlobalizationTaiwanCalendar␍ClassTopic.asp">System.Globalization.TaiwanCalendar␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemGlobalizationTextElementEnumerator␍ClassTopic.asp">System.Globalization.TextElementEnumerator␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemGlobalizationTextInfo␍ClassTopic.asp">System.Globalization.TextInfo␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemGlobalizationThaiBuddhistCalendar␍ClassTopic.asp">System.Globalization.ThaiBuddhistCalendar␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemIOEndOfStreamException␍ClassTopic.asp">System.IO.EndOfStreamException␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemIOIsolatedStorageIsolatedStorage␍ClassTopic.asp">System.IO.IsolatedStorage.IsolatedStorage␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemIOIsolatedStorageIsolatedStorageException␍ClassTopic.asp">System.IO.IsolatedStorage.IsolatedStorageException␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemIOIsolatedStorageIsolatedStorageFile␍ClassTopic.asp">System.IO.IsolatedStorage.IsolatedStorageFile␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemIOPathTooLongException␍ClassTopic.asp">System.IO.PathTooLongException␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemReflectionEmitMethodRental␍ClassTopic.asp">System.Reflection.Emit.MethodRental␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemReflectionMemberFilter␍ClassTopic.asp">System.Reflection.MemberFilter␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemReflectionMissing␍ClassTopic.asp">System.Reflection.Missing␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemReflectionModuleResolveEventHandler␍ClassTopic.asp">System.Reflection.ModuleResolveEventHandler␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemReflectionPointer␍ClassTopic.asp">System.Reflection.Pointer␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemReflectionStrongNameKeyPair␍ClassTopic.asp">System.Reflection.StrongNameKeyPair␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemReflectionTargetException␍ClassTopic.asp">System.Reflection.TargetException␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemReflectionTypeFilter␍ClassTopic.asp">System.Reflection.TypeFilter␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemResolveEventHandler␍ClassTopic.asp">System.ResolveEventHandler␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeCompilerServicesAccessedThroughPropertyAttribute␍ClassTopic.asp">System.Runtime.CompilerServices.AccessedThroughPropertyAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeCompilerServicesCallConvCdecl␍ClassTopic.asp">System.Runtime.CompilerServices.CallConvCdecl␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeCompilerServicesCallConvFastcall␍ClassTopic.asp">System.Runtime.CompilerServices.CallConvFastcall␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeCompilerServicesCallConvStdcall␍ClassTopic.asp">System.Runtime.CompilerServices.CallConvStdcall␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeCompilerServicesCallConvThiscall␍ClassTopic.asp">System.Runtime.CompilerServices.CallConvThiscall␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeCompilerServicesCompilationRelaxationsAttribute␍ClassTopic.asp">System.Runtime.CompilerServices.CompilationRelaxationsAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeCompilerServicesCompilerGlobalScopeAttribute␍ClassTopic.asp">System.Runtime.CompilerServices.CompilerGlobalScopeAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeCompilerServicesCustomConstantAttribute␍ClassTopic.asp">System.Runtime.CompilerServices.CustomConstantAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeCompilerServicesDateTimeConstantAttribute␍ClassTopic.asp">System.Runtime.CompilerServices.DateTimeConstantAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeCompilerServicesDecimalConstantAttribute␍ClassTopic.asp">System.Runtime.CompilerServices.DecimalConstantAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeCompilerServicesDiscardableAttribute␍ClassTopic.asp">System.Runtime.CompilerServices.DiscardableAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeCompilerServicesIDispatchConstantAttribute␍ClassTopic.asp">System.Runtime.CompilerServices.IDispatchConstantAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeCompilerServicesIsVolatile␍ClassTopic.asp">System.Runtime.CompilerServices.IsVolatile␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeCompilerServicesIUnknownConstantAttribute␍ClassTopic.asp">System.Runtime.CompilerServices.IUnknownConstantAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeCompilerServicesRequiredAttributeAttribute␍ClassTopic.asp">System.Runtime.CompilerServices.RequiredAttributeAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesArrayWithOffset␍ClassTopic.asp">System.Runtime.InteropServices.ArrayWithOffset␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesAssemblyRegistrationFlags␍ClassTopic.asp">System.Runtime.InteropServices.AssemblyRegistrationFlags␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesAutomationProxyAttribute␍ClassTopic.asp">System.Runtime.InteropServices.AutomationProxyAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesBIND_OPTS␍ClassTopic.asp">System.Runtime.InteropServices.BIND_OPTS␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesBINDPTR␍ClassTopic.asp">System.Runtime.InteropServices.BINDPTR␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesCALLCONV␍ClassTopic.asp">System.Runtime.InteropServices.CALLCONV␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesClassInterfaceAttribute␍ClassTopic.asp">System.Runtime.InteropServices.ClassInterfaceAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesClassInterfaceType␍ClassTopic.asp">System.Runtime.InteropServices.ClassInterfaceType␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesCoClassAttribute␍ClassTopic.asp">System.Runtime.InteropServices.CoClassAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesComAliasNameAttribute␍ClassTopic.asp">System.Runtime.InteropServices.ComAliasNameAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesComConversionLossAttribute␍ClassTopic.asp">System.Runtime.InteropServices.ComConversionLossAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesComEventInterfaceAttribute␍ClassTopic.asp">System.Runtime.InteropServices.ComEventInterfaceAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesCOMException␍ClassTopic.asp">System.Runtime.InteropServices.COMException␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesComImportAttribute␍ClassTopic.asp">System.Runtime.InteropServices.ComImportAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesComInterfaceType␍ClassTopic.asp">System.Runtime.InteropServices.ComInterfaceType␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesComMemberType␍ClassTopic.asp">System.Runtime.InteropServices.ComMemberType␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesComRegisterFunctionAttribute␍ClassTopic.asp">System.Runtime.InteropServices.ComRegisterFunctionAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesComSourceInterfacesAttribute␍ClassTopic.asp">System.Runtime.InteropServices.ComSourceInterfacesAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesComUnregisterFunctionAttribute␍ClassTopic.asp">System.Runtime.InteropServices.ComUnregisterFunctionAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesComVisibleAttribute␍ClassTopic.asp">System.Runtime.InteropServices.ComVisibleAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesCONNECTDATA␍ClassTopic.asp">System.Runtime.InteropServices.CONNECTDATA␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesCurrencyWrapper␍ClassTopic.asp">System.Runtime.InteropServices.CurrencyWrapper␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesDESCKIND␍ClassTopic.asp">System.Runtime.InteropServices.DESCKIND␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesDispatchWrapper␍ClassTopic.asp">System.Runtime.InteropServices.DispatchWrapper␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesDispIdAttribute␍ClassTopic.asp">System.Runtime.InteropServices.DispIdAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesDISPPARAMS␍ClassTopic.asp">System.Runtime.InteropServices.DISPPARAMS␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesELEMDESC␍ClassTopic.asp">System.Runtime.InteropServices.ELEMDESC␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesErrorWrapper␍ClassTopic.asp">System.Runtime.InteropServices.ErrorWrapper␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesEXCEPINFO␍ClassTopic.asp">System.Runtime.InteropServices.EXCEPINFO␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesExpandoIExpando␍ClassTopic.asp">System.Runtime.InteropServices.Expando.IExpando␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesExporterEventKind␍ClassTopic.asp">System.Runtime.InteropServices.ExporterEventKind␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesExtensibleClassFactory␍ClassTopic.asp">System.Runtime.InteropServices.ExtensibleClassFactory␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesFILETIME␍ClassTopic.asp">System.Runtime.InteropServices.FILETIME␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesFUNCDESC␍ClassTopic.asp">System.Runtime.InteropServices.FUNCDESC␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesFUNCFLAGS␍ClassTopic.asp">System.Runtime.InteropServices.FUNCFLAGS␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesFUNCKIND␍ClassTopic.asp">System.Runtime.InteropServices.FUNCKIND␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesGCHandle␍ClassTopic.asp">System.Runtime.InteropServices.GCHandle␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesGuidAttribute␍ClassTopic.asp">System.Runtime.InteropServices.GuidAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesHandleRef␍ClassTopic.asp">System.Runtime.InteropServices.HandleRef␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesICustomAdapter␍ClassTopic.asp">System.Runtime.InteropServices.ICustomAdapter␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesICustomFactory␍ClassTopic.asp">System.Runtime.InteropServices.ICustomFactory␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesICustomMarshaler␍ClassTopic.asp">System.Runtime.InteropServices.ICustomMarshaler␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesIDispatchImplAttribute␍ClassTopic.asp">System.Runtime.InteropServices.IDispatchImplAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesIDispatchImplType␍ClassTopic.asp">System.Runtime.InteropServices.IDispatchImplType␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesIDLDESC␍ClassTopic.asp">System.Runtime.InteropServices.IDLDESC␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesIDLFLAG␍ClassTopic.asp">System.Runtime.InteropServices.IDLFLAG␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesIMPLTYPEFLAGS␍ClassTopic.asp">System.Runtime.InteropServices.IMPLTYPEFLAGS␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesImportedFromTypeLibAttribute␍ClassTopic.asp">System.Runtime.InteropServices.ImportedFromTypeLibAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesImporterEventKind␍ClassTopic.asp">System.Runtime.InteropServices.ImporterEventKind␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesInterfaceTypeAttribute␍ClassTopic.asp">System.Runtime.InteropServices.InterfaceTypeAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesInvalidComObjectException␍ClassTopic.asp">System.Runtime.InteropServices.InvalidComObjectException␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesInvalidOleVariantTypeException␍ClassTopic.asp">System.Runtime.InteropServices.InvalidOleVariantTypeException␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesINVOKEKIND␍ClassTopic.asp">System.Runtime.InteropServices.INVOKEKIND␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesIRegistrationServices␍ClassTopic.asp">System.Runtime.InteropServices.IRegistrationServices␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesITypeLibConverter␍ClassTopic.asp">System.Runtime.InteropServices.ITypeLibConverter␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesITypeLibExporterNameProvider␍ClassTopic.asp">System.Runtime.InteropServices.ITypeLibExporterNameProvider␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesITypeLibExporterNotifySink␍ClassTopic.asp">System.Runtime.InteropServices.ITypeLibExporterNotifySink␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesITypeLibImporterNotifySink␍ClassTopic.asp">System.Runtime.InteropServices.ITypeLibImporterNotifySink␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesLCIDConversionAttribute␍ClassTopic.asp">System.Runtime.InteropServices.LCIDConversionAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesLIBFLAGS␍ClassTopic.asp">System.Runtime.InteropServices.LIBFLAGS␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesMarshalDirectiveException␍ClassTopic.asp">System.Runtime.InteropServices.MarshalDirectiveException␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesObjectCreationDelegate␍ClassTopic.asp">System.Runtime.InteropServices.ObjectCreationDelegate␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesPARAMDESC␍ClassTopic.asp">System.Runtime.InteropServices.PARAMDESC␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesPARAMFLAG␍ClassTopic.asp">System.Runtime.InteropServices.PARAMFLAG␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesPreserveSigAttribute␍ClassTopic.asp">System.Runtime.InteropServices.PreserveSigAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesPrimaryInteropAssemblyAttribute␍ClassTopic.asp">System.Runtime.InteropServices.PrimaryInteropAssemblyAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesProgIdAttribute␍ClassTopic.asp">System.Runtime.InteropServices.ProgIdAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesRegistrationServices␍ClassTopic.asp">System.Runtime.InteropServices.RegistrationServices␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesRuntimeEnvironment␍ClassTopic.asp">System.Runtime.InteropServices.RuntimeEnvironment␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesSafeArrayRankMismatchException␍ClassTopic.asp">System.Runtime.InteropServices.SafeArrayRankMismatchException␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesSafeArrayTypeMismatchException␍ClassTopic.asp">System.Runtime.InteropServices.SafeArrayTypeMismatchException␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesSEHException␍ClassTopic.asp">System.Runtime.InteropServices.SEHException␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesSTATSTG␍ClassTopic.asp">System.Runtime.InteropServices.STATSTG␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesSYSKIND␍ClassTopic.asp">System.Runtime.InteropServices.SYSKIND␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesTYPEATTR␍ClassTopic.asp">System.Runtime.InteropServices.TYPEATTR␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesTYPEDESC␍ClassTopic.asp">System.Runtime.InteropServices.TYPEDESC␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesTYPEFLAGS␍ClassTopic.asp">System.Runtime.InteropServices.TYPEFLAGS␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesTYPEKIND␍ClassTopic.asp">System.Runtime.InteropServices.TYPEKIND␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesTYPELIBATTR␍ClassTopic.asp">System.Runtime.InteropServices.TYPELIBATTR␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesTypeLibConverter␍ClassTopic.asp">System.Runtime.InteropServices.TypeLibConverter␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesTypeLibExporterFlags␍ClassTopic.asp">System.Runtime.InteropServices.TypeLibExporterFlags␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesTypeLibFuncAttribute␍ClassTopic.asp">System.Runtime.InteropServices.TypeLibFuncAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesTypeLibFuncFlags␍ClassTopic.asp">System.Runtime.InteropServices.TypeLibFuncFlags␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesTypeLibImporterFlags␍ClassTopic.asp">System.Runtime.InteropServices.TypeLibImporterFlags␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesTypeLibTypeAttribute␍ClassTopic.asp">System.Runtime.InteropServices.TypeLibTypeAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesTypeLibTypeFlags␍ClassTopic.asp">System.Runtime.InteropServices.TypeLibTypeFlags␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesTypeLibVarAttribute␍ClassTopic.asp">System.Runtime.InteropServices.TypeLibVarAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesTypeLibVarFlags␍ClassTopic.asp">System.Runtime.InteropServices.TypeLibVarFlags␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesUCOMIBindCtx␍ClassTopic.asp">System.Runtime.InteropServices.UCOMIBindCtx␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesUCOMIConnectionPoint␍ClassTopic.asp">System.Runtime.InteropServices.UCOMIConnectionPoint␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesUCOMIConnectionPointContainer␍ClassTopic.asp">System.Runtime.InteropServices.UCOMIConnectionPointContainer␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesUCOMIEnumConnectionPoints␍ClassTopic.asp">System.Runtime.InteropServices.UCOMIEnumConnectionPoints␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesUCOMIEnumConnections␍ClassTopic.asp">System.Runtime.InteropServices.UCOMIEnumConnections␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesUCOMIEnumMoniker␍ClassTopic.asp">System.Runtime.InteropServices.UCOMIEnumMoniker␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesUCOMIEnumString␍ClassTopic.asp">System.Runtime.InteropServices.UCOMIEnumString␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesUCOMIEnumVARIANT␍ClassTopic.asp">System.Runtime.InteropServices.UCOMIEnumVARIANT␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesUCOMIMoniker␍ClassTopic.asp">System.Runtime.InteropServices.UCOMIMoniker␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesUCOMIPersistFile␍ClassTopic.asp">System.Runtime.InteropServices.UCOMIPersistFile␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesUCOMIRunningObjectTable␍ClassTopic.asp">System.Runtime.InteropServices.UCOMIRunningObjectTable␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesUCOMIStream␍ClassTopic.asp">System.Runtime.InteropServices.UCOMIStream␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesUCOMITypeComp␍ClassTopic.asp">System.Runtime.InteropServices.UCOMITypeComp␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesUCOMITypeInfo␍ClassTopic.asp">System.Runtime.InteropServices.UCOMITypeInfo␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesUCOMITypeLib␍ClassTopic.asp">System.Runtime.InteropServices.UCOMITypeLib␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesUnknownWrapper␍ClassTopic.asp">System.Runtime.InteropServices.UnknownWrapper␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesVARDESC␍ClassTopic.asp">System.Runtime.InteropServices.VARDESC␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeInteropServicesVARFLAGS␍ClassTopic.asp">System.Runtime.InteropServices.VARFLAGS␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingActivatedClientTypeEntry␍ClassTopic.asp">System.Runtime.Remoting.ActivatedClientTypeEntry␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingActivatedServiceTypeEntry␍ClassTopic.asp">System.Runtime.Remoting.ActivatedServiceTypeEntry␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingActivationUrlAttribute␍ClassTopic.asp">System.Runtime.Remoting.Activation.UrlAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingChannelsBaseChannelObjectWithProperties␍ClassTopic.asp">System.Runtime.Remoting.Channels.BaseChannelObjectWithProperties␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingChannelsBaseChannelSinkWithProperties␍ClassTopic.asp">System.Runtime.Remoting.Channels.BaseChannelSinkWithProperties␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingChannelsBaseChannelWithProperties␍ClassTopic.asp">System.Runtime.Remoting.Channels.BaseChannelWithProperties␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingChannelsChannelDataStore␍ClassTopic.asp">System.Runtime.Remoting.Channels.ChannelDataStore␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingChannelsChannelServices␍ClassTopic.asp">System.Runtime.Remoting.Channels.ChannelServices␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingChannelsClientChannelSinkStack␍ClassTopic.asp">System.Runtime.Remoting.Channels.ClientChannelSinkStack␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingChannelsIChannel␍ClassTopic.asp">System.Runtime.Remoting.Channels.IChannel␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingChannelsIChannelDataStore␍ClassTopic.asp">System.Runtime.Remoting.Channels.IChannelDataStore␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingChannelsIChannelReceiver␍ClassTopic.asp">System.Runtime.Remoting.Channels.IChannelReceiver␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingChannelsIChannelReceiverHook␍ClassTopic.asp">System.Runtime.Remoting.Channels.IChannelReceiverHook␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingChannelsIChannelSender␍ClassTopic.asp">System.Runtime.Remoting.Channels.IChannelSender␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingChannelsIChannelSinkBase␍ClassTopic.asp">System.Runtime.Remoting.Channels.IChannelSinkBase␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingChannelsIClientChannelSink␍ClassTopic.asp">System.Runtime.Remoting.Channels.IClientChannelSink␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingChannelsIClientChannelSinkProvider␍ClassTopic.asp">System.Runtime.Remoting.Channels.IClientChannelSinkProvider␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingChannelsIClientChannelSinkStack␍ClassTopic.asp">System.Runtime.Remoting.Channels.IClientChannelSinkStack␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingChannelsIClientFormatterSink␍ClassTopic.asp">System.Runtime.Remoting.Channels.IClientFormatterSink␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingChannelsIClientFormatterSinkProvider␍ClassTopic.asp">System.Runtime.Remoting.Channels.IClientFormatterSinkProvider␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingChannelsIClientResponseChannelSinkStack␍ClassTopic.asp">System.Runtime.Remoting.Channels.IClientResponseChannelSinkStack␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingChannelsIServerChannelSink␍ClassTopic.asp">System.Runtime.Remoting.Channels.IServerChannelSink␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingChannelsIServerChannelSinkProvider␍ClassTopic.asp">System.Runtime.Remoting.Channels.IServerChannelSinkProvider␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingChannelsIServerChannelSinkStack␍ClassTopic.asp">System.Runtime.Remoting.Channels.IServerChannelSinkStack␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingChannelsIServerFormatterSinkProvider␍ClassTopic.asp">System.Runtime.Remoting.Channels.IServerFormatterSinkProvider␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingChannelsIServerResponseChannelSinkStack␍ClassTopic.asp">System.Runtime.Remoting.Channels.IServerResponseChannelSinkStack␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingChannelsITransportHeaders␍ClassTopic.asp">System.Runtime.Remoting.Channels.ITransportHeaders␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingChannelsServerChannelSinkStack␍ClassTopic.asp">System.Runtime.Remoting.Channels.ServerChannelSinkStack␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingChannelsServerProcessing␍ClassTopic.asp">System.Runtime.Remoting.Channels.ServerProcessing␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingChannelsSinkProviderData␍ClassTopic.asp">System.Runtime.Remoting.Channels.SinkProviderData␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingChannelsTransportHeaders␍ClassTopic.asp">System.Runtime.Remoting.Channels.TransportHeaders␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingContextsContextProperty␍ClassTopic.asp">System.Runtime.Remoting.Contexts.ContextProperty␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingContextsCrossContextDelegate␍ClassTopic.asp">System.Runtime.Remoting.Contexts.CrossContextDelegate␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingContextsIContextPropertyActivator␍ClassTopic.asp">System.Runtime.Remoting.Contexts.IContextPropertyActivator␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingContextsIContributeClientContextSink␍ClassTopic.asp">System.Runtime.Remoting.Contexts.IContributeClientContextSink␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingContextsIContributeDynamicSink␍ClassTopic.asp">System.Runtime.Remoting.Contexts.IContributeDynamicSink␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingContextsIContributeEnvoySink␍ClassTopic.asp">System.Runtime.Remoting.Contexts.IContributeEnvoySink␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingContextsIContributeObjectSink␍ClassTopic.asp">System.Runtime.Remoting.Contexts.IContributeObjectSink␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingContextsIContributeServerContextSink␍ClassTopic.asp">System.Runtime.Remoting.Contexts.IContributeServerContextSink␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingIChannelInfo␍ClassTopic.asp">System.Runtime.Remoting.IChannelInfo␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingIEnvoyInfo␍ClassTopic.asp">System.Runtime.Remoting.IEnvoyInfo␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingInternalRemotingServices␍ClassTopic.asp">System.Runtime.Remoting.InternalRemotingServices␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingIObjectHandle␍ClassTopic.asp">System.Runtime.Remoting.IObjectHandle␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingIRemotingTypeInfo␍ClassTopic.asp">System.Runtime.Remoting.IRemotingTypeInfo␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingLifetimeClientSponsor␍ClassTopic.asp">System.Runtime.Remoting.Lifetime.ClientSponsor␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingLifetimeILease␍ClassTopic.asp">System.Runtime.Remoting.Lifetime.ILease␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingLifetimeISponsor␍ClassTopic.asp">System.Runtime.Remoting.Lifetime.ISponsor␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingLifetimeLeaseState␍ClassTopic.asp">System.Runtime.Remoting.Lifetime.LeaseState␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingLifetimeLifetimeServices␍ClassTopic.asp">System.Runtime.Remoting.Lifetime.LifetimeServices␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMessagingAsyncResult␍ClassTopic.asp">System.Runtime.Remoting.Messaging.AsyncResult␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMessagingCallContext␍ClassTopic.asp">System.Runtime.Remoting.Messaging.CallContext␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMessagingConstructionCall␍ClassTopic.asp">System.Runtime.Remoting.Messaging.ConstructionCall␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMessagingConstructionResponse␍ClassTopic.asp">System.Runtime.Remoting.Messaging.ConstructionResponse␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMessagingHeader␍ClassTopic.asp">System.Runtime.Remoting.Messaging.Header␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMessagingHeaderHandler␍ClassTopic.asp">System.Runtime.Remoting.Messaging.HeaderHandler␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMessagingILogicalThreadAffinative␍ClassTopic.asp">System.Runtime.Remoting.Messaging.ILogicalThreadAffinative␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMessagingIMessageCtrl␍ClassTopic.asp">System.Runtime.Remoting.Messaging.IMessageCtrl␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMessagingIMessageSink␍ClassTopic.asp">System.Runtime.Remoting.Messaging.IMessageSink␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMessagingIMethodCallMessage␍ClassTopic.asp">System.Runtime.Remoting.Messaging.IMethodCallMessage␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMessagingInternalMessageWrapper␍ClassTopic.asp">System.Runtime.Remoting.Messaging.InternalMessageWrapper␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMessagingIRemotingFormatter␍ClassTopic.asp">System.Runtime.Remoting.Messaging.IRemotingFormatter␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMessagingLogicalCallContext␍ClassTopic.asp">System.Runtime.Remoting.Messaging.LogicalCallContext␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMessagingMessageSurrogateFilter␍ClassTopic.asp">System.Runtime.Remoting.Messaging.MessageSurrogateFilter␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMessagingMethodCall␍ClassTopic.asp">System.Runtime.Remoting.Messaging.MethodCall␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMessagingMethodCallMessageWrapper␍ClassTopic.asp">System.Runtime.Remoting.Messaging.MethodCallMessageWrapper␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMessagingMethodResponse␍ClassTopic.asp">System.Runtime.Remoting.Messaging.MethodResponse␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMessagingMethodReturnMessageWrapper␍ClassTopic.asp">System.Runtime.Remoting.Messaging.MethodReturnMessageWrapper␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMessagingOneWayAttribute␍ClassTopic.asp">System.Runtime.Remoting.Messaging.OneWayAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMessagingRemotingSurrogateSelector␍ClassTopic.asp">System.Runtime.Remoting.Messaging.RemotingSurrogateSelector␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMessagingReturnMessage␍ClassTopic.asp">System.Runtime.Remoting.Messaging.ReturnMessage␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMetadataSoapAttribute␍ClassTopic.asp">System.Runtime.Remoting.Metadata.SoapAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMetadataSoapFieldAttribute␍ClassTopic.asp">System.Runtime.Remoting.Metadata.SoapFieldAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMetadataSoapMethodAttribute␍ClassTopic.asp">System.Runtime.Remoting.Metadata.SoapMethodAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMetadataSoapOption␍ClassTopic.asp">System.Runtime.Remoting.Metadata.SoapOption␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMetadataSoapParameterAttribute␍ClassTopic.asp">System.Runtime.Remoting.Metadata.SoapParameterAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMetadataSoapTypeAttribute␍ClassTopic.asp">System.Runtime.Remoting.Metadata.SoapTypeAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMetadataW3cXsd2001ISoapXsd␍ClassTopic.asp">System.Runtime.Remoting.Metadata.W3cXsd2001.ISoapXsd␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMetadataW3cXsd2001SoapAnyUri␍ClassTopic.asp">System.Runtime.Remoting.Metadata.W3cXsd2001.SoapAnyUri␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMetadataW3cXsd2001SoapBase64Binary␍ClassTopic.asp">System.Runtime.Remoting.Metadata.W3cXsd2001.SoapBase64Binary␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMetadataW3cXsd2001SoapDate␍ClassTopic.asp">System.Runtime.Remoting.Metadata.W3cXsd2001.SoapDate␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMetadataW3cXsd2001SoapDateTime␍ClassTopic.asp">System.Runtime.Remoting.Metadata.W3cXsd2001.SoapDateTime␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMetadataW3cXsd2001SoapDay␍ClassTopic.asp">System.Runtime.Remoting.Metadata.W3cXsd2001.SoapDay␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMetadataW3cXsd2001SoapDuration␍ClassTopic.asp">System.Runtime.Remoting.Metadata.W3cXsd2001.SoapDuration␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMetadataW3cXsd2001SoapEntities␍ClassTopic.asp">System.Runtime.Remoting.Metadata.W3cXsd2001.SoapEntities␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMetadataW3cXsd2001SoapEntity␍ClassTopic.asp">System.Runtime.Remoting.Metadata.W3cXsd2001.SoapEntity␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMetadataW3cXsd2001SoapHexBinary␍ClassTopic.asp">System.Runtime.Remoting.Metadata.W3cXsd2001.SoapHexBinary␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMetadataW3cXsd2001SoapId␍ClassTopic.asp">System.Runtime.Remoting.Metadata.W3cXsd2001.SoapId␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMetadataW3cXsd2001SoapIdref␍ClassTopic.asp">System.Runtime.Remoting.Metadata.W3cXsd2001.SoapIdref␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMetadataW3cXsd2001SoapIdrefs␍ClassTopic.asp">System.Runtime.Remoting.Metadata.W3cXsd2001.SoapIdrefs␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMetadataW3cXsd2001SoapInteger␍ClassTopic.asp">System.Runtime.Remoting.Metadata.W3cXsd2001.SoapInteger␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMetadataW3cXsd2001SoapLanguage␍ClassTopic.asp">System.Runtime.Remoting.Metadata.W3cXsd2001.SoapLanguage␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMetadataW3cXsd2001SoapMonth␍ClassTopic.asp">System.Runtime.Remoting.Metadata.W3cXsd2001.SoapMonth␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMetadataW3cXsd2001SoapMonthDay␍ClassTopic.asp">System.Runtime.Remoting.Metadata.W3cXsd2001.SoapMonthDay␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMetadataW3cXsd2001SoapName␍ClassTopic.asp">System.Runtime.Remoting.Metadata.W3cXsd2001.SoapName␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMetadataW3cXsd2001SoapNcName␍ClassTopic.asp">System.Runtime.Remoting.Metadata.W3cXsd2001.SoapNcName␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMetadataW3cXsd2001SoapNegativeInteger␍ClassTopic.asp">System.Runtime.Remoting.Metadata.W3cXsd2001.SoapNegativeInteger␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMetadataW3cXsd2001SoapNmtoken␍ClassTopic.asp">System.Runtime.Remoting.Metadata.W3cXsd2001.SoapNmtoken␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMetadataW3cXsd2001SoapNmtokens␍ClassTopic.asp">System.Runtime.Remoting.Metadata.W3cXsd2001.SoapNmtokens␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMetadataW3cXsd2001SoapNonNegativeInteger␍ClassTopic.asp">System.Runtime.Remoting.Metadata.W3cXsd2001.SoapNonNegativeInteger␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMetadataW3cXsd2001SoapNonPositiveInteger␍ClassTopic.asp">System.Runtime.Remoting.Metadata.W3cXsd2001.SoapNonPositiveInteger␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMetadataW3cXsd2001SoapNormalizedString␍ClassTopic.asp">System.Runtime.Remoting.Metadata.W3cXsd2001.SoapNormalizedString␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMetadataW3cXsd2001SoapNotation␍ClassTopic.asp">System.Runtime.Remoting.Metadata.W3cXsd2001.SoapNotation␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMetadataW3cXsd2001SoapPositiveInteger␍ClassTopic.asp">System.Runtime.Remoting.Metadata.W3cXsd2001.SoapPositiveInteger␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMetadataW3cXsd2001SoapQName␍ClassTopic.asp">System.Runtime.Remoting.Metadata.W3cXsd2001.SoapQName␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMetadataW3cXsd2001SoapTime␍ClassTopic.asp">System.Runtime.Remoting.Metadata.W3cXsd2001.SoapTime␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMetadataW3cXsd2001SoapToken␍ClassTopic.asp">System.Runtime.Remoting.Metadata.W3cXsd2001.SoapToken␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMetadataW3cXsd2001SoapYear␍ClassTopic.asp">System.Runtime.Remoting.Metadata.W3cXsd2001.SoapYear␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMetadataW3cXsd2001SoapYearMonth␍ClassTopic.asp">System.Runtime.Remoting.Metadata.W3cXsd2001.SoapYearMonth␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingMetadataXmlFieldOrderOption␍ClassTopic.asp">System.Runtime.Remoting.Metadata.XmlFieldOrderOption␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingProxiesProxyAttribute␍ClassTopic.asp">System.Runtime.Remoting.Proxies.ProxyAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingProxiesRealProxy␍ClassTopic.asp">System.Runtime.Remoting.Proxies.RealProxy␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingRemotingConfiguration␍ClassTopic.asp">System.Runtime.Remoting.RemotingConfiguration␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingRemotingException␍ClassTopic.asp">System.Runtime.Remoting.RemotingException␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingRemotingServices␍ClassTopic.asp">System.Runtime.Remoting.RemotingServices␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingRemotingTimeoutException␍ClassTopic.asp">System.Runtime.Remoting.RemotingTimeoutException␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingServerException␍ClassTopic.asp">System.Runtime.Remoting.ServerException␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingServicesEnterpriseServicesHelper␍ClassTopic.asp">System.Runtime.Remoting.Services.EnterpriseServicesHelper␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingServicesITrackingHandler␍ClassTopic.asp">System.Runtime.Remoting.Services.ITrackingHandler␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingServicesTrackingServices␍ClassTopic.asp">System.Runtime.Remoting.Services.TrackingServices␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingSoapServices␍ClassTopic.asp">System.Runtime.Remoting.SoapServices␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingTypeEntry␍ClassTopic.asp">System.Runtime.Remoting.TypeEntry␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingWellKnownClientTypeEntry␍ClassTopic.asp">System.Runtime.Remoting.WellKnownClientTypeEntry␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingWellKnownServiceTypeEntry␍ClassTopic.asp">System.Runtime.Remoting.WellKnownServiceTypeEntry␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeSerializationFormatter␍ClassTopic.asp">System.Runtime.Serialization.Formatter␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeSerializationFormatterConverter␍ClassTopic.asp">System.Runtime.Serialization.FormatterConverter␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeSerializationFormattersBinaryBinaryFormatter␍ClassTopic.asp">System.Runtime.Serialization.Formatters.Binary.BinaryFormatter␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeSerializationFormattersInternalRM␍ClassTopic.asp">System.Runtime.Serialization.Formatters.InternalRM␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeSerializationFormattersInternalST␍ClassTopic.asp">System.Runtime.Serialization.Formatters.InternalST␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeSerializationFormattersServerFault␍ClassTopic.asp">System.Runtime.Serialization.Formatters.ServerFault␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeSerializationFormattersSoapFault␍ClassTopic.asp">System.Runtime.Serialization.Formatters.SoapFault␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeSerializationFormattersSoapMessage␍ClassTopic.asp">System.Runtime.Serialization.Formatters.SoapMessage␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeSerializationFormatterServices␍ClassTopic.asp">System.Runtime.Serialization.FormatterServices␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeSerializationObjectIDGenerator␍ClassTopic.asp">System.Runtime.Serialization.ObjectIDGenerator␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeSerializationObjectManager␍ClassTopic.asp">System.Runtime.Serialization.ObjectManager␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeSerializationSerializationBinder␍ClassTopic.asp">System.Runtime.Serialization.SerializationBinder␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeSerializationSerializationEntry␍ClassTopic.asp">System.Runtime.Serialization.SerializationEntry␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeSerializationSerializationInfoEnumerator␍ClassTopic.asp">System.Runtime.Serialization.SerializationInfoEnumerator␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeSerializationSurrogateSelector␍ClassTopic.asp">System.Runtime.Serialization.SurrogateSelector␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeArgumentHandle␍ClassTopic.asp">System.RuntimeArgumentHandle␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityAllowPartiallyTrustedCallersAttribute␍ClassTopic.asp">System.Security.AllowPartiallyTrustedCallersAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityCryptographyCryptoConfig␍ClassTopic.asp">System.Security.Cryptography.CryptoConfig␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityCryptographyDSACryptoServiceProvider␍ClassTopic.asp">System.Security.Cryptography.DSACryptoServiceProvider␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityCryptographyHMACSHA1␍ClassTopic.asp">System.Security.Cryptography.HMACSHA1␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityCryptographyKeyedHashAlgorithm␍ClassTopic.asp">System.Security.Cryptography.KeyedHashAlgorithm␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityCryptographyMACTripleDES␍ClassTopic.asp">System.Security.Cryptography.MACTripleDES␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityCryptographyMaskGenerationMethod␍ClassTopic.asp">System.Security.Cryptography.MaskGenerationMethod␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityCryptographyPasswordDeriveBytes␍ClassTopic.asp">System.Security.Cryptography.PasswordDeriveBytes␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityCryptographyPKCS1MaskGenerationMethod␍ClassTopic.asp">System.Security.Cryptography.PKCS1MaskGenerationMethod␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityCryptographyRandomNumberGenerator␍ClassTopic.asp">System.Security.Cryptography.RandomNumberGenerator␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityCryptographyRC2␍ClassTopic.asp">System.Security.Cryptography.RC2␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityCryptographyRC2CryptoServiceProvider␍ClassTopic.asp">System.Security.Cryptography.RC2CryptoServiceProvider␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityCryptographyRijndael␍ClassTopic.asp">System.Security.Cryptography.Rijndael␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityCryptographyRijndaelManaged␍ClassTopic.asp">System.Security.Cryptography.RijndaelManaged␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityCryptographyRNGCryptoServiceProvider␍ClassTopic.asp">System.Security.Cryptography.RNGCryptoServiceProvider␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityCryptographyRSA␍ClassTopic.asp">System.Security.Cryptography.RSA␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityCryptographyRSACryptoServiceProvider␍ClassTopic.asp">System.Security.Cryptography.RSACryptoServiceProvider␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityCryptographyRSAOAEPKeyExchangeDeformatter␍ClassTopic.asp">System.Security.Cryptography.RSAOAEPKeyExchangeDeformatter␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityCryptographyRSAOAEPKeyExchangeFormatter␍ClassTopic.asp">System.Security.Cryptography.RSAOAEPKeyExchangeFormatter␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityCryptographyRSAParameters␍ClassTopic.asp">System.Security.Cryptography.RSAParameters␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityCryptographyRSAPKCS1KeyExchangeDeformatter␍ClassTopic.asp">System.Security.Cryptography.RSAPKCS1KeyExchangeDeformatter␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityCryptographyRSAPKCS1KeyExchangeFormatter␍ClassTopic.asp">System.Security.Cryptography.RSAPKCS1KeyExchangeFormatter␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityCryptographyRSAPKCS1SignatureDeformatter␍ClassTopic.asp">System.Security.Cryptography.RSAPKCS1SignatureDeformatter␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityCryptographyRSAPKCS1SignatureFormatter␍ClassTopic.asp">System.Security.Cryptography.RSAPKCS1SignatureFormatter␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityCryptographySHA1Managed␍ClassTopic.asp">System.Security.Cryptography.SHA1Managed␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityCryptographySHA384Managed␍ClassTopic.asp">System.Security.Cryptography.SHA384Managed␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityCryptographySHA512Managed␍ClassTopic.asp">System.Security.Cryptography.SHA512Managed␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityCryptographyTripleDES␍ClassTopic.asp">System.Security.Cryptography.TripleDES␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityCryptographyTripleDESCryptoServiceProvider␍ClassTopic.asp">System.Security.Cryptography.TripleDESCryptoServiceProvider␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityCryptographyX509CertificatesX509Certificate␍ClassTopic.asp">System.Security.Cryptography.X509Certificates.X509Certificate␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityNamedPermissionSet␍ClassTopic.asp">System.Security.NamedPermissionSet␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPermissionsEnvironmentPermission␍ClassTopic.asp">System.Security.Permissions.EnvironmentPermission␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPermissionsFileDialogPermission␍ClassTopic.asp">System.Security.Permissions.FileDialogPermission␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPermissionsFileDialogPermissionAccess␍ClassTopic.asp">System.Security.Permissions.FileDialogPermissionAccess␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPermissionsIsolatedStorageFilePermission␍ClassTopic.asp">System.Security.Permissions.IsolatedStorageFilePermission␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPermissionsIsolatedStoragePermissionAttribute␍ClassTopic.asp">System.Security.Permissions.IsolatedStoragePermissionAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPermissionsPrincipalPermission␍ClassTopic.asp">System.Security.Permissions.PrincipalPermission␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPermissionsPrincipalPermissionAttribute␍ClassTopic.asp">System.Security.Permissions.PrincipalPermissionAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPermissionsPublisherIdentityPermission␍ClassTopic.asp">System.Security.Permissions.PublisherIdentityPermission␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPermissionsPublisherIdentityPermissionAttribute␍ClassTopic.asp">System.Security.Permissions.PublisherIdentityPermissionAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPermissionsReflectionPermission␍ClassTopic.asp">System.Security.Permissions.ReflectionPermission␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPermissionsRegistryPermission␍ClassTopic.asp">System.Security.Permissions.RegistryPermission␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPermissionsSecurityPermission␍ClassTopic.asp">System.Security.Permissions.SecurityPermission␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPermissionsSecurityPermissionAttribute␍ClassTopic.asp">System.Security.Permissions.SecurityPermissionAttribute␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPermissionsSiteIdentityPermission␍ClassTopic.asp">System.Security.Permissions.SiteIdentityPermission␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPermissionsStrongNameIdentityPermission␍ClassTopic.asp">System.Security.Permissions.StrongNameIdentityPermission␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPermissionsStrongNamePublicKeyBlob␍ClassTopic.asp">System.Security.Permissions.StrongNamePublicKeyBlob␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPermissionsUIPermission␍ClassTopic.asp">System.Security.Permissions.UIPermission␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPermissionsUrlIdentityPermission␍ClassTopic.asp">System.Security.Permissions.UrlIdentityPermission␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPermissionsZoneIdentityPermission␍ClassTopic.asp">System.Security.Permissions.ZoneIdentityPermission␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPolicyAllMembershipCondition␍ClassTopic.asp">System.Security.Policy.AllMembershipCondition␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPolicyApplicationDirectory␍ClassTopic.asp">System.Security.Policy.ApplicationDirectory␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPolicyApplicationDirectoryMembershipCondition␍ClassTopic.asp">System.Security.Policy.ApplicationDirectoryMembershipCondition␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPolicyFileCodeGroup␍ClassTopic.asp">System.Security.Policy.FileCodeGroup␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPolicyFirstMatchCodeGroup␍ClassTopic.asp">System.Security.Policy.FirstMatchCodeGroup␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPolicyHash␍ClassTopic.asp">System.Security.Policy.Hash␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPolicyHashMembershipCondition␍ClassTopic.asp">System.Security.Policy.HashMembershipCondition␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPolicyNetCodeGroup␍ClassTopic.asp">System.Security.Policy.NetCodeGroup␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPolicyPermissionRequestEvidence␍ClassTopic.asp">System.Security.Policy.PermissionRequestEvidence␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPolicyPolicyStatement␍ClassTopic.asp">System.Security.Policy.PolicyStatement␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPolicyPublisher␍ClassTopic.asp">System.Security.Policy.Publisher␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPolicyPublisherMembershipCondition␍ClassTopic.asp">System.Security.Policy.PublisherMembershipCondition␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPolicySite␍ClassTopic.asp">System.Security.Policy.Site␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPolicySiteMembershipCondition␍ClassTopic.asp">System.Security.Policy.SiteMembershipCondition␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPolicyStrongName␍ClassTopic.asp">System.Security.Policy.StrongName␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPolicyStrongNameMembershipCondition␍ClassTopic.asp">System.Security.Policy.StrongNameMembershipCondition␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPolicyUnionCodeGroup␍ClassTopic.asp">System.Security.Policy.UnionCodeGroup␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPolicyUrl␍ClassTopic.asp">System.Security.Policy.Url␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPolicyUrlMembershipCondition␍ClassTopic.asp">System.Security.Policy.UrlMembershipCondition␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPolicyZone␍ClassTopic.asp">System.Security.Policy.Zone␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPolicyZoneMembershipCondition␍ClassTopic.asp">System.Security.Policy.ZoneMembershipCondition␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPrincipalWindowsIdentity␍ClassTopic.asp">System.Security.Principal.WindowsIdentity␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPrincipalWindowsImpersonationContext␍ClassTopic.asp">System.Security.Principal.WindowsImpersonationContext␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemSecurityPrincipalWindowsPrincipal␍ClassTopic.asp">System.Security.Principal.WindowsPrincipal␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemThreadingCompressedStack␍ClassTopic.asp">System.Threading.CompressedStack␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemThreadingIOCompletionCallback␍ClassTopic.asp">System.Threading.IOCompletionCallback␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemThreadingThreadStart␍ClassTopic.asp">System.Threading.ThreadStart␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemThreadingTimerCallback␍ClassTopic.asp">System.Threading.TimerCallback␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemThreadingWaitCallback␍ClassTopic.asp">System.Threading.WaitCallback␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemThreadingWaitOrTimerCallback␍ClassTopic.asp">System.Threading.WaitOrTimerCallback␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemTimeZone␍ClassTopic.asp">System.TimeZone␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemTypedReference␍ClassTopic.asp">System.TypedReference␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemUnhandledExceptionEventHandler␍ClassTopic.asp">System.UnhandledExceptionEventHandler␍</a><br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemWeakReference␍ClassTopic.asp">System.WeakReference␍</a><br>
-22
View File
@@ -1,22 +0,0 @@
* Status of the various pieces of the class library
You can browse the status of the class library and see who has
registered to work on what parts of the system. These list
work-in-progress components currently.
Browse the current <a href="class-status/index.html">status</a>.
You can also download the XML <a
href="class-status/maintainers.xml">maintainers</a> file that
contains the actual maintainers list.
You can also download the master <a
href="class-status/class.xml">Class Status XML</a> file.
* List of not-implemented classes
These classes are only classes pending from the CORLIB assembly
other assemblies are not yet listed. We are going to be working
on an improved status display for pending classes.
Please bear with us in the meantime.
-105
View File
@@ -1,105 +0,0 @@
* Class Library Documentation
** Summary
<em>
[This documentation is in progress. Comments to
<a href="mailto:[email protected]">[email protected]</a>.]
</em>
While using inline XML tags to document classes is certainly
convenient, properly verbose documentation quickly overwhelms
the code, making the source quite difficult to read. Furthermore,
multilingual documentation makes for significant additional text.
With these considerations in mind, Mono will use external XML files
for type documentation, rather than documenting the source inline.
Several tools will be created for managing, verifying, generating,
and updating class library documentation, including:
<ul>
<li><a href="#docstub">docstub</a></li>
<li><a href="#docverify">docverify</a></li>
<li><a href="#docconv">docconv</a></li>
<li><a href="#docgen">docgen</a></li>
<li><a href="#monodoc">monodoc</a></li>
</ul>
** XML Documentation Files and Formats
*** Monodoc XML
This XML is similar to the XML documentation described in the
C# standard, with added tags for internationalization and a
slightly different structure. Documentation and a DTD/Schema
for Monodoc XML is forthcoming.
Monodoc XML does not contain any definitive type information,
and is only useful in conjunction with the Type definition for
whatever is being documented.
This XML could be generated by hand, by monostub, or by monodoc.
*** Assembly XML
This XML is generated by combining runtime type information for
an Assembly with a collection of Monodoc XML files. The resultant
XML (in the best of cases) contains both complete type and
documentary information for each type in the assembly.
This XML contains enough information to be transformed into
user-accessible documentation. It is likely that scripts
will be created to generate reference docs as HTML and other
formats.
Documentation and a DTD/Schema for Assembly XML is forthcoming.
** Documentation Tools
*** <a name="docstub">docstub</a>
Given a type name and an assembly, generates stub Monodoc XML
documentation for the type. Optionally, docstub can attempt to
populate initial documentation from an XML file in the format
published along with the ECMA standard.
*** <a name="docverify">docverify</a>
Given a Monodoc XML file and an assembly, verifies that the
documentation matches the compiled type. Checks signatures,
parameters, et cetera.
*** <a name="docconv">docconv</a>
Converts from Monodoc XML to the standard C# compiler-emitted
XML format and vice versa.
*** <a name="docgen">docgen</a>
Given an assembly and a collection of Monodoc XML files, creates
an Assembly XML file containing all documentation and type information
available. This output is suitable for transforming into user
documentation.
*** <a name="monodoc">monodoc</a>
A GUI tool for documentation and translation, this encapsulates
the capabilities of docstub, docverify, docconv, and docgen in
a friendly user interface. In addition, monodoc provides features
to ease translation, such as side-by-side editing and coverage
statistics.
** Status and Roadmap
*** 2 January 2002
As I write the initial version of this document, very little has been
implemented. Currently, there is a:
<ul>
<li>Preliminary version of the Monodoc XML format</li>
<li>Preliminary version of the docstub utility</li>
</ul>
Here's hoping for frequent, productive updates.
** Get Involved
Help us define Mono's documentation structure! Subscribe to
<a href="http://lists.ximian.com/mailman/listinfo/mono-docs-list">mono-docs-list</a>
and wade right in.
+3
View File
@@ -1,5 +1,8 @@
* Contacting the Mono team.
You can contact the Mono Team by sending e-mail to `<a
href="mailto:[email protected]">mailto:[email protected]</a>'.
You can contact the general forum of discussion by sending
e-mail to <a href="mailto:[email protected]">[email protected]</a>
+7 -45
View File
@@ -10,7 +10,7 @@
href="tools.html">the tools</a>, the <a
href="testing.html">testing framework</a>
* <b>Writers:</b> You can help us bywriting <a
* <b>Writers:</b> You can help us with writing <a
href="documentation.html">documentation</a>.
</ul>
@@ -18,57 +18,19 @@
something that would help tremendously would be to help with
small duties in the project that need to be addressed.
** To start contributing
To start developing classes or to contribute to the compiler,
you only need Windows and the .NET Framework 1.0 SDK. Please notice
that you do not need Visual Studio (although you can use it if
you want).
You can get it <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>
** Bug reporting
If you find bugs in Mono, please make sure you enter a bug
report so we can keep track of problems in Mono.
To enter bug reports go to <a href="http://bugzilla.ximian.com">
http://bugzilla.ximian.com</a> and enter bug reports against
your favorite component (Mono, Runtime, C# compiler).
** Small tasks
A few smaller tasks are here, dropped in no particular order:
<ul>
* <b>MCS compilation process:</b> Currently MCS does
not build with a single `make' command. This should
be fixed (this being part of the `Joel Test' that
software has to pass).
* <b>Mono/doc and web site:</b> They need to be
packaged up in the official `distribution'
* Adding serialization support to all the classes.
We have many classes, but we have not implemented in
many cases the serialization and re-incarnation support in
them (this is pretty straight forward code, and simple,
but there is a lot to be done here).
</ul>
* Emacs support
Brad Merryl's C# mode for Emacs is available: <a
href="http://www.cybercom.net/~zbrad/DotNet/Emacs/">http://www.cybercom.net/~zbrad/DotNet/Emacs/</a>
* Books on C# and DotNet.
<ul>
* Dotnet Books (<a href="http://www.dotnetbooks.com">http://www.dotnetbooks.com</a>)
* Dotnet Resources (<a href="http://www.dotnetexperts.com/resources/">
http://www.dotnetexperts.com/resources</a>)
* O'Reilly C# Essentials (<a href="http://www.oreilly.com/catalog/csharpess/">
http://www.oreally.com/catalog/csharpess</a>)
* O'Really .NET Essentials (<a href="http://www.oreilly.com/catalog/dotnetfrmess/">
http://www.oreally.com/catalog/dotnetfrmess</a>)
* <b>Enthusiasts: </b>
</ul>
* Special note
-190
View File
@@ -1,190 +0,0 @@
* Developer FAQ
** New classes
Q: Should we write classes which are not part of the .NET or ECMA specs?
A: Yes. The ECMA and .NET specifications are far from complete, and
to produce a complete platform we will need a number of other
classes and components.
Any new classes that are not part of .NET or ECMA should be
designed to be reusable on anyone's CLI implementation. So that
Windows developers can also use any new classes that we come up
with.
We have a few existing <a href="ideas.html">Ideas on missing
classes</a>
** Language Compatibility
Q: What is the magic that allow multiple languages to co-exist?
A: From Fergus Henderson:
<i><blockquote>
There are different levels of interoperability.
The ECMA spec defines different categories of
CLS (Common Language Specification) conformance.
There are also some useful categories that don't
correspond to any of the levels defined in the ECMA spec.
In increasing degree of difficulty, your language implementation
can
<ul>
* (a) just generate IL
* (b) be a CLS "consumer", which means that it can read in
meta-data describing component interfaces,
and that it provides a way to declare variables of
CLS-complaint types and to call CLS-complaint methods.
* (c) be a CLS "extender", which means that it can in addition
derive from CLS-compliant classes
and implement CLS-compliant interfaces
* (d) be able to produce components with *any* CLS-compliant
component interface.
</ul>
Supporting some of these may require extending your language. However,
you can get quite a lot of interoperability by just putting appropriate
functionality in your compiler, without extending your language.
For some things, e.g. ASP.NET, your language implementation also needs to be
able to
<ul>
* (e) consume CodeDom trees. CodeDom trees are an abstract
representation of programs in a form similar to a C# parse
tree, with embedded code snippets (unparsed strings).
Given a CodeDom tree, with the snippets in your language,
your language implementation needs to generate a (i) .NET
assembly and possibly also (ii) a source file in your language.
* (f) produce CodeDom trees. For some applications,
your language implementation also needs to be able to
round-trip from CodeDom -> your language -> CodeDom.
</ul>
and for some things it needs to
<ul>
* (g) generate *verifiable* IL
</ul>
So when you hear all the hype about how language XYZ is a
".NET language", make sure you ask which of these different
things are supported.
[For the record, Mercury currently supports (a). We're working on
(b) and (g), and on parts of (c) and (e). We're never going to do (f), I very
strongly doubt we'll ever do (d), and for (c) we might only ever support
implementing interfaces, not deriving from classes.]
</blockquote></i>
** PInvoke
Q: What are the two major initiatives to implement PInvoke?
A: Fergus Henderson answers:
<i><blockquote>
Many of the .NET APIs will need to be implemented using code that calls C/Unix
APIs, such as stat(). The standard way of interfacing with native code from
.NET code is to use "PInvoke". However, there is a difficulty: many of
these APIs are defined in terms of types such as C's `long' or `size_t'
or the Posix `struct stat' whose representation varies depending on the
platform (architecture/OS/C compiler). There's no *portable* way of
accessing those from .NET managed code.
So, there are a couple of different approaches.
One possibility is to access such routines by writing a wrapper, e.g. in C,
that provides the same functionality without using types with a system-dependent
representation. The wrapper can then be directly accessed from portable
.NET code. The .NET code remains both source- and binary-portable;
the wrapper code is source-portable, but needs to be compiled
seperately for each target platform. The drawback of this approach is
that you have to write a lot of cumbersome wrapper code.
Another possibility is to extend the .NET VM with support for an
additional custom attribute, e.g. "[PosixType]". The VM would then
represent types tagged with this attribute in the same way that the
underlying system represents those types. With this approach, no
wrapper code would be needed. A drawback of this approach is that it
pushes quite a bit of complexity into the VM; the VM would have to know
the native representation of all types annotated with this attribute.
Another drawback is that code using this extension might not work on
different VMs.
There have also been some other suggestions, but those are the two that
I think are the best.
</blockquote></i>
Q: What is the problem implementing PInvoke?
A: Again, from Fergus Henderson:
<i><blockquote>
There's no problem implementing PInvoke as specified in the ECMA
specs and/or MS documentation. It's just that PInvoke by itself
doesn't solve all of the problems; in particular it doesn't solve
the problem of C types whose representation is different on different
systems.
</blockquote></i>
** CVS use
Q: Why do we keep ChangeLogs and make the CVS commit messages be the
same? One could be generated from the other
A: There are a number of reasons for keeping ChangeLog files as well as
CVS commit files:
<ul>
* Offline programming: when people are traveling, CVS logs are
not available.
* Slow CVS access: Many people work over modem lines (very
typical for contributors in Europe, Asia, Latin America)
using CVS is slow and might not be available to you (cvs
server down, no anoncvs server available).
* ChangeLogs travel in a released tarball package, so it is
possible to study the rationale of changes even after a
project is long "released", or you only have the sources for
the code.
* ChangeLog are not metadata for each file, they are live
files that you can browse in the package that is being
distributed.
</ul>
Making the CVS commit message be the same as the ChangeLog has other
benefits:
<ul>
* You can track down with `cvs log' what things were changed,
and match those to meaningful reports on the intentions of
the commit.
* When reading the commits-list, you can get a glimpse of the
changes without having to diff out or cvs update your tree.
* You can read off-line the changes that are being made
(asyncrouns operation).
</ul>
This mechanism works very well for GNOME and other projects.
Q: Should I use any of the special RCS keywords like $Id: devel-faq,v 1.1 2001/07/31 21:13:05 miguel Exp $, $Author: miguel $,
$Date: 2001/07/31 21:13:05 $, or $Revision: 1.1 $?
A: Please avoid using those in the source code in the CVS. They
are not really useful, and they cause a lot of conflicts when
people have separate CVS trees.
It was a nightmare with the Linux kernel when two people had their
private CVS trees and were submitting patches to the core.
+17 -2
View File
@@ -31,5 +31,20 @@
** Class Library documentation
We are moving to a new setup for documenting the class libraries,
you can read about it <a href="classlib-doc.html">here</a>
When contributing to the Class Library effort, please use the
inline XML documentation tags to document your classes so we
can automatically generate the documentation from the class
libraries.
If you provide examples, please do not embed them into the
source code, as that will make the source code harder to read
and maintain. Instead, put examples for your code into a
subdirectory of the class libraries. Make your sample
code a full standalone application that people can compile.
Ideally the Mono documentation browser will let you edit, modify
and run the sample programs.
+11 -231
View File
@@ -10,245 +10,19 @@
test suite and the class library are in the `mcs' package, we
will move this later into `mono' itself.
In order to make mcs and the class libraries you will need the
GNU make tools. These may be obtained for the Windows
environment from <a href="http://www.cygwin.com">cygwin.com</a>.
The mcs compiler requires the `jay' parser generator, this is
available in module `jay'.
You will also need to get GLIB and <a
href="http://www.freedesktop.org/software/pkgconfig">pkgconfig</a>.
You can get Glib 1.3 from: <a
href="ftp://ftp.gtk.org/pub/gtk/v1.3/glib-1.3.12.tar.gz">ftp://ftp.gtk.org/pub/gtk/v1.3/glib-1.3.12.tar.gz</a>.
<a name="sources">
** Sources
We provide both <a href="#packaged">packaged and tested</a>
tarballs (those are known to compile and pass `make
distcheck') as well as <a href="snapshots">daily snapshots</a> done
at 10pm Boston Time
<a name="snapshots">
*** Snapshots
The daily snapshots are available <a
href="http://www.go-mono.com/snapshots">here</a>. These
snapshots are done every day at 10pm EST (Boston Time).
They are not guaranteed to build, but most of the time they
should. They should give you a window to see what we are up to.
You might also want to track our development using the <a
href="http://lists.ximian.com/mailman/listinfo/mono-cvs-list">mono-cvs-list</a>
mailing list.
<a name="packaged">
At this point, you should look into using one of the <a
href="snapshots">nightly snapshots</a> or getting the
sources from <a href="anoncvs.html">Anonymous CVS</a>
as significant work has gone into Mono since our last stable
release in September.
We will be making a packaged release sometime in January.
<a name="install">
** Installing the software
To install and work on the compiler and the class libraries,
follow these instructions:
Currently we will be providing CVS snapshots every day, until
we make the first tarball release.
<ul>
* Install <a href="http://www.cygwin.com">CygWin</a> first.
* Untar the MCS distribution (see below for information).
* Go into the MCS directory and type `make windows'
</ul>
To compile the mono runtime on windows:
<ul>
* Install <a href="http://www.cygwin.com">CygWin</a> first.
* Install in /usr/local in your Cygwin world the following
packages (compiled by <a href="mailto:[email protected]">Alex Graveley</a>):
<ul>
<li><a href="http://primates.ximian.com/~alex/glib-1.3.12-win32-native.zip">
http://primates.ximian.com/~alex/glib-1.3.12-win32-native.zip</a>
<li><a href="http://primates.ximian.com/~alex/pkg-config-0.8-cygwin.zip">
http://primates.ximian.com/~alex/pkg-config-0.8-cygwin.zip</a>
</ul>
These already contain libiconv linked statically.
</ul>
If you want to compile things yourself you will need to compile and install:
<ul>
* Install <a href="http://www.freedesktop.org/software/pkgconfig">pkgconfig</a>.
(I had to change line 674 of
<nobr><tt>pkgconfig-0.8.0/glib-1.2.8/gstrfuncs.c</tt></nobr> from
<nobr><tt>extern char *strsignal (int sig);</tt></nobr> to
<nobr><tt>extern const char *strsignal (int sig);</tt></nobr>.
<pre>
tar xzvf pkgconfig-0.8.0.tar.gz
cd pkgconfig-0.8.0
./configure --prefix=/usr
make
make install
</pre>
* Install <a href="ftp://ftp.gnu.org/pub/gnu/libiconv/libiconv-1.7.tar.gz">libiconv</a>.
If you dont have MS Visual C/C++ 4.0 or 5.0 or 6.0 you can also try
the binary package available at <a
href="http://www.gimp.org/win32/libiconv-dev-20001007.zip">here</a>.
* Install the newest glib (1.3 version). You can download it
from <a href="ftp://ftp.gtk.org/pub/gtk/v1.3/glib-1.3.12.tar.gz">here</a>.
* Unpack the mono distribution:
<pre>
tar xzvf mono-XXX.tar.gz
</pre>
* Configure, compile and install:
For official releases, use:
<pre>
./configure --prefix=//c/mono
make
make install
</pre>
For Snapshots, or CVS trees, use:
<pre>
./autogen.sh --prefix=//c/mono
make
make install
</pre>
* Some people observed problems with autoconf 2.52. Installing
autoconf 2.13 helped in those cases (don't forget to do a
`make maintainer-clean' after the update)
</ul>
To compile the mono runtime on Unix:
<ul>
* Install <a href="http://www.freedesktop.org/software/pkgconfig">pkgconfig</a>.
* Install newest glib (cvs head version). You can download it
from <a href="ftp://ftp.gtk.org/pub/gtk/v1.3/glib-1.3.12.tar.gz">here</a>. Maybe you need
to modify your ACLOCAL_FLAGS for pkgconfig, for example if
your install prefix is /usr/local:
<pre>
export ACLOCAL_FLAGS="-I /usr/local/share/aclocal"
</pre>
* Download the mono distribution
* Unpack the mono distribution:
<pre>
tar xzvf mono-XXX.tar.gz
</pre>
* Configure, compile and install:
For official releases:
<pre>
./configure
make
make install
</pre>
For snapshots and CVS trees:
<pre>
./autogen.sh
make
make install
</pre>
</ul>
<a name="oldreleases">
*** Old releases.
<ul>
<a name="sep-18">
<b>September 18, 2001</b>
<ul>
* <a href="archive/mono-0.7.tar.gz">mono-0.7.tar.gz</a>: Mono Runtime 0.7 release.
* <a href="archive/mcs-0.7.tar.gz">mcs-0.7.tar.gz</a>: Mono Compiler and Classes 0.7 release.
* <a href="archive/mono-0.7">Release Notes.</a>
</ul>
<a name="august-22">
<b>August 22, 2001</b>
<ul>
* <a href="archive/mono-0.6.tar.gz">mono-0.6.tar.gz</a>: Mono Runtime 0.6 release.
* <a href="archive/mono-compiler-classes-0.6.tar.gz">mono-compiler-classes-0.6.tar.gz</a>: Mono Compiler and Classes 0.6 release.
* <a href="archive/mono-0.6">Release Notes.</a>
</ul>
<a name="july-29">
<b>July 29, 2001</b>
<ul>
* <a href="archive/mono-0.5.tar.gz">mono-0.5.tar.gz</a>: Mono Runtime 0.5 release.
* <a href="archive/mono-0.5">Release Notes.</a>
</ul>
<a name="july-22">
<b>July 22, 2001</b>
<ul>
* <a href="archive/mcs-22-Jul-2001.tar.gz">mcs-22-Jul-2001.tar.gz</a>: CVS snapshot.
* <a href="archive/mcs-Jul-22-Jul-19-2001.tar.gz">Differences since 19</a>: CVS snapshot.
* <a href="archive/mcs-22">Release Notes.</a>
</ul>
<a name="july-19">
<b>July 19th, 2001</b>
<ul>
* <a href="archive/mcs-19-Jul-2001.tar.gz">mcs-19-Jul-2001.tar.gz</a>: CVS snapshot.
* <a href="archive/mcs-Jul-17-Jul-19-2001.tar.gz">Differences since 17</a>: CVS snapshot.
* <a href="archive/mcs-19">Release Notes.</a>
</ul>
<a name="july-17">
<b>July 17th, 2001</b>
<ul>
* <a href="archive/mcs-17-Jul-2001.tar.gz">mcs-17-Jul-2001.tar.gz</a>: CVS snapshot.
* <a href="archive/mcs-Jul-15-Jul-17-2001.tar.gz">Differences since 15</a>: CVS snapshot.
* <a href="archive/mcs-17">Release Notes.</a>
</ul>
<a name="july-15">
<b>July 15th, 2001</b>
<ul>
* <a href="archive/mcs-15-Jul-2001.tar.gz">mcs-15-Jul-2001.tar.gz</a>: CVS snapshot.
* <a href="archive/mono-0.4.tar.gz">mono-0.4.tar.gz</a>: Packaged Source Code.
* <a href="archive/mono-0.4">Release Notes.</a>
</ul>
<a name="july-14">
<b>July 14th, 2001</b>
<ul>
* <a href="archive/jay.cs.tar.gz">archive/jay.cs.tar.gz</a>: Sources to Jay.
* <a href="archive/mcs-12-Jul-2001.tar.gz">mcs-12-Jul-2001.tar.gz</a>: CVS snapshot.
* <a href="archive/mono-0.3.tar.gz">mono-0.3.tar.gz</a>: Packaged Source Code.
</ul>
@@ -257,8 +31,14 @@ make install
<b>July 8th, 2001</b>
<ul>
* <a href="archive/jay.cs.tar.gz">archive/jay.cs.tar.gz</a>: Sources.
* <a href="archive/mcs-08-Jul-2001.tar.gz">mcs-08-Jul-2001.tar.gz</a>: CVS Snapshot
* <a href="archive/mono-08-Jul-2001.tar.gz">mono-08-Jul-2001.tar.gz</a>: CVS Snapshot
</ul>
</ul>
** CVS
We are trying to figure out where to put our CVS repository.
We are debating between the GNOME CVS or SourceForge. Watch
this spot.
+335 -389
View File
@@ -1,42 +1,18 @@
<a href="#basics">Basics</a><br>
<a href="#ximian">The Ximian Role in the Mono project</a><br>
<a href="#gnome">Mono and GNOME</a><br>
<a href="#gui">Building GUI applications with Mono</a><br>
<a href="#msft">Mono and Microsoft</a><br>
<a href="#pnpproject">Mono and the Portable.NET Project</a><br>
<a href="#webservices">Web Services</a><br>
<a href="#devel">Development Tools and Issues</a><br>
<a href="#java">Mono and Java</a><br>
<a href="#extending">Extending Mono</a><br>
<a href="#portability">Portability</a><br>
<a href="#reuse">Reusing Existing Code</a><br>
<a href="#gcc">Mono and GCC</a><br>
<a href="#performance">Performance</a><br>
<a href="#licensing">Licensing</a><br>
<a href="#etc">Miscellaneous Questions</a><br>
<a name="basics"></a>
** Basics
Q: What is Mono exactly?
Q: Is Mono the same as Microsoft's .NET initiative?
A: The Mono Project is an open development initiative sponsored by
Ximian that is working to develop an open source, Linux-based
version of the Microsoft .NET development platform. Its objective
is to enable Linux developers to build and
deploy cross-platform .NET Applications. The project will
implement various technologies developed by Microsoft that have now
been submitted to the ECMA for standardization.
A: It is not.
Q: What is the difference between Mono and the .NET Initiative?
.NET is a company-wide initiative at Microsoft that
encompasses many different areas. The .NET development framework,
Passport, Biztalk, new server products, and anything that is
remotely connected to .NET gets the ".NET-stamping" treatment.
Some components of Microsoft's .NET initiative have been announced
and some others are in the works.
A: The ".NET Initiative" is a somewhat nebulous company-wide effort by
Microsoft, one part of which is a cross-platform development
framework. Mono is an implementation of the development framework,
but not an implementation of anything else related to the .NET
Initiative, such as Passport, software-as-a-service, or
corporate rebranding.
Mono is a project to implement several technologies developed by
Microsoft that have now been submitted to the ECMA Standards Body.
Q: What technologies are included in Mono?
@@ -54,18 +30,20 @@ A: Mono contains a number of components useful for building new
* A compiler for the C# language. In the future we
might work on other compilers that target the Common
Language Runtime.
Windows has compilers that target the
virtual machine from
<a href="http://msdn.microsoft.com/net/thirdparty/default.asp#lang">a
number of languages:</a> Managed C++, Java Script,
Eiffel, Component Pascal, APL, Cobol, Oberon, Perl,
Python, Scheme, Smalltalk, Standard ML, Haskell,
Mercury and Oberon.
</ul>
Windows has compilers that target the virtual machine from <a
href="http://msdn.microsoft.com/net/thirdparty/default.asp#lang">a
number of languages:</a> Managed C++, Java Script, Eiffel,
Component Pascal, APL, Cobol, Oberon, Perl, Python, Scheme,
Smalltalk, Standard ML, Haskell, Mercury and Oberon.
The CLR and the Common Type System (CTS) enables applications and
libraries to be written in a collection of different languages that
target the byte code
libraries to be written in a number of languages. Classes and
methods created in one language can be used from a different
language.
This means for example that if you define a class to do algebraic
manipulation in C#, that class can be reused from any other
@@ -87,58 +65,45 @@ Q: Will you implement the .NET Framework SDK class libraries?
A: Yes, we will be implementing the APIs of the .NET Framework SDK
class libraries.
Q: Will you offer an ECMA-compliant set of class libraries?
Q: What does Mono stand for?
A: Eventually we will. Our current focus is on interoperating
with the Microsoft SDK, but we will also offer an ECMA compliant
set of libraries.
Q: What does the name "Mono" mean?
A: Mono is the word for `monkey' in Spanish. We like monkeys.
Q: Is Mono usable?
A: The JIT engine is usable on Intel x86 machines. An interpreter
can be used on other non-Intel x86 machines.
The class libraries are not yet mature enough to run real applications,
but if you are interested in trying out Mono, you can definetly start
testing things out as many programs run.
The C# compiler has made significant progress, it can even compile
itself now, but it can not yet be ran with our class libraries as
they are missing some features.
A: Mono is the word for `Monkey' in Spanish. We like monkeys.
Q: When will you ship it?
A: It is premature to target a shipdate for the code, but we
anticipate that it will be available some time in the middle of
2002.
A: We do not know when the code will be shipped. The more
contributions we get to the project, the sooner it will ship.
A rough estimate is that we might be able to run our C# compiler on
Linux by the end of the year. That means running the Windows
Executable generated by a Microsoft .NET compiler on the Linux
platform.
We expect that doing GUI applications will require more work on the
class libraries. That could take another six months.
Q: How can I contribute?
A: Check the <a href="contributing.html">contributing</a> section.
Q: Aren't you just copying someone else's work?
Q: You guys should innovate instead of copying.
A: We are interested in providing the best tools for programmers to
develop applications for Free Operating Systems. We also want to help
provide the interoperability that will allow those systems to fit in
with other standards.
A: In this particular case, we see a clear advantage in the platform
and we are interested in using the features of the CLI on open source systems.
For more background, read the <a href="http://www.go-mono.com/rationale.html">Mono
Project white paper</a>.
the project.
We have decided that we should spend our limited resources towards
implementing an existing specification instead of designing and
implementing our own.
Designing and implementing our own would be possible, but it doesn't make
sense to do that just because the specification comes from a
proprietary vendor.
<a name="ximian"></a>
** The Ximian Role in the Mono Project
** Ximian
Q: Why is Ximian working on .NET?
A: Ximian is interested in providing the best tools for programmers to
A: We are interested in providing the best tools for programmers to
develop applications for Free Operating Systems.
For more information, read the project <a
@@ -146,150 +111,83 @@ A: Ximian is interested in providing the best tools for programmers to
Q: Will Ximian be able to take on a project of this size?
A: Of course not. Ximian a supporter of the Mono project, but the only way
to implement something of this size is for the entire free software
community to get involved. Visit the <a href="contributing.html">contributing</a>
page if you'd like to help out.
A: Ximian will not be able to taken on the whole project on its own.
Mono will be a free software/open source community project, that is
the only way we can hope to implement something of this size. You
can <a href="contributing.html">contribute</a> to this effort.
Q: What pieces will Ximian be working on?
A: We will devote most of our resources to work on the pieces which are
on the critical path to release a development and execution
environment. Once the project is at a stage where it is useful in
the real world, it will achieve a critical mass of developers to
improve it further.
A: We will focus on building a development and execution
environment.
Q: Will Ximian offer Mono commercially?
The idea is to get Mono to a state of that would allow
third parties to actually be able to use it real-world development.
A: When Mono is ready to be shipped Ximian will offer a commercial
support and services for Mono.
Q: Why does Ximian even care?
Q: Will you wait until Mono is finished?
A: We like the features that the CLI and its related technologies
bring to the table. An exciting addition to the developer toolkit.
The goal of Mono is to bring this technology to non-Windows
platforms (although we hope Mono will also run on Windows, for
debugging and comparative purposes).
A: Mono will ship on various stages as they mature. Some people
require only a subset of the technologies, those will ship first.
More advanced features will take more time to develop. A support
timeline will be available in June 2002.
** Licensing
<a name="gnome"></a>
** Mono and GNOME
Q: Will I be able to write proprietary applications that run with
Mono?
Q: How is Mono related to GNOME?
A: Yes. We will make sure that the licensing will allow developers to
create proprietary applications.
Q: What license is Mono on?
A: In a number of ways. This project was born out of the need of
providing improved tools for the GNOME community, and will use
existing components that have been developed for GNOME when they
are available. For example, we plan to use Gtk+ and Libart to
implement Winforms and the Drawing2D API and are considering
GObject support.
A: The C# Compiler is released under the terms of the GPL. The class
libraries will be under the LGPL or the GPL with a special
exception. The runtime libraries are under the LGPL.
Q: Has the GNOME Foundation or the GNOME team adopted Mono?
Here is the exception for the class libraries:
A: Mono is too new to be adopted by those groups. We hope that the
tools that we will provide will be adopted by free software
programmers including the GNOME Foundation members and the GNOME
project generally.
The library is distributed under the terms of the GNU General
Public License with the following exception:
Q: Should GNOME programmers switch over to Mono now?
If you link this library against your own program, then you do not
need to release the source code for that program. However, any
changes that you make to the library itself, or to any native
methods upon which the library relies, must be re-distributed in
accordance with the terms of the GPL.
A: It is still far to early for discussions of "switching over." No
pieces of Mono will be ready within the next six months, and a
complete implementation is roughly one year away.
This is similar in spirit to <a
href="http://www.gnu.org/software/classpath/classpath.html">GNU
Classpath.</a>
We encourage GNOME developers to continue using the existing tools,
libraries and components. Improvements made to GNOME will have an
impact on Mono, as they would be the "backend" for various classes.
Q: Will you accept code under the XXX License?
Q: Will Mono include compatibility with Bonobo components? What is the
relationship between Mono and Bonobo?
A: If the XXX License is compatible with the license we use in that
specific piece of code, then yes. If you want to use the BSD license, make
sure you use the BSD license without the advertisement clause (The
`Ousterhout License').
A: Yes, we will provide a set of classes for implementing and using
Bonobo components from within Mono. Mono should allow you to write
Bonobo components more easily, just like .NET on Windows allows you
to export .NET components to COM.
** Mono and .NET
Q: Does Mono depend on GNOME?
A: No, Mono does not depend on GNOME. We use a few packages produced by
the GNOME team like the `glib' library.
Q: But will I be able to build GNOME applications?
A: Yes, we will enable people to write GNOME applications using Mono.
<a name="gui"></a>
** GUI applications
Q: Will Mono enable GUI applications to be authored?
A: Yes, you will be able to build GUI applications. Indeed, that is our
main focus. We will provide both the Windows.Forms API and the Gtk# AP(I.
Q: What is the difference between Gtk# and System.Windows.Forms?
A: Gtk# is a set of bindings for the Gtk+ toolkit for C# (and other
CIL-enabled languages). System.Windows.Forms is an API defined
by Microsoft to build GUI applications.
Q: Will I be able to run my smart clients on systems powered by Mono?
A: As long as your applications are 100% .NET and do not make use
of P/Invoke to call Win32 functions, your smart client applications
will run on Mono platforms.
<a name="msft"></a>
** Mono and Microsoft
Q: Is Microsoft helping Ximian with this project?
A: No. Ximian CTO Miguel de Icaza had a friendly conversation with
Microsoft software architect David Stutz, but that's about the
extent of the contact. Microsoft is interested in other
implementations of .NET and are willing to help make the ECMA spec
more accurate for this purpose.
Ximian representatives have also spoken with Sam Ruby at the ECMA
TG3 committee to discuss the same issues.
Q: Is Microsoft or Corel paying Ximian to do this?
A: No.
Q: Do you fear that Microsoft will change the spec and render Mono
useless?
A: No. Microsoft proved with the CLI and the C# language that it was
possible to create a powerful foundation for many languages to
interoperate. We will always have that.
Even if changes happened in the platform which were undocumented,
the existing platform would a value on its own.
Q: Are you writing Mono from the ECMA specs?
A: Yes, we are writing them from the ECMA specs and the published
materials in print about .NET.
Q: If my applications use Mono, will I have to pay a service fee?
Q: If applications use Mono, does that mean that I have to pay a service fee?
A: No. Mono is not related to Microsoft's initiative of
software-as-a-service.
software-as-a-service.
Q: Is the Mono Project is related to the Microsoft Hailstorm effort? Is
Ximian endorsing Hailstorm?
Q: If you implement .NET, will I depend on Microsoft Passport to run my software?
A: No. The Mono Project is focused on providing a compatible set of
tools for the Microsoft .NET development platform. It does not
address, require, or otherwise endorse the MS Passport-based
Hailstorm single sign-on system that is part of Windows XP and
other services.
A: No. The .NET Framework is a runtime infrastructure and collection
of class libraries. Passport may be required to access certain web
services written for that framework, but only if the programmer
chooses Passport as the authentication mechanism.
Q: Will Mono or .NET applications depend on Microsoft Passport?
Q: Is .NET just a bunch of marketing slogans?
A: No. MS Passport is unrelated to running .NET compatible applications
produced with the Mono tools. The only thing you will need is a
just-in-time compiler (JIT).
A: Although the `.NET initiative' is still quite nebulous, The .NET Framework
has been available for some time. Mono is not an implementation of the .NET
initiative, just the development framework.
Q: What is a 100% .NET application?
@@ -298,83 +196,123 @@ A: A `100% .NET application' is one that only uses the APIs defined
applications would in theory run unmodified on Windows, Linux,
HP-UX, Solaris, MacOS X and others.
Q: If Microsoft will release a port of their .NET platform under the
`Shared Source' license, why should I bother with anything else?
Q: But Microsoft will release a port of the real thing under the
`Shared Source' license, why bother with anything else?
A: The Shared Source implementation will be expensive and its uses
will be tightly restricted, especially for commercial use. We are
working towards an implementation that will grant a number of
important rights to recipients: use for any purpose,
A: The Shared Source implementation will not be usable for commercial
purposes. We are working towards an implementation that will grant
a number of rights to recipients: use for any purpose,
redistribution, modification, and redistribution of modifications.
This is what we call <a
href="http://www.gnu.org/philosophy/free-sw.html">Free Software</a>
Q: Is Mono a free implementation of Passport?
** Passport
A: No. Mono is just a runtime, a compiler and a set of class
libraries.
Q: Is this a free implementation of Passport?
Q: Will the System.Web.Security.PassportIdentity class mean
A: No. Passport is part of Microsoft's Hailstorm initiative. Mono
is just a runtime, a compiler and a set of class libraries.
Q: Will the System.Web.Security.PassportIdentity class, mean
that my software will depend on Passport?
A: No. Applications may use that API to contact a Passport site, but
are not required to do so.
A: No. That just means that applications might use that API to
contact a Passport site.
As long as your application does not use Passport, you will not
need Passport.
Q: Will Mono running on Linux make Passport available for Linux?
It might even be possible to implement that class with
a set of dummy functions, or use an alternate Passport implementation.
A: No. However, the Passport toolkit for Linux-based web servers is
available from Microsoft.
We do not know at this time whether the Passport protocol is
documented and whether we will be able to talk to
passport.com
Q: What is your opinion?
A: You can read my personal <a href="passport.html">opinion on
passport</a>.
** Mono and Windows
Q: Will Mono allow me to run Microsoft Office on Linux?
A: No, it will not. Microsoft Office is a Windows application. To
learn more about running Windows applications on Intel Unix systems
refer to <a href="http://www.winehq.com">the Wine Project</a>.
run Windows applications on Intel Unix systems refer to <a
href="http://www.winehq.com">the Wine Project</a>
<a name="pnpproject"></a>
** Mono and Portable.NET
** GNOME
Q: What are the differences between Mono and Portable.NET?
Q: How is this related to GNOME?
A: Most of Mono is being written using C#, with only
a few parts written in C (The JIT engine, the runtime, the
interfaces to the garbage collection system). The Portable.NET
Project is using C for development.
A: In a number of ways:
* Mono will use existing
components that have been developed for GNOME when it makes
sense. For example on X systems, we will use Gtk+ and
Libart to implement Winforms and the Drawing2D API.
For database access, we will use LibGDA (not really
depending on GNOME, but related to).
* This project was born out of the need of providing improved
tools for the GNOME community.
* We would like to add support to our CLR implementation to
deal with GObjects (in GNOME 1.x, they are called
GtkObjects), and allow Mono developers to provide GObjects
or use and extend existing GObjects.
Q: Has the GNOME Foundation or the GNOME team adopted Mono?
A: Mono is too new to be adopted by those groups. We hope that the
tools that we will provide will be adopted by free software
programmers including the GNOME Foundation members and the GNOME
project generally.
Q: Should GNOME programmers switch over to Mono?
A: Mono will not be ready even within the next six months, and a
complete implementation is probably one year away.
We encourage GNOME developers to continue using the existing tools,
libraries and components. Improvements made to GNOME will have an
impact on Mono, as they will provide the "backend" for various
classes.
Q: Will Mono include compatibility with Bonobo components?
A: Yes, we will provide a set of classes for implementing and using
Bonobo components from within Mono.
** Mono and the Web
Q: Is Mono a way of running Java applets?
A: No.
<a name="webservices"></a>
** Web Services
Q: How is Mono related to Web Services?
Q: Is Mono just a new way of writing Web Services?
A: Mono is only related to Web Services in that it will implement the
same set of classes that have been authored in the .NET Framework
to simplify and streamline the process of building Web Services.
A: No.
But most importantly, Mono is an Open Source implementation of the
.NET Framework.
Q: Can I author Web Services with Mono?
A: You will be able to write Web Services on .NET that run on Mono and
viceversa.
Q: If Mono implements the SDK classes, will I be able to write and
execute .NET Web Services with it?
Q: If this implements the SDK classes, will I be able to write and
execute .NET Web Services with this?
A: Yes. When the project is finished, you will be able to use the
same technologies that are available through the .NET Framework SDK
on Windows to write Web Services.
A: Yes, you will.
Q: What about Soup? Can I use Soup without Mono?
When the project is finished, you will be able to use the same
technologies that are available through the .NET Framework SDK on
Windows to write Web Services.
A: Soup is a library for GNOME applications to create SOAP servers and
SOAP clients, and can be used without Mono. You can browse the
source code for soup using <a
href="http://cvs.gnome.org/bonsai">GNOME's Bonsai</a>.
Q: What about Soup?
A: Soup is a library for GNOME applications to create SOAP server and
SOAP clients. You can browse the source code for soup using <a
href="http://cvs.gnome.org/bonsai">GNOME's Bonsai</a>
Q: Can I use CORBA?
@@ -392,8 +330,7 @@ Q: Can I serialize my objects to other things other than XML?
A: Yes, although the serializing tools have not yet been planned, and
you would probably have to implement them yourself.
<a name="devel"></a>
** Development Tools and Issues
** Development Tools
Q: Will it be possible to use the CLI features without using bytecodes
or the JIT?
@@ -406,34 +343,14 @@ A: Yes. The CLI engine will be made available as a shared library.
Q: Will you have new development tools?
A: With any luck, Free Software enthusiasts will contribute tools to
A: Hopefully Free Software enthusiasts will contribute tools to
improve the developer environment. These tools could be developed
initially using the Microsoft implementation of the CLI and then
initially using Microsoft implementation of the CLI and then
executed later with Mono.
Q: What kind of rules make the Common Intermediate Language useful for
JITers?
A: The main rule is that the stack in the CLI is not a general purpose
stack. You are not allowed to use it for other purposes than
computing values and passing arguments to functions or return
values.
At any given call or return instruction, the types on the stack
have to be the same independently of the flow of execution of your
code.
Q: Is it true that the CIL is ideal for JITing and not efficient for
interpreters?
A: The CIL is better suited to be JITed than JVM byte codes, but you
can interpret them as trivially as you can interpret JVM byte
codes.
<a name="java">
** Mono and Java
Q: Why don't you use Java? After all, there are many languages that
Q: What about using Java? After all there are many languages that
target the Java VM.
A: You can get very good tools for doing Java development on free
@@ -452,36 +369,26 @@ A: You can get very good tools for doing Java development on free
wide variety of programming languages, and has a set of rules
designed to be optimal for JITers.
Q: Could Java target the CLI?
A: Yes, Java could target the CLI. We have details on a <a
href="ideas.html#guavac">project</a> that someone could take on to
make this happen.
Q: What kind of rules make the Common Intermediate Language useful for
JITers?
Microsoft has an implemenation of the Java language called J# that
can target the CIL execution engine.
A: The main rule is that the stack in the CLI is not a general purpose
stack. You are not allowed to use it for other purposes than
computing values and passing arguments to functions or return
values.
Q: Is it possible to write a JVM byte code to CIL convertor?
At any given call or return instruction, the types on the stack
have to be the same independently of the flow of execution of your
code.
A: Yes, it is possible. Here are a few starting point:
Q: I heard that the CIL is ideal for JITing and not efficient for
interpreters, is this the case?
<ul>
* A byte code representation is really a flattened forest of
trees. Look at the Mono JIT engine to see how we compute
the basic blocks (this is used to figure out the "trees").
A: The CIL is better suited to be JITed than JVM byte codes, but you
can interpret them as trivially as you can interpret JVM byte
codes.
The forest is just an array of trees.
Indeed, run the JIT engine with -d (mono -d prog.exe) and
you will see how these trees look like.
You will have to do something similar for Java.
* Each "forest of trees" has a meaning. This meaning can now
be translated into the equivalent "meaning" in CLR-land.
</ul>
<a name="extending"></a>
** Extending Mono
Q: Would you allow other classes other than those in the
@@ -500,18 +407,7 @@ A: Yes. The Microsoft class collection is very big, but it is by no
For more information on extending Mono, see our <a
href="ideas.html">ideas</a> page.
Q: Do you plan to Embrace and Extend .NET?
A: Embracing a good technology is good. Extending technologies in
incompatible ways is bad for the users, so we do not plan on
extending the technologies.
If you have innovative ideas, and want to create new classes, we
encourage you to make those classes operate correctly well in both
Mono and .NET
<a name="portability"></a>
** Portability
** Mono and portability
Q: Will Mono only work on Linux?
@@ -525,23 +421,9 @@ A: Our main intention at Ximian is to be able to develop GNOME
applications with Mono, but if you are interested in providing a
port of the Winform classes to other platforms (frame buffer or
MacOS X for example), we would gladly integrate them, as long
they are under an open source license.
they are under a Free Software License.
Q: Will Mono run on Windows?
A: We hope so. Currently some parts of Mono only run on Windows
(the C# compiler is a .NET executable) and other parts have only
been compiled on Linux, but work on Windows with Cygwin.
Q: Will Mono depend on GNOME?
A: It will depend only if you are using a particular assembly (for
example, for doing GUI applications). If you are just interested
in Mono for implementing a `Hello World Enterprise P2P Web
Service', you will not need any GNOME components.
<a name="reuse"></a>
** Reusing Existing Code
** Reusing existing Code
Q: What projects will you reuse or build upon?
@@ -551,9 +433,9 @@ A: We want to get Mono in the hands of programmers soon. We are
Q: What about Intel's research JIT framework, ORP?
A: At this time, we are investigating whether we can use elements of
ORP for Mono. ORP is a research JIT engine that has a clearly
ORP for Mono. ORP is a research JIT engine that has a clear
defined API that splits the JIT from the GC system and the actual
byte code implementation.
byte code implementation. It is a research product.
Q: What about using GNU Lightning?
@@ -561,16 +443,89 @@ A: We are also researching <a
href="http://www.gnu.org/software/lightning/lightning.html">GNU
Lightning</a>.
<a name="gcc"></a>
** Ximian and Microsoft
Q: Didn't Miguel de Icaza say that `Unix Sucks'?
A: Yes, he did, as a catch phrase in his opening remark on the Ottawa
Linux Symposium. His talk focused on various ways to improve Unix.
There is a paper describing some ways to improve Unix at:
<a href="http://primates.ximian.com/~miguel/bongo-bong.html">
http://primates.ximian.com/~miguel/bongo-bong.html</a>
Q: Didn't Ximian's Miguel work for Microsoft?
A: Actually, Nat Friedman (Ximian's co-founder) did work as an
intern for Microsoft for one summer but Miguel did not.
Q: Did Nat and Miguel meet at Microsoft?
A: They met online on the Linux IRC network; They met in person for
the first time in 1997.
** Mono and Microsoft
Q: How can you expect Mono to compete with Microsoft, wont this
require an effort too large?
A: You are right. Mono will never become a reality without the help
of other contributors. Ximian is a small company that can not
finish Mono alone. We will be working with members of the
community to deliver the product.
Q: Is Microsoft and Corel involved in the Mono implementation?
A: No, they are not.
Q: Are you writing Mono from the ECMA specs?
A: yes, we are writing them from the ECMA specs and the published
materials in print about .NET
** Acronyms
Q: What is the difference between CLR (Common Language Runtime) and
CLI (Common Language Infrastructure)?
A: CLI is the specification of an execution system. The Microsoft
implementation of this specification is named CLR.
Unless we come up with our own acronym, we could just call ours
also CLR, just because it would do exactly the same thing the
Microsoft implementation does.
<a name="gcc">
** Mono and GCC
Q: Are you working on a GCC front-end to C#? A GCC backend that will
generate CIL images? What about making a front-end to GCC that
takes CIL images and generates native code?
Q: Should someone work on a GCC front-end to C#?
A: We are currently seeking volunteers for those projects.
Visit the <a href="contributing.html">contributing</a> section if
you are interested.
A: I would love if someone does, and we would love to help anyone that
takes on that task, but we do not have the time or expertise to
build a C# compiler with the GCC engine. I find it a lot more fun
personally to work on C# on a C# compiler, which has an intrinsic
beauty.
Q: Should someone make a GCC backend that will generate CIL images?
A: I would love to see a backend to GCC that generates CIL images. It
would provide a ton of free compilers that would generate CIL
code. This is something that people would want to look into
anyways for Windows interoperation in the future.
Q: What about making a front-end to GCC that takes CIL images and
generates native code?
A: I would love to see this, specially since GCC supports this same
feature for Java Byte Codes. You could use the metadata library
from Mono to read the byte codes (ie, this would be your
"front-end") and generate the trees that get passed to the
optimizer.
Ideally our implementation of the CLI will be available as a shared
library that could be linked with your application as its runtime
support.
Q: But would this work around the GPL in the GCC compiler and allow
people to work on non-free front-ends?
@@ -580,84 +535,75 @@ A: People can already do this by targeting the JVM byte codes (there
Q: Why are you writing a JIT engine instead of a front-end to GCC?
A: We want the JIT engine and runtime engine because they will be able
to execute CIL executables generated on Windows, and so no recompilation
will be necessary.
A: The JIT engine and runtime engine will be able to execute CIL
executables generated on Windows.
** Mono and GNU
Q: Is Mono part of the GNU project?
A: Mono is a Ximian project, that is also part of the GNU project.
** Mono and Portability
Q: Will Mono work on other variants of Unix?
A: Yes. We do not expect to add any gratuitous incompatibilities.
Q: Will Mono run on Windows?
A: Hopefully yes. Currently some parts of Mono only run on Windows
(the C# compiler is a .NET executable) and other parts have only
been compiled on Linux, but work on Windows with Cygwin.
Q: Will Mono depend on GNOME?
A: It will depend only if you are using a particular assembly (for
example, for doing GUI applications). If you are just interested
in Mono for implementing a `Hello World Enterprise P2P Web
Service', you will not need any GNOME component.
<a name="performance"></a>
** Performance
Q: How fast will Mono be?
Q: How fast will be Mono?
A: We can not predict the future, but a conservative estimate is that
it would be at least `as fast as other JIT engines'.
We would like to ship various JIT engines with Mono, just like
Microsoft has done with their .NET development platform. We could
provide a faster, JIT for fast load times but lower performance,
and an and an optimizing JIT that would be slower at generating
code but produce more optimal output.
Now, wishfully thinking I hope that we will ship various JITs with
Mono just like Microsoft has done. A fast JITer when maximum
performance is not needed, but fast load times are important; And
an optimizing JITer that would be slower at generating code but
produce more optimal output.
The CIL has some advantages over the Java byte code: it is really
an intermediate representation and there are a number of
restrictions on how you can emit CIL code that simplify creating
better JIT engines.
For example, on the CIL, the stack is not really an abstraction
available for the code generator to use at will. Rather, it is a
way of creating a postfix representation of the parsed tree. At
any given call point or return point, the contents of the stack are
For example, on the CIL the stack is not really an abstraction
available for the code generator to use at will: it is just a way
of creating a postfix representation of the parsed tree. At any
given call point or return point, the contents of the stack are
expected to contain the same object types independently of how the
instruction was reached.
instructions was reached.
<a name="licensing"></a>
** Licensing
Q: Will I be able to write proprietary applications that run with
Mono?
A: Yes. The licensing scheme is planned to allow proprietary
developers to write applications with Mono.
Q: What license or licenses are you using for the Mono Project?
A: The C# Compiler is released under the terms of the <a
href="http://www.opensource.org/licenses/gpl-license.html">GNU GPL</a>. The runtime
libraries are under the <a
href="http://www.opensource.org/licenses/lgpl-license.html">GNU
Library GPL</a>. And the class libraries are released
under the terms of the <a
href="http://www.opensource.org/licenses/mit-license.html">MIT X11</a>
license.
Q: I would like to contribute code to Mono under a particular
license. What licenses will you accept?
A: We will have to evaluate the licenses for compatibility first,
but as a general rule, we will accept the code under the same
terms of the "container" module.
<a name="etc"></a>
** Miscellaneous Questions
** Assorted questions
Q: You say that the CLI allows multiple languages to execute on the
same environment. Isn't this the purpose of CORBA?
A: The key difference between CORBA (and COM) and the CLI is that the
CLI allows "data-level interoperability" because every
language/component uses the same data layout and memory management.
A: CORBA can be used for this purpose, but think of CORBA mostly as a
inter-process (local machine or remote machine) communication
system.
This means you can operate directly upon the datatypes that someone
else provides, without having to go via their interfaces. It also
means you don't have to "marshall" (convert) parameters (data
layouts are the same, so you can just pass components directly) and
you don't have to worry about memory managment, because all
languages/components share the same garbage collector and address
space. This means much less copying and no need for reference
counting.
Think of the CLI to be targeted to interoperation of languages in
the same process, and CORBA as being a nifty addition for
out-of-process.
Q: Will you support COM?
Sure, we have used CORBA for in-proc components, but the lack of an
ABI for in-proc components does not translate into a good framework
for in-proc systems
A: The runtime will support XPCOM on Unix systems and COM on Windows.
Most of the code for dynamic trampolines exists already.
+1 -73
View File
@@ -1,39 +1,15 @@
* Ideas
There are many pending classes that need to be implemented. Those have
the highest impact in the Mono project: the sooner they are done,
the sooner we can start using this platform to create new and
exciting applications.
That being said, if you are not very excited about working on class
libraries, here is a list of other related projects or tools that might
be useful to the Mono project.
Here are a few ideas of tools, classes and projects that you
could start. More are forthcoming.
<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).
@@ -42,71 +18,23 @@ TODO=camel,Mail API
<a href="http://cvs.gnome.org/bonsai/rview.cgi?dir=evolution%2Fcamel">
Camel implementation</a>.
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
researched the problem before
</ul>
<a name="projects">
** Projects
<ul>
TODO=xmlStorage,
* Implement an xmlStorageSystem for the CLI:
<a href="http://www.soapware.org/xmlStorageSystem">
http://www.soapware.org/xmlStorageSystem</a>
TODO=guavac,Java compiler for .NET
* You could take one of the existing Java compilers
(Guavac comes to mind as it is so nice) and modify
it to generate .NET code rather than JVM byte
codes.
This should be a pretty straightforward task.
Guavac has the advantage of being written in C++ and
it could be compiled with the Microsoft Managed C++
compiler and produce a .NET executable with it.
TODO=CORBA,CORBA implementation
* Build a CORBA interoperability engine for the CLR.
You do not need to do all of the work, just talking
the protocol will get us a long way (<a
href="http://www.omg.org">The OMG site</a> has the
CORBA specs).
Get in touch with David Taylor (dtaylo11 at bigpond
dot net dot au) as he has been working on this
project.
TODO=Bonobo,Bonobo for Mono
* Once CORBA is done, implement the Bonobo interfaces
to allow people to use Bonobo components in Mono and
Mono components with Bonobo. The best of both worlds!
TODO=moniker,Object Naming System with Monikers
* A naming space for Mono. An object naming space is
a very powerful tool. Bonobo implements a moniker
system that is more powerful than the original
moniker concept that was pioneered by COM/OLE in the
Microsoft world.
Our implementation builds on a concept, and we have
made it simpler, more powerful, more extensible and
a much better mechanism than the equivalent monikers
on Windows.
Implementing Mono monikers would benefit both
Windows users using .NET and Mono users on Unix and
Windows.
Here is <a
href="http://primates.ximian.com/~miguel/monikers.html">an
overview of the moniker system</a> in Bonobo.
href="http://www.omg.org">The OMG site</a> has the CORBA specs).
</ul>
+23 -688
View File
@@ -1,23 +1,30 @@
<table>
<tr>
<td>
<a href="http://www.ximian.com">Ximian</a> announced the
launch of the Mono project, an effort to create an Open Source
implementation of the .NET Development Framework.
** Jul 14, 2001
Mono includes: <a href="c-sharp.html">a compiler</a> for the
C# language, a <a href="runtime.html">runtime</a> for the
Common Language Infrastructure and a set of <a
href="class-library.html">class libraries</a>.
A <a
href="http://mail.ximian.com/archives/public/mono-list/2001-July/000399.html">new
release</a> of the
runtime, compiler and classes has been made. Get it <a href="download.html#july-14">here</a>
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>
** Jul 12, 2001
I keep getting questions about my opinion on Passport, even when
Mono has <b>nothing</b> to do with it. I finally <a
href="passport.html">wrote something.</a>
** Jul 9, 2001
Today <a href="http://www.ximian.com">Ximian</a> announced the
launch of the Mono
project, an effort to create a free software
(sometimes called open source) implementation of the .NET
Development Framework.
If you have questions about the
project, please read our list of <a
href="faq.html">Frequently Asked Questions</a>.
You might also want to <a href="download.html">Download the
source</a> for our work so far. Or you can grab a <a
href="snapshots">snapshot</a> of our current work.
source</a> for our work so far.
You might want to <a
href="resources.html#mailing">subscribe</a> to our mono-list
@@ -25,680 +32,8 @@
You can contact the team at: <a
href="mailto:[email protected]">[email protected]</a>
</td>
<td>
<table border=1 bgcolor>
<tr>
</tr>
<tr>
<td>
<b><a href="c-sharp.html">Compiler</a></b>
</td>
<td>
Self hosting on .NET.<br>
Classes need work to run on Mono.
</td>
</tr>
<tr>
<td>
<b>JIT</b>
</td>
<td>
Linux/x86 working.
</td>
</tr>
<tr>
<td>
<b>Interpreter</b>
</td>
<td>
Linux/PPC working<br>
In progress: StrongARM, SPARC.
</td>
</tr>
<tr>
<td>
<b><a href="class-status.html">Classes</a></b>
</td>
<td>
Corlib for self hosting mostly done
</td>
</tr>
</table>
</td>
</tr>
</table>
** Feb 11, 2002
We would like to welcome all the new developers that have
joined the project in the last couple of days. The classes
are rapidly moving.
An explanation of the relationship between <a
href="http://mail.gnome.org/archives/gnome-hackers/2002-February/msg00031.html">GNOME
and Mono</a>.
Nick is still leading our test suite platform. I can not
stress how important it is to have a good regression test suite
for our platform, as buggy class libraries are what are
stopping the compiler from running completely on Linux.
We are of course psyched to see Mono run on
non-Linux systems. Work is moving on native code generation
for StrongARM, PowerPC, and SPARC as well as porting Mono to
other systems.
There are a couple of debates on the Mono list on implementing
a set of web server classes for <a
href="http://lists.ximian.com/archives/public/mono-list/2002-February/002911.html">enabling
ASP.NET</a> on Mono.
Paolo also <a
href="http://lists.ximian.com/archives/public/mono-list/2002-February/002944.html">
posted a list of pending tasks</a> to enable the compiler to run on Linux
** Feb 10, 2002
Mike Kestner has posted an <a
href="http://lists.ximian.com/archives/public/gtk-sharp-list/2002-February/000024.html">Update
on his Gtk#</a> activities.
** Feb 4, 2002
Adam has done <a
href="http://lists.ximian.com/archives/public/mono-list/2002-February/002808.html">Qt
bindings</a> for .NET. Adam is cool.
** Jan 29, 2002
Dan Lewis has contributed a major missing set of classes to
Mono: <a
href="http://lists.ximian.com/archives/public/mono-list/2002-January/002745.html">
System.Text.RegularExpressions</a>.
This is a fully .NET compatible implementation of the .NET regular expressions,
fully Unicode aware. This contribution is very appreciated, as implementing this
was not entirely trivial (supporting Unicode, plus a regex engine which is a super
set of the Perl regex engine).
** Jan 28, 2002
The Mono contributors have relicensed the Class Libraries under
the terms of the
<a href="http://www.opensource.org/licenses/mit-license.html">MIT X11</a> license.
This license is an Open Source license, and is used by other projects
(most notably, the XFree86 project).
The runtime (JIT, metadata library, interpreter) remains under
the LGPL and the C# compiler remains under the GPL.
Our <a
href="http://www.ximian.com/about_us/press_center/press_releases/mono_partners.html">Press
Release</a>
Press coverage: <a
href="http://news.com.com/2100-1001-823734.html">CNet</a>, <a
href="http://www.wired.com/news/technology/0,1282,50037-2,00.html">Wired</a>,
<a href="http://www.infoworld.com/articles/hn/xml/02/01/28/020128hnopennet.xml">InfoWorld</a>,
<a href="http://www.newsforge.com/article.pl?sid=02/01/27/2232231">NewsForge</a>.
** Jan 23, 2002
New mailing list: <a href="mailto:[email protected]">[email protected]</a>.
This mailing list will receive automatically the patches that are submitted
to the Mono CVS to any of its modules.
This allows anyone who wants to participate in the peer-review of the
code submitted to CVS to receive patches on e-mail. It should also
expose to everyone the changes that are being done by the team every day.
** Jan 21, 2002
Dick has got a simple web server running with Mono (`MIS: Mono
Internet Server') that is mostly used to test our IO layer, a
<a href="http://primates.ximian.com/~miguel/dick-mis-server.png">screenshot</a>
Paolo and Dietmar are busy making our runtime self sufficient on
non-Windows platforms.
C# compiler front: A lot of focus in the past weeks after
the C# became self hosting has been in making the compiler a useful
tool for development: improve error handling, provide better error
reports, fixing all known bugs, and finally profiling of the compiler
has begun.
** Jan 8, 2002
Our compiler has been self-supporting since January 3rd. In
the meantime, we have been busy working on making it run on
Linux. Today Paolo got more work done on Reflection.Emit and
the compiler compiled `console.cs' (a sample Mono program) on
Linux.
** Jan 4, 2002
Dietmar landed the Unicode support patch. Class libraries and
runtimes are now fully Unicode aware. The details are <a href=
"http://lists.ximian.com/archives/public/mono-list/2002-January/002409.html">
here</a>
Last minute breaking news: Paolo got our compiler in Linux to
compile fib.cs, patches are comming tomorrow once we have
ChangeLog entries.
** Jan 4, 2002
Mike Kestner posted an update on Gtk# <a
href="http://lists.ximian.com/archives/public/gtk-sharp-list/2002-January/000021.html"><i>New
year, new direction</i></a>.
Gtk# will be our foundation on which we will be implementing
System.Windows.Forms.
** Jan 3, 2002
Mono C# compiler becomes self-sufficient. We can now continue
development of the compiler with itself.
Work on the class libraries is still underway for having a full
self hosting system. We hope to achieve our goal of self-hosting
on Linux before the end of the month.
Join the fun by downloading either tonight's <a
href="snapshots">snapshot</a> or getting your sources from our
<a href="anoncvs.html">Anonymous CVS server</a>.
** Dec 28, 2001
After a lot of work, the C# compiler can compile itself.
There are still errors in the generated image, but they are
being fixed quickly.
We will soon have the first non-Microsoft C# implementation!
** Dec 18, 2001
JIT: More work on our IO abstraction layer (Dick).
JIT: exception handling for unmanaged code (Dietmar)
System.Reflection: Support for PropertyInfo and
PropertyBuilder as well as the various queries for MethodBase.
C#: Pre-processor; Rewrite of MemberLookup which fixed many of
the outstanding issues. More bug fixing allows it to compile
more programs.
** Dec 14, 2001
Dietmar has improved the register allocation and now Mono performs
two to three times as fast as it did yesterday. Amazing.
The compiler keeps moving along, explicit interface
implementation is there.
** Dec 11, 2001
The JIT engine can now run all the compiler regression tests as
well as assorted other programs, many more opcodes added
recently. Currently the JIT engine uses a very simplistic register
allocator (just enough to allow us to focus on feature completeness)
and that will be the next major task to improve performance and
reduce spills and reloads.
On the C# compiler front: language features are now pretty
much complete. The big missing tasks are unsafe code support,
visibility, explicit interface implementation plus static flow
analysis. There are many small bugs that need to be addressed.
You can get your copy of the <a href="snapshots">latest Mono</a>
More work is also required on fixing the foundation class
libraries, it is easy to find spots now since Nick got the
`make test' going.
** Dec 1, 2001
AnonCVS access to Mono is here (updated every hour). Thanks
to <a href="http://www.hispalinux.es">HispaLinux</a> and Jesus
Climent for helping to set this up.
** Nov 30, 2001
All tests from the mono runtime work with the JIT engine now
(Dietmar).
Recursive enumeration definition in the C# compiler are
working now (Ravi).
More work on the Web classes (Gaurav).
** Nov 28, 2001
JIT land: Paolo got GDB support into the JIT engine while
Dietmar added exceptions support to it.
The C# compiler supports all array initializations now, and the
switch statement as well as fixing many existing bugs. Many
new more tests.
Nick keeps working on improving our class library test suite.
Dick has almost completed the Mono IO layer.
** Nov 16, 2001
<blockquote>
Mike Kestner has posted an <a
href="http://lists.ximian.com/archives/public/gtk-sharp-list/2001-November/000015.html">update</a>
on Gtk# development.
</blockquote>
** Nov 14, 2001
<blockquote>
Paolo today got the Mono C# compiler running <a
href="http://lists.ximian.com/archives/public/mono-list/2001-November/001941.html">on
Linux</a>. It compiles a sample program and then the sample
program is executed.
Mutator unary operators (++ and --) in the compiler are fully
functional, they used to only work on variables, and now they
are complete.
To sum things up: The Mono C# compiler is written in C# and
uses the .NET classes to get its work done. To make this work
on Linux work has to happen in various fronts:
<ul>
* The C# compiler is being worked on and can compile
many programs now (our test suite at this point is
made up of 40 tests).
* The class libraries need to be mature enough to support
the compiler, particularly System.Reflection.Emit (which is
what Paolo has been working on lately).
The compiler currently requires 103 classes from the
.NET runtime (you can get the list by running: <b>monodis --typeref mcs.exe</b>
* The interpreter should be mature enough to run the actual
compiler byte codes and the corlib bytecodes.
</ul>
At the same time, Dietmar is working on the JIT engine which will
replace our interpreter in production.
</blockquote>
** Nov 12, 2001
<blockquote>
Dietmar got value types working on the JIT engine. Sean has
got assembly loading in the runtime (required for NUnit).
More progress on enumerations and attributes from Ravi.
Nick keeps working on improving our class libraries.
</blockquote>
** Nov 8, 2001
<blockquote>
Enumerations, array access and attributes for the C# compiler are into the CVS now.
Full array support is not complete, but moving along.
</blockquote>
** Nov 5, 2001
<blockquote>
Dietmar's new set of patches to the JIT have 20 out of 33
tests running now.
</blockquote>
** Nov 4, 2001
<blockquote>
Mike Kestner, main Gtk# contributor has posted a very interesting <a
href="http://lists.ximian.com/archives/public/gtk-sharp-list/2001-November/000013.html">
update</a> on his work on Gtk#.
Ravi commited the initial support for Attributes in the
compiler.
Many HTML Controls from Leen checked into CVS.
Paolo checked in his new System.Reflection and
System.Reflection.Emit implementations. He has been working
steadily on this huge task for a few weeks now. This is the
foundation for the Mono C# compiler, and hence a very
important piece of the puzzle.
</blockquote>
** Nov 3, 2001
<blockquote>
Many clean ups have been going into the class library by Nick Drochak.
Mega patch from Dietmar: he commited the flow analysis code
for the JITer.
A lot of work has been going into the WebControls by Gaurav (4
new controls plus improved and bug fixed base classes).
</blockquote>
** Nov 1, 2001
<blockquote>
Ravi commited the caller-side method selection of methods with
variable length arguments. Now he depends on Miguel finishing
the array handling support.
</blockquote>
** Oct 27, 2001
<blockquote>
Lots of classes for System.Web from Gaurav were commited this
morning.
Some large recent developments:
The Decimal implementation from Martin Weindel has been
partially integrated (we need to put the internalcalls in
place now and compile and link the decimal code).
Derek Holden commited recently the IntegerFormatter code into
the CVS, so we got a pretty comprehensive integer formatting
engine that we can finally use all over the place.
Compiler got support for lock as well as assorted bug fixes.
Ravi is still working on array support (and then we can
optimize foreach for the array case).
Dietmar is busy working on flow analysis on the JITer, the
previous mechanism of generating the forest was wrong. Paolo
has been a busy bee reworking the System.Reflection.Emit
support code, and we should have some pretty nice stuff next
week. Dick on the other hand is still working on the
WaitOne/WaitAll emulation code. WaitAll is like select on
steroids: it can wait for different kinds of objects: files,
mutexes, events and a couple of others.
Mike Kestner is busy working on Gtk# which is now using the
.defs files to quickly wrap the API.
</blockquote>
** Oct 18, 2001
<blockquote>
Reworking expressions to support cleanly indexers and
properties. <a href="http://www.nat.org/evolution.php3">11
days</a> until Evolution 1.0 ships.
Ximian users around the world <!--a
href="http://www.bez.it/IMAGES/nora.jpg"-->rejoice<!--/a--> with
recent C# compiler progress.
</blockquote>
** Oct 17, 2001
<blockquote>
Delegate support has been checked into the compiler
(definition and invocation); break/continue implemented.
</blockquote>
** Oct 15, 2001
<blockquote>
JIT engine supports many of the object constructs now (object
creation, vtable setup, interface table setup).
The C# compiler now has almost full property support (only
missing bit are pre-post increment/decrement operations),
delegates are now created (still missing delegate invocation).
try/catch/finally is also supported in the compiler now.
System.Decimal implementation is in, as well as many crypto
classes.
</blockquote>
** Oct 5, 2001
<blockquote>
Sergey has released his first version of the <b>ilasm</b>
assembler written in C#. You can get it from his web page:
<a
href="http://mono.eurosoft.od.ua">http://mono.eurosoft.od.ua</a>.
The plan is to integrate ildasm into the Mono CVS soon. This
component should in theory also be reusable for SharpDevelop
eventually.
</blockquote>
** Oct 4, 2001
<blockquote>
Our System.Reflection.Emit implementation created its first
executable today. This means that a very simple .NET program
that was compiled on Windows was able to generate a .NET program
while running on Linux using the Mono runtime.
The various piece of the puzzle are starting to get together:
the compiler can compile simple programs now and we are
basically focusing on completeness now.
</blockquote>
** Sep 28, 2001
<blockquote>
<a
href="http://www.icsharpcode.net/OpenSource/SD/default.asp">Sharp
Develop 0.80</a> was released today.
</blockquote>
** Sep 26, 2001
<blockquote>
More progress: more opcodes are working (Paolo); The compiler
runs up to a point in Mint (Paolo); operator overloading works
(both unary and binary) all over the place (Miguel); Completed decimal
type conversions (Miguel); New build system in place based on
Ant (Sean and Sergey); Refactored and documented the
internals of the JIT engine (Dietmar); StatementExpressions
handled correctly (Miguel).
</blockquote>
** Sep 21, 2001
<blockquote>
A couple of news-worthy items: Dick got the initial thread
support into mint; Paolo implemented many new opcodes; Dietmar
got long operations and mul/div working on the JITer; Ravi rewrote
the Method selector for expressions to be conformant; Miguel
got i++ working. All in tonight's snapshot
</blockquote>
** Sep 19, 2001
<blockquote>
Paolo has written a section on <a href="porting.html">Porting
Mono</a> to othre architectures.
</blockquote>
** Sep 18, 2001
<blockquote>
<A a href="download.html#sep-18">Mono 0.7</a> has been
released (runtime engine, class libraries
and C# compiler). Check the <a href="archive/mono-0.7">Mono
0.7 announcement</a> for details
</blockquote>
** Sep 17, 2001
<blockquote>
Mike Kestner's Gtk# (Gtk-sharp) was checked into the CVS
repository. Gtk# can run a simple hello world application.
The binding is nice, as it maps Gtk+ signals to delegates in
C#. You can see the Gtk# Hello World program <a href="src/HelloWorld.cs">here</a>
Gtk-sharp should be available on the next snapshot set.
</blockquote>
** Sep 10, 2001
<blockquote>
Dietmar checked in his CIL tree/forest regeneration and most
importantly, the x86 instruction selector burg grammar.
</blockquote>
** Sep 5, 2001
<blockquote>
The MCS compiler <b>can compile the sample Hello World</b>
application and generate a Windows/CIL executable that runs!
This executable runs with the Mono Interpreter of course (see
August 28)
</blockquote>
** Sep 4, 2001
<blockquote>
Dietmar checked into CVS the `monoburg' architecture
independent instruction selector for the JIT engine.
</blockquote>
** Aug 28, 2001
<blockquote>
<b>.NET Hello World is working under Mono!</b> The latest snapshots
will let you run it.
Hello World consits of 1821 CIL instructions,
performs 66 subroutine calls and loads 12 classes from the corlib.dll
Good work Mono team!
</blockquote>
** Aug 23, 2001
<blockquote>
Lloyd Dupont has announced his OpenGL bindings for C#, they
are available here: <a
href="http://csgl.sourceforge.net">http://csgl.sourceforge.net</a>
</blockquote>
** Aug 22, 2001
<blockquote>
New version of the Mono Runtime, Compiler and Classes has been
<a
href="download.html#august-22">released.</a> Check the <a
href="archive/mono-0.6">0.6 announcement</a>.
</blockquote>
** Aug 20, 2001
<blockquote>
A new <a href="contributing.html#compile-service">Compilation
service</a> has been made available by Derek to allow people
without access to the <a
href="http://msdn.microsoft.com/downloads/default.asp?url=/downloads/sample.asp?url=/msdn-files/027/000/976/msdncompositedoc.xml&frame=true">.NET SDK</a>
</blockquote>
** Aug 3, 2001
<blockquote>
Daily snapshots of mcs and mono are now available, they will
run every night at 10pm Boston time.
</blockquote>
** Jul 29, 2001
<blockquote>
Mono Runtime 0.5 has been <a
href="download.html#july-29">released.</a> Check the <a
href="archive/mono-0.5">release notes</a>
</blockquote>
** Jul 25, 2001
<blockquote>
The slides for <A href="Presentations/O-Reilly">my
presentation</a> at <a href="http://www.oreilly.com">O'Reilly
Open Source Software Convention</a>
</blockquote>
** Jul 22, 2001
<blockquote>
Another release of the class libraries is out, check the <a
href="archive/mcs-22">MCS 22-July Release Notes</a>. You can
get the new class libraries from <a
href="download.html#july-22">here</a>
</blockquote>
** Jul 19, 2001
<blockquote>
Another release of the class libraries is out, check the <a
href="archive/mcs-19">MCS 19-July Release Notes</a>. You can
get the new class libraries from <a
href="download.html#july-19">here</a>
</blockquote>
** Jul 17, 2001
<blockquote>
Another release of the class libraries is out, check the <a
href="archive/mcs-17">MCS 17-July Release Notes</a>. You can
get the new class libraries from <a
href="download.html#july-17">here</a>
Do not forget to check out the updated <a href="faq.html">FAQ</a>.
Got Sean's new <a href="class-status/index.html">Class
Status</a> web pages up. These are a lot better than mine, and
we are now keeping better track of contributors.
</blockquote>
** Jul 15, 2001
<blockquote>
Another release of Mono is out, check the <a
href="archive/mono-0.4">Mono 0.4 Release Notes</a>. Get it <a
href="download.html#july-15">here</a>.
</blockquote>
** Jul 14, 2001
<blockquote>
A <a
href="http://lists.ximian.com/archives/public/mono-list/2001-July/000399.html">new
release</a> of the
runtime, compiler and classes has been made. Get it <a href="download.html#july-14">here</a>
</blockquote>
** Jul 12, 2001
<blockquote>
I keep getting questions about my opinion on Passport, even when
Mono has <b>nothing</b> to do with it. I finally <a
href="passport.html">wrote something.</a>
</blockquote>
** Jul 9, 2001
<blockquote>
Project launched.
</blockquote>
** O'Reilly
<blockquote>
Brian posted a story on <a
href="http://www.oreillynet.com/dotnet">O'Reilly Network .NET</a>
</blockquote>
+13 -75
View File
@@ -1,26 +1,3 @@
* Updates
<b>Sep 20, 2001:</b> Microsoft has just announced some changes
to passport that are rather interesting. This document
reflects the Passport system without taking into account the
new changes.
Read about it <a href="http://www.microsoft.com/presspass/features/2001/sep01/09-20passport.asp">here</a>.
For an analysis of security problems with passport, check <a
href="http://avirubin.com/passport.html">http://avirubin.com/passport.html</a>.
The bottom line is that you should not put any sensitive
information on passport.
I have received many comments from people, and I have updated
the page accordingly. From removing incorrect statements, to
fixing typos, to include mentions to other software pieces.
I also corrected my statement about IIS and a trojan horse, I
should read a more educated press in the future. My apologies
to Microsoft and its employees on this particular topic. IIS
did not have a trojan horse built in.
* Microsoft Hailstorm and Passport
Microsoft Passport is a centralized database hosted by
@@ -37,7 +14,7 @@
** Passport
Passport is important not because of it being a breakthrough
Passport is important not because of it being breaktrough
technologically speaking, but because the company is in a
position to drive most people toward being suscribers of it.
@@ -98,7 +75,12 @@
at the corporate level policy, but also the fact that
the source code for Microsoft products is not
available, means that trojans or worms could be built
into the products by malicious engineers.
into the products by malicious engineers. This is not
unheard of, as the <a
href="http://slashdot.org/articles/00/04/14/0619206.shtml">Microsoft
Internet Server</a> had a trojan horse built into that
allowed anyone that knew about this to control any
server running IIS.
* <b>Security:</b> With a centralized system like
Passport, imagine the repercussions of a malicious
@@ -109,21 +91,7 @@
Hackers have already <a
href="http://slashdot.org/articles/00/10/27/1147248.shtml">broken
into Microsoft</a> in the past. And the company was
unable to figure out for how long their systems had
been hacked.
Security holes have been found in <a
href="http://slashdot.org/articles/00/04/14/0619206.shtml">IIS
in the past.</a> If all the world's data is stored on
a central location, when a single security hole is
detected, it would allow an intruder to install a
backdoor within seconds into the corporate network
without people ever noticing.
Microsoft itself has been recently hit by worms,
imagine if all your business depended on a single
provider for providing all or your authentication
needs
unable to figure out for how long their systems had been hacked.
</ul>
Microsoft might or might not realize this. The idea behind
@@ -144,15 +112,6 @@
system should not create an internet `blackout' in the
case of failure.
A distributed system using different software
platforms and different vendors would be more
resistent to an attack, as holes in a particular
implementation of the server software would not affect
every person at the same time.
A security hole attack might not even be relevant to
other software vendors software.
* <b>Allow for multiple registrars:</b> Users should
be able to choose a registrar (their banks, local
phone company, service provider, Swiss bank, or any
@@ -170,14 +129,10 @@
possibility of replicating and caching public information
about the user.
For instant messaging (another piece of the Hailstorm bit),
For instant messaging (another pieces of the Hailstorm bit),
you want to use a non-centralized system like Sun's <a
href="http://www.jxta.org">JXTA</a>. Some people mailed me to
mention Jabber as a messaging platform and other people
pointed out to the <a
href="http://java.sun.com/products/jms/">Java Message
Service</a>. The JMS does support a number of very
interesting features that are worth researching.
mention Jabber as a messaging platform.
It could also just use the user e-mail address as the `key' to
choose the registrar (msn.com, hotmail.com -> passport.com;
@@ -208,7 +163,7 @@
** Deploying it
The implementation of such a system should be a pretty
straightforward task once security cryptographers have
straightforward tasks once security cryptographers have
designed such a beast.
The major problems are:
@@ -233,7 +188,7 @@
** Passport and Mono
The .NET class libraries include a Passport class that
The .NET class libraries includes a Passport class that
applications might use to authenticate with Passport. Since
we do not have information at this point on the exact protocol
of Passport, it is not even feasible to implement it.
@@ -252,18 +207,6 @@
Currently, we are too far from the point where this is a real
issue.
** Passport and endangering Open Source.
A few people have said: `Mono will allow Passport to be
available for Linux and that is bad'. This is plain
misinformation.
Currently, you can obtain Passport for Linux from Microsoft
itself and deploy it today on your Web server. Mono does not
even enter the picture here. Go to passport.com and download
the toolkit and you will see with your own eyes that passport
is <B>already</b> available for Linux.
** Disclaimer
This is just a group of personal thoughts of mine that I have
@@ -276,12 +219,7 @@
Nat Friedman (Ximian's co-founder) has his own ideas on how a
competing system to Passport could be designed, but I will let
<a href="http://www.nat.org/">him</a> post his own story.
** Other Passport Comments
An interesting study on the security of passport is available at: <a
href="http://avirubin.com/passport.html">http://avirubin.com/passport.html</a>
<a href="http://www.nat.org/gym">him</a> post his own story.
** Other Alternatives
-384
View File
@@ -1,384 +0,0 @@
Microsoft.Win32.Registry
Microsoft.Win32.RegistryHive
Microsoft.Win32.RegistryKey
System.__ComObject
System.Activator
System.ArgIterator
System.AssemblyLoadEventHandler
System.AsyncCallback
System.CrossAppDomainDelegate
System.DBNull
System.Diagnostics.SymbolStore.SymDocumentType
System.Diagnostics.SymbolStore.SymLanguageType
System.Diagnostics.SymbolStore.SymLanguageVendor
System.EventHandler
System.Globalization.CompareInfo
System.Globalization.HebrewCalendar
System.Globalization.HijriCalendar
System.Globalization.JapaneseCalendar
System.Globalization.KoreanCalendar
System.Globalization.RegionInfo
System.Globalization.SortKey
System.Globalization.StringInfo
System.Globalization.TaiwanCalendar
System.Globalization.TextElementEnumerator
System.Globalization.TextInfo
System.Globalization.ThaiBuddhistCalendar
System.IO.EndOfStreamException
System.IO.IsolatedStorage.IsolatedStorage
System.IO.IsolatedStorage.IsolatedStorageException
System.IO.IsolatedStorage.IsolatedStorageFile
System.IO.PathTooLongException
System.Reflection.Emit.MethodRental
System.Reflection.MemberFilter
System.Reflection.Missing
System.Reflection.ModuleResolveEventHandler
System.Reflection.Pointer
System.Reflection.StrongNameKeyPair
System.Reflection.TargetException
System.Reflection.TypeFilter
System.ResolveEventHandler
System.Runtime.CompilerServices.AccessedThroughPropertyAttribute
System.Runtime.CompilerServices.CallConvCdecl
System.Runtime.CompilerServices.CallConvFastcall
System.Runtime.CompilerServices.CallConvStdcall
System.Runtime.CompilerServices.CallConvThiscall
System.Runtime.CompilerServices.CompilationRelaxationsAttribute
System.Runtime.CompilerServices.CompilerGlobalScopeAttribute
System.Runtime.CompilerServices.CustomConstantAttribute
System.Runtime.CompilerServices.DateTimeConstantAttribute
System.Runtime.CompilerServices.DecimalConstantAttribute
System.Runtime.CompilerServices.DiscardableAttribute
System.Runtime.CompilerServices.IDispatchConstantAttribute
System.Runtime.CompilerServices.IsVolatile
System.Runtime.CompilerServices.IUnknownConstantAttribute
System.Runtime.CompilerServices.RequiredAttributeAttribute
System.Runtime.InteropServices.ArrayWithOffset
System.Runtime.InteropServices.AssemblyRegistrationFlags
System.Runtime.InteropServices.AutomationProxyAttribute
System.Runtime.InteropServices.BIND_OPTS
System.Runtime.InteropServices.BINDPTR
System.Runtime.InteropServices.CALLCONV
System.Runtime.InteropServices.ClassInterfaceAttribute
System.Runtime.InteropServices.ClassInterfaceType
System.Runtime.InteropServices.CoClassAttribute
System.Runtime.InteropServices.ComAliasNameAttribute
System.Runtime.InteropServices.ComConversionLossAttribute
System.Runtime.InteropServices.ComEventInterfaceAttribute
System.Runtime.InteropServices.COMException
System.Runtime.InteropServices.ComImportAttribute
System.Runtime.InteropServices.ComInterfaceType
System.Runtime.InteropServices.ComMemberType
System.Runtime.InteropServices.ComRegisterFunctionAttribute
System.Runtime.InteropServices.ComSourceInterfacesAttribute
System.Runtime.InteropServices.ComUnregisterFunctionAttribute
System.Runtime.InteropServices.ComVisibleAttribute
System.Runtime.InteropServices.CONNECTDATA
System.Runtime.InteropServices.CurrencyWrapper
System.Runtime.InteropServices.DESCKIND
System.Runtime.InteropServices.DispatchWrapper
System.Runtime.InteropServices.DispIdAttribute
System.Runtime.InteropServices.DISPPARAMS
System.Runtime.InteropServices.ELEMDESC
System.Runtime.InteropServices.ErrorWrapper
System.Runtime.InteropServices.EXCEPINFO
System.Runtime.InteropServices.Expando.IExpando
System.Runtime.InteropServices.ExporterEventKind
System.Runtime.InteropServices.ExtensibleClassFactory
System.Runtime.InteropServices.FILETIME
System.Runtime.InteropServices.FUNCDESC
System.Runtime.InteropServices.FUNCFLAGS
System.Runtime.InteropServices.FUNCKIND
System.Runtime.InteropServices.GCHandle
System.Runtime.InteropServices.GuidAttribute
System.Runtime.InteropServices.HandleRef
System.Runtime.InteropServices.ICustomAdapter
System.Runtime.InteropServices.ICustomFactory
System.Runtime.InteropServices.ICustomMarshaler
System.Runtime.InteropServices.IDispatchImplAttribute
System.Runtime.InteropServices.IDispatchImplType
System.Runtime.InteropServices.IDLDESC
System.Runtime.InteropServices.IDLFLAG
System.Runtime.InteropServices.IMPLTYPEFLAGS
System.Runtime.InteropServices.ImportedFromTypeLibAttribute
System.Runtime.InteropServices.ImporterEventKind
System.Runtime.InteropServices.InterfaceTypeAttribute
System.Runtime.InteropServices.InvalidComObjectException
System.Runtime.InteropServices.InvalidOleVariantTypeException
System.Runtime.InteropServices.INVOKEKIND
System.Runtime.InteropServices.IRegistrationServices
System.Runtime.InteropServices.ITypeLibConverter
System.Runtime.InteropServices.ITypeLibExporterNameProvider
System.Runtime.InteropServices.ITypeLibExporterNotifySink
System.Runtime.InteropServices.ITypeLibImporterNotifySink
System.Runtime.InteropServices.LCIDConversionAttribute
System.Runtime.InteropServices.LIBFLAGS
System.Runtime.InteropServices.MarshalDirectiveException
System.Runtime.InteropServices.ObjectCreationDelegate
System.Runtime.InteropServices.PARAMDESC
System.Runtime.InteropServices.PARAMFLAG
System.Runtime.InteropServices.PreserveSigAttribute
System.Runtime.InteropServices.PrimaryInteropAssemblyAttribute
System.Runtime.InteropServices.ProgIdAttribute
System.Runtime.InteropServices.RegistrationServices
System.Runtime.InteropServices.RuntimeEnvironment
System.Runtime.InteropServices.SafeArrayRankMismatchException
System.Runtime.InteropServices.SafeArrayTypeMismatchException
System.Runtime.InteropServices.SEHException
System.Runtime.InteropServices.STATSTG
System.Runtime.InteropServices.SYSKIND
System.Runtime.InteropServices.TYPEATTR
System.Runtime.InteropServices.TYPEDESC
System.Runtime.InteropServices.TYPEFLAGS
System.Runtime.InteropServices.TYPEKIND
System.Runtime.InteropServices.TYPELIBATTR
System.Runtime.InteropServices.TypeLibConverter
System.Runtime.InteropServices.TypeLibExporterFlags
System.Runtime.InteropServices.TypeLibFuncAttribute
System.Runtime.InteropServices.TypeLibFuncFlags
System.Runtime.InteropServices.TypeLibImporterFlags
System.Runtime.InteropServices.TypeLibTypeAttribute
System.Runtime.InteropServices.TypeLibTypeFlags
System.Runtime.InteropServices.TypeLibVarAttribute
System.Runtime.InteropServices.TypeLibVarFlags
System.Runtime.InteropServices.UCOMIBindCtx
System.Runtime.InteropServices.UCOMIConnectionPoint
System.Runtime.InteropServices.UCOMIConnectionPointContainer
System.Runtime.InteropServices.UCOMIEnumConnectionPoints
System.Runtime.InteropServices.UCOMIEnumConnections
System.Runtime.InteropServices.UCOMIEnumMoniker
System.Runtime.InteropServices.UCOMIEnumString
System.Runtime.InteropServices.UCOMIEnumVARIANT
System.Runtime.InteropServices.UCOMIMoniker
System.Runtime.InteropServices.UCOMIPersistFile
System.Runtime.InteropServices.UCOMIRunningObjectTable
System.Runtime.InteropServices.UCOMIStream
System.Runtime.InteropServices.UCOMITypeComp
System.Runtime.InteropServices.UCOMITypeInfo
System.Runtime.InteropServices.UCOMITypeLib
System.Runtime.InteropServices.UnknownWrapper
System.Runtime.InteropServices.VARDESC
System.Runtime.InteropServices.VARFLAGS
System.Runtime.Remoting.ActivatedClientTypeEntry
System.Runtime.Remoting.ActivatedServiceTypeEntry
System.Runtime.Remoting.Activation.UrlAttribute
System.Runtime.Remoting.Channels.BaseChannelObjectWithProperties
System.Runtime.Remoting.Channels.BaseChannelSinkWithProperties
System.Runtime.Remoting.Channels.BaseChannelWithProperties
System.Runtime.Remoting.Channels.ChannelDataStore
System.Runtime.Remoting.Channels.ChannelServices
System.Runtime.Remoting.Channels.ClientChannelSinkStack
System.Runtime.Remoting.Channels.IChannel
System.Runtime.Remoting.Channels.IChannelDataStore
System.Runtime.Remoting.Channels.IChannelReceiver
System.Runtime.Remoting.Channels.IChannelReceiverHook
System.Runtime.Remoting.Channels.IChannelSender
System.Runtime.Remoting.Channels.IChannelSinkBase
System.Runtime.Remoting.Channels.IClientChannelSink
System.Runtime.Remoting.Channels.IClientChannelSinkProvider
System.Runtime.Remoting.Channels.IClientChannelSinkStack
System.Runtime.Remoting.Channels.IClientFormatterSink
System.Runtime.Remoting.Channels.IClientFormatterSinkProvider
System.Runtime.Remoting.Channels.IClientResponseChannelSinkStack
System.Runtime.Remoting.Channels.IServerChannelSink
System.Runtime.Remoting.Channels.IServerChannelSinkProvider
System.Runtime.Remoting.Channels.IServerChannelSinkStack
System.Runtime.Remoting.Channels.IServerFormatterSinkProvider
System.Runtime.Remoting.Channels.IServerResponseChannelSinkStack
System.Runtime.Remoting.Channels.ITransportHeaders
System.Runtime.Remoting.Channels.ServerChannelSinkStack
System.Runtime.Remoting.Channels.ServerProcessing
System.Runtime.Remoting.Channels.SinkProviderData
System.Runtime.Remoting.Channels.TransportHeaders
System.Runtime.Remoting.Contexts.ContextProperty
System.Runtime.Remoting.Contexts.CrossContextDelegate
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.Remoting.IChannelInfo
System.Runtime.Remoting.IEnvoyInfo
System.Runtime.Remoting.InternalRemotingServices
System.Runtime.Remoting.IObjectHandle
System.Runtime.Remoting.IRemotingTypeInfo
System.Runtime.Remoting.Lifetime.ClientSponsor
System.Runtime.Remoting.Lifetime.ILease
System.Runtime.Remoting.Lifetime.ISponsor
System.Runtime.Remoting.Lifetime.LeaseState
System.Runtime.Remoting.Lifetime.LifetimeServices
System.Runtime.Remoting.Messaging.AsyncResult
System.Runtime.Remoting.Messaging.CallContext
System.Runtime.Remoting.Messaging.ConstructionCall
System.Runtime.Remoting.Messaging.ConstructionResponse
System.Runtime.Remoting.Messaging.Header
System.Runtime.Remoting.Messaging.HeaderHandler
System.Runtime.Remoting.Messaging.ILogicalThreadAffinative
System.Runtime.Remoting.Messaging.IMessageCtrl
System.Runtime.Remoting.Messaging.IMessageSink
System.Runtime.Remoting.Messaging.IMethodCallMessage
System.Runtime.Remoting.Messaging.InternalMessageWrapper
System.Runtime.Remoting.Messaging.IRemotingFormatter
System.Runtime.Remoting.Messaging.LogicalCallContext
System.Runtime.Remoting.Messaging.MessageSurrogateFilter
System.Runtime.Remoting.Messaging.MethodCall
System.Runtime.Remoting.Messaging.MethodCallMessageWrapper
System.Runtime.Remoting.Messaging.MethodResponse
System.Runtime.Remoting.Messaging.MethodReturnMessageWrapper
System.Runtime.Remoting.Messaging.OneWayAttribute
System.Runtime.Remoting.Messaging.RemotingSurrogateSelector
System.Runtime.Remoting.Messaging.ReturnMessage
System.Runtime.Remoting.Metadata.SoapAttribute
System.Runtime.Remoting.Metadata.SoapFieldAttribute
System.Runtime.Remoting.Metadata.SoapMethodAttribute
System.Runtime.Remoting.Metadata.SoapOption
System.Runtime.Remoting.Metadata.SoapParameterAttribute
System.Runtime.Remoting.Metadata.SoapTypeAttribute
System.Runtime.Remoting.Metadata.W3cXsd2001.ISoapXsd
System.Runtime.Remoting.Metadata.W3cXsd2001.SoapAnyUri
System.Runtime.Remoting.Metadata.W3cXsd2001.SoapBase64Binary
System.Runtime.Remoting.Metadata.W3cXsd2001.SoapDate
System.Runtime.Remoting.Metadata.W3cXsd2001.SoapDateTime
System.Runtime.Remoting.Metadata.W3cXsd2001.SoapDay
System.Runtime.Remoting.Metadata.W3cXsd2001.SoapDuration
System.Runtime.Remoting.Metadata.W3cXsd2001.SoapEntities
System.Runtime.Remoting.Metadata.W3cXsd2001.SoapEntity
System.Runtime.Remoting.Metadata.W3cXsd2001.SoapHexBinary
System.Runtime.Remoting.Metadata.W3cXsd2001.SoapId
System.Runtime.Remoting.Metadata.W3cXsd2001.SoapIdref
System.Runtime.Remoting.Metadata.W3cXsd2001.SoapIdrefs
System.Runtime.Remoting.Metadata.W3cXsd2001.SoapInteger
System.Runtime.Remoting.Metadata.W3cXsd2001.SoapLanguage
System.Runtime.Remoting.Metadata.W3cXsd2001.SoapMonth
System.Runtime.Remoting.Metadata.W3cXsd2001.SoapMonthDay
System.Runtime.Remoting.Metadata.W3cXsd2001.SoapName
System.Runtime.Remoting.Metadata.W3cXsd2001.SoapNcName
System.Runtime.Remoting.Metadata.W3cXsd2001.SoapNegativeInteger
System.Runtime.Remoting.Metadata.W3cXsd2001.SoapNmtoken
System.Runtime.Remoting.Metadata.W3cXsd2001.SoapNmtokens
System.Runtime.Remoting.Metadata.W3cXsd2001.SoapNonNegativeInteger
System.Runtime.Remoting.Metadata.W3cXsd2001.SoapNonPositiveInteger
System.Runtime.Remoting.Metadata.W3cXsd2001.SoapNormalizedString
System.Runtime.Remoting.Metadata.W3cXsd2001.SoapNotation
System.Runtime.Remoting.Metadata.W3cXsd2001.SoapPositiveInteger
System.Runtime.Remoting.Metadata.W3cXsd2001.SoapQName
System.Runtime.Remoting.Metadata.W3cXsd2001.SoapTime
System.Runtime.Remoting.Metadata.W3cXsd2001.SoapToken
System.Runtime.Remoting.Metadata.W3cXsd2001.SoapYear
System.Runtime.Remoting.Metadata.W3cXsd2001.SoapYearMonth
System.Runtime.Remoting.Metadata.XmlFieldOrderOption
System.Runtime.Remoting.Proxies.ProxyAttribute
System.Runtime.Remoting.Proxies.RealProxy
System.Runtime.Remoting.RemotingConfiguration
System.Runtime.Remoting.RemotingException
System.Runtime.Remoting.RemotingServices
System.Runtime.Remoting.RemotingTimeoutException
System.Runtime.Remoting.ServerException
System.Runtime.Remoting.Services.EnterpriseServicesHelper
System.Runtime.Remoting.Services.ITrackingHandler
System.Runtime.Remoting.Services.TrackingServices
System.Runtime.Remoting.SoapServices
System.Runtime.Remoting.TypeEntry
System.Runtime.Remoting.WellKnownClientTypeEntry
System.Runtime.Remoting.WellKnownServiceTypeEntry
System.Runtime.Serialization.Formatter
System.Runtime.Serialization.FormatterConverter
System.Runtime.Serialization.Formatters.Binary.BinaryFormatter
System.Runtime.Serialization.Formatters.InternalRM
System.Runtime.Serialization.Formatters.InternalST
System.Runtime.Serialization.Formatters.ServerFault
System.Runtime.Serialization.Formatters.SoapFault
System.Runtime.Serialization.Formatters.SoapMessage
System.Runtime.Serialization.FormatterServices
System.Runtime.Serialization.ObjectIDGenerator
System.Runtime.Serialization.ObjectManager
System.Runtime.Serialization.SerializationBinder
System.Runtime.Serialization.SerializationEntry
System.Runtime.Serialization.SerializationInfoEnumerator
System.Runtime.Serialization.SurrogateSelector
System.RuntimeArgumentHandle
System.Security.AllowPartiallyTrustedCallersAttribute
System.Security.Cryptography.CryptoConfig
System.Security.Cryptography.DSACryptoServiceProvider
System.Security.Cryptography.HMACSHA1
System.Security.Cryptography.KeyedHashAlgorithm
System.Security.Cryptography.MACTripleDES
System.Security.Cryptography.MaskGenerationMethod
System.Security.Cryptography.PasswordDeriveBytes
System.Security.Cryptography.PKCS1MaskGenerationMethod
System.Security.Cryptography.RandomNumberGenerator
System.Security.Cryptography.RC2
System.Security.Cryptography.RC2CryptoServiceProvider
System.Security.Cryptography.Rijndael
System.Security.Cryptography.RijndaelManaged
System.Security.Cryptography.RNGCryptoServiceProvider
System.Security.Cryptography.RSA
System.Security.Cryptography.RSACryptoServiceProvider
System.Security.Cryptography.RSAOAEPKeyExchangeDeformatter
System.Security.Cryptography.RSAOAEPKeyExchangeFormatter
System.Security.Cryptography.RSAParameters
System.Security.Cryptography.RSAPKCS1KeyExchangeDeformatter
System.Security.Cryptography.RSAPKCS1KeyExchangeFormatter
System.Security.Cryptography.RSAPKCS1SignatureDeformatter
System.Security.Cryptography.RSAPKCS1SignatureFormatter
System.Security.Cryptography.SHA1Managed
System.Security.Cryptography.SHA384Managed
System.Security.Cryptography.SHA512Managed
System.Security.Cryptography.TripleDES
System.Security.Cryptography.TripleDESCryptoServiceProvider
System.Security.Cryptography.X509Certificates.X509Certificate
System.Security.NamedPermissionSet
System.Security.Permissions.EnvironmentPermission
System.Security.Permissions.FileDialogPermission
System.Security.Permissions.FileDialogPermissionAccess
System.Security.Permissions.IsolatedStorageFilePermission
System.Security.Permissions.IsolatedStoragePermissionAttribute
System.Security.Permissions.PrincipalPermission
System.Security.Permissions.PrincipalPermissionAttribute
System.Security.Permissions.PublisherIdentityPermission
System.Security.Permissions.PublisherIdentityPermissionAttribute
System.Security.Permissions.ReflectionPermission
System.Security.Permissions.RegistryPermission
System.Security.Permissions.SecurityPermission
System.Security.Permissions.SecurityPermissionAttribute
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.AllMembershipCondition
System.Security.Policy.ApplicationDirectory
System.Security.Policy.ApplicationDirectoryMembershipCondition
System.Security.Policy.FileCodeGroup
System.Security.Policy.FirstMatchCodeGroup
System.Security.Policy.Hash
System.Security.Policy.HashMembershipCondition
System.Security.Policy.NetCodeGroup
System.Security.Policy.PermissionRequestEvidence
System.Security.Policy.PolicyStatement
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
System.Threading.IOCompletionCallback
System.Threading.ThreadStart
System.Threading.TimerCallback
System.Threading.WaitCallback
System.Threading.WaitOrTimerCallback
System.TimeZone
System.TypedReference
System.UnhandledExceptionEventHandler
System.WeakReference
-63
View File
@@ -1,63 +0,0 @@
* How to port Mono to your preferred architecture
** Endian, 64 bits and unaligned access issues
The first thing to do is to check that the metadata handling
library works on your target processor. You may use the disassembler
on simple programs and check that you get sensible results
(assuming it compiles at all on your system:-).
The main issue is to write macros that read unaligned
little endian shorts/ints/longs/float/doubles: look into
mono/metadata/endian.h. There may be other spots in the code that are
unsafe at reading/writing to some datatypes that require special
alignment, but there should be few such issues and they need to be fixed.
Once this stuff is sorted out, you should be able to run the interpreter
on simple programs that don't require delegates, P/Invoke functions etc..
** Generating assembly bytecodes for the target processor
Next, you need to provide the support code for generating assembly bytecode
for your target platform (in mono/arch/{ppc,sparc,alpha,*}).
The code should be more or less like the code in x86-codegen.h:
macros that produce fast in-line code. You don't need to provide
code to create every possible code, at first, just the code to
create trampolines and execute them is fine (you'll need to research
how the call convention works on your platform): that would be, for
example, the prolog and epilog code in a function, code to pass function
parameters and deal with the return value and so on.
libffi in gcc or the xptcall sources in mozilla may be helpful to
understand how the calling convention works, if you can't find a specification.
You'd need a processor manual to know how to create the assembly binary data.
This requires a lot of reading if you're not familiar with the assembly for your
target platform. Manuals for many processors are available as PDF files on the
web site of the respective vendors. Note that some processors require you to
flush the I-cache before executing the code: have a look at how the same thing is
done in GNU lightning.
** Getting the interpreter to work
Once you can generate binary code, you can start working on a
mono_create_trampoline() function for your platform: this function will receive
a MonoMethod that describes the arguments and the return type of a C function
and will create the code to call such function. When this function is complete
you'll be able to run more sample programs, that use System.IO, P/Invoke
functions etc.
To support delegates you'll need to write a mono_create_method_pointer()
function that creates a native function: this can be used to call the
method using the runtime's calling convention (it's basically the reverse
of mono_create_trampoline()).
** The final step: porting the JIT
At this point you'd need to have a more complete code generation header file
and you can start writing the machine description file for the monoburg
system. This code (jit/tesjit.c) will require some machine specific tweaks,
but hopefully all you have to do is create the grammar that emit assembly
code from the IR tree. Work is at the early stages also for x86 on this stuff
as we are still testing various solutions: you'd want to read about burg-like
code-generator generators (the LCC book is a good starting point).
+1 -1
View File
@@ -18,7 +18,7 @@
standard GNOME interfaces for easily creating reusable,
language independent components, controls and compound
documents. This technology is known as <a
href="http://developer.ximian.com/tech/bonobo.html">Bonobo</a>.
href="http://www.ximian.com/tech/bonobo.php3">Bonobo</a>.
Interfaces to Bonobo exist for C, Perl, Python, and
Java.
-46
View File
@@ -1,46 +0,0 @@
To: [email protected], [email protected]
Subject: July 12 snapshots.
FCC: ~/Mail/outbox.txt
X-Windows: Sometimes you fill a vacuum and it still sucks.
--text follows this line--
Hey!
July 12 snapshots of class libraries, the compiler and the mono
runtime are available.
New on this release:
* Runtime (module: mono)
The beginning of a simple interpreter that Paolo started
workign on (can run really simple .NET programs).
Disassembler copes with more elements of the binary format and
more tokens are decoded. Paolo is working now on moving some
of these to the metadata library.
More tables are dumped.
* Class libraries (module: mcs/class)
Many new more classes are in from Joe, Vladimir, Jeff, Sean
and yours truly.
Sean fixed the build process, and it is now possible to
compile with a single command the assemblies. We will be
revisiting this mechanism in the future to compile per-OS
assemblies (ie, Unix, Windows, MacOS, etc).
* Compiler (module mcs/mcs)
Not much done this week, just a few fixes here and there, and
more work to make it easy to compiler.
* Documentation (module: mono/doc)
All the changes to the web site are there for your browsing
pleasure. We still need to integrate the status system in
there.
Miguel.
-43
View File
@@ -1,43 +0,0 @@
To: [email protected]
Subject: Sunday snapshot available.
Gcc: mail.2001-07
--text follows this line--
Hey guys,
I promise I will not be doing these so often once we have the CVS
server up. In the meantime:
* MCS
Sean got the classes to compile in a single go. You
will need CygWin (www.cygwin.org) to compile though
(GNU make and stuff is required).
System.Xml.XmlReader contribution from Jason
(WOOHHOO!!). It also contains a nice test-suite for
his functions, and in his new code bit, his
implementation is faster than Microsoft's
We now ship `jay' as part of the distribution to allow
you to compile the compiler with the same `make'
command. Small fixes to the parser as well were
introduced.
* Mono 0.4
Paolo's interpreter supports call instructions and has
the test suite program that he posted about.
All documentation ships now in the mono-0.4.tar.gz
Notes:
As usual, MCS is targeted to be compiled on a Windows machine
(you will need Cygwin).
Mono is targeted to be compiled on a Unix machine or a Windows
machine running Cygwin.
Miguel.
+7 -86
View File
@@ -7,64 +7,9 @@
If you want to send suggestions for links, address them to <a
mailto="[email protected]">[email protected]</a>.
** Microsoft .NET
The <a href="http://msdn.microsoft.com/net">Microsoft.NET site.
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>
** IRC
Various Mono contributors get together on channel #mono on
irc.gnome.org
** Mono related sites.
Sergey's web page on Mono resources:
<a href="http://mono.eurosoft.od.ua">http://mono.eurosoft.od.ua</a>
Got Dot Net:
<a href="http://www.gotdotnet.com">Got Dot Net</a>
MonoMail:
<a href="http://sourceforge.net/projects/monomail/">http://sourceforge.net/projects/monomail/</a>
Zip classes:
Mike's port to .NET: <a
href="http://www.icsharpcode.net/OpenSource/NZipLib/default.asp">NZipLib</a>
.NET Security:
A nice overview paper on the <a
href="http://www.foundstone.com/pdf/dotnet-security-framework.pdf">.NET
security architecture</a>.
** Presentations
Currently the <a href="Presentations/O-Reilly">O'Reilly</a>
presentation on Mono is available. Arturo Espinosa has given
a talk on Mono in Mexico and made <a
href="http://construct.ximian.com/~arturo/Presentations/Mono.OLS/html">spanish
slides</a>
** ECMA Documentation.
You can get the documentation for the ECMA specs from:
<ul>
* <a href="http://www.ecma.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>
Older copies of the standard are available here:
You can get the documentation for the ECMA specs from a number of sites:
<ul>
* <a href="http://msdn.microsoft.com/net/ecma">At MSDN</a>
* <a href="http://www.dotnetexperts.com">Dot Net Experts</a>
@@ -94,25 +39,15 @@
<ul>
* <b><a
href="http://lists.ximian.com/mailman/listinfo/mono-list">mono-list:</a></b>
href="http://mail.ximian.com/mailman/listinfo/mono-list">mono-list:</a></b>
The general Mono discussion list.
* <b><a
href="http://lists.ximian.com/mailman/listinfo/mono-announce-list">mono-announce-list:</a></b>
href="http://mail.ximian.com/mailman/listinfo/mono-announce-list">mono-announce-list:</a></b>
Announcements of Mono developments.
* <b><a
href="http://lists.ximian.com/mailman/listinfo/mono-gc-list">mono-gc-list:</a></b>
Discussion on the GC system of Mono.
* <b><a
href="http://lists.ximian.com/mailman/listinfo/mono-cvs-list">mono-cvs-list:</a></b>
Track the CVS activity of Mono on this mailing list. You can get <a href="http://www.go-mono.com/snapshots">daily snapshots</a> as well.
* <b><a
href="http://lists.ximian.com/mailman/listinfo/mono-docs-list">mono-docs-list:</a></b>
href="http://mail.ximian.com/mailman/listinfo/mono-docs-list">mono-docs-list:</a></b>
Discussion on the documentation of Mono.
* <b><a
href="http://lists.ximian.com/mailman/listinfo/mono-patches">mono-patches:</a></b>
Track the development of Mono in realtime: receive patches to the Mono repository
by email.
* <b><a
href="http://discuss.develop.com/dotnet.html">Dotnet mailing
list at Develop.com:</a></b> The guys at Develop Mentor run
this general purpose mailing list.
@@ -140,31 +75,17 @@
href="http://www.icsharpcode.net/OpenSource/SD/default.asp">Sharp
Develop:</a> an IDE for the C# language written in C#.
* <a
href="http://janet-js.sourceforge.net/">Janet:</a>
an implemention of ECMAScript (the standarized
version of JavaScript) in C#
* <a
href="http://xmarks.sourceforge.net/doc.html">XMarks DOC.NET:</a> For
creating online documentation you can browse for your own classes.
href="http://www.southern-storm.com.au/portable_net.html">Portable.NET:</a>
* <a href="http://nunit.sourceforge.net">NUnit:</a> A
testing framework for .NET classes.
testing framework for .NET classes.
* <a href="http://www.kaffe.org">Kaffe:</a> A popular
Free Software JIT engine for Java.
* <a href="http://www.intel.com/research/mrl/orp">ORP:</a> A research
JIT/VM/GC system from Intel.
* C# bindings for OpenGL and SDL are available here: <a
href="http://csgl.sourceforge.net">http://csgl.sourceforge.net</a>
* <a
href="http://www.southern-storm.com.au/portable_net.html">Portable.NET:</a>
Another implementation of the CLI and C# compiler.
JIT/VM/GC system from Intel.
</ul>
** GNOME Documentation
+54 -74
View File
@@ -1,98 +1,95 @@
* The Mono runtime
The MonoNet runtime
The Mono runtime implements a JIT engine for the CIL virtual
machine (as well as a byte code interpreter, this is to
quickly port it to new systems), the class loader, the garbage
collector, threading system and metadata access libraries.
The MonoNet runtime will implement the JIT engine (and a byte
code interpreter for quickly porting to new systems), the
class loader, the garbage collector, threading system and
metadata access libraries.
We currently have two runtimes:
Currently the runtime contains the beginning of an image
loader and metadata access entry points. Since Beta2 has been
now released, it is possible to resume work using the ECMA
specs and testing with Beta2-generated executables.
<ul>
* <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>
Currently both runtimes are missing garbage collection. We
are planning on using the ORP GC engine and deploy it by
middle January.
* COM and XPCOM
We plan on adding support for XPCOM on Unix and COM on Microsoft
Windows later in our development process.
The runtime core will be implemented in C, in a library
"libMonoVES.so".
** Executing MSIL/CIL images
The code will load an executable and map the references to
external assemblies to our own version of the assemblies on
Linux.
GNU/Linux.
Our roadmap looks like this, this has been updated as of
<b>Dec 18, 2001</b>:
<b>Jul 15, 2001</b>:
<ul>
* Milestone 1: <b>Done</b> Fully read and parse all CIL byte-codes
and metadata tokens (ie, a disassembler).
* Milestone 1: Fully read and parse all CIL byte-codes
and metadata tokens (ie, a disassembler).
* Milestone 2: <b>Done</b> Complete an interpreter for CIL byte
* Milestone 2: Complete an interpreter for CIL byte
codes. This interpreter can be used temporarly to
run CIL byte code on a system where no JIT is
available.
* Milestone 3: <b>Done</b>Define an <i>lburg</i>-like
instruction selector for the JITer for Intel.
* Milestone 3: Define an <i>lburg</i> instruction
selector for the JITer for Intel. Although slower
at JITing than a streaming JITer, it generates
better code. The same grammar can later be used for
the stream jitter.
* Milestone 4: <b>Done</b> Implement JITer. This is where our
current efforts are focused on, the JITer currently runs
all of the code we have tested on it. The major limitation
is that our class libraries are not complete, and hence not
every application can be ran.
* Milestone 4: Implement JITer.
* Milestone 5: Port of the JITer to non IA32 systems.
</ul>
A setup similar to the Kaffe JIT engine will be used to
A setup similar to the Kaffe JIT engine can be used to
layout the code to support non-IA32 architectures. Our work
will be focused on getting a IA32 version running first.
The JIT engine should work on Linux and Win32, although you
will need to install the CygWin32 development tools to get a
Unix-like compilation environment (mostly we use GNU make in
a few of the makefiles).
Unix-like compilation environment.
** JIT Engine (<b>updated, Dec 18th, 2001</b>)
** JIT Engine (<b>updated, Jul 14th, 2001</b>)
The JIT engine uses a code-generator generator approach for
compilation. Given the properties of CIL byte codes, we can
take full advantage of a real instruction selector for our
code generator.
We will be using a code-generator generator approach for our
JITer. Given the properties of CIL byte codes, we can take
full advantage of a real instruction selector for our code
generator.
There are a couple of books that deal with this technique: "A
Retargetable C Compiler" and "Advanced Compiler Design and
Implementation" are good references. You can also get a
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>.
href="http://research.microsoft.com/copyright/accept.asp?path=http://www.research.microsoft.com/~drh/pubs/iburg.pdf&pub=ACM">lbrug</a>
A few papers that describe the instruction selector:
Previously we had looked at a number of JIT engines and tools,
but they would not take full advantage of the CIL properties:
<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>
* <a
href="http://www.intel.com/research/mrl/orp/">ORP</a>
* <a
href="http://www.gnu.org/software/lightning/">GNU
Lightning</a>
* <a href="http://research.microsoft.com/copyright/accept.asp?path=http://www.research.microsoft.com/~drh/pubs/iburg.pdf&pub=ACM">Engineering efficient code generators using tree matching and dynamic programming.</a>
* href="http://www.eecs.harvard.edu/~nr/toolkit/">NJ Machine
Toolkit</a>.).
* VCODE.
</ul>
** Garbage Collection
We will be using the Intel ORP GC engine as it provides a precise
garbage collector engine, similar to what is available on the
.NET environment.
We have decided to implement a generational tracing garbage
collector, which is very similar to the one being used by
.NET. For an introduction to the garbage collection system
used by Microsoft's CLR implementation, you can read this book
on <a
href="http://www.amazon.com/exec/obidos/ASIN/0471941484/o/qid=992556433/sr=2-1/ref=aps_sr_b_1_1/103-5866388-0492603">Garbage
Collection.</a>
Although using a conservative garbage collector like Bohem's
would work, all the type information is available at runtime,
@@ -103,33 +100,17 @@
* Garbage collection list and FAQ:<br>
<a href="http://www.iecc.com/gclist/">http://www.iecc.com/gclist/</a>
* "GC points in a Threaded Environment":<br>
<a href="http://research.sun.com/techrep/1998/abstract-70.html">
http://research.sun.com/techrep/1998/abstract-70.html</a>
* "A Generational Mostly-concurrent Garbage Collector":
<a href="http://research.sun.com/techrep/2000/abstract-88.html">
http://research.sun.com/techrep/2000/abstract-88.html</a>
* Details on The Microsoft .NET Garbage Collection Implementation:<br>
* The Microsoft .NET Garbage Collection Implementation:<br>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnmag00/html/GCI.asp">http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnmag00/html/GCI.asp</a>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnmag00/html/GCI.asp">http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnmag00/html/GCI.asp</a>
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnmag00/html/GCI2.asp">http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnmag00/html/GCI2.asp</a>
</ul>
** IO and threading
The ECMA runtime and the .NET runtime assume an IO model and a
threading model that is very similar to the Win32 API.
Dick Porter has been working on the Mono abstraction layer
that allows our runtime to execute code that depend on this
behaviour.
** Useful links
Paolo Molaro found a few interesting links:
<ul>
* On compilation of stack-based languages:<br>
<a href="http://www.complang.tuwien.ac.at/projects/rafts.html">
http://www.complang.tuwien.ac.at/projects/rafts.html</a>
@@ -146,8 +127,7 @@
** PInvoke
PInvoke is the mechanism we are using to wrap Unix API calls
as well as talking to system libraries.
Initially we used libffi, but it was fairly slow, so we have
reused parts of the JIT work to create efficient PInvoke trampolines.
PInvoke will be supported, and will be used to wrap Unix API
calls, these in turn are required for reusing some of the
GNOME libraries that will reduce the work we have to do to
deliver a complete class library.
+28 -24
View File
@@ -4,37 +4,41 @@
Pieces of Mono that have been implemented:
<ul>
* C# compiler: The C# compiler is mostly complete, a
few features are still missing (for a list, check the
<a href="c-sharp.html">C# compiler</a> web page.
* C# compiler: The C# parser can now generate parse
trees. Next up: semantic analysis, compiler lever optimizations
and code generation.
* The Mono JIT engine (<b>mono</b>. The JIT engine is
the real
virtual machine that we support. It is
functionaly currently, and we are improving its speed,
and making it feature complete.
* Metadata library: Can currently parse and load
information from .NET modules (executables and DLL
files). It has a few bugs outstanding (table
dimension computation is incorrect).
* A CIL bytecode interpreter (<b>mint</b>). This
currently can be used to run most .NET programs
(modulo the fact that our class libraries are not
complete enough).
Parsing of Exception tables is missing.
<b>mint</b> can currently run the Mono C# compiler and
the compiler generates valid code.
We use <b>mint</b> as a reference implementation of
the runtime environment and to quickly support
non-Intel platforms.
* Metadata library: Can currently parse
and load information from .NET modules (executables
and DLL files).
It lacks Token to (Table, Index) mapping, but this
should be trivial to write.
* Disassembler: Can disassemble .NET modules. Still
lacking exception handling as well as useful debugging
tools (hex dumping, token dumping).
* Class Libraries: You can check the current status in the
<a href="class-status.html">Class Status page</a>.
* Class Libraries: Only a few classes have been
implemented.
</ul>
Tasks on the critical path:
<ul>
* Method and Field resolution.
* Bytecode interpreter: Not implemented yet.
* Simple JIT: Not implemented yet.
* Garbage collection engine.
</ul>
+2 -27
View File
@@ -1,12 +1,4 @@
* Testing
Testing is an important part of the Mono project: every one of its
three major components has a test suite tailored for its needs. This
is very helpful, because in the course of developing the software it
is very common to introduce bugs in existing code. A test suite
helps us fix the bugs as soon as they are introduced.
** Class Library Tests
* Testing
All classes in Mono libraries should have comprehensive unit test
suites to go with them. Unit testing is a software engineering
@@ -25,22 +17,5 @@
be written to demonstrate the bug and its fix. Then, if
you ever reintroduce the bug, you will know immediately. For
more info, read <a
href="http://junit.sourceforge.net/doc/testinfected/testing.htm">
href="http://nunit.sourceforge.net/doc/testinfected/testing.html">
JUnit Test Infected: Programmers Love Writing Tests</a>.
** Getting Started
We welcome all contributions to the Class Libary Test Suite.
There is information to help you get started in CVS at
mcs/class/doc/NUnitGuidelines. Once you have written your test, please
post it to <a href="resources.html#mailing">mono-list</a>.
Someone will make sure to add the file or apply the patch as
appropriate. If you plan to be an on-going contributor and
would like to get cvs account, email <a href="mailto:[email protected]">miguel</a>.
Normally, after you send a couple of well-written new files
and/or patches to the list, you will be given cvs access.
+6 -48
View File
@@ -4,64 +4,22 @@
Mono-based solution. Some of these tools can be developed on
Windows before Mono is fully finished.
All of these tools should be written using C#.
For the tools that are typically command line tools: Try to
write these as components that could load their input from
streams or collections of streams, and implement the command
line tools as wrappers around those classes.
For example, we will be making the C# compiler a component
that could be reused by applications that might have a use for
the various bits of the compiler (either to embed the
compiler, or reuse the code generator part of it).
This is important so that these components (compiler,
assembler, linker, etc) can be integrated later into the
visual development environment (hopefully with the help of the
SharpDevelop hackers).
TODO=ilasm,IL Assembler
** IL Assembler.
This assembler should basically take as input a file
containing IL bytecodes as specified in the `Partition II' of
the ECMA spec, and produce a binary file.
TODO=al,Assembly Linker
** Assembly Linker.
This tool is used to construct assemblies, which are basically
deployment units for CLI executables.
TODO=debugger,Debugger
** Debugger
We will need a debugging API to debug CLI applications and
then a debugger component that can be used in an IDE
environment.
TODO=ide,Integrated Development Environment
** Integrated Development Environment
There is already a project to create a C# development
environment: <a
href="http://www.icsharpcode.net/OpenSource/SD/default.asp">SharpDevelop</a>.
People should work with the SharpDevelop hackers to produce a
unified development environment.
environment (SharpDevelop). People could work with the
SharpDevelop hackers to produce a unified development environment.
Please work with the SharpDevelop hackers to build a good IDE.
We will work on creating an embedable compiler component and
an embeddable debugger component that can be used withing
SharpDevelop
TODO=hbrowser,Help Browser
** Help Browser
We need a good help browser that can be used to browse
documentation. Ideally this help browser can accept as input
XML Docbook input and an assorted set of file formats
(Microsoft Help, Unix manual pages, Unix Info pages)
We need a good help browser that can be used to browse all the
Mono documentation.
Look at the GNOME DevHelp for a good set of ideas on how to
implement this.
+1 -6
View File
@@ -3,19 +3,14 @@
0,Mono,rationale.html,rationale.src
1,Runtime,runtime.html,runtime.src
1,Classes,class-library.html,class-library.src
1,Gtk#,http://gtk-sharp.sourceforge.net
2,Class Status,class-status.html,class-status.src
1,C# Compiler,c-sharp.html,c-sharp.src
1,Status,status.html,status.src
0,Download,download.html,download.src
1,CVS access,ccvs.html,ccvs.src
1,AnonCVS access,anoncvs.html,anoncvs.src
0,Contributing,contributing.html,contributing.src
1,Documentation,documentation.html,documentation.src
1,Class Docs,classlib-doc.html,classlib-doc.src
1,Test Suite,testing.html,testing.src
1,Tools,tools.html,tools.src
1,Porting,porting.html,porting.src
0,Download,download.html,download.src
0,Resources,resources.html,resources.src
1,Ideas,ideas.html,ideas.src
1,Passport,passport.html,passport.src
+2 -4
View File
@@ -14,13 +14,11 @@ while (<>){
} elsif (/^\t\t\* (.*)$/) {
print "<li>$1\n";
} elsif (/^Q: (.*)$/){
print "<p><a name=\"q$q\"></a><b>Question $q:</b> $1\n";
print "<p><a name=\"q$q\"><b>Question $q:</b> $1\n";
$q++;
} elsif (/^A: (.*)$/){
print "$1\n";
} elsif (/^TODO=(.*),$/){
print "<a name=\"$1\">\n";
} else {
} else {
print "$_\n";
}
}
-76
View File
@@ -1,76 +0,0 @@
#!/usr/bin/perl
$q = 1;
# Modified by Edwin Lima ([email protected]; [email protected])
# Date: 08/21/01, The Netherlands
# $f: Variable used as a flag to create the list of questions on top of the question-answers set. This
# is the only way that I found to scan the questions which have a <CR><LF>, in such a way that I will not
# scan the answer together at same time.
# @aname: Buffer used to store the question-answers set to print them out just after the print of the
# questions.
# @href: Buffer used to store the anchors (only questions) to the questions-answers set on the bottom
# of the page.
# I opened explicitly the file for input (input.txt) but U can change this as it was originally.
#
#
#comment this line if you are not open the file explicitly
#open(IN, "input.txt") || die "cannot open file input.txt" ;
print("<A name=TOP>") ;
#Uncomment line bellow to make it work as it was originally.
while (<>){
#comment line bellow
#while (<IN>){
chop;
if (/^\* (.*)$/){
push(@aname,"<h1>$1</h1>\n");
# print $body;
} elsif (/^\*\* (.*)$/) {
push(@aname, "<h2>$1</h2>\n");
push(@href, "<h2>$1</h2>\n");
} elsif (/^\*\*\* (.*)$/) {
push(@aname, "<h3>$1</h3>\n");
} elsif (/^$/) {
push(@aname, "<p>\n");
# push(@href, "<p>\n"); NOT NEEDED
} elsif (/^\t\t\* (.*)$/) {
push(@aname, "<li>$1\n");
} elsif (/^Q: (.*)$/){
push(@aname, "<p><a name=\"q$q\"></a><b>Question $q:</b> $1\n");
push(@href,"<p><a href=\"#q$q\"><b>Question $q:</b></a> $1\n");
$f=1;
$q++;
} elsif (/^A: (.*)$/){
push(@aname,"<P>\n<A HREF=#TOP>Top</A>\n<P>");
push(@aname,"$1\n");
$f=0;
} elsif (/^TODO=(.*),$/){
push(@aname, "<a name=\"$1\">\n");
#push(@href, "<a name=\"$1\">\n");
} else {
push(@aname,"$_\n");
if ($f==1) {
push(@href,"$_\n");
}
}
}
foreach $line (@href) #"\n\n";
{
print $line;
}
foreach $line (@aname) #"\n\n";
{
print $line;
}
#comment this line if you are not open the file explicitly
# close(IN) || die "cannot close file" ;
Binary file not shown.

Before

Width:  |  Height:  |  Size: 3.0 KiB

After

Width:  |  Height:  |  Size: 3.3 KiB

+2 -10
View File
@@ -1,15 +1,9 @@
# Until we are ready:
# ../class-library \
SOURCES= \
../anoncvs \
../contributing \
../class-status \
../class-library \
../classlib-doc \
../class-status \
../contact \
../c-sharp \
../ccvs \
../documentation \
../download \
../faq \
@@ -23,7 +17,6 @@ SOURCES= \
../runtime \
../status \
../testing \
../porting \
../tools
all:
@@ -40,8 +33,7 @@ clean:
done;
push:
scp -P 2200 *.html [email protected]:/web/cvsmodules/mono
echo scp *.html [email protected]:/home/groups/m/mo/mononet/htdocs
scp *.html [email protected]:/web/cvsmodules/mono
push2:
scp *.html primates:public_html/xxx
+25 -27
View File
@@ -44,32 +44,30 @@ while (<COMMANDS>) {
chop;
my @command = split /,/;
if ($command[2] =~ /^http:/){
} else {
$n = $ARGV[2] . "/" . $command[2];
open OUTPUT, ">" . $n || die "Can not create $n";
my $content = "";
open INPUT, $command[3] || die "Can not open $command[3]";
while (<INPUT>) {
$content .= $_;
}
close INPUT;
my $line;
my $temp;
my $tit;
my $title;
$tit = $command[1];
foreach $line (@template) {
$temp = $line;
$title = "$tit / Mono";
$temp =~ s/#TITLE#/$title/;
$temp =~ s/#CONTENT#/$content/;
$temp =~ s/#MENU#/$menu/;
print OUTPUT $temp;
}
}
$n = $ARGV[2] . "/" . $command[2];
open OUTPUT, ">" . $n || die "Can not create $n";
my $content = "";
open INPUT, $command[3] || die "Can not open $command[3]";
while (<INPUT>) {
$content .= $_;
}
close INPUT;
my $line;
my $temp;
my $tit;
my $title;
$tit = $command[1];
foreach $line (@template) {
$temp = $line;
$title = "$tit / Mono";
$temp =~ s/#TITLE#/$title/;
$temp =~ s/#CONTENT#/$content/;
$temp =~ s/#MENU#/$menu/;
print OUTPUT $temp;
}
close OUTPUT;
}
+3 -3
View File
@@ -30,7 +30,7 @@
<tr>
<td><img src="images/pixel.gif"></td><!-- left border -->
<td colspan="4">
<a href="http://www.go-mono.com"><img src="images/mono.gif" border="0"></a></td>
<a href="/"><img src="images/mono.gif" border="0"></a></td>
<td><img src="images/pixel.gif"></td><!-- right border -->
</tr>
<tr>
@@ -47,13 +47,13 @@
</table>
</td>
<td bgcolor="black" width="1"><img src="images/pixel.gif" width="1"></td>
<td bgcolor="white" align="left" width="80%" valign="top">
<td bgcolor="white">
<table cellpadding="16">
<tr><td>
#CONTENT#
</td></tr>
</table>
</td>
</td>
<td bgcolor="black"><img src="images/pixel.gif" width="1"></td>
<td width="100"><img src="images/pixel.gif"></td>
</tr>
-54
View File
@@ -1,54 +0,0 @@
Exception implementation (jit):
===============================
Stack unwinding:
================
We record the code address (start_address, size) of all methods. That way it is
possible to map an instruction pointer (IP) to the method information needed
for unwinding the stack:
void handle_exception ((struct sigcontext *ctx, gpointer obj)
{
info = mono_jit_info_table_find (mono_jit_info_table, ctx->ip);
if (info) { // we are inside managed code
if (ch = find_catch_handler ())
execute_catch_handler (ch, ctx, obj);
execute_all_finally_handler ();
// restore register, including IP and Frame pointer
restore_caller_saved_registers (ji, ctx);
// continue unwinding
handle_exception (ctx, obj);
} else {
// not implemented
}
}
Code generation:
================
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: 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 (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.
-47
View File
@@ -1,47 +0,0 @@
How to use the debug support in the jit.
----------------------------------------
You need to run mono inside gdb. The following command line swicthes
are available:
--stabs
--debug methodName
--stabs will create an assemblyname-stabs.s file for each assembly the
CLR program uses. Note that to properly display source code lines,
you need to disassemble the CLR executables with monodis before running
mono. Each IL assembly file needs to have the name <assemblyname>.il.
--debug methodName will insert a breakpoin at the beginning of
methodName's code, so that control is trasnfered to the debugger as soon
as it is entered. You may use this switch multiple times.
So, suppose you use the --debug switch, or hit a segfault inside a
jitted method. In a shell you need to compile the stab information
created with the --stabs option with the assembler:
as assemblyname-stabs.s -o assemblyname-stabs.o
Now, inside gdb, you can load the debug information with:
add-symbol-file assemblyname-stabs.o 0
And at this point the debugger should be able to print a correct
backtrace, you should be able to inspect method parameters and local
variables, disassemble methods and step through the code.
Note that apparently you can't unload a symbol file from gdb, so you
need to restart it if you restart the program to debug.
Name mangling.
-------------
Currently CLR methods are exposed as C functions, so, if they are not
static, their first argument will be called 'this'.
Method names are mangled in the following way: a long name is created
concatting namespace, class name and method name. '.' chars are changed
to underscaore '_'. To allow for overloading, the address of the
MonoMethod from wich the method was created is appended to the end of
the name (i's also handy since you can use the address in gdb to inspect
the MonoMethod).
-182
View File
@@ -1,182 +0,0 @@
Just some thoughts for the JITer:
General issues:
===============
We are designing a JIT compiler, so we have to consider two things:
- the quality of the generated code
- the time needed to generate that code
The current approach is to keep the JITer as simple as possible, and thus as
fast as possible. The generated code quality will suffer from that.
Register allocation is first done inside the trees of the forest, and each
tree can use the full set of registers. We simply split a tree if we get out of
registers, for example the following tree:
add(R0)
/ \
/ \
a(R0) add(R1)
/ \
/ \
b(R1) add(R2)
/ \
/ \
c(R2) b(R3)
can be transformed to:
stloc(t1) add(R0)
| / \
| / \
add(R0) a(R0) add(R1)
/ \ / \
/ \ / \
c(R0) b(R1) b(R1) t1(R2)
Please notice that the split trees use less registers than the original
tree.
Triggering JIT compilation:
===========================
The current approach is to call functions indirectly. The address to call is
stored in the MonoMethod structure. For each method we create a trampoline
function. When called, this function does the JIT compilation and replaces the
trampoline with the compiled method address.
We should consider using the CACAO approach, they do not use a trampoline at
all.
Register Allocation:
====================
With lcc you can assign a fixed register to a tree before register
allocation. For example this is needed by call, which return the value always
in EAX on x86. The current implementation works without such system, due to
special forest generation.
X86 Register Allocation:
========================
We can use 8bit or 16bit registers on the x86. If we use that feature we have
more registers to allocate, which maybe prevents some register spills. We
currently ignore that ability and always allocate 32 bit registers, because I
think we would gain very little from that optimisation and it would complicate
the code.
Different Register Sets:
========================
Most processors have more that one register set, at least one for floating
point values, and one for integers. Should we support architectures with more
that two sets? Does someone knows such an architecture?
64bit Integer Values:
=====================
I can imagine two different implementation. On possibility would be to treat
long (64bit) values simply like any other value type. This implies that we
call class methods for ALU operations like add or sub. Sure, this method will
be be a bit inefficient.
The more performant solution is to allocate two 32bit registers for each 64bit
value. We add a new non terminal to the monoburg grammar called long_reg. The
register allocation routines takes care of this non terminal and allocates two
32 bit registers for them.
Forest generation:
==================
Consider the following code:
OPCODE: STACK LOCALS
LDLOC.0 (5) [5,0]
LDC.1 (5,1) [5,0]
STLOC.0 (5) [1,0]
STLOC.1 () [1,5]
The current forest generation generates:
STLOC.0(LDC.1)
STLOC.1(LDLOC.0)
Which is wrong, since it stores the wrong value (1 instead of 5). Instead we
must generate something like:
STLOC.TMP(LDLOC.0)
STLOC.0(LDC.1)
STLOC.1(LDLOC.TMP)
Where STLOC.TMP saves the value into a new temporary variable.
We also need a similar solution for basic block boundaries when the stack depth
is not zero. We can simply save those values to new temporary values. Consider
the following basic block with one instruction:
LDLOC.1
This should generate a tree like:
STLOC.TMP(LDLOC.1) Please notice that an intelligent register allocator can
still allocate registers for those new variables.
DAG handling:
=============
Monoburg can't handle DAGs, instead we need real trees as input for
the code generator. So we have two problems:
1.) DUP instruction: This one is obvious - we need to store the value
into a temporary variable to solve the problem.
2.) function calls: Chapter 12.8, page 343 of "A retargetable C compiler"
explains that: "because listing a call node will give it a hidden reference
from the code list". I don't understand that (can someone explain that?), but
there is another reason to save return values to temporaries: Consider the
following code:
x = f(y) + g(z); // all functions return integers
We could generate such a tree for this expression: STLOC(ADD(CALL,CALL))
The problem is that both calls returns the value in the same register,
so it is non trivial to generate code for that tree. We must copy one
register into another one, which make register allocation more complex.
The easier solution is store the result of function calls to
temporaries. This leads to the following forest:
STLOC(CALL)
STLOC(CALL)
STLOC(ADD (LDLOC, LDLOC))
This is what lcc is doing, if I understood 12.8, page 342, 343?
Value Types:
============
The only CLI instructions which can handle value types are loads and stores,
either to local variable, to the stack or to array elements. Value types with a
size smaller than sizeof(int) are handled like any other basic type. For other
value types we load the base address and emit block copies to store them.
Possible Optimisations:
=======================
Miguel said ORP does some optimisation on IL level, for example moving array
bounds checking out of loops:
for (i = 0; i < N; i++) { check_range (a, i); a [i] = X; }
id transformed to:
if (in_range (a, 0, N)) { for (i = 0; i < N; i++) a[i] = X; }
else for (i = 0; i < N; i++) { check_range (a, i); a [i] = X; }
The "else" is only to keep original semantics (exception handling).
-58
View File
@@ -1,58 +0,0 @@
Object and VTable layout
========================
The first pointer inside an Object points to a MonoClass structure. Objects
also contains a MonoThreadsSync structure which is used by the mono Thread
implementation.
typedef struct {
MonoClass *class;
MonoThreadsSync synchronisation;
/* object specific data goes here */
} MonoObject;
The MonoClass contains all Class infos, the VTable and a pointer to static
class data.
typedef struct {
/* various class infos */
MonoClass *parent;
const char *name;
const char *name_space;
...
/* interface offset table */
gint *interface_offsets;
gpointer data; /* a pointer to static data */
/* the variable sized vtable is included at the end */
gpointer vtable [vtable_size];
} MonoClass;
Calling virtual functions:
==========================
Each MonoMethod (if virtual) has an associated slot, which is an index into the
VTable. So we can use the following code to compute the address of a virtual
function:
method_addr = object->class->vtable [method->slot];
Calling interface methods:
==========================
Each interface class is associated with an unique ID. The following code
computes the address of an interface function:
offset_into_vtable = object->class->interface_offsets [interface_id];
method_addr = object->class->vtable [offset_into_vtable + method->slot];
-2
View File
@@ -1,2 +0,0 @@
Makefile
Makefile.in
-4
View File
@@ -1,4 +0,0 @@
man_MANS = mcs.1
EXTRA_DIST = $(man_MANS)
-118
View File
@@ -1,118 +0,0 @@
.TH mcs 1 "6 January 2001"
.SH NAME
mcs \- Mono Compiler Suite.
.SH SYNOPSIS
.B mcs
[option] [source-files]
.SH DESCRIPTION
mcs is the Mono C# compiler, an implementation of the ECMA-334
specification. You can pass one or more options to drive the
compiler, and a set of source files. Extra options or arguments can
be provided in a response file. Response files are referenced by
prepending the @ symbol to the response file name.
.PP
C# source files must end with a ".cs" extension. Compilation of C#
source code requires all the files that make up a library, module or
executable to be provided on the command line. There is no support
for partial compilation. To achieve the benefits of partial
compilation, you should compile programs into their own assemblies,
and later reference them with the "-r" flag.
.PP
The Mono C# compiler generates images (.exe files) that contain CIL
byte code that can be executed by any system that implements a Common
Language Infrastructure virtual machine such as the Microsoft .NET
runtime engine on Windows or the Mono runtime engine on Unix systems.
Executables are not bound to a specific CPU or operating system.
.PP
.SH OPTIONS
.TP
.I \-\-about
Displays information about the Mono C# compiler
.TP
.I \-\-checked
Sets the default compilation mode to `checked'. This makes all
the math operations checked (the default is unchecked).
.TP
.I \-\-define SYMBOL
Defines a symbol named SYMBOL. This can be tested in the source code
by the pre-processor.
.TP
.I \-\-fatal
This is used for debugging the compiler. This makes the error emission
generate an exception that can be caught by a debugger.
.TP
.I \-\-stacktrace
Generates a stack trace at the time the error is reported, useful for
debugging the compiler.
.TP
.I \-L PATH
Directs the compiler to look for libraries in the specified path.
Multiple paths can be provided.
.TP
.I \-\-nostdlib
Use this flag if you want to compile the core library. This makes the
compiler load its internal types from the assembly being compiled.
.TP
.I \-\-nowarn XXX
Makes the compiler ignore warning XXX.
.TP
.I \-o FNAME
Names the output file to be generated.
.TP
.I \-\-optimize
Turns on optimizations in the compiler.
.TP
.I \-\-parse
Used for benchmarking. The compiler will only parse its input files.
.TP
.I \-\-probe X L
Probes for the code to generate an error named `X' in line `L'. This
is only used by the test suite.
.TP
.I \-\-target KIND
Used to specify the desired target. The possible values are: exe,
winexe, library and module.
.TP
.I \-\-timestamp
Another debugging flag. Used to display the times at various points
in the compilation process.
.TP
.I \-\-unsafe
Enables compilation of unsafe code.
.TP
.I \-\-werror
Treat warnings as errors.
.TP
.I \-\-wlevel LEVEL
Sets the warning level. 0 is the lowest warning level, and 4 is the
highest. The default is 2.
.TP
.I \-r ASSEMBLY
Reference the named assembly. Use this to use classes from the named
assembly in your program.
.TP
.I \-v
Debugging. Turns on verbose yacc parsing.
.PP
.SH AUTHORS
The Mono C# Compiler was written by Miguel de Icaza and Ravi Pratap at
Ximian.
.PP
.SH LICENSE
The Mono Compiler Suite is released under the terms of the GNU GPL.
Please read the accompanying `COPYING' file for details. Alternative
licenses are available from Ximian.
.PP
.SH BUGS
To report bugs in the compiler, you can use `bug-buddy', or you can
file bug reports in our bug tracking system:
http://bugzilla.ximian.com.
.SH MAILING LIST
The Mono Mailing List is available at: [email protected]
.SH MORE INFORMATION
The Mono C# compiler is developed by Ximian, Inc
(http://www.ximian.com) (http://www.ximian.com) and is based on the
ECMA C# language standard available here:
http://www.ecma.ch/ecma1/STAND/ecma-334.htm
-4
View File
@@ -2,12 +2,8 @@ C# Compiler:
Miguel de Icaza ([email protected])
Class Libraries:
Gaurav Vaish <[email protected]>
Jeff Stedfast ([email protected])
Joe Shaw ([email protected])
Miguel de Icaza ([email protected])
Sean MacIsaac ([email protected])
Vladimir Vukicevic ([email protected])
Garrett Rooney ([email protected])
Bob Smith ([email protected])
John Barnette ([email protected])
-8
View File
@@ -1,8 +0,0 @@
2002-01-20 Nick Drochak <[email protected]>
* on the 'test' target, make sure NUnit is built first before building
and running tests
2002-01-20 Nick Drochak <[email protected]>
* add nunit directory to the list of dirs to build in
+1 -22
View File
@@ -1,23 +1,2 @@
This contains the Mono C# compiler as well as the Mono runtime
library.
Layout:
class/
Class libraries
errors/
Sample programs that should generate errors by the compiler.
jay/
Yacc-based parser generator.
mcs/
The Mono C# compiler
tests/
Sample tests
Thanks a lot to Sergey Chaban for his help during the development of
the C# compiler.
This is the Ximian MCS C# compiler written in C#
-1
View File
@@ -1 +0,0 @@
lib
-36
View File
@@ -3,28 +3,6 @@ The class libraries are grouped together in the assemblies they belong.
Each directory here represents an assembly, and inside each directory we
divide the code based on the namespace they implement.
In addition, each assembly directory contains a Test directory that holds the
NUnit tests for that assembly.
The nant build file for an assembly creates two versions of the dll for that
assembly. One version is a "full" dll. The full dll contains (almost) all
of the classes, regardless of how complete the classes are. The name of this
dll is the normal name you would expect, like "corlib.dll" or "System.dll".
These full dll's are created in the /mcs/class/lib directory.
The other dll which is built is a "restricted" dll. The restricted dll
omits incomplete classes that would prevent the NUnit testrunner from actually
running the tests. These restricted dll's are created in the Test directory
of their respective assembly and named with a "_res" suffix. So, for example,
the NUnit-testable dll for corlib is /mcs/class/corlib/Test/corlib_res.dll.
The final dll which is built is the one which houses the actual NUnit tests.
This dll is built from all of the classes in the Test directory and below, and
is named with a "_test" suffix. So, for example, the NUnit tests for corlib
are in /mcs/class/corlib/Test/corlib_test.dll. This dll is also linked with
the restricted dll found in the same directory.
* Missing implementation bits
If you implement a class and you are missing implementation bits,
@@ -54,17 +32,3 @@ the restricted dll found in the same directory.
this consistent). If you are modifying someone else's code, try
to keep the coding style similar.
Please use code that looks like this:
bool Method (int argument_1, int argument_2)
{
if (argument_1 == argument_2)
throw new Exception (Locale.GetText ("They are equal!");
if (argument_1 < argument_2) {
if (argument_1 * 3 > 4)
return true;
else
return false;
}
}
-9
View File
@@ -1,9 +0,0 @@
2002-02-10 Christopher Podurgiel <[email protected]>
* Removed *.cs from System.Data as the correct files are in mcs/class/System.Data/System.Data
* Updated all Enums, Interfaces, and Delegates in System.Data
2002-02-11 Christopher Podurgiel <[email protected]>
* DataColumnChangeEventArgs.cs : Added
* DataColumnChangeEventHandler.cs : Added
-24
View File
@@ -1,24 +0,0 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!-- NAnt build file for System.Data.dll -->
<project name="System.Data" default="build">
<property name="debug" value="false"/>
<target name="build">
<csc target="library" output="../lib/System.Data.dll" debug="${debug}">
<arg value="/nowarn:1595"/>
<arg value="/unsafe"/>
<sources>
<includes name="**/*.cs"/>
<excludes name="Test/**"/>
</sources>
<references>
<includes name="../lib/corlib.dll"/>
</references>
</csc>
</target>
<target name="clean">
<delete file="../lib/System.Data.dll" failonerror="false"/>
</target>
</project>
@@ -1,23 +0,0 @@
//
// System.Data.AcceptRejectRule.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
namespace System.Data
{
/// <summary>
/// Determines the action that occurs when the AcceptChanges or RejectChanges method is invoked on a DataTable with a ForeignKeyConstraint.
/// </summary>
[Serializable]
public enum AcceptRejectRule
{
Cascade = 1,
None = 0
}
}
@@ -1,30 +0,0 @@
//
// System.Data.CommandBehavior.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
namespace System.Data
{
/// <summary>
/// Specifies a description of the results and the affect on the database of the query command.
/// This enumeration has a FlagsAttribute that allows a bitwise combination of its member values.
/// </summary>
[Flags]
[Serializable]
public enum CommandBehavior
{
Default = 0,
SingleResult = 1,
SchemaOnly = 2,
KeyInfo = 4,
SingleRow = 8,
SequentialAccess = 16,
CloseConnection = 32
}
}
@@ -1,25 +0,0 @@
//
// System.Data.CommandType.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
using System;
namespace mono.System.Data
{
/// <summary>
/// Specifies how a command string is interpreted.
/// </summary>
[Serializable]
public enum CommandType
{
Text = 1,
StoredProcedure = 4,
TableDirect = 512
}
}
@@ -1,30 +0,0 @@
//
// System.Data.ConnectionState.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
using System;
namespace mono.System.Data
{
/// <summary>
/// Returns the current state of the connection to a data source.
/// This enumeration has a FlagsAttribute that allows a bitwise combination of its member values.
/// </summary>
[Flags]
[Serializable]
public enum ConnectionState
{
Closed = 0,
Open = 1,
Connecting = 2,
Executing = 4,
Fetching = 8,
Broken = 16
}
}
@@ -1,80 +0,0 @@
//
// System.Data.DataColumnChangeEventArgs.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
using System;
namespace System.Data
{
/// <summary>
/// Provides data for the ColumnChanging event.
/// </summary>
public class DataColumnChangeEventArgs : EventArgs
{
private DataColumn _column = null;
private DataRow _row = null;
private object _proposedValue = null;
/// <summary>
/// Initializes a new instance of the DataColumnChangeEventArgs class.
/// </summary>
/// <param name="row"></param>
/// <param name="column"></param>
/// <param name="value"></param>
public DataColumnChangeEventArgs(DataRow row, DataColumn column, object value)
{
_column = column;
_row = row;
_proposedValue = value;
}
/// <summary>
/// Gets the DataColumn with a changing value.
/// </summary>
public DataColumn Column
{
get
{
return _column;
}
}
/// <summary>
/// Gets or sets the proposed new value for the column.
/// </summary>
public object ProposedValue
{
get
{
return _proposedValue;
}
set
{
_proposedValue = value;
}
}
/// <summary>
/// Gets the DataRow of the column with a changing value.
/// </summary>
public DataRow Row
{
get
{
return _row;
}
}
}
}
@@ -1,18 +0,0 @@
//
// System.Data.DataColumnChangeEventHandler.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
namespace System.Data
{
/// <summary>
/// Represents the method that will handle the the ColumnChanging event.
/// </summary>
[Serializable]
public delegate void DataColumnChangeEventHandler(object sender, DataColumnChangeEventArgs e);
}
@@ -1,413 +0,0 @@
//
// System.Data.DataColumnCollection.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
using System;
using System.Collections;
using System.ComponentModel;
namespace System.Data
{
/// <summary>
/// Represents a collection of DataColumn objects for a DataTable.
/// </summary>
public class DataColumnCollection : InternalDataCollectionBase
{
protected ArrayList list = null;
// The defaultNameIndex is used to create a default name for a column if one wasn't given.
private int defaultNameIndex;
//table should be the DataTable this DataColumnCollection belongs to.
private DataTable parentTable = null;
// Internal Constructor. This Class can only be created from other classes in this assembly.
internal DataColumnCollection(DataTable table):base()
{
list = new ArrayList();
defaultNameIndex = 1;
parentTable = table;
}
/// <summary>
/// Gets the DataColumn from the collection at the specified index.
/// </summary>
public virtual DataColumn this[int index]
{
get
{
return (DataColumn)list[index];
}
}
/// <summary>
/// Gets the DataColumn from the collection with the specified name.
/// </summary>
public virtual DataColumn this[string name]
{
get
{
foreach (DataColumn column in list)
{
if (column.ColumnName == name)
{
return column;
}
}
return null;
}
}
/// <summary>
/// Gets a list of the DataColumnCollection items.
/// </summary>
protected override ArrayList List
{
get
{
return list;
}
}
/// <summary>
/// Creates and adds a DataColumn object to the DataColumnCollection.
/// </summary>
/// <returns></returns>
public virtual DataColumn Add()
{
DataColumn column = new DataColumn("Column" + defaultNameIndex.ToString());
CollectionChangeEventArgs e = new CollectionChangeEventArgs(CollectionChangeAction.Add, this);
list.Add(column);
OnCollectionChanged(e);
defaultNameIndex++;
return column;
}
/// <summary>
/// Creates and adds the specified DataColumn object to the DataColumnCollection.
/// </summary>
/// <param name="column">The DataColumn to add.</param>
public void Add(DataColumn column)
{
if(Contains(column.ColumnName))
{
throw new DuplicateNameException("A column named " + column.ColumnName + " already belongs to this DataTable.");
}
else
{
CollectionChangeEventArgs e = new CollectionChangeEventArgs(CollectionChangeAction.Add, this);
list.Add(column);
OnCollectionChanged(e);
return;
}
}
/// <summary>
/// Creates and adds a DataColumn object with the specified name to the DataColumnCollection.
/// </summary>
/// <param name="columnName">The name of the column.</param>
/// <returns>The newly created DataColumn.</returns>
public virtual DataColumn Add(string columnName)
{
if (columnName == null || columnName == String.Empty)
{
columnName = "Column" + defaultNameIndex.ToString();
defaultNameIndex++;
}
if(Contains(columnName))
{
throw new DuplicateNameException("A column named " + columnName + " already belongs to this DataTable.");
}
else
{
DataColumn column = new DataColumn(columnName);
CollectionChangeEventArgs e = new CollectionChangeEventArgs(CollectionChangeAction.Add, this);
list.Add(column);
OnCollectionChanged(e);
return column;
}
}
/// <summary>
/// Creates and adds a DataColumn object with the specified name and type to the DataColumnCollection.
/// </summary>
/// <param name="columnName">The ColumnName to use when cretaing the column.</param>
/// <param name="type">The DataType of the new column.</param>
/// <returns>The newly created DataColumn.</returns>
public virtual DataColumn Add(string columnName, Type type)
{
if (columnName == null || columnName == "")
{
columnName = "Column" + defaultNameIndex.ToString();
defaultNameIndex++;
}
if(Contains(columnName))
{
throw new DuplicateNameException("A column named " + columnName + " already belongs to this DataTable.");
}
else
{
DataColumn column = new DataColumn(columnName, type);
CollectionChangeEventArgs e = new CollectionChangeEventArgs(CollectionChangeAction.Add, this);
list.Add(column);
OnCollectionChanged(e);
return column;
}
}
/// <summary>
/// Creates and adds a DataColumn object with the specified name, type, and expression to the DataColumnCollection.
/// </summary>
/// <param name="columnName">The name to use when creating the column.</param>
/// <param name="type">The DataType of the new column.</param>
/// <param name="expression">The expression to assign to the Expression property.</param>
/// <returns>The newly created DataColumn.</returns>
public virtual DataColumn Add(string columnName, Type type, string expression)
{
if (columnName == null || columnName == "")
{
columnName = "Column" + defaultNameIndex.ToString();
defaultNameIndex++;
}
if(Contains(columnName))
{
throw new DuplicateNameException("A column named " + columnName + " already belongs to this DataTable.");
}
else
{
DataColumn column = new DataColumn(columnName, type, expression);
CollectionChangeEventArgs e = new CollectionChangeEventArgs(CollectionChangeAction.Add, this);
list.Add(column);
OnCollectionChanged(e);
return column;
}
}
/// <summary>
/// Copies the elements of the specified DataColumn array to the end of the collection.
/// </summary>
/// <param name="columns">The array of DataColumn objects to add to the collection.</param>
public void AddRange(DataColumn[] columns)
{
foreach (DataColumn column in columns)
{
Add(column);
}
return;
}
/// <summary>
/// Checks whether a given column can be removed from the collection.
/// </summary>
/// <param name="column">A DataColumn in the collection.</param>
/// <returns>true if the column can be removed; otherwise, false.</returns>
public bool CanRemove(DataColumn column)
{
//Check that the column does not have a null reference.
if (column == null)
{
return false;
}
//Check that the column is part of this collection.
if (!Contains(column.ColumnName))
{
return false;
}
//Check if this column is part of a relationship. (this could probably be written better)
foreach (DataRelation childRelation in parentTable.ChildRelations)
{
foreach (DataColumn childColumn in childRelation.ChildColumns)
{
if (childColumn == column)
{
return false;
}
}
foreach (DataColumn parentColumn in childRelation.ParentColumns)
{
if (parentColumn == column)
{
return false;
}
}
}
//Check if this column is part of a relationship. (this could probably be written better)
foreach (DataRelation parentRelation in parentTable.ParentRelations)
{
foreach (DataColumn childColumn in parentRelation.ChildColumns)
{
if (childColumn == column)
{
return false;
}
}
foreach (DataColumn parentColumn in parentRelation.ParentColumns)
{
if (parentColumn == column)
{
return false;
}
}
}
//Check if another column's expression depends on this column.
foreach (DataColumn dataColumn in list)
{
if (dataColumn.Expression.ToString().IndexOf(column.ColumnName) > 0)
{
return false;
}
}
return true;
}
/// <summary>
/// Clears the collection of any columns.
/// </summary>
public void Clear()
{
CollectionChangeEventArgs e = new CollectionChangeEventArgs(CollectionChangeAction.Refresh, this);
list.Clear();
OnCollectionChanged(e);
return;
}
/// <summary>
/// Checks whether the collection contains a column with the specified name.
/// </summary>
/// <param name="name">The ColumnName of the column to check for.</param>
/// <returns>true if a column exists with this name; otherwise, false.</returns>
public bool Contains(string name)
{
return (IndexOf(name) != -1);
}
/// <summary>
/// Gets the index of a column specified by name.
/// </summary>
/// <param name="column">The name of the column to return.</param>
/// <returns>The index of the column specified by column if it is found; otherwise, -1.</returns>
public virtual int IndexOf(DataColumn column)
{
return list.IndexOf(column);
}
/// <summary>
/// Gets the index of the column with the given name (the name is not case sensitive).
/// </summary>
/// <param name="columnName">The name of the column to find.</param>
/// <returns>The zero-based index of the column with the specified name, or -1 if the column doesn't exist in the collection.</returns>
public int IndexOf(string columnName)
{
DataColumn column = this[columnName];
if (column != null)
{
return IndexOf(column);
}
else
{
return -1;
}
}
/// <summary>
/// Raises the OnCollectionChanged event.
/// </summary>
/// <param name="ccevent">A CollectionChangeEventArgs that contains the event data.</param>
protected virtual void OnCollectionChanged(CollectionChangeEventArgs ccevent)
{
if (CollectionChanged != null)
{
// Invokes the delegate.
CollectionChanged(this, ccevent);
}
}
/// <summary>
/// Raises the OnCollectionChanging event.
/// </summary>
/// <param name="ccevent">A CollectionChangeEventArgs that contains the event data.</param>
protected internal virtual void OnCollectionChanging(CollectionChangeEventArgs ccevent)
{
if (CollectionChanged != null)
{
// Invokes the delegate.
CollectionChanged(this, ccevent);
}
}
/// <summary>
/// Removes the specified DataColumn object from the collection.
/// </summary>
/// <param name="column">The DataColumn to remove.</param>
public void Remove(DataColumn column)
{
CollectionChangeEventArgs e = new CollectionChangeEventArgs(CollectionChangeAction.Remove, this);
list.Remove(column);
OnCollectionChanged(e);
return;
}
/// <summary>
/// Removes the DataColumn object with the specified name from the collection.
/// </summary>
/// <param name="name">The name of the column to remove.</param>
public void Remove(string name)
{
DataColumn column = this[name];
CollectionChangeEventArgs e = new CollectionChangeEventArgs(CollectionChangeAction.Remove, this);
list.Remove(column);
OnCollectionChanged(e);
return;
}
/// <summary>
/// Removes the column at the specified index from the collection.
/// </summary>
/// <param name="index">The index of the column to remove.</param>
public void RemoveAt(int index)
{
CollectionChangeEventArgs e = new CollectionChangeEventArgs(CollectionChangeAction.Remove, this);
list.RemoveAt(index);
OnCollectionChanged(e);
return;
}
/// <summary>
/// Occurs when the columns collection changes, either by adding or removing a column.
/// </summary>
public event CollectionChangeEventHandler CollectionChanged;
}
}
@@ -1,28 +0,0 @@
//
// System.Data.DataRowAction.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
namespace System.Data
{
/// <summary>
/// Describes the action taken on a DataRow.
/// This enumeration has a FlagsAttribute that allows a bitwise combination of its member values.
/// </summary>
[Flags]
[Serializable]
public enum DataRowAction
{
Nothing = 0,
Delete = 1,
Change = 2,
Rollback = 4,
Commit = 8,
Add = 16
}
}
@@ -1,18 +0,0 @@
//
// System.Data.DataRowChangeEventHandler.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
namespace System.Data
{
/// <summary>
/// Represents the method that will handle the RowChanging, RowChanged, RowDeleting, and RowDeleted events of a DataTable.
/// </summary>
[Serializable]
public delegate void DataRowChangeEventHandler(object sender, DataRowChangeEventArgs e);
}
@@ -1,26 +0,0 @@
//
// System.Data.DataRowState.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
namespace System.Data
{
/// <summary>
/// Gets the state of a DataRow object.
/// </summary>
[Flags]
[Serializable]
public enum DataRowState
{
Detached = 1,
Unchanged = 2,
Added = 4,
Deleted = 8,
Modified = 16
}
}
@@ -1,23 +0,0 @@
//
// System.Data.DataRowVersion.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
namespace System.Data
{
/// <summary>
/// Describes the version of a DataRow.
/// </summary>
[Serializable]
public enum DataRowVersion
{
Original = 256,
Current = 512,
Proposed = 1024,
Default = 1536
}
}
@@ -1,29 +0,0 @@
//
// System.Data.DataViewRowState.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
namespace System.Data
{
/// <summary>
/// Describes the version of data in a DataRow.
/// This enumeration has a FlagsAttribute that allows a bitwise combination of its member values.
/// </summary>
[Flags]
[Serializable]
public enum DataViewRowState
{
None = 0,
Unchanged = 2,
Added = 4,
Deleted = 8,
ModifiedCurrent = 16,
CurrentRows = 22,
ModifiedOriginal = 32,
OriginalRows = 42
}
}
@@ -1,44 +0,0 @@
//
// System.Data.DbType.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
namespace System.Data
{
/// <summary>
/// Gets the data type of a field, a property, or a Parameter object of a .NET data provider.
/// </summary>
[Serializable]
public enum DbType
{
AnsiString = 0,
Binary = 1,
Byte = 2,
Boolean = 3,
Currency = 4,
Date = 5,
DateTime = 6,
Decimal = 7,
Double = 8,
Guid = 9,
Int16 = 10,
Int32 = 11,
Int64 = 12,
Object = 13,
SByte = 14,
Single = 15,
String = 16,
Time = 17,
UInt16 = 18,
UInt32 = 19,
UInt64 = 20,
VarNumeric = 21,
AnsiStringFixedLength = 22,
StringFixedLength = 23
}
}
@@ -1,18 +0,0 @@
//
// System.Data.FillErrorEventHandler.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
namespace System.Data
{
/// <summary>
/// Represents the method that will handle the FillError event.
/// </summary>
[Serializable]
public delegate void FillErrorEventHandler(object sender, FillErrorEventArgs e);
}
@@ -1,35 +0,0 @@
//
// System.Data.IColumnMapping.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
namespace System.Data
{
/// <summary>
/// Associates a data source column with a DataSet column, and is implemented by the DataColumnMapping class, which is used in common by .NET data providers.
/// </summary>
public interface IColumnMapping
{
/// <summary>
/// Gets or sets the name of the column within the DataSet to map to.
/// </summary>
string DataSetColumn
{
get;
set;
}
/// <summary>
/// Gets or sets the name of the column within the data source to map from. The name is case-sensitive.
/// </summary>
string SourceColumn
{
get;
set;
}
}
}
@@ -1,35 +0,0 @@
//
// System.Data.IColumnMappingCollection.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
using System.Collections;
namespace System.Data
{
/// <summary>
/// Contains a collection of ColumnMapping objects, and is implemented by the DataColumnMappingCollection, which is used in common by .NET data providers.
/// </summary>
public interface IColumnMappingCollection : IList, ICollection, IEnumerable
{
IColumnMapping Add(string sourceColumnName, string dataSetColumnName);
bool Contains(string sourceColumnName);
IColumnMapping GetByDataSetColumn(string dataSetColumnName);
int IndexOf(string sourceColumnName);
void RemoveAt(string sourceColumnName);
object this[string index]
{
get;
set;
}
}
}
@@ -1,33 +0,0 @@
//
// System.Data.IDataAdapter.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
namespace System.Data
{
/// <summary>
/// Allows an object to implement a DataAdapter, and represents a set of methods and mapping action-related properties used to fill and refresh a DataSet and update a data source.
/// </summary>
public interface IDataAdapter
{
int Fill(DataSet dataSet);
DataTable[] FillSchema(DataSet dataSet, SchemaType schemaType);
IDataParameter[] GetFillParameters();
int Update(DataSet dataSet);
MissingMappingAction MissingMappingAction{get;set;}
MissingSchemaAction MissingSchemaAction{get;set;}
ITableMappingCollection TableMappings{get;}
}
}
@@ -1,34 +0,0 @@
//
// System.Data.IDataParameter.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
namespace System.Data
{
/// <summary>
/// Represents a parameter to a Command object, and optionally, its mapping to DataSet columns; and is implemented by .NET data providers that access data sources.
/// </summary>
public interface IDataParameter
{
DbType DbType{get;set;}
ParameterDirection Direction{get;set;}
bool IsNullable{get;}
string ParameterName{get;set;}
string SourceColumn{get;set;}
DataRowVersion SourceVersion {get;set;}
object Value {get;set;}
}
}
@@ -1,27 +0,0 @@
//
// System.Data.IDataParameterCollection.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
using System.Collections;
namespace System.Data
{
/// <summary>
/// Collects all parameters relevant to a Command object and their mappings to DataSet columns, and is implemented by .NET data providers that access data sources.
/// </summary>
public interface IDataParameterCollection : IList, ICollection, IEnumerable
{
void RemoveAt(string parameterName);
int IndexOf(string parameterName);
bool Contains(string parameterName);
object this[string parameterName]{get; set;}
}
}
@@ -1,33 +0,0 @@
//
// System.Data.IDataReader.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
namespace System.Data
{
/// <summary>
/// Provides a means of reading one or more forward-only streams of result sets obtained by executing a command at a data source, and is implemented by .NET data providers that access relational databases.
/// </summary>
public interface IDataReader : IDisposable, IDataRecord
{
void Close();
DataTable GetSchemaTable();
bool NextResult();
bool Read();
int Depth{get;}
bool IsClosed{get;}
int RecordsAffected{get;}
}
}
@@ -1,67 +0,0 @@
//
// System.Data.IDataRecord.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
namespace System.Data
{
/// <summary>
/// Provides access to the column values within each row for a DataReader, and is implemented by .NET data providers that access relational databases.
/// </summary>
public interface IDataRecord
{
bool GetBoolean(int i);
byte GetByte(int i);
long GetBytes(int i, long fieldOffset, byte[] buffer, int bufferOffset, int length);
char GetChar(int i);
long GetChars(int i, long fieldOffset, char[] buffer, int bufferOffset, int length);
IDataReader GetData(int i);
string GetDataTypeName(int i);
DateTime GetDateTime(int i);
decimal GetDecimal(int i);
double GetDouble(int i);
Type GetFieldType(int i);
float GetFloat(int i);
Guid GetGuid(int i);
short GetInt16(int i);
int GetInt32(int i);
long GetInt64(int i);
string GetName(int i);
int GetOrdinal(string name);
string GetString(int i);
object GetValue(int i);
int GetValues(object[] values);
bool IsDBNull(int i);
int FieldCount{get;}
object this[string name]{get;}
object this[int i]{get;}
}
}
@@ -1,46 +0,0 @@
//
// System.Data.IDBCommand.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
namespace System.Data
{
/// <summary>
/// Represents a SQL statement that is executed while connected to a data source, and is implemented by .NET data providers that access relational databases.
/// </summary>
public interface IDBCommand
{
void Cancel();
IDbDataParameter CreateParameter();
int ExecuteNonQuery();
IDataReader ExecuteReader();
IDataReader ExecuteReader(CommandBehavior behavior);
object ExecuteScalar();
void Prepare();
string CommandText{get; set;}
int CommandTimeout{get; set;}
CommandType CommandType{get; set;}
IDbConnection Connection{get; set;}
IDataParameterCollection Parameters{get;}
IDbTransaction Transaction{get; set;}
UpdateRowSource UpdatedRowSource{get; set;}
}
}
@@ -1,39 +0,0 @@
//
// System.Data.IDBConnection.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
namespace System.Data
{
/// <summary>
/// Represents an open connection to a data source, and is implemented by .NET data providers that access relational databases.
/// </summary>
public interface IDBConnection
{
IDbTransaction BeginTransaction();
IDbTransaction BeginTransaction(IsolationLevel il);
void ChangeDatabase(string databaseName);
void Close();
IDbCommand CreateCommand();
void Open();
string ConnectionString{get; set;}
int ConnectionTimeout{get;}
string Database{get;}
ConnectionState State{get;}
}
}
@@ -1,25 +0,0 @@
//
// System.Data.IDbDataAdapter.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
namespace System.Data
{
/// <summary>
/// Represents a set of command-related properties that are used to fill the DataSet and update a data source, and is implemented by .NET data providers that access relational databases.
/// </summary>
public interface IDbDataAdapter : IDataAdapter
{
IDbCommand DeleteCommand{get; set;}
IDbCommand InsertCommand{get; set;}
IDbCommand SelectCommand{get; set;}
IDbCommand UpdateCommand{get; set;}
}
}
@@ -1,23 +0,0 @@
//
// System.Data.IDbDataParameter.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
namespace System.Data
{
/// <summary>
/// Used by the Visual Basic .NET Data Designers to represent a parameter to a Command object, and optionally, its mapping to DataSet columns.
/// </summary>
public interface IDbDataParameter
{
byte Precision{get; set;}
byte Scale{get; set;}
int Size{get; set;}
}
}
@@ -1,25 +0,0 @@
//
// System.Data.IDbTransaction.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
namespace System.Data
{
/// <summary>
/// Represents a transaction to be performed at a data source, and is implemented by .NET data providers that access relational databases.
/// </summary>
public interface IDbTransaction
{
void Commit();
void Rollback();
IDbConnection Connection{get;}
IsolationLevel IsolationLevel{get;}
}
}
@@ -1,23 +0,0 @@
//
// System.Data.ITableMapping.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
namespace System.Data
{
/// <summary>
/// Associates a source table with a table in a DataSet, and is implemented by the DataTableMapping class, which is used in common by .NET data providers.
/// </summary>
public interface ITableMapping
{
IColumnMappingCollection ColumnMappings{get;}
string DataSetTable{get; set;}
string SourceTable{get; set;}
}
}
@@ -1,31 +0,0 @@
//
// System.Data.ITableMappingCollection.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
using System.Collections;
namespace System.Data
{
/// <summary>
/// Contains a collection of TableMapping objects, and is implemented by the DataTableMappingCollection, which is used in common by .NET data providers.
/// </summary>
public interface ITableMappingCollection : IList, ICollection, IEnumerable
{
ITableMapping Add(string sourceTableName, string dataSetTableName);
bool Contains(string sourceTableName);
ITableMapping GetByDataSetTable(string dataSetTableName);
int IndexOf(string sourceTableName);
void RemoveAt(string sourceTableName);
object this[string index]{get; set;}
}
}
@@ -1,27 +0,0 @@
//
// System.Data.IsolationLevel.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
namespace System.Data
{
/// <summary>
/// Specifies the transaction locking behavior for the connection.
/// This enumeration has a FlagsAttribute that allows a bitwise combination of its member values.
/// </summary>
[Flags]
[Serializable]
public enum IsolationLevel
{
Unspecified = -1,
Chaos = 16,
ReadUncommitted = 256,
ReadCommitted = 4096,
RepeatableRead = 65536,
Serializable = 1048576
}
}
@@ -1,26 +0,0 @@
//
// System.Data.MappingType.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
using System;
namespace mono.System.Data
{
/// <summary>
/// Specifies how a DataColumn is mapped.
/// </summary>
[Serializable]
public enum MappingType
{
Element = 1,
Attribute = 2,
SimpleContent = 3,
Hidden = 4
}
}
@@ -1,18 +0,0 @@
//
// System.Data.MergeFailedEventHandler.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
namespace System.Data
{
/// <summary>
/// Represents the method that will handle the MergeFailed event.
/// </summary>
[Serializable]
public delegate void MergeFailedEventHandler(object sender, MergeFailedEventArgs e);
}
@@ -1,24 +0,0 @@
//
// System.Data.MissingMappingAction.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
using System;
namespace mono.System.Data
{
/// <summary>
/// Determines the action that occurs when a mapping is missing from a source table or a source column.
/// </summary>
[Serializable]
public enum MissingMappingAction
{
Passthrough = 1,
Ignore = 2,
Error = 3
}
}
@@ -1,25 +0,0 @@
//
// System.Data.MissingSchemaAction.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
using System;
namespace mono.System.Data
{
/// <summary>
/// Specifies the action to take when adding data to the DataSet and the required DataTable or DataColumn is missing.
/// </summary>
[Serializable]
public enum MissingSchemaAction
{
Add = 1,
Ignore = 2,
Error = 3,
AddWithKey = 4
}
}
@@ -1,25 +0,0 @@
//
// System.Data.ParameterDirection.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
using System;
namespace mono.System.Data
{
/// <summary>
/// Specifies the type of a parameter within a query relative to the DataSet.
/// </summary>
[Serializable]
public enum ParameterDirection
{
Input = 1,
Output = 2,
InputOutput = 3,
ReturnValue = 6
}
}
@@ -1,28 +0,0 @@
//
// System.Data.PropertyAttributes.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
using System;
namespace mono.System.Data
{
/// <summary>
/// Specifies the attributes of a property.
/// This enumeration has a FlagsAttribute that allows a bitwise combination of its member values
/// </summary>
[Flags]
[Serializable]
public enum PropertyAttributes
{
NotSupported = 0,
Required = 1,
Optional = 2,
Read = 512,
Write = 1024
}
}
-25
View File
@@ -1,25 +0,0 @@
//
// System.Data.Rule.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
using System;
namespace mono.System.Data
{
/// <summary>
/// Indicates the action that occurs when a ForeignKeyConstraint is enforced.
/// </summary>
[Serializable]
public enum Rule
{
None = 0,
Cascade = 1,
SetNull = 2,
SetDefault = 3
}
}
@@ -1,23 +0,0 @@
//
// System.Data.SchemaType.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
using System;
namespace mono.System.Data
{
/// <summary>
/// Specifies how to handle existing schema mappings when performing a FillSchema operation.
/// </summary>
[Serializable]
public enum SchemaType
{
Source = 1,
Mapped = 2
}
}
@@ -1,45 +0,0 @@
//
// System.Data.SqlDbType.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
using System;
namespace mono.System.Data
{
/// <summary>
/// Specifies SQL Server data types.
/// </summary>
[Serializable]
public enum SqlDbType
{
BigInt = 0,
Binary = 1,
Bit = 2,
Char = 3,
DateTime = 4,
Decimal = 5,
Float = 6,
Image = 7,
Int = 8,
Money = 9,
NChar = 10,
NText = 11,
NVarChar = 12,
Real = 13,
UniqueIdentifier = 14,
SmallDateTime = 15,
SmallInt = 16,
SmallMoney = 17,
Text = 18,
Timestamp = 19,
TinyInt = 20,
VarBinary = 21,
VarChar = 22,
Variant = 23
}
}
@@ -1,18 +0,0 @@
//
// System.Data.StateChangeEventHandler.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
namespace System.Data
{
/// <summary>
/// Represents the method that will handle the StateChange event.
/// </summary>
[Serializable]
public delegate void StateChangeEventHandler(object sender, StateChangeEventArgs e);
}
@@ -1,25 +0,0 @@
//
// System.Data.StatementType.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
using System;
namespace mono.System.Data
{
/// <summary>
/// Specifies the type of SQL query to be used by the OleDbRowUpdatedEventArgs, OleDbRowUpdatingEventArgs, SqlRowUpdatedEventArgs, or SqlRowUpdatingEventArgs class.
/// </summary>
[Serializable]
public enum StatementType
{
Select = 0,
Insert = 1,
Update = 2,
Delete = 3
}
}
@@ -1,25 +0,0 @@
//
// System.Data.UpdateRowSource.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
using System;
namespace mono.System.Data
{
/// <summary>
/// Specifies how query command results are applied to the row being updated.
/// </summary>
[Serializable]
public enum UpdateRowSource
{
None = 0,
OutputParameters = 1,
FirstReturnedRecord = 2,
Both = 3
}
}
@@ -1,25 +0,0 @@
//
// System.Data.UpdateStatus.cs
//
// Author:
// Christopher Podurgiel ([email protected])
//
// (C) Chris Podurgiel
//
using System;
namespace mono.System.Data
{
/// <summary>
/// Specifies the action to take with regard to the current and remaining rows during an Update.
/// </summary>
[Serializable]
public enum UpdateStatus
{
Continue = 0,
ErrorsOccurred = 1,
SkipCurrentRow = 2,
SkipAllRemainingRows = 3
}
}
Loaded 100 of 1882 files, more files were not shown because too many files have changed in this diff. Show more