C# 检查非托管 DLL 是 32 位还是 64 位？
声明：本页面是StackOverFlow热门问题的中英对照翻译，遵循CC BY-SA 4.0协议，如果您需要使用它，必须同样遵循CC BY-SA许可，注明原文地址和作者信息，同时你必须将它归于原作者（不是我）：StackOverFlow
原文地址: http://stackoverflow.com/questions/1001404/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
Check if unmanaged DLL is 32-bit or 64-bit?
提问by yoyoyoyosef
How can I programmatically tell in C# if an unmanagedDLL file is x86 or x64?
如何在 C# 中以编程方式判断非托管DLL 文件是 x86 还是 x64？
采纳答案by yoyoyoyosef
Refer to the specifications. Here's a basic implementation:
请参阅规格。这是一个基本的实现：
public static MachineType GetDllMachineType(string dllPath)
{
// See http://www.microsoft.com/whdc/system/platform/firmware/PECOFF.mspx
// Offset to PE header is always at 0x3C.
// The PE header starts with "PEpublic enum MachineType : ushort
{
IMAGE_FILE_MACHINE_UNKNOWN = 0x0,
IMAGE_FILE_MACHINE_AM33 = 0x1d3,
IMAGE_FILE_MACHINE_AMD64 = 0x8664,
IMAGE_FILE_MACHINE_ARM = 0x1c0,
IMAGE_FILE_MACHINE_EBC = 0xebc,
IMAGE_FILE_MACHINE_I386 = 0x14c,
IMAGE_FILE_MACHINE_IA64 = 0x200,
IMAGE_FILE_MACHINE_M32R = 0x9041,
IMAGE_FILE_MACHINE_MIPS16 = 0x266,
IMAGE_FILE_MACHINE_MIPSFPU = 0x366,
IMAGE_FILE_MACHINE_MIPSFPU16 = 0x466,
IMAGE_FILE_MACHINE_POWERPC = 0x1f0,
IMAGE_FILE_MACHINE_POWERPCFP = 0x1f1,
IMAGE_FILE_MACHINE_R4000 = 0x166,
IMAGE_FILE_MACHINE_SH3 = 0x1a2,
IMAGE_FILE_MACHINE_SH3DSP = 0x1a3,
IMAGE_FILE_MACHINE_SH4 = 0x1a6,
IMAGE_FILE_MACHINE_SH5 = 0x1a8,
IMAGE_FILE_MACHINE_THUMB = 0x1c2,
IMAGE_FILE_MACHINE_WCEMIPSV2 = 0x169,
}
// Returns true if the dll is 64-bit, false if 32-bit, and null if unknown
public static bool? UnmanagedDllIs64Bit(string dllPath)
{
switch (GetDllMachineType(dllPath))
{
case MachineType.IMAGE_FILE_MACHINE_AMD64:
case MachineType.IMAGE_FILE_MACHINE_IA64:
return true;
case MachineType.IMAGE_FILE_MACHINE_I386:
return false;
default:
return null;
}
}
" = 0x50 0x45 0x00 0x00,
// followed by a 2-byte machine type field (see the document above for the enum).
//
FileStream fs = new FileStream(dllPath, FileMode.Open, FileAccess.Read);
BinaryReader br = new BinaryReader(fs);
fs.Seek(0x3c, SeekOrigin.Begin);
Int32 peOffset = br.ReadInt32();
fs.Seek(peOffset, SeekOrigin.Begin);
UInt32 peHead = br.ReadUInt32();
if (peHead!=0x00004550) // "PEAssembly assembly = Assembly.ReflectionOnlyLoadFrom(@"<assembly Path>");
PortableExecutableKinds kinds;
ImageFileMachine imgFileMachine;
assembly.ManifestModule.GetPEKind(out kinds, out imgFileMachine);
FILE HEADER VALUES
8664 machine (x64)
5 number of sections
47591774 time date stamp Fri Dec 07 03:50:44 2007
", little-endian
throw new Exception("Can't find PE header");
MachineType machineType = (MachineType) br.ReadUInt16();
br.Close();
fs.Close();
return machineType;
}
The MachineTypeenum is defined as:
该MachineType枚举定义为：
private static (string pkName, string imName) FindPEKind(string filename)
{
// some files, especially if loaded into memory
// can cause errors. Thus, load into their own appdomain
AppDomain tempDomain = AppDomain.CreateDomain(Guid.NewGuid().ToString());
PEWorkerClass remoteWorker =
(PEWorkerClass)tempDomain.CreateInstanceAndUnwrap(
typeof(PEWorkerClass).Assembly.FullName,
typeof(PEWorkerClass).FullName);
(string pkName, string imName) = remoteWorker.TryReflectionOnlyLoadFrom_GetManagedType(filename);
AppDomain.Unload(tempDomain);
return (pkName, imName);
}
I only needed three of these, but I included them all for completeness. Final 64-bit check:
我只需要其中的三个，但为了完整起见，我将它们都包括在内。最后的 64 位检查：
public (string pkName, string imName) TryReflectionOnlyLoadFrom_GetManagedType(string fileName)
{
string pkName;
string imName;
try
{
Assembly assembly = Assembly.ReflectionOnlyLoadFrom(assemblyFile: fileName);
assembly.ManifestModule.GetPEKind(
peKind: out PortableExecutableKinds peKind,
machine: out ImageFileMachine imageFileMachine);
// Any CPU builds are reported as 32bit.
// 32bit builds will have more value for PortableExecutableKinds
if (peKind == PortableExecutableKinds.ILOnly && imageFileMachine == ImageFileMachine.I386)
{
pkName = "AnyCPU";
imName = "";
}
else
{
PortableExecutableKindsNames.TryGetValue(
key: peKind,
value: out pkName);
if (string.IsNullOrEmpty(value: pkName))
{
pkName = "*** ERROR ***";
}
ImageFileMachineNames.TryGetValue(
key: imageFileMachine,
value: out imName);
if (string.IsNullOrEmpty(value: pkName))
{
imName = "*** ERROR ***";
}
}
return (pkName, imName);
}
catch (Exception ex)
{
return (ExceptionHelper(ex), "");
}
}
回答by muusbolla
Even easier: check out the System.Reflection.Module class. It includes the GetPEKind method, which returns 2 enums that describe the type of code and the CPU target. No more hex!
更简单：查看 System.Reflection.Module 类。它包括 GetPEKind 方法，该方法返回 2 个描述代码类型和 CPU 目标的枚举。没有更多的十六进制！
(the rest of this very informative post was copied shamelessly from http://www.developersdex.com/vb/message.asp?p=2924&r=6413567)
（这篇内容丰富的帖子的其余部分是从http://www.developersdex.com/vb/message.asp?p=2924&r=6413567无耻地复制的）
Sample code:
示例代码：
##代码##PortableExecutableKinds can be used to check what kind of the assembly. It has 5 values:
PortableExecutableKinds 可用于检查程序集的类型。它有 5 个值：
ILOnly: The executable contains only Microsoft intermediate language (MSIL), and is therefore neutral with respect to 32-bit or 64-bit platforms.
ILOnly：可执行文件仅包含 Microsoft 中间语言 (MSIL)，因此对于 32 位或 64 位平台是中立的。
NotAPortableExecutableImage: The file is not in portable executable (PE) file format.
NotAPortableExecutableImage：文件不是可移植可执行 (PE) 文件格式。
PE32Plus: The executable requires a 64-bit platform.
PE32Plus：可执行文件需要 64 位平台。
Required32Bit: The executable can be run on a 32-bit platform, or in the 32-bit Windows on Windows (WOW) environment on a 64-bit platform.
Required32Bit：可执行文件可以在 32 位平台上运行，也可以在 64 位平台上的 32 位 Windows on Windows (WOW) 环境中运行。
Unmanaged32Bit: The executable contains pure unmanaged code.
Unmanaged32Bit：可执行文件包含纯非托管代码。
Following are the links:
以下是链接：
Module.GetPEKind Method: http://msdn.microsoft.com/en-us/library/system.reflection.module.getpekind.aspx
Module.GetPEKind 方法：http: //msdn.microsoft.com/en-us/library/system.reflection.module.getpekind.aspx
PortableExecutableKinds Enumeration: http://msdn.microsoft.com/en-us/library/system.reflection.portableexecutablekinds(VS.80).aspx
PortableExecutableKinds 枚举：http: //msdn.microsoft.com/en-us/library/system.reflection.portableexecutablekinds(VS.80) .aspx
ImageFileMachine Enumeration: http://msdn.microsoft.com/en-us/library/system.reflection.imagefilemachine.aspx
ImageFileMachine 枚举：http: //msdn.microsoft.com/en-us/library/system.reflection.imagefilemachine.aspx
回答by David Silva Smith
Using a Visual Studio command prompt, dumpbin /headers dllname.dll works too. On my machine the beginning of the output stated:
使用 Visual Studio 命令提示符，dumpbin /headers dllname.dll 也可以工作。在我的机器上，输出的开头指出：
##代码##回答by user1383112
Instead of Assembly.LoadFile, use Assembly.ReflectionOnlyLoadFrom. This will let you work around the "Bad Image Format" exceptions.
而不是Assembly.LoadFile，使用Assembly.ReflectionOnlyLoadFrom。这将让您解决“错误的图像格式”异常。
回答by Charlie Ezzell
I know it has been a while since this was updated. I was able to get away with the "Bad Image Format" exceptions by loading the file into it's own AppDomain.
我知道自从更新以来已经有一段时间了。通过将文件加载到它自己的 AppDomain 中，我能够摆脱“错误的图像格式”异常。
##代码##At this point, I do the following:
此时，我执行以下操作：
##代码##Running this against my Widows\Assembly directory gives me zero errors with over 3600 files processed. note: I use a dictionary to load the values being returned.
对我的 Widows\Assembly 目录运行这个程序可以让我在处理超过 3600 个文件时出现零错误。注意：我使用字典来加载返回的值。
I hope it helps. YMMV
我希望它有帮助。青年会
