REFLECTOR

xiaoxiao2021-03-05  21

REFLECTOR

Reflector download address: http://www.aisto.com/roeder/dotnet

FileDisassembled download address: http://www.denisbauer.com/

Use VS.NET to create a new project, create a new folder based on the folder structure, import all source files and resource files. Using the resource file exported by the FileDisassembler as a full name, in the actual project, you must change the resource file name according to NameSpace and must change "Generate" to "embedded resources". You can use ILDASM to view metadata to determine the resource file name and Folders, compile and change some errors;

When compiled, find all the contents related to COM will comment out (because the CCW / RCW technology is used), and make the corresponding changes, after the CLASS is changed, compiled once until it removes the relevant references;

After the changes are complete, they need to be reconstructed, mainly refactoring the following:

Rename, because the REFLECTOR tool is named, if the variable name is naming according to the type, such as Text1, Text2, Num1, etc .; remove the GOTO statement, if there is a SWTICH statement in the code, the Reflector tool uses the GOTO statement, which seriously affects the program logic. Readability; EXTRACT METHOD will perform a decomposition operation of too long Method;

When the reconstruction is completed, apply to the project and change the corresponding Register statement, Test, Run, and the result is Successful, which has completed the project manager to give me the task of the project manager.

Is the signature file that the signature file can't be found in the FileDisassembler installation?

You need to manually change the assemblyinfo.cs file, remove the following sentence [Assembly: assemblykeyKeyfile "] The signature file in the following is removed, and recompile can solve the signature problem.

转载请注明原文地址:https://www.9cbs.com/read-35794.html

New Post(0)