SmartAssembly supports protecting WPF (Windows Presentation Foundation) assemblies.

To ensure that your XAML file works with the obfuscated assembly, SmartAssembly excludes some classes/methods from obfuscation. If you call other members by reflection from your XAML files, you may need to exclude them manually.

To decide whether this is required, follow the steps for 'Your application does not work after building with SmartAssembly' in Troubleshooting after building. When you have identified the line where the error occurs, exclude the class or method either in the SmartAssembly project settings or by using custom attributes directly in your code.

Troubleshooting WPF assembly protection

in SmartAssembly 6.6 and earlier, merging a dependency containing WPF often did not work. 

In SmartAssembly 6.7 and later, merging WPF has been greatly improved but sometimes you cannot apply Name Mangling to the merged dependency. If you experience problems when using Name Mangling, see Troubleshooting after building.