Turn: ilmerge combines multiple components (updated)

An article at the beginning of the yearArticleMentioned below:
Http://margiex.cnblogs.com/archive/2005/01/31/100104.html

The. NET 2.0 version is now supported. Recently, due to the development of a clientProgramWe used multiple DLL files, so we considered using ilmerge to merge them into one. We tried it over the past two days. A simple example is as follows:

Ilmerge/ndebug/Target: EXE/targetplatform: V1.1/out: newclient.exe oldclient.exe/log autoupdater. DLL dockingsuite. DLL documentmanager. DLL filehelpers. DLL outlookbar. DLL sandbar. DLL icsharpcode. sharpziplib. DLL

Explanation:
Target: specifies the type of the output component, including dll/EXE/winexe ;(If it is exe, a DOS window (even a winform program) will appear during execution of the program. Therefore, set target to winexe.)
Targetplatform: the. NET running version of the output component;
Out: The full name of the merged component;
The names of the main components to be merged and all other related DLL;
In the preceding example, only the files are merged into EXE, and multiple DLL files can be merged into one DLL. Their namespaces will not change;

1. the DLL converted from com, InterOP, cannot be merged; ( can be merged, but the associated dll must also be merged, only Excel is used for the first merge. DLL, always reported errors, thought it was because of InterOP, and later found that vbide was not merged. for DLL, copy to the directory and merge it together. Everything is OK .)
2. if a resource dll exists, replace the oldclient.exe to be merged with another name, and name the merged output as oldclient.exe because the resource file name is oldclient. resources. DLL, while ilmerge cannot merge resource files; otherwise, this resource file cannot be found after export. (If anyone knows how to merge resource files, please advise, thank you)
3. although the merged EXE is relatively large, there is only one EXE in the user, which is more intuitive and easy to upgrade and maintain.