Package Creator can't build packages with new SharpZipLib about c1-cms-foundation HOT 4 CLOSED

This can be fixed by adding a assemblyBinding redirect in web.config... should prop. be done by the PackageCreator package upon install

<runtime>
  <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
    <dependentAssembly>
      <assemblyIdentity name="ICSharpCode.SharpZipLib" publicKeyToken="1b03e6acf1164f73" culture="neutral" />
      <bindingRedirect oldVersion="0.0.0.0-0.86.0.518" newVersion="0.86.0.518" />
    </dependentAssembly>
  </assemblyBinding>
</runtime>

from c1-cms-foundation.

I'm thinking of update PackageCreator, so it uses build in .net library classes for zip generation, to remove the dependency completely. In the core, it may have sense to reference the old version, or add a binding so we won't have any compatibility issues with existing solutions. And in future - to also remove the dependency as well.

from c1-cms-foundation.

@napernik should be enough to add the assemblyBinding in your out-of-the-box web.config... should resolve any any compatibility issues with existing solutions.

And maybe do the same for Razor and WebPages dlls.

from c1-cms-foundation.

Verified with:

• C1: 5.0.5795.21979
• Package: 3.6.3

from c1-cms-foundation.