[CLOSED] Can Ext.NET 1.x support newer Json.NET?

[anup]

Hi,

Is it possible for Ext.NET 1.x to support a more up to date version of Json.NET?

The reason I ask is we would like to introduce Web API into our current project. When you do that, Visual Studio automatically brings in various dependencies including Json.NET. This ends up overriding the reference to the version that is used by Ext.NET 1.x, but when you compile you get an error similar to this:

Error 2 Assembly '<Your Project>' uses 'Newtonsoft.Json, Version=6.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' which has a higher version than referenced assembly 'Newtonsoft.Json, Version=4.5.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' d:\Projects\Sonetto\bin\Sonetto.dll Sonetto.Test

Ext.NET 1.x references Json.NET 4.5.

I have no idea if it is a major effort to support Json.NET 6???

Thanks!

[anup]

Sorry. Ignore. It seems to work.

I removed the reference to the original Json.NET manually from the project and then added the Web API controller, which brought in the later Json.NET and it seems to compile and run...

[anup]

Just a quick update (and reminder for myself!)

While removing the Json.NET version that came with Ext.NET 1 worked, unit test projects I had failed (we had some code loading assemblies for a given domain which failed to find the version of Json.NET that Ext.NET was expecting).

Turned out in the unit test project, we just needed the same assembly redirect that was added (by VS or NuGet I think) to the main projects:

    <runtime>
        <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
            <dependentAssembly>
                <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" />
                <bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0" />
            </dependentAssembly>
        </assemblyBinding>
    </runtime>

That works for us (our over-sized solution with thousands of unit tests etc all continue to work. I don't know if that is officially supported for Ext.NET 1, but while I use a fair few features of Ext.NET I am sure there is a LOT I do not use :))

[Daniil]

Anup, thank you for the question and sharing all the additional information.

We are glad that you were able to sort it out.

As for upgrading Json.NET in v1, we are probably not going to do that. It doesn't worth enough comparing a chance to introduce some breaking change or bug and efforts that would be required to test out everything.

If you have any other thoughts or information that might change our mind, please feel free to share.

[anup]

Hi,

Sorry for the delayed reply (been away!).

What you say is fair enough. For our usages so far it seems to be working, but of course I am not using every single bit, so your caution makes sense.

Thanks!
Anup