Home/ Questions/Q 4331050
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-21T10:03:06+00:00

I have a very modest application with a single external assembly (log4net.dll) that I

  • 0

I have a very modest application with a single external assembly (log4net.dll) that I wanted to use ILMerge on. I merge the App.exe and the log4net.dll, and the resulting executable (New.exe) appears to work correctly. However, New.exe is no longer logging and it was logging fine before being merged. Bear I mind I copied App.exe.config over before testing New.exe.

I’m not sure what to make of this. Does anybody have any idea why this would happen? Have I mis-used ILMerge.exe some how? Reflector seems to indicate that New.exe is “whole”; I can see the Log4net assembly and everything.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I do not know the internals of log4net, but I suspect it’s looking for the log4net assembly and can’t find it since you merged it into new.exe. A solution to this is to provide the AssemblyResolve event in the AppDomain with a function that remaps log4net.dll to new.exe.

    • 0