Thanks Bill,
I will update that information to say it requires mojoPortal 2.3.9.4, sorry for any inconvenience.
Sorry for the inconvenience. I was worried about breaking other people's custom code by updating to the new log4net because I thought it might require everyone to re-compile their custom features against the new log4net dll, but I was able to prevent that problem by adding this in the Web.config in 2.3.9.4:
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="System.Web.Mvc" publicKeyToken="31bf3856ad364e35" />
<bindingRedirect oldVersion="1.0.0.0-2.0.0.0" newVersion="3.0.0.0" />
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="log4net"
publicKeyToken="1b44e1d426115821" />
<bindingRedirect oldVersion="1.2.10.0"
newVersion="1.2.11.0" />
</dependentAssembly>
</assemblyBinding>
</runtime>
though it still would be best for anyone using custom code that also uses log4net to re-reference it and re-compile when they get a chance.
Best,
Joe