This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- trialware 64 bits c++
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 05, 2011
04:18 AM
trialware 64 bits c++
Hi,
I'm trying to use trialware feature on my setup.
Main application is a c# .net application which target any cpu (32 bits and 64 bits).
So i created a pure win32 dll in c++ and wrapped it using trialware.
Loaded by [ImportDll] in c# code, it works well... If system is 32 bits !
So i generated a 64 bits version of my security dll and now application is loading either 32 or 64 bits dll based on computer CPU.
My problem: no way to wrap this 64 bits dll with InstallShield 2012 trialware (error -7102)... Which make this feature completly useless for us.
Has someone any idea about this issue?
Thank you.
I'm trying to use trialware feature on my setup.
Main application is a c# .net application which target any cpu (32 bits and 64 bits).
So i created a pure win32 dll in c++ and wrapped it using trialware.
Loaded by [ImportDll] in c# code, it works well... If system is 32 bits !
So i generated a 64 bits version of my security dll and now application is loading either 32 or 64 bits dll based on computer CPU.
My problem: no way to wrap this 64 bits dll with InstallShield 2012 trialware (error -7102)... Which make this feature completly useless for us.
Has someone any idea about this issue?
Thank you.
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 05, 2011
03:02 PM
This accurately reflects the limitations of InstallShield's trialware feature. It only handles 32-bit native code. The scenario you describe would work if you can change to target the x86 (32-bit) platform only. For a wider set of capabilities, you might consider our full software licensing solutions.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 06, 2011
02:48 AM
Thank you for the answer.
After a short research on 32/64 bits interprocess communication (with COM for example), I concluded the same thing.
I will do a specific x86 build on our continuous integration server to build the trial version.
Thank you again for your help.
After a short research on 32/64 bits interprocess communication (with COM for example), I concluded the same thing.
I will do a specific x86 build on our continuous integration server to build the trial version.
Thank you again for your help.
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)