search

JamesDriscoll / ELMAH.OracleErrorLog

ELMAH ErrorLog implementation for Oracle
Apache License 2.0
0 stars 1 forks source link

Oracle Managed Driver #3

Open atifaziz opened 6 years ago

atifaziz commented 6 years ago

Forking this issue here from elmah/Elmah#428 and re-quoting the relevant comments.

@paal123 said:

For me it is bit of a problem that the OracleErrorLog is no longer a part of the official Elmh repo and has no nuget package, as my customer, a large multinational company requests me to use official Elmah nuget packages. I can be an official maintainer as we need this for long term usage with Oracle Managed Driver.

@atifaziz said:

@paal123 Thanks for stepping up to volunteer and help maintain OracleErrorLog. While I'll let @JamesDriscoll answer on how he sees the collaboration going forward, I wanted to point out that what's in the ELMAH.OracleErrorLog repo is based on the ELMAH 2.0 code that's currently “alpha”. Is your hope to get the managed version out based on 1.x (which by the way sits in the 1x branch here)?

@paal123 said:

I did make a working version of 1x with Oracle managed driver. My thought was elmah 2.0 nuget with an official OracleErrorLog nuget package in addition.

@atifaziz said:

I did make a working version of 1x with Oracle managed driver.

@paal123 If you have a working version, why not start by sharing this as a repo under your account that we can eventually talk about transferring under the org? If it makes sense, you could fork ELMAH.OracleErrorLog and work your changes on top.

My thought was elmah 2.0 nuget with an official OracleErrorLog nuget package in addition.

It might be best to publish an initial version still based on 1.x as 2.0 is still alpha.

@JamesDriscoll said:

Hi guys,

Sorry for my silence 'til now!

Firstly, I have no issue with the repo sitting under the ELMAH organisation, or any other location. The important thing is to do the correct thing for ELMAH itself.

Second, I think we need to be a little bit careful in how the move to Oracle.ManagedDataAccess is implemented. As far as I'm aware, the Oracle managed client is ONLY available for .NET 4.0 and above. There will be folks out there who are still supporting .NET 3.5 SP1 and below, for which the current OracleErrorLog will be their only option. My initial feeling here is that we should have a brand new OracleManagedErrorLog that takes dependencies on Elmah.Core and Oracle.ManagedDataAccess.

Cheers,

James