X-Git-Url: http://wien.tomnetworks.com/gitweb/?a=blobdiff_plain;f=web%2Fado-net;h=0095d79ef79996374030641fce45c5c8a01272ac;hb=80496539cbb4d78d3cdd2806fe45a75d956f53a4;hp=516c1c74d6e6f61b33feedfc55e39ec3dbfe1583;hpb=ea380d9f671a175f665ecd66e554c51f1f00d0cd;p=mono.git diff --git a/web/ado-net b/web/ado-net index 516c1c74d6e..0095d79ef79 100644 --- a/web/ado-net +++ b/web/ado-net @@ -1,405 +1,198 @@ * ADO.NET - The coordinator for the ADO.NET implementation is - Rodrigo Moya, - with the collaboration of: - Daniel Morgan, - Tim Coleman, - Brian Ritchie, and - Vladimir Vukicevic. - - -* Action plan - - The current plan to implement ADO.NET is as follows: - - Step 1:System.Data.OleDb Provider: - - - - Step 2: System.Data.SqlClient Provider: - - +** Data Access in Mono - Step 3: System.Data.Odbc Provider: + - Step 4: Other ADO.NET providers: +** Bugs and Feature Requests - - - Step 5: Create tools for ADO.NET + -

According to Gonzalo, this is how it could be implemented: - -

After some work done in System.Configuration, you can now do something - like: - -

- 

- // Get an instance of the multiplexor from machine.config file
- // Can be overriden in the application config file	
- object o = ConnectionSettings.GetConfig ("mono.data/multiplexor");
- if (o == null)
-	--- error
-    
- Multiplexor mp = (Multiplexor) o;
-    
- // may be a string [] argument can help passing arguments
- IDbConnection cnc = mp.CreateConnection (providerName);
-    
- and in the machine.config file:
-
-  
-   
-    

-    ....
-   
-   ...
-   
-     
-       
-     
-   
-  
-
- validate="false" tells MultiplexorSectionHandler not to load the Type
- until an instance is required. You can add more attributes or whatever
- inside  as long as MultiplexorSectionHandler parses it.
-
-    public class MultiplexorSectionHandler :
-    IConfigurationSectionHandler
-    {
-        public object Create (object parent, object configContext,
-        XmlNode section)
-        {
-            Multiplexor mp;
-        // Here you get the ChildNodes and set up a Multiplexor
-        // instance that will hold the information needed to create 
-        // instances of each provider. Only one instance will be 
-        // created by the config system.
-            return mp;
-        }
-    }
-
- This way, if our providers works with MS, the user can test them in both
- MS and mono by just adding a few lines to machine.config (i still have
- to upload a default machine.config file for mono). And this is the .NET
- way of doing it (of course, if you prefer, you can use the other config
- file. I just wanted to make people aware of this feature that now works
- on mono).
-
+** ADO.NET Data Providers -

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 - +

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. + +** Database Access from ASP.NET

- On Windows - -