Could not load file or assembly log4net version 1.2 0.30714

Add a Solution. Top Rated Most Recent. Accept Solution Reject Solution. Make sure that log4net. Posted Jun pm Mehdi Gholam. Madhav Gunjal 2-Jan am. Mehdi Gholam 2-Jan am. Just copy the file beside your exe on the production machine. Posted Jun am Kasun Madhupa Udawaththa. Check whether the log4net.

Posted Jun am Nirav Prabtani. Check weather your Bin folder contains the log4net dll referenced. IF it is referenced then check the config file and make sure XML. In all the source code, it only refers to the assembly without a version, but the log indicates that there's a "fully specified" version with the old version number somewhere that it's looking to find. Where is that specified? I've tried both fully specifying the assembly with culture, version, and publickeytoken see original message and not specifying them.

I've also attempted fully specifying it and checking the right assembly into the GAC. Unfortunately, it still wants to look for the older versiojn as shown in the assembly bind trace. I've grepped my website directory in its entirety and can find no instance or reference to the old version--where is the assembly binder looking to get the idea to look for the old version?

If I could change that, I'd be home free. The content you requested has been removed. Ask a question. Search related threads. Remove From My Forums. Answered by:. Archived Forums. Getting Started with ASP. NET question on a topic that's not covered by one of the other more specific forums - ask it here. My general problem is that Common. Log4Net facade is looking for a concrete version of the Log4Net library. That is not a problem if you are not using some other framework which depends on higher version of Log4Net.

So if you are using NuGet, you might obtain the following exception while adding the references:. A similar thing might happen if you just decide to use the latest Log4Net by default.

Then, you might get an exception when initializing Spring. NET context or starting the Quartz. NET scheduler:. One way to get around this is to define runtime assembly binding.

But this solution forces you to add the reference to log4net manually.