Comments
Sort by recent activity
Hi Alex,
Thanks for the reply.
Yes, I see, that's make sense for private fields to not be obfuscated when the type is [Serializable].
How about private constants?
Consider this class:
[Serializable]
public class Class1
{
private const int State = 123;
private readonly string timestamp = DateTime.Now.ToTimestamp();
public string GetStatus()
{
return string.IsNullOrEmpty(timestamp) ? "Not initialized " + State.ToString() : "Initialized at " + timestamp + " " + State.ToString();
}
}
Obfuscated version has "private const int State" unobfuscated. Any reasons why? It does not seem to have any effect on serialization.
If I apply [NonSerialized] attribute to the constant, its name gets mangled during obfuscation.
Thanks. / comments
Hi Alex,
Thanks for the reply.
Yes, I see, that's make sense for private fields to not be obfuscated when the type is [Serializable].
How about private constants?
Consider this class:
[Serializ...
Hello,
Any news on SA-1569 ?
I am working on obfuscating a .NET solution where a few assemblies are merged into facade so that the facade will expose only a few selected types to clients. I need to obfuscate everything in merged assemblies except the types explicitly excluded.
SA documentation (http://documentation.red-gate.com/display/SA6/Troubleshooting+name+mangling) mentions KeepPublicMembersAccessible (former ExcludePublicMembers) attribute, but unfortunately it is not fully documented.
Would this be a correct usage of KeepPublicMembersAccessible attribute?
<Assembly AssemblyName="MyAssembly, Culture=neutral, PublicKeyToken=*****">
<Merging Merge="1">
<Obfuscation Obfuscate="1" KeepPublicMembersAccessible="0" />
</Merging>
</Assembly>
Will it cause the effect I need (obfuscating public members)?
Thanks. / comments
Hello,
Any news on SA-1569 ?
I am working on obfuscating a .NET solution where a few assemblies are merged into facade so that the facade will expose only a few selected types to clients. I need to...