Home > Back-end >  Why I used ILMerge merge two DLL will go wrong
Why I used ILMerge merge two DLL will go wrong

Time:09-29

Why would I used ILMerge merge two DLLS error





PS: the verification code below is for people to see? Lost the dozens of times are wrong, can't see ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~

CodePudding user response:

Used to, the function of the net?

CodePudding user response:

Doing the.net low-level coding process, in order to function independently, is likely to generate multiple DLLS, reference is very inconvenience, the Microsoft provides a ILMerge original DOS tools, multiple DLLS can be merged into one, need to install it after the download is complete, and then through the DOS command to enter, specific usage is as follows:

D: \ \ Program Files \ Microsoft \ ILMerge> Ilmerge/log: log. TXT/targetplatform: v4/
Out: merge. DLL AnalysisLibrary. DLL USBClassLibrary. DLL

Description: this is the purpose of the operation, the current directory AnalysisLibrary. DLL and USBClassLibrary. DLL library, according to the. NetFramework 4.0 form (V4) merged into a merge. DLL,

Among them:/log: log. TXT command is generated in the process of log, write to the log. The TXT file, out: merge. DLL: is the output file, AnalysisLibrary. DLL USBClassLibrary. DLL is the source file, multiple source files separated by a space,

Someone, of course, also add the interface, if not used DOS command, also can be downloaded to the GUI interface tools, please download version 1.9 or newer version, version 1.0 supports only to Framework2.0, interface tool is simpler, not fat here,
  • Related