Version history - Crypto Obfuscator For .Net

What's New!! in v2010 R2

• NEW: Ability to hide calls to methods and properties from external assemblies (such as those from the .Net framework).
• NEW: Ability to hide calls to unrenamed methods and properties from the project assemblies. So, even if some methods and properties must be excluded from renaming, its impossible to determine when, where and how they are used.
• NEW: Added Warnings feature which lists all lines of code (such as that which uses Reflection) which may work incorrectly in an obfuscated assembly.
• NEW: Optimized the string encryption feature to reduce memory requirements during runtime.
• NEW: Improved renaming algorithm is faster.
• NEW: Improved support for default values for parameters and fields.
• NEW: Added support for .Net Micro Framework 3.0 & 4.0
• NEW: Added support for .Net Framework 4.0 and Visual Studio 2010
• NEW: New command-line options added to specify additional obfuscation settings via command-line.
• NEW: Added support for Silverlight for Phone.
• NEW: Added support for x64 assemblies
• NEW: Anti-Reflector Protection and Anti-Reflection Protection now works against .Net Reflector v6.x
• NEW: Improved support for LINQ-to-SQL or other LINQ-to-XXXXX projects.
• NEW: Added support for automatic obfuscation of satellite assemblies.
• NEW: Improved support for XNA
• NEW: Improved support for WCF projects.
• NEW: When using cryptographic renaming, a salt is used so that new names of types/members are not deterministic across projects.
• NEW: Stack traces can now be deobfuscated via command-line
• NEW: Now interfaces are also matched against the 'Base Class Pattern Matching" pattern.
• NEW: 'Base Class Pattern Matching" pattern now traverses the entire hierarchy, not just the immediate base class.
• NEW: MSBuild task now honors the ContinueOnError property.
• NEW: Added support for vararg methods.
• NEW: Search Directories can now be relative to the project file just like assembly paths, key paths, etc
• NEW: Added support for optional and required modifiers.
• FIX: Fixed renaming bugs in certain interface implementation scenarios.
• FIX: Clearer error message if project file is not specified properly via the command-line
• FIX: Project file passed via command line can now have relative path
• FIX: Fixed error in certain scenarios when signed obfuscated assemblies.
• FIX: Obfuscation of Silverlight and Compact Framework assemblies did not work on x64 systems.
• FIX: Symbol names produced by the cryptographic scheme are now CLS-compliant.

What's New!! in v2010

• NEW: Improved obfuscation of WPF assemblies. Crypto Obfuscator can now analyses XAML files corresponding to a WPF assembly and automatically determine classes and members to exclude from Symbol Renaming.
• NEW: Performs code analysis and presents a list of all lines in your code which can potentially cause an obfuscated assembly to fail to run or run incorrectly. This saves a tremendous amount of time when specifying classes and members to exclude from symbol renaming.
• NEW: Ability to disable Symbol Renaming on a per assembly basis. All other settings such as control flow, string encryption, etc take effect independently of symbol renaming.
• NEW: You can now exclude specified assemblies from embedding in the main assembly.
• NEW: Improved honoring of NonSerialized attribute applied to fields.
• NEW : Improved resolution od assembly references.
• NEW: Each assembly in obfuscation project can now be signed with a different key file.
• NEW: Support for signing assemblies using password protected pfx files.
• NEW: Improved heuristics for automatic exclusion of classes and members based on their usage.
• NEW: Improved support for SQL CLR assemblies.
• NEW: Improved heuristics for automatic exclusion of classes and members for SQL CLR assemblies.
• NEW: Ability to deobfuscate stack trace from command line.
• NEW: Methods can now be excluded from control flow and string encryption using obfuscation attributes.
• NEW: Assemblies targeting different .Net frameworks (normal Desktop framework, Compact framework, Silverlight and XNA) can now be put in the same obfuscation project.
• NEW: General UI improvements and much faster obfuscation.

What's New!! in v2009

• NEW: Deep integration (merging) of the LogicNP.CryptoLicensing.dll assembly in your assembly to remove obvious links between your assembly and CryptoLicensing, making it even more difficult to reverse-engineer or crack your assemblies.
• NEW: Support for .Net Framework 4.0 Beta 2 and Visual Studio 2010.
• NEW: Improved support for Silverlight 2.0 and 3.0.
• NEW: Improved support for Compact Framework.
• NEW: Add normal, compact framework, Silverlight and XNA assemblies to the same project.
• NEW: Improved string encryption for Silverlight assemblies.
• NEW: Improved assembly resolution during assembly obfuscation step.

What's New!! in v2.0

• NEW : Advanced Overload Renaming
• NEW : Anti-Debug & Anti-Tracing Protection
• NEW : Advanced Tamper Detection
• NEW : Rename To Unprintable Characters (All Symbols Look Same In Dissassembler/Decompiler)
• NEW : Improved String Encryption With Compression And In-Built tamper Detection
• NEW : Visual Studio Integration Via Build Events And MSBuild
• NEW : Improved Compact Framework Support
• NEW: Ability to specify search directories for dependant assemblies.
• NEW: Ability to turn ON/OFF processing of obfuscation attributes used in code.
• NEW: Ability to specify watermarks via command-line or MSBuild task.

What's New!! in v1.0

• Initial release! Crypto Obfuscator For .Net is a powerful and easy-to-use obfuscation and protection product for code protection & obfuscation of .Net assemblies, their optimization and performance improvement & their smaller and simplified deployment.