2

I am writing an extension (dll) for a 3rd party program. The main program is using log4net version 1.2.10. I want to use LinqToExcel to read Excel files, which also depends on a newer version of log4net.

When I use the log4net.dll from the main executable I get an System.BadImageFormatException when using the extension.

When I replace the log4net.dll with the newer version from LinqToExcel I get an System.NullReferenceException from the main program.

Is there a way to get this to work, or do I have to use an other way to read Excel files?

WORKAROUND: I did remove all logging from LinqToExcel and did rebuild it without the log4net reference.

Fabian S.
  • 909
  • 6
  • 20

2 Answers2

1

source of log4net Source of LinqToExcel

I suggest you debug with the dll to find the problem. If you don't have interest to find the problem, I suggest you to use ADO.net to get data from excel file, it just like read data from database

FrankX
  • 167
  • 1
  • 7
1

If you have ownership over the main program, you can update the log4net version 1.2.10 with the one your other dependent assembly uses (if that's newer). Theoretically, log4net should be backward compliant. Though I see that the latest LinqToExcel release 1.10.1 uses older versions of log4net than your main app, specifically 1.2.9 for the release and 1.2.1.40796 for NuGet.

Since your main app uses a newer assembly and don't wish to modify LinqToExcel, you could wrap the reference to log4net 1.2.10 into an ILMerge-d assembly. Conversely, you could have your own LinqToExcel build that uses only log4net 1.2.10.

andrei.ciprian
  • 2,895
  • 1
  • 19
  • 29