ODP Object's Non CLR Compliant as parameters in C#
379394Mar 19 2003 — edited Mar 26 2003I am converting a Data Access Building Block to use ODP.NET as a provider option (It currently works in VB.NET for SQLClient, ODBC.NET, OleDb.NET, MS Oracle.NET
and ODP.NET) However, when I converted the all these classes to the C# implementation, the ODP.NET throws a compiler error "Argument type 'Oracle.DataAccesss.Client.OracleConnection' is not CLS compliant. This message is basically repeated for all the ODP.NET objects (OracleCommand,OracleParameter,OracleTransaction,etc..), do you know of any issues with passing ODP.NET objects to other methods in C#? I can Send the Code to anyone who wishes to review it. Basically, I took the Microsoft Data Access Building Block (VB.NET & C# implementations) and expanded them to cover a wide range of providers. Everything is solid except ODP.NET's issue with being CLR compliant, and of course the DeriveParameters function implementation that is missing. But aside from that, it works great in VB.NET, but won't compile in C#.
Any help or suggestions would be greatly appreciated.
Thanks,
Scott