32 or 64 bit version of product: 64-bit
Operating system: Windows 10 1803
32 or 64 bit OS: 64-bit
Powershell studio needs to be able to import different versions of the same assembly via the assemblies feature, as there are times when this is necessary. For example, in order to use the box .net assemblies, both Newtonsoft.json 10.0.0.1 and Newtonsoft.json 9.0.1 are needed in order for it to work. The reason is best described by a box employee I spoke to:
This being the case, it would be awesome if powershell studio would allow this functionality when selecting assemblies to import.the Box SDK depends on Newtonsoft.Json 10 but the System.IdentityModel.Tokens.Jwt library we use depends on 9. A full .NET project respects the SDK's app.config file that does a binding redirect to reconcile these dependencies, but if you're loading assemblies manually in PowerShell you're probably not picking that config up and the IdentityModel library is not able to resolve it's dependency on Newtonsoft.Json 9.