PUN assembly conflict errors for UWP build specifically Hololens 2

Hello

I am working on a project that is being developed on Unity 2018.4.29f1 with Mapbox SDK which is currently compatible with .net scripting backend only and therefore we are using .net scripting backend paired up with PUN 2. (Tried PUN Classic as well)

I am well aware that the unity has ended support for .net scripting backend and have been removed in latest unity version and Photon also advises not to use PUN Classic in new projects but it is the need of the project.

Configuration:

Unity 2018.4.29f1 PUN 2 (v2.40) Scripting backend: .Net API compatibility level: .Net 4x

Problem:

The problem we are facing for about a week now is that unity builds the visual studio solution fine for UWP but when we try to build it for Hololens 2 from visual studio 2017 version 15.9.45 we get photon assembly conflict with .nuget packages.

Errors:

Warning Found conflicts between different versions of "System.Runtime.Extensions" that could not be resolved. These reference conflicts are listed in the build log when log verbosity is set to detailed. Disaster Simu C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets 2110

There was a conflict between "System.Runtime.Extensions, Version=4.0.10.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" and "System.Runtime.Extensions, Version=4.2.1.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a".

1> "System.Runtime.Extensions, Version=4.0.10.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" was chosen because it was primary and "System.Runtime.Extensions, Version=4.2.1.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" was not.

1> References which depend on "System.Runtime.Extensions, Version=4.0.10.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" [C:\Users\Asad Rana.nuget\packages\system.runtime.extensions\4.1.0\ref\netcore50\System.Runtime.Extensions.dll].

Output Build Log: (wouldn't let direct uploading, apparently size is big)

https://drive.google.com/file/d/1mXSeO_OI2z8EoxaYb0R3TtcVY4ANTz5l/view?usp=sharing

Solutions I tried:

1. Tried creating app.config with redirect bindings and side by side assembly loading later to realize that 2. UWP doesn't support app.config. There are some work arounds as well that didn't seem to work for me.

2. Tried passing the conflicting assemblies in project.json so .nuget may download at the time of build.

3. Tried adding reference in visual studio but that didn't seem to work.

What I am looking for:

Some way to load these assemblies side by side or implement redirect bindings for UWP or any solution that would work.