Enable In-App Product Purchases for Desktop Bridge Converted Desktop Applications

Desktop Bridge helps developers gradually migrate traditional apps to the Universal Windows Platform (UWP). The In-App Purchase (IAP) in Windows Store is an important scenario to monetize the converted apps. When working with developers on this scenario, I notice certain obstacles are in common,for example:

a. Porting old .Net or unmanaged applications to use the IAP UWP APIs.

b. Didn’t use async calls properly in UI apps and caused hang/deadlock

c. Default purchase windows failed to popup

d. Need accurate guide to follow IAP testing with current Windows Store APIs

Here I would like to explain a general solution to solve above issues, and also show four samples to use the IAPWrapper quickly:

a. WinForm in old .Net version

b. WPF app

c. Win32 App in C++

d. Unity App in old .Net version

All sample codes can be got from: https://github.com/appconsult/IAPWrapper

Many converted Win32 Desktop apps were developed in unmanaged code or old .NET version which cannot directly call current UWP Store APIs, in order to eliminate this gap, I create an .Net IAP Wrapper library. This wrapper will finally leverage DLLEXPORT nuget package to export function entries, which can be used by different kinds of Apps easily.

Create an IAP Wrapper Project:

1. Create a Win32 .NET class library project. The target frame work can be 4.6.1. I uses VS2017 as a quick start.

2. Add two references to allow this Win32 dll calls UWP APIs and async/await properly:

C:\Program Files (x86)\Windows Kits\10\UnionMetadata\Windows.winmd

C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework


3. Add statements to use necessary namespaces:


4. Follow this guide to call a StoreContext object in class library project that will be uses the Desktop Bridge:


In Converted Win32 Desktop App, it needs to configure the StoreContext object to specify which application window is the owner window for modal dialogs. The functional sample code is:




5. Install DLLExport nuget package to the project:


After installed the nuget package, you may see a setting dialog box pups up, can refer to this picture to configure (name space is still IAPWrapper here):


For more details of DLLExport, please refer to:


6. Add one statement to declare DLLExport on top of the Purchase (string storeID) method:


7. Use X86 or X64 option to build the library.

Note: AnyCPU option doesn’t give me the expected exported function entries.

If I build it in X64 option, using “dumpbin iapwrapper.dll /exports” can see the “Purchase” is listed in export section


This means we can load the library and function address to call it directly.

If build it in AnyCPU configuration option, the export function will not show up:


8. After above steps, we will get the IAPWRAPPER.dll, now can use it easily in various scenarios.

For all scenarios, please avoid below known issues:

1. Don’t call Task.Wait, this will cause UI apps deadlock issue. For detailed info, refer to: Async/Await – Best Practices in Asynchronous Programming https://msdn.microsoft.com/en-us/magazine/jj991977.aspx

2. Don’t run app with admin privilege, otherwise may not see the purchase diaglog box popup.

3. Make sure the purchase option runs in the UI thread, refer to:



4. The store ID used as parameter is the 12 characters of your add-on on your developer portal, not product display name.

Use IAPWRAPPER in .Net 2.0 Winform app

1. Add DLLImport statement and call the Purchase function:


2. Build the app, and put IAPWRAPPER.dll into the output folder. Run the app, and trigger the purchase, we can see default purchase windows pops up (depends on your account setting, authentication window may occur as well,):



Use IAPWRAPPER in .Net 4.6 WPF app

1. Add DLLImport and call purchase function:


2. Build the app, and put IAPWRAPPER.dll into the output folder. Run the app, it will show up the same purchase window.

Use IAPWRAPPER in C++ Win32 app

1. Use LoadLibrary and GetProcAddress to


2. Run the app, it will show up the same purchase window.


1. Put IAPWrapper into the Assets\Plugins folder

2. Add DLLImport and Purchase function as below:


3. Build the app as Win32 app, and run it.

Here I mainly explained how to quickly integrate the essential Windows IAP function to different kinds of Win32 Apps. You may expand your IAPWrapper for more specific usage scenarios, checking licensing, trail status, enumerate add-ons, etc. Can refer to:


After completing above tasks, please follow the 5 bullets exactly to ensure your applications are ready for IAP and Store function tests:



Freist Li


How to fix “Invalid Package Identity Name” error when submit Desktop Bridge (Centennial) converted application to Windows Store

After successfully converted Win32 app with Desktop Application Convert, and passed Windows Application Certificate Kit test, you may still meet this kind of error message when submit this app to Windows Store:

Invalid package identity name: MyTestApp (expected: 38323MyAccount.MyTestApp)Invalid package family name: MyTestApp_xx232xxxxxxxx (expected: 38323MyAccount.MyTestApp_ xx232xxxxxxxx)

This is because the PackageName was not set correctly when converting the app with DAC. Try using below command pattern to solve this issue:

DesktopAppConverter.exe -Installer D:\Release -Destination d:\output -PackageName “38323MyAccount.MyTestApp -Publisher “CN=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx” PackagePublisherDisplayName “My Account” -PackageDisplayName “MyTestApp” -AppDisplayName “MyTestApp” -AppID “MyTestApp” -Version -makeappx -AppExecutable “MyTestApp.exe” -packagearch x86