.NET obfuscator and automated error reporting
Moderators: Luke Jefferson, melvyn.harbour, dom.smith
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: 28
- Joined: Fri Nov 30, 2012 5:51 pm
Red Gate Software Ltd.
- Posts: 235
- Joined: Mon Apr 23, 2012 1:13 pm
Return to SmartAssembly 6
Who is online
Users browsing this forum: No registered users and 2 guests