Compatibility with Plant an App version 1.23+

[schotman]

When installing both Plant an App and 2sxc we end up having .dll version issues.

This crashes the DNN installation.

We would like to propose the following changes to the bindings 2sxc is currently adding:

change the binding redirect from: 
<bindingRedirect oldVersion="0.0.0.0-32767.32767.32767.32767" newVersion="2.1.1.0" />
to: <bindingRedirect oldVersion="0.0.0.0-2.1.1.0" newVersion="2.1.1.0" />

It concerns the following DLLs:

<dependentAssembly xmlns="urn:schemas-microsoft-com:asm.v1">
	<assemblyIdentity name="Microsoft.EntityFrameworkCore.Abstractions" publicKeyToken="adb9793829ddae60" />
	<bindingRedirect oldVersion="0.0.0.0-2.1.1.0" newVersion="2.1.1.0" />
</dependentAssembly>

<dependentAssembly xmlns="urn:schemas-microsoft-com:asm.v1">
	<assemblyIdentity name="Microsoft.EntityFrameworkCore" publicKeyToken="adb9793829ddae60" />
	<bindingRedirect oldVersion="0.0.0.0-2.1.1.0" newVersion="2.1.1.0" />
</dependentAssembly>

<dependentAssembly xmlns="urn:schemas-microsoft-com:asm.v1">
	<assemblyIdentity name="Microsoft.EntityFrameworkCore.Relational" publicKeyToken="adb9793829ddae60" />
	<bindingRedirect oldVersion="0.0.0.0-2.1.1.0" newVersion="2.1.1.0" />
</dependentAssembly>

<dependentAssembly xmlns="urn:schemas-microsoft-com:asm.v1">
	<assemblyIdentity name="Microsoft.EntityFrameworkCore.SqlServer" publicKeyToken="adb9793829ddae60" />
	<bindingRedirect oldVersion="0.0.0.0-2.1.1.0" newVersion="2.1.1.0" />
</dependentAssembly>

<dependentAssembly xmlns="urn:schemas-microsoft-com:asm.v1">
	<assemblyIdentity name="Microsoft.Extensions.Caching.Abstractions" publicKeyToken="adb9793829ddae60" />
	<bindingRedirect oldVersion="0.0.0.0-2.1.1.0" newVersion="2.1.1.0" />
</dependentAssembly>

<dependentAssembly xmlns="urn:schemas-microsoft-com:asm.v1">
	<assemblyIdentity name="Microsoft.Extensions.Caching.Memory" publicKeyToken="adb9793829ddae60" />
	<bindingRedirect oldVersion="0.0.0.0-2.1.1.0" newVersion="2.1.1.0" />
</dependentAssembly>

<dependentAssembly xmlns="urn:schemas-microsoft-com:asm.v1">
	<assemblyIdentity name="Microsoft.Extensions.Configuration.Binder" publicKeyToken="adb9793829ddae60" />
	<bindingRedirect oldVersion="0.0.0.0-2.1.1.0" newVersion="2.1.1.0" />
</dependentAssembly>

<dependentAssembly xmlns="urn:schemas-microsoft-com:asm.v1">
	<assemblyIdentity name="Microsoft.Extensions.Configuration" publicKeyToken="adb9793829ddae60" />
	<bindingRedirect oldVersion="0.0.0.0-2.1.1.0" newVersion="2.1.1.0" />
</dependentAssembly>

<dependentAssembly xmlns="urn:schemas-microsoft-com:asm.v1">
	<assemblyIdentity name="Microsoft.Extensions.Logging" publicKeyToken="adb9793829ddae60" />
	<bindingRedirect oldVersion="0.0.0.0-2.1.1.0" newVersion="2.1.1.0" />
</dependentAssembly>

<dependentAssembly xmlns="urn:schemas-microsoft-com:asm.v1">
	<assemblyIdentity name="Microsoft.Extensions.Options" publicKeyToken="adb9793829ddae60" />
	<bindingRedirect oldVersion="0.0.0.0-2.1.1.0" newVersion="2.1.1.0" />
</dependentAssembly>

[iJungleboy]

@tvatavuk I believe you had already looked into this a while ago, and there were some reasons why this wasn't feasible - but I'm not sure about the details. Could you add your findings here?

[schotman]

Any news on this issue? An update would be appreciated ;)

[Tychodewaard]

@schotman I think this issue is resolved?

[schotman]

@Tychodewaard not to my knowledge

[iJungleboy]

Brief summary

It concerns changes to the web.config which a pro can apply himself. The problem is that doing this automatically requires a major change how 2sxc is installed, because the standard DNN installation cannot apply the changes reliably in all scenarios (new-install, upgrade, etc.)

So to do this automatically would require a lot of work and testing - 3-5 days, which is not on our priorities unless someone sponsors it.

[iJungleboy]

This is a very old task, and I believe it's not relevant any more, so I'll close it.