[Mono-dev] Removing Obsolete Code from Mono 2.8

[Daniel Morgan]

Obsolete Types in .NET 4.0
http://msdn.microsoft.com/en-us/library/ee461503%28VS.100%29.aspx

Here's my 2 cents.

Remove Mono.Data.dll which has been superceded by the provider factory added to System.Data.dll in .NET 2.0.  The Mono.Data.dll assembly has had the Obsolete attributes on it for a long time. 

There are many different versions of the SQLite provider.  However, Mono has a couple of different versions: Mono.Data.SqliteClient which is 1.1 only.  It will not work with NET_2_0 profile unless someone fixes it.  Mono.Data.Sqlite - the 2.0 parts - is based on System.Data.Sqlite.  

Remove Mono.Data.TdsClient since no one uses this.  This assembly is for older Sybase ASE and Microsoft SQL Server databases < version 7.0)

Keep Mono.Data.Tds which is required by System.Data.SqlClient in System.Data assembly and Mono.Data.SybaseClient assembly.

I am okay with old Npgsql, ByteFX, and Firebird being removed.  People should go to the respective project to get the provider.

I am also okay if fxjr adds Npgsql2 to Mono to be distributed with Mono -- only Npgsql2 is maintained in Mono. 

Even though System.Data.OracleClient is considered obsolete in .net 4.0, I think we should keep it for those who need it. 

If no one ones IBM.Data and Mono.Data.SybaseClient, these two can be removed too because they can use System.Data.Obdc to connect to these and other databases.

--- On Mon, 3/1/10, Miguel de Icaza <miguel at novell.com> wrote:

> From: Miguel de Icaza <miguel at novell.com>
> Subject: [Mono-dev] Removing Obsolete Code from Mono 2.8
> To: "mono-devel" <mono-devel-list at lists.ximian.com>
> Date: Monday, March 1, 2010, 1:54 AM
> With the upcoming release of Mono 2.8 we
> are dropping the 1.0 profile as developers moved a long time
> ago to the generics-based 2.0 profile and because it is
> maintenance burden for us.
> 
> In addition to this, I would like to stop distributing
> some libraries that were either never completed and are not
> being actively maintained.   We could move these libraries
> to a separate module if people would like to maintain them
> or keep distributing them.
> 
> Here is what I have in mind:
> 
> * Drop Microsoft.JScript and
> `mjs'
>   Microsoft abandoned JScript, our
> implementation was never complete, and DLR-based solutions
> (all 3 of them) offer better ECMAScript/Javascript
> compatibility.
> 
> * The ByteFX data provider for
> MySQL.
>    It has not been developed since 2004, it is
> released under the LGPL, unlike the MySQL driver which is
> GPL, but nobody has updated the driver.
> 
> * FirebirdSql data provider.
>   The firebird team provides downloads for the
> database from their web site from 2010;   Our provider was
> last updated in 2005.
> 
> = Debatable =
> The Npgsql provider is also maintained
> externally, but the API that we have has been maintained in
> our tree for a while.   In the meantime the upstream
> project broke binary compatibility.   It seems like an
> extra burden in our team to maintain the old APIs that
> upstream developers are breaking.
> 
> Miguel.
>         
> 
> -----Inline Attachment Follows-----
> 
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>