X-Git-Url: http://wien.tomnetworks.com/gitweb/?a=blobdiff_plain;f=web%2Fado-net;h=0095d79ef79996374030641fce45c5c8a01272ac;hb=f514aab35c57e64ae361d7069676cdb8ce7bf857;hp=e509c91d12ae97cd2f9a4e480208062387841469;hpb=726fef391cc423f85f0dd1a40a00c63cdfb7a570;p=mono.git diff --git a/web/ado-net b/web/ado-net index e509c91d12a..0095d79ef79 100644 --- a/web/ado-net +++ b/web/ado-net @@ -1,158 +1,108 @@ * ADO.NET -

Mono's ADO.NET Developers: -

+** Data Access in Mono + + -

The current plan to implement ADO.NET is as follows: +** Bugs and Feature Requests -

+ -

Constraints need lots of work +** ADO.NET Data Providers -

TypeDataSetGenerator needs to be stubbed and implemented. - -

DataSet, DataAdaptor, DataTable, DataRelation, DataRow, DataColumn, - DataColumnCollection, DataRowCollection, and others need more work. There are - many classes that are just stubs and need to be implemented. - -

XML support in System.Data needs work. This involves working on - the classes: DataSet, XmlDataDocument, and the method ExecuteXmlReader() that - exists in a provider's class that implements IDbCommand, and others. - Stuart Caborn has started the XML support in a DataSet. Tim Coleman started - XML support in the ExecuteXmlReader() in a SqlCommand. Ville Palo has been - heavily modifying DataSet, XmlDataDocument, and other classes for reading - and writing XML. +

Mono has many ADO.NET Data Providers to get you connected: + +

+ +

External Projects that have created ADO.NET Providers that work on Mono: + +

+ +** Tools + +

Some tools that can be used for ADO.NET and other technologies (ASP.NET, XML, etc). + +

+ +** Extra Classes in Mono ADO.NET + +

An ADO.NET Provider Factory + was created by Brian Ritchie. The + Provider Factory is a way to dynamically create + connections, commands, parameters, and data adapters based on configuration + information. -

ADO.NET Provider Factory has been started by Brian Ritchie. The - Provider Factory is way to dynamically create - connections, commands, parameters, and data adapters based on configuration information. The - provider factory also provides utility functions needed by a lot of - providers but are not exposed via the provider. The ProviderFactory - is found at mcs/class/Mono.Data and includes a test named test.cs for it in - mcs/class/Mono.Data/Test. Also, take a look at the sample .config file for the - test.exe application named test.exe.config. The .config file is automatically - read when you use the Mono.Data.ProviderFactory or Mono.Data.DataTools. - -

Integration with ASP.NET has been started, such as, data binding of - a DataTable in a DataSet to a System.Web.UI.WebControls.DataGrid. This may - involve implementing or fixing many classes - in System.Web and System.Data. If you want to help, - contact Gonzalo Paniagua Javier. Here is information about using ADO.NET in ASP.NET: +** Database Access from ASP.NET

- -

Integration with Windows.Forms has not been started, such as, data binding - to a System.Windows.Forms.DataGrid. This may involve implementing many classes - in System.Windows.Forms and System.Data. - -

Integration with GTK# - has not been 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#. - -

Integration with QT# has not been started. Any information on - how this can be done is appreciated. Adam Treat would be the best - person to ask about QT#. - -

Building System.Data - -

The System.Data.dll gets built with the rest of the class library. - To compile the System.Data.dll assembly separately, you need: - - On Unix - -

- On Windows - - - -* Testing +** Testing +