Replies: 1 comment
-
Sorry for the waste of time, since the DLL started with System. I made a bad assumption that is part of the framework. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This may be a .NET question, but I thought I would start here. Long story why I need to do what I am calling Xcopy to install. I will try and give some basic context. I have a function that handles the AssemblyReslove. It looks through certain directories till it finds the DLL and then will creates a Reflection.Assembly from that DLL. This works with SqLite (System.Data.SQLite.dll). I now have a need to access MySql. If I install with NuGet it all works. In fact, that is how I get the DLL. Once I have it I put it in a different folder so I can reference it. Then I uninstall the NuGet and manually reference the DLL. There must be more than just the MySqlConnector.dll, because when I resolve the DLL to the correct path, and load it (Reflection.Assembly.LoadFrom("/thepath/MySqlConnector.dll"), keeps trying to resolve the assembly till I blow out the stack. I did notice the NuGet reference in a few other assemblies. I did add those and it did not make a difference. Any thoughts are appreciated, but if this is too far off topic then I understand.
Beta Was this translation helpful? Give feedback.
All reactions