Latest blog posts for tag ".NET"

Today, I released version 3.0 of my NuGet package LegacyWrapper. LegacyWrapper 3.0 supports calling methods from legacy DLLs with a convenient managed method call.

Today, I released version 2.1 of my NuGet package LegacyWrapper. It comes with a major enhancement regarding the cross-architecture loading of DLLs: It is now possible to load 64bit DLLs from a 32bit process:

1using (var client = new WrapperClient(TestDllPath, TargetArchitecture.Amd64))
2{
3    result = (int)client.Invoke<TestStdCallDelegate>("TestStdCall", new object[] { input });
4}

As the second constructor parameter is optional and defaults to X86, the new release should be fully backwards compatible.

As a mainly WPF developer, I decided to take a look at the new Universal Windows Platform (UWP). In this post, I will focus on some small differences between WPF and UWP, including StringFormat and DataTemplates.

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.