LegacyWrapper
LegacyWrapper copied to clipboard
LegacyWrapper uses a x86 wrapper to call legacy dlls from a 64 bit process (or vice versa).
I'm hoping to create something to stick between an updated-to-64-bit product (A) that will allow it to still use an old 32-bit product (B) that we still use. Product A...
I used a 32 bit DLL method that has void *lp parameter. When IntPtr returned by Marshall.StructureToPtr was passed, DLL method returned invalid pointer error. Solution is to cast structure...
LegacyWrapper.dll, LegacyWrapper.Common.dll... can not embedded by fody ? if embedded by fody, call exception: The system can't find the specify File
I am trying to call a 32-bit DLL from an asp.net mvc website (which is running in a 64-bit application pool), but I keep getting this exception: "The system cannot...
I implement LegacyWrapper but i have a problem when execute it and try to find the dll file:    but dll exist when compile projects 
Would it be possible to sign the assemblies with a [strong-name](https://docs.microsoft.com/en-us/dotnet/standard/assembly/strong-named)? Otherwise, we're not able to use this in our project because we sign our assemblies in order to be...
Does this LegacyWrapper have support for ARM64 systems? And if not, then could it be added in the near future?
Example
I am new to Windows and DLL's. I have an old 32 bit DLL written in Visual Studio 6 c++. I need to make a 64 bit version. I want...
Resolves #17 Resolves #18
When the native signature is `int MyFunction(BSTR * pszVerificationId)` With PInvoke I can do something like ``` [System.Runtime.InteropServices.DllImportAttribute("TestDLL", EntryPoint = "MyFunction", CallingConvention = System.Runtime.InteropServices.CallingConvention.StdCall)] public static extern int MyFunction([MarshalAsAttribute(UnmanagedType.BStr)] ref...