Static Library for Windows 10 ARM64

We haven't released the ARM64 static libraries for VS 2019 yet. No hard date on that. Use the dynamic libraries in the meantime.

It is very hard to use TurboActivate.dll dynamic library when you target multiple Windows versions.I'm using InnoSetup installer, which requires the TurboActivate.dll x86 dynamic library.My ARM64 program requires the TurboActivate.dll ARM64 library.I cannot have both x86 and ARM64 TurboActivate.dll in the same C:\Program Files\<my program>\ folder.

You could remove the licensing bit from the installer. Or you could rename what's included in the installer (so it's just used from the installer / uninstaller).

The first option is easier (and means more people will just install your app and begin using it faster).

Sorry, I don't understand the first option.Yes, I can remove LimeLM and "more people will just install my app and begin using it faster" without buying it.

Instead of integrating TurboActivate into your installer integrate it exclusively in your app. They still need to activate your app, but now you dont need to maintain 2 implementations of the activation process. Just one: the one in your app.

Wyatt wrote:> Instead of integrating TurboActivate into your installer integrate it exclusively> in your app. They still need to activate your app, but now you dont need to maintain> 2 implementations of the activation process. Just one: the one in your app.Yeah, but if they uninstall my app, the license will remain bound to that PC.

True. Then renaming the installer-included dll will be the best option.