Lex Li

https://www.erikschierboom.com/2015/12/31/csharp6-under-the-hood-nameof/ This is caused by the implementation of `nameof`, so no plan to fix that yet. Pull requests are welcome.

Related to #318

Obfuscation might slightly change the way your app works (if you check the opened issues), so such exceptions are not unexpected. However, without accessing your project (assemblies and maybe source...

You'd better exclude those items from obfuscation, as the setting system is based on naming convention.

UWP apps run on .NET Native, which is an obfuscator of itself. You don't need Obfuscar there.

Thanks. As Mono Cecil does not automatically associate the two parts, renaming the attribute class (and its field) would lead to broken pieces like you reported. To fix that, either...

It is too difficult for the renaming algorithm to locate all references of a name (in this case a name referred in LINQ expressions), so like you discovered the only...

Related to #130.

Is it really a must? I evaluated its urgency but did not think it is urgent.

You have to give a more concrete example on what's the matter. There is no plan to add any complexity here in a simple obfuscation tool, unless it turns out...