Oh just to say, not every function within a .dll uses the same CallingConvention and setting it wrong can imbalance the stack which will result in a none recoverable exception.Quote:
Oh, I had the exact same problem a while ago, go to your dllimport thingy and look for something like this:
[DllImport("nameofdllwithproblem")]
And change it to:
[DllImport("nameofdllwithproblem", CallingConvention = CallingConvention.Cdecl)]
Well I don't know anything about this subject, just re-posting stuff from another thread.Quote:
Oh just to say, not every function within a .dll uses the same CallingConvention and setting it wrong can imbalance the stack which will result in a none recoverable exception.