dll

问题 I have a base class ( QIndicator ) and I want to implement derived classes in DLLs. The DLL project in Visual Studio 2012 for a sample derived class has the following code: header file with base class #ifndef _DLL_COMMON_INDICATOR_ #define _DLL_COMMON_INDICATOR_ // define the DLL storage specifier macro #if defined DLL_EXPORT #define DECLDIR __declspec(dllexport) #else #define DECLDIR __declspec(dllimport) #endif class QIndicator { private: int x; int y; }; extern "C" { // declare the factory

问题 I have a simple C DLL that exposes functions from a static library. The DLL compiles without errors and I can run DUMPBIN on it to see the exports. However, when I attempt to load it with DllImport in C#, it says this: System.DllNotFoundException: Unable to load DLL 'ei.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E). It's in the correct directory, for sure. So, I read that it might be a good idea to try Dependency Walker, in case I need to include

问题 I just completed working on a client's tool, which uses Jfreechart jar, and dll and a lib file for JNI interface. Now I would like to export/ provide a executable file to client, I tried to click on java project folder and export Java>Runnable Jar file (extract required libraries into generated JAR) , a Jar file is exported with some Warnings. However, we are not able to run the file on client's machine. How can I fix this, obviously I don't want to provide complete Java project and ask

问题 I am doing a project in which i have to interface a device via USB using MATLAB. The API (dll files) of the device is written in the C++ so i used loadlibrary command in MATLAB to load it and done interfacing. It's working fine. The problem is that when i run the program from MATLAB it works fine but for running it again i need to plug out the device and then plug in to make it run successfully. But i wrote a C++ interface that is working fine. Can anyone tell me what should i do? The problem

问题 Got a strange one and I know it is something silly but I can't see it for anything! I have a DLL created in VB.net (No I can't change it! :-)) and am calling it from C#. The problems come at the point the object is created in C# and I get the message that it has "some invalid arguments". The constructor code in the DLL is as follows: Sub New(ByRef Connection As IConnection) The code in C# is: IConnection conn = new Connection(); CustomObject test = new CustomObject(conn) It is happy with the

问题 I have good knowledge on the working of a "traditional" .dll . Also the differences between dynamic loading and static loading , etc. But I have the following doubts about the working of COM objects, Is it mandatory to register COM objects with regsvr32 ? can I have two versions of a registered COM object lying in the same/different directory? besides being packaged inside a .dll file is there anything in common between a "traditional" .dll and a COM object ? 回答1: 1) No - it is NOT necessary

问题 I have two C# projects, LibraryA and LibraryB, each producing a separate DLL. LibraryA makes use of the classes in LibraryB. LibraryB needs to make a TypeForwardedTo reference to class in LibraryA. (See this question for background.) Normally, I would resolve either issue by adding a project reference, but I can't do both because VS doesn't allow circular references. The only reason I need the B-to-A reference is for the TypeForwardedTo link. I've tried using Type.GetType(string) but the

问题 I have two C# projects, LibraryA and LibraryB, each producing a separate DLL. LibraryA makes use of the classes in LibraryB. LibraryB needs to make a TypeForwardedTo reference to class in LibraryA. (See this question for background.) Normally, I would resolve either issue by adding a project reference, but I can't do both because VS doesn't allow circular references. The only reason I need the B-to-A reference is for the TypeForwardedTo link. I've tried using Type.GetType(string) but the

问题 I asked a question regarding assembly security and someone told me few things: You could invoke a licensing technology when the library was to be instantiated. What I've done in the past is include a public key as a resource to the dll, and then look for a license xml document with a cryptographic signature signed with my private key. As long as I keep close track of my private key, it's pretty difficult to defeat. After reading this I have some questions: How to invoke my licensing

问题 I asked a question regarding assembly security and someone told me few things: You could invoke a licensing technology when the library was to be instantiated. What I've done in the past is include a public key as a resource to the dll, and then look for a license xml document with a cryptographic signature signed with my private key. As long as I keep close track of my private key, it's pretty difficult to defeat. After reading this I have some questions: How to invoke my licensing