Closed GoogleCodeExporter closed 8 years ago
I have this same issue and it is driving me mad. It looks like I have to change
the log4net version of my whole project.
Original comment by dustin.l...@gmail.com
on 13 Jun 2014 at 10:46
Sorry, I don't have time to make this change myself. But I am happy to accept
pull requests from anybody that does have time to make this change.
Original comment by paulyo...@gmail.com
on 18 Jun 2014 at 9:14
To make it worst, log4net has signed 1.2.11 with two different public key and
linqToExcel picked a different one compared to the one my company uses. So its
either changing all the references in the assemblies in my company or give up
on LinqToExcel or download the source and rebuild linqToExcel.
It's very bad for 3rd party lib to have hard coded version of specific
libraries.
And curses Log4Net having 2 different public keys.
Original comment by laubo...@gmail.com
on 18 Jul 2014 at 4:22
version 1.8.1 now references Log4Net through its NuGet package, so see if this
helps you now.
Original comment by paulyo...@gmail.com
on 28 Jul 2014 at 1:45
Original issue reported on code.google.com by
mikewred...@gmail.com
on 1 May 2014 at 8:11