Adobe just released some new security-related patches for their Flash Player.
My question here is not “why again”, because I expected that. We all expected that. The real question is - who the hell still uses flash? And why are guides like “This is how you secure your flash installation now” so popular? (The expression “security hole” is always particularly funny; that’s obviously no hole here, because a hole clearly has an edge ;) )
Read this post in about 1 minute
When loading unmanaged / native libraries from managed .NET code, the normal way is to use the “Platform Invoke (P/Invoke)” mechanism.
1[DllImport("shell32.dll", CallingConvention = CallingConvention.Winapi)]
2static extern int DllGetVersion(ref DLLVERSIONINFO pdvi);
The problem
P/Invoke has an annoying limitation: You can not load an x86 (32bit) library into a 64bit process and vice versa.
This is especially problematic when your application is compiled with the “AnyCPU”-flag - which lets the .NET runtime decide which architecture to use at runtime - and there is only one 32bit version of a specific DLL.
If recompiling the library against a different architecture is not an option, you have to find another solution.
Read this post in about 3 minutes