Yes, this is my question. The solution I found was to use
System.Reflection.Assembly.LoadFile(fullPath)
Kind regards,
Joe
Am 30.04.2018 um 04:58 schrieb Denis Akhiyarov:
I presume this is your question with an open bounty on it?
https://stackoverflow.com/questions/49942487/python-for-net-how-to-explicitly-create-instances-of-c-sharp-classes-using-dif
On Tue, Apr 24, 2018 at 7:04 AM, Joe <solar...@posteo.org
<mailto:solar...@posteo.org>> wrote:
Hello,
I found a rather old thread (2003) that describes how multiple
versions of a
DLL can be used.
It states
Things get a lot more complicated if you need to load more than one
version of a particular assembly (or more likely, you have a
dependency
on some library the does so). In this case, the names you access via
the CLR modules will always come from the first version of the
assembly loaded (which will always win in the internals of the
runtime).
(https://mail.python.org/pipermail/pythondotnet/2003-October/000010.html
<https://mail.python.org/pipermail/pythondotnet/2003-October/000010.html>)
Is this still correct or are there more convenient methods to do this?
Kind regards,
Joe
_________________________________________________
Python.NET mailing list - PythonDotNet@python.org
<mailto:PythonDotNet@python.org>
https://mail.python.org/mailman/listinfo/pythondotnet
<https://mail.python.org/mailman/listinfo/pythondotnet>
_________________________________________________
Python.NET mailing list - PythonDotNet@python.org
https://mail.python.org/mailman/listinfo/pythondotnet
_________________________________________________
Python.NET mailing list - PythonDotNet@python.org
https://mail.python.org/mailman/listinfo/pythondotnet
