> > You are missing a binding redirect from that version to whatever the newer >> version is. >> > > Normally I would redirect Extensions 4.2.0.0 to 4.2.0.1, but my assemblies > are loose in a folder being called by Python.NET. >
D'oh! There is a stupidly simple workaround for this. I manually extracted the *exact* DLL versions required from their NuGet packages and placed them in the Python folder. Now all of the loose files down the dependency chain are loaded and work. No binding redirects are needed because the perfectly correct versions are present. Luckily there are no Y-shaped "forked" (what are they called?) dependencies on different versions of the same library. So I have a Python 3.7 script now calling our data analysis library. A bridge across the divide! Although as I said yesterday, I do have to make a Python package that feels perfectly natural to Python coders so they can just load-and-go. I don't have a Pythonic background, so a bit of reading will be required. Oh drats! The interop works with data on the file-system, but when I try to get data from Azure Blobs I get a timeout. A new and completely different problem I think. Cheers, *Greg* P.S. I found two other libraries that also required manual extraction of older versions to bypass the need for redirects: System.Buffers.dll and System.Runtime.CompilerServices.Unsafe.dll.
