Postbuild for .NET is the powerful, reliable, and easy-to-use code protection and deployment solution for .NET developers.
Protects .NET code against decompilation and reverse engineering
Converts .NET applications to native binaries that run without the .NET Framework
Embeds SQL Server Express databases directly into the application binary
Eliminates compatibility errors by linking all application components into a single EXE
Optimizes application performance with metadata reduction and code pruning
What's new in Xenocode Postbuild 2010?
The latest version of Postbuild includes dozens of exciting new features, usability improvements, and engine enhancements, including:
Windows 7 compatibility: Xenocode is the first virtualization engine in its class to include full support for all editions of the new Windows 7 operating system.
Publish to Web: Publish apps to the web with a single click. Once online, apps can be launched with a single click directly within a web browser over 10 times faster than traditional download.
SQL Server Express embedding: Eliminate local database setup by embedding SQL Express databases directly into your binary with a single click.
Multi-platform capabilities: Platform merge allows virtual application behavior to be customized on a per-operating system basis while distributing a single executable.
Built-in support for the latest .NET runtimes and Windows components: The 2010 edition of Postbuild includes one-click configuration of the latest popular components, including .NET Framework 3.5, .NET 3.5 Client Profile, and Silverlight.
How does Xenocode Postbuild help me deploy my application?
Xenocode Postbuild includes many unique features which reduce the complexity of testing and deploying complex .NET applications:
Native executable generation: Postbuild allows for the creation of a native x86 executable allowing your application to run, with or without a .NET Framework installed. Required portions of a third-party .NET Framework payload are automatically selected and embedded into the executable, dramatically reducing the complexity of application testing, deployment, and support. Postbuild automatically identifies and statically binds a minimal set of Framework dependencies, reducing overall deployment size and eliminating dynamic link costs.
Assembly linking: Postbuild�s single-assembly output mode allows multi-assembly projects to be combined into a single output assembly, allowing for "copy" deployment of multi-assembly .NET applications. Linking is fully integrated into the obfuscation and optimization pipeline � encryption settings are automatically propagated across linked assemblies and redundant inter-assembly data are merged, reducing output assembly sizes.
Filesystem, registry, SQL, and service virtualization: Postbuild allows filesystem data, registry entries, SQL Server Express, and other Windows services to be directly embedded within the executable. Virtual machine resources are visible to the executing application without any modifications to the host device. For instance, application data files and COM components can be made available to the application without requiring any separate setup or registration. This also allows applications to emulate behavior of privileged applications under a non-privileged user account.
Code watermarking: Watermarking allows per-instance customization information, such as user names and registration codes, to be embedded into the visible text (for example, text in an About dialog or splash screen) as well as internal binary structures within your assembly. Watermarking can assist in tracking distribution of your product on a per-executable basis and deterring software licensing violations.
How does Xenocode Postbuild protect my product from decompilation?
Postbuild incorporates a range of powerful, industry-leading obfuscation techniques to inhibit decompilation and other forms of reverse engineering, including:
Symbol renaming: Xenocode Postbuild renames symbolic metadata, such as class, variable, and method names, into meaningless characters. This completely destroys the single most valuable resource available to a decompiler or a hacker studying your compiled executable.
Control flow obfuscation: Xenocode Postbuild manipulates the program control flow within the IL itself, editing branch instructions generated by the compiler, inserting decoy branches, and re-ordering instruction sequences. This conceals the original structure of your control flow (for example, the layout of if, for, and while blocks) and confuses decompilers. In fact, in our experience, Postbuild�s control flow obfuscation is so confusing to decompilers that they simply crash or completely fail to produce a valid decompilation.
String encryption: A common technique used by hackers to identify critical pieces of code involves searching the executable for a known literal string, for example "Enter password", and then looking at the point in the code which references the string. Xenocode Postbuild prevents identification of critical code locations in this manner by scrambling literal strings and injecting appropriate descrambling code whenever a scrambled string literal is referenced. This closes another door for the hacker.
Disassembly suppression: Xenocode Postbuild applies counter-analysis technology to your assembly to prevent many decompilers and disassemblers (for instance, Microsoft's ILDASM) to be unable to process your binaries. This prevents hackers from using such tools to analyze and disassemble your code. Xenocode Postbuild offers multiple suppression modes, depending on the security/compatibility trade-off required by your application.
Native code generation: While primarily intended as a deployment feature, use of native code generation provides an additional obstacle to decompilation by directly merging in Framework dependencies and converting managed executables into x86-based native executables.
Debug data stripping: Xenocode Postbuild strips all CodeView debugging information and symbol references from your binary. This information, which may be inserted by your compiler to facilitate debugging, can also be exploited by hackers to assist in reverse engineering your code.
Link checked on Fri Jun 11, 2010 2:41 pm (GMT) [Linkchecker Bot]