Hello,
Is there a design reason that pythonnet loads C# assemblies into its own AppDomain rather than establishing a separate AppDomain? It would be useful for instance when developing in C# in parallel with writing python code (say, in the ipython REPL) to be able to reload C# assemblies dynamically.
Also, we’ve found it useful in Initialize() to enable shadow copying, to prevent file locking, ie
internal static void Initialize() {
...
AppDomain domain = AppDomain.CurrentDomain;
// prevent file locking
domain.SetShadowCopyFiles();
domain.SetShadowCopyPath(null)
;
Although these are deprecated methods, and really it should be establishing a new AppDomain as above.
Regards,
Adam
______________________________
___ Adam D Klein
BlueMountain Capital Management LLC
280 Park Ave, 5th Floor East
New York, NY 10017
_________________________________________________
Python.NET mailing list - PythonDotNet@python.org
https://mail.python.org/mailman/listinfo/pythondotnet