Yes, you’ll have to recompile the DLL for 64-bit. Your only other option is to switch to a 32-bit JVM, or otherwise get some 32-bit process to load the DLL on your behalf and communicate with that process somehow.
Once you’ve embedded the third-party assembly as a resource, add code to subscribe to the AppDomain.AssemblyResolve event of the current domain during application start-up. This event fires whenever the Fusion sub-system of the CLR fails to locate an assembly according to the probing (policies) in effect. In the event handler for AppDomain.AssemblyResolve, load the resource … Read more
This happens because Oracle dropped support for Windows XP (which doesn’t have RegDeleteKeyExA used by the installer in its ADVAPI32.DLL by the way) as described in http://mail.openjdk.java.net/pipermail/openjfx-dev/2013-July/009005.html. Yet while the official support for XP has ended, the Java binaries are still (as of Java 8u20 EA b05 at least) XP-compatible – only the installer isn’t… … Read more
Exporting from a DLL is platform-specific. You will have to fix this for Windows (basically use declspec(dllexport/dllimport) on the instantiated class template) and encapsulate the required code in your Windows-specific preprocessor macro. My experience is that exporting STL classes from DLLs on Windows is fraught with pain, generally I try to design the interface such … Read more
EncodeAndSend is not a static function, which means it can be called on an instance of the class CPMSifDlg. You cannot write this: CPMSifDlg::EncodeAndSend(/*…*/); //wrong – EncodeAndSend is not static It should rather be called as: CPMSifDlg dlg; //create instance, assuming it has default constructor! dlg.EncodeAndSend(/*…*/); //correct
try running path\to\VC\bin\vcvars32.bat from within your current shell first. This should ensure your command-line setup will match the IDE-setup. This is not a permanent fix — you need to do it every time you launch a new shell. You could probably also find some way to add everything that’s in that .bat permanently to the … Read more
Make sure the project type is WPF User Control Library when you create your project. If it isn’t then no sweat, just edit the csproj file and make sure the <ProjectTypeGuids> element under Project/PropertyGroup contain the following GUIDs <ProjectTypeGuids>{60dc8134-eba5-43b8-bcc9-bb4bc16c2548};{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}</ProjectTypeGuids> Also, make sure you reference PresentationFramework and System.Xaml in your project, or you will not get … Read more
They contain the comments for the code in xml format. They can be used with sandcastle to generate windows help files or MSDN-style html documents.
When you touch a member in your class from the client, you need to provide a DLL-interface. A DLL-interface means, that the compiler creates the function in the DLL itself and makes it importable. Because the compiler doesn’t know which methods are used by the clients of a DLL_EXPORTED class it must enforce that all … Read more
Keep in mind one thing before you read further: My answer is coming from the point of view of writing portable code that can be used in applications made up of modules compiled under different compilers. This can include different versions or even different patch levels of the same compiler. How can I use stl-classes … Read more