Incomplete version of Newtonsoft.Json installed

[sandboek Profile]

The installation of Helicon Ape results in an assembly "Newtonsoft.Json, Version=6.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed" being installed in the GAC. As it turns out, this particular assembly of "Newtonsoft.Json.dll" appears to be an altered version of the original. Certain convertors (EntityKeyMemberConverter and ExpandoObjectConverter) are in fact missing from this assembly. Websites deployed with the original Newtonsoft.Json.dll in their local bin folder are now overruled by the altered version installed in the GAC. This has severe consequences.

A good example is Umbraco 7 which also uses Newtonsoft.Json, Version=6.0.0.0. If deployed on a hosting environment which has Helicon Ape installed, signing in to the back-office is rendered impossible (see also http://issues.umbraco.org/issue/U4-4509). Hence, this is a major issue. In order to solve this, Helicon Ape might need to consider using the original Newtonsoft.Json instead of the altered version.

[matthiasbier Profile]

I can only agree to this. My hosting provider installed Helicon Ape globally and now My Umbraco is nearly impossible to use.
It took me days of work - now at least somebody found the cause of the troubles!

[Anton]

Hello,

Please try using the following piece in web.config:

<dependentAssembly>
<assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" />
<bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0"/>
</dependentAssembly>

[sandboek Profile]

Anton,

The assembly redirect you mentioned is already present in the Umbraco 7 web.config. It's not going to work because both Umbraco and Helicon Ape use a Newtonsoft.Json assembly in the Version 6.0 range. If the GAC version is the same or higher, the assembly in the local bin folder gets ignored.

When Newtonsoft.Json version 7.0 is released, then we should be able to resolve this issue using the assembly redirect.

[sandboek Profile]

Here's some additional information concerning version numbering for Newtonsoft.Json: http://james.newtonking.com/archive/201 ... on-numbers

There's a distinction between assembly version and release number. The latest release of Newtonsoft.Json is 6.0.6. Helicon Ape uses an altered version of release 6.0.3 However, the assembly version remains 6.0 for both releases. So adding release 6.0.6 to the local bin folder combined with an assembly redirect in the web.config is not going to overrule Helicon Ape's altered version of Newtonsoft.Json release 6.0.3 which runs in the Global Assembly Cache.

[matthiasbier Profile]

Would it hurt Helicoon Ape if we just install the original version of the dll (release 6.0.3) in the GAC? We should be able to just overwrite the dll, right?
This would be the easiest work-around (beside uninstalling Helicon Ape).

[Yaroslav]

Hello!

Sorry for delay. Please try to download and upgrade to Helicon Ape build 145 that is now available: https://www.helicontech.com/ape/download.html
This build now uses different version of Json dll that will not interfere with your projects.

[sandboek Profile]

Thanks for the swift response to solve this issue! My hosting provider already installed build 145 and my Umbraco 7 back-end is up & running again. Job well done Helicon Ape!