exe和dll文件合并工具_exe合并dll资源-CSDN文库

共2个文件

doc：1个

exe：1个

4星 · 超过85%的资源需积分: 50 41 浏览量 2012-09-06 06:41:57 上传评论收藏 248KB RAR 举报

资源推荐

资源详情

资源评论

收起资源包目录

ILMerge.rar （2个子文件）

ILMerge.doc 89KB

ExeMerger.exe 750KB

ILMerge

Michael Barnett

Programming Languages and Methods

Microsoft Research

1 Introduction

This document describes the ILMerge utility which merges multiple .NET assemblies

into a single assembly. However, some .NET assemblies may not be able to be merged

because they may contain features such as unmanaged code. I would highly recommend

using peverify (the .NET Framework SDK tool) on the output of ILMerge to guarantee

that the output is verifiable and will load in the .NET runtime.

ILMerge is packaged as a console application. But all of its functionality is also

accessible programmatically. Note that Visual Studio does allow one to add an

executable as a reference, so you can write a client that uses ILMerge as a library.

ILMerge takes a set of input assemblies and merges them into one target assembly. The

first assembly in the list of input assemblies is the primary assembly. When the primary

assembly is an executable, then the target assembly is created as an executable with the

same entry point as the primary assembly. Also, if the primary assembly has a strong

name, and a .snk file is provided, then the target assembly is re-signed with the specified

key so that it also has a strong name.

Note that anything that depended upon any of the names of the input assemblies, e.g.,

configuration files, must be updated to refer instead to the name of the target assembly.

Any Win32 Resources in the primary assembly are copied over into the target assembly.

There are many options that control the behavior of ILMerge. These are described in the

next section.

2 Public Interface

The public interface for ILMerge is defined in the ILMerging namespace as the class

ILMerge.

namespace ILMerging;

public class ILMerge { }

To use this class programmatically, just create an instance using the default (nullary)

constructor. There are several properties and methods which are used to affect the

behavior of the merging. The method Merge() is called to actually perform the merging.

2.1 AllowDuplicateType

public void AllowDuplicateType(string typeName);

The normal behavior of ILMerge is to not allow there to be more than one public type

with the same name. If such a duplicate is found, then an exception is thrown. However,

ILMerge can just rename the type so that it no longer causes a conflict. For private types,

this is not a problem since no outside client can see it anyway, so ILMerge just does the

renaming by default. For public types, it is not often a useful feature to have it renamed.

However, there are situations where it is needed. In particular, for obfuscated assemblies,

it seems that the obfuscator defines an attribute and creates an assembly-level attribute

for the obfuscated assembly using that attribute. This would mean that obfuscated

assemblies cannot be merged.

So this option allows the user to either allow all public types to be renamed when they are

duplicates, or to specify it for arbitrary type names. On the command line, there can be as

many options as desired, if followed by a colon and a type name, otherwise just specify it

alone with no colon (and type name) to allow all duplicates.

When used through the API, an argument of “null” means to allow all public types to be

renamed.

Default: no duplicates of public types allowed

Command line option: [/allowDup[:typeName]]*

2.2 AllowMultipleAssemblyLevelAttributes

public bool AllowMultipleAssemblyLevelAttributes { get; set; }

When this is set before calling Merge, then if the CopyAttributes property (Section 2.7) is

also set, any assembly-level attributes names that have the same type are copied over into

the target directory as long as the definition of the attribute type specifies that

“AllowMultiple” is true.

Default: false

Command line option: /allowMultiple

2.3 AllowWildCards

public bool AllowWildCards { get; set; }

When this is set before calling Merge, any wild cards in file names are expanded and all

matching files will be used as input. Note that because the wild card matching is done by

a call to Directory.GetFiles, it does not allow the characters ".." to appear in a file name.

So if you want to specify a relative path containing ".." to move up a directory, you will

have to use it with the "/lib" option (Section 2.20). That option does allow the use of ".."

to move up directories.

Default: false

Command line option: /wildcards

2.4 AllowZeroPeKind

public bool AllowZeroPeKind { get; set; }

When this is set before calling Merge, then if an assembly's PeKind flag (this is the value

of the field listed as .corflags in the Manifest) is zero it will be treated as if it was ILonly.

This can be used to allow C++ assemblies to be merged; it does not appear that the C++

compiler writes the value as ILonly. However, if such an assembly has any non-IL

features, then they will probably not be copied over into the target assembly correctly. So

please use this option with caution.

Default: false

Command line option: /zeroPeKind

2.5 AttributeFile

public string AttributeFile { get; set; }

If this is set before calling Merge, then it specifies the path and filename to an atttribute

assembly, an assembly that will be used to get all of the assembly-level attributes such as

Culture, Version, etc. It will also be used to get the Win32 Resources from. It is mutually

exclusive with the CopyAttributes property (Section 2.7). When it is not specified, then

the Win32 Resources from the primary assembly are copied over into the target

assembly. If it is not a full path, then the current directory is used.

Default: null

Command line option: /attr:filename

2.6 Closed

public bool Closed { get; set; }

When this is set before calling Merge, then the "transitive closure" of the input

assemblies is computed and added to the list of input assemblies. An assembly is

considered part of the transitive closure if it is referenced, either directly or indirectly,

from one of the originally specified input assemblies and it has an external reference to

one of the input assemblies, or one of the assemblies that has such a reference.

Complicated, but that is life...

Default: false

Command line option: /closed

评论收藏

内容反馈

youciyixing00

2014-04-23

用不了用不了
yhdkzy

2013-07-02

可以用。注意：路径不要有中文
xiaoluogang

2019-08-16

报错，用不了
tangguoshuai

2014-07-14

用不了，不知道为什么
sonyuer

2017-10-11

很差用不了

前往

页

blessor_true

粉丝: 0
资源: 2

exe和dll文件合并工具

合并DLL把DLL作为exe资源合并到EXE中

exe dll合并工具

ILMerge EXE、Dll合并工具

EXE合并工具

dll 和exe 合并工具

.Net程序集合并工具v1.0中文免费绿色版

DLL合并工具v1.0中绿色免费版

将DLL合并到exe的工具.zip

dll和exe合并的小工具

合并多个DLL或EXE 工具+说明.rar

合并exe与dll文件

开源工具NetZ（合并Exe、Dll，并混淆代码）中文版

最实用的dll合并软件和dll.exe合并软件

合并EXE和DLL文件.使产生一个可执行文件

合并DLL到EXE文件

c# dll、exe等合并工具

多个DLL合并成一个DLL

多个Dll合成一个Dll工具

C#程序（含多个Dll）合并成一个Exe的简单方法

EXE合并器-用于合并两个EXE文件

exe文件合并器exe文件合并器

EXE合并工具（汉化版）

exe文件合并器.rar

把dll合并到exe文件c++源码

压缩工具 将DLL和EXE文件打包到一起

Dll程序集合并工具

合并 dll 工具 ILMerge

ILMerge【DLL合并工具】

多个dll合并工具 ILMergeGUI

DLL合并工具ILMergeUI

最新资源

压缩工具将DLL和EXE文件打包到一起