try preemptive solutions now! 

Home
 

Dotfuscator Technology

Dotfuscator uses code instrumentation to transform .NET executables by injecting additional functionality without additional programming. Added functionalities can include obfuscation, watermarking, application analytics, application expiration, and more:

  • (AH) Obfuscation: Dotfuscator obfuscations .NET applications so that the executable logic is preserved, but the reverse semantics are rendered non-deterministic.
  • (AH) Watermarking: Watermarking is used to identify owners of the software or track the origin of a pirated copy. Dotfuscator uses watermarking to hide customer identification or copyright information within applications, similar to how it is hidden within other digital content.
  • (AH) Compaction: Dotfuscator removes unused classes, methods, instance variables, and design time metadata to produce a smaller application. Whenused with correctly application obfuscation technicques such as overload-induction, application sizes can be reduced further.
  • (AH) Linking: Preexisting assemblies can be linked together and merged into a single assembly by Dotfuscator. This process can be combined with other Dotfuscator features to secure your code.
  • (AH & AA) Tamper Detection and Reporting: Dotfuscator can enhance and enable an application to self-diagnose and report on tampering whenever and wherever it may occur.
  • (AH & AA) Shelf Lifeâ„¢ and Sign-of-Lifeâ„¢: Shelf Life helps you control the availability of an application, such as a Beta or Evaluation copy. Sign of Life lets you know how often an application is activated.
  • (AA) Application Analytics: The Applications Analytics Solution Set provides application- and feature-level analytics with near real-time access to adoption, usage, and behavior patterns. In addition, the AA Solution Set provides activation reports that are reliable and auditable and can drive your back office billing and support systems.
  • (AH & AA) Code Instrumentation: Bridge the development, business, and operational sides of the house. Just like makefiles, source control, and regression testing, code instrumentation should be a regular step in your build processes.