New feature: Skater protects .NET Core DLLs.
Skater .NET Obfuscator is an obfuscation tool for .NET code protection. It implements all known software protection techniques and obfuscation algorithms.
Skater .NET Obfuscator is a comprehensive professional solution for .NET application code protection. With Skater .NET Obfuscator you can easily protect Microsoft .NET framework applications from illegal code extraction and reverse engineering.Moreover, you do not need any source code changes or programming experience to accomplish professional software protection of your programs. Skater .NET Obfuscator reconstructs your .NET assemblies to the new view that is impracticable to be understand, and impossible to decompile.
If you would like periodically obfuscate your .NET products the Skater .NET Obfuscator is for you. RustemSoft is using the Skater for internal needs securing all RustemSoft .NET executables and assemblies. Its command-line version running in batch mode is much useful for your scheduled products updates. You have to assign settings for an assembly in GUI version first. Then the batch obfuscate task will use the settings.
Main features of Skater .NET Obfuscator Ultimate Edition
Prohibits reverse engineering
Obfuscated application usually is not recompilable
Processes any .NET application, executable or assembly
Encrypts string constants
Compatible with any .NET framework
Control flow obfuscation stops decompilers and deobfuscators
Scrambles class names, method names, field names etc.
Provides .NET Licensing features
Implements .NET Code Extension for small .NET applications protection.
Implements assemblies linkage; linker unites .NET assemblies into a single dll or exe.
When your WPF application is compiled into the build, XAMLs are converted to the BAML form of XAML. The BAML is abbreviation for Binary Application Markup File, a compiled XAML file.
These BAML forms are stored in YourApplicationName.g.resources file. The resource file is built-in inside your compiled exe or dll.
Every WPF .NET production-quality application uses resources. A resource is any nonexecutable data that is logically deployed with an application.
Why do we need to obfuscate XAML (baml) in WPF applications?
There are special software tools that load assemblies containing BAML resources (e.g. localized resource assemblies) and show the corresponding XAML. Anybody can see your XAMLs embedded in your .NET assembly.
<!-- Recent Reviews -->