I know there is a way to call c++ DLL from Chromium based App is DLL binding.
I want to know if I can call c++ DLL via the way of webassembly?
Related
Using Registration-free WinRT it is possible to load WinRT components inside Win32 application.
What's the process to load WinRT component from inside Win32 dll? I tried the steps mentioned as part of Win32, but winmd files are not generating the corresponding header files.
Main usage scenario is dll can be loaded any application, like electron node addon or c# app etc.,
Without any changes to application, dll by itself should be able to consume WinRT component!
Did you add a reference to the WinMD file in the vcxproj and then installed the C++/WinRT NuGet package? This should make it generate the corresponding header files that your DLL project can then consume.
Following is the solution:
Was able to fix this in weird manner i.e. not a standard way to solve this.
Our use case was to use FFmpegInteropX inside win32 dll, so that we can use ffmpeg as a source reader and use the underlying hardware decode support. Mechanism is discussed detailly in the following link:
https://github.com/ffmpeginteropx/FFmpegInteropX/discussions/275#discussioncomment-3091100
Following changes were done to use WinRT component inside a Win32 dll:
Copied the WinRT generated files from the application to Win32 dll project
Before invoking any of the api from the generated runtime class, did LoadLibrary of the specific WinRT component into the dll
Now the make the necessary WinRT component call as it was done in standard win32 application
All modules were working as expected.
Above solution was copied from:
https://learn.microsoft.com/en-us/answers/questions/924996/how-to-consume-winrt-component-inside-win32-dll-pr.html
It's not a straight forward solution, also not sure if MS has any plans to add support for WinRT component inside dll project, if such support comes up then this may not be needed.
I use a CAN communication driver DLL for windows, which I call/import from C++, and I was wondering if there was a way to wrap the DLL and call it directly from Elixir, or maybe Erlang.
I have created a DLL that are using VCL components in its code. The DLL is hiding all C++ code behind a C API.
Using the DLL works fine in a console application.
However, when trying to use it in a regular VCL forms application, I get errors when any code is trying to view VCL frames or forms, e.g.
I suspect this has todo with linking in the VCL into the DLL.
Question is, do one have to prepare the creation of a DLL using VCL components in some way to avoid this problem? I think it has todo with HINSTANCE somehow?
The reason for creating the DLL in the first place, is to be able to provide a pure C API, so that the code can be used with other compilers, e.g. Visual studio. I would use a package otherwise.
Team,
The following code returns empty/null to myobj, in my classic ASP page while trying to invoke a dll component.
Set myobj = Server.CreateObject("MODULENAME.cCLASSNAME")
This is related to a DLL which is placed alongside this asp page under \Bin. The DLL is an Interop COM dll custom developed by a former colleague and currently there's no access to the code.
The DLL components are appearing in the regEdit under HKEY_LOCAL_MACHINE\SOFTWARE\Classes\ which makes me assume it is registered. However when I try to re-register using regsvr32, it shows that it was loaded but couldn't find DLLRegisterServer method. I use regAsm to register the component.
Any alternate approach that can be done here? Am I missing something?
If the file name starts with "Interop" or "AxInterop", it is likely a wrapper to a COM DLL, not the DLL it's self. The COM DLL must be registered on the system and then a dotNet application will use/create that wrapper so you can make calls to it.
What you need to do is find the DLL, not the Interop because you are not using dotNet in Classic ASP. Make sure it is registered on that computer (using regsvr32 without error) and then this should work.
Last note/hint, that dll created by ex-coworker was done in C or VB (not dotNet) right? If done in dotNet, it is not COM and you need to research "How to call a managed DLL from unmanaged code".
Apparently it is possible to call a native executable from AIR using NativeProcessInfo. But can an AIR app call a DLL directly?
One possibility is to wrap the DLL is some kind of proxy EXE, but I'd like to avoid that, if possible.
By "call a DLL" you must be meaning retrieve pointer to some DLL function and invoke it. But how native code should execute in AIR application? AIR can run executables in separate processes, but what should it do with native code from DLL? You definitely need proxy exe to do that, at least to provide environment for function calls.