BAML obfuscation

Question

Is there any tool / commercial obfuscator that can obfuscate BAML resources in WPF controls? If not, its a tough time in terms of IP protection sicne hackers can easily peek into the BAML resource by using BAML to XAML converters.

Answer 1

Herein lies the problem with .NET stuff: Claytons Open Source -- the open source you do when you're not doing open source.

This subject has been visited a bit elsewhere on the web:

• Protecting my intellectual property/XAML
• Code Protection and Licensing of WPF Applications.
• .net obfuscator {smartassembly}

The latter looks promising.

Answer 2

Hi Jan,

I know it's been a while since you wrote your question, but I wanted to inform you that obfuscation of XAML and BAML code is now possible.

At Creatix we have today released the 1.0 version of CodeFort, an obfuscation tool which is able to obfuscate .NET, WPF and Silverlight assemblies, and even rename identifiers inside of XAML and BAML code. This makes it for the first time ever possible to obfuscate 100% of a WPF or Silverlight Application's types and members.

You can learn more about the obfuscator and download the CodeFort Freeware Edition at: http://www.codefort.org

Best regards, Christian

Answer 3

It has been a long time in the making, but PreEmptive Solutions is in the final phase of beta testing the latest Dotfuscator release. For those WPF developers who have ever tried to obfuscate (specifically rename) WPF applications, you know that most of your application has had to be excluded. In this latest release, Dotfuscator is extending renaming into your XAML/BAML. This has three benefits; more of your assembly is protected, your XAML/BAML is protected, and you save time since configuration is now much simpler.

If you would like to run your application through this beta version of Dotfuscator, just email me ([email protected]) and I will have our support team send you credentials. This is beta – there are no fees – and you will have access to our support – but you cannot use this version for any production work. .NET 1.1 or higher is the only requirement.

We are seeing good results - for example, three production applications yielded the following increased coverage: • Medical imaging – increased protected surface from 27% to 100%. • Measuring device – increased protected surface from 26% to 78%. • Software development tool – increased protected surface from 61% to 100%.

…but we want to be sure we are covering all bases – so challenge us with your most complex WPF applications and let’s see how we do. Thanks!

Answer 4

Crypto Obfuscator obfuscates XAML (in Silverlight assemblies ) as well as BAML (in WPF assemblies) - it renames class/member references inside the XAML/BAML files. Plus it will strip all comments, newlines and whitespace in these files turning them into garbage to the human eye.