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.
eric-914
0

Comments

1 comment

Add comment

Please sign in to leave a comment.