SA with MVVM and XAML binding WP7

.NET obfuscator and automated error reporting

SA with MVVM and XAML binding WP7

Postby cohowap » Thu Jun 02, 2011 1:23 pm


I have a WP7 app I am trying to obfuscuate, but am having horrible results. First, it appears error reporting is not working.

But other than that, I think the issue is because SA is renaming my ViewModel properties that are bound to the View (xaml) and raised when changed (from a string).

Any idea how SA handles MVVM? Should I be skipping all the fields?

Has anyone successfully used SA for a MVVM project?

Posts: 3
Joined: Thu Jun 02, 2011 1:19 pm

Postby Brian Donahue » Fri Jun 03, 2011 2:51 pm

Not sure about MVVM and Phone, but we have had a lot of interest in WPF and Silverlight, which are the basis for most Phone applications.

Obfuscating WPF at the moment is troublesome because the BAML doesn't get rewritten when the member names are being changed by SmartAssembly. There are a very basic guide for troubleshooting WPF obfuscationon the Red Gate support site. Hopefully this is helpful.
Brian Donahue
Posts: 6590
Joined: Mon Aug 23, 2004 9:48 am

Postby Alex.Davies » Mon Jun 13, 2011 1:09 pm

Hi cohowap,
I hope Brian's guide helps you with the binding problems.

I'm very interested in your use of exception reporting on the phone. As you can probably tell, this is a relatively new feature. We'd really appreciate if you could give more details of the situation you found that error reporting doesn't work with WP7 so we can fix it.

Red Gate .NET Tools
Posts: 335
Joined: Tue Dec 02, 2008 11:23 am
Location: Cambridge, uk

Return to SmartAssembly 6

Who is online

Users browsing this forum: No registered users and 1 guest