* ADO.NET
- The coordinator for the ADO.NET implementation is
- <a href="mailto:rodrigo@ximian.com">Rodrigo Moya</a>,
- with the collaboration of:
- <a href="mailto:danmorg@sc.rr.com">Daniel Morgan</a>,
- <a href="mailto:tim@timcoleman.com">Tim Coleman</a>,
- <a href="mailto:brianlritchie@hotmail.com">Brian Ritchie</a>, and
- <a href="mailto:vladimir@pobox.com">Vladimir Vukicevic</a>.
-
-
-* Action plan
-
- The current plan to implement ADO.NET is as follows:
-
- <b>Step 1:</b> Initial <a href="http://msdn.microsoft.com/library/en-us/cpref/html/frlrfsystemdatasqlclient.asp?frame=true">System.Data.SqlClient</a> Provider:
-
- <ul>
- * Initial implementation of System.Data.SqlClient is based on
- the <a href="http://www.postgresql.org/idocs/">PostgreSQL C API</a> which is a
- client API to the PostgreSQL DBMS. PostgreSQL was chosen so we could quickly
- create and test the System.Data classes.
-
- * Once the <a href="http://msdn.microsoft.com/library/en-us/cpref/html/frlrfsystemdatasqlclient.asp?frame=true">System.Data.SqlClient</a>
- code is functional and is usable by other people, we willl move it to
- Mono.Data.PostgreSQL.
-
- * <a href="http://www.go-mono.com/postgresql.html">Current PostgreSQL ADO.NET Provider Status and Test Notes</a>
-
- </ul>
-
- <b>Step 2:</b> <a href="http://msdn.microsoft.com/library/en-us/cpref/html/frlrfSystemDataOleDb.asp?frame=true">System.Data.OleDb</a> Provider:
-
- <ul>
- * <p>On Unix systems: System.Data.OleDb uses the
- <a href="http://www.gnome-db.org/">LibGDA</a>
- engine.
-
- <p>LibGDA is a data access engine like ADO/OLE-DB, but for Unix. The
- GDA in libGDA stands for GNU/GNOME Data Access, but it does not require GNOME.
- It only requires glib2 and libxml2. LibGDA is used by
- libgnomedb, GNOME-DB, and gaSQL.
-
- <p>There is work under way to get libgda working under
- Windows using Cygwin by the GNOME-DB developers.
-
- <p>LibGDA has providers for
- <a href="http://www.mysql.com/">MySQL</a>,
- <a href="http://www.postgresql.org/">PostgreSQL</a>,
- XML,
- ODBC (via <a href="http://www.unixodbc.org/">unixODBC</a>),
- <a href="http://www.oracle.com/">Oracle</a>,
- <a href="http://www.borland.com/products/downloads/download_interbase.html">Interbase</a>,
- <a href="http://www.sybase.com/downloads">Sybase</a> and
- <a href="http://www.microsoft.com/sql/default.asp">Microsoft SQL Server</a> (
- via <a href="http://www.freetds.org/">FreeTDS</a>),
- <a href="http://www-3.ibm.com/software/data/db2/">IBM DB2 Universal Database</a>,
- <a href="http://www.hwaci.com/sw/sqlite/download.html">SQL Lite</a>,
- and http://www.microsoft.com/office/access/default.asp">MS Access</a>
- (via <a href="http://mdbtools.sourceforge.net/">MDB Tools</a>).
-
- * On Windows systems: System.Data.OleDb will use libgda as well,
- if we can get it working, or OLE-DB as
- its engine.
-
- </ul>
-
- <b>Step 3:</b> <a href="http://msdn.microsoft.com/library/en-us/cpref/html/frlrfsystemdatasqlclient.asp?frame=true">System.Data.SqlClient</a> Provider:
+** Data Access in Mono
- <ul>
- * <p>System.Data.SqlClient will then become a
- provider for Microsoft SQL Server, both on Windows and
- Linux, to be compatible with applications written
- for the Microsoft .NET Development Framework.
-
- <p>Once Step 1 has been completed and the PostgreSQL
- provider support has been moved to its own place at
- Mono.Data.PostgreSQL, we will use
- <a href="http://www.freetds.org/">FreeTDS</a> as the basis
- for providing access to Microsoft SQL Server databases. Or we will
- use FreeTDS and jTDS (a 100% Java JDBC Provider for TDS) as a basis for
- creating a pure managed SQL Server provider.
-
- <P>FreeTDS is a C API for Unix and Windows that implements
- the TDS (Tabular Data Stream) protocol used in accessing
- Microsoft SQL Server and Sybase databases. A .NET Data Provider could be
- created for Sybase databases as well, but this would be put in Mono.Data.Sybase.
- </ul>
-
- <b>Step 4:</b> <a href="http://msdn.microsoft.com/downloads/sample.asp?url=/MSDN-FILES/027/001/668/msdncompositedoc.xml&frame=true">System.Data.Odbc</a> Provider:
+<ul>
+ <li>Today, our goal is to be compatible with .NET 1.1 and .NET 1.0. We also would like
+ to extend data access beyond what is included with .NET 1.0 and .NET 1.1,
+ such as, include access to more databases, such as, PostgreSQL and MySQL,
+ but also provide classes that help in creating data source-agnostic code, such as,
+ Mono.Data.ProviderFactory.</li>
+
+ <li>In the future, we would like to be compatible with .NET 1.2. This includes features
+ like <a href="http://longhorn.msdn.microsoft.com/lhsdk/ndp/daconworkingwithobjectspacesarchitecture.aspx">ObjectSpaces</a></li>
- <ul>
- * An ADO.NET Provider for ODBC has been created in
- System.Data.Odbc for those using ODBC.
- On Unix, <a href="http://www.unixodbc.org/">unixODBC</a> mabye used
- which has libodbc.so
- On Windows, uses the native ODBC libraries (odbc32.dll) that comes
- with Windows since unixODBC is supposed to be compatible with that.
- If you do not have odbc32.dll on Wwindows, get the latest MDAC
- from Microsoft. The mapping between these native shared libraries is handled
- in etc/mono/config
- In mono cvs, the file is mono/data/config.in
-
- <p>unixODBC works on Unix and Windows. Well, I have not actually
- used it on Cygwin, but it does build and install without problems.
-
- <p>unixODBC has providers for:
- Oracle, Microsoft SQL Server and Sybase (via FreeTDS),
- MySQL, PostgreSQL, Informix, IBM DB2 Universal Database,
- Interbase, miniSQL (mSQL), AdabasD, Empress, Ingres, Sap DB, and others.
-
- </ul>
-
- <b>Step 5:</b> Other ADO.NET providers:
-
- <ul>
- * <p>The idea in Microsoft .NET System.Data is to have
- a managed provider for each supported DBMS. System.Data.SqlClient
- for Microsoft SQL Server.
- System.Data.OracleClient for Oracle 8i and 9i.
-
- <p>Two Mono.Data providers have been started:
- Mono.Data.MySql for the MySQL client/server database
- and Mono.Data.SqliteClient for the SQL Lite database.
- See Current Status for more information on these providers.
-
- <p>Some providers we would like to have are
- Mono.Data.DB2, Mono.Data.miniSQL,
- System.Data.OracleClient, Mono.Data.Interbase,
- Mono.Data.Berkeley, and SapDB.
- Others, of course, are welcomed.
-
- <p>System.Data has been designed so
- non-database providers can be created too.
- </ul>
-
- <b>Step 6:</b> Create tools for ADO.NET
+</ul>
- <ul>
- * <p><b>SQL# CLI - a command-line tool</b> to execute SQL commands,
- test connection strings, and connect to various ADO.NET
- providers in Mono. The SQL# CLI has been started on and can be found in
- mcs/class/System.Data/Test/SqlSharpCli.cs
- It is written in C# and runs on Mono.
-
- * <p><b>SQL# GUI - a GUI tool</b> to execute SQL commands. This
- has not been started. The idea is to use the GnomeDbSqlEditor,
- GnomeDbBrowser, and GnomeDbGrid gtk+ widgets that exists
- in libgnomedb# that is part of gtk#. However, we could base it
- on System.Windows.Forms, but System.Windows.Forms in Mono
- is not as complete as gtk#.
-
- <p>libgnomedb uses libgda for its data model and data access capabilities and
- can be found <a href="http://www.gnome-db.org/">here</a>. libgnomedb#
- and gda# are part of <a href="http://gtk-sharp.sourceforge.net/">gtk#</a>
- libgnomedb# is the C# bindings to libgnomedb which is a gtk+ GUI
- widget library for data access.
- gda# is the C# bindings to libgda which is a generic data access
- library that has providers for many databases.
-
- * <p>ADO.NET Configuration command-line and GUI tools. These tools have
- not been started. They could become a part of SQL# though. The
- configuration tool can be used to set up DSNs for the ODBC and OLE-DB
- providers. The tools would be written in C# and run on Mono.
-
- </ul>
-
-* Current Status
+** Bugs and Feature Requests
- <p>We are working on Steps 1, 2, 4, and 5. We still have tons and tons of
- stuff still to do. If you have any ideas, let us know on the mono-list@ximian.com
-
- <p><b>For Step 1</b>, the <p>PostgreSQL</p> provider can connect,
- execute commands, retrieve data via a Data Reader, read data in a DataTable
- in a DataSet via a Data Adapter, get a DataTable holding schema data,
- and use input parameters in its SQL. Currently, the PostgreSQL provider
- exists in System.Data.SqlClient. It needs to be moved
- to Mono.Data.PostgreSQL so the Microsoft SQL Server provider can
- be placed in System.Data.SqlClient.
-
- <p><b>For Step 2</b>, Rodrigo Moya has been working on <b>System.Data.OleDb</b>
- which uses libgda
- which is an OLE-DB/ADO data access for Unix. The C-Sharp bindings to libgda
- currently work - meaning they can compile, run, and you can connect to a
- PostgreSQL database via libgda via the C-Sharp bindings to libgda. Basic
- functionality (execution of commands, data retrieval, transactions, etc) are
- now working. Current focus is on filling up the missing pieces (Data adapters
- mainly) and schema support. We need help building libgda on Windows though. libgda
- builds find on linux though.
-
- <p><b>For Step 3</b>, we need someone to start on the <b>Microsoft SQL Server</b>
- and <b>Sybase</b> support. This can be done by creating
- a <b>FreeTDS</b> .NET Data Provider
- or C# bindings to FreeTDS native libraries. A better solution, but a solution
- that would take longer, would be to create a pure
- managed provider in C# that implements the TDS (Tabular DataStream) protocol. TDS
- is used to access Microsoft SQL Server and Sybase databases. Another possibility
- is to wrap System.Data.SqlClient around System.Data.OleDb since System.Data.OleDb on
- Mono uses <a href="http://www.gnome-db.org/">libgda</a> and libgda has
- a FreeTDS provider. Yet another possibility, port
- the <a href="http://jtds.sourceforge.net/">jTDS</a> provider to a pure C# ADO.NET \r
- provider. jTDS is a 100% pure Java (Type 4) open source JDBC 2.0 driver for \r
- the Microsoft SQL Server series (6.5, 7.x and 2000). \r
-
- <p><b>For Step 4</b>, Brian Ritchie has contributed an initial implementation of
- an <b>ODBC</b> ADO.NET Provider that uses unixODBC on Linux and the native odbc\r
- that comes on Windows. There is basic implementations of \r
- OdbcConnection, OdbcCommand, OdbcDataReader, OdbcParameter, and \r
- OdbcParameterCollection. The provider can execute queries and display result sets \r
- (and ExecuteNonQuery too). Currently, developers are working on the Parameter & \r
- Transaction support. It was tested on Debian against a DB2 7.2 UDB. It was\r
- also test on Windows XP against a Microsoft SQL Server 2000.\r
-
- <p><b>For Step 5</b>, we have create two Mono.Data providers so far:
- Mono.Data.MySql and Mono.Data.SqliteClient.
-
- <p><b>Mono.Data.MySql</b> is an ADO.NET provider for
- the <b>MySQL</b> client/server database management system
- that uses the MySQL C Client Library. This provider is
- found in Mono.Data.MySql. Currently, we can connect,
- execute simple commands, and
- retrieve results using a data reader. A schema DataTable has been partially
- implemented which is returned from GetSchemaTable() in MySqlDataReader.
- The shared client libraries
- between windows version and linux are different: windows has libmySQL.dll
- while linux has libmysqlclient.so. This is handled by the
- file etc/mono/config which is mapped by the mono runtime in knowing
- which native shared library to load. In cvs, this file is mono/config.in and
- can be modified with a text editor.
- The C# Bindings to MySQL are thanks to Brad Meril.
+<ul>
- <p><b>Mono.Data.SqliteClient</b> is an ADO.NET provider for
- the <b>SQL Lite</b> database. SQL Lite can be
- found <a href"http://www.hwaci.com/sw/sqlite/download.html">here</a>.
- There is SQL Lite binaries for Linux and Windows. sqlite.dll on Windows
- and sqlite.so on Linux. The SQL Lite proivder
- was contributed by Vladimir Vukicevic.
-
- <p><b>DataSet, DataAdaptor, DataTable, DataRelation, DataRow, DataColumn,
- DataColumnCollection, DataRowCollection, and others</b> need more work.
-
- <p><b>Integration with ASP.NET</b> needs to be started, such as, data binding
- to a System.Web.UI.WebControls.DataGrid. This may involve implementing many classes
- in System.Web and System.Data. Gonzalo, Gaurav, Leen, Patrik, Duncan, and others are
- working very hard on the ASP.NET support. If you want to help,
- contact <a href="mailto:gonzalo@ximian.com">Gonzalo Paniagua Javier</a>
-
- <p><b>Integration with Windows.Forms</b> needs to be started, such as, data binding
- to a System.Windows.Forms.DataGrid. This may involve implementing many classes
- in System.Windows.Forms and System.Data.
+ <li>Bugs with Mono or any data provider in Mono should be reported
+ in Mono's Bugzilla <a href="http://bugzilla.ximian.com/">here</a>. If you
+ do not have a Bugzilla user account, it is free
+ and easy to create
+ one <a href="http://bugzilla.ximian.com/createaccount.cgi">here</a>.</li>
- <p><b>Integration with <a href="http://gtk-sharp.sourceforge.net/">GTK#</a></b>
- needs to be started, such as, data binding
- to a GtkTreeView. This may involve creating new classes
- to go between the glist data model and the ADO.NET data model.
- Mike Kestner would be the best person to ask for help on GTK#.
-
- <p><b>Integration with QT#</b> needs to be started. Any information on
- how this can be done is appreciated. Adam Treat would be the best
- person to ask about QT#.
-
- <p><b>Integration with GDA# and Libgnomedb#</b> which exists in GTK# needs
- to be started. Creating classes
- to bind data between the data model in ADO.NET and the data model that
- exists in <a href="http://www.gnome-db.org/">GDA</a> and
- <a href="http://www.gnome-db.org/">libgnomedb</a>. There are some nifty widgets
- (GUI controls) that can be used, such as, GnomeDbGrid, GnomeDbBrowswer,
- GnomeDbSqlEditor, GnomeDbList, GnomeDbLogin, GnomeDbReportEditor, GnomeDbTableEditor,
- GnomeDbCombo, and GnomeDbForm.
-
- <p><b>XML support in System.Data</b> needs to be started. This involves working on
- the classes: DataSet, XmlDataDocument, and the method ExecuteXmlReader() that
- exists in a provider's class that implements IDbCommand, and others.
-
- <p><b>ADO.NET Multiplexor Provider</b> needs to be created. This is not
- part of Microsoft .NET, but it needs to be able to run on Microsoft .NET
- and Mono. This provider can be a generic provider, much like the ODBC.NET and
- OLEDB.NET providers are, but be written in 100% C# and be configurable via
- a configuration file. This provider will multiplex to other providers
- that exist. If one does not exist for a given DBMS,
- default to the ODBC or OLEDB .NET provider. Or it could be a class
- that its sole duty is to dynamically create a provider's Connection class
- based on a configuration file. It can provide some utility functions as
- well that can be used in all or most of the providers, such as, what
- parameter marker character should be used: a colon, at, question mark,
- or square brackets.
-
- <p>According to Gonzalo, this is how it could be implemented:
-\r
- <p>After some work done in System.Configuration, you can now do something\r
- like: \r
-\r
-<pre>\r
- // Get an instance of the multiplexor from machine.config file\r
- // Can be overriden in the application config file \r
- object o = ConnectionSettings.GetConfig ("mono.data/multiplexor");\r
- if (o == null)\r
- --- error\r
- \r
- Multiplexor mp = (Multiplexor) o;\r
- \r
- // may be a string [] argument can help passing arguments\r
- IDbConnection cnc = mp.CreateConnection (providerName);\r
-</pre>\r
- \r
- <p>and in the machine.config file:\r
-\r
-<pre>\r
- <configuration>\r
- <configSections>\r
- <section name="mono.data"\r
- type="Mono.Data.MultiplexorSectionHandler,Mono.Data" />\r
- ....\r
- </configSections>\r
- ...\r
- <sectionGroup name="mono.data">\r
- <multiplexor>\r
- <add provider="PostgreSQL" type="Mono.Data.PostgreSQLClient,Mono.Data"\r
- validate="false" parameters="USER=xxx;HOST=127.0.0.1;DBNAME=xxx" />\r
- </multiplexor>\r
- </sectionGroup>\r
- </configuration>\r
-</pre>\r
-\r
- <p>validate="false" tells MultiplexorSectionHandler not to load the Type\r
- until an instance is required. You can add more attributes or whatever\r
- inside <multiplexor> as long as MultiplexorSectionHandler parses it.\r
-\r
-<pre> \r
- public class MultiplexorSectionHandler :\r
- IConfigurationSectionHandler\r
- {\r
- public object Create (object parent, object configContext,\r
- XmlNode section)\r
- {\r
- Multiplexor mp;\r
- // Here you get the ChildNodes and set up a Multiplexor\r
- // instance that will hold the information needed to create \r
- // instances of each provider. Only one instance will be \r
- // created by the config system.\r
- return mp;\r
- }\r
- }\r
-</pre>\r
-\r
- <p>This way, if our providers works with MS, the user can test them in both\r
- MS and mono by just adding a few lines to machine.config (i still have\r
- to upload a default machine.config file for mono). And this is the .NET\r
- way of doing it (of course, if you prefer, you can use the other config\r
- file. I just wanted to make people aware of this feature that now works\r
- on mono).\r
+ <li>Any requests for new features or missing functionality
+ can entered as a bug in Bugzilla too</li>
+</ul>
- <p><b>Building System.Data</b>
+** ADO.NET Data Providers
- <p>The System.Data.dll gets built with the rest of the class library.
- To compile the System.Data.dll assembly separately, you need:
-
- <b>On Unix</b>
-
+<p>Mono has many ADO.NET Data Providers to get you connected:
+
+<ul>
+ <li><a href="http://www.go-mono.com/ibmdb2.html">IBM DB2 Universal Database</a></li>
+ <li><a href="http://www.go-mono.com/mysql.html">MySQL</a></li>
+ <li><a href="http://www.go-mono.com/odbc.html">ODBC</a></li>
+ <li><a href="http://www.go-mono.com/oracle.html">Oracle</a></li>
+ <li><a href="http://www.go-mono.com/oledb.html">OLE DB</a></li>
+ <li><a href="http://www.go-mono.com/postgresql.html">PostgreSQL</a></li>
+ <li><a href="http://www.go-mono.com/sqlclient.html">Microsoft SQL Server</a></li>
+ <li><a href="http://www.go-mono.com/sqlite.html">SQL Lite</a></li>
+ <li><a href="http://www.go-mono.com/sybase.html">Sybase</a></li>
+ <li><a href="http://www.go-mono.com/tdsclient.html">Older Microsoft SQL Server and Sybase databases</a></li>
+</ul>
+
+<p>External Projects that have created ADO.NET Providers that work on Mono:
+
+<ul>
+
+ <li><a href="http://www.go-mono.com/firebird.html">Firebird Interbase</a></li> is a
+ Firebird SQL Managed data provider. It can be used with Interbase databases too. It
+ is written in 100%C# and does not require a client library. Works on .NET and Mono.</a>
+ <li><a href="http://gborg.postgresql.org/project/npgsql/projdisplay.php">Npgsql</a> is a
+ PostgreSQL Managed data provider written
+ in 100% C#, does not require a client library, and works on .NET and Mono</li>
+ <li><a href="http://sourceforge.net/projects/mysqlnet/">MySQLNet</a> is a
+ MySQL Managed data provider written in 100% C#, does not
+ require a client library, and works on .NET and Mono</li>
+</ul>
+
+** Tools
+
+<p>Some tools that can be used for ADO.NET and other technologies (ASP.NET, XML, etc).
+
+<ul>
+ <li>sqlsharp.exe
+ <ul>
+ <li>SQL# is a command line query tool included with Mono to enter and execute SQL statements</li>
+ </ul>
+ </li>
+ <li>xsd.exe
+ <ul>
+ <li>XML Schema Definition tool</li>
+ <ul>
+ <li><b>XDR to XSD</b> - used to generate an XML schema from an XDR (XML Data Reduced schema) file. \r
+ XDR was used by Microsoft prior to XSD becoming a W3C recommendation. So, this needs\r
+ to be supported for legacy reasons</li>\r
+ <li><b>XML to XSD</b> - used to generate an XML schema from an XML file</li> \r
+ <li><b>XSD to DataSet</b> - used to generate DataSet classes from an XSD schema file. The\r
+ DataSet classes created can then be used with XML data</li>\r
+ <li><b>XSD to Classes</b> - used to generate classes from an XSD schema file. The \r
+ classes created can be used with System.XML.Serialization.XMLSerializer \r
+ to read and write XML code that follows the schema</li>\r
+ <li><b>Classes to XSD</b> - used to generate an XML schema \r
+ from type(s) in a assembly file. The \r
+ XML schema created by the tool defines the XML format used \r
+ by System.XML.Serialization.XMLSerializer</li>\r
+ </ul>\r
+ </li>\r
+ </ul>\r
+ </li>
+</ul>
+
+** Extra Classes in Mono ADO.NET
+
+ <p>An ADO.NET <a href="http://www.go-mono.com/provider-factory.html">Provider Factory</a>
+ was created by Brian Ritchie. The
+ Provider Factory is a way to dynamically create
+ connections, commands, parameters, and data adapters based on configuration
+ information.
+
+** Database Access from ASP.NET
<ul>
- * update your mono sources. Be sure you have latest mcs.exe
- and .dll's, since there have been many fixes needed for
- compilation on Linux.
-
- * compile System.Data.dll:
-<pre>
- cd mcs/class/System.Data<br>
- mcs --target library -o System.Data.dll @list
-</pre>
+ <li>Take a look at xsp in cvs and look at the examples in test: dbpage1.aspx
+ and dbpage2.aspx:
+ <ul>
+ <li>Notice that the namespace System.Data is imported via <b>import</b></li>
+ <li>A NameValueCollection is gotten using ConfigurationSettings.AppSetings. These
+ settings are gotten from the file server.exe.config which is a XML file. The XML
+ file has a section appSettings. In the appSettings section, you have keys
+ for DBProviderAssembly, DBConnectionType, and DBConnectionString.
+ <ul>
+ <li><b>DBProviderAssembly</b> is the assembly of the ADO.NET provider.
+ For example:
+ "ByteFX.Data"</li>
+ <li><b>DBConnectionType</b> is the System.Type of the class that
+ implements System.Data.IDbConnection that is found
+ in the DBProviderAssembly.
+ For example:
+ "ByteFX.Data.MySqlConnection"</li>
+ <li><b>DBConnectionString</b> is the ConnectionString to set to the
+ IDbConnection object to use in opening a connection to a data source.
+ For Example:
+ "hostaddr=127.0.0.1;user=monotest;password=monotest;dbname=monotest"</li>
+ </ul>
+ <li>The function GetConnectionData() gets the database provider assembly, connection type,
+ and connection string parameters if they exist; otherwise, it uses default values. This is
+ done during the loading of the web page.</li>
+ <li>With the connection parameters, the assembly is loaded, the connection type is verified that
+ it implements IDbConnection and an instance of the class can be created, creates a instance
+ of the class, sets the connection string, and opens the connection.</li>
+ </ul>
+ </li>
</ul>
- <b>On Windows</b>
-
- <ul>
- * update your mono sources. Be sure you have latest mcs.exe
- and .dll's. You can use the same method as Linux,
- or you can use NAnt.
-
- * To use NAnt:
-
-<pre>
- cd mcs/class/System.Data
- ../../nant/NAnt.exe
-</pre>
+** Testing
+
+<ul>
+ <li>Testing connection-oriented classes are done
+ via the provider specific tests
+ found in the mcs source at mcs/class</br>
+ <table border=1>
+ <tr>
+ <td><b>Name</b></td>
+ <td><b>Assembly /</br> Namespace</b></td>
+ <td><b>Test</b></td>
+ </tr>
- This will automatically copy the System.Data.dll to Test.
- If you need to do a clean for the System.Data.dll assembly,<br><br>
-
-<pre>
- cd mcs/class/System.Data
- ../../nant/NAnt.exe clean
-</pre>
- </ul>
+ <tr>
+ <td>Microsoft</br> SQL</br> Server</br></td>
+ <td>System.Data /</br> System.Data.SqlClient</td>
+ <td>SqlTest.cs at</br> System.Data/Test</td>
+ </tr>
+
+ <tr>
+ <td>PostgreSQL</br> (Npgsql)</td>
+ <td>Npgsql /</br> Npgsql</td>
+ <td>*.cs at</br> Npgsql/Test</td>
+ </tr>
+
+ <tr>
+ <td>Oracle</br> (Mono)</td>
+ <td>System.Data.OracleClient /</br> System.Data.OracleClient</td>
+ <td>TestOracleClient.cs at</br> System.Data.OracleClient/Test</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>
+ </tr>
+
+ </table>
+
+
+ <li><a href="http://www.go-mono.com/testing.html">Testing non-connection classes</a> are
+ done via mono's modified version of NUnit.
+ <ul>
+ <li>To run all the NUnit tests for Mono, you need the mcs source. cd to the root
+ of the mcs source. To run it:
+ <ul>
+ <li>make test</li>
+ </ul>
+ </li>
+ <li>If you just want to run the NUnit tests for System.Data, you would cd into
+ the mcs source at class/System.Data/Test and run it:
+ <ul>
+ <li>make test</li>
+ </ul>
+ </li>
+ </ul>
+ </li>
+
+</ul>
projects / mono.git / blobdiff