That's strange. The bug fix does not change the logging at all - it's been that way from previous version. Sounds more like a log configuration issue to me. How does your Episerverlog.config look like?

EPiServerLog.config looks normal to me:

<?xml version="1.0" encoding="utf-8"?>
<log4net>
    <appender name="errorFileLogAppender" type="log4net.Appender.RollingFileAppender" >
        <!-- Consider moving the log files to a location outside the web application -->
        <file value="App_Data\EPiServerErrors.log" />
        <encoding value="utf-8" />
        <staticLogFileName value="true"/>
        <datePattern value=".yyyyMMdd.'log'" />
        <rollingStyle value="Date" />
        <threshold value="Error" />
        <lockingModel type="log4net.Appender.FileAppender+MinimalLock" />
        <appendToFile value="true" />
        <layout type="log4net.Layout.PatternLayout">
            <conversionPattern value="%date [%thread] %level %logger: %message%n" />
        </layout>
    </appender>
    <appender name="outputDebugStringAppender" type="log4net.Appender.OutputDebugStringAppender" >
        <layout type="log4net.Layout.PatternLayout">
            <conversionPattern value="[%thread] %level %logger: %message%n" />
        </layout>
    </appender>
 
    <!-- Reduce amount of debug logging -->
    <logger name="EPiServer.Core.OptimisticCache" additivity="false">
        <level value="Error" />
    </logger>
    <logger name="EPiServer.Core.ContentProvider" additivity="false">
        <level value="Error" />
    </logger>
    <logger name="EPiServer.Data.Dynamic.Providers.DbDataStoreProvider" additivity="false">
        <level value="Error" />
    </logger>
    <logger name="EPiServer.Data.Providers.SqlDatabaseHandler" additivity="false">
        <level value="Error" />
    </logger>
    <logger name="EPiServer.Data.Providers.ConnectionContext" additivity="false">
        <level value="Error" />
    </logger>
 
    <root>
        <!--Be careful, setting this value to All, Debug or Info will affect performance.-->
        <level value="Error" />
 
        <!--Enabled file logging-->
        <appender-ref ref="errorFileLogAppender" />
 
        <!-- Use DebugView (Microsoft/SysInternals) and enable Capture Win32 + Capture Global Win32 (http://technet.microsoft.com/en-us/sysinternals/bb896647). -->
        <!--appender-ref ref="outputDebugStringAppender" /-->
    </root>
</log4net>

There is no other use of that package that I'm aware of.  What version of that pacakge is supported?  I just tried downgrading to 1.1.2 and am getting the same error when it tries to load ILogValues from that version.

So, my issues do appear to be due to a newer version of that package than what the Epi DLLs are expecting.  However, shouldn't the Epi nuget package dependencies prevent me from installing too new of a version of a given package?

For example, I had v2.0.0 of Microsoft.Extensions.Logging.Abstractions installed, and that version does indeed not contain a definition for ILogValues, which explains the errors I was seeing.  By manually downgrading that pacakge and decompiling, I learned that v1.0.0 does not contain ILogValues either.  Some searching on github revealed that ILogValues did exist at some point, so I went even further back than v1.0.0.  After clicking "include prerelease" for nuget, I tried v1.0.0-rc2, and then eventually v1.0.0-rc1 where I finally found a DLL that contains ILogValues.  So, not only does the latest major version of Microsoft.Extensions.Logging.Abstractions (v2.0.0) break things, so does the initial release (v1.0.0).  You need to go all the way back to the first release candidate -- this does not seem very intuitive, and as far as I can tell, is not documented anywhere.

On a related note, in my log, I have several similar type load errors coming from Epi Forms, which I'm guessing are similar issues to what I experienced with Microsoft.Extensions.Logging.Abstractions.

Is there a reason that Epi's nuget pacakge dependencies are not set up in a way that they prevent installing incompatible versions?  Is there a way to prevent inadvertently upgrading to an incompatible version?

Edit:  It looks like some of these issues are because the Microsoft pacakages have poorly defined dependencies.  This github issue sheds a little light on things.  It definitely doesn't look like I'm the only one that has wasted time on this either.  I'm thikning whatever changes happened in v10.1.1 of Episerver.Find.Commerce just made the issue more apparent.