I have an ActiveX control written in C# and working when run in an ActiveX compatible program (CoDeSys). The problem I\'ve come across is that in order to allow CoDeSys to interact with the ActiveX co
We have a DLL, built with MS Visual Studio 2010, in release mode. We provide this DLL to different customers, along with a .lib file. The functions in the DLL are exported with:
What is my main concern is , I am able to write a C++ dll using VC++ . Now the dll is present in the Debug folder.
We are using an external Dlls as : [DllImport(\"DemoExport.dll\")] public static extern string GetDBConnection(string sDBName);
I want to have multiple instances of a DLLInterface class but as each obje开发者_C百科ct will have pointers to the same DLL functions I want these to be static.
I came across this article on Code Project that talks about using an abstract interface as an alternative to exporting an entire class from a C++ D开发者_StackOverflow中文版LL to avoid name mangling i
I have the following static function: static inline HandVal StdDeck_StdRules_EVAL_N( StdDeck_CardMask cards, int n_cards )
I\'ve got two unmanaged C++ functions, 开发者_StackOverflowCompress and Decompress. The arguments and returns go as followed:
I have a rather big Core project that I\'m working with, I\'m attempting to adapt it to use a DLL Engine I\'ve built, I\'m getting a bunch of errors like:
I have a DLL which contains a class with static members. I use __declspec(dllexport) in order to make use of this class\'s methods. But when I link it to another project and try to compile it, I get \