Upgrading to 9.43.1 fails related to System.Web.Helpers

I’m submitting a bug report about upgrading/general.

Current behavior When I upgrade a DNN 9.2.2 or 9.3.x with 2sxc 9.4x+ to 9.43.1 specifically, I soon get errors related to System.Web.Helpers.

In one case I got the classic, “DNN Error, Return to Site” and this was the URL (note the “AntiForgery” https://staging123.accuraty.ws/Default.aspx?tabid=59&error=The+type+initializer+for+‘System.Web.Helpers.AntiForgery’+threw+an+exception.&content=0

Other times I get an IIS Error 500

Then when I get on the server (local) I get a detailed IIS/.NET error explaining that System.Web.Helpers has a method being requested but if found the wrong version of the DLL in the bin (paraphrasing since I didn’t save that one, sorry).

ALSO NOTE THIS IS EASY TO FIX by just adding the following to web.config:

  <runtime>
<!-- other stuff -->
      <dependentAssembly>
        <assemblyIdentity name="System.Web.Helpers" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="1.0.0.0-3.0.0.0" newVersion="3.0.0.0" />
      </dependentAssembly>

In each case it was not there at all until I added it.

Expected behavior Upgrade should just work.

Minimal reproduction of the problem with instructions I think I covered this well above.

Windows Server 2016/IIS, all patches and updates, latest .NET but no install of .NET Core anything

2sxc version(s): 9.2+ upgrading to 9.43.1 Browser: all but probably not relevant DNN: 9.2+ and 9.3+ Language: any

[iJungleboy]

Found out that this is a DNN bug! See https://github.com/dnnsoftware/Dnn.Platform/issues/2971 It only happens if a DNN is updated from a 7 or 8.0.x. Otherwise this never happens.

[jeremy-farrance]

Oh, and again, easily fixed with the web.config addition mentioned above (bindingRedirect).