Yes, Spices.Obfuscator works with WPF, but please don't forget that some classes automatically associated with different custom resources. Xaml files are custom resources. Now you can solve that problem by excluding window1 class name from obfuscation. We'll try to find solution to the nearest update.