Compare commits

..
1 Commits
Author SHA1 Message Date
nobody 395708bec9 This commit was manufactured by cvs2svn to create tag 'MONO_0_29'.
svn path=/tags/MONO_0_29/mono/; revision=20640
2003-11-30 21:03:40 +00:00
2380 changed files with 46628 additions and 158813 deletions

No files matched your search

-79
View File
@@ -1,82 +1,3 @@
Fri Jan 23 16:07:05 EST 2004 Paolo Molaro <[email protected]>
* configure.in, acconfig.h: check for truncl. Disable
version script on MacOSX (see bug #51590 if a check becomes
necessary).
Fri Jan 23 21:26:01 CET 2004 Paolo Molaro <[email protected]>
* configure.in, acconfig.h: added check for socklen_t.
2004-01-22 Zoltan Varga <[email protected]>
* Makefile.am: Do not install mono.pc on platforms without a JIT.
2004-01-21 Zoltan Varga <[email protected]>
* Makefile.am (remove-binaries): Get rid of non-portable >& construct.
2003-12-29 Miguel de Icaza <[email protected]>
* scripts/sn.in: Add sn script.
2004-01-15 Zoltan Varga <[email protected]>
* scripts/Makefile.am: Add al.exe.
* scripts/al.in: New file.
* runtime/Makefile.am: Add al.exe.
2004-01-10 Jackson Harper <[email protected]>
* data/machine.config: Add trace handler (Trace.axd) add trace
configuration handlers.
2004-01-06 Martin Willemoes Hansen <[email protected]>
* doc/books: Added books on Web Services and ASP.NET
2004-01-04 Daniel Morgan <[email protected]>
* monowiz.win32.nsi: update the NSIS installer script for windows
to support NSIS 2.0 rc1 and Mono 0.29
2003-12-22 Bernie Solomon <[email protected]>
* configure.in: missed in my last change
* samples/embed/testi.c: interpreter embedding example
* docs/embedded-api: add info on interpreter embedding
Mon Dec 22 18:27:14 CET 2003 Paolo Molaro <[email protected]>
* configure.in, acconfig.h: use mach semaphores on darwin.
2003-12-22 Bernie Solomon <[email protected]>
* Makefile.am: Create mint.pc
mint.pc.in: Added for embedding the interpreter
2003-12-16 Martin Baulig <[email protected]>
* Makefile.am: In a Makefile.am, comments are started with `#' and
not with `dnl' - I must have been an idiot ...
2003-12-10 Todd Berman <[email protected]>
* configure.in: adding libicu url to the ICU: no message.
2003-12-05 John Luke <[email protected]>
* data/config.in: new dll mapping entry for libgstreamer
2003-12-02 Atsushi Enomoto <[email protected]>
* README: tiny fix ;-)
2003-11-26 Zoltan Varga <[email protected]>
* configure.in: Add -fno-strict-aliasing to CFLAGS.
+7 -12
View File
@@ -2,17 +2,13 @@ AUTOMAKE_OPTIONS = foreign
SUBDIRS = @libgc_dir@ mono doc docs runtime scripts man data samples
# EXTRA_SUBDIRS = libgc
dnl EXTRA_SUBDIRS = libgc
EXTRA_DIST= mono.pc.in mono.spec.in mint.pc.in
EXTRA_DIST= mono.pc.in mono.spec.in
pkgconfigdir = $(libdir)/pkgconfig
if JIT_SUPPORTED
pkgconfig_DATA= mono.pc mint.pc
else
pkgconfig_DATA= mint.pc
endif
DISTCLEANFILES= mono.pc mint.pc
pkgconfig_DATA= mono.pc
DISTCLEANFILES= mono.pc
#
# The following target is used to compile and install
@@ -24,21 +20,20 @@ fullbuild: remove-binaries mcs-tree-safe-build xinstall-runtime mcs-rest install
mcs-tree-safe-build:
(cd ../mcs/jay; $(MAKE))
(cd ../mcs/mcs; $(MAKE) MCS=mcs BOOTSTRAP_MCS=mcs)
(cd ../mcs/class/corlib; $(MAKE) MCS=mcs BOOTSTRAP_MCS=mcs)
(cd ../mcs/mcs; $(MAKE) MCS=mcs)
(cd ../mcs/class/corlib; $(MAKE) MCS=mcs)
cp ../mcs/class/lib/mscorlib.dll runtime
cp ../mcs/mcs/mcs.exe runtime
xinstall-runtime:
if echo $(SUBDIRS) | grep "libgc " > /dev/null; then (cd libgc; $(MAKE) && $(MAKE) install); fi
(cd mono; $(MAKE) && $(MAKE) install)
(cd runtime; $(MAKE) install assemblies_DATA=mscorlib.dll monobins_DATA=mcs.exe)
mcs-rest:
(cd ../mcs/class; $(MAKE))
remove-binaries:
rm ../mcs/class/lib/mscorlib.dll ../mcs/mcs/mcs.exe runtime/*dll runtime/*.exe > /dev/null 2>&1; echo
rm ../mcs/class/lib/mscorlib.dll ../mcs/mcs/mcs.exe runtime/*dll runtime/*.exe >& /dev/null; echo
win32getdeps:
+2 -91
View File
@@ -8,36 +8,6 @@ This is Mono.
1. Compilation and Installation
===============================
a. Build Requirements
---------------------
To build Mono, you will need the following components:
* pkg-config
Available from: http://www.freedesktop.org/Software/pkgconfig
* glib 2.0
Available from: http://www.gtk.org/
Optional dependencies:
* ICU library
http://oss.software.ibm.com/icu/index.html
You will need this one to get complete support for the international
features of the .NET Framework.
* Cairo and libgdiplus
If you want to get support for System.Drawing, you will need to get
both Libgdiplus and Cairo.
b. Building the Software
------------------------
If you obtained this package as an officially released tarball,
this is very simple, use configure and make:
@@ -46,51 +16,11 @@ This is Mono.
make install
If you obtained this as a snapshot, you will need an existing
Mono installation. To upgrade your installation, unpack both
mono and mcs:
Mono installation. To upgrade your installation do:
tar xzf mcs-XXXX.tar.gz
tar xzf mono-XXXX.tar.gz
cd mono-XXXX
./autogen.sh --prefix=/usr/local
make fullbuild
c. Upgrade from CVS
-------------------
If you are upgrading from CVS you will need an existing Mono installation.
First verify that you have a working installation:
echo 'class X { static void Main () { System.Console.Write("OK");}'}' > x.cs
Compile:
mcs x.cs
And run:
mono x.exe
If you get the output `OK' and no errors, you are ready to start your CVS upgrade.
First, make sure that you have up-to-date mcs and mono sources:
cvs co mono mcs
Then, go into the mono directory, and configure:
cd mono
./autogen --prefix=/usr/local
Then compile using the special target `fullbuild':
make fullbuild
This step will compile and install at the same time.
Failure to follow these steps will result in a broken installation.
2. Using Mono
=============
@@ -117,13 +47,7 @@ This is Mono.
====================
doc/
Contains the web site contents.
docs/
Technical documents about the Mono runtime.
data/
Configuration files installed as part of the Mono runtime.
Contains documentation and the web site contents.
mono/
The core of the Mono Runtime.
@@ -154,17 +78,4 @@ This is Mono.
arch/
Architecture specific portions.
man/
Manual pages for the various Mono commands and programs.
scripts/
Scripts used to invoke Mono and the corresponding program.
runtime/
A directory holding a pre-compiled version of the Mono
runtime.
-3
View File
@@ -30,6 +30,3 @@
#undef HAVE_ICU
#undef HAVE_KW_THREAD
#undef HAVE_SIGNBIT
#undef USE_MACH_SEMA
#undef HAVE_SOCKLEN_T
#undef HAVE_TRUNCL
-51
View File
@@ -1,51 +0,0 @@
/* config.h.in. Generated automatically from configure.in by autoheader 2.13. */
/* Define if you have the ANSI C header files. */
#undef STDC_HEADERS
#undef HAVE_INET_PTON
#undef HAVE_INET_ATON
#undef HAVE_SOL_IP
#undef HAVE_SOL_TCP
#undef HAVE_IP_PKTINFO
#undef HAVE_STRUCT_IP_MREQN
#undef HAVE_PTHREAD
#undef HAVE_PTHREAD_MUTEX_TIMEDLOCK
#undef USE_MONO_MUTEX
#undef HAVE_LARGE_FILE_SUPPORT
#undef PLATFORM_WIN32
#undef HAVE_NEW_ICONV
#undef NAME_DEV_RANDOM
#undef HAVE_CRYPT_RNG
#undef HAVE_BOEHM_GC
/* The number of bytes in a void *. */
#undef SIZEOF_VOID_P
/* Define if you have the inet_aton function. */
#undef HAVE_INET_ATON
/* Define if you have the inet_pton function. */
#undef HAVE_INET_PTON
/* Define if you have the <dlfcn.h> header file. */
#undef HAVE_DLFCN_H
/* Define if you have the <netdb.h> header file. */
#undef HAVE_NETDB_H
/* Define if you have the <sys/filio.h> header file. */
#undef HAVE_SYS_FILIO_H
/* Define if you have the <sys/sockio.h> header file. */
#undef HAVE_SYS_SOCKIO_H
/* Define if you have the <utime.h> header file. */
#undef HAVE_UTIME_H
/* Name of package */
#undef PACKAGE
/* Version number of package */
#undef VERSION
+1 -30
View File
@@ -1,7 +1,7 @@
AC_INIT(README)
AC_CANONICAL_SYSTEM
AM_CONFIG_HEADER(config.h)
AM_INIT_AUTOMAKE(mono,0.30)
AM_INIT_AUTOMAKE(mono,0.29)
AM_MAINTAINER_MODE
dnl
@@ -27,9 +27,6 @@ libmono_ldflags=""
AC_SUBST(libmono_cflags)
AC_SUBST(libmono_ldflags)
dnl if linker handles the version script
no_version_script=no
# Thread configuration inspired by sleepycat's db
AC_MSG_CHECKING([host platform characteristics])
libgc_threads=no
@@ -100,8 +97,6 @@ case "$host" in
libmono_ldflags="-pthread"
AC_DEFINE(NEED_LINK_UNLINK)
AC_DEFINE(PTHREAD_POINTER_ID)
AC_DEFINE(USE_MACH_SEMA)
no_version_script=yes
libdl=
libgc_threads=no
gc_default=none
@@ -114,7 +109,6 @@ case "$host" in
esac
AC_MSG_RESULT(ok)
AM_CONDITIONAL(PLATFORM_WIN32, test x$platform_win32 = xyes)
AM_CONDITIONAL(NO_VERSION_SCRIPT, test x$no_version_script = xyes)
AC_CHECK_TOOL(CC, gcc, gcc)
AC_PROG_CC
@@ -676,27 +670,6 @@ else
AC_CHECK_LIB(psapi, main, LIBS="$LIBS -lpsapi", AC_ERROR(bad mingw install?))
fi
dnl socklen_t check
AC_MSG_CHECKING(for socklen_t)
AC_TRY_COMPILE([
#include <sys/types.h>
#include <sys/socket.h>
],[
socklen_t foo;
],[
ac_cv_c_socklen_t=yes
AC_DEFINE(HAVE_SOCKLEN_T)
AC_MSG_RESULT(yes)
],[
AC_MSG_RESULT(no)
])
AC_CHECK_FUNCS(truncl, , AC_MSG_CHECKING(for truncl in math.h)
AC_TRY_LINK([#include <math.h>],
[ truncl(0.0); ],
AC_DEFINE(HAVE_TRUNCL) AC_MSG_RESULT(yes),
AC_MSG_RESULT(no)))
dnl ****************************
dnl *** Look for /dev/random ***
dnl ****************************
@@ -776,7 +749,6 @@ enable_icu=no
AC_PATH_PROG(ICU_CONFIG, icu-config, no)
if test "x$ICU_CONFIG" = "xno" -o ! -x "$ICU_CONFIG"; then
AC_MSG_WARN([Only invariant locale available; install ICU for I18N support])
enable_icu="no, if you want full i18n support download it from: http://oss.software.ibm.com/icu/index.html"
else
enable_icu="yes. Version: `$ICU_CONFIG --version`"
AC_DEFINE(HAVE_ICU)
@@ -898,7 +870,6 @@ AC_SUBST(LDFLAGS)
AC_OUTPUT([
Makefile
mint.pc
mono.pc
mono/Makefile
mono/utils/Makefile
-1
View File
@@ -2,4 +2,3 @@ Makefile.in
Makefile
config
.cvsignore
browscap.ini
+5 -855
View File
@@ -86,9 +86,7 @@ void BuildOperationInfo ()
InParams = new ArrayList ();
OutParams = new ArrayList ();
Port port = FindPort (CurrentOperationBinding, null);
Binding binding = descriptions.GetBinding (port.Binding);
Binding binding = FindBinding (CurrentOperationBinding);
PortType portType = descriptions.GetPortType (binding.Type);
Operation oper = FindOperation (portType, CurrentOperationName);
@@ -231,33 +229,15 @@ ArrayList FindServiceProtocols(string operName)
return table;
}
Port FindPort (string portName, string protocol)
Binding FindBinding (string portName)
{
Service service = descriptions[0].Services[0];
foreach (Port port in service.Ports)
{
if (portName == null)
{
Binding binding = descriptions.GetBinding (port.Binding);
if (GetProtocol (binding) == protocol) return port;
}
else if (port.Name == portName)
return port;
}
if (port.Name == portName)
return descriptions.GetBinding (port.Binding);
return null;
}
string GetProtocol (Binding binding)
{
if (binding.Extensions.Find (typeof(SoapBinding)) != null) return "Soap";
HttpBinding hb = (HttpBinding) binding.Extensions.Find (typeof(HttpBinding));
if (hb == null) return "";
if (hb.Verb == "POST") return "HttpPost";
if (hb.Verb == "GET") return "HttpGet";
return "";
}
Operation FindOperation (PortType portType, string name)
{
foreach (Operation oper in portType.Operations) {
@@ -359,40 +339,6 @@ string GetTestResult ()
}
}
string GenerateOperationMessages (string protocol, bool generateInput)
{
if (!IsOperationSupported (protocol)) return "";
Port port;
if (protocol != "Soap") port = FindPort (null, protocol);
else port = FindPort (CurrentOperationBinding, null);
Binding binding = descriptions.GetBinding (port.Binding);
OperationBinding obin = FindOperation (binding, CurrentOperationName);
PortType portType = descriptions.GetPortType (binding.Type);
Operation oper = FindOperation (portType, CurrentOperationName);
HtmlSampleGenerator sg = new HtmlSampleGenerator (descriptions, schemas);
string txt = sg.GenerateMessage (port, obin, oper, protocol, generateInput);
if (protocol == "Soap") txt = WrapText (txt,CodeTextColumns);
txt = ColorizeXml (txt);
txt = txt.Replace ("@placeholder!","<span class='literal-placeholder'>");
txt = txt.Replace ("!placeholder@","</span>");
return txt;
}
bool IsOperationSupported (string protocol)
{
if (CurrentPage != "op" || CurrentTab != "msg") return false;
if (protocol == "Soap") return true;
Port port = FindPort (null, protocol);
if (port == null) return false;
Binding binding = descriptions.GetBinding (port.Binding);
if (binding == null) return false;
return FindOperation (binding, CurrentOperationName) != null;
}
//
// Proxy code generation
//
@@ -742,765 +688,9 @@ class Parameter
public string Description { get { return description; } set { description = value; } }
}
public class HtmlSampleGenerator: SampleGenerator
{
public HtmlSampleGenerator (ServiceDescriptionCollection services, XmlSchemas schemas)
: base (services, schemas)
{
}
protected override string GetLiteral (string s)
{
return "@placeholder!" + s + "!placeholder@";
}
}
public class SampleGenerator
{
protected ServiceDescriptionCollection descriptions;
protected XmlSchemas schemas;
XmlSchemaElement anyElement;
ArrayList queue;
SoapBindingUse currentUse;
XmlDocument document = new XmlDocument ();
static readonly XmlQualifiedName anyType = new XmlQualifiedName ("anyType",XmlSchema.Namespace);
static readonly XmlQualifiedName arrayType = new XmlQualifiedName ("Array","http://schemas.xmlsoap.org/soap/encoding/");
static readonly XmlQualifiedName arrayTypeRefName = new XmlQualifiedName ("arrayType","http://schemas.xmlsoap.org/soap/encoding/");
const string SoapEnvelopeNamespace = "http://schemas.xmlsoap.org/soap/envelope/";
const string WsdlNamespace = "http://schemas.xmlsoap.org/wsdl/";
const string SoapEncodingNamespace = "http://schemas.xmlsoap.org/soap/encoding/";
class EncodedType
{
public EncodedType (string ns, XmlSchemaElement elem) { Namespace = ns; Element = elem; }
public string Namespace;
public XmlSchemaElement Element;
}
public SampleGenerator (ServiceDescriptionCollection services, XmlSchemas schemas)
{
descriptions = services;
this.schemas = schemas;
queue = new ArrayList ();
}
public string GenerateMessage (Port port, OperationBinding obin, Operation oper, string protocol, bool generateInput)
{
OperationMessage msg = null;
foreach (OperationMessage opm in oper.Messages)
{
if (opm is OperationInput && generateInput) msg = opm;
else if (opm is OperationOutput && !generateInput) msg = opm;
}
if (msg == null) return null;
switch (protocol) {
case "Soap": return GenerateHttpSoapMessage (port, obin, oper, msg);
case "HttpGet": return GenerateHttpGetMessage (port, obin, oper, msg);
case "HttpPost": return GenerateHttpPostMessage (port, obin, oper, msg);
}
return "Unknown protocol";
}
public string GenerateHttpSoapMessage (Port port, OperationBinding obin, Operation oper, OperationMessage msg)
{
string req = "";
if (msg is OperationInput)
{
SoapAddressBinding sab = port.Extensions.Find (typeof(SoapAddressBinding)) as SoapAddressBinding;
SoapOperationBinding sob = obin.Extensions.Find (typeof(SoapOperationBinding)) as SoapOperationBinding;
req += "POST " + new Uri (sab.Location).AbsolutePath + "\n";
req += "SOAPAction: " + sob.SoapAction + "\n";
req += "Content-Type: text/xml; charset=utf-8\n";
req += "Content-Length: " + GetLiteral ("string") + "\n";
req += "Host: " + GetLiteral ("string") + "\n\n";
}
else
{
req += "HTTP/1.0 200 OK\n";
req += "Content-Type: text/xml; charset=utf-8\n";
req += "Content-Length: " + GetLiteral ("string") + "\n\n";
}
req += GenerateSoapMessage (obin, oper, msg);
return req;
}
public string GenerateHttpGetMessage (Port port, OperationBinding obin, Operation oper, OperationMessage msg)
{
string req = "";
if (msg is OperationInput)
{
HttpAddressBinding sab = port.Extensions.Find (typeof(HttpAddressBinding)) as HttpAddressBinding;
HttpOperationBinding sob = obin.Extensions.Find (typeof(HttpOperationBinding)) as HttpOperationBinding;
string location = new Uri (sab.Location).AbsolutePath + sob.Location + "?" + BuildQueryString (msg);
req += "GET " + location + "\n";
req += "Host: " + GetLiteral ("string");
}
else
{
req += "HTTP/1.0 200 OK\n";
req += "Content-Type: text/xml; charset=utf-8\n";
req += "Content-Length: " + GetLiteral ("string") + "\n\n";
MimeXmlBinding mxb = (MimeXmlBinding) obin.Output.Extensions.Find (typeof(MimeXmlBinding)) as MimeXmlBinding;
if (mxb == null) return req;
Message message = descriptions.GetMessage (msg.Message);
XmlQualifiedName ename = null;
foreach (MessagePart part in message.Parts)
if (part.Name == mxb.Part) ename = part.Element;
if (ename == null) return req + GetLiteral("string");
StringWriter sw = new StringWriter ();
XmlTextWriter xtw = new XmlTextWriter (sw);
xtw.Formatting = Formatting.Indented;
currentUse = SoapBindingUse.Literal;
WriteRootElementSample (xtw, ename);
xtw.Close ();
req += sw.ToString ();
}
return req;
}
public string GenerateHttpPostMessage (Port port, OperationBinding obin, Operation oper, OperationMessage msg)
{
string req = "";
if (msg is OperationInput)
{
HttpAddressBinding sab = port.Extensions.Find (typeof(HttpAddressBinding)) as HttpAddressBinding;
HttpOperationBinding sob = obin.Extensions.Find (typeof(HttpOperationBinding)) as HttpOperationBinding;
string location = new Uri (sab.Location).AbsolutePath + sob.Location;
req += "POST " + location + "\n";
req += "Content-Type: application/x-www-form-urlencoded\n";
req += "Content-Length: " + GetLiteral ("string") + "\n";
req += "Host: " + GetLiteral ("string") + "\n\n";
req += BuildQueryString (msg);
}
else return GenerateHttpGetMessage (port, obin, oper, msg);
return req;
}
string BuildQueryString (OperationMessage opm)
{
string s = "";
Message msg = descriptions.GetMessage (opm.Message);
foreach (MessagePart part in msg.Parts)
{
if (s.Length != 0) s += "&";
s += part.Name + "=" + GetLiteral (part.Type.Name);
}
return s;
}
public string GenerateSoapMessage (OperationBinding obin, Operation oper, OperationMessage msg)
{
SoapOperationBinding sob = obin.Extensions.Find (typeof(SoapOperationBinding)) as SoapOperationBinding;
SoapBindingStyle style = (sob != null) ? sob.Style : SoapBindingStyle.Document;
MessageBinding msgbin = (msg is OperationInput) ? (MessageBinding) obin.Input : (MessageBinding)obin.Output;
SoapBodyBinding sbb = msgbin.Extensions.Find (typeof(SoapBodyBinding)) as SoapBodyBinding;
SoapBindingUse bodyUse = (sbb != null) ? sbb.Use : SoapBindingUse.Literal;
StringWriter sw = new StringWriter ();
XmlTextWriter xtw = new XmlTextWriter (sw);
xtw.Formatting = Formatting.Indented;
xtw.WriteStartDocument ();
xtw.WriteStartElement ("soap", "Envelope", SoapEnvelopeNamespace);
xtw.WriteAttributeString ("xmlns", "xsi", null, XmlSchema.InstanceNamespace);
xtw.WriteAttributeString ("xmlns", "xsd", null, XmlSchema.Namespace);
if (bodyUse == SoapBindingUse.Encoded)
{
xtw.WriteAttributeString ("xmlns", "soapenc", null, SoapEncodingNamespace);
xtw.WriteAttributeString ("xmlns", "tns", null, msg.Message.Namespace);
}
// Serialize headers
foreach (object ob in msgbin.Extensions)
{
SoapHeaderBinding hb = ob as SoapHeaderBinding;
if (hb == null) continue;
xtw.WriteStartElement ("soap", "Header", SoapEnvelopeNamespace);
WriteHeader (xtw, hb);
xtw.WriteEndElement ();
}
// Serialize body
xtw.WriteStartElement ("soap", "Body", SoapEnvelopeNamespace);
currentUse = bodyUse;
WriteBody (xtw, oper, msg, sbb, style);
xtw.WriteEndElement ();
xtw.WriteEndElement ();
xtw.Close ();
return sw.ToString ();
}
void WriteHeader (XmlTextWriter xtw, SoapHeaderBinding header)
{
Message msg = descriptions.GetMessage (header.Message);
if (msg == null) throw new InvalidOperationException ("Message " + header.Message + " not found");
MessagePart part = msg.Parts [header.Part];
if (part == null) throw new InvalidOperationException ("Message part " + header.Part + " not found in message " + header.Message);
currentUse = header.Use;
if (currentUse == SoapBindingUse.Literal)
WriteRootElementSample (xtw, part.Element);
else
WriteTypeSample (xtw, part.Type);
}
void WriteBody (XmlTextWriter xtw, Operation oper, OperationMessage opm, SoapBodyBinding sbb, SoapBindingStyle style)
{
Message msg = descriptions.GetMessage (opm.Message);
if (msg.Parts.Count > 0 && msg.Parts[0].Name == "parameters")
{
MessagePart part = msg.Parts[0];
if (part.Element == XmlQualifiedName.Empty)
WriteTypeSample (xtw, part.Type);
else
WriteRootElementSample (xtw, part.Element);
}
else
{
string elemName = oper.Name;
string ns = "";
if (opm is OperationOutput) elemName += "Response";
if (style == SoapBindingStyle.Rpc) {
xtw.WriteStartElement (elemName, sbb.Namespace);
ns = sbb.Namespace;
}
foreach (MessagePart part in msg.Parts)
{
if (part.Element == XmlQualifiedName.Empty)
{
XmlSchemaElement elem = new XmlSchemaElement ();
elem.SchemaTypeName = part.Type;
elem.Name = part.Name;
WriteElementSample (xtw, ns, elem);
}
else
WriteRootElementSample (xtw, part.Element);
}
if (style == SoapBindingStyle.Rpc)
xtw.WriteEndElement ();
}
WriteQueuedTypeSamples (xtw);
}
void WriteRootElementSample (XmlTextWriter xtw, XmlQualifiedName qname)
{
XmlSchemaElement elem = (XmlSchemaElement) schemas.Find (qname, typeof(XmlSchemaElement));
if (elem == null) throw new InvalidOperationException ("Element not found: " + qname);
WriteElementSample (xtw, qname.Namespace, elem);
}
void WriteElementSample (XmlTextWriter xtw, string ns, XmlSchemaElement elem)
{
bool sharedAnnType = false;
XmlQualifiedName root;
if (!elem.RefName.IsEmpty) {
XmlSchemaElement refElem = FindRefElement (elem);
if (refElem == null) throw new InvalidOperationException ("Global element not found: " + elem.RefName);
root = elem.RefName;
elem = refElem;
sharedAnnType = true;
}
else
root = new XmlQualifiedName (elem.Name, ns);
if (!elem.SchemaTypeName.IsEmpty)
{
XmlSchemaComplexType st = FindComplexTyype (elem.SchemaTypeName);
if (st != null)
WriteComplexTypeSample (xtw, st, root);
else
{
xtw.WriteStartElement (root.Name, root.Namespace);
if (currentUse == SoapBindingUse.Encoded)
xtw.WriteAttributeString ("type", XmlSchema.InstanceNamespace, GetQualifiedNameString (xtw, elem.SchemaTypeName));
xtw.WriteString (GetLiteral (FindBuiltInType (elem.SchemaTypeName)));
xtw.WriteEndElement ();
}
}
else if (elem.SchemaType == null)
{
xtw.WriteStartElement ("any");
xtw.WriteEndElement ();
}
else
WriteComplexTypeSample (xtw, (XmlSchemaComplexType) elem.SchemaType, root);
}
void WriteTypeSample (XmlTextWriter xtw, XmlQualifiedName qname)
{
XmlSchemaComplexType ctype = FindComplexTyype (qname);
if (ctype != null) {
WriteComplexTypeSample (xtw, ctype, qname);
return;
}
XmlSchemaSimpleType stype = (XmlSchemaSimpleType) schemas.Find (qname, typeof(XmlSchemaSimpleType));
if (stype != null) {
WriteSimpleTypeSample (xtw, stype);
return;
}
xtw.WriteString (GetLiteral (FindBuiltInType (qname)));
throw new InvalidOperationException ("Type not found: " + qname);
}
void WriteComplexTypeSample (XmlTextWriter xtw, XmlSchemaComplexType stype, XmlQualifiedName rootName)
{
WriteComplexTypeSample (xtw, stype, rootName, -1);
}
void WriteComplexTypeSample (XmlTextWriter xtw, XmlSchemaComplexType stype, XmlQualifiedName rootName, int id)
{
string ns = rootName.Namespace;
if (rootName.Name.IndexOf ("[]") != -1) rootName = arrayType;
if (currentUse == SoapBindingUse.Encoded) {
string pref = xtw.LookupPrefix (rootName.Namespace);
if (pref == null) pref = "q1";
xtw.WriteStartElement (pref, rootName.Name, rootName.Namespace);
ns = "";
}
else
xtw.WriteStartElement (rootName.Name, rootName.Namespace);
if (id != -1)
{
xtw.WriteAttributeString ("id", "id" + id);
if (rootName != arrayType)
xtw.WriteAttributeString ("type", XmlSchema.InstanceNamespace, GetQualifiedNameString (xtw, rootName));
}
WriteComplexTypeAttributes (xtw, stype);
WriteComplexTypeElements (xtw, ns, stype);
xtw.WriteEndElement ();
}
void WriteComplexTypeAttributes (XmlTextWriter xtw, XmlSchemaComplexType stype)
{
WriteAttributes (xtw, stype.Attributes, stype.AnyAttribute);
}
void WriteComplexTypeElements (XmlTextWriter xtw, string ns, XmlSchemaComplexType stype)
{
if (stype.Particle != null)
WriteParticleComplexContent (xtw, ns, stype.Particle);
else
{
if (stype.ContentModel is XmlSchemaSimpleContent)
WriteSimpleContent (xtw, (XmlSchemaSimpleContent)stype.ContentModel);
else if (stype.ContentModel is XmlSchemaComplexContent)
WriteComplexContent (xtw, ns, (XmlSchemaComplexContent)stype.ContentModel);
}
}
void WriteAttributes (XmlTextWriter xtw, XmlSchemaObjectCollection atts, XmlSchemaAnyAttribute anyat)
{
foreach (XmlSchemaObject at in atts)
{
if (at is XmlSchemaAttribute)
{
string ns;
XmlSchemaAttribute attr = (XmlSchemaAttribute)at;
XmlSchemaAttribute refAttr = attr;
// refAttr.Form; TODO
if (!attr.RefName.IsEmpty) {
refAttr = FindRefAttribute (attr.RefName);
if (refAttr == null) throw new InvalidOperationException ("Global attribute not found: " + attr.RefName);
}
string val;
if (!refAttr.SchemaTypeName.IsEmpty) val = FindBuiltInType (refAttr.SchemaTypeName);
else val = FindBuiltInType ((XmlSchemaSimpleType) refAttr.SchemaType);
xtw.WriteAttributeString (refAttr.Name, val);
}
else if (at is XmlSchemaAttributeGroupRef)
{
XmlSchemaAttributeGroupRef gref = (XmlSchemaAttributeGroupRef)at;
XmlSchemaAttributeGroup grp = (XmlSchemaAttributeGroup) schemas.Find (gref.RefName, typeof(XmlSchemaAttributeGroup));
WriteAttributes (xtw, grp.Attributes, grp.AnyAttribute);
}
}
if (anyat != null)
xtw.WriteAttributeString ("custom-attribute","value");
}
void WriteParticleComplexContent (XmlTextWriter xtw, string ns, XmlSchemaParticle particle)
{
WriteParticleContent (xtw, ns, particle, false);
}
void WriteParticleContent (XmlTextWriter xtw, string ns, XmlSchemaParticle particle, bool multiValue)
{
if (particle is XmlSchemaGroupRef)
particle = GetRefGroupParticle ((XmlSchemaGroupRef)particle);
if (particle.MaxOccurs > 1) multiValue = true;
if (particle is XmlSchemaSequence) {
WriteSequenceContent (xtw, ns, ((XmlSchemaSequence)particle).Items, multiValue);
}
else if (particle is XmlSchemaChoice) {
if (((XmlSchemaChoice)particle).Items.Count == 1)
WriteSequenceContent (xtw, ns, ((XmlSchemaChoice)particle).Items, multiValue);
else
WriteChoiceContent (xtw, ns, (XmlSchemaChoice)particle, multiValue);
}
else if (particle is XmlSchemaAll) {
WriteSequenceContent (xtw, ns, ((XmlSchemaAll)particle).Items, multiValue);
}
}
void WriteSequenceContent (XmlTextWriter xtw, string ns, XmlSchemaObjectCollection items, bool multiValue)
{
foreach (XmlSchemaObject item in items)
WriteContentItem (xtw, ns, item, multiValue);
}
void WriteContentItem (XmlTextWriter xtw, string ns, XmlSchemaObject item, bool multiValue)
{
if (item is XmlSchemaGroupRef)
item = GetRefGroupParticle ((XmlSchemaGroupRef)item);
if (item is XmlSchemaElement)
{
XmlSchemaElement elem = (XmlSchemaElement) item;
XmlSchemaElement refElem;
if (!elem.RefName.IsEmpty) refElem = FindRefElement (elem);
else refElem = elem;
int num = (elem.MaxOccurs == 1 && !multiValue) ? 1 : 2;
for (int n=0; n<num; n++)
{
if (currentUse == SoapBindingUse.Literal)
WriteElementSample (xtw, ns, refElem);
else
WriteRefTypeSample (xtw, ns, refElem);
}
}
else if (item is XmlSchemaAny)
{
xtw.WriteStartElement ("any"); xtw.WriteEndElement ();
if (multiValue) {
xtw.WriteStartElement ("any"); xtw.WriteEndElement ();
}
}
else if (item is XmlSchemaParticle) {
WriteParticleContent (xtw, ns, (XmlSchemaParticle)item, multiValue);
}
}
void WriteChoiceContent (XmlTextWriter xtw, string ns, XmlSchemaChoice choice, bool multiValue)
{
foreach (XmlSchemaObject item in choice.Items)
WriteContentItem (xtw, ns, item, multiValue);
}
void WriteSimpleContent (XmlTextWriter xtw, XmlSchemaSimpleContent content)
{
XmlSchemaSimpleContentExtension ext = content.Content as XmlSchemaSimpleContentExtension;
if (ext != null)
WriteAttributes (xtw, ext.Attributes, ext.AnyAttribute);
XmlQualifiedName qname = GetContentBaseType (content.Content);
xtw.WriteString (GetLiteral (FindBuiltInType (qname)));
}
string FindBuiltInType (XmlQualifiedName qname)
{
if (qname.Namespace == XmlSchema.Namespace)
return qname.Name;
XmlSchemaComplexType ct = FindComplexTyype (qname);
if (ct != null)
{
XmlSchemaSimpleContent sc = ct.ContentModel as XmlSchemaSimpleContent;
if (sc == null) throw new InvalidOperationException ("Invalid schema");
return FindBuiltInType (GetContentBaseType (sc.Content));
}
XmlSchemaSimpleType st = (XmlSchemaSimpleType) schemas.Find (qname, typeof(XmlSchemaSimpleType));
if (st != null)
return FindBuiltInType (st);
throw new InvalidOperationException ("Definition of type " + qname + " not found");
}
string FindBuiltInType (XmlSchemaSimpleType st)
{
if (st.Content is XmlSchemaSimpleTypeRestriction) {
return FindBuiltInType (GetContentBaseType (st.Content));
}
else if (st.Content is XmlSchemaSimpleTypeList) {
string s = FindBuiltInType (GetContentBaseType (st.Content));
return s + " " + s + " ...";
}
else if (st.Content is XmlSchemaSimpleTypeUnion)
{
// Check if all types of the union are equal. If not, then will use anyType.
XmlSchemaSimpleTypeUnion uni = (XmlSchemaSimpleTypeUnion) st.Content;
string utype = null;
// Anonymous types are unique
if (uni.BaseTypes.Count != 0 && uni.MemberTypes.Length != 0)
return "string";
foreach (XmlQualifiedName mt in uni.MemberTypes)
{
string qn = FindBuiltInType (mt);
if (utype != null && qn != utype) return "string";
else utype = qn;
}
return utype;
}
else
return "string";
}
XmlQualifiedName GetContentBaseType (XmlSchemaObject ob)
{
if (ob is XmlSchemaSimpleContentExtension)
return ((XmlSchemaSimpleContentExtension)ob).BaseTypeName;
else if (ob is XmlSchemaSimpleContentRestriction)
return ((XmlSchemaSimpleContentRestriction)ob).BaseTypeName;
else if (ob is XmlSchemaSimpleTypeRestriction)
return ((XmlSchemaSimpleTypeRestriction)ob).BaseTypeName;
else if (ob is XmlSchemaSimpleTypeList)
return ((XmlSchemaSimpleTypeList)ob).ItemTypeName;
else
return null;
}
void WriteComplexContent (XmlTextWriter xtw, string ns, XmlSchemaComplexContent content)
{
XmlQualifiedName qname;
XmlSchemaComplexContentExtension ext = content.Content as XmlSchemaComplexContentExtension;
if (ext != null) qname = ext.BaseTypeName;
else {
XmlSchemaComplexContentRestriction rest = (XmlSchemaComplexContentRestriction)content.Content;
qname = rest.BaseTypeName;
if (qname == arrayType) {
ParseArrayType (rest, out qname);
XmlSchemaElement elem = new XmlSchemaElement ();
elem.Name = "Item";
elem.SchemaTypeName = qname;
xtw.WriteAttributeString ("arrayType", SoapEncodingNamespace, qname.Name + "[2]");
WriteContentItem (xtw, ns, elem, true);
return;
}
}
// Add base map members to this map
XmlSchemaComplexType ctype = FindComplexTyype (qname);
WriteComplexTypeAttributes (xtw, ctype);
if (ext != null) {
// Add the members of this map
WriteAttributes (xtw, ext.Attributes, ext.AnyAttribute);
if (ext.Particle != null)
WriteParticleComplexContent (xtw, ns, ext.Particle);
}
WriteComplexTypeElements (xtw, ns, ctype);
}
void ParseArrayType (XmlSchemaComplexContentRestriction rest, out XmlQualifiedName qtype)
{
XmlSchemaAttribute arrayTypeAt = FindArrayAttribute (rest.Attributes);
XmlAttribute[] uatts = arrayTypeAt.UnhandledAttributes;
if (uatts == null || uatts.Length == 0) throw new InvalidOperationException ("arrayType attribute not specified in array declaration");
XmlAttribute xat = null;
foreach (XmlAttribute at in uatts)
if (at.LocalName == "arrayType" && at.NamespaceURI == WsdlNamespace)
{ xat = at; break; }
if (xat == null)
throw new InvalidOperationException ("arrayType attribute not specified in array declaration");
string arrayType = xat.Value;
string type, ns;
int i = arrayType.LastIndexOf (":");
if (i == -1) ns = "";
else ns = arrayType.Substring (0,i);
int j = arrayType.IndexOf ("[", i+1);
if (j == -1) throw new InvalidOperationException ("Cannot parse WSDL array type: " + arrayType);
type = arrayType.Substring (i+1);
type = type.Substring (0, type.Length-2);
qtype = new XmlQualifiedName (type, ns);
}
XmlSchemaAttribute FindArrayAttribute (XmlSchemaObjectCollection atts)
{
foreach (object ob in atts)
{
XmlSchemaAttribute att = ob as XmlSchemaAttribute;
if (att != null && att.RefName == arrayTypeRefName) return att;
XmlSchemaAttributeGroupRef gref = ob as XmlSchemaAttributeGroupRef;
if (gref != null)
{
XmlSchemaAttributeGroup grp = (XmlSchemaAttributeGroup) schemas.Find (gref.RefName, typeof(XmlSchemaAttributeGroup));
att = FindArrayAttribute (grp.Attributes);
if (att != null) return att;
}
}
return null;
}
void WriteSimpleTypeSample (XmlTextWriter xtw, XmlSchemaSimpleType stype)
{
xtw.WriteString (GetLiteral (FindBuiltInType (stype)));
}
XmlSchemaParticle GetRefGroupParticle (XmlSchemaGroupRef refGroup)
{
XmlSchemaGroup grp = (XmlSchemaGroup) schemas.Find (refGroup.RefName, typeof (XmlSchemaGroup));
return grp.Particle;
}
XmlSchemaElement FindRefElement (XmlSchemaElement elem)
{
if (elem.RefName.Namespace == XmlSchema.Namespace)
{
if (anyElement != null) return anyElement;
anyElement = new XmlSchemaElement ();
anyElement.Name = "any";
anyElement.SchemaTypeName = anyType;
return anyElement;
}
return (XmlSchemaElement) schemas.Find (elem.RefName, typeof(XmlSchemaElement));
}
XmlSchemaAttribute FindRefAttribute (XmlQualifiedName refName)
{
if (refName.Namespace == XmlSchema.Namespace)
{
XmlSchemaAttribute at = new XmlSchemaAttribute ();
at.Name = refName.Name;
at.SchemaTypeName = new XmlQualifiedName ("string",XmlSchema.Namespace);
return at;
}
return (XmlSchemaAttribute) schemas.Find (refName, typeof(XmlSchemaAttribute));
}
void WriteRefTypeSample (XmlTextWriter xtw, string ns, XmlSchemaElement elem)
{
if (elem.SchemaTypeName.Namespace == XmlSchema.Namespace || schemas.Find (elem.SchemaTypeName, typeof(XmlSchemaSimpleType)) != null)
WriteElementSample (xtw, ns, elem);
else
{
xtw.WriteStartElement (elem.Name, ns);
xtw.WriteAttributeString ("href", "#id" + (queue.Count+1));
xtw.WriteEndElement ();
queue.Add (new EncodedType (ns, elem));
}
}
void WriteQueuedTypeSamples (XmlTextWriter xtw)
{
for (int n=0; n<queue.Count; n++)
{
EncodedType ec = (EncodedType) queue[n];
XmlSchemaComplexType st = FindComplexTyype (ec.Element.SchemaTypeName);
WriteComplexTypeSample (xtw, st, ec.Element.SchemaTypeName, n+1);
}
}
XmlSchemaComplexType FindComplexTyype (XmlQualifiedName qname)
{
if (qname.Name.IndexOf ("[]") != -1)
{
XmlSchemaComplexType stype = new XmlSchemaComplexType ();
stype.ContentModel = new XmlSchemaComplexContent ();
XmlSchemaComplexContentRestriction res = new XmlSchemaComplexContentRestriction ();
stype.ContentModel.Content = res;
res.BaseTypeName = arrayType;
XmlSchemaAttribute att = new XmlSchemaAttribute ();
att.RefName = arrayTypeRefName;
res.Attributes.Add (att);
XmlAttribute xat = document.CreateAttribute ("arrayType", WsdlNamespace);
xat.Value = qname.Namespace + ":" + qname.Name;
att.UnhandledAttributes = new XmlAttribute[] {xat};
return stype;
}
return (XmlSchemaComplexType) schemas.Find (qname, typeof(XmlSchemaComplexType));
}
string GetQualifiedNameString (XmlTextWriter xtw, XmlQualifiedName qname)
{
string pref = xtw.LookupPrefix (qname.Namespace);
if (pref != null) return pref + ":" + qname.Name;
xtw.WriteAttributeString ("xmlns", "q1", null, qname.Namespace);
return "q1:" + qname.Name;
}
protected virtual string GetLiteral (string s)
{
return s;
}
void GetOperationFormat (OperationBinding obin, out SoapBindingStyle style, out SoapBindingUse use)
{
style = SoapBindingStyle.Document;
use = SoapBindingUse.Literal;
SoapOperationBinding sob = obin.Extensions.Find (typeof(SoapOperationBinding)) as SoapOperationBinding;
if (sob != null) {
style = sob.Style;
SoapBodyBinding sbb = obin.Input.Extensions.Find (typeof(SoapBodyBinding)) as SoapBodyBinding;
if (sbb != null)
use = sbb.Use;
}
}
}
</script>
<head>
<link rel="alternate" type="text/xml" href="<%=Request.FilePath%>?disco"/>
<title><%=WebServiceName%> Web Service</title>
<style type="text/css">
BODY { font-family: Arial; margin-left: 20px; margin-top: 20px; font-size: x-small}
@@ -1524,7 +714,6 @@ public class HtmlSampleGenerator: SampleGenerator
.code-vb { font-size:10pt; font-family:courier }
.tabLabelOn { font-weight:bold }
.tabLabelOff {color: darkgray }
.literal-placeholder {color: darkblue; font-weight:bold}
A:link { color: black; }
A:visited { color: black; }
A:active { color: black; }
@@ -1642,11 +831,6 @@ function clearForm ()
<br>Supported protocols: <%#CurrentOperationProtocols%>
<% } %>
<!--
**********************************************************
Operation description - Test form
-->
<% if (CurrentTab == "test") {
if (CurrentOperationSupportsTest) {%>
Enter values for the parameters and click the 'Invoke' button to test this method:<br><br>
@@ -1676,42 +860,8 @@ function clearForm ()
The test form is not available for this operation because it has parameters with a complex structure.
<% } %>
<% } %>
<!--
**********************************************************
Operation description - Message Layout
-->
<% if (CurrentTab == "msg") { %>
The following are sample SOAP requests and responses for each protocol supported by this method:
<br/><br/>
<% if (IsOperationSupported ("Soap")) { %>
<span class="label">Soap</span>
<br/><br/>
<div class="codePanel"><div class="code-xml"><%#GenerateOperationMessages ("Soap", true)%></div></div>
<br/>
<div class="codePanel"><div class="code-xml"><%#GenerateOperationMessages ("Soap", false)%></div></div>
<br/>
<% } %>
<% if (IsOperationSupported ("HttpGet")) { %>
<span class="label">HTTP Get</span>
<br/><br/>
<div class="codePanel"><div class="code-xml"><%#GenerateOperationMessages ("HttpGet", true)%></div></div>
<br/>
<div class="codePanel"><div class="code-xml"><%#GenerateOperationMessages ("HttpGet", false)%></div></div>
<br/>
<% } %>
<% if (IsOperationSupported ("HttpPost")) { %>
<span class="label">HTTP Post</span>
<br/><br/>
<div class="codePanel"><div class="code-xml"><%#GenerateOperationMessages ("HttpPost", true)%></div></div>
<br/>
<div class="codePanel"><div class="code-xml"><%#GenerateOperationMessages ("HttpPost", false)%></div></div>
<br/>
<% } %>
TODO
<% } %>
<%}%>
+2 -11
View File
@@ -1,15 +1,6 @@
monodir = $(sysconfdir)/mono
EXTRA_DIST = config.in \
machine.config \
DefaultWsdlHelpGenerator.aspx \
browscap.ini.gz
EXTRA_DIST = config.in machine.config DefaultWsdlHelpGenerator.aspx
mono_DATA = config \
machine.config \
DefaultWsdlHelpGenerator.aspx \
browscap.ini
browscap.ini: browscap.ini.gz
gunzip -c $^ > $@
mono_DATA = config machine.config DefaultWsdlHelpGenerator.aspx
Binary file not shown.
-1
View File
@@ -17,5 +17,4 @@
<dllmap dll="oci" target="clntsh" />
<dllmap dll="gtkhtml-3.0" target="libgtkhtml-3.0.so.2" />
<dllmap dll="db2cli" target="libdb2_36.so"/>
<dllmap dll="gstreamer" target="libgstreamer-0.6.so" />
</configuration>
-13
View File
@@ -21,8 +21,6 @@
type="System.Web.Configuration.GlobalizationConfigurationHandler, System.Web" />
<section name="sessionState"
type="System.Web.SessionState.SessionStateSectionHandler, System.Web" />
<section name="trace"
type="System.Web.Configuration.TraceConfigurationHandler, System.Web" />
<section name="webServices"
type="System.Web.Services.Configuration.WebServicesConfigurationSectionHandler, System.Web.Services" />
<section name="webControls"
@@ -31,10 +29,6 @@
type="System.Web.Configuration.CompilationConfigurationHandler, System.Web" />
<section name="httpRuntime"
type="System.Web.Configuration.HttpRuntimeConfigurationHandler, System.Web" />
<section name="customErrors"
type="System.Web.Configuration.CustomErrorsConfigHandler, System.Web" />
<section name="pages"
type="System.Web.Configuration.PagesConfigurationHandler, System.Web" />
</sectionGroup>
<sectionGroup name="system.net">
<section name="settings"
@@ -56,8 +50,6 @@
</connectionManagement>
<authenticationModules>
<add type="System.Net.BasicClient" />
<add type="System.Net.DigestClient" />
<add type="System.Net.NtlmClient" />
</authenticationModules>
<defaultProxy>
<proxy />
@@ -75,7 +67,6 @@
</system.net>
<system.web>
<httpHandlers>
<add verb="*" path="Trace.axd" type="System.Web.Handlers.TraceHandler, System.Web" />
<add verb="*" path="*.aspx" type="System.Web.UI.PageHandlerFactory, System.Web" />
<add verb="*" path="*.asmx" validate="false"
type="System.Web.Services.Protocols.WebServiceHandlerFactory, System.Web.Services" />
@@ -147,10 +138,6 @@
minFreeThreads="8"
minLocalRequestFreeThreads="4"
appRequestQueueLimit="100" />
<pages buffer="true"
enableSessionState="true"
autoEventWireup="true"
validateRequest="true" />
</system.web>
<system.runtime.remoting>
-16
View File
@@ -1,16 +0,0 @@
2004-01-22 Atsushi Enomoto <[email protected]>
* xml-classes : status update, additional infos.
2004-01-16 Atsushi Enomoto <[email protected]>
* web/commands : Added xml-classes (forgot to commit).
* mono-build-w32.sh : Added icu support as well as glib.
* ChangeLog : tiny fix
2004-01-11 Atsushi Enomoto <[email protected]>
* xml-classes : added v2 info. schema status updates.
Added ChangeLog. (There is no reason not to keep ChangeLog for
documents, at least for not a little changes ;-)
+4 -10
View File
@@ -47,7 +47,7 @@
<li><a href="http://www.go-mono.com/sqlclient.html">Microsoft SQL Server</a></li>
<li><a href="http://www.go-mono.com/sqlite.html">SQL Lite</a></li>
<li><a href="http://www.go-mono.com/sybase.html">Sybase</a></li>
<li><a href="http://www.go-mono.com/tdsclient.html">Older Microsoft SQL Server and Sybase databases</a></li>
<li><a href="http://www.go-mono.com/tdsclient.html">TDS Generic</a></li>
</ul>
<p>Providers which we do not have, but we would like to have. Currently,
@@ -333,12 +333,6 @@
<td>System.Data /</br> System.Data.SqlClient</td>
<td>SqlTest.cs at</br> System.Data/Test</td>
</tr>
<tr>
<td>PostgreSQL</br> (Npgsql)</td>
<td>Npgsql /</br> Npgsql</td>
<td>*.cs at</br> Npgsql/Test</td>
</tr>
<tr>
<td>PostgreSQL</br> (Mono)</td>
@@ -355,13 +349,13 @@
<tr>
<td>Oracle</br> (Mono)</td>
<td>System.Data.OracleClient /</br> System.Data.OracleClient</td>
<td>TestOracleClient.cs at</br> System.Data.OracleClient/Test</td>
<td>TestOracleClient.cs at</br> System.Data.OracleClient</td>
</tr>
<tr>
<td>ODBC</br> (Mono)</td>
<td>System.Data.Odbc /</br> System.Data</td>
<td>OdbcTest.cs (to connect to MS SQL Server)at</br> System.Data/Test</td>
<td>System.Data.OracleClient /</br> System.Data.OracleClient</td>
<td>TestOracleClient.cs at</br> System.Data.OracleClient</td>
</tr>
</table>
+1 -1
View File
@@ -21,7 +21,7 @@
<a href="http://primates.ximian.com/~martin/blog/rss.xml"><img align="center" src="images/xml.gif"></a>
<a href="http://primates.ximian.com/~martin/blog/">Martin Baulig</a>
<br>
<a href="http://primates.ximian.com/~miguel/miguel.rss2"><img align="center" src="images/xml.gif"></a>
<a href="http://primates.ximian.com/~miguel/miguel2.rss"><img align="center" src="images/xml.gif"></a>
<a href="http://primates.ximian.com/~miguel/activity-log.php">Miguel de Icaza</a>
<br>
<a href="http://primates.ximian.com/~mkestner/blog/index.rdf"><img align="center" src="images/xml.gif"></a>
+8 -19
View File
@@ -1,10 +1,10 @@
* Mono
* Mono Books
<a href="http://www.amazon.de/exec/obidos/ASIN/3827264928/qid=1050051051/sr=2-1/ref=sr_2_3_1/028-2755135-1623712">
Mono: .NET-kompatible Anwendungen mit dem Open Source-Framework
</a>
* C#
* C# Books
A Programmer's Introduction to C# - Second Edition: Eric Gunnerson
@@ -16,23 +16,8 @@
* Remoting
<a href="http://www.dotnetremoting.cc/book/AdvancedDotNetRemoting.asp">Advanced .NET Remoting: Ingo Rammer</a>
* Threading
.NET Multithreading: Alan L. Dennis (ISBN 1-930110-54-5)
* Web Services
Web Services: Architecture and Implementation with .NET: Keith Ballinger
* ASP.NET
Essential ASP.NET with Examples in C# by Fritz Onion
ASP.NET in a Nutshell by G. Andrew Duthie & Matthew MacDonald
Programming ASP.NET by Jessy Liberty & Dan Hurtwitz
<a href="http://www.dotnetremoting.cc/book/AdvancedDotNetRemoting.asp">
Advanced .NET Remoting: Ingo Rammer</a>
* Compiler Implementation
@@ -46,6 +31,10 @@
A Retargetable C Compiler - Design and Implementation: C. Fraser, David
Hanson
* Threading
.NET Multithreading: Alan L. Dennis (ISBN 1-930110-54-5)
* Reference Manuals
<a
+3 -10
View File
@@ -9,9 +9,9 @@
<ul>
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FClass+Libraries&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&newqueryname=&form_name=query&order=bugs.priority%2C%20bugs.bug_id">[Query]</> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FClass%20Libraries">[Add]</a> Class Libraries
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FCompilers&component=IL+assembler&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FCompilers&component=IL%20assembler">[Add]</a> IL Assembler.
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FAssembler&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FAssembler">[Add]</a> IL Assembler.
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FCompilers&component=C%23&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FCompilers&component=C%23">[Add]</a> C# Compiler.
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FMCS&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FMCS">[Add]</a> C# Compiler.
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FRuntime&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FRuntime">[Add]</a> Runtime
@@ -19,16 +19,9 @@
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=gtk%23&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=gtk%23">[Add]</a> Gtk#
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FClass+Libraries&component=System.Web&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FClass%20Libraries&component=System.Web">[Add]</a> ASP.NET WebForms
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FClass+Libraries&component=System.Web.Services&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FClass%20Libraries&component=System.Web.Services">[Add]</a> ASP.NET Web Services
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FDebugger&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FDebugger">[Add]</a> Debugger.
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono+Develop&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono+Develop">[Add]</a> Mono Develop.
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono+Tasks&product=Mono%2FClass+Libraries&product=Mono%2FCompilers&product=Mono%2FDebugger&product=Mono%2FDoctools&product=Mono%2FRuntime&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> All core components.
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FClass+Libraries&product=Mono%2FMCS&product=Mono%2FRuntime&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&order=%27Importance%27&form_name=query">[Query]</a> All core components.
</ul>
<a name="goodbugreport"/>
-71
View File
@@ -262,77 +262,6 @@
cvs commit file-1.cs file-2.cs
</pre>
* Using SVN
This is a small tutorial for using SVN (subversion).
For a more complete tutorial on subversion, look at
<a href="http://svnbook.red-bean.com/">the svn book</a>
or <a href="http://subversion.tigris.org">the svn homepage</a>
** Generating a key
Follow the cvs instructions above.
** Checking out the sources
To checkout the sources for the first time use the command:
Note: You should be running 0.35.1 (latest) of svn before attempting
anything here.
<pre>
svn co svn+ssh://mono-cvs.ximian.com/svn/monodevelop/trunk/MonoDevelop
</pre>
If you have a different username on mono-cvs and the local computer
you can do the following:
<pre>
svn co svn+ssh://[email protected]/svn/monodevelop/trunk/MonoDevelop
</pre>
before checking out.
** Updating your sources
You can update your repository to the latest copy of MonoDevelop by
running the following command:
<pre>
svn up
</pre>
from inside your repository.
** Committing your work
Before you commit anything, you should first update to the latest
sources by following the updating directions. After you are up to date
you need to run a:
<pre>
svn add filename
</pre>
for every file that you have created. You can get a list of these files
by running:
<pre>
svn status
</pre>
After all the files are added, run:
<pre>
svn commit
</pre>
to commit your changes.
** For more information
Look at the MonoDevelop website (coming soon)
* Keeping track of changes.
We provide two e-mail based mechanisms to keep track of
+11 -15
View File
@@ -7,22 +7,22 @@
the code, making the source quite difficult to read. Furthermore,
multilingual documentation makes for significant additional text.
With these considerations in mind, Mono is using external XML files
for class documentation, rather than documenting the source
With these considerations in mind, Mono will use external XML files
for type documentation, rather than documenting the source
inline. The XML file format used is inspired by the XML format used
to document the ECMA APIs.
Several tools exist for managing, verifying, generating,
and updating class library documentation.
The documentation infrastructure is part of the `Monodoc'
module. Monodoc includes a graphical GUI browser and tools to
generate the initial stubbed XML document out of an assembly.
Several tools will be created for managing, verifying, generating,
and updating class library documentation, including:
Download `monodoc' to start producing documentation for your
application.
<ul>
<li><a href="#monodoc">monodoc - A graphical documentation viewer.</a></li>
For instructions, read the monodoc/README file.
<li>xmllint: a tool used to validate a proper XML document.
</ul>
You can download the tools to document Mono from the CVS
repository from module `monodoc'.
** Documentation Tools
@@ -43,7 +43,3 @@
Help us develop Mono's documentation tools! Subscribe to
<a href="http://lists.ximian.com/mailman/listinfo/mono-docs-list">mono-docs-list</a>
and wade right in.
Monodoc today also supports a GUI-based collaborative editing
system. You can now edit the documentation from the browser
and upload your contributions directly to the Mono site.
-235
View File
@@ -1,235 +0,0 @@
* Compiling Mono
This document describes how to compile and install Mono from
its source code. If you are only interested in running Mono,
you might want to install Mono from packages, which have been
tested.
The core of Mono is split in two components:
<ul>
* C components (available in the mono package)
* C# components (available in the mcs package).
</ul>
Mono is also available in various forms:
<dl>
<dt>Officially <a href="download.html">released</a> packages.</dt>
<dd>
<p>This is the format of choice for people to use, since these
have been tested and are known to build and work.
</dd>
<dt><a href="daily">Daily</a> packages.</dt>
<dd>
<p>This is a service offered for people who want to try out the
daily changes. Baked daily.</dd>
<dt>CVS source code.</dt>
<dd>
<p>These are available to Mono <a href="ccvs.html">developers</a> and
also for enthusiasts through <a href="anoncvs.html">anonymous CVS</a>.
</dd>
<dt>CVS snapshots.</dt>
<dd>
<p>Available for curious developers which do not necessarily want to
install the CVS source. Baked daily.
</dd>
</dl>
* Compiling the code
There are a number of ways of compiling Mono
<ul>
<li>From the <a href="#scripts">scripts</A>
<LI><a href="#install">Manually</a> for the first time.
<li>Manually, <a href="#upgrade">while upgrading</a> to CVS
</ul>
(which is an easy way to get the latest CVS information)
<a name="scripts">
* Compiling with scripts
These scripts should be used for installing from packages, specially
on Windows, where dependencies have not always been installed.
There are scripts to help build mono for both Unix and Windows. Get
<a href="mono-build.sh">mono-build.sh</a> for Unix, or <a
href="mono-build-w32.sh">mono-build-w32.sh</a> for Windows.
These scripts automate the installation of GLIB and pkgconfig
(building from source on Unix, and using binary packages
provided by the GIMP for Windows project on Windows.) To use
the script, follow these simple steps:
<ul>
* Save the script for your platform somewhere (e.g. /usr/local/bin)
* Make the script executable (i.e chmod 755 /usr/local/bin/mono-build.sh)
* Create a directory to hold the mono source, and the compiled binaries (e.g. mkdir ~/mono)
* Change to the new directory (i.e. cd ~/mono)
* run the script (i.e. /usr/local/bin/mono-build.sh)
</ul>
The script requires wget on either platform, and building the
software requires make, gcc, automake, autoconf, and libtool.
You should install these packages from your distribution or
with the cygwin installer. You should also take care of setting
the right environment variables as the PKG_CONFIG_FLAGS, etc.
The script will download required packages from
www.go-mono.com and do a cvs checkout of mono in the current
directory. <b>IMPORTANT!:</b> The cvs server chosen defaults to
anonymous cvs;
set your CVSROOT environment variable before running the script to
select a particular cvs server.
<a name="install">
** Building the software manually
You will need to obtain the Mono dependencies first: <a
href="http://www.gtk.org">glib 2.x</a> and
<a href="http://www.freedesktop.org/software/pkgconfig">pkg-config</a>.
*** Building From Packages
This applies to both the officially released packages, as well as the
daily tarball packages.
<ul>
Unpack the Mono runtime distribution:
<pre class="shell">
tar xzvf mono-X.XX.tar.gz
cd mono-X.XX</pre>
<p>
Then configure, compile and install:
<pre class="shell">
./configure --prefix=/usr/local
make
make install</pre>
This will give you a runtime, C# compiler and runtime
libraries.
If you want to recompile the runtime and the compiler,
follow these steps, first unpack the MCS package:
<pre class="shell">
tar xzvf mcs-X.XX.tar.gz</pre>
Then use the following command to compile and install:
<pre class="shell">
./configure --profile=atomic
make</pre>
You can change /usr/local to something else if you want.
</ul>
*** Building from CVS
To upgrade your Mono installation from CVS, it is very
important that you update your Mono and MCS modules from CVS
at the same time. Failure to do so might result in a
problematic installation as the runtime and the class
libraries will be out of sync.
Run the following commands to update your CVS tree (more
details in <a href="ccvs.html">Cvs and Mono</a> and the <A
href="anoncvs.html">AnonCVS and Mono</a> pages).
<pre>
(cd mono; cvs update -dP .)
(cd mcs; cvs update -dP .)
</pre>
Then you can run:
<pre>
(cd mono; make fullbuild)
</pre>
Now you can install the result:
<pre>
(cd mono; make install)
</pre>
Notice that following the above procedure does not require you
to manually install the software in the `mcs' directory, as
the relevant files will be copied by the `mono' makefiles.
* Software resources and notes
The required and additional software can be downloaded here:
* Microsoft's .NET Framework SDK from
<a href="http://msdn.microsoft.com/downloads">
msdn.microsoft.com/downloads</a>.
* Cygwin and the GNU Make tools from
<a href="http://www.cygwin.com">www.cygwin.com</a>.
Some people observed problems with autoconf 2.52. Installing
autoconf 2.13 helped in those cases.
* Precompiled GLIB 2.0 and pkg-config packages (and
their dependencies) by the <a href="http://www.gimp.org/~tml/gimp/win32//index.html">GIMP for Windows</a> project from
<a href="http://www.go-mono.com/archive/pkgconfig-0.11-20020310.zip">http://www.go-mono.com/archive/pkgconfig-0.11-20020310.zip</a><br>
<a href="http://www.go-mono.com/archive/glib-2.0.4-20020703.zip">http://www.go-mono.com/archive/glib-2.0.4-20020703.zip</a> <br>
<a href="http://www.go-mono.com/archive/glib-dev-2.0.4-20020703.zip">http://www.go-mono.com/archive/glib-dev-2.0.4-20020703.zip</a> <br>
<a href="http://www.go-mono.com/archive/libiconv-1.7.zip">http://www.go-mono.com/archive/libiconv-1.7.zip</a> <br>
<a href="http://www.go-mono.com/archive/libiconv-dev-1.7.zip">http://www.go-mono.com/archive/libiconv-dev-1.7-20020101.zip</a> <br>
<a href="http://www.go-mono.com/archive/libintl-0.10.40-20020101.zip">http://www.go-mono.com/archive/libintl-0.10.40-20020101.zip</a><br>
* Download the Mono source code from the
<a href="download.html">packaged versions</a> or
the <a href="http://www.go-mono.com/snapshots">
nightly snapshots</a> or the <a href="anoncvs.html">
Anonymous CVS</a>. The nightly snapshots are done every
night at 10pm EST (Boston Time). The nightly snapshots are
not guaranteed to build, but most of the time they should.
</ul>
*** Notes on compiling GLIB 2.0 and pkg-config from source:
<ul>
* Some people observed problems with autoconf 2.52. Installing
autoconf 2.13 helped in those cases (don't forget to do a
`make maintainer-clean' after the update).
* Download, compile and install <a href="http://www.freedesktop.org/software/pkgconfig">pkg-config</a> from source.
(I had to change line 674 of
<nobr><tt>pkg-config-0.8.0/glib-1.2.8/gstrfuncs.c</tt></nobr> from
<nobr><tt>extern char *strsignal (int sig);</tt></nobr> to
<nobr><tt>extern const char *strsignal (int sig);</tt></nobr>.
<pre class="shell">
tar xzvf pkg-config-0.8.0.tar.gz
cd pkg-config-0.8.0
./configure --prefix=/usr
make
make install
</pre>
* Download, compile and install <a href="ftp://ftp.gnu.org/pub/gnu/libiconv/libiconv-1.7.tar.gz">libiconv</a> from source.<br>
If you dont have MS Visual C/C++ 4.0 or 5.0 or 6.0 you can also try
the binary package available at <a
href="http://www.gimp.org/~tml/gimp/win32/libiconv-1.9.1.bin.woe32.zip">
http://www.gimp.org/~tml/gimp/win32/libiconv-1.9.1.bin.woe32.zip</a>
* Download, compile and install the
<a href="ftp://ftp.gtk.org/pub/gtk/v2.0/glib-2.0.6.tar.gz">
glib 2.0</a> from source.
</ul>
+21 -13
View File
@@ -11,15 +11,25 @@
**** Status
<ul>
* All classes are present.
* Every classes are present.
* Most classes have their unit tests. Some tests like <code>
SymmetricAlgorithmTest</code> are generated by external
tools.
* MACTripleDES is compatible with the implementation shipped in
framework 1.0. Version 1.1 gives different results when the
MACed data is a multiple of BlockSize (8 bytes).
</ul>
**** TODO
<ul>
* RNGCryptoServiceProvider is currently only working on Linux.
The current implementation reside in Mono's runtime and use
the <code>/dev/[u]random</code> device (which do not exists
under Windows). A Windows specific alternative is available
using the Mono.Security.Win32 assembly.
* Keypair persistance for RSA and DSA. This persistance must
somehow be linked with X509 certificate stores (in planning).
@@ -35,8 +45,8 @@
<ul>
* All cryptographic algorithms are entirely managed, including
classes named <code>*CryptoServiceProvider</code>, with the
exception of <code>RNGCryptoServiceProvider</code> for which
parts of the implementation resides in the runtime.
exception of <code>RNGCryptoServiceProvider</code> (which
implementation resides in the runtime).
* There is a bug in the <code>PKCS1MaskGenerationMethod</code>
class (in both framework 1.0 and 1.1). This means our
@@ -135,19 +145,16 @@
</ul>
*** Namespace: Mono.Security.Cryptography
<ul>
* Additional algorithms: MD2, MD4, ARCFOUR (required for SSL)
* Additional algorithms: MD2, ARCFOUR (required for SSL)
* Convertion helpers
</ul>
*** Namespace: Mono.Security.Protocol.*
*** Namespace: Mono.Security.Protocol.Tls
<ul>
* Tls: An 100% managed TLS implementation from Carlos Guzman
Alvarez.
* Ntlm: NTLM authentication (used for HTTP and SQL Server).
* An 100% managed TLS implementation from Carlos Guzman Alvarez.
</ul>
*** Namespace: Mono.Security.X509
<ul>
* X.509 structures (certificate, CRL...) building and decoding.
* PKCS#12 decoding.
</ul>
*** Namespace: Mono.Security.X509.Extensions
<ul>
@@ -377,8 +384,9 @@
<b>monodoc</b> as I'm not a very good writer (at least in English).
</ul>
Contact <a href="mailto:[email protected]">Sebastien Pouliot</a> if
you need additional informations about the status of the cryptographic
classes.
Contact Sebastien Pouliot (<a href="mailto:[email protected]">home</a>
, <a href="mailto:[email protected]">work</a>) if you need additional
informations about the status of the cryptographic classes.
<hr>
Last reviewed: January 26, 2004 (post mono 0.29)
Last reviewed: October 26, 2003 (post mono 0.28)
+258 -57
View File
@@ -13,55 +13,6 @@
section</a>, the <a
href="http://www.go-mono.org/faq.html">FAQ</a>.
<table>
<tbody>
<tr bgcolor="#DDDDDD">
<td>
<b>Release 0.29</b><br>
<a href="archive/mono-0.29.html">Release notes</a><br>
Dec 2nd, 2003
</td>
<td>
<table cellspacing="1" cellpadding="3">
<tr bgcolor="#BBBBBB">
<td>
<b>Source Code</b>
</td>
<td>
<ul>
<li><a href="archive/mcs-0.29.tar.gz">Mono Class Libraries and C# Compiler.</a>
<li><a href="archive/mono-0.29.tar.gz">Mono Runtime</a>
<li><a href="archive/xsp-0.8.tar.gz">XSP web server (0.8)</a>
<li><a href="archive/mod_mono-0.6.tar.gz">Apache Mono module 0.6 (mod_mono)</a>
<li><a href="archive/monodoc-0.9.tar.gz">MonoDoc 0.9</a>
</ul>
</td>
</tr>
<tr bgcolor="#bbbbbb">
<td bgcolor="#999999">
<img src="images/redhat-36.gif"><b>Red Hat 8.0, Red Hat 9.0/x86</b><br>
<img src="images/mandrake-36.gif"><b>Mandrake 9.1/x86</b><br>
<img src="images/suse-36.gif"><b>SuSE 8.2</b><br>
</td>
<td>
Packages are available on <a
href="http://www.ximian.com/products/redcarpet/download.html">Red
Carpet's</a> Mono channel.
</td>
</tr>
<tr>
<td bgcolor="#999999">
<img src="images/windows-36.gif"><b>Windows installer</b>
</td>
<td>
<a href="archive/mono-0.29-win32-1.exe">mono-0.29-win32-1.exe</a>
</td>
</tr>
</table>
</td>
</table>
<table>
<tbody>
<tr bgcolor="#DDDDDD">
@@ -94,7 +45,7 @@
<td>
<ul>
<li><a href="archive/redhat-90-i386/mono-0.28-1.ximian.6.1.src.rpm">mono-0.28-1.src.rpm (RH9)</a>
<li><a href="archive/redhat-90-i386/mono-0.28-1.ximian.6.1.src.rpm">mono-0.28-1.src.rpm (RH8)</a>
<li><a href="archive/redhat-90-i386/mono-0.28-1.ximian.5.1.src.rpm">mono-0.28-1.src.rpm (RH8)</a>
</ul>
</td>
</tr>
@@ -193,7 +144,7 @@
<td>
<ul>
<li><a href="archive/redhat-90-i386/mono-0.26-1.ximian.6.1.src.rpm">mono-0.26-1.src.rpm (RH9)</a>
<li><a href="archive/redhat-90-i386/mono-0.26-1.ximian.6.1.src.rpm">mono-0.26-1.src.rpm (RH8)</a>
<li><a href="archive/redhat-90-i386/mono-0.26-1.ximian.5.1.src.rpm">mono-0.26-1.src.rpm (RH8)</a>
</ul>
</td>
</tr>
@@ -220,7 +171,7 @@
<li><a href="archive/redhat-90-i386/monodoc-0.6-1.ximian.6.1.i386.rpm">monodoc-0.6-1.ximian.6.1.i386.rpm</a> (To be used only with CVS gtk-sharp)
<li><a href="archive/redhat-90-i386/monodoc-debuginfo-0.5-1.ximian.6.1.i386.rpm">monodoc-debuginfo-0.5-1.ximian.6.1.i386.rpm</a>
<li><a href="archive/redhat-90-i386/mono-wine-20030318-1.ximian.6.3.i386.rpm">mono-wine-20030318-1.ximian.6.3.i386.rpm</a>
<li><a href="archive/redhat-90-i386/mono-wine-debuginfo-20030318-1.ximian.6.3.i386.rpm">mono-wine-debuginfo-20030318-1.ximian.6.3.i386.rpm</a>
<li><a href="archive/redhat-90-i386/mono-wine-debuginfo-20030318-1.ximian.6.2.i386.rpm">mono-wine-debuginfo-20030318-1.ximian.6.3.i386.rpm</a>
</ul>
</td>
<td bgcolor="#999999">
@@ -300,7 +251,7 @@
</td>
<td>
<ul>
<li><a href="archive/redhat-80-i386/mono-0.25-1.ximian.5.1.src.rpm">mono-0.25-1.src.rpm</a>
<li><a href="archive/mono-0.25-1.ximian.5.src.rpm">mono-0.25-1.src.rpm</a>
</ul>
</td>
</tr>
@@ -855,7 +806,7 @@
<td>
<ul>
<li><a href="archive/libgc-6.1-1.src.rpm">libgc-6.1-1.src.rpm</a>
<li><a href="archive/redhat-73-i386/mono-0.20-1.src.rpm">mono-0.20-1.src.rpm</a>
<li><a href="archive/mono-0.20-1.src.rpm">mono-0.20-1.src.rpm</a>
</ul>
</td>
</tr>
@@ -1169,6 +1120,7 @@
<ul>
* <a href="http://www.debianplanet.org/mono/">DebianPlanet</a>
* <a href="http://www.superin.formativ.net/mono/mono.htm">Windows</a> (works without cygwin!)
</ul>
* Snapshots
@@ -1183,7 +1135,256 @@
The <a href="anoncvs.html">anoncvs</a> mirrors provided by
Hispalinux are updated every six hours.
* Compilation
* Compiling the code
For instructions on how to build Mono, please refer to the
<a href="compiling.html">compiling</a> page.
There are a number of ways of compiling Mono
<ul>
<li>From the <a href="#scripts">scripts</A>
<LI><a href="#install">Manually</a> for the first time.
<li>Manually, <a href="#upgrade">while upgrading</a> to CVS
</ul>
(which is an easy way to get the latest CVS information)
<a name="scripts">
* Compiling with scripts
There are scripts to help build mono for both Unix and Windows. Get
<a href="mono-build.sh">mono-build.sh</a> for Unix, or <a
href="mono-build-w32.sh">mono-build-w32.sh</a> for Windows.
These scripts automate the installation of GLIB and pkgconfig
(building from source on Unix, and using binary packages
provided by the GIMP for Windows project on Windows.) To use
the script, follow these simple steps:
<ul>
* Save the script for your platform somewhere (e.g. /usr/local/bin)
* Make the script executable (i.e chmod 755 /usr/local/bin/mono-build.sh)
* Create a directory to hold the mono source, and the compiled binaries (e.g. mkdir ~/mono)
* Change to the new directory (i.e. cd ~/mono)
* run the script (i.e. /usr/local/bin/mono-build.sh)
</ul>
The script requires wget on either platform, and building the
software requires make, gcc, automake, autoconf, and libtool.
You should install these packages from your distribution or
with the cygwin installer. You should also take care of setting
the right environment variables as the PKG_CONFIG_FLAGS, etc.
The script will download required packages from
www.go-mono.com and do a cvs checkout of mono in the current
directory. <b>IMPORTANT!:</b> The cvs server chosen defaults to
anonymous cvs;
set your CVSROOT environment variable before running the script to
select a particular cvs server.
<a name="install">
** Building the software manually
You will need to obtain the Mono dependencies first: <a
href="http://www.gtk.org">glib 2.x</a> and
<a href="http://www.freedesktop.org/software/pkgconfig">pkg-config</a>.
*** Building on Linux
<ul>
Unpack the Mono runtime distribution:
<pre>
tar xzvf mono-X.XX.tar.gz
cd mono-X.XX
</pre>
<p>
Then configure, compile and install:
<pre>
./configure --prefix=/usr/local
make
make install</pre>
This will give you a runtime, C# compiler and runtime
libraries.
If you want to recompile the runtime and the compiler,
follow these steps, first unpack the MCS package:
<pre>
tar xzvf mcs-X.XX.tar.gz
cd mcs-X.XX
</pre>
Then use the following command to compile and install:
<pre>
make -f makefile.gnu install prefix=/usr/local
</pre>
You can change /usr/local to something else if you want.
</ul>
*** On Windows, to install and work on the compiler and the class libraries:
**** Install Cygwin and the GNU build tools, Microsoft's .NET Framework SDK and the precompiled GLIB 2.0 and pkg-config libraries.
<ul>
* Install <a href="http://www.cygwin.com">Cygwin</a>.
* Install <a href="http://msdn.microsoft.com/downloads">
Microsoft .NET Framework SDK</a>.
* Change to the /usr/local directory
of your Cygwin installation.<br>
Unzip the precompiled packages listed above.
</ul>
<ul>
* If you downloaded the Mono
<a href="http://www.go-mono.com/snapshots">nightly snapshot
</a>, untar the snapshot.
* Change directories to "mcs".
* Compile:
<pre>
make
</pre>
</ul>
*** On Windows, to compile the mono runtime:
<ul>
* If you downloaded the Mono
<a href="http://www.go-mono.com/snapshots">nightly snapshot
</a>, untar the snapshot.
* Change directories to "mono".
* Configure, compile and install:
<pre>
./configure --prefix=c:/mono
make
make install
</pre>
</ul>
* Software resources and notes
The required and additional software can be downloaded here:
* Microsoft's .NET Framework SDK from
<a href="http://msdn.microsoft.com/downloads">
msdn.microsoft.com/downloads</a>.
* Cygwin and the GNU Make tools from
<a href="http://www.cygwin.com">www.cygwin.com</a>.
Some people observed problems with autoconf 2.52. Installing
autoconf 2.13 helped in those cases.
* Precompiled GLIB 2.0 and pkg-config packages (and
their dependencies) by the <a href="http://www.gimp.org/~tml/gimp/win32//index.html">GIMP for Windows</a> project from
<a href="http://www.go-mono.com/archive/pkgconfig-0.11-20020310.zip">http://www.go-mono.com/archive/pkgconfig-0.11-20020310.zip</a><br>
<a href="http://www.go-mono.com/archive/glib-2.0.4-20020703.zip">http://www.go-mono.com/archive/glib-2.0.4-20020703.zip</a> <br>
<a href="http://www.go-mono.com/archive/glib-dev-2.0.4-20020703.zip">http://www.go-mono.com/archive/glib-dev-2.0.4-20020703.zip</a> <br>
<a href="http://www.go-mono.com/archive/libiconv-1.7.zip">http://www.go-mono.com/archive/libiconv-1.7.zip</a> <br>
<a href="http://www.go-mono.com/archive/libiconv-dev-1.7.zip">http://www.go-mono.com/archive/libiconv-dev-1.7-20020101.zip</a> <br>
<a href="http://www.go-mono.com/archive/libintl-0.10.40-20020101.zip">http://www.go-mono.com/archive/libintl-0.10.40-20020101.zip</a><br>
* Download the Mono source code from the
<a href="#feb-11">packaged versions</a> or
the <a href="http://www.go-mono.com/snapshots">
nightly snapshots</a> or the <a href="anoncvs.html">
Anonymous CVS</a>. The nightly snapshots are done every
night at 10pm EST (Boston Time). The nightly snapshots are
not guaranteed to build, but most of the time they should.
</ul>
*** Notes on compiling GLIB 2.0 and pkg-config from source:
<ul>
* Some people observed problems with autoconf 2.52. Installing
autoconf 2.13 helped in those cases (don't forget to do a
`make maintainer-clean' after the update).
* Download, compile and install <a href="http://www.freedesktop.org/software/pkgconfig">pkg-config</a> from source.
(I had to change line 674 of
<nobr><tt>pkg-config-0.8.0/glib-1.2.8/gstrfuncs.c</tt></nobr> from
<nobr><tt>extern char *strsignal (int sig);</tt></nobr> to
<nobr><tt>extern const char *strsignal (int sig);</tt></nobr>.
<pre>
tar xzvf pkg-config-0.8.0.tar.gz
cd pkg-config-0.8.0
./configure --prefix=/usr
make
make install
</pre>
* Download, compile and install <a href="ftp://ftp.gnu.org/pub/gnu/libiconv/libiconv-1.7.tar.gz">libiconv</a> from source.<br>
If you dont have MS Visual C/C++ 4.0 or 5.0 or 6.0 you can also try
the binary package available at <a
href="http://www.gimp.org/win32/libiconv-dev-20001007.zip">
http://www.gimp.org/win32/libiconv-dev-20001007.zip</a>.
* Download, compile and install the
<a href="ftp://ftp.gtk.org/pub/gtk/v2.0/glib-2.0.6.tar.gz">
glib 2.0</a> from source.
</ul>
<a name="upgrading">
** Upgrading
To upgrade your Mono installation from CVS, it is very
important that you update your Mono and MCS modules from CVS
at the same time. Failure to do so might result in a
problematic installation as the runtime and the class
libraries will be out of sync.
Run the following commands to update your CVS tree (more
details in <a href="ccvs.html">Cvs and Mono</a> and the <A
href="anoncvs.html">AnonCVS and Mono</a> pages).
<pre>
(cd mono; cvs update -dP .)
(cd mcs; cvs update -dP .)
</pre>
Once you have updated your sources, remove any cached
assemblies or old binaries from the Mono "runtime" directory,
and then compile each component:
<pre>
(cd mono/runtime; rm *exe *dll)
(cd mono; make)
(cd mcs; make)
</pre>
Now you can install the result:
<pre>
(cd mono; make install)
</pre>
Notice that following the above procedure does not require you
to manually install the software in the `mcs' directory, as
the relevant files will be copied by the `mono' makefiles.
+5 -13
View File
@@ -11,24 +11,16 @@
similar to the PDF 1.4 composition-based imaging model.
Our implementation is a C# wrapper around the GDI+ C API (also
called the <a
href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/gdicpp/GDIPlus/GDIPlusReference.asp">"GDI+
Flat API"</a>).
This means that the C# code is the same for Windows and Unix
systems. The following graph explains the situation:
called the "GDI+ Flat API").
<center>
<img src="images/system-drawing.png">
</center>
In Windows Mono uses the GDI+ library that is included with
the operating system (<tt>GDIPLUS.DLL</tt>, while in Unix we
provide an implementation of this API in the
<tt>libgdiplus.so</tt> shared library. Our
<tt>libgdiplus.so</tt> has the same C Flat API as the
<tt>GDIPLUS.DLL</tt>. Our implementation uses Cairo to do
the heavy lifting.
In Windows Mono uses the GDI+ library that is included
with the operating system, while in Unix we provide an
implementation of this API which uses Cairo to do the heavy
lifting.
The implementation of GDI+ lives in mcs/class/System.Drawing
in the gdiplus directory and requires <a
+7 -8
View File
@@ -23,8 +23,8 @@
<a href="#problems">Mono Common Problems</a><br>
A <a
href="http://www.monohispano.org/tutoriales/mono-puf//">Spanish
translation</a> is also available (it is outdated though)
href="http://www.es.gnome.org/documentacion/articulos/mono-puf/mono-puf/">Spanish
translation</a> is also available
<a name="basics"></a>
** Basics
@@ -353,7 +353,7 @@ A: As long as your applications are 100% .NET and do not make use
Q: Where can I learn more about Gtk#?
A: The following <a href="http://gtk-sharp.sourceforge.net">link</a> sends you to the page of the project.
A: The following <a href="http://gtk-sharp.sourceforge.net>link</a> sends you to the page of the project.
Q: What can I do with Gtk#?.
@@ -760,7 +760,7 @@ Q: What about Soup? Can I use Soup without Mono?
A: Soup is a library for GNOME applications to create SOAP servers and
SOAP clients, and can be used without Mono. You can browse the
source code for soup using <a
href="http://cvs.gnome.org/bonsai/">GNOME's Bonsai</a>.
href="http://cvs.gnome.org/bonsai">GNOME's Bonsai</a>.
Q: Can I use CORBA?
@@ -1053,13 +1053,12 @@ Q: Why don't you use Java? After all, there are many languages that
A: You can get very good tools for doing Java development on free
systems right now. <a href="http://www.redhat.com">Red Hat</a> has
contributed a <a href="http://gcc.gnu.org">GCC</a> <a
href="http://gcc.gnu.org/java/">front-end for Java</a> that can take
href="http://gcc.gnu.org/java">front-end for Java</a> that can take
Java sources or Java byte codes and generate native executables; <a
href="http://www.google.com/search?q=transvirtual">Transvirtual</a>
implemented
href="http://www.transvirtual.com">Transvirtual</a> has implemented
<a href="http://www.kaffe.org">Kaffe</a> a JIT engine for Java;
Intel also has a Java VM called <a
href="http://www.intel.com/research/mrl/orp/">ORP</a>.
href="http://www.intel.com/research/mrl/orp">ORP</a>.
The JVM is not designed to be a general purpose virtual machine.
The Common Intermediate Language (CIL), on the other hand, is
+6 -1
View File
@@ -21,7 +21,7 @@
** Where to learn more.
Visit the official site for the <a href="http://gtk-sharp.sourceforge.net">Gtk# Project</a>.
The <a href="http://www.go-mono.org/faq.html">Mono FAQ</a> has some useful
The <a href="http://www.go-mono.org/faq">Mono FAQ</a> has some useful
information too.
** GTK# On Linux
@@ -75,6 +75,11 @@ following:
<li>Microsoft .NET Framework at
<a href="http://msdn.microsoft.com/downloads/default.asp?url=/downloads/sample.asp?url=/msdn-files/027/000/976/msdncompositedoc.xml&frame=true">here</a> </li>
<p>If you are running Windows 95/98/ME, then you will need Unicode support.
Look in
mono-list archives for information about how to get
Mono to work on Windows 9x.
<a href="http://lists.ximian.com/archives/public/mono-list/2002-December/004158.html">here</a>
<p>Environment Variables to set:
<ul>
+2 -2
View File
@@ -49,14 +49,14 @@ In order to test.
<li>Have working mono and mcs setup</li>
<li>Have access to an IBM DB2 database. If you do not have access, download the
<a href="http://www-306.ibm.com/software/data/db2/">IBM DB2</a> software. There
<a href="http://www-3.ibm.com/software/data/db2/">IBM DB2</a> software. There
are versions for Windows, Linux, AIX, and Sun Solaris.</li>
<li>Make sure the assembly Mono.Data.DB2Client.dll was built and installed
where the other class libraries are installed.</li>
<li>If you do not have the source to mcs, get the source from
<a href="http://www.go-mono.com/download.html">here</a></li>
<a href="http://www.go-mono.com/download">here</a></li>
<li>Has a ConnectionString format like ODBC</li>
+982 -62
View File
File diff suppressed because it is too large. Load diff
+11 -12
View File
@@ -34,7 +34,7 @@
* <a href="#python">Python</a>
</ul>
<a name="Java"></a>
<a name="Java">
** Java
There is a very interesting project to make a JavaVM for .NET
@@ -78,6 +78,9 @@
Examples:
<a href="http://www.oberon.ethz.ch/oberon.net/examples/">http://www.oberon.ethz.ch/oberon.net/examples/</a>
<a href="http://www.superin.formativ.net/mono/oberon/oberon.zip">http://www.superin.formativ.net/mono/oberon/oberon.zip</a>
<a name="ComponentPascal">
** Component Pascal
@@ -90,8 +93,9 @@
<a name="Forth">
** Delta Forth
The Delta Forth.NET project: <a href="http://www.dataman.ro/dforth">Home
Page</a> and <a href="http://www.dataman.ro/dforth">more
The Delta Forth.NET project: <a
href="www.dataman.ro/dforth">Home
Page</a> and <a href="http://www.dataman.ro/dforth/index.html">more
details here</a>.
@@ -101,15 +105,17 @@
A subset of Scheme language called <a
href="http://radio.weblogs.com/0101156/stories/2002/03/19/tachy.html">Tachy</a>
<a name="Python"></a>
<a name="Python">
** Python
<a href="mailto:[email protected]">Brian Lloyd</a> is
working on linking the Python runtime with the .NET runtime.
More information on the PS.NET project can be found <a
href="http://www.zope.org/Members/Brian/PythonNet">here</a>.
An FAQ document is available <a
href="http://www.zope.org/Members/Brian/PythonNet/FAQ.html">here</a>.
<a name="dotlisp"></a>
<a name="dotlisp">
** dotLisp
DotLisp is available from: <a
@@ -143,13 +149,6 @@
LCC is not an open source compiler, but it is free as long as you
do not profit from selling it.
<a name="ada"></a>
* ADA
A# is an ADA compiler for the CIL platform, it can be downloaded from:
<a
href="http://www.usafa.af.mil/dfcs/bios/mcc_html/a_sharp.html">http://www.usafa.af.mil/dfcs/bios/mcc_html/a_sharp.html</a>
<a name="Java">
* Java
+1 -10
View File
@@ -126,15 +126,6 @@
Used to discuss the Gtk bindings for Mono (<a href="http://gtk-sharp.sf.net">Gtk#</a>).
</td>
</tr>
<tr>
<td>
<b><a
href="http://lists.ximian.com/mailman/listinfo/mono-vb">mono-vb</a></b>
</td>
<td>
Mono's implementation of Visual Basic.NET.
</td>
</tr>
</table>
Other mailing lists of interest:
@@ -159,7 +150,7 @@
<table>
<tr>
<td><a href="http://www.google.com/search"><img src="images/Logo_40wht.gif" border="0" alt="Google" align="middle"></a></td>
<td><a href="http://www.google.com/search"><img src="mailing-lists_files/Logo_40wht.gif" border="0" alt="Google" align="middle"></a></td>
<td>
<table>
+13 -28
View File
@@ -59,13 +59,11 @@ else
echo "Automake version new enough."
fi
# This causes libgc-not-found problem
#
## Select the stable version anyway...
#if [ ! -z "${AUTO_STABLE}" -o -e /usr/autotool/stable ]; then
# export AUTO_STABLE=${AUTO_STABLE:-/usr/autotool/stable}
# export AUTO_DEVEL=${AUTO_STABLE}
#fi
# Select the stable version anyway...
if [ ! -z "${AUTO_STABLE}" -o -e /usr/autotool/stable ]; then
export AUTO_STABLE=${AUTO_STABLE:-/usr/autotool/stable}
export AUTO_DEVEL=${AUTO_STABLE}
fi
# Need to install pkgconfig and set ACLOCAL_FLAGS if there is not a
# pkgconfig installed already. Otherwise set PKG_CONFIG_PATH to the
@@ -100,15 +98,6 @@ function aclocal_scan () {
return 1
}
function install_icuconfig() {
if [ ! -f $here/install/bin/icu-config ]; then
wget http://www.go-mono.com/archive/icu-config
mv icu-config $here/install/bin
chmod 755 $here/install/bin/icu-config
fi
}
function install_package() {
zipfile=$1
markerfile=$2
@@ -134,13 +123,11 @@ else
install_pkgconfig=yes
fi
# This causes libgc-not-found problem
#
## But we still need to use the mingw libs for glib & co
#ACLOCAL_FLAGS="-I $here/install/share/aclocal $ACLOCAL_FLAGS"
# But we still need to use the mingw libs for glib & co
ACLOCAL_FLAGS="-I $here/install/share/aclocal $ACLOCAL_FLAGS"
#export PATH
#export ACLOCAL_FLAGS
export PATH
export ACLOCAL_FLAGS
# Grab pkg-config, glib etc
if [ ! -d $here/install ]; then
@@ -159,9 +146,6 @@ install_package glib-dev-2.0.4-20020703.zip lib/glib-2.0.lib glib-dev
install_package libiconv-1.7.zip lib/iconv.dll iconv
install_package libintl-0.10.40-20020101.zip lib/libintl-1.dll intl
install_package libgc-dev.zip lib/gc.dll gc-dev
install_package icu-2.6.1-Win32_msvc7.zip icu/bin/icuuc26.dll icu
install_icuconfig
if [ $install_pkgconfig = "no" ]; then
echo "Fixing up the pkgconfig paths"
@@ -174,9 +158,10 @@ if [ $install_pkgconfig = "no" ]; then
fi
# Needed to find the libgc bits
export CFLAGS="-I $here/install/include -I $here/install/icu/include"
export LDFLAGS="-L$here/install/lib -L$here/install/icu/lib"
export PATH="$here/install/icu/bin:$PATH"
CPPFLAGS="$CPPFLAGS -I$here/install/include"
LDFLAGS="$LDFLAGS -L$here/install/lib"
export CPPFLAGS
export LDFLAGS
# Make sure we build native w32, not cygwin
#CC="gcc -mno-cygwin"
-2
View File
@@ -73,8 +73,6 @@ vertical-align: top;
<p>
</center>
<i>Last update: Jan 18th, 2004</i>
<h3>Introduction</h3>
<p>This document describes the high-level roadmap for <a
+8 -109
View File
@@ -4,10 +4,10 @@
on the mailing list what they can help with. The generic
answer is always:
<ul>
<li> Write documentation.
<li> Write regression tests.
<li> Complete the implementations of the class libraries.
<li> Help fix the bugs filed in our bugzilla database.
* Write documentation.
* Write regression tests.
* Complete the implementations of the class libraries.
* Help fix the bugs filed in our bugzilla database.
</ul>
The proposed tasks are very important for the Mono project and
@@ -91,7 +91,7 @@ Happy hacking!
by the MS runtime.
<td>Medium-hard (thesis subject)
<td>2-4 months
<td><a href="http://bugzilla.ximian.com/show_bug.cgi?id=52605">52605</a>
<td>not assigned
</tr>
<tr>
@@ -126,13 +126,13 @@ Happy hacking!
support the generics requirements.
<td>Medium-hard
<td>2-3 months
<td>lupus and Martin
<td>not assigned
</tr>
<tr>
<td>JIT (mono/mini/)
<td>Port the JIT to additional architectures.
Currently ports are in the works for mips, arm, sparc, s390. None of the ports
Currently ports are in the works for ppc, arm, sparc, s390. None of the ports
are as feature-complete as the x86 one, yet, so help is needed in getting them
up to speed. Ports to more architectures are welcome as well.
<td>Medium-hard
@@ -162,7 +162,7 @@ Happy hacking!
stack walking to collect security info.
<td>Medium-hard (thesis subject)
<td>4-5 months
<td><a href="http://bugzilla.ximian.com/show_bug.cgi?id=52606">52606</a>
<td>not assigned
</tr>
<tr>
@@ -190,106 +190,5 @@ Happy hacking!
<td>not assigned
</tr>
<tr>
<td>Tools
<td>Write an implementation of the MSBuild compilation tool available in .NET 1.2
<td>Medium
<td>4-6 months
<td>not assigned
</tr>
<tr>
<td>Build tools.
<td>Currently it is easy for people doing daily
updates from CVS to break their installation. Design a mechanism by
which Mono never fails to compile.
<td>Easy
<td>1-2 weeks
<td>not assigned
</tr>
<tr>
<td>Documentation.
<td>Editorial review of the Monkeyguide: The monkeyguide is known to contain outdated
statements, it needs to be reviewed and it needs an
editor to take control over it. Some simple tasks
include flattening out the Monkeyguide, since it is
too nested today.
<td>Easy
<td>Ongoing work.
<td>not assigned
</tr>
<tr>
<td>Documentation
<td>GNOME.NET Chapter should probably be separated
from the Monkeyguide. This is probably the most
complete chapter, but it is burried in various nested
levels of stuff, and because of this, it is not being
updated. Write a chapter on custom control
authoring and common patterns of app development.
<td>Easy
<td>Ongoing work.
<td>not assigned
</tr>
<tr>
<td>Documentation Tools
<td>The Monodoc collaborative service needs a better
administration tool than it has today; Someone needs
to redo the UI and streamline its process.
<td>Easy
<td>2-3 months.
<td>not assigned
</tr>
<tr>
<td>Comment Service API
<td>Design a full system for comments and ratings so
people can annotate the documentation in Monodoc.
<td>Easy
<td>2-3 months.
<td>not assigned
</tr>
<tr>
<td>POSIX bindings.
<td>The Mono.POSIX assembly is a project to create a binding to
the various low-level calls in Unix which are not available
thought he regular assemblies in .NET.
The work should be done in two steps: one step is doing the
low-level binding for the system call, and another possibly is
to expose .NET-level objects like Streams for common patterns:
for example Streams for socketpairs.
<ul>
<li>Complete the bindings for all POSIX calls.
<li>Design a glue layer, because the various low-level
structures and values differ from operating system to
operating system, so we must do the translation from
our own set of definitions to the OS definitions.
The details are availble on bug <a
href="http://bugzilla.ximian.com/show_bug.cgi?id=51849">51849</a>
for details.
</ul>
<td>Medium
<td>2-3 months + QA.
<td>not assigned
</tr>
<tr>
<td>System.Drawing CODECs
<td>Complete the JPEG and PNG codecs to be fully
finished; Implement EXIF data loading; Implement the missing image codecs.
<td>Medium
<td>2-3 months.
<td>not assigned
</tr>
<tr>
<td>System.Data updates
<td>.NET 1.2 introduced many new updates to the
System.Data namespace: MARS and ObjectSpaces are the
big ones.
<td>Medium
<td>6-9 months.
<td>Work with the mono-devel-list to keep track of things.
</tr>
</table>
+4 -4
View File
@@ -25,7 +25,7 @@
<li>List of unixODBC <a href="http://www.unixodbc.org/drivers.html">drivers</a>
<li>List of <a href="http://www.sqlsummit.com/odbcvend.htm">ODBC Vendors</a>
<li>List of <a href="http://ourworld.compuserve.com/homepages/Ken_North/odbcvend.htm">ODBC Vendors</a>
<li>ODBC can connect to various databases which has an ODBC driver installed:
<ul>
@@ -38,7 +38,7 @@
<li><a href="http://www.microsoft.com/sql/default.asp">Microsoft SQL Server</a> (
via <a href="http://www.freetds.org/">FreeTDS</a> on UNIX)</li>
<li><a href="http://www-3.ibm.com/software/data/db2/">IBM DB2 Universal Database</a></li>
<li><a href="http://www.microsoft.com/office/access">MS Access</a>
<li><a href="http://www.microsoft.com/office/access/default.asp">MS Access</a>
(via <a href="http://mdbtools.sourceforge.net/">MDB Tools</a> on UNIX)</li>
</ul>
@@ -105,14 +105,14 @@
<li>For Unix, you will need unixODBC or iODBC installed</li>
<li>Have acess to a <a href="http://www-306.ibm.com/software/data/db2/">IBM DB2 Universal Database</a> or
<li>Have acess to a <a href="http://www-3.ibm.com/software/data/db2/">IBM DB2 Universal Database</a> or
you can download from IBM</li>
<li>Read these web pages about Unix, ODBC, and IBM DB2
<ul>
<li><a href="http://www.unixodbc.com/doc/db2.html">unixODBC web page about IBM DB2</a></li>
<li><a href="http://www-306.ibm.com/software/data/db2/udb/ad/v8/cli/t0010406.htm">IBM web page about unixODBC and DB2</a></li>
<li><a href="http://www-3.ibm.com/software/data/db2/udb/ad/v8/cli/t0010406">IBM web page about unixODBC and DB2</a></li>
</ul>
</li>
-978
View File
@@ -1,981 +1,3 @@
@item Jul 9th, 2003: ASP.NET web services, coverage tools.
Web Services keep advancing: now we also support server-side
authoring of Web Services as well as web service clients
(which shipped in Mono 0.25). This works using our ASP.NET
runtime, so it works with either XSP or the Apache module. The
new Web Services work from Lluis added the missing bits:
<ul>
<li> .asmx files.
<li> Method calls with complex parameters (whatever XmlSerializer can currently serialize, which is a quite a lot).
<li> ref and out parameters.
<li> Soap headers (In, Out and InOut).
<li> Soap extensions, both global (configured in web.config) and particular to methods (configured using attributes).
</ul>
For more details, see Lluis <a href="http://lists.ximian.com/archives/public/mono-devel-list/2003-July/001449.html">post</a>
GUI-wise: Work on <a href="http://xr.xwin.org">Xr</a> to
implement System.Drawing continues. This will provide a full
GDI+ implementation for Mono, and this will be hooked up into
Gtk# and System.Windows.Forms.
MonoDoc keeps moving along, with a new web-based version
coming up next, and we are also exploring a collaborative
extension to allow people to contribute documentation through
their web browsers.
Zoltan's Coverage analysis tool has been checked into CVS.
With this tool it is now possible to find which class library
code paths are missing regression tests. The module is
`monocov'. Details are <a
href="http://www.nexus.hu/vargaz/">here</a>. A fresh Gtk#
version is available now.
Jean's remoting-based Soap implenentation is also maturing.
@item Jun 26th: Mono 0.25 has been released.
We have released Mono 0.25. A list of the new features is
available <a href="archive/mono-0.25.html">here</a>.
Packages for Windows, and various Linux distributions are
available on our <a href="download.html">download</a> page.
@item Jun 17th, 2003: Web Services client; Profiling hooks
Lluis and Gonzalo have checked into CVS the support for web
services in the Mono runtime. This allows Mono to work as a
web services client. We still require a WSDL compiler to
compile the initial stub, but Erik has the beginning of a WSDL
compiler ready and Atsushi has continued work on his
experimental Xml Schema to C# class generator.
As part of this, the Mono Http runtime has been rewritten to
increase reliability, scalability and conformance to the
specs. Also our io-layer has been extended to not have
arbitrary limits. This was done as part of our collaboration
with SourceGear.
Paolo has commited the new pluggable profiling API to the Mono
runtime: now the profiler is built as a module, and a new code
coverage analysis has been checked in (and Zoltan already
added improvements to it).
Mark's Mozilla bindings continue to improve, and we will shortly
migrate the Mono documentation browser to use Mozilla, to take
advantage of the tutorial's use of CSS.
Jackson's work on the IL assembler and Ben on running
regression tests have provided us with a very needed tool in
the Mono toolkit. One of the last missing pieces on the SDK.
On the crypto world, we got Sebastien's certificate viewer
checked into CVS and the crypto code keeps advancing by leaps
and bounds.
Alexandre and Aleksey Work continues on Windows.Forms on top
of Wine and Gtk# (the former for full compatibility, the later
for ease-of-authoring).
Cesar checked in the beginning of the semantic analysis code
for his JScript compiler, and will be working on it full time.
@item Jun 11th, 2003: SourceGear and Ximian announce partnership
Ximian, Inc., the leading provider of desktop and server
solutions enabling enterprise Linux adoption, today announced
that SourceGear Corporation will use Mono\x{2122} Project
technology to offer cross-platform versions of its
products. In addition, the companies have entered into a
development partnership under which Ximian will provide
custom Mono development to enable delivery of SourceGear
products later this year. As a result, SourceGear will offer
both UNIX and Linux clients for its SourceGear Vault source
code management tool, enabling broader use of its solutions in
mixed-platform development organizations.
<a href="http://www.ximian.com/about_us/press_center/press_releases/index.html?pr=sourcegear">Read more...</a>
Some technical details are available <a
href="http://lists.ximian.com/archives/public/mono-list/2003-June/014334.html">here</a>.
@item May 20th, 2003: OpenLink releases WineLib patches.
OpenLink <a
href="http://lists.ximian.com/archives/public/mono-winforms-list/2003-May/000284.html">announced</a>
the release of Vladimir's work to turn Wine into a library
that can be used dynamically from Mono. This work simplifies
the work on System.Windows.Forms as it is no longer necessary
have a special version of the GC, nor have a stub program.
The patches are available <a
href="http://www.openlinksw.com/mono/">here</a>.
Mono packages for the Linux/s390 are available now in the <a
href="download.html">download page</a>.
@item May 10th, 2003: Eclipse runs on Mono
Today Zoltan Varga announced that he got the <a
href="http://www.eclipse.org">Eclipse IDE</a> running on top
of Mono+<a href="http://www.ikvm.net">IKVM</a>.
A screenshot of Eclipse running with Mono can be found <a
href="images/ikvm-screenshot.png">here</a>
@item May 6th, 2003: Mono 0.24 ships
We have released Mono 0.24 which includes our new code
generation engine. A list of the new features is available <a
href="archive/mono-0.24.html">here</a>.
Packages for Windows, and various Linux distributions are
available on our <a href="download.html">download</a> page.
We are shipping Gtk# and MonoDoc packages for the first time.
@item Apr 21st, 2003: Virtuoso 3.0 ships.
<a href="http://www.openlinksw.com">OpenLink's</a> released
their <a href="http://www.openlinksw.com/press/virt3rel.htm">Virtuoso
3.0</a> database system. Virtuoso ships on Windows and Linux.
On Linux they use Mono as their runtime to host C#, .NET and
ASP.NET. Congratulations to OpenLink for their release.
Virtuoso can be downloaded <a
href="http://oplweb2.openlinksw.com:8080/download/virtuoso.vsp">here</a>
and a demo is available <a
href="http://demo.openlinksw.com:8890/tutorial/hosting/ho_s_2/ho_s_2.vsp">here</a>.
OpenLink is contributing fixes and code to the Mono project on
an ongoing basis.
Jon Udell wrote a small <a
href="http://www.infoworld.com/article/03/03/14/11stratdev_1.html">entry</a>
@item Apr 19th, 2003: RelaxNG validating reader; Activities.
Atsushi has created a <a
href="http://www24.brinkster.com/ginga/RelaxngValidatingReader/">RelaxNG</a>
validating XML reader.
There is activity on the <a
href="http://www.gotmono.com">GotMono forums</a> and the <a
href="http://www.nullenvoid.com/gtksharp/wiki/">Gtk# Wiki</a>
@item Apr 11th, 2003: First Mono Book is out; Team pages.
The first book to cover Mono is out. This book is currently
only available in German, you can find it <a
href="http://www.amazon.de/exec/obidos/ASIN/3827264928/qid=1050051051/sr=2-1/ref=sr_2_3_1/028-2755135-1623712">here</a>
We now have a page for the <a href="team.html">Mono Team</a>
where we include a list of some of the people who have made
Mono possible. If you have CVS access, please update the page
to include your information.
@item Apr 5th, 2003: New compilation engine.
The new Mono compilation engine has been placed on CVS, the
details are <a
href="http://lists.ximian.com/archives/public/mono-list/2003-April/013269.html">here</a>
Zoltan has commited his <a
href="http://lists.ximian.com/archives/public/mono-devel-list/2003-April/000274.html">typed
allocation</a> patches to CVS as well.
@item Apr 3rd, 2003: NUnit 2.0 GTK# GUI; GtkMozEmbed; SWT#
Gonzalo has checked in his <a href="http://gtk-sharp.sf.net">Gtk#</a>-based
<a href="http://nunit.org">NUnit</a> tool. Screenshots are <a
href="http://primates.ximian.com/~gonzalo/mono/shots/running.png">here</a>
and <a
href="http://primates.ximian.com/~gonzalo/mono/shots/finished.png">here</a>
Mark has checked his bindings for Gtk-based Mozilla into CVS,
module name: `GtkMozEmbed'. Read the <a
href="http://lists.ximian.com/archives/public/mono-list/2003-April/013247.html">details</a>
The SWT port to C# using Gtk is <a
href="http://lists.ximian.com/archives/public/sd-mono-port/2003-March/000114.html">progressing</a>. Screenshots are
<a href="http://www.roboto.ch/swt">here</a>.
@item Mar 28th: Mono community site.
<a href="http://www.gotmono.com">www.gotmono.com</a> has
openend its door: Got Mono is a Mono Community site.
@item Mar 25th: Second Mono Survey
<table width="100%" cellpadding="0" cellspacing="1" border="0" bgcolor="blue">
<tr>
<td valign="top">
<div style="background: #c0d0ff; margin: 0px 0px 0px 0px; padding: 1px;">
What do you think about Mono?
Is your company involved with the development and
deployment of web applications? Is Linux becoming an
important part of your company's business application
strategy? Are you considering Mono for your next
project? Would you like to shape the future of Mono
and the use of Linux in business critical
applications?
If you answered yes to any of these questions, we
would like to talk with you. If interested, please
email us at <a
href="mailto:[email protected]">[email protected]</a>.
</div>
</td>
</tr>
</table>
@item Mar 20th: Windows.Forms and Wine.
Alexandre has provided a modified version of the GC system
that will work with and Mono. See the mono-winforms-list. It
is now possible to run our Win32-based implementation of
Windows.Forms with Mono on Linux.
@item Mar 7th: Mono 0.23
A new freshly baked release of Mono is available. Release
notes are <a href="archive/mono-0.23">here</a>. This is mostly a
bug fix release. No new features.
@item Mar 5th, 2003: Mono 0.22; MonoDoc 0.2; Debugger 0.2.1: Release-o-Rama.
Mono 0.22 has been released. See the <a
href="archive/mono-0.22">release notes</a>. This is a bug fix
release.
A new preview of MonoDoc 0.2, the Mono Documentation browser
has been <a href="http://lists.ximian.com/archives/public/gtk-sharp-list/2003-March/001266.html">released</a>.
Martin also announced a <a
href="http://lists.ximian.com/archives/public/mono-list/2003-March/012756.html">new
release</a> of the Mono Debugger (both GUI and command line).
@item Mar 3rd, 2003: The Mono Hackers Hall Of Fame welcomes Zoltan Varga
The <a href="hackers.html">Mono Hackers Hall Of Fame</a>
continues to show our appreciation to the excellent
contributors that make <b>mono::</b> a successful free
software project.
Zoltan has contributed significantly to Mono, with bug reports and bug
fixes as well as pushing the envelope of the things that can be done in
and with the mono runtime: the gcc-based ngen compiler, code coverage
and more recently his work with Reflection.Emit that got mono to the
point of running the <a href="http://www.ikvm.net">IKVM</a> Java virtual
machine.
@item Mar 2nd, 2003: New Mono mailing list.
A new mailing list for <a
href="http://lists.ximian.com/mailman/listinfo/mono-devel-list">Mono
Development</a> has been created.
@item Feb 27th, 2003: Mono 0.21 released
Mono 0.21 has been released. This is only a bug fix release.
The <a href="archive/mono-0.21">release notes</a> are available.
Windows binary is available <a href="archive/mono-0.21-win32-1.exe">here</a>
@item Feb 25th, 2003: Mono 0.20 for Windows released; New Apache module released.
Packages of Mono for Windows have been <a
href="archive/mono-0.20-stable-win32-2.exe">released</a>.
Thanks to Daniel, Johannes and Paolo for setting this up.
Daniel has released a new version of his Mono Apache module that
handles ASP.NET. The code is available at <a
href="http://apacheworld.org/modmono/">here</a>
Nick has posted an update on the progress on our <a
href="http://lists.ximian.com/archives/public/mono-list/2003-February/012467.html">regression
tests</a>. We are looking for more tests, and more volunteers to write them.
Also, remember to contribute to the Gtk# documentation effort,
momentum is picking up! See the entry for Feb 18th for more details.
@item Feb, 23rd, 2003: Mono 0.20 released; Gtk# 0.8 released.
Mono 0.20 has been released. Check out the <a
href="archive/mono-0.20">release notes</a> for an overview of
the changes. You can get it <a href="download.html">here</a>.
There are no major features in this release, mostly bug fixes
and performance improvements.
Gtk# 0.8 has been <a
href="http://lists.ximian.com/archives/public/gtk-sharp-list/2003-February/001114.html">released</a>
<b>Important</b>: The contributed binaries for Windows
binaries of Mono 0.20 contain a virus. Please read <a
href="virus.html">this</a> if you installed the binary.
@item Feb 18th, 2003: Volunteers to document Gtk#
With the availability of a documentation browser, we are
looking for volunteers to help us complete the documentation
of the Gtk# binding for Mono.
Experience with Gtk is useful, but not mandatory. We have
checked in stubs, and we have instructions, and resources to
how to complete this process <a
href="documentation.html">here</a>. Mail the <a
href="mailto:[email protected]">[email protected]</a>
for further discussion.
@item Feb 14th, 2003: OpenGL# bindings for Mono; Mono Basic updates.
Mark Crichton has completed his OpenGL/GLUT bindings for
Gnome. A screenshot can be seen <a
href="sshots/oglcs.png">here</a>. The bindings are available
on the Mono CVS repository on the module `glgen'. This is a
straight binding to the C API.
Marco has <a
href="http://lists.ximian.com/archives/public/mono-list/2003-February/011752.html">posted
an update</a> on the current state of the free VB.NET compiler
for Mono.
We are looking for contributors and maintainers to the
JavaScript compiler as well (Janet)
@item Feb 12th, 2003: New assemblies, Gtk# stub documentation, Authenticode, Polish site
Mono now distributes a few new assemblies: Mono.Security.Win32
as a layer to use the crypto functionality on Win32. The
Mono.Posix assembly which contains functionality for taking
advantage of Unix facilities.
A <a href="http://www.go-mono.pl/">Mono site in Poland</a>.
Stubs for the Gtk# documentation have been checked into CVS.
If you want to contribute please read <a
href="http://lists.ximian.com/archives/public/mono-list/2003-February/012108.html">this
message</a>
Mono development is moving quickly: Tim and Daniel have been
improving the Oracle database provider and Sebastien Pouliot
has got code signing to work using Authenticode with pure open
source and managed code. Plenty of new VB.NET work from Marco
(compiler) and Daniel (runtime). Also Jackson has resumed
work on the IL assembler and the fully managed library to
generate CIL images (Sergey wrote the first Mono.PEToolkit).
@item Feb 11th, 2003: Mono Weekly News, New assemblies.
<a href="http://monoevo.sourceforge.net/mwn/index.html">Mono
Weekly News</a>: Includes a new interview, software
announcements and the PHP/Mono integration.
@item Feb 5th, 2003: MonoDoc 0.1
A <a
href="http://www.go-mono.com/archive/monodoc-0.1.tar.gz">preliminary
release</a> of the Mono Documentation Browser is now availble.
Release <a
href="http://lists.ximian.com/archives/public/mono-list/2003-February/011935.html">notes</a>
@item Jan, 22th, 2003: Mono wins award, OpenLink releases Virtuoso.
Mono won the `Best Open Source Project' award at the Linux
World Expo. A description is <a
href="http://linuxtoday.com/news_story.php3?ltsn=2003-01-23-024-26-OP-EV">here</a>
Open Link has a <a
href="http://biz.yahoo.com/prnews/030123/neth013_1.html">press
release</a> about Virtuoso 3.0: the first commercial product
shipping that uses Mono.
@item Jan, 20th, 2003: Mono 0.19 released; Screenshots page; Gtk# 0.7
Mono 0.19 has been released. Check out the <a
href="archive/mono-0.19">release notes</a> for an overview of
the changes. You can get it <a href="download.html">here</a>.
There are no major features in this release, mostly bug fixes
and performance improvements.
We have now a new section <a href="screenshots.html">with
screenshots</a> of various Mono applications. You can see
there the new released Debugger, as well as the work in
progress on the documentation browser.
<a href="http://gtk-sharp.sf.net">Gtk# 0.7</a> has been <a
href="http://lists.ximian.com/archives/public/mono-list/2003-January/005222.html">released</a>
@item Jan, 19th, 2003: Mono Debugger released.
After six month of extensive development, Martin Baulig has
released the first version of the Mono debugger. The Mono
debugger is written in C# and can debug both managed and
unmanaged applications, support for multiple-threaded
applications and should be relatively easy to port to new
platforms.
Details of the release are available in <a
href="http://lists.ximian.com/archives/public/mono-list/2003-January/005192.html">post</a>.
The debugger contains both Gtk# and command line interfaces.
The debugging file format used in Dwarf (its already supported
by our class libraries and the Mono C# compiler; To debug C
applications, you need a recent GCC, or to pass the -gdwarf-2
flag to gcc).
@item Jan, 17th, 2003: DB2 provider, MacOS X
Christopher Bockner has contributed a DB2 System.Data client.
MacOS X support on the runtime has been integrated into the
distribution, and MCS works with it.
Zoltan has managed to get <a
href="http://radio.weblogs.com/0109845/">IKVM</a> (a Java VM
for .NET) to run with Mono. The HelloWorld.class runs with
the Mono runtime.
@item Jan, 13th, 2003: Mono 0.18 released
Mono 0.18 has been released. Check out the <a
href="archive/mono-0.18">release notes</a> for an overview of
the changes. You can get it <a href="download.html">here</a>.
@item Jan 10th, 2003: Mono Weekly News.
A new issue of the <a
href="http://lists.ximian.com/archives/public/mono-list/2003-January/004903.html">Mono
Weekly News</a> has been published.
Check out the <a href="crypto.html">Crypto status</a> page
that Sebastien has put together.
@item Jan 3rd, 2003: Glade#, Code Coverage, Apache, MBas, Debugger.
Rachel has made Glade# use attributes so binding C# widgets to
the designed widgets is now easier than ever. Alp has
improved this to use implicit names as well.
Martin's Mono debugger now has support for multi-thread
debugging. Special feature: breakpoints can be defined in a
per-thread basis now.
Daniel López has checked in his Apache module to integrate
Mono and Mono's ASP.NET support as an Apache module. Gonzalo
has folded his new Mono hosting classes into this module (they
are now shared between XSP and mod_mono). You can get the
mod_apache from CVS (module name: mod_mono).
Mono Basic improvements: Marco has added support for more
statements on the grammar.
Zoltan has <a href="http://www.nexus.hu/vargaz2/">posted</a>
his Code Coverage analysis tool for Mono.
@item Dec 17th, 2002: Mono: Commercial uses.
<a href="http://www.tipic.com">Tipic</a> today <a
href="http://www.ximian.com/about_us/press_center/press_releases/index.html?pr=tipic_mono">announced</a>
their work on porting their Instant Messaging Server platform
to run on Mono.
<a href="http://www.winfessor.com">Winfessor</a> also <a
href="http://www.winfessor.com/press.asp">announced</a> the
availability of their Jabber SDK to run on Mono.
Also two weeks ago we mentioned <a
href="http://www.openlinksw.com">OpenLink Software's</a> <a
href="http://www.ximian.com/about_us/press_center/press_releases/index.html?pr=openlink_mono">announcement</a>
of their product, also using Mono.
@item Dec 10th, 2002: Gtk# 0.6 released; Mono 0.17 packages for Windows and Debian.
Mike Kestner <a
href="http://lists.ximian.com/archives/public/mono-list/2002-December/003961.html">announced
Gtk# 0.6</a>. This new release includes many new features and
bug fixes, and is the perfect companion to the <a
href="archive/mono-0.17">Mono 0.17</a> release.
Johannes has contributed a Windows-ready package of Mono 0.17,
and its available from our <a
href="download.html">download</a> page.
Alp Toker has <a href="http://www.atoker.com/mono/">Debian packages</a>
@item Dec 9th, 2002: Mono 0.17 has been released
Mono 0.17 has been released. Check out the <a
href="archive/mono-0.17">release notes</a> for a more detailed
list. You can get it <a href="download.html">here</a>.
Many new features as well as plenty of bug fixes. Many new
System.Data providers and a more mature System.Web (ASP.NET)
which can now be hosted in any web server. A simple <a
href="archive/xsp-0.2.tar.gz">test web server</a> to host
asp.net has been released as well.
This version also integrates Neale's s390 port.
This release also includes a new exception handling system
that uses the gcc exception information that vastly improves
our internalcall speed (15% faster mcs compilation times).
@item Dec 8th, 2002: VB.NET, Oracle Provider.
Marco has got the Mono Basic compiler up to speed (support for
classes, modules, expressions, object creation, method
invocation, local variables, and some statements). The
compiler is based on the work from Rafael Teixeira on MCS.
Screenshots: <a
href="http://modgb.sourceforge.net/monobasic_snap.png">in
Windows doing Windows.Forms</a> and in Linux doing <a
href="images/gtk-vb.png">VB with Gtk#</a> (courtesy of Alp).
Daniel Morgan has checked in his Oracle provider to the CVS
repository as well.
@item Nov 27th, 2002: Press release, tutorials, Windows Forms, ADO.NET, Magazine.
<a
href="http://www.business2.com/articles/mag/0,1640,45454,FF.html">The
Penguin Takes Flight</a>: an article written by Erick
Schonfeld appears on the December issue of <a
href="http://www.business2.com/">Business 2.0</a> magazine.
<a href="http://www.openlinksw.com">OpenLink</a> and <a
href="http://www.ximian.com">Ximian</a> made <a
href="http://www.ximian.com/about_us/press_center/press_releases/index.html?pr=openlink_mono">joint
announcement</a> on the plans of OpenLink to ship their <a
href="http://www.openlinksw.com/virtuoso/index.htm">Virtuoso</a>
server on Unix using Mono.
Martin Willemoes's <a href="gnometutorial">GNOME.NET
tutorial</a> is now available from the main Mono site. This
tutorial is a collaborative effort to teach developers how to
use Mono to create Mono applications using <a href="http://gtk-sharp.sf.net">Gtk#</a>
Dennis Hayes has posted and <a
href="http://lists.ximian.com/archives/public/mono-list/2002-December/003800.html">update</a>
on the work to get Windows.Forms working on Mono. There is a
new test application that people can use to test their
controls. If you are interested in working on Windows.Forms,
you can participate in the <a
href="http://lists.ximian.com/mailman/listinfo/mono-winforms-list">mono-winforms
mailing list</a>
Brian Ritchie has been working on an ADO.NET <a
href="http://brianritchie.webhop.net/ideas/adocodegen.aspx">data
layer</a> and an <a
href="http://brianritchie.webhop.net/ideas/appserver.aspx">application
server</a> for Mono.
Dan Morgan has checked in his Oracle provider, and Tim Coleman
continues to work on the TDS implementation of the data classes.
The rest of the team has been working on bug fixing in the
runtime, the compiler, and the class libraries. Also,
compilation speed has increased recently by performing a
number of simple optimizations in the compiler.
@item Nov 19th, 2002: Crypto update; Books; Gtk# Datagrid; .NET ONE Slides
Sebastien has got DSA and RSA signatures <a
href="http://lists.ximian.com/archives/public/mono-list/2002-November/003497.html">working</a>
as well as RSA <a
href="http://lists.ximian.com/archives/public/mono-list/2002-November/003502.html">encryption</a>.
We now distribute Chew Keong TAN's BigInteger classes.
Brian has contributed a System.Data multiplexor in Mono, it
can be found in the Mono.Data assembly. The details of this
new technology are <a
href="http://lists.ximian.com/archives/public/mono-list/2002-November/003400.html">here</a>.
It works in Mono and the .NET Framework.
Larry O'Brien has announced the candidate book for <a
href="http://lists.ximian.com/archives/public/mono-list/2002-November/003500.html">
Thinking in C#</a>. The book is Mono-friendly.
Another book that covers mono (available in German only) is <a
href="http://www.databecker.de/frames.php?PHPSESSD=4948515556575049525459495248485949485348&PHPSESSID=6cc68dbcfbcbacd7b82a984b0700d5d6&t=2">
here</a>.
Dan Morgan has implemented a DataGrid widget for Gtk#, you can
see Windows screenshots for it <a
href="images/GtkSharpDataGridScreenshot.png">here</a> and <a
href="images/SqlSharpGtkScreenshot4.png">here</a>.
Slides from the Mono developers for the .NET ONE conference are available now:
<ul>
<li><a
href="http://primates.ximian.com/~miguel/slides-europe-nov-2002/DotNetOneKeynote.sxi">
Mono Keynote presentation</a>
<li><a href="http://primates.ximian.com/~lupus/slides/embed/">Hosting the Mono Runtime</a><br>
The simple embedding of Mono in Perl is available <a
href="http://primates.ximian.com/~lupus/slides/embed/Mono-0.01.tar.gz">here</a>
<li><a href="http://primates.ximian.com/~lupus/slides/jit/">The Mono JIT compiler</a>
<li><a href="http://primates.ximian.com/~miguel/slides-europe-nov-2002/Mono_C_Sharp_Overview_1007.sxi">
Mono C# Compiler Overview</a>
</ul>
A couple of other presentations from Miguel's trip to Europe
are available <a
href="http://primates.ximian.com/~miguel/slides-europe-nov-2002/">here</a>
in Open Office file format.
@item Nov 8th, 2002: Mono s390, Database work, new JIT updates.
Neale Ferguson has contributed <a href="download.html">RPM
packages</a> of Mono for the Linux/s390.
Tim Coleman posted an <a
href="http://lists.ximian.com/archives/public/mono-list/2002-November/003329.html">update</a>
on the improvements in the System.Data
The new JIT engine can run 72 out of our 154 tests for the
virtual machine, and it also got exception support this week.
@item Nov 1st, 2002: TDS, Crypto, Gtk#, Winforms, bug fixes.
Tim's SqlClient is <a
href="http://lists.ximian.com/archives/public/mono-list/2002-November/003161.html">now
capable</a> of communicating with the Microsoft SQL server
using the TDS protocol. A screenshot showing a sample client
running with <a href="http://gtk-sharp.sf.net">Gtk#</a> on
Windows is shown <a
href="images/SqlSharpGtkSceenshot3.png">here</a>
Sebastien has made all symetric ciphers functional on all
supported modes; All the classes in Security.Cryptography are
present and the X590 certificates are now in too. Jackson has
been working on the Security classes.
Many bug fixes all over the place: class libraries (Dick,
Piers, Ville, Zoltan, Gonzalo, Dan, Atsushi, Nick, Phillip),
compiler, runtime engine. A big thank goes for everyone who
has been providing bug reports for us to track down.
Gaurav has been working on multiple WebControls. Gonzalo migrated
the ASP.NET engine to use POST for interaction.
In the Gtk# land saw the integration of gda, gnome-db and GStreamer
bindings.
Windows.Forms classes now build on Linux and Windows, check
out the status pages for areas of collaboration.
@item Oct 24th, 2002: S390 support, XSP/ASP.NET, Win32 contributors, TDS.
Today Neal Ferguson's support for the IBM S390 was checked
into CVS.
The XSP processor has been fully integrated into the
System.Web assembly, and Gonzalo has finished the hosting
interfaces in Mono. This means that it is possible to embed
ASP.NET with the same APIs used in Windows, and is possible to
easily embed it with Apache for example. The XSP module has
now become a shell for testing the System.Web classes.
We are looking for contributors that know Win32 to contribute
to the Windows.Forms implementation. If you want to help
write some controls using the Win32 API, get in touch with our new <a
href="http://lists.ximian.com/mailman/listinfo/mono-winforms-list">[email protected]
list</a> mailing list.
Tim's TDS System.Data set of classes can now talk to SQL
servers using the TDS protocol (version 4.2) with
connection pooling. Currently it can connect, run
transactions, update/insert/delete, and read some types. A
data adapter is also coming soon.
@item Oct 21th, 2002: Crypto, Winforms list, Database, GConf, Debugger.
Sebastien Poliot has made a lot of progress, he reports that
DES and TripleDES have been fixed; Rijndael and CFB modes
still have problems in some configurations and some areas that
are not supported by the .NET framework.
Last week we created a new <a
href="http://lists.ximian.com/mailman/listinfo/mono-winforms-list">mailing
list</a> to discuss the Mono Winforms implementation.
Tim has started a full C# implementation of the TDS protocol
and the providers, and Brian continues his work on his ODBC
binding.
Rachel Hestilow has also checked in a binding for GConf. This
binding <a
href="http://toxic.magnesium.net/~hestilow/gconfsharp/intro.html">is
unique</a> in that it uses some features in the CLI to support
complex data types, and allows the user to keep only one
representation of the types instead of two (the master types
is defined in CLI-land). Also Property Editors (<a
href="http://primates.ximian.com/~miguel/shots/gconf-shot.png">shot</a>)
simplify the creation of user interfaces that bind their
configuration to backend keys, following the <a
href="http://developer.gnome.org/projects/gup/hig/1.0/">GNOME
Human Interface Guidelines.</a>
Martin is now on vacation, but before leaving he produced a
number of documents detailing the state of the debugger. The
major missing feature is full support for debugging unmanaged
applications (it requires dwarf-2 handlers for types). We
will do some polishing of the user interface (<a
href="http://primates.ximian.com/~miguel/shots/debugger-4.png">new
shot</a>) to expose the existing and rich functionality to the
users and try to release a preview of the debugger at the same
time as Mono 0.17.
@item Oct 14th, 2002: Crypto, Database work, Debugger, Documentation.
Brian, Daniel and Rodrigo have been busy working on the ODBC
provider for Mono. Daniel posted some <a
href="http://lists.ximian.com/archives/public/mono-list/2002-October/002755.html">updates</a>.
Brian posted <a
href="http://lists.ximian.com/archives/public/mono-list/2002-October/002758.html">details
about the ODBC.NET</a> provider.
Also Sebastien Pouliot has been improving the various
cryptographic classes in Mono, something that we had not done
in quite some time. We are looking for a way to handle
big-nums. We need either a managed or unmanaged set of
classes for handling large numbers, and some volunteers to
expose this functionality to C# (Either as an internal
assembly, or as a set of P/Invoke, Internal call wrappers).
Martin has got our debugger to support adding breakpoints at
file/line combos. This was more complex than generic
breakpoints in routines, because these breakpoints are set on
routines that probably have not been JITed just yet. Martin's
focus now is on stabilizing our debugger and aim for a public
release of it.
We have also imported the ECMA documentation into a separate
module, and with the help from Scott Bronson we will have the
necessary XSLT tools to finish our native documentation
browser for Mono. This together with the work from Adam will
be the foundation for the <a href="classlib-doc.html">Mono
Documentation Tools</a>.
@item Oct 9th, 2002: Various Mono updates.
Brian Ritchie, Daniel Morgan, Rodrigo Moya and Ville Palo have
been working on various database providers. The MySQL has
seen a lot of work, and a new ODBC provider is now on CVS and
more extensive regression tests have been checked in.
Dick Porter is our background hero and keeps fixing the
low-level bugs in the portability layer. Now the Mono handle
daemon should be a lot more robust and will no longer leave IPC
regions. Gonzalo Paniagua has initiated the migration of XSP
into the System.Web class libraries now that we have a
complete HttpRuntime implementation. This means that you are
able to embed the ASP.NET processor into any web server you
want. This also includes support for the system-wide
configuration file `machine.config'.
Martin Baulig has been busy with the Mono Debugger, you can see how
it looks <a
href="http://primates.ximian.com/~miguel/debugger-1.png">here</a>
and <a
href="http://primates.ximian.com/~miguel/debugger-2.png">here</a>.
Now local variables and breakpoints are supported, and we are
working on the UI elements to simplify their use (as seen on
the screenshot).
<a href="http://gtk-sharp.sf.net">Gtk#</a> has seen a lot of
activity specially as we start to build larger applications.
Vladimir Vukicevic, Kristian Rietveld, Rachel Hestilow, Mike
Kestner and Miguel de Icaza have been busy improving it.
mPhoto which is a Photo management application for Mono and
Gtk# is seen <a
href="http://primates.ximian.com/~miguel/shots/mphoto-2.jpg">here</a>.
Chris Toshok the man behind LDAP in Evolution continues to
work on the Mono.LDAP# implementation.
Dietmar Maurer and Paolo Molaro are still busy working on our
new optimized JIT/ATC engine and are making great progress.
The code base has been designed to ease the implementation of
more advanced compiler optimizations, and optimizations can be
chosen individually so they can be tuned for a particular
processor, or use profile-based information to improve the
performance.
@item Oct 1st, 2002: Mono 0.16 released; Debugger updates.
Mono 0.16 has been released. Source and RPMs are <a
href="download.html">available</a>. The release notes are <a
href="archive/mono-0.16">here</a>.
Martin's debugger can debug both managed and unmanaged code.
Recently Martin added support for locals, parameters, and
breakpoints on top of the existing infrastructure (his
debugger supported instruction-level and source-code level
single-stepping).
@item Sep 19th, 2002: Mono Survey.
Help us plan for the future of Mono by filing out the <a
href="http://primates.ximian.com/~miguel/monosurvey">First Mono
Survey</a>
@item Sep 17th, 2002: Mono Hackers Hall of Fame: Sergey Chaban
The <a href="hackers.html">Mono Hackers Hall Of Fame</a>
continues to show our appreciation to the excellent
contributors that made <b>mono::</b> a successful free
software project.
This time the Hall of Fame welcomes Sergey Chaban. Sergey has
been a long time contributor to the project, from the early
work on the class libraries that were critical to Mono's
origin: every time you use a Hashtable in Mono, it runs
Sergey's code, to the low-level optimizations on the JIT
engine and to his work on ILASM and the PEToolkit.
@item Sep 16th, 2002: Documentation Tools, ILASM, Debugger, Mono LDAP, Winforms
Adam Treat has started moving the documentation universe again. We
have a new strategy to document our APIs (given that we have
chosen <a href="classlib-doc.html">not to document the code
inline</a>). This includes the use of a master reference file
that will hold the entry points to document. All master files
for our assemblies have been checked into CVS now.
Sergey Chaban's Mono.PEToolkit and ILASM tools have been
checked into CVS. Although ILASM is old and will soon be
updated, we wanted to get the build issues sorted out.
Martin Baulig's Mono Debugger is still on its early stages,
but you can run and run step by step your C# code and C code
(including the Mono runtime). Dwarf-2 is required to compile
your code. The regular step, step-into, and assembly-level
step and step-into are supported. And comes with a Gtk#
UI. The debugger is written mostly in C# with some C glue
code. Most of the work is on the engine, we will be working
on making a good UI in the future.
Chris Toshok of the Hungry Programmer's fame has checked in
Mono.Directory.LDAP, a C# wrapper for the LDAP libraries.
This is the substrate for implementing the
System.DirectoryServices assembly.
Andrew has also continued with some of the cryptographic
classes implementation.
After much public debate, we have chosen a new <a
href="winforms.html">strategy to implement winforms</a>.
Implementing a Gtk, Qt or Aqua based version of Winforms was
going to be almost as complex as implementing Wine itself. So
the new strategy is to only roll out a WineLib-based
implementation.
@item Sep 4th, 2002: .NET One 2002 Program available
The <a
href="http://www.sigs-datacom.de/sd/kongresse/dotnet_2002/index.htm">.NET
ONE 2002</a> conference in Frankfurt is now available. Paolo
will be talking about the Mono JIT and embedding the Mono
runtime in your Windows and Linux applications. Mike Kestner
will talk about <a href="http://gtk-sharp.sf.net">Gtk#</a> and
the automatic binding generator used by Gtk# and Miguel will
be talking about the Mono project on Monday's keynote and on
the Mono C# compiler on Tuesday.
@item Sep 3rd, 2002: Apache integration
<a
href="http://lists.ximian.com/archives/public/mono-list/2002-September/001862.html">Sterling</a>
announced an Apache module that hosts
Mono, and allows CIL code to run from within Apache, giving the
module access to the Apache runtime. This uses the Mono embedding
API.
@item Aug 24th, 2002: Gtk# 0.4 released
Shortly after <a href="download.html">Mono 0.15</a> was
released a fresh version of <a
href="http://gtk-sharp.sf.net">Gtk#</a> was <a
href="http://lists.ximian.com/archives/public/mono-list/2002-August/001702.html">announced</a>.
@item Aug 23rd, 2002: Mono 0.15 released
Mono 0.15 has been released. Source and RPMs are <a
href="download.html">available</a>. The release notes are <a
href="archive/mono-0.15">here</a>
@item Aug 21th, 2002: Portable.NET encodings integrated into Mono.
Rhys Weatherley has contributed the Portable.NET encoders to
the Mono class libraries. This is a great step towards
cooperation between these projects. Thanks to Paolo for doing the
merger on our side.
His encoders are more complete than the iconv-based approach
that mono used, which was unreliable under certain
circumstances.
@item Aug 20th, 2002: Remoting work, Resources, SPARC checkins, ADO.NET
<b>San Francisco</b>: August 14th. Linux World Expo.
Mark Crichton has checked in his patches to get the SPARC port
on par with the PPC port.
Dick has checked-in the resource reader and resource writers
to the class libraries, and Dietmar checked in the C# support
code for the remoting infrastructure.
More work on System.Data: the LibGDA (our OleDB backend) based
providers are quickly maturing, and recently they executed
their first query.
@item Aug 13th, 2002: MCS news, Gtk# progress, Windows.Forms, ADO.NET
Martin Baulig has been fixing all the known bugs in the C#
compiler and now has moved into improving the compilation
speed and the generated code quality of MCS. Today we got a
50% speedup in the bootstrap of MCS going from 24 seconds to 12 seconds.
Gtk# has been making a lot of progress, some interesting
corner cases are now supported:, you can now create canvas items as
well as using the tree widget. Here is a shot of <a
href="images/mocil.png">MonoCIL</a>.
On the runtime front, focus has been on improving remoting
support, exception handling, as well as completing the support
for structure marshaling.
Patrik is also back in action: the HttpRuntime infrastructure
is rapidly improving, and Gonzalo is working into moving XSP
into our main class library and providing the missing pieces
to integrate with Patrik's code.
Dennis and his team are working on a WineLib-based
implementation of Windows Forms to guarantee that the corner
cases of Windows.Forms can be handled, and we are back on track again.
A lot more work on the ADO.NET and WebServices has also been
checked into CVS.
@item Aug 1st, 2002: Mono Hackers Hall of Fame
The <a href="hackers.html">Mono Hackers Hall Of Fame</a> has been started
to show our appreciation to the excellent contributors that made <b>mono::</b>
a successful free software project.
The first, deserved, entry goes to
Nick Drochak, who joined us in the first days of Mono and built the testing
infrastructure for the C# assemblies, fixed tons of bugs and even adventured
himself in the lands of the C runtime. His work is invaluable for keeping
Mono on the right track through the daily changes in the codebase.
@item Looking for volunteers
We are looking for volunteers to help complete various pieces
+24 -9
View File
@@ -8,7 +8,9 @@
<li>Works on Windows and Linux</li>
<li>Works with Oracle 8i and 9i.</li>
<li>Works with Oracle 8i</li>
<li>May work with Oracle 9i</li>
<li>Uses the Oracle CLI (Call Level Interface) which is a C library (API) for the Oracle Client
software</li>
@@ -28,15 +30,23 @@
** Current Status
<ul>
<li>OracleConnection can connect and disconnect to an Oracle 8i or 9i database on
<li>OracleConnection can connect and disconnect to an Oracle 8i database on
Windows and Linux via OCI (Oracle Call-level Interface)</li>
<li>No longer uses a glue library (a library between the System.Data.OracleClient.dll
assembly and the oci library). In Current Mono cvs, System.Data.OracleClient
directly platform invokes into the oci library thanks to Tim Coleman.</li>
<li>Can have multiple connections with different transactions where each transaction is
separated from the others, so a rollback or commit in one transaction
does not affect the other.</li>
<li>Can execute simple DML SQL statements, such as,
INSERT a row into the EMP table via the OracleCommand's ExecuteNonQuery method</li>
<li>The System.Data.OracleClient.dll assembly can be built with mcs/mono via
the makefile.gnu for System.Data.OracleClient or csc/.net via the
System.Data.OracleClient.build nant build file.</li>
<li>Can retrieve data via ExecuteReader and OracleDataReader. Currently,
supports character, numeric, some date data types. ExecuteScalar
@@ -56,7 +66,8 @@
<li>Lots of missing functionality and bugs.</li>
<li>Works with SQL# command-line and GTK# GUI versions.</li>
<li>Works with SQL# command-line and GTK# versions in cvs. Only works with
simple character data though.</li>
</ul>
@@ -68,12 +79,12 @@
<li>transactions (WORKING)</li>
<li>Stored Procedures, Functions, and Packages support</li>
<li>Be able to fill a DataTable in a DataSet via a data adapter (IN PROGRESS)</li>
<li>Support for Oracle 8i and 9i (WORKING)</li>
<li>Support for Oracle 8i (WORKING</li>
<li>Support for Oracle 9i (UNKNOWN)</li>
<li>Support LOBs</li>
<li>Support all the data types</li>
<li>Implement Connection pooling</li>
<li>Security</li>
<li>Once Oracle 10g is released, make sure Mono works with Oracle 10g.</li>
</ul>
@@ -88,7 +99,9 @@
Registration to the <a href="http://technet.oracle.com/">Oracle Technology Network</a> is free. If installing on Linux,
I suggest you do a lot of searching to see how others installed Oracle on Linux.</li>
<li>Make sure System.Data.OracleClient.dll assembly is built.</li>
<li>Make sure System.Data.OracleClient.dll assembly is built, if not, go
into System.Data.OracleClient and do a make -f makefile.gnu (on Linux) or
../../nant/NAnt.exe (on Windows using Cygwin).</li>
<li>Take a look at TestOracleClient.cs found at mcs/class/System.Data.OracleClient/Test</li>
@@ -148,10 +161,12 @@
-r System.Data.OracleClient.dll
</pre>
</li>
<li>Build on Windows:
<li>Build on Windows via Cygwin:
<pre>
mcs TestExample.cs /r:System.Data.dll \
/r:System.Data.OracleClient.dll
mono C:/cygwin/home/MyHome/mono/install/bin/mcs.exe \
TestExample.cs \
-lib:C:/cygwin/home/MyHome/mono/install/lib \
-r System.Data.dll -r System.Data.OracleClient.dll
</pre>
</li>
</ul>
-2
View File
@@ -10,8 +10,6 @@
<li><a href="http://www.go-mono.pl">Mono Poland</a>:
Mono site for polish users.
<li><a href="http://primates.ximian.com/~atsushi/mono-jp/">Mono Japanese Translation</a>:
Mono site Japanese translation pages. Translated sources are maintained at <a href="http://forge.novell.com/modules/xfmod/project/?mono-jp">Novell Forge</a>.
</ul>
* User sites
-246
View File
@@ -1,246 +0,0 @@
System.Object
System.Exception
System.ValueType
System.Delegate
System.MulticastDelegate
System.Enum
System.Activator
System.ArgIterator
System.__ComObject
System.TypedReference
System.Security.AllowPartiallyTrustedCallersAttribute
System.Runtime.Serialization.Formatter
System.Runtime.Serialization.FormatterConverter
System.Runtime.Serialization.FormatterServices
System.Runtime.Serialization.ObjectIDGenerator
System.Runtime.Serialization.ObjectManager
System.Reflection.ModuleResolveEventHandler
System.Reflection.Pointer
System.Globalization.CompareInfo
System.Globalization.HebrewCalendar
System.Globalization.HijriCalendar
System.Globalization.JapaneseCalendar
System.Globalization.KoreanCalendar
System.Globalization.SortKey
System.Globalization.StringInfo
System.Globalization.TaiwanCalendar
System.Globalization.TextElementEnumerator
System.Globalization.TextInfo
System.Globalization.ThaiBuddhistCalendar
System.IO.IsolatedStorage.IsolatedStorageFile
System.Reflection.Emit.MethodRental
System.Runtime.CompilerServices.AccessedThroughPropertyAttribute
System.Runtime.CompilerServices.CallConvCdecl
System.Runtime.CompilerServices.CallConvStdcall
System.Runtime.CompilerServices.CallConvThiscall
System.Runtime.CompilerServices.CallConvFastcall
System.Runtime.CompilerServices.CustomConstantAttribute
System.Runtime.CompilerServices.DateTimeConstantAttribute
System.Runtime.CompilerServices.DiscardableAttribute
System.Runtime.CompilerServices.DecimalConstantAttribute
System.Runtime.CompilerServices.CompilationRelaxationsAttribute
System.Runtime.CompilerServices.CompilerGlobalScopeAttribute
System.Runtime.CompilerServices.IDispatchConstantAttribute
System.Runtime.CompilerServices.IsVolatile
System.Runtime.CompilerServices.IUnknownConstantAttribute
System.Runtime.CompilerServices.RequiredAttributeAttribute
System.Runtime.InteropServices.ArrayWithOffset
System.Runtime.InteropServices.DispIdAttribute
System.Runtime.InteropServices.ClassInterfaceType
System.Runtime.InteropServices.ClassInterfaceAttribute
System.Runtime.InteropServices.ComVisibleAttribute
System.Runtime.InteropServices.LCIDConversionAttribute
System.Runtime.InteropServices.ComRegisterFunctionAttribute
System.Runtime.InteropServices.ComUnregisterFunctionAttribute
System.Runtime.InteropServices.ProgIdAttribute
System.Runtime.InteropServices.ImportedFromTypeLibAttribute
System.Runtime.InteropServices.IDispatchImplType
System.Runtime.InteropServices.IDispatchImplAttribute
System.Runtime.InteropServices.ComSourceInterfacesAttribute
System.Runtime.InteropServices.ComConversionLossAttribute
System.Runtime.InteropServices.TypeLibTypeFlags
System.Runtime.InteropServices.TypeLibFuncFlags
System.Runtime.InteropServices.TypeLibVarFlags
System.Runtime.InteropServices.TypeLibTypeAttribute
System.Runtime.InteropServices.TypeLibFuncAttribute
System.Runtime.InteropServices.TypeLibVarAttribute
System.Runtime.InteropServices.ComImportAttribute
System.Runtime.InteropServices.PreserveSigAttribute
System.Runtime.InteropServices.ComAliasNameAttribute
System.Runtime.InteropServices.AutomationProxyAttribute
System.Runtime.InteropServices.PrimaryInteropAssemblyAttribute
System.Runtime.InteropServices.CoClassAttribute
System.Runtime.InteropServices.ComEventInterfaceAttribute
System.Runtime.InteropServices.COMException
System.Runtime.InteropServices.ComMemberType
System.Runtime.InteropServices.CurrencyWrapper
System.Runtime.InteropServices.DispatchWrapper
System.Runtime.InteropServices.ErrorWrapper
System.Runtime.InteropServices.ExtensibleClassFactory
System.Runtime.InteropServices.HandleRef
System.Runtime.InteropServices.InvalidComObjectException
System.Runtime.InteropServices.InvalidOleVariantTypeException
System.Runtime.InteropServices.TypeLibImporterFlags
System.Runtime.InteropServices.ExporterEventKind
System.Runtime.InteropServices.ITypeLibExporterNotifySink
System.Runtime.InteropServices.ITypeLibConverter
System.Runtime.InteropServices.MarshalDirectiveException
System.Runtime.InteropServices.ObjectCreationDelegate
System.Runtime.InteropServices.RuntimeEnvironment
System.Runtime.InteropServices.RegistrationServices
System.Runtime.InteropServices.SafeArrayRankMismatchException
System.Runtime.InteropServices.SafeArrayTypeMismatchException
System.Runtime.InteropServices.SEHException
System.Runtime.InteropServices.TypeLibConverter
System.Runtime.InteropServices.BIND_OPTS
System.Runtime.InteropServices.UCOMIBindCtx
System.Runtime.InteropServices.UCOMIConnectionPointContainer
System.Runtime.InteropServices.UCOMIConnectionPoint
System.Runtime.InteropServices.UCOMIEnumMoniker
System.Runtime.InteropServices.CONNECTDATA
System.Runtime.InteropServices.UCOMIEnumConnections
System.Runtime.InteropServices.UCOMIEnumConnectionPoints
System.Runtime.InteropServices.UCOMIEnumString
System.Runtime.InteropServices.UCOMIEnumVARIANT
System.Runtime.InteropServices.FILETIME
System.Runtime.InteropServices.UCOMIMoniker
System.Runtime.InteropServices.UCOMIPersistFile
System.Runtime.InteropServices.UCOMIRunningObjectTable
System.Runtime.InteropServices.STATSTG
System.Runtime.InteropServices.UCOMIStream
System.Runtime.InteropServices.DESCKIND
System.Runtime.InteropServices.BINDPTR
System.Runtime.InteropServices.UCOMITypeComp
System.Runtime.InteropServices.TYPEKIND
System.Runtime.InteropServices.TYPEFLAGS
System.Runtime.InteropServices.IMPLTYPEFLAGS
System.Runtime.InteropServices.TYPEATTR
System.Runtime.InteropServices.FUNCDESC
System.Runtime.InteropServices.IDLFLAG
System.Runtime.InteropServices.IDLDESC
System.Runtime.InteropServices.PARAMFLAG
System.Runtime.InteropServices.PARAMDESC
System.Runtime.InteropServices.TYPEDESC
System.Runtime.InteropServices.ELEMDESC
System.Runtime.InteropServices.VARDESC
System.Runtime.InteropServices.DISPPARAMS
System.Runtime.InteropServices.EXCEPINFO
System.Runtime.InteropServices.FUNCKIND
System.Runtime.InteropServices.INVOKEKIND
System.Runtime.InteropServices.CALLCONV
System.Runtime.InteropServices.FUNCFLAGS
System.Runtime.InteropServices.VARFLAGS
System.Runtime.InteropServices.UCOMITypeInfo
System.Runtime.InteropServices.SYSKIND
System.Runtime.InteropServices.LIBFLAGS
System.Runtime.InteropServices.TYPELIBATTR
System.Runtime.InteropServices.UCOMITypeLib
System.Runtime.InteropServices.UnknownWrapper
System.Runtime.Remoting.IObjectHandle
System.Runtime.Remoting.IRemotingTypeInfo
System.Runtime.Remoting.IChannelInfo
System.Runtime.Remoting.IEnvoyInfo
System.Runtime.Remoting.RemotingConfiguration
System.Runtime.Remoting.TypeEntry
System.Runtime.Remoting.ActivatedClientTypeEntry
System.Runtime.Remoting.ActivatedServiceTypeEntry
System.Runtime.Remoting.WellKnownClientTypeEntry
System.Runtime.Remoting.WellKnownServiceTypeEntry
System.Runtime.Remoting.RemotingException
System.Runtime.Remoting.ServerException
System.Runtime.Remoting.RemotingTimeoutException
System.Runtime.Remoting.RemotingServices
System.Runtime.Remoting.InternalRemotingServices
System.Runtime.Remoting.SoapServices
System.Runtime.Remoting.Activation.UrlAttribute
System.Runtime.Remoting.Messaging.IMessageSink
System.Runtime.Remoting.Messaging.AsyncResult
System.Runtime.Remoting.Messaging.CallContext
System.Runtime.Remoting.Messaging.ILogicalThreadAffinative
System.Runtime.Remoting.Messaging.InternalMessageWrapper
System.Runtime.Remoting.Messaging.IMethodCallMessage
System.Runtime.Remoting.Messaging.MethodCallMessageWrapper
System.Runtime.Remoting.Messaging.HeaderHandler
System.Runtime.Remoting.Messaging.IMessageCtrl
System.Runtime.Remoting.Messaging.IRemotingFormatter
System.Runtime.Remoting.Messaging.ReturnMessage
System.Runtime.Remoting.Messaging.MethodCall
System.Runtime.Remoting.Messaging.ConstructionCall
System.Runtime.Remoting.Messaging.MethodResponse
System.Runtime.Remoting.Messaging.ConstructionResponse
System.Runtime.Remoting.Messaging.MethodReturnMessageWrapper
System.Runtime.Remoting.Messaging.OneWayAttribute
System.Runtime.Remoting.Messaging.MessageSurrogateFilter
System.Runtime.Remoting.Messaging.RemotingSurrogateSelector
System.Runtime.Remoting.Contexts.CrossContextDelegate
System.Runtime.Remoting.Contexts.ContextProperty
System.Runtime.Remoting.Contexts.IContextPropertyActivator
System.Runtime.Remoting.Contexts.IContributeClientContextSink
System.Runtime.Remoting.Contexts.IContributeDynamicSink
System.Runtime.Remoting.Contexts.IContributeEnvoySink
System.Runtime.Remoting.Contexts.IContributeObjectSink
System.Runtime.Remoting.Contexts.IContributeServerContextSink
System.Runtime.Serialization.Formatters.InternalRM
System.Runtime.Serialization.Formatters.InternalST
System.Runtime.Serialization.Formatters.SoapMessage
System.Runtime.Serialization.Formatters.SoapFault
System.Runtime.Serialization.Formatters.ServerFault
System.Runtime.Serialization.Formatters.Binary.BinaryFormatter
System.Security.Cryptography.CryptoConfig
System.Security.Cryptography.KeyedHashAlgorithm
System.Security.Cryptography.HMACSHA1
System.Security.Cryptography.MACTripleDES
System.Security.Cryptography.MaskGenerationMethod
System.Security.Cryptography.PasswordDeriveBytes
System.Security.Cryptography.PKCS1MaskGenerationMethod
System.Security.Cryptography.RC2
System.Security.Cryptography.RC2CryptoServiceProvider
System.Security.Cryptography.RSACryptoServiceProvider
System.Security.Cryptography.RSAOAEPKeyExchangeDeformatter
System.Security.Cryptography.RSAOAEPKeyExchangeFormatter
System.Security.Cryptography.RSAPKCS1KeyExchangeDeformatter
System.Security.Cryptography.RSAPKCS1KeyExchangeFormatter
System.Security.Cryptography.RSAPKCS1SignatureDeformatter
System.Security.Cryptography.RSAPKCS1SignatureFormatter
System.Security.Cryptography.SHA1Managed
System.Security.Cryptography.TripleDES
System.Security.Cryptography.TripleDESCryptoServiceProvider
System.Security.Permissions.EnvironmentPermission
System.Security.Permissions.FileDialogPermission
System.Security.Permissions.IsolatedStorageFilePermission
System.Security.Permissions.PrincipalPermissionAttribute
System.Security.Permissions.SecurityPermissionAttribute
System.Security.Permissions.PublisherIdentityPermissionAttribute
System.Security.Permissions.PublisherIdentityPermission
System.Security.Permissions.ReflectionPermission
System.Security.Permissions.RegistryPermission
System.Security.Permissions.PrincipalPermission
System.Security.Permissions.SiteIdentityPermission
System.Security.Permissions.StrongNameIdentityPermission
System.Security.Permissions.StrongNamePublicKeyBlob
System.Security.Permissions.UIPermission
System.Security.Permissions.UrlIdentityPermission
System.Security.Permissions.ZoneIdentityPermission
System.Security.Policy.ApplicationDirectory
System.Security.Policy.ApplicationDirectoryMembershipCondition
System.Security.Policy.FirstMatchCodeGroup
System.Security.Policy.Hash
System.Security.Policy.HashMembershipCondition
System.Security.Policy.NetCodeGroup
System.Security.Policy.PermissionRequestEvidence
System.Security.Policy.Publisher
System.Security.Policy.PublisherMembershipCondition
System.Security.Policy.Site
System.Security.Policy.SiteMembershipCondition
System.Security.Policy.StrongName
System.Security.Policy.StrongNameMembershipCondition
System.Security.Policy.UnionCodeGroup
System.Security.Policy.Url
System.Security.Policy.UrlMembershipCondition
System.Security.Policy.Zone
System.Security.Policy.ZoneMembershipCondition
System.Security.Principal.WindowsIdentity
System.Security.Principal.WindowsImpersonationContext
System.Security.Principal.WindowsPrincipal
System.Threading.CompressedStack
-204
View File
@@ -1,204 +0,0 @@
* Writing performant .NET and Mono applications
The following document contains a few hints on how to improve
the performance of your Mono/.NET applications.
These are just guidelines, and you should still profile your
code to find the actual performance problems in your
application. It is never a smart idea to make a change with the
hopes of improving the performance of your code without first
measuring. In general, these guidelines should serve as ideas
to help you figure out `how can I make this method run faster'.
It is up to you to figure out, `Which method is running slowly.'
** Using the Mono profiler
So, how does one measure what method are running slowly? A profiler
helps with this task. Mono includes a profiler that is built
into the runtime system. You can invoke this profiler on your program
by running with the --profile flag.
<pre>
mono --profile program.exe
</pre>
The above will instruct Mono to instrument your application
for profiling. The default Mono profiler will record the time
spent on a routine, the number of times the routine called,
the memory consumed by each method broken down by invoker, and
the total amount of memory consumed.
It does this by asking the JIT to insert a call to the profiler
every time a method is entered or left. The profiler times the
amount of time elapsed between the beginning and the end of the
call. The profiler is also notified of allocations.
When the program has finished executing, the profiler prints the
data in human readable format. It looks like:
<pre>
Total time spent compiling 227 methods (sec): 0.07154
Slowest method to compile (sec): 0.01893: System.Console::.cctor()
Time(ms) Count P/call(ms) Method name
########################
91.681 1 91.681 .DebugOne::Main()
Callers (with count) that contribute at least for 1%:
1 100 % .DebugOne::Main(object,intptr,intptr)
...
Total number of calls: 3741
...
Allocation profiler
Total mem Method
########################
406 KB .DebugOne::Main()
406 KB 1000 System.Int32[]
Callers (with count) that contribute at least for 1%:
1 100 % .DebugOne::Main(object,intptr,intptr)
Total memory allocated: 448 KB
</pre>
At the top, it shows each method that is called. The data is sorted
by the total time that the program spent within the method. Then
it shows how many times the method was called, and the average time
per call.
Below this, it shows the top callers of the method. This is very useful
data. If you find, for example, that the method Data::Computate () takes
a very long time to run, you can look to see if any of the calls can be
avoided.
Two warnings must be given about the method data. First,
the profiler has an overhead associated with it. As such,
a high number of calls to a method may show up as comsuming
lots of time, when in reality they do not consume much time
at all. If you see a method that has a very high number of
calls, you may be able to ignore it. However, do consider
removing calls if possible, as that will sometimes help
performance. This problem is often seen with the use
of built in collection types.
Secondly, due to the nature of the profiler, recursive calls
have extermely large times (because the profiler double counts
when the method calls itself). One easy way to see this problem
is that if a method is shown as taking more time than the Main
method, it is very likely recursive, and causing this problem.
Below the method data, allocation data is shown. This shows
how much memory each method allocates. The number beside
the method is the total amount of memory. Below that, it
is broken down into types. Then, the caller data is given. This
data is again useful when you want to figure out how to eliminate calls.
You might want to keep a close eye on the memory consumption
and on the method invocation counts. A lot of the
performance gains in MCS for example came from reducing its
memory usage, as opposed to changes in the execution path.
** Memory Management in the .NET/Mono world.
Since Mono and .NET offer automatic garbage collection, the
programmer is freed from having to track and dispose the
objects it consumes (except for IDispose-like classes). This
is a great productivity gain, but if you create thousands of
objects, that will make the garbage collector do more work,
and it might slow down your application.
Remember, each time you allocate an object, the GC is forced
to find space for the object. Each object has an 8 byte overhead
(4 to tell what type it is, then 4 for a sync block). If
the GC finds that it is running out of room, it will scan every
object for pointers, looking for unreferenced objects. If you allocate
extra objects, the GC then must take the effort to free the objects.
Mono uses the Boehm GC, which is a conservative collector,
and this might lead to some memory fragmentation and unlike
generational GC systems, it has to scan the entire allocated
memory pool.
*** Boxing
The .NET framework provides a rich hierchy of object types.
Each object not only has value information, but also type
information associated with it. This type information makes
many types of programs easier to write. It also has a cost
associated with it. The type information takes up space.
In order to reduce the cost of type information, almost every
Object Oriented language has the concept of `primitatives'.
They usually map to types such as integers and bools. These
types do not have any type information associated with them.
However, the language also must be able to treat primitatives
as first class datums -- in the class with objects. Languages
handle this issue in different ways. Some choose to make a
special class for each primative, and force the user to do an
operation such as:
<pre>
// This is Java
list.add (new Integer (1));
System.out.println (list.get (1).intValue ());
</pre>
The C# design team was not satisfied with this type
of construct. They added a notion of `boxing' to the language.
Boxing preforms the same thing as Java's <code>new Integer (1)</code>.
The user is not forced to write the extra code. However,
behind the scenes the <em>same thing</em> is being done
by the runtime. Each time a primative is cast to an object,
a new object is allocated.
You must be careful when casting a primative to an object.
Note that because it is an implicit conversion, you will
not see it in your code. For example, boxing is happening here:
<pre>
ArrayList foo = new ArrayList ();
foo.Add (1);
</pre>
In high performance code, this operation can be very costly.
*** Using structs instead of classes for small objects
For small objects, you might want to consider using value
types (structs) instead of object (classes).
However, you must be careful that you do not use the struct
as an object, in that case it will actually be more costly.
As a rule of thumb, only use structs if you have a small
number of fields (totaling less than 32 bytes), and
need to pass the item `by value'. You should not box the object.
*** Assisting the Garbage Collector
Although the Garbage Collector will do the right thing in
terms of releasing and finalizing objects on time, you can
assist the garbage collector by clearing the fields that
points to objects. This means that some objects might be
elegible for collection earlier than they would, this can help
reduce the memory consumption and reduce the work that the GC
has to do.
** foreach
The <tt>foreach</tt> C# statement handles various kinds of
different constructs (about seven different code patterns are
generated). Typically foreach generates more efficient code
than loops constructed manually, and also ensures that objects
which implement IDispose are properly released.
But foreach sometimes might generate code that under stress
performs badly. Foreach performs badly when its used in tight
loops, and its use leads to the creation of many enumerators.
Although technically obtaining an enumerator for some objects
like ArrayList is more efficient than using the ArrayList
indexer, the pressure introduced due to the extra memory
requirements and the demands on the garbage collector make it
more inneficient.
There is no straight-forward rule on when to use foreach, and
when to use a manual loop. The best thing to do is to always
use foreach, and only when profile shows a problem, replace
foreach with for loops.
+1 -1
View File
@@ -8,7 +8,7 @@
Currently you can read our plans for <a
href="ado-net.html">ADO.NET</a>, <a
href="asp-net.html">ASP.NET</a>, <a href="java.html">Java</a> and
href="asp-net">ASP.NET</a>, <a href="java.html">Java</a> and
<a href="winforms.html">WinForms</a>.
+1 -1
View File
@@ -545,8 +545,8 @@ mono TestExample.exe
"User ID=postgres;" +
"Password=fun2db;";
IDbConnection dbcon;
dbcon = new NpgsqlConnection(connectionString);
dbcon.Open();
dbcon = new NpgsqlConnection(connectionString);
IDbCommand dbcmd = dbcon.CreateCommand();
// requires a table to be created named employee
// with columns firstname and lastname
+2 -4
View File
@@ -13,9 +13,7 @@
*** Jitter
Works on MacOS X 10.2 and Linux/PPC.
There are known problems on MacOS 10.3
Start the port
** Documentation
@@ -30,6 +28,6 @@
*** Calling conventions:
<a href="http://refspecs.freestandards.org/elf/elfspec_ppc.pdf">The PowerPC SystemV ABI specification</a>
<a href="http://www.esofta.com/softspecs.html">The PowerPC SystemV ABI specification</a>
+17 -4
View File
@@ -9,7 +9,7 @@
** Microsoft .NET
The <a href="http://msdn.microsoft.com/netframework">Microsoft.NET site.</a>
The <a href="http://msdn.microsoft.com/net">Microsoft.NET site.</a>
The Microsoft .NET Framework can be downloaded <a
href="http://msdn.microsoft.com/library/default.asp?url=/downloads/list/netdevframework.asp">here</a>
@@ -74,13 +74,21 @@
<li><a href="http://www.gotdotnet.com/userarea/keywordsrch.aspx?keyword=winchurn">http://www.gotdotnet.com/userarea/keywordsrch.aspx?keyword=winchurn</a>
</ul>
** Presentations
Currently the <a href="Presentations/O-Reilly">O'Reilly</a>
presentation on Mono is available. Arturo Espinosa has given
a talk on Mono in Mexico and made <a
href="http://construct.ximian.com/~arturo/Presentations/Mono.OLS/html">spanish
slides</a>
** ECMA Documentation.
You can get the documentation for the ECMA specs from:
<ul>
* <a href="http://www.ecma-international.org/publications/standards/Ecma-334.HTM">C# Language Specification</a>
* <a href="http://www.ecma-international.org/publications/standards/Ecma-335.HTM">Common Language Infrastructure</a>
* <a href="http://www.ecma-international.org/publications/standards/ECMA-334.HTM">C# Language Specification</a>
* <a href="http://www.ecma-international.org/publications/standards/ECMA-335.HTM">Common Language Infrastructure</a>
</ul>
@@ -89,6 +97,7 @@
<ul>
* <a href="http://msdn.microsoft.com/net/ecma">At MSDN</a>
* <a href="http://www.dotnetexperts.com">Dot Net Experts</a>
* <a href="http://developer.intel.com/software/idap/ecma">Intel</a>
* <a href="http://lightning.csse.monash.edu.au/.net/CLI">Monash University</a>
</ul>
@@ -144,7 +153,7 @@
<li><b>Class Libraries</b></li>
<ul>
* <a href="http://cs-sdl.sourceforge.net/">SDL for
* <a href="http://9mm.com/~ogl/sdldotnet/">SDL for
.NET:</a> Bindings for the popular SDL graphics library.
@@ -184,6 +193,10 @@
* <a
href="http://www.southern-storm.com.au/portable_net.html">Portable.NET:</a>
Another implementation of the CLI and C# compiler.
* A Free (GFDL) tutorial on C# in Spanish with
examples, slides, and extras (under development). Get it <a
href="http://geneura.ugr.es/~jaime/csharp/">here</a>.
</ul>
** GNOME Documentation
+9 -17
View File
@@ -31,14 +31,11 @@
<ul>
<li>Thanks to Sebastien Pouliot, we now have NT Authentication (Integrated Security) support. This support was
added after the release of Mono 0.29. So, you either get it from cvs or wait for the Mono 0.30 release.</li>
<li>Able to connect to Microsoft SQL Server 7/2000 databases via SQL Server authentication and NT Authentication.</li>
<li>Able to connect to Microsoft SQL Server 7/2000 databases</li>
<li>Connection pooling works.</li>
<li>Stored Procedures work.</li>
<li>Stored Procedures work</li>
<li>Parameters work.</li>
@@ -62,6 +59,8 @@
<li>Uses TDS Protocol Version 7.0</li>
<li><a href="http://www.go-mono.com/tds-providers.html">Design of the Microsoft SQL Server, Sybase, and TDS Providers in Mono</a></li>
<li>Works in the SQL# command-line and GTK# GUI version</li>
</ul>
@@ -72,9 +71,9 @@
<li>Needs more testing</li>
<li>Start work on TDS Protocol Version 8.0 support</li>
<li>Would like to figure out how to connect via Trusted_Connection or Integrated Security</li>
<li>Add support for .NET 1.2 and 2.0 and Microsoft SQL Server (Yukon) support</li>
<li>Start work on TDS Protocol Version 8.0 support</li>
</ul>
@@ -90,10 +89,9 @@
</ul>
</li>
<li><b>IMPORTANT:</b> If using Microsoft SQL Server 2000, make sure
<li>If using Microsoft SQL Server 2000, make sure
you are using at least Service Pack 3 for Microsoft SQL Server 2000. If using
MSDE 2000, make sure you have the special Service Pack 3 for MSDE 2000. You
can get it from <a href="http://www.microsoft.com/sql/downloads/2000/sp3.asp">here</a></li>
MSDE 2000, make sure you have the special Service Pack 3 for MSDE 2000.</li>
<li>For those that only have MSDE installed. You can change the authentication mode
from Windows Only Authentication to SQL Server and Windows Authentications (also knows as Mixed-mode authentication)
@@ -123,17 +121,11 @@
to explicitly use a User ID and Password
authenticated by SQL Server.</li>
<li>Has a connection string format for SQL Server Authentication:
<li>Has a connection string format:
<pre>
Server=hostname;Database=databaseName;User ID=userid;Password=password
</pre>
</li>
<li>Has a connection string format for NT Authentication:
<pre>
Server=hostname;Database=databaseName;User ID=windowsUserid;Password=windowsPassword;Integrated Security=SSPI
</pre>
</li>
<li>The Server part can be used three ways:
<table border=1>
+2 -2
View File
@@ -25,7 +25,7 @@
<li>Created by Vladimir Vukicevic so he could have a database of
thumbnail images for mPhoto. mPhoto is GUI application
for cataloging images. mPhoto runs on Mono
and uses <a href="http://www.go-mono.com/gtk-sharp.html">GTK#</a> for its GUI.</li>
and uses <a href="http:www.go-mono.com/gtk-sharp.html">GTK#</a> for its GUI.</li>
<li>Bugs with Mono or the data provider should be reported
in Mono's Bugzilla <a href="http://bugzilla.ximian.com/">here</a>. If you
@@ -82,7 +82,7 @@
{
string connectionString = "URI=file:SqliteTest.db";
IDbConnection dbcon;
dbcon = new SqliteConnection(connectionString);
dbcon = new MySQLConnection(connectionString);
dbcon.Open();
IDbCommand dbcmd = dbcon.CreateCommand();
// requires a table to be created named employee
+2
View File
@@ -17,6 +17,8 @@
<li>Requires the assembly Mono.Data.Tds.dll which implements the TDS protocol in 100% C#.</li>
<li>Uses TDS Protocol Version 5.0</li>
<li>Does not support trusted connections</li>
<li>Bugs with Mono or the data provider should be reported
in Mono's Bugzilla <a href="http://bugzilla.ximian.com/">here</a>. If you
+2
View File
@@ -18,6 +18,8 @@
<li>Uses TDS Protocol Version 4.2 by default</li>
<li>Does not support trusted connections</li>
<li>Bugs with Mono or the data provider should be reported
in Mono's Bugzilla <a href="http://bugzilla.ximian.com/">here</a>. If you
do not have Bugzilla user account, it is free
+4 -126
View File
@@ -6,26 +6,7 @@
is very common to introduce bugs in existing code. A test suite
helps us fix the bugs as soon as they are introduced.
There are various kinds of tests in Mono:
<ul>
<li><a href="#unit"><b>Class Library Unit
Tests:</b></a> These are used to test the class
libraries.
<li><a href="#compiler"><b>Compiler tests</b></a>: Both
tests that should pass and tests that should fail are included.
<li><a href="#runtime"><b>Runtime tests</b></a>: Tests for
the virtual machine.
<li><a href="#aspnet"><b>ASP.NET tests</b></a>: ASP.NET tests.
<li><a href="#ws"><b>Web Services tests</b></a>: Web Services
client/server tests.
</ul>
<a name="unit"></a>
* Class Library Tests
** Class Library Tests
All classes in Mono libraries should have comprehensive unit test
suites to go with them. Unit testing is a software engineering
@@ -34,29 +15,6 @@
that they work correctly. Mono also needs a testing framework
to make it easy to write and run lots of tests.
In some classes, we might also provide standalone tests because of
some reasons such as too huge testcases, another downloading and so on.
(For example, managed XSLT has standalone test which downloads and
expands some megabytes of OASIS test suite.)
Here I list them up as long as I know. If you are going to add another
standalone tests, please add one line here. It is also recommended that
you add some notes on how to build and run tests.
<ul>
* Mono.Data/test/
* System.Data/Test, and some individual ADO.NET libraries:
there are some standalone tests. See the bottom of <a href="ado-net.html">
ADO.NET page</a> for detail.
* System.Web/Test/TestMonoWeb : see README
* System.Web.Services/Test/standalone : see README
* System.Windows.Forms/SWFTest/
* System.XML/Tests/System.Xml.Schema/standalone_tests : see README
* System.XML/System.Xml.Serialization/standalone_tests/
* System.XML/Tests/System.Xml.Xsl/standalone_tests : see README
</ul>
** Getting started
@@ -84,8 +42,8 @@
testing.
Once all of that is done, you can do a 'make test' from the top mcs
directory. Your test class needs also to be listed in the
.sources file at the top of the Test directory.
directory. Your test class will be automagically included in the
build and the tests will be run along with all the others.
* Tips on writing Unit tests.
@@ -154,7 +112,7 @@
bug in their runtime or something is misleading or wrong in their
documentation. In this case, please put a detailed description of the
problem to mcs/class/doc/API-notes and do also report it to the
<a href="mailing-lists.html">mailing list</a> - we'll forward this to the
<a href="mailing-lists">mailing list</a> - we'll forward this to the
Microsoft people from time to time to help them fix their documentation
and runtime.
@@ -187,83 +145,3 @@
Normally, after you send a couple of well-written new files
and/or patches to the list, you will be given cvs access.
<a name="compiler"></a>
* Compiler tests
Mono ships with three compilers: C#, VB.NET and JScript. The
tests are ran by running the makefile target `make
run-test-local' in the appropriate directory.
The C# compilation tests live in mcs/tests, and the C# error
tests live in mcs/errors.
The VB.NET compilation tests live in mcs/btests.
<a name="runtime"></a>
* Runtime Tests
These tests verify the virtual machine, to run these tests, do:
<pre>
cd mono/mono/tests
make test
</pre>
<a name="aspnet"></a>
* ASP.NET tests
XSP, the Mono ASP.NET server has tests for ASP.NET pages. It uses
<a href="http://nunitasp.sourceforge.net">NUnitAsp</a>. Right now
it only has standalone tests, ie., tests that do not need their own
global.asax or web.config files.
If you want to run them, get the xsp CVS module and install it. Then:
<pre>
cd xsp/nunit-tests
make
cd standalone
xsp
</pre>
And from another terminal:
<pre>
cd xsp/nunit-tests/standalone
nunit-console standalone-tests.dll
</pre>
<a name="ws"></a>
* Web Services tests
The Test directory for the System.Web.Services assembly contains a
standalone test suite for testing web services. It tests:
<ul>
<li>Proxy generation using the wsdl tool</li>
<li>Access to web services using the generated client proxies</li>
<li>Execution of web services in the server</li>
</ul>
This suite not only tests web services running on XSP, but it can also test
services running on other platforms and that are available in internet. This
will help track down interoperability issues.
To build the test suite, just run:
<pre>
cd mcs/class/System.Web.Services/Test/standalone
xsp --root server
</pre>
And from another terminal:
<pre>
cd mcs/class/System.Web.Services/Test/standalone
make
nunit-console testclient.dll
</pre>
This will download the wsdl documents, generate the proxies, build a dll with
the proxies, and build the nunit tests. Then you can use nunit-console or
gnunit to run the tests (the nunit dll is testclient.dll).
Read the README file in mcs/class/System.Web.Services/Test/standalone for
more info.
+1 -53
View File
@@ -1,53 +1 @@
** System.Windows.Forms
Progress on Windows.Forms has been good, but we need more work
on this area. Currently redrawing of controls is not
funcional.
** Languages work
Mono has work-in-progress implementations of JScript and the
VB.NET languages
<ul>
<li>Write positive tests for those languages.
<li>Write negative tests for those languages.
<li>Mono-devel-list is the mailing list to discuss
improvements and fixes to those compilers.
</ul>
** Debugger
<ul>
<li>The Mono debugger needs some better widgets to
provide a useful environment, many of those have been
authored for Anjuta/gIDE, we should wrap those for the
debugger
<li>Design a small tool-command-language like Tcl to
build the debugger on top of it.
<li>Design work: a new UI design must be done
for the debugger and later implemented.
</ul>
** Research topics
<ul>
<li>Design and implement a command processor like the
Unix shell, but which uses .NET objects as commands.
This shell would be a CLS consumer ideally, and only
later a CLS producer. This should make it simple for
people to explore the .NET API interactively.
</ul>
** IDE development
Mono lacks an IDE, and we depend on third-parties to work on
these.
<ul>
Sharp
</ul>
Discuss with write new JIT
+2 -4
View File
@@ -20,7 +20,6 @@
1,CVS access,ccvs.html,ccvs.src
1,AnonCVS access,anoncvs.html,anoncvs.src
1,Forge,forge.html,forge.src
1,Compiling,compiling.html,compiling.src
0,Contributing,contributing.html,contributing.src
1,Hackers,hackers.html,hackers.src
1,Documentation,documentation.html,documentation.src
@@ -34,7 +33,7 @@
0,Resources,resources.html,resources.src
1,Beginning,mono-beginning.html,mono-beginning.src
1,Mailing Lists,mailing-lists.html,mailing-lists.src
1,Blogs,http://www.go-mono.com/monologue/
1,Blogs,http://www.go-mono.com/monologue
1,Ideas,ideas.html,ideas.src
1,Passport,passport.html,passport.src
1,Books,books.html,books.src
@@ -42,8 +41,8 @@
1,Languages,languages.html,languages.src
1,Debugging,jit-debug.html,jit-debug.src
0,Plans,plans.html,plans.src
1,Drawing,drawing.html,drawing.src
1,ADO.NET,ado-net.html,ado-net.src
1,Drawing,drawing.html,drawing.src
2,ProviderFactory,provider-factory.html,provider-factory.src
2,Firebird Interbase,firebird.html,firebird.src
2,IBM DB2,ibmdb2.html,ibmdb2.src
@@ -60,7 +59,6 @@
1,Crypto,crypto.html,crypto.src
1,Java,java.html,java.src
1,Windows.Forms,winforms.html,winforms.src
1,XML Classes,xml-classes.html,xml-classes.src
0,Class Status,class-status.html,class-status.src,cm/cormissing.css,cm/cormissing.js
1,corlib,class-status-corlib.html,class-status-corlib.src,cm/cormissing.css,cm/cormissing.js
1,System,class-status-System.html,class-status-System.src,cm/cormissing.css,cm/cormissing.js
-3
View File
@@ -216,9 +216,6 @@ function clickHandler (evt)
if (strAssembly)
{
if (strAssembly == 'mscorlib')
strAssembly = 'corlib';
strRoot = strRoot + strAssembly + '/';
if (strNamespace)
{
+1 -4
View File
@@ -21,7 +21,6 @@ OBJECTS= \
deploy/documentation.html \
deploy/download.html \
deploy/drawing.html \
deploy/compiling.html \
deploy/crypto.html \
deploy/embedded-api.html \
deploy/faq.html \
@@ -69,10 +68,8 @@ OBJECTS= \
deploy/testing.html \
deploy/tools.html \
deploy/winforms.html \
deploy/xml-classes.html \
deploy/class-library.html \
deploy/classlib-doc.html \
deploy/class-status.html \
deploy/class-status-corlib.html \
deploy/class-status-System.html \
deploy/class-status-System.Xml.html \
@@ -131,7 +128,7 @@ render-team-page.exe: render-team-page.cs
$(CSC) render-team-page.cs
clean:
rm -f $(OBJECTS) $(patsubst deploy/%.html,src/%.src, $(OBJECTS)) src/*.xml src/*.html.in ../class-status-* ../class-status infos/*.xml
rm -f $(OBJECTS) $(patsubst deploy/%.html,src/%.src, $(OBJECTS)) src/*.xml src/*.html.in ../class-status-* ../class-status infos/*
push:
cp -f $(NON_HTML_SOURCES) deploy
-60
View File
@@ -1,60 +0,0 @@
# Note that you will need Microsoft.NET to generate those masterinfos
# Customize to indicate your own installation dir.
DLL_PATH=c:/WINDOWS/Microsoft.NET/Framework/v1.1.4322
all: \
mscorlib.xml \
System.xml \
System.Xml.xml \
System.Data.xml \
System.Web.xml \
System.Web.Services.xml \
System.Runtime.Serialization.Formatters.Soap.xml \
System.Drawing.xml \
System.Security.xml \
System.DirectoryServices.xml \
System.Windows.Forms.xml \
Cscompmgd.xml
mscorlib.xml :
mono-api-info $(DLL_PATH)/mscorlib.dll > mscorlib.xml
System.xml :
mono-api-info $(DLL_PATH)/System.dll > System.xml
System.Xml.xml :
mono-api-info $(DLL_PATH)/System.Xml.dll > System.Xml.xml
System.Data.xml :
mono-api-info $(DLL_PATH)/System.Data.dll > System.Data.xml
System.Web.xml :
mono-api-info $(DLL_PATH)/System.Web.dll > System.Web.xml
System.Web.Services.xml :
mono-api-info $(DLL_PATH)/System.Web.Services.dll > System.Web.Services.xml
System.Runtime.Serialization.Formatters.Soap.xml :
mono-api-info $(DLL_PATH)/System.Runtime.Serialization.Formatters.Soap.dll > System.Runtime.Serialization.Formatters.Soap.xml
System.Drawing.xml :
mono-api-info $(DLL_PATH)/System.Drawing.dll > System.Drawing.xml
System.Security.xml :
mono-api-info $(DLL_PATH)/System.Security.dll > System.Security.xml
System.DirectoryServices.xml :
mono-api-info $(DLL_PATH)/System.DirectoryServices.dll > System.DirectoryServices.xml
System.Windows.Forms.xml :
mono-api-info $(DLL_PATH)/System.Windows.Forms.dll > System.Windows.Forms.xml
Cscompmgd.xml :
mono-api-info $(DLL_PATH)/Cscompmgd.dll > Cscompmgd.xml
clean:
rm mscorlib.xml System.xml System.Xml.xml System.Data.xml System.Web.xml System.Web.Services.xml System.Runtime.Serialization.Formatters.Soap.xml System.Drawing.xml System.Security.xml System.DirectoryServices.xml System.Windows.Forms.xml Cscompmgd.xml
+8 -48
View File
@@ -418,7 +418,7 @@
<image>timc.png</image>
<location>Waterloo, Ontario, Canada</location>
<location>Kitchener-Waterloo, Canada</location>
<tasks>
@@ -915,7 +915,7 @@
</name>
<e-mail>[email protected]</e-mail>
<e-mail>[email protected]</e-mail>
<image>none.png</image>
@@ -1017,23 +1017,17 @@
</name>
<e-mail>[email protected]</e-mail>
<e-mail>[email protected]</e-mail>
<image>none.png</image>
<location>Tokyo, Japan</location>
<organization>Ximian</organization>
<description>Mono Hacker</description>
<description>MIDI Programmer</description>
<tasks>
<task>System.Xml</task>
<task>RELAX NG</task>
<task>Japanese Website Translation</task>
<task>XML</task>
</tasks>
@@ -1428,7 +1422,7 @@
<e-mail>[email protected]</e-mail>
<image>jluke.png</image>
<image>none.png</image>
<location>Daytona, FL</location>
@@ -1492,16 +1486,12 @@
<organization></organization>
<description>hacker</description>
<description></description>
<tasks>
<task>WSE2</task>
<task>gacutil</task>
<task>MonoDevelop</task>
</tasks>
</contributor>
@@ -1543,7 +1533,7 @@
</name>
<e-mail>jordi [at] ximian.com</e-mail>
<e-mail>j[email protected]</e-mail>
<image>jordi.png</image>
@@ -1555,39 +1545,9 @@
<tasks>
<task>System.Drawing implementation</task>
<task>Windows.Forms implementation</task>
</tasks>
</contributor>
<contributor>
<name>
<first-name>Pedro</first-name>
<last-name>Abelleira Seco</last-name>
</name>
<e-mail>[email protected]</e-mail>
<image>pedroas.png</image>
<location>Galicia, Spain</location>
<organization></organization>
<description>Developer</description>
<tasks>
<task>MonoDevelop</task>
</tasks>
</contributor>
</contributors>
Binary file not shown.

Before

Width:  |  Height:  |  Size: 4.7 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 4.4 KiB

+3 -9
View File
@@ -2,7 +2,7 @@
<html>
<head>
<title>#TITLE#</title>
<link rel="icon" href="MonoIcon.png" type="image/png">
<link rel="icon" href="../MonoIcon.png" type="image/png">
<!-- background-image: url("images/bgsquares.gif"); -->
<style type="text/css">
<!--
@@ -38,12 +38,6 @@
border-bottom: 2px solid #dddddd;
}
.shell {
border-style: solid; background: #000000; color: #bbbbbb;
#777777; border-width:
1px; padding: 2pt;
margin:15px;
}
// -->
</style>
#CSS#
@@ -64,11 +58,11 @@
</td>
<td>
<a class="topmenu" href="download.html">Downloads</a> |
<a class="topmenu" href="http://go-mono.com/daily/">Daily snapshots</a> |
<a class="topmenu" href="http://go-mono.com/daily">Daily snapshots</a> |
<a class="topmenu" href="screenshots.html">Screenshots</a> |
<a class="topmenu" href="http://www.go-mono.com:8080">Documentation</a> |
<a class="topmenu" href="bugs.html">Bugs</a> |
<a class="topmenu" href="http://www.go-mono.com/monologue/">Blogs</a>
<a class="topmenu" href="blogs.html">Blogs</a>
</td>
</tr>
</table>
-310
View File
@@ -1,310 +0,0 @@
* XML Classes
** Abstract
XML library is used by several field of Mono such as ADO.NET and XML
Digital Signature (xmldsig). Here I write about System.Xml.dll and
related tools. This page won't include any classes which are in other
assemblies such as XmlDataDocument.
Note that current corlib has its own XML parser class named Mono.Xml.MiniParser.
Basically System.XML.dll feature has finished, or almost finished, so
I write this page mainly for bugs and improvement hints.
** System.Xml namespace
*** Document Object Model (Core)
DOM feature has already implemented. There is still missing feature.
<ul>
* ID constraint support is problematic because W3C DOM does not
specify handling of ID attributes into non-adapted element.
(MS.NET also looks incomplete in this area).
* I think, event feature is not fully tested. There are no
concrete desctiption on which events are risen, so we have to
do some experiment on MS.NET.
</ul>
*** Xml Writer
Here XmlWriter almost equals to XmlTextWriter. If you want to see
another implementation, check XmlNodeWriter.cs used in monodoc.
XmlTextWriter is completed. However, it looks nearly twice as slow as
MS.NET (I tried 1.1)
*** XmlResolver
Currently XmlTextReader uses specified XmlResolver. If nothing was supplied,
then it uses XmlUrlResolver. XmlResolver is used to parse external DTD,
importing XSL stylesheets and schemas etc.
However, XmlUrlResolver is still buggy (mainly because System.Uri is also
incomplete yet) and this results in several loading error.
XmlSecureResolver, which is introduced in MS .NET Framework 1.1 is basically
implemented, but it requires CAS (code access security) feature. We need to
fixup this class after ongoing CAS effort works.
You might also be interested in an improved <a href="http://codeblogs.ximian.com/blogs/benm/archives/000039.html">XmlCachingResolver</a> by Ben Maurer.
*** XmlNameTable
XmlNameTable itself is implemented. However, it should be actually used in
several classes. Currently it makes sense if compared names are both in
the table, they should be simply compared using ReferenceEquals(). We
have partially done in XmlNamespaceManager (in .NET 1.2 methods; if the
build is not NET_1_2 then it is internal use only).
*** Xml Stream Reader
When we are using ASCII document, we don't care which encoding we are using.
However, XmlTextReader must be aware of the specified encoding in XML
declaration. So we have internal XmlStreamReader class (and currently
XmlInputStream class. This may disappear since XmlStreamReader is enough to
handle this problem).
However, there seems some problems in these classes on reading network
stream (especially on Linux). This should be fixed soon, if we found the
actual reason.
*** XML Reader
XmlTextReader, XmlNodeReader and XmlValidatingReader are almost finished.
<ul>
* Most of the OASIS conformance test passes as Microsoft
does, but about W3C tests, it is still not perfect.
* I won't add any XDR support on XmlValidatingReader. (I haven't
ever seen XDR used other than Microsoft's BizTalk Server 2000,
and Now they have 2002 with XML Schema support)
</ul>
XmlTextReader and XmlValidatingReader should be faster than now. Currently
XmlTextReader looks nearly twice as slow as MS.NET, and XmlValidatingReader
(which uses this slow XmlTextReader) looks nearly three times slower. (Note
that XmlValidatingReader won't be slow as itself. It uses schema validating
reader and dtd validating reader.)
**** Some Advantages
The design of Mono's XmlValidatingReader is radically different from
that of Microsoft's implementation. Under MS.NET, DTD content validation
engine is in fact simple replacement of XML Schema validation engine.
Mono's DTD validation is designed fully separate and does validation
as normal XML parser does. For example, Mono allows non-deterministic DTD.
Another advantage of this XmlValidatingReader is support for *any* XmlReader.
Microsoft supports only XmlTextReader.
I added extra support interface named "IHasXmlParserContext", which is
considered in XmlValidatingReader.ResolveEntity(). Microsoft failed to
design XmlReader to support pluggable use of XmlReader (i.e. wrapping use
of other XmlReader) since XmlParserContext is required to support both
entity resolution and namespace manager. (In .NET 1.2, Microsoft also
supported similar to IHasXmlParserContext, named IXmlNamespaceResolver,
but it still does not provide any DTD information.)
We also have RELAX NG validating reader. See mcs/class/Commons.Xml.Relaxng.
** System.Xml.Schema
*** Summary
Basically it is completed. We can compile complex and simple types, refer to
external schemas, extend or restrict other types, or use substitution groups.
You can test how current schema validation engine is (in)complete by using
standalone test module
(see mcs/class/System.XML/Test/System.Xml.Schema/standalone_tests).
At least in my box, msxsdtest fails only 30 cases with bugfixed catalog.
*** Schema Object Model
Completed, except for some things to be fixed:
<ul>
* Complete facet support. Currently some of them is missing.
Recently David Sheldon is doing several fixes on them.
* ContentTypeParticle for pointless xs:choice is incomplete
(It is because fixing this arose another bugs in
compilation. Interestingly, MS.NET also fails around here,
so it might be nature of ContentTypeParticle design)
* Some derivation by restriction (DBR) handling is incorrect.
</ul>
*** Validating Reader
XML Schema validation feature is (currently) implemented on
Mono.Xml.Schema.XsdValidatingReader, which is internally used in
XmlValidatingReader.
Basically this is implemented and actually its feature is almost complete,
but I have only did validation feature testing. So we have to write more
tests on properties, methods, and events (validation errors).
** System.Xml.Serialization
Lluis rules ;-)
Well, in fact XmlSerializer is almost finished and is on bugfix phase.
However, we appliciate more tests. Please try
<ul>
* System.Web.Services to invoke SOAP services.
* xsd.exe and wsdl.exe to create classes.
</ul>
And if any problems were found, please file it to bugzilla.
Lluis also built interesting standalone test system placed under
mcs/class/System.Web.Services/Test/standalone.
You might also interested in genxs, which enables you to create custom
XML serializer. This is not included in Microsoft.NET.
See mcs/tools/genxs for the details.
** System.Xml.XPath and System.Xml.Xsl
There are two implementations for XSLT. One (and historical) implementation
is based on libxslt. Now we uses fully implemented managed XSLT.
As for Managed XSLT, we support msxsl:script.
It would be nice if we can support <a href="http://www.exslt.org/">EXSLT</a>.
<a href="http://msdn.microsoft.com/WebServices/default.aspx?pull=/library/en-us/dnexxml/html/xml05192003.asp">Microsoft has already done it</a>, but it
is not good code since it depends on internal concrete derivatives of
XPathNodeIterator classes. In general, .NET's "extension objects" is not
usable to return node-sets, so if we support EXSLT, it has to be done
internally inside our System.XML.dll. Volunteers are welcome.
Our managed XSLT implementation is still inefficient. XslTransform.Load()
and .Transform() looks three times slower (However it depends on
XmlTextReader which is also slow, so we are starting optimization from
that class, not XSLT itself). These number are only for specific cases,
and there might be more critical point on XSLT engine (mainly
XPathNodeIterator).
** System.Xml and ADO.NET v2.0
Microsoft introduced the first beta version of .NET Framework 1.2 runtime
and sdk (and Visual Studio Whidbey). They are now available on MSDN
_subscriber_ download (i.e. it is not publicly downloadable yet). It
contains several new classes.
There are two assemblies related to System.Xml v2.0; System.Xml.dll and
System.Data.SqlXml.dll (here I treat sqlxml.dll as part of System.Xml v2.0,
but note that it is also one of the ADO.NET 2.0 feature). There are several
namespaces such as MS.Internal.Xml and System.Xml. Note that .NET Framework
is pre-release version and MS.Internal.Xml namespace apparently shows that
it is not in stable status as yet.
System.Xml 2.0 contains several features such as:
<ul>
* XPathNavigator2 and XPathDocument2
* XML Query
* XmlAdapter
* XSLT IL generator (similar to Apache XSLTC) - it is
internal use
</ul>
Tim Coleman started ADO.NET 2.0 related works. Currently I have no plan to
implement System.Xml v2.0 classes and won't touch with them immediately,
but will start in next some months. If any of you wants to try this
frontier, we welcome your effort.
*** XPathNavigator2
System.Xml v2.0 implementation will be started from XPathDocument2 and
XPathNavigator2 implementations. Firstly, its document structure and
basic navigation feature will be implemented. And next, XPath2 engine
should be implemented (XPathNavigator2 looks very different from
XPathNavigator). Another requirement is schema based validation feature.
It needs some schema improvements, such like IXmlInfosetReader support.
(IXmlInfosetReader is in MS.Internal.Xml.)
*** XML Query
XML Query is a new face XML data manipulation language (well, at least new
to .NET world). It is similar to SQL, but intended to manipulate and to
support XML. It is similar to XSLT, but extended to support new features
such as XML Schema based datatypes.
XML Query implementation can be found mainly in System.Xml.Query and
MS.Internal.Xml.Query namespaces. Note that they are in
System.Data.SqlXml.dll.
MSDN documentation says that there are two kind of API for XML Query: High
Level API and Low Level API. At the time of this beta version, the Low Level
API is described not released yet (though it may be MS.Internal.Xml.*
classes). However, to implement the High Level API, the Low Level API will
be used. They looks to have interesting class structures in MS.Internal.Xml
related stuff, so it would be nice (and I will) start to learn about them.
They looks to have IL generator classes, but it would be difficult to
start from them.
*** System.Data.Mapping
System.Data.Mapping and System.Data.Mapping.RelationalSchema are the
namespaces for mapping support between database and xml. This is at
stubbing phase (incomplete as yet).
*** XmlAdapter
XmlAdapter is used to support XML based query and update using
XPathDocument2 and XPathNavigator2. This class is designed to synthesize
ADO.NET and System.Xml. It connects to databases, and querys data however
in XML shape into XPathDocument2, using Mapping schema above. This must be
done after several classes such as XPathDocument2 and MappingSchema.
** Miscellaneous Class Libraries
*** RELAX NG
I implemented an experimental RelaxngValidatingReader. It is far from
complete, especially simplification stuff (see RELAX NG spec chapter 4),
some constraints (in chapter 7), and datatype handling.
I am planning improvements (starts with renaming classes, giving more
kind error messages, supporting compact syntax and even object mapping),
but it is still my wishlist.
** Tools
*** xsd.exe
See <a href="ado-net.html">ADO.NET page</a>.
Microsoft has another inference class from XmlReader to XmlSchemaCollection
(Microsoft.XsdInference). It may be useful, but it won't be so easy.
** Miscellaneous
Sometimes I hear complain about System.dll and System.Xml.dll mutual
dependency: System.dll references to System.Xml.dll (e.g.
System.Configuration.ConfigXmlDocument extended from XmlDocument), while
System.Xml.dll vice versa (e.g. XmlUrlResolver.ResolveUri takes System.Uri).
Since they are in public method signatures, so at least we cannot get rid
of these mutual references.
However, for those who really want to build System.Xml.dll without System.dll,
I created <a href="http://primates.ximian.com/~atsushi/System_DummyClasses.cs">dummy classes in System.dll</a>. To build System.Xml.dll in such way, remove
<code>/r:System.dll</code> from Makefile, and add this source to
System.Xml.dll.sources. Note that this is at the point of Mono 0.30 release.
Also note that you still need System.dll to run mcs.
+36 -51
View File
@@ -1,57 +1,42 @@
HOWTO bundle assemblies inside the mono runtime.
Paolo Molaro ([email protected])
HOWTO bundle assemblies inside the mono runtime.
* Intent
Bundling assemblies inside the mono runtime may be useful for a number
of reasons:
* creating a standalone complete runtime that can be more easily
distributed
* having an application run against a known set of assemblies
that has been tested
Bundling assemblies inside the mono runtime may be useful for a number
of reasons:
Of course, there are drawbacks, too: if there has been fixes to the assemblies,
replacing them means recompiling the runtime as well and if there are other mono apps,
unless they use the same mono binary, there will be less opportunities for
the operating system to optimize memory usage. So use this feature only
when really needed.
* creating a standalone complete runtime that can be more easily
distributed
* having an application run against a known set of assemblies
that has been tested
Of course, there are drawbacks, too: if there has been fixes
to the assemblies, replacing them means recompiling the
runtime as well and if there are other mono apps, unless they
use the same mono binary, there will be less opportunities for
the operating system to optimize memory usage. So use this
feature only when really needed.
* Creating the Bundle
To bundle a set of assemblies, you need to create a file that
lists the assembly names and the relative files. Empty lines
and lines starting with # are ignored:
== cut cut ==
# Sample bundle template
mscorlib: /path/to/mscorlib/assembly.dll
myapp: /path/to/myapp.exe
== cut cut ==
Next you need to build the mono runtime using a special configure option:
./configure --with-bundle=/path/to/bundle/template
The path to the template should be an absolute path.
The script metadata/make-bundle.pl will take the specifie
assemblies and embed them inside the runtime where the loading
routines can find them before searching for them on disk.
* Open Issues
There are still two issues to solve:
* config files: sometimes they are needed but they are
not yet bundled inside the library ()
* building with the included libgc makes it not
possible to build a mono binary statically linked to
libmono: this needs to be fixed to make bundles
really useful.
To bundle a set of assemblies, you need to create a file that lists the assembly
names and the relative files. Empty lines and lines starting with # are ignored:
== cut cut ==
# Sample bundle template
mscorlib: /path/to/mscorlib/assembly.dll
myapp: /path/to/myapp.exe
== cut cut ==
Next you need to build the mono runtime using a special configure option:
./configure --with-bundle=/path/to/bundle/template
The path to the template should be an absolute path.
The script metadata/make-bundle.pl will take the specifie assemblies and embed
them inside the runtime where the loading routines can find them before
searching for them on disk.
There are still two issues to solve:
* config files: sometimes they are needed but they are not yet bundled
inside the library ()
* building with the included libgc makes it not possible to build a mono
binary statically linked to libmono: this needs to be fixed to make bundles
really useful
+5 -34
View File
@@ -1,13 +1,11 @@
Embedding the Mono runtime, preliminary version
Miguel de Icaza ([email protected]),
Paolo Molaro ([email protected])
Miguel de Icaza, Paolo Molaro.
This document describes how to embed the Mono runtime in your
application, and how to invoke CIL methods from C, and how to
invoke C code from CIL. Both the JIT and interpreter can be
embedded in very similar ways so most of what is described
here can be used in either case.
invoke C code from CIL.
* Embedding the runtime.
@@ -29,12 +27,6 @@
pkg-config --cflags --libs mono
is used to get the flags for the JIT runtime and
pkg-config --cflags --libs mint
for the interpreted runtime.
Like this:
gcc sample.c `pkg-config --cflags --libs mono`
@@ -47,22 +39,12 @@
** Initializing the Mono runtime
To initialize the JIT runtime, call mono_jit_init, like this:
#include <mono/mini/jit.h>
To initialize the runtime, call mono_jit_init, like this:
MonoDomain *domain;
domain = mono_jit_init ("domain-name");
For the interpreted runtime use mono_interp_init instead:
#include <mono/interpreter/embed.h>
MonoDomain *domain;
domain = mono_interp_init ("domain-name");
That will return a MonoDomain where your code will be
executed. You can create multiple domains. Each domain is
isolated from the other domains and code in one domain will
@@ -88,10 +70,6 @@
retval = mono_jit_exec (domain, assembly, argc - 1, argv + 1);
or when using the interpreter use:
retval = mono_interp_exec (domain, assembly, argc - 1, argv + 1);
If you want to invoke a different method, look at the
`Invoking Methods in the CIL universe' section later on.
@@ -102,10 +80,6 @@
mono_jit_cleanup (domain);
Or in the case of the interpreted runtime use:
mono_interp_cleanup (domain);
** Applications that use threads.
The Boehm GC system needs to catch your calls to the pthreads
@@ -209,9 +183,6 @@
methods, a MonoObject* for object instances and a pointer to
the value type for value types.
These functions can be used in both the JIT and the interpreted
environments.
The params array contains the arguments to the method with the
same convention: MonoObject* pointers for object instances and
pointers to the value type otherwise. The _invoke_array
@@ -265,7 +236,7 @@
* Samples
See the sample programs in mono/sample/embed for examples of
See the sample programs inmono/sample/embed for examples of
embedding the Mono runtime in your application.
+2 -3
View File
@@ -1,6 +1,5 @@
Exception Implementation in the Mono Runtime
Dietmar Maurer ([email protected])
(C) 2001 Ximian, Inc.
Author: Dietmar Maurer ([email protected])
(C) 2001 Ximian, Inc.
Exception implementation (jit):
===============================
+32 -57
View File
@@ -1,19 +1,7 @@
Internal Call Topics
* Introduction
The Common Language Infrastructure allows for methods to be
implemented in unmanaged code. Unlike the Platform Invocation
services which provide marshalling and unmarshalling of data
from managed to unmanaged and viceversa the Internal calls do
not perform any kind of marshalling.
* Basic Type mapping
The following lists how the C# types are exposed to the C API.
* How to map C# types for use in the C implementation of internal calls
C# type C type
-----------------------------
char gunichar2
bool MonoBoolean
sbyte signed char
@@ -28,57 +16,44 @@
object MonoObject*
string MonoString*
* Pointers
For ref and out paramaters you'll use the corresponding pointer type.
Arrays of any type must be described with a MonoArray* and the elements
must be accessed with the mono_array_* macros.
Any other type that has a matching C structure representation, should use
a pointer to the struct instead of a generic MonoObject pointer.
For ref and out paramaters you'll use the corresponding
pointer type.
Instance methods that are internal calls will receive as first argument
the instance object, so you must account for it in the C method signature:
So if you have a C# type listed as "ref int", you should use
"int *" in your implementation.
[MethodImplAttribute(MethodImplOptions.InternalCall)]
public extern override int GetHashCode ();
* Arrays
becaomes:
Arrays of any type must be described with a MonoArray* and the
elements must be accessed with the mono_array_* macros.
gint32 ves_icall_System_String_GetHashCode (MonoString *this);
* Other Structures
Any other type that has a matching C structure representation,
should use a pointer to the struct instead of a generic
MonoObject pointer.
* Instance Methods.
Instance methods that are internal calls will receive as first argument
the instance object, so you must account for it in the C method signature:
[MethodImplAttribute(MethodImplOptions.InternalCall)]
public extern override int GetHashCode ();
becomes:
gint32 ves_icall_System_String_GetHashCode (MonoString *this);
* How to hook internal calls with the runtime
Once you require an internal call in corlib, you need to
create a C implementation for it and register it in a static
table in metadata/icall.c. Add an entry in the table like:
"System.String::GetHashCode", ves_icall_System_String_GetHashCode,
Note that you need to include the full namespace.name of the
class. If there are overloaded methods, you need also to
specify the signature of _all_ of them:
[MethodImplAttribute(MethodImplOptions.InternalCall)]
public extern override void DoSomething ();
[MethodImplAttribute(MethodImplOptions.InternalCall)]
public extern override void DoSomething (bool useful);
should be mapped with:
"Namespace.ClassName::DoSomething()", ves_icall_Namespace_ClassName_DoSomething,
"Namespace.ClassName::DoSomething(bool)", ves_icall_Namespace_ClassName_DoSomething_bool,
Once you require an internal call in corlib, you need to create a C
implementation for it and register it in a static table in metadata/icall.c.
Add an entry in the table like:
"System.String::GetHashCode", ves_icall_System_String_GetHashCode,
Note that you need to include the full namespace.name of the class.
If there are overloaded methods, you need also to specify the signature
of _all_ of them:
[MethodImplAttribute(MethodImplOptions.InternalCall)]
public extern override void DoSomething ();
[MethodImplAttribute(MethodImplOptions.InternalCall)]
public extern override void DoSomething (bool useful);
should be mapped with:
"Namespace.ClassName::DoSomething()", ves_icall_Namespace_ClassName_DoSomething,
"Namespace.ClassName::DoSomething(bool)", ves_icall_Namespace_ClassName_DoSomething_bool,
-30
View File
@@ -1,30 +0,0 @@
Mono Intermediate Representation Documentation
Operation: OP_LOCALLOC
inst_left:
The value
ins->inst_left = *sp;
ins->cil_code = ip;
This is the equivalent of alloca() in a C implementation: it
allocates a bunch of bytes on the stack dynamically. Local
variables are allocated statically in the stack instead.
It is implemented by moving the stack pointer according to the
platform ABI: you may need to keep a specific frame register
to address local variables when LOCALLOC is used (the PPC code
does this, for example: ifyou're doing the s390 port I suggest
starting from that)
Operation: OP_CALL_HANDLER.
cil_code:
Points to the CIL where the LEAVE or LEAVE_S
instruction was found.
inst_target_bb:
The target basic block for this invocation.
This instruction must call the target basic block.
+297 -372
View File
@@ -1,424 +1,349 @@
Mono JIT porting guide.
Paolo Molaro ([email protected])
Mono JIT porting guide.
Paolo Molaro ([email protected])
* Introduction
This documents describes the process of porting the mono JIT
to a new CPU architecture. The new mono JIT has been designed
to make porting easier though at the same time enable the port
to take full advantage from the new architecture features and
instructions. Knowledge of the mini architecture (described in
the mini-doc.txt file) is a requirement for understanding this
guide, as well as an earlier document about porting the mono
interpreter (available on the web site).
There are six main areas that a port needs to implement to
have a fully-functional JIT for a given architecture:
1) instruction selection
2) native code emission
3) call conventions and register allocation
4) method trampolines
5) exception handling
6) minor helper methods
To take advantage of some not-so-common processor features
(for example conditional execution of instructions as may be
found on ARM or ia64), it may be needed to develop an
high-level optimization, but doing so is not a requirement for
getting the JIT to work.
We'll see in more details each of the steps required, note,
though, that a new port may just as well start from a
cut&paste of an existing port to a similar architecture (for
example from x86 to amd64, or from powerpc to sparc).
The architecture specific code is split from the rest of the
JIT, for example the x86 specific code and data is all
included in the following files in the distribution:
mini-x86.h mini-x86.c
inssel-x86.brg
cpu-pentium.md
tramp-x86.c
exceptions-x86.c
I suggest a similar split for other architectures as well.
Note that this document is still incomplete: some sections are
only sketched and some are missing, but the important info to
get a port going is already described.
This documents describes the process of porting the mono JIT
to a new CPU architecture. The new mono JIT has been designed
to make porting easier though at the same time enable the port
to take full advantage from the new architecture features and
instructions. Knowledge of the mini architecture (described in the
mini-doc.txt file) is a requirement for understanding this guide,
as well as an earlier document about porting the mono interpreter
(available on the web site).
There are six main areas that a port needs to implement to
have a fully-functional JIT for a given architecture:
1) instruction selection
2) native code emission
3) call conventions and register allocation
4) method trampolines
5) exception handling
6) minor helper methods
To take advantage of some not-so-common processor features (for example
conditional execution of instructions as may be found on ARM or ia64), it may
be needed to develop an high-level optimization, but doing so is not a
requirement for getting the JIT to work.
We'll see in more details each of the steps required, note, though,
that a new port may just as well start from a cut&paste of an existing
port to a similar architecture (for example from x86 to amd64, or from
powerpc to sparc).
The architecture specific code is split from the rest of the JIT,
for example the x86 specific code and data is all included in the
following files in the distribution:
mini-x86.h mini-x86.c
inssel-x86.brg
cpu-pentium.md
tramp-x86.c
exceptions-x86.c
I suggest a similar split for other architectures as well.
Note that this document is still incomplete: some sections are only
sketched and some are missing, but the important info to get a port
going is already described.
* Architecture-specific instructions and instruction selection.
The JIT already provides a set of instructions that can be
easily mapped to a great variety of different processor
instructions. Sometimes it may be necessary or advisable to
add a new instruction that represent more closely an
instruction in the architecture. Note that a mini instruction
can be used to represent also a short sequence of CPU
low-level instructions, but note that each instruction
represents the minimum amount of code the instruction
scheduler will handle (i.e., the scheduler won't schedule the
instructions that compose the low-level sequence as individual
instructions, but just the whole sequence, as an indivisible
block).
The JIT already provides a set of instructions that can be easily
mapped to a great variety of different processor instructions.
Sometimes it may be necessary or advisable to add a new instruction
that represent more closely an instruction in the architecture.
Note that a mini instruction can be used to represent also a short
sequence of CPU low-level instructions, but note that each
instruction represents the minimum amount of code the instruction
scheduler will handle (i.e., the scheduler won't schedule the instructions
that compose the low-level sequence as individual instructions, but just
the whole sequence, as an indivisible block).
New instructions are created by adding a line in the mini-ops.h file,
assigning an opcode and a name. To specify the input and output for
the instruction, there are two different places, depending on the context
in which the instruction gets used.
If the instruction is used in the tree representation, the input and output
types are defined by the BURG rules in the *.brg files (the usual
non-terminals are 'reg' to represent a normal register, 'lreg' to
represent a register or two that hold a 64 bit value, freg for a
floating point register).
If an instruction is used as a low-level CPU instruction, the info
is specified in a machine description file. The description file is
processed by the genmdesc program to provide a data structure that
can be easily used from C code to query the needed info about the
instruction.
As an example, let's consider the add instruction for both x86 and ppc:
New instructions are created by adding a line in the
mini-ops.h file, assigning an opcode and a name. To specify
the input and output for the instruction, there are two
different places, depending on the context in which the
instruction gets used.
x86 version:
add: dest:i src1:i src2:i len:2 clob:1
ppc version:
add: dest:i src1:i src2:i len:4
If the instruction is used in the tree representation, the
input and output types are defined by the BURG rules in the
*.brg files (the usual non-terminals are 'reg' to represent a
normal register, 'lreg' to represent a register or two that
hold a 64 bit value, freg for a floating point register).
Note that the instruction takes two input integer registers on both CPU,
but on x86 the first source register is clobbered (clob:1) and the length
in bytes of the instruction differs.
Note that integer adds and floating point adds use different opcodes, unlike
the IL language (64 bit add is done with two instructions on 32 bit architectures,
using a add that sets the carry and an add with carry).
A specific CPU port may assign any meaning to the clob field for an instruction
since the value will be processed in an arch-specific file anyway.
See the top of the existing cpu-pentium.md file for more info on other fields:
the info may or may not be applicable to a different CPU, in this latter case
the info can be ignored.
The code in mini.c together with the BURG rules in inssel.brg, inssel-float.brg
and inssel-long32.brg provides general purpose mappings from the tree representation
to a set of instructions that should be easily implemented in any architecture.
To allow for additional arch-specific functionality, an arch-specific BURG file
can be used: in this file arch-specific instructions can be selected that provide
better performance than the general instructions or that provide functionality
that is needed by the JIT but that cannot be expressed in a general enough way.
As an example, x86 has the special instruction "push" to make it easier to
implement the default call convention (passing arguments on the stack): almost
all the other architectures don't have such an instruction (and don't need it anyway),
so we added a special rule in the inssel-x86.brg file for it.
If an instruction is used as a low-level CPU instruction, the
info is specified in a machine description file. The
description file is processed by the genmdesc program to
provide a data structure that can be easily used from C code
to query the needed info about the instruction.
So, one of the first things needed in a port is to write a cpu-$(arch).md machine
description file and fill it with the needed info. As a start, only a few
instructions can be specified, like the ones required to do simple integer
operations. The default rules of the instruction selector will emit the common
instructions and so we're ready to go for the next step in porting the JIT.
As an example, let's consider the add instruction for both x86
and ppc:
x86 version:
add: dest:i src1:i src2:i len:2 clob:1
ppc version:
add: dest:i src1:i src2:i len:4
Note that the instruction takes two input integer registers on
both CPU, but on x86 the first source register is clobbered
(clob:1) and the length in bytes of the instruction differs.
Note that integer adds and floating point adds use different
opcodes, unlike the IL language (64 bit add is done with two
instructions on 32 bit architectures, using a add that sets
the carry and an add with carry).
A specific CPU port may assign any meaning to the clob field
for an instruction since the value will be processed in an
arch-specific file anyway.
See the top of the existing cpu-pentium.md file for more info
on other fields: the info may or may not be applicable to a
different CPU, in this latter case the info can be ignored.
The code in mini.c together with the BURG rules in inssel.brg,
inssel-float.brg and inssel-long32.brg provides general
purpose mappings from the tree representation to a set of
instructions that should be easily implemented in any
architecture. To allow for additional arch-specific
functionality, an arch-specific BURG file can be used: in this
file arch-specific instructions can be selected that provide
better performance than the general instructions or that
provide functionality that is needed by the JIT but that
cannot be expressed in a general enough way.
As an example, x86 has the special instruction "push" to make
it easier to implement the default call convention (passing
arguments on the stack): almost all the other architectures
don't have such an instruction (and don't need it anyway), so
we added a special rule in the inssel-x86.brg file for it.
So, one of the first things needed in a port is to write a
cpu-$(arch).md machine description file and fill it with the
needed info. As a start, only a few instructions can be
specified, like the ones required to do simple integer
operations. The default rules of the instruction selector will
emit the common instructions and so we're ready to go for the
next step in porting the JIT.
*) Native code emission
Since the first step in porting mono to a new CPU is to port
the interpreter, there should be already a file that allows
the emission of binary native code in a buffer for the
architecture. This file should be placed in the
Since the first step in porting mono to a new CPU is to port the interpreter,
there should be already a file that allows the emission of binary native code
in a buffer for the architecture. This file should be placed in the
mono/arch/$(arch)/
directory.
mono/arch/$(arch)/
The bulk of the code emission happens in the mini-$(arch).c file, in a function
called mono_arch_output_basic_block (). This function takes a basic block, walks the
list of instructions in the block and emits the binary code for each.
Optionally a peephole optimization pass is done on the basic block, but this can be
left for later, when the port actually works.
This function is very simple, there is just a big switch on the instruction opcode
and in the corresponding case the functions or macros to emit the binary native code
are used. Note that in this function the lengths of the instructions are used to
determine if the buffer for the code needs enlarging.
directory.
To complete the code emission for a method, a few other functions need
implementing as well:
The bulk of the code emission happens in the mini-$(arch).c
file, in a function called mono_arch_output_basic_block
(). This function takes a basic block, walks the list of
instructions in the block and emits the binary code for each.
Optionally a peephole optimization pass is done on the basic
block, but this can be left for later, when the port actually
works.
mono_arch_emit_prolog ()
mono_arch_emit_epilog ()
mono_arch_patch_code ()
This function is very simple, there is just a big switch on
the instruction opcode and in the corresponding case the
functions or macros to emit the binary native code are
used. Note that in this function the lengths of the
instructions are used to determine if the buffer for the code
needs enlarging.
To complete the code emission for a method, a few other
functions need implementing as well:
mono_arch_emit_prolog ()
mono_arch_emit_epilog ()
mono_arch_patch_code ()
mono_arch_emit_prolog () will emit the code to setup the stack
frame for a method, optionally call the callbacks used in
profiling and tracing, and move the arguments to their home
location (in a caller-save register if the variable was
allocated to one, or in a stack location if the argument was
passed in a volatile register and wasn't allocated a
non-volatile one). caller-save registers used by the function
are saved in the prolog as well.
mono_arch_emit_epilog () will emit the code needed to return
from the function, optionally calling the profiling or tracing
callbacks. At this point the basic blocks or the code that was
moved out of the normal flow for the function can be emitted
as well (this is usually done to provide better info for the
static branch predictor). In the epilog, caller-save
registers are restored if they were used.
mono_arch_emit_prolog () will emit the code to setup the stack frame for a method,
optionally call the callbacks used in profiling and tracing, and move the
arguments to their home location (in a caller-save register if the variable was
allocated to one, or in a stack location if the argument was passed in a volatile
register and wasn't allocated a non-volatile one). caller-save registers used by the
function are saved in the prolog as well.
Note that, to help exception handling and stack unwinding,
when there is a transition from managed to unmanaged code,
some special processing needs to be done (basically, saving
all the registers and setting up the links in the Last Managed
Frame structure).
When the epilog has been emitted, the upper level code
arranges for the buffer of memory that contains the native
code to be copied in an area of executable memory and at this
point, instructions that use relative addressing need to be
patched to have the right offsets: this work is done by
mono_arch_patch_code ().
mono_arch_emit_epilog () will emit the code needed to return from the function,
optionally calling the profiling or tracing callbacks. At this point the basic blocks
or the code that was moved out of the normal flow for the function can be emitted
as well (this is usually done to provide better info for the static branch predictor).
In the epilog, caller-save registers are restored if they were used.
Note that, to help exception handling and stack unwinding, when there is a transition
from managed to unmanaged code, some special processing needs to be done (basically,
saving all the registers and setting up the links in the Last Managed Frame
structure).
When the epilog has been emitted, the upper level code arranges for the buffer of
memory that contains the native code to be copied in an area of executable memory
and at this point, instructions that use relative addressing need to be patched
to have the right offsets: this work is done by mono_arch_patch_code ().
* Call conventions and register allocation
To account for the differences in the call conventions, a few functions need to
be implemented.
mono_arch_allocate_vars () assigns to both arguments and local
variables the offset relative to the frame register where they
are stored, dead variables are simply discarded. The total
amount of stack needed is calculated.
mono_arch_call_opcode () is the function that more closely
deals with the call convention on a given system. For each
argument to a function call, an instruction is created that
actually puts the argument where needed, be it the stack or a
specific register. This function can also re-arrange th order
of evaluation when multiple arguments are involved if needed
(like, on x86 arguments are pushed on the stack in reverse
order). The function needs to carefully take into accounts
platform specific issues, like how structures are returned as
well as the differences in size and/or alignment of managed
and corresponding unmanaged structures.
The other chunk of code that needs to deal with the call
convention and other specifics of a CPU, is the local register
allocator, implemented in a function named
mono_arch_local_regalloc (). The local allocator deals with a
basic block at a time and basically just allocates registers
for temporary values during expression evaluation, spilling
and unspilling as necessary.
To account for the differences in the call conventions, a few functions need to
be implemented.
The local allocator needs to take into account clobbering
information, both during simple instructions and during
function calls and it needs to deal with other
architecture-specific weirdnesses, like instructions that take
inputs only in specific registers or output only is some.
mono_arch_allocate_vars () assigns to both arguments and local variables
the offset relative to the frame register where they are stored, dead
variables are simply discarded. The total amount of stack needed is calculated.
mono_arch_call_opcode () is the function that more closely deals with the call
convention on a given system. For each argument to a function call, an instruction
is created that actually puts the argument where needed, be it the stack or a
specific register. This function can also re-arrange th order of evaluation
when multiple arguments are involved if needed (like, on x86 arguments are pushed
on the stack in reverse order). The function needs to carefully take into accounts
platform specific issues, like how structures are returned as well as the
differences in size and/or alignment of managed and corresponding unmanaged
structures.
The other chunk of code that needs to deal with the call convention and other
specifics of a CPU, is the local register allocator, implemented in a function
named mono_arch_local_regalloc (). The local allocator deals with a basic block
at a time and basically just allocates registers for temporary
values during expression evaluation, spilling and unspilling as necessary.
The local allocator needs to take into account clobbering information, both
during simple instructions and during function calls and it needs to deal
with other architecture-specific weirdnesses, like instructions that take
inputs only in specific registers or output only is some.
Some effort will be put later in moving most of the local register allocator to
a common file so that the code can be shared more for similar, risc-like CPUs.
The register allocator does a first pass on the instructions in a block, collecting
liveness information and in a backward pass on the same list performs the
actual register allocation, inserting the instructions needed to spill values,
if necessary.
When this part of code is implemented, some testing can be done with the generated
code for the new architecture. Most helpful is the use of the --regression
command line switch to run the regression tests (basic.cs, for example).
Note that the JIT will try to initialize the runtime, but it may not be able yet to
compile and execute complex code: commenting most of the code in the mini_init()
function in mini.c is needed to let the JIT just compile the regression tests.
Also, using multiple -v switches on the command line makes the JIT dump an
increasing amount of information during compilation.
Some effort will be put later in moving most of the local
register allocator to a common file so that the code can be
shared more for similar, risc-like CPUs. The register
allocator does a first pass on the instructions in a block,
collecting liveness information and in a backward pass on the
same list performs the actual register allocation, inserting
the instructions needed to spill values, if necessary.
When this part of code is implemented, some testing can be
done with the generated code for the new architecture. Most
helpful is the use of the --regression command line switch to
run the regression tests (basic.cs, for example).
Note that the JIT will try to initialize the runtime, but it
may not be able yet to compile and execute complex code:
commenting most of the code in the mini_init() function in
mini.c is needed to let the JIT just compile the regression
tests. Also, using multiple -v switches on the command line
makes the JIT dump an increasing amount of information during
compilation.
* Method trampolines
To get better startup performance, the JIT actually compiles a
method only when needed. To achieve this, when a call to a
method is compiled, we actually emit a call to a magic
trampoline. The magic trampoline is a function written in
assembly that invokes the compiler to compile the given method
and jumps to the newly compiled code, ensuring the arguments
it received are passed correctly to the actual method.
To get better startup performance, the JIT actually compiles a method only when
needed. To achieve this, when a call to a method is compiled, we actually emit a
call to a magic trampoline. The magic trampoline is a function written in assembly
that invokes the compiler to compile the given method and jumps to the newly compiled
code, ensuring the arguments it received are passed correctly to the actual method.
Before jumping to the new code, though, the magic trampoline takes care of patching
the call site so that next time the call will go directly to the method instead of the
trampoline. How does this all work?
mono_arch_create_jit_trampoline () creates a small function that just
preserves the arguments passed to it and adds an additional argument (the method
to compile) before calling the generic trampoline. This small function is called
the specific trampoline, because it is method-specific (the method to compile
is hard-code in the instruction stream).
The generic trampoline saves all the arguments that could get clobbered
and calls a C function that will do two things:
Before jumping to the new code, though, the magic trampoline
takes care of patching the call site so that next time the
call will go directly to the method instead of the
trampoline. How does this all work?
*) actually call the JIT to compile the method
*) identify the calling code so that it can be patched to call directly
the actual method
mono_arch_create_jit_trampoline () creates a small function
that just preserves the arguments passed to it and adds an
additional argument (the method to compile) before calling the
generic trampoline. This small function is called the specific
trampoline, because it is method-specific (the method to
compile is hard-code in the instruction stream).
If the 'this' argument to a method is a boxed valuetype that is passed to
a method that expects just a pointer to the data, an additional unboxing
trampoline will need to be inserted as well.
The generic trampoline saves all the arguments that could get
clobbered and calls a C function that will do two things:
*) actually call the JIT to compile the method
*) identify the calling code so that it can be patched to call directly
the actual method
If the 'this' argument to a method is a boxed valuetype that
is passed to a method that expects just a pointer to the data,
an additional unboxing trampoline will need to be inserted as
well.
* Exception handling
Exception handling is likely the most difficult part of the
port, as it needs to deal with unwinding (both managed and
unmanaged code) and calling catch and filter blocks. It also
needs to deal with signals, because mono takes advantage of
the MMU in the CPU and of the operation system to handle
dereferences of the NULL pointer. Some of the function needed
to implement the mechanisms are:
mono_arch_get_throw_exception () returns a function that takes
an exception object and invokes an arch-specific function that
will enter the exception processing. To do so, all the
relevant registers need to be saved and passed on.
mono_arch_handle_exception () this function takes the
exception thrown and a context that describes the state of the
CPU at the time the exception was thrown. The function needs
to implement the exception handling mechanism, so it makes a
search for an handler for the exception and if none is found,
it follows the unhandled exception path (that can print a
trace and exit or just abort the current thread). The
difficulty here is to unwind the stack correctly, by restoring
the register state at each call site in the call chain,
calling finally, filters and handler blocks while doing so.
As part of exception handling a couple of internal calls need
to be implemented as well.
Exception handling is likely the most difficult part of the port, as it needs
to deal with unwinding (both managed and unmanaged code) and calling
catch and filter blocks. It also needs to deal with signals, because mono
takes advantage of the MMU in the CPU and of the operation system to
handle dereferences of the NULL pointer. Some of the function needed
to implement the mechanisms are:
ves_icall_get_frame_info () returns info about a specific
frame.
mono_arch_get_throw_exception () returns a function that takes an exception object
and invokes an arch-specific function that will enter the exception processing.
To do so, all the relevant registers need to be saved and passed on.
mono_jit_walk_stack () walks the stack and calls a callback with info for
each frame found.
mono_arch_handle_exception () this function takes the exception thrown and
a context that describes the state of the CPU at the time the exception was
thrown. The function needs to implement the exception handling mechanism,
so it makes a search for an handler for the exception and if none is found,
it follows the unhandled exception path (that can print a trace and exit or
just abort the current thread). The difficulty here is to unwind the stack
correctly, by restoring the register state at each call site in the call chain,
calling finally, filters and handler blocks while doing so.
As part of exception handling a couple of internal calls need to be implemented
as well.
ves_icall_get_frame_info () returns info about a specific frame.
mono_jit_walk_stack () walks the stack and calls a callback with info for
each frame found.
ves_icall_get_trace () return an array of StackFrame objects.
ves_icall_get_trace () return an array of StackFrame objects.
** Code generation for filter/finally handlers
Filter and finally handlers are called from 2 different locations:
1.) from within the method containing the exception clauses
2.) from the stack unwinding code
To make this possible we implement them like subroutines,
ending with a "return" statement. The subroutine does not save
the base pointer, because we need access to the local
variables of the enclosing method. Its is possible that
instructions inside those handlers modify the stack pointer,
thus we save the stack pointer at the start of the handler,
and restore it at the end. We have to use a "call" instruction
to execute such finally handlers.
The MIR code for filter and finally handlers looks like:
OP_START_HANDLER
...
OP_END_FINALLY | OP_ENDFILTER(reg)
OP_START_HANDLER: should save the stack pointer somewhere
OP_END_FINALLY: restores the stack pointers and returns.
OP_ENDFILTER (reg): restores the stack pointers and returns the value in "reg".
Filter and finally handlers are called from 2 different locations:
1.) from within the method containing the exception clauses
2.) from the stack unwinding code
To make this possible we implement them like subroutines, ending with a
"return" statement. The subroutine does not save the base pointer, because we
need access to the local variables of the enclosing method. Its is possible
that instructions inside those handlers modify the stack pointer, thus we save
the stack pointer at the start of the handler, and restore it at the end. We
have to use a "call" instruction to execute such finally handlers.
The MIR code for filter and finally handlers looks like:
OP_START_HANDLER
...
OP_END_FINALLY | OP_ENDFILTER(reg)
OP_START_HANDLER: should save the stack pointer somewhere
OP_END_FINALLY: restores the stack pointers and returns.
OP_ENDFILTER (reg): restores the stack pointers and returns the value in "reg".
** Calling finally/filter handlers
There is a special opcode to call those handler, its called
OP_CALL_HANDLER. It simple emits a call instruction.
Its a bit more complex to call handler from outside (in the
stack unwinding code), because we have to restore the whole
context of the method first. After that we simply emit a call
instruction to invoke the handler. Its usually possible to use
the same code to call filter and finally handlers (see
arch_get_call_filter).
There is a special opcode to call those handler, its called OP_CALL_HANDLER. It
simple emits a call instruction.
Its a bit more complex to call handler from outside (in the stack unwinding
code), because we have to restore the whole context of the method first. After that
we simply emit a call instruction to invoke the handler. Its usually
possible to use the same code to call filter and finally handlers (see
arch_get_call_filter).
** Calling catch handlers
Catch handlers are always called from the stack unwinding
code. Unlike finally clauses or filters, catch handler never
return. Instead we simply restore the whole context, and
restart execution at the catch handler.
Catch handlers are always called from the stack unwinding code. Unlike finally clauses
or filters, catch handler never return. Instead we simply restore the whole
context, and restart execution at the catch handler.
** Passing Exception objects to catch handlers and filters.
We use a local variable to store exception objects. The stack
unwinding code must store the exception object into this
variable before calling catch handler or filter.
We use a local variable to store exception objects. The stack unwinding code
must store the exception object into this variable before calling catch handler
or filter.
* Minor helper methods
A few minor helper methods are referenced from the arch-independent code.
Some of them are:
*) mono_arch_cpu_optimizations ()
This function returns a mask of optimizations that
should be enabled for the current CPU and a mask of
optimizations that should be excluded, instead.
*) mono_arch_regname ()
Returns the name for a numeric register.
*) mono_arch_get_allocatable_int_vars ()
Returns a list of variables that can be allocated to
the integer registers in the current architecture.
*) mono_arch_get_global_int_regs ()
Returns a list of caller-save registers that can be
used to allocate variables in the current method.
*) mono_arch_instrument_mem_needs ()
*) mono_arch_instrument_prolog ()
*) mono_arch_instrument_epilog ()
Functions needed to implement the profiling interface.
A few minor helper methods are referenced from the arch-independent code.
Some of them are:
*) mono_arch_cpu_optimizations ()
This function returns a mask of optimizations that should be enabled for the
current CPU and a mask of optimizations that should be excluded, instead.
*) mono_arch_regname ()
Returns the name for a numeric register.
*) mono_arch_get_allocatable_int_vars ()
Returns a list of variables that can be allocated to the integer registers
in the current architecture.
*) mono_arch_get_global_int_regs ()
Returns a list of caller-save registers that can be used to allocate variables
in the current method.
*) mono_arch_instrument_mem_needs ()
*) mono_arch_instrument_prolog ()
*) mono_arch_instrument_epilog ()
Functions needed to implement the profiling interface.
* Writing regression tests
Regression tests for the JIT should be written for any bug
found in the JIT in one of the *.cs files in the mini
directory. Eventually all the operations of the JIT should be
tested (including the ones that get selected only when some
specific optimization is enabled).
Regression tests for the JIT should be written for any bug found in the JIT
in one of the *.cs files in the mini directory. Eventually all the operations
of the JIT should be tested (including the ones that get selected only when
some specific optimization is enabled).
* Platform specific optimizations
An example of a platform-specific optimization is the peephole
optimization: we look at a small window of code at a time and
we replace one or more instructions with others that perform
better for the given architecture or CPU.
An example of a platform-specific optimization is the peephole optimization:
we look at a small window of code at a time and we replace one or more
instructions with others that perform better for the given architecture or CPU.
+1 -1
View File
@@ -1,4 +1,4 @@
man_MANS = mcs.1 mono.1 monostyle.1 mono-config.5 sqlsharp.1 oldmono.1 ilasm.1 \
cert2spc.1 cilc.1 genxs.1 wsdl.1 disco.1 soapsuds.1
cert2spc.1 cilc.1 genxs.1
EXTRA_DIST = $(man_MANS)
-68
View File
@@ -1,68 +0,0 @@
.\"
.\" disco manual page.
.\" (C) 2003 Novell, Inc.
.\" Author:
.\" Lluis Sanchez Gual ([email protected])
.\"
.TH disco 1
.SH NAME
disco \- Mono's Web Service Discovery Tool
.SH SYNOPSIS
.PP
.B disco
[options] url
.SH DESCRIPTION
.I disco
is a tool for discovering web services and for retireving the documents that
describe those services.
.PP
.I url
is the location of a DISCO document, which includes a list of WSDL documents,
XML schemas and references to other DISCO documents.
.PP
.I disco
downloads the DISCO document and all referenced documents (unless
the
.I "-nosave"
option is specified), and saves them to disk.
.SH OPTIONS
The following options are available:
.TP
.I "-nologo"
Supress the startup logo.
.TP
.I "-nosave"
Do not save the discovered documents to disk. The default is to save the documents.
.TP
.I "-o:directory", "-out:directory"
The directory where to save the discovered documents.
By default, documents are saved in the current directory.
.TP
.I "-u:username", "-user:username"
The user name to use when connecting to the server.
.TP
.I "-p:password", "-password:password"
The password to use when connecting to the server.
.TP
.I "-d:domain", "-domain:domain"
The domain to use when connecting to the server.
.TP
.I "-proxy:url"
The url of the proxy server to use for http requests.
.TP
.I "-proxyusername:username"
The user name to use when connecting to the proxy.
.TP
.I "-proxypassword:password"
The password to use when connecting to the proxy.
.TP
.I "-proxydomain:domain"
The domain to use when connecting to the proxy.
.SH AUTHORS
Lluis Sanchez Gual ([email protected])
.PP
.SH LICENSE
disco is released under the terms of the GNU GPL.
.PP
.SH SEE ALSO
wsdl(1), soapsuds(1), mono(1), mcs(1)
-3
View File
@@ -15,7 +15,4 @@
<manpage name="chktrust" page="chktrust.1" />
<manpage name="signcode" page="signcode.1" />
<manpage name="sn" page="sn.1" />
<manpage name="wsdl" page="wsdl.1" />
<manpage name="disco" page="disco.1" />
<manpage name="soapsuds" page="soapsuds.1" />
</manpages>
+18 -30
View File
@@ -36,9 +36,6 @@ Executables are not bound to a specific CPU or operating system.
.I \-\-about
Displays information about the Mono C# compiler
.TP
.I \-\-addmodule:MODULE1[,MODULE2]
Includes the specified modules in the resulting assembly.
.TP
.I -checked, -checked+
Sets the default compilation mode to `checked'. This makes all
the math operations checked (the default is unchecked).
@@ -117,15 +114,6 @@ name will be the file name.
Links to the specified RESOURCE. The optional ID can be used to give
a name to the linked resource.
.TP
.I -r:ASSEMBLY1[,ASSEMBLY2], \-r ASSEMBLY1[,ASSEMBLY2]
Reference the named assemblies. Use this to use classes from the named
assembly in your program. The assembly will be loaded from either the
system directory where all the assemblies live, or from the path
explicitly given with the -L option.
.PP
You can also use a semicolon to separate the assemblies instead of a
comma.
.TP
.I \-recurse:PATTERN, --recurse PATTERN
Does recursive compilation using the specified pattern. In Unix the
shell will perform globbing, so you migth want to use it like this:
@@ -135,9 +123,8 @@ shell will perform globbing, so you migth want to use it like this:
.fi
.TP
.I \-target:KIND, \-t:KIND
Used to specify the desired target. The possible values are: exe
(plain executable), winexe (Windows.Forms executable), library
(component libraries) and module (partial library).
Used to specify the desired target. The possible values are: exe,
winexe, library and module.
.TP
.I \-\-timestamp
Another debugging flag. Used to display the times at various points
@@ -146,6 +133,22 @@ in the compilation process.
.I \-unsafe, -unsafe+
Enables compilation of unsafe code.
.TP
.I \-warnaserror, \-warnaserror+
Treat warnings as errors.
.TP
.I \-warn:LEVEL
Sets the warning level. 0 is the lowest warning level, and 4 is the
highest. The default is 2.
.TP
.I -r:ASSEMBLY1[,ASSEMBLY2], \-r ASSEMBLY1[,ASSEMBLY2]
Reference the named assemblies. Use this to use classes from the named
assembly in your program. The assembly will be loaded from either the
system directory where all the assemblies live, or from the path
explicitly given with the -L option.
.PP
You can also use a semicolon to separate the assemblies instead of a
comma.
.TP
.I \-v
Debugging. Turns on verbose yacc parsing.
.TP
@@ -155,21 +158,6 @@ Turns on C# 2.0 language features.
.I \-\-version
Shows the compiler version.
.TP
.I \-warnaserror, \-warnaserror+
Treat warnings as errors.
.TP
.I \-warn:LEVEL
Sets the warning level. 0 is the lowest warning level, and 4 is the
highest. The default is 2.
.TP
.I \-win32res:FILE
Specifies a Win32 resource file (.res) to be bundled into the
resulting assembly.
.TP
.I \-win32icon:FILE
Attaches the icon specified in FILE on the output into the resulting
assembly.
.TP
.I \-\-
Use this to stop option parsing, and allow option-looking parameters
to be passed on the command line.
+1 -18
View File
@@ -256,21 +256,6 @@ If set its the directory where the ".wapi" handle state is stored.
This is the directory where the Windows I/O Emulation layer stores its
shared state data (files, events, mutexes, pipes). By default Mono
will store the ".wapi" directory in the users's home directory.
.TP
.I "MONO_UNMANAGED_XSLT"
If set any value, System.Xml.Xsl.XslTransform uses libxslt-based
transformation engine (a.k.a Unmanaged XSLT). Unmanaged XSLT has
long been used for XSLT engine while Managed XSLT engine is so
new and might have some bugs. Basically we recommend Managed XSLT
solution, but if it contains some blocking bugs, then you can also
use traditional libxslt. If you want to use msxsl:script, you have
to select Managed XSLT.
.TP
.I "MONO_MANAGED_WATCHER"
If set to any value, System.IO.FileSystemWatcher will use the default
managed implementation (slow). If unset, mono will try to use FAM under
Unix systems and native API calls on Windows, falling back to the
managed implementation on error.
.SH FILES
On Unix assemblies are loaded from the installation lib directory. If you set
`prefix' to /usr, the assemblies will be located in /usr/lib. On
@@ -286,8 +271,6 @@ Visit http://mail.ximian.com/mailman/mono-list for details.
.SH WEB SITE
Visit: http://www.go-mono.com for details
.SH SEE ALSO
.BR mcs(1), mint(1), monodis(1), mono-config(5).
.PP
For ASP.NET-related documentation, see the xsp(1) manual page
.BR mcs(1), mint(1), monodis(1), mono-config(5)
-126
View File
@@ -1,126 +0,0 @@
.\"
.\" soapsuds manual page.
.\" (C) 2003 Novell, Inc.
.\" Author:
.\" Lluis Sanchez Gual ([email protected])
.\"
.TH soapsuds 1
.SH NAME
soapsuds \- Mono's Remoting Proxy Generator
.SH SYNOPSIS
.PP
.B soapsuds
[options] [inputs] [outputs]
.SH DESCRIPTION
.I soapsuds
is a tool for generating WSDL documents and client proxies for remoting services.
A WSDL document describes the methods that a service provides together with XML schemas
of all referenced data structures. A client proxy is a class which offers the same methods
as the service it represents, but provides no implementation, it just forwards calls to the
remote service.
.PP
Generated client proxies are not strictly necessary, since the runtime can
automatically generate proxies from the original service types. However, it implies the need
of distributing the service class to all clients. In some scenarios a better approach is
to use soapsuds to generate a proxy class which has the same interface as the service,
but without any implementation.
.PP
.I soapsuds
can generate a WSDL document from a set of types specified with the option
.I -types
or can extract the types from an assembly specified with
.I -inputassemblyfile.
In this last case, soapsuds will include schemas for all serializable classes in
the WSDL document.
.PP
Taking as input a WSDL document (or anything from which such document can be generated)
the tool can generate source code for the client proxy (using the
.I -gc
option) or it can directly generate an assembly that implements the proxy (with the
.I -outputassemblyfile
option). soapsuds will also generate fake serializable classes for all types defined
in the schema. However, beware that those classes will lack the semantics of the
original classes, since only data structure is generated.
.PP
.SH INPUT SOURCES
The following sources are available (only one can be specified):
.TP
.I "-urltoschema:url" "-url:url"
Url from which to retrieve the WSDL document.
.TP
.I "-types:type1,assembly[,serviceEndPoint][;type2,assembly[,serviceEndPoint]]..."
Specifies types for which to generate a schema or proxy. If no service endpoint is
provided, the one provided with the
.I -serviceendpoint
option is used.
.TP
.I "-inputassemblyfile:file", "-ia:file"
Assembly that contains the types to export.
.TP
.I "-inputschemafile:schena", "-is:schema"
Schema from which to generate proxy classes.
.SH INPUT OPTIONS
The following options are available:
.TP
.I "-inputdirectory:directory", "-id:directory"
Directory where DLLs are located.
.TP
.I "-serviceendpoint:url", "-se:url"
Url of the service to be placed in the WSDL document.
.SH OUTPUTS
The following output options are available (more than one can be specified):
.TP
.I "-outputassemblyfile:file", "-oa:file"
Generates the proxy code and compiles it into an assembly with the provided name.
.TP
.I "-outputschemafile:file", "-os:file"
Generates a WSDL document that represents the provided types.
.TP
.I "-generatecode", "-gc"
Generates proxy source code for the provided WSDL document or types.
.SH OUTPUT OPTIONS
The following options are available:
.TP
.I "-outputdirectory:directory", "-od:directory"
Directory where generated files will be placed.
.TP
.I "-proxynamespace:namespace", "-pn:namespace"
Namespace of the generated proxy.
.TP
.I "-nowrappedproxy", "-nowp"
Do not generate a wrapped proxy.
.TP
.I "-wrappedproxy", "-wp"
Generate a wrapped proxy.
.TP
.I "-strongnamefile:file", "-sn:file"
Strong name file.
.SH GENERAL OPTIONS
The following options are available:
.TP
.I "-nologo"
Supress the startup logo.
.TP
.I "-u:username", "-user:username"
The user name to use when connecting to the server.
.TP
.I "-p:password", "-password:password"
The password to use when connecting to the server.
.TP
.I "-d:domain", "-domain:domain"
The domain to use when connecting to the server.
.TP
.I "-httpproxyname:name", "-hpn:name"
Name of the http proxy.
.TP
.I "-httpproxyport:port", "-hpp:port"
Port of the http proxy.
.PP
.SH AUTHORS
Lluis Sanchez Gual ([email protected])
.PP
.SH LICENSE
wsdl is released under the terms of the GNU GPL.
.PP
.SH SEE ALSO
wsdl(1), disco(1), mono(1), mcs(1)
-76
View File
@@ -1,76 +0,0 @@
.\"
.\" wsdl manual page.
.\" (C) 2003 Novell, Inc.
.\" Author:
.\" Lluis Sanchez Gual ([email protected])
.\"
.TH wsdl 1
.SH NAME
wsdl \- Mono's Web Service Proxy Generator
.SH SYNOPSIS
.PP
.B wsdl
[options] [path | url]
.SH DESCRIPTION
.I wsdl
is a tool for generating proxy classes that can be used to access to web services.
The tool reads a WSDL document from the provided path or url, and downloads
referenced schemas or other WSDL documents if needed.
.PP
.SH OPTIONS
The following options are available:
.TP
.I "-appsettingurlkey:key" "-urlkey:key"
Specifies that the url for the services should be read from the <appsettings> section
of the configuration file, using the provided key.
.TP
.I "-appsettingbaseurl:url", "-baseurl:url"
Specifies a base URL for the service. The final URL will be constructed by
combining this value with the URL read from the
.I -appsettingurlkey
option, and the
.I location
attribute specified in the WSDL document.
.TP
.I "-language:language", "-l"
Language of the code to generate. It can be CS (default) or VB.
.TP
.I "-namespace:name", "-n:name"
The namespace of the generated classes. If none is specified, the default
namespace is used.
.TP
.I "-out:filename", "-o:filename"
The target file for generated code.
.TP
.I "-protocol:protocol", "-p:protocol"
The protocol for which to generate code. It can be Soap (default), HttpGet or
HttpPost.
.TP
.I "-sample:METHOD"
This will display XML request and reply of the sample invocations to
that SOAP message. You can use the -protocol: option to render the
message in different forms.
.TP
.I "-server"
Generate a server skeleton instead of a client proxy.
.TP
.I "-nologo"
Supress the startup logo.
.TP
.I "-u:username", "-user:username"
The user name to use when connecting to the server.
.TP
.I "-p:password", "-password:password"
The password to use when connecting to the server.
.TP
.I "-d:domain", "-domain:domain"
The domain to use when connecting to the server.
.PP
.SH AUTHORS
Lluis Sanchez Gual ([email protected])
.PP
.SH LICENSE
wsdl is released under the terms of the GNU GPL.
.PP
.SH SEE ALSO
disco(1), soapsuds(1), mono(1), mcs(1)
-8
View File
@@ -1,11 +1,3 @@
2004-01-14 Martin Willemoes Hansen <[email protected]>
* INSTALL.txt: Fixed, autogen should be autogen.sh
2003-12-01 Cesar Lopez Nataren <[email protected]>
* Added dirs mcs/jtest and mcs/jerrors.
2003-10-28 Jackson Harper <[email protected]>
* INSTALL.txt: Tell users where to find monocharges, do not
+11 -24
View File
@@ -9,32 +9,22 @@ be supplemented by the class libraries, which are written in C#. This
package contains the components written in C#: class libraries,
compilers and tools.
*********************************************************************
* *
* NOTICE *
* *
* Unless you are developing the class libraries, you should *
* not need to do any build steps in this directory. *
* *
* Go to ../mono and read the README file to compile and *
* install. *
* *
*********************************************************************
Build Process for Users.
========================
If you only want to build a snapshot or a fresh CVS checkout of the
sources, you should go into the `mono' sibling directory and issue the
make fullbuild command, like this:
following command:
cd ../mono
./autogen.sh --prefix=/usr/local
./autogen --prefix=/usr/local
make fullbuild
That will build and install the code in a single pass. The
compilation is bundled with the build due to dependencies on the class
libraries on the runtime.
Build Features for Developers of Mono.
======================================
Build Features for Developers.
==============================
These instructions apply to both Linux and Windows. To build this
package, you must already have a C# compiler installed. This means
@@ -44,13 +34,6 @@ www.go-mono.com/daily. On Windows, you can just use the
Microsoft compiler. You also need GNU make to build the software (on
Windows, you will need for example the Cygwin environment setup).
You can customize your MCS configuration by using:
./configure [--prefix=PREFIX] [--profile=PROFILE]
If you do not run the above, the defaults are /usr/local for the
prefix, and `default' for the profile.
To build the compiler and class libraries, run:
make
@@ -62,6 +45,10 @@ To install them, run the following:
make install
The default prefix is /usr/local. To change this configuration option type:
echo prefix=/your-prefix >> build/config.make
If you get "corlib out of sync" errors, try
make PROFILE="atomic"
@@ -125,7 +112,7 @@ rest of your build can proceed.
If you want to always use the atomic profile, run this command:
./configure --profile=atomic
echo PROFILE=atomic >> build/config.make
More About the Build System
===========================
-3
View File
@@ -1,3 +0,0 @@
*~
.*
*.out
-12
View File
@@ -1,12 +0,0 @@
Imports System
Module BoolLiteralTest
Sub Main()
Try
Dim b As Boolean
b = True
b = False
Catch e As Exception
Console.WriteLine(e.Message)
End Try
End Sub
End Module
-10
View File
@@ -1,10 +0,0 @@
Module BoolLiteralTest1
Sub Main()
Try
Dim b As Boolean
b = Not True
Catch e As Exception
Console.WriteLine(e.Message)
End Try
End Sub
End Module
-17
View File
@@ -1,17 +0,0 @@
Module CharacterLiterals
Sub Main()
Dim c As Char
c = "x"
c = "X"
Dim a As String = "X"c
If a <> c Then
Throw New System.Exception("a is not same as c")
End If
'the outcome should be "x"
c = """x"""
End Sub
End Module
-11
View File
@@ -1,11 +0,0 @@
Module CharacterLiterals1
Sub Main()
Dim c As Char
c = "x"c
Dim a As String = "X"
If a <> c Then
Throw New System.Exception("a is not same as c")
End If
End Sub
End Module
-6
View File
@@ -1,6 +0,0 @@
Module CharacterLiteralsC2
Sub Main()
Dim ch As Char
ch = "xc"c
End Sub
End Module
-5
View File
@@ -1,5 +0,0 @@
Module CharacterLiteralsC3
Sub Main()
c = ""x"
End Sub
End Module
-48
View File
@@ -1,48 +0,0 @@
Module DateLiterals
Sub Main()
Dim d As Date
dim d1 as Date
d = # 12/1/2001 3:24:59 PM #
d1 = # 12-01-2001 3:24:59 PM #
if d1 <> d then
Throw new System.Exception("#A1 : values d and d1 are not same")
end if
d = # 12/01/2001 #
d1 = # 12/01/2001 12:00:00 AM#
if d1 <> d then
Throw new System.Exception("#A2 : values d and d1 are not same")
end if
d = # 3:24:59 #
d1 = # 01/01/0001 3:24:59 AM#
if d1 <> d then
Throw new System.Exception("#A3 : values d and d1 are not same")
end if
d = # 15:24:59 #
d1 = # 01/01/0001 3:24:59 PM#
if d1 <> d then
Throw new System.Exception("#A4 : values d and d1 are not same")
end if
d = # 3 PM #
d1 = # 01/01/0001 15:00:00 #
if d1 <> d then
Throw new System.Exception("#A5 : values d and d1 are not same")
end if
d = # 3:13 PM #
d1 = # 01/01/0001 3:13:00 PM#
if d1 <> d then
Throw new System.Exception("#A6 : values d and d1 are not same")
end if
End Sub
End Module
-10
View File
@@ -1,10 +0,0 @@
Module DateLiterals
Sub Main()
Dim d As Date
d = # 15/01/2002 #
End Sub
End Module
-12
View File
@@ -1,12 +0,0 @@
Module DateLiterals
Sub Main()
Dim d As Date
' if minuts and seconds are not specified
' AM or PM must be specified
d = # 1 #
End Sub
End Module
-10
View File
@@ -1,10 +0,0 @@
Module DateLiterals
Sub Main()
Dim d As Date
d = 23:05:07
End Sub
End Module
-14
View File
@@ -1,14 +0,0 @@
' This test case runs on .Net 1.1 as well
' Though the vb spec says the date format should be as follows
' #[Whitespace+]DateOrTime[Whitespace+]#
Module DateLiterals
Sub Main()
Dim d As Date
d = #01/01/2004 5:05:07PM#
End Sub
End Module
-12
View File
@@ -1,12 +0,0 @@
Module DateLiterals
Sub Main()
Dim d As Date
d = # 12/40/2002 #
d = # 11/31/2002 #
End Sub
End Module
-10
View File
@@ -1,10 +0,0 @@
Module DateLiterals
Sub Main()
Dim d As Date
d = # 11/31/2002 #
End Sub
End Module
-10
View File
@@ -1,10 +0,0 @@
Module DateLiterals
Sub Main()
Dim d As Date
d = # 12/31/02 #
End Sub
End Module
-10
View File
@@ -1,10 +0,0 @@
Module DateLiterals
Sub Main()
Dim d As Date
d = # 13:05:07 PM #
End Sub
End Module
-10
View File
@@ -1,10 +0,0 @@
Module DateLiterals
Sub Main()
Dim d As Date
d = # 25:05:07 #
End Sub
End Module
-10
View File
@@ -1,10 +0,0 @@
Module DateLiterals
Sub Main()
Dim d As Date
d = # 13:05:07 AM #
End Sub
End Module
-10
View File
@@ -1,10 +0,0 @@
Module DateLiterals
Sub Main()
Dim d As Date
d = # 11:65:07 PM #
End Sub
End Module
-10
View File
@@ -1,10 +0,0 @@
Module DateLiterals
Sub Main()
Dim d As Date
d = # 11:00:60 PM #
End Sub
End Module
-18
View File
@@ -1,18 +0,0 @@
Module DecimalTypeCharTest
Sub Main()
Try
Dim m As Decimal
m = f(20.2D)
If m <> 20.2D Then
Throw New Exception("DecimalTypeCharTest: failed")
End If
Exit Sub
Catch e As Exception
Console.WriteLine(e.Message)
End Try
End Sub
Function f@(ByVal param@)
f = param
End Function
End Module
-18
View File
@@ -1,18 +0,0 @@
Module DoubleTypeCharTest
Sub Main()
Try
Dim m As Double
m = f(20)
If m <> 20 Then
Throw New Exception("DoubleTypeCharTest: failed")
End If
Exit Sub
Catch e As Exception
Console.WriteLine(e.Message)
End Try
End Sub
Function f#(ByVal param#)
f = param
End Function
End Module
-3
View File
@@ -1,3 +0,0 @@
Module FloatingPointLiteralsTest
End Module
-18
View File
@@ -1,18 +0,0 @@
Imports System
Module Identifier
Function _abc()
End Function
Sub xys2()
End Sub
'' escaped identifier
Sub [sub]()
End Sub
Dim [function] As Int16
Sub Main()
End Sub
End Module
-9
View File
@@ -1,9 +0,0 @@
Module IdentifierFail1
' not a valid identifier as per spec
' but accepted by .net 1.0
Sub __()
End Sub
Sub Main()
End Sub
End Module
-8
View File
@@ -1,8 +0,0 @@
Module IdentifierFail2
Sub _() ' not a valid identifier
End Sub
Sub Main()
End Sub
End Module
-7
View File
@@ -1,7 +0,0 @@
Module IdentifierFail3
sub 2sd() ' not a valid identifier
End Sub
Sub Main()
End Sub
End Module
-8
View File
@@ -1,8 +0,0 @@
Module IdentifierFail4
'' invalid identifier
sub sub()
End Sub
Sub Main()
End Sub
End Module
Loaded 100 of 2380 files, more files were not shown because too many files have changed in this diff. Show more