The more I attach the debugger to an office application, the more I think that the executables are all caps to make them easier to find in the attach debugger dialog.
Yes, I see that, too. However, showing the extension would be an improvement and is essentially free since FileName ought to succeed all the time in Access host.
"So main variant should be VT_VARIANT | VT_BYREF, it should point to another variant VT_UI8 | VT_ARRAY, and that should point to a SAFEARRAY generated via SafeArrayCreate(). That outermost variant should then be copied into a block of memory, and its IntPtr sent to the Invoke method."
so this is the IntPtr that the custom marshaller needs to return from IntPtr ICustomMarshaler.MarshalManagedToNative(object ManagedObj)
does someone want to implement this for me puppy dog eyes
For me, the mental construct that works is that managed code basically mean it's running in a virtual machine, but I use the term "virtual machine" very loosely, nothing like virtualization.
anyways...how do i use that VARIANT struct thing you defined in the RD marshaler
i dont actually get what im doing here with it
i do get what I was doing yesterday with intptr
i got i need to copy the managed array to unmanaged, then get a pointer to it, then get a pointer to that pointer
"If a non-blittable class is marshaled by reference, the callee receives a pointer to a pointer to a copy of the data structure." from the MS documentation on Copying and Pinning