Ticket #86 (closed defect: fixed)

Opened 9 months ago

Last modified 9 months ago

Fix log4net dependency to not break DNOA when a different version of log4net is present

Reported by: http://blog.nerdbank.net/ Owned by: http://blog.nerdbank.net/
Priority: major Milestone: v3.0.3
Component: general Version: v2.5.3.9044
Keywords: rp op c sp Cc:

Description (last modified by http://blog.nerdbank.net/) (diff)

From ".NET Master"'s comment on  http://blog.nerdbank.net:
Unfortunately, you have bound the dll to the log4net version 1.2.10 signed dll, so your dll will not run on any site which uses a different version, or a custom build, of log4net. This make it unusable for a large percentage of websites.

Can you please releases a version of the dll which will run with ANY version of log4net, or remove the log4net dependency entirely.

Thank you.

Change History

Changed 9 months ago by http://blog.nerdbank.net/

  • status changed from new to accepted
  • version changed from v3.1.0 to v2.5.4.9045
  • component changed from Discovery to general
  • description modified (diff)
  • milestone set to v3.0.3

Changed 9 months ago by http://blog.nerdbank.net/

  • keywords rp op c sp added
  • status changed from accepted to closed
  • version changed from v2.5.4.9045 to v2.5.3.9044
  • resolution set to fixed

There's an  MSDN article on assembly binding redirects that seems to apply here, but in my tests it didn't solve the problem.

So instead my approach is to quietly switch to .NET tracing or no tracing at all rather than crash if an unexpected log4net.dll version is found.

v2.5 206368ccf
v3.0 a80dbea52

Note: See TracTickets for help on using tickets.