Summary
InstallShield cannot wrap .NET or Java files for the Try and Buy/Product Activation or Try and Die types of trialware. With .NET and Java-based applications, build errors may occur in InstallShield when users attempt to build the installation.Synopsis
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. Also, InstallShield cannot wrap NT services.
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. NT services that are protected with trialware cannot be started.
There are some issues with trialware on Windows Vista systems. Windows Vista systems cannot run trialware if an .exe file was wrapped with trialware protection in InstallShield; however, .dll files that were wrapped with trialware protection do work, as long as end users have administrative privileges when they install and run the trialware. This applies to the Try and Buy/Product Activation type of trialware, as well as the Try and Die type of trialware.
This article describes a workaround that enables users to create trialware versions of .NET applications, Java applications, applications that were created with interpretive languages, NT services, and applications that will run on Windows Vista systems.
Discussion
If your application is a .NET or Java-based application, if you used a tool such as PowerBuilder to create your application, if you are creating an NT service, or if you are targeting Windows Vista systems, 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 or NT service without having to activate it.
Related Articles
Cannot Control an Existing NT Service 4Number of Views Start/Stop an NT Service Through InstallScript 7Number of Views Problem: Lost Connection to Custom Action Server Process. Attempting to Regenerate. 5Number of Views What is the Difference Between a .NET Service and an NT Service? 3Number of Views SQL script to create custom properties for FlexNet Manager Suite 2015 6Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Case id: 00001065
Activity: Status change: 2 hours ago