Sentinel Hardware Keys Developer's Guide - Customer Connection ...

Frequently Asked Questions
Contents Glossary Index Troubleshooting
Question 10: What precautions should I take while protecting
applications using CodeCover?
We recommend you to protect only the RELEASE build applications for
CodeCover, as the memory management and optimizations may differ for
DEBUG and RELEASE build applications.
Hence, it is recommended not to use CodeCover protection for the DEBUG
built applications.
Question 11: Why is it so that when I protect the DLL that is statically
linked to the application, the application fails to execute with
the protected DLL. Whereas, if the DLL is linked dynamically, it executes
successfully?
This is a static linked DLL issue that occurs once you have protected your
application. Please use one of the following tips while protecting a statically
linked DLL to resolve this issue:
Protect both the static linked DLL, and executable instead of
protecting only the DLL.
Use LoadLibrary instead of linking the DLL statically.
Question 12: What is the advantage of using the Command-Line
CodeCover utility?
The Command-Line CodeCover utility is an exe file. And as such, it can be
called by your project building script, to protect your desired application.
This eliminates the dependency on the Toolkit to protect the application.
Question 13: Will there be any difference in my protected application
if I protect my file using the Command-Line CodeCover utility,
instead of the Protect button provided in the License Designer
stage of the Sentinel Keys Toolkit?
The Command-Line CodeCover utility uses the license template (*.ltm) file to
get the various protection options (like: protection layer level, licensing
mode, network settings, etc. Hence, there is no difference between the file
protected via the Command-Line CodeCover utility or Sentinel Keys Toolkit.
Sentinel Hardware Keys Developer’s Guide 107