Oracle Managed ODP.NET

Note:This documentation/guide is based on Managed ODP.NET v11.2.0.3.50 Beta

Download Managed ODP.NET from Oracle Technology Network.

Finally Oracle has released a pure .NET based client for connecting and working with Oracle databases from your CLR world without the dependencies lying around in the GC ignorant world. With a reference added to the Oracle.ManagedDataAccess.dll which weighs a mere 6+ MB’s (against 150+ MB’s previously) you are ready to get started with you day-to-day interaction to the 10g R2 or higher Oracle Databases.

[Read More]

Dapper – Micro ORM for Oracle and Microsoft .NET

I have been on the hunt for an easier ORM tool to help with my day-to-day work. Till now the ones I have tested have fallen short of fulling one of criteria: Should work with Oracle Should support multiple REFCURSOR output parameters from Oracle Stored Procedures and OracleDbType’s We use stored procedures exclusively for our CURD operations, so this is the determining requirement and I do not like compromising having an abstract layer which does not support OracleDbType’s just because it has to work with other DB’s [Read More]

Digging into old components through MSIL

Yesterday and today I had to deal with an old component who’s source code has already been ported from .net framework v1.1 to v3.5 (most of them rewritten from scratch). This asp.net based component was working fine till sometime last week and then suddenly started throwing up exceptions. Due to some legacy dependencies the web app had to be run in v1.1 and I do not have VS2003 with me. [Read More]

Connecting to Remote IBM WebSphere MQ Server

The below post will provide a “hello world” kind of introduction to connecting to a remote IBM WebSphere Message Queue server using client application written in C#. Points to note: Server and client should have a common OS login name. The passwords can be different between the server and client, what matters is that the login name should be identical. The login name you have selected to use should be part of the MQM group on the MQ server, or it should be explicitly given permission for querying the Queue manager and the queue. [Read More]