views:

200

answers:

0

Hello,

As I understand there is no direct way to implement trials with InstallShield 2009 and .NET applications.

Their documentation claims that there is a workaround:

"*InstallShield cannot wrap .NET or Java files for the Try and Buy/Product Activation or Try and Die types of trialware. In addition, InstallShield cannot wrap files that were created with applications such as PowerBuilder, which uses interpretive languages. With .NET and Java-based applications, build errors may occur in InstallShield when users attempt to build the installation. With PowerBuilder-created applications, end users can install the application, but the application cannot be launched when end users click Finish in the trialware run-time dialog.

If your application is a .NET or Java-based application or you used a tool such as PowerBuilder to create your application, create a traditional Windows-based .dll file:

· The .dll file should contain a function that is called by your product’s executable file.

· Wrap the .dll file with the trialware protection in InstallShield.

· Obfuscate the function call to make it difficult for unscrupulous users to create their own versions of the unwrapped .dll file in an attempt to work around the trialware protection and use your application without having to activate it. With this workaround, when an end user tries to launch the executable file, the executable file calls the protected .dll file, which triggers the trialware technology.* "

Has anyone had experience implementing this workaround?

Are there other alternatives for implementing trials for .NET applications?

Thank You