I'm working on a C#/.NET 9 project, and want to include an interop bridge for our systems engineers who are only proficient in python.

I found a couple oddities where i was unable to import types after successfully adding references to their respective DLLs.

some of these were bugs on my part (but possibly still noteworthy for this project): when moving a file from one project to another if i neglected to change the namespace, it would fail to import the type (presumably because the type didn't exist within the assembly connoted by the namespace?). fixing the namespaces to the intended ones for their respective assemblies resolved those, but perhaps this is a shortcoming worth noting for the devs here.

i cannot seem to overcome others. the only commonality i can find is that they have nuget package dependencies. i use Silk.NET, MessagePack, and OpenCVSharp4 in the affected projects. it doesn't seem to matter what the package is - any of the projects using any of these causes any imports from this dll to fail. it's also notable i'm able to access the types in python via reflection with Assembly.LoadFile + GetType, so i know they're in the runtime.

is there another step i need to take to work with these sorts of projects or is there a known incompatibility? any suggestions on workarounds? i've used pythonnet in the past and it was an awesome tool, i'd really like to continue to be able to here.