How can the above reflection problems be solved?
Our obfuscator adds a warning to the log file if the above reflection methods are used in the obfuscated code. If the reflection methods act only on classes, methods, fields, properties and events outside of the assembly, there will be no problem. If, however, the reflection methods act on identifiers within the assembly, these identifiers must be specified in the XML config file so that obfuscation does not change them. • My application uses Microsoft Remoting technologies, will this work after obfuscation? Yes, but you need to reserve the class-names of the server objects from obfuscation, and Remoting calls will work normally. If you use an interface to define the remote methods, the interface and its methods need to be excluded from obfuscation as well. • How does remotesoft obfuscator deal with strong named assemblies? Our obfuscator deals with strong named assemblies automatically, no extra work is required. Usually, attaching a strong name signature to your code involves two ste
