Pruning Report?

.NET obfuscator and automated error reporting

Pruning Report?

Postby eric-914 » Thu May 02, 2013 7:44 pm

Just wondering if for a future feature, S/A could generate a pruning report, detailing everything it deemed "prunable" and removed. It would make it so much easier tracking down what I need to mark as [DoNotPrune].

S/A's pruning is failing pretty bad when using Unity/XAML/MVVM, as Unity negates the need to ever "new" up a class explicitly, and XAML references ValueConverters which never are "new"d up explicitly either. Seems S/A will think any such classes are unused.
Posts: 30
Joined: Fri Nov 30, 2012 4:51 pm

Postby jessica.ramos » Fri May 03, 2013 8:46 pm

Hi Eric,

You should find the log file useful. :) ... a_Log_File
Jessica Ramos
Technical Support
Red Gate Software Ltd.
Posts: 544
Joined: Mon Apr 23, 2012 12:13 pm

Return to SmartAssembly 6

Who is online

Users browsing this forum: No registered users and 0 guests