If you are definitely some of open members are not to be accessed from farther than, you may want to conceal them.
For exe executables you may consider the assemblies to be self-contained, and set obfuscation of all workable names very belligerently, including Public Members.Private and Public members names obfuscation scrambles names of course, methods, variables, and other assembly members. A few Skater settings set a limit to generated names that want prevent recompilation.
Public members in dll libraries are on purpose reserved starting obfuscation because they are proposed to be used in peripheral assembly code. It makes assembly code reverse business much harder by obfuscating names. You may privileged all strings to be encrypted. Also you may feature some exclusive strings to obfuscate. Lone specified strings strength of character be encrypted/obfuscated.
Since Strings can provide beneficial clues for a person trying to reverse-engineer your code it makes common sense to protect your string data since spying eyes. The string encryption job allows you to select literal standards of string data type to be encrypted. However, for model, an attacker tiresome to break a licensing repetitive would first focus thought on Strings having to do with licensing to locate the proper spot of code. This is ready by inserting a decryption routine hooked on the assembly and calling the decryption code at runtime to send back the original Strings.Skater can brand this more demanding by encrypting the strings in your .NET assembly. You have top-drawer to apply a cryptography means for the string encryption. It will not avert an absolute hacker commencing deciphering the conversion and seeing your data.