2sxc assemblies that are shared dependencies with DNN in bin folder should be in bin\2sxc folder if version of dll's is not the same as dnn default version

[tvatavuk]

I'm submitting a ...
[x] feature request

...about
[x] DNN parts

Current behavior
There is issue with DNN upgrade as explained #2684 that can break future DNN upgrades and requires manual workaround by user.

Goal is to upgrade 2sxc installation to avoid this DNN upgrade issues in future.

Plan is that 2sxc installation should deploy and install dll's that are shared with DNN (currently in bin folder) to separate bin\Imageflow folder if version of dll's is not the same as dnn default version. Assembly binding redirection should be limited only to this non default dnn version that is in use by 2sxc only. Installation should also take a care of complications that could follow, when we install 2sxc v13+ to older dnn v7.4.2 (that do not have dependency on this dll's) but newer dnn version after upgrade will deploy this dll's again. 2sxc unit tests should be updated to use shared dlls from dnn.

Expected behavior

Instructions to Reproduce the Problem

Why change the behavior?

Your environment

• 2sxc version(s): 11.X.X
• Browser: [all | Chrome XX | Firefox XX | Edge XX | IE XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari ]
• DNN: [all | 7.4.2 | 8.X.X | 9.X.X ]
• Language: [any/all | English | German | other ]

Anything you would like to add

[iJungleboy]

Related to #2682

[tvatavuk]

DNN websites that have 2sxc v13.00-v13.03, after DNN Upgrade to DNN 9.4+ version will get server error Could not load file or assembly 'Microsoft.Extensions.DependencyInjection.Abstractions' or one of its dependencies.

To prevent this server error please install 2sxc v13.04+ before DNN Upgrade.

With 2sxc v13.04 our goal was to ensure that DNN upgrade do not break DNN installation.

Root cause

Imageflow is included in 2sxc v13+ and have dependency on Microsoft.Extensions.DependencyInjection.dll v2.2.0 (and related deps) and for that reason 2sxc v13.00-v13.03 and indirectly DNN 9.4+ got DI upgrade to v2.2.0 (with assembly binding redirects) that is root cause for server error after DNN upgrade.

What we did

To avoid same issue again (and keep existing functionality) we did the following:

• 2sxc v13.04 have dependency to Microsoft.Extensions.DependencyInjection.dll v2.1.1 (and related), so it is the same as in DNN 9.4+ install and upgrade versions to ensure that 2sxc DI directly depends on DNN DI.
• 2sxc v13.04 deploys Microsoft.Extensions.DependencyInjection.dll v2.1.1 (and related) to DNN bin folder to enable DI also in DNN 7.4.2+ (minimal DNN version for 2sxc).
• Imageflow still have dependency to Microsoft.Extensions.DependencyInjection.dll v2.2.0 but that version is in bin/Imageflow subfolder, so it will not overwrite and upgrade DNN DI dlls. Also assembly binding redirect for only this specific version are added to web.config so Imageflow can find right version of its deps.

What we tested

Various clean install and upgrade scenarios are tested with DNN 7.4.2; 9.4.4; 9:10.1; 9.10.2 and 2sxc 12.10 LTS; 13.03; 13.04 to confirm that fix solution works as intended.

[jeremy-farrance]

I just wanted to insure that you saw this and had an opportunity to follow or chime in if needed.

Updates to the Microsoft.DependencyInjection.* Libraries #5058

[iJungleboy]

@jeremy-farrance thanks. We just discussed this on our bi-weekly meeting and just everybody agreed this would be important