Decide which DLL to use based on 32/64 bit

Hey all,

I am rolling out an update that will copy a DLL to my program's folder but I need to decide which DLL to copy based on the user's cpu architecture (32/64). Coincidentally, it is the DLL for wyDay's LimeLM. I see there are plenty of built-in options for 32/64 folders (system32, program files, etc.) in wyBuild, but I need to copy the proper DLL over. Is there a simple way to do this or do I need to create a script that does this?

Thanks,

Eric

Hey Eric,

I see there are plenty of built-in options for 32/64 folders (system32, program files, etc.) in wyBuild, but I need to copy the proper DLL over. Is there a simple way to do this or do I need to create a script that does this?

Well, if you're making a .NET app then you should make your app's CPU Type as x86 (as per our instruction in the C# and VB.NET articles). This way you only ever have to distribute the x86 version of TurboActivate and you get full compatibility with all Windows machines.

If you're making a non-.NET app, and you support the 2 separate architectures with 2 separate builds of your app, then the way to go about this is to create 2 separate projects files for wyBuild. An x86 version and an x64 version. This way the x86 version of your app will download updates specific to that architecture, ditto for the x64 version.

Tell me if that helps.

Oh, we already have our app designated as x86. The trouble we were running into was the TurboActivate.exe wizard for manual activation (offline). I suppose we can just include both with our installer and update and let the user browse to the appropriate cpu architecture (via start menu). Assuming you don't have a turboactive.exe that works for both.

Thanks!

Actually, come to think of it, would we be able to use the manual activation outside of our app's folder? It seems that once the request file is loaded it would need to be copied to the app's folder.

Oh, we already have our app designated as x86. The trouble we were running into was the TurboActivate.exe wizard for manual activation (offline). I suppose we can just include both with our installer and update and let the user browse to the appropriate cpu architecture (via start menu). Assuming you don't have a turboactive.exe that works for both.

Thanks!

Just use the x86 version of the TurboActivate wizard (it works on x86 and x64 versions of Windows).

Actually, come to think of it, would we be able to use the manual activation outside of our app's folder? It seems that once the request file is loaded it would need to be copied to the app's folder.

The actual activation data is all handled behind the scenes and stored in separate folders. So TurboActivate never writes to your program's directory.

Well that helps a lot! Thanks

(helps to solve the other issue I had been emailing you about too!)

Reply
Discard post