AngleSharp dependency issue in .NET Framework (IIS-hosted WCF service) about htmlsanitizer HOT 9 CLOSED

I think you'll need a binding redirect. AngleSharp.Css 0.17.0 references AngleSharp 0.17.0 while the latest HtmlSanitizer references AngleSharp 0.17.1. In .NET Framework 4.5.1 and later binding redirects should be created automatically.

See https://learn.microsoft.com/en-us/dotnet/framework/configure-apps/redirect-assembly-versions
and https://learn.microsoft.com/en-us/dotnet/framework/configure-apps/how-to-enable-and-disable-automatic-binding-redirection#enable-automatic-binding-redirects-in-web-apps

When you create a net48 desktop application, the following gets automatically added to the App.config when adding the HtmlSanitizer NuGet package:

<configuration>
  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="AngleSharp" publicKeyToken="e83494dcdc6d31ea" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-0.17.1.0" newVersion="0.17.1.0" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>
</configuration>

from htmlsanitizer.

Looks like App.config of the WCF service project does indeed have an (automatically added) binding redirect for AngleSharp, but the Web.config of the website hosting the WCF service does not.

Copying over the binding redirect from App.config to Web.config solves the issue.

Thanks for your time.

from htmlsanitizer.

Have you checked for #528 (comment)?

from htmlsanitizer.

Yes. As mentioned above I tried your suggestion from #528 , but it didn't work.

from htmlsanitizer.

I meant the binding redirect fix that worked for @Chmielinski.

from htmlsanitizer.

Not sure I follow...

@Chmielinski mentions the issue being caused by an out-of-date binding redirect for AngleSharp.
I assume he simply removed the binding redirect and cleared his build folders to fix the issue.

My project does not have any binding redirect, and until last week I had no dependency on HtmlSanitizer, AngleSharp or AngleSharp.Css.

from htmlsanitizer.

Perhaps you can try Fuslogvw to debug the issue.

from htmlsanitizer.

AngleSharp, Version=0.17.0.0, Culture=neutral, PublicKeyToken=e83494dcdc6d31ea.HTM.txt
AngleSharp, Version=0.17.1.0, Culture=neutral, PublicKeyToken=e83494dcdc6d31ea.HTM.txt

Looks like the root issue is in (the .NET framework build of) AngleSharp.CSS.

from htmlsanitizer.