将非托管dll嵌入到托管C#dll中


87

我有一个托管C#dll,它使用DLLImport使用非托管C ++ dll。一切都很好。但是,我想将该非托管DLL嵌入到托管DLL中,如Microsoft所解释的那样:

http://msdn.microsoft.com/zh-CN/library/system.runtime.interopservices.dllimportattribute.dllimportattribute.aspx

因此,我将非托管dll文件添加到了托管dll项目,将属性设置为“嵌入式资源”,并将DLLImport修改为:

[DllImport("Unmanaged Driver.dll, Wrapper Engine, Version=1.0.0.0,
Culture=neutral, PublicKeyToken=null",
CallingConvention = CallingConvention.Winapi)]

其中“包装器引擎”是我的托管DLL的程序集名称“非托管Driver.dll”是非托管DLL

当我跑步时,我得到:

访问被拒绝。(来自HRESULT的异常:0x80070005(E_ACCESSDENIED))

我从MSDN和http://blogs.msdn.com/suzcook/看到这应该是可能的...



1
您可以考虑针对自己的情况使用
BxILMerge

Answers:


64

如果在初始化过程中将非托管DLL自己提取到一个临时目录中,并可以在使用P / Invoke之前使用LoadLibrary显式加载它,则可以将其作为资源嵌入。我已经使用了这种技术,并且效果很好。您可能更喜欢将其作为单独的文件链接到部件,如Michael指出的那样,但是将其全部保存在一个文件中具有其优点。这是我使用的方法:

// Get a temporary directory in which we can store the unmanaged DLL, with
// this assembly's version number in the path in order to avoid version
// conflicts in case two applications are running at once with different versions
string dirName = Path.Combine(Path.GetTempPath(), "MyAssembly." +
  Assembly.GetExecutingAssembly().GetName().Version.ToString());
if (!Directory.Exists(dirName))
  Directory.CreateDirectory(dirName);
string dllPath = Path.Combine(dirName, "MyAssembly.Unmanaged.dll");

// Get the embedded resource stream that holds the Internal DLL in this assembly.
// The name looks funny because it must be the default namespace of this project
// (MyAssembly.) plus the name of the Properties subdirectory where the
// embedded resource resides (Properties.) plus the name of the file.
using (Stream stm = Assembly.GetExecutingAssembly().GetManifestResourceStream(
  "MyAssembly.Properties.MyAssembly.Unmanaged.dll"))
{
  // Copy the assembly to the temporary file
  try
  {
    using (Stream outFile = File.Create(dllPath))
    {
      const int sz = 4096;
      byte[] buf = new byte[sz];
      while (true)
      {
        int nRead = stm.Read(buf, 0, sz);
        if (nRead < 1)
          break;
        outFile.Write(buf, 0, nRead);
      }
    }
  }
  catch
  {
    // This may happen if another process has already created and loaded the file.
    // Since the directory includes the version number of this assembly we can
    // assume that it's the same bits, so we just ignore the excecption here and
    // load the DLL.
  }
}

// We must explicitly load the DLL here because the temporary directory 
// is not in the PATH.
// Once it is loaded, the DllImport directives that use the DLL will use
// the one that is already loaded into the process.
IntPtr h = LoadLibrary(dllPath);
Debug.Assert(h != IntPtr.Zero, "Unable to load library " + dllPath);

LoadLibrary是否使用kenel32的DLLImport?Debug.Assert在WCF服务中使用相同的代码失败。
Klaus Nji 2012年

这是一个很好的解决方案,但是当两个应用程序尝试同时写入同一位置时,找到可靠的分辨率甚至更好。异常处理程序在其他应用程序完成DLL的解压缩之前完成。
罗伯特·瓦赞(RobertVažan)2014年

太棒了。唯一不必要的是,directory.createdirectory已经具有目录存在的检查内容
Gaspa79,19年

13

这是我的解决方案,它是JayMcClellan答案的修改版本。将下面的文件保存到class.cs文件中。

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Runtime.InteropServices;
using System.IO;
using System.Reflection;
using System.Diagnostics;
using System.ComponentModel;

namespace Qromodyn
{
    /// <summary>
    /// A class used by managed classes to managed unmanaged DLLs.
    /// This will extract and load DLLs from embedded binary resources.
    /// 
    /// This can be used with pinvoke, as well as manually loading DLLs your own way. If you use pinvoke, you don't need to load the DLLs, just
    /// extract them. When the DLLs are extracted, the %PATH% environment variable is updated to point to the temporary folder.
    ///
    /// To Use
    /// <list type="">
    /// <item>Add all of the DLLs as binary file resources to the project Propeties. Double click Properties/Resources.resx,
    /// Add Resource, Add Existing File. The resource name will be similar but not exactly the same as the DLL file name.</item>
    /// <item>In a static constructor of your application, call EmbeddedDllClass.ExtractEmbeddedDlls() for each DLL that is needed</item>
    /// <example>
    ///               EmbeddedDllClass.ExtractEmbeddedDlls("libFrontPanel-pinv.dll", Properties.Resources.libFrontPanel_pinv);
    /// </example>
    /// <item>Optional: In a static constructor of your application, call EmbeddedDllClass.LoadDll() to load the DLLs you have extracted. This is not necessary for pinvoke</item>
    /// <example>
    ///               EmbeddedDllClass.LoadDll("myscrewball.dll");
    /// </example>
    /// <item>Continue using standard Pinvoke methods for the desired functions in the DLL</item>
    /// </list>
    /// </summary>
    public class EmbeddedDllClass
    {
        private static string tempFolder = "";

        /// <summary>
        /// Extract DLLs from resources to temporary folder
        /// </summary>
        /// <param name="dllName">name of DLL file to create (including dll suffix)</param>
        /// <param name="resourceBytes">The resource name (fully qualified)</param>
        public static void ExtractEmbeddedDlls(string dllName, byte[] resourceBytes)
        {
            Assembly assem = Assembly.GetExecutingAssembly();
            string[] names = assem.GetManifestResourceNames();
            AssemblyName an = assem.GetName();

            // The temporary folder holds one or more of the temporary DLLs
            // It is made "unique" to avoid different versions of the DLL or architectures.
            tempFolder = String.Format("{0}.{1}.{2}", an.Name, an.ProcessorArchitecture, an.Version);

            string dirName = Path.Combine(Path.GetTempPath(), tempFolder);
            if (!Directory.Exists(dirName))
            {
                Directory.CreateDirectory(dirName);
            }

            // Add the temporary dirName to the PATH environment variable (at the head!)
            string path = Environment.GetEnvironmentVariable("PATH");
            string[] pathPieces = path.Split(';');
            bool found = false;
            foreach (string pathPiece in pathPieces)
            {
                if (pathPiece == dirName)
                {
                    found = true;
                    break;
                }
            }
            if (!found)
            {
                Environment.SetEnvironmentVariable("PATH", dirName + ";" + path);
            }

            // See if the file exists, avoid rewriting it if not necessary
            string dllPath = Path.Combine(dirName, dllName);
            bool rewrite = true;
            if (File.Exists(dllPath)) {
                byte[] existing = File.ReadAllBytes(dllPath);
                if (resourceBytes.SequenceEqual(existing))
                {
                    rewrite = false;
                }
            }
            if (rewrite)
            {
                File.WriteAllBytes(dllPath, resourceBytes);
            }
        }

        [DllImport("kernel32", SetLastError = true, CharSet = CharSet.Unicode)]
        static extern IntPtr LoadLibrary(string lpFileName);

        /// <summary>
        /// managed wrapper around LoadLibrary
        /// </summary>
        /// <param name="dllName"></param>
        static public void LoadDll(string dllName)
        {
            if (tempFolder == "")
            {
                throw new Exception("Please call ExtractEmbeddedDlls before LoadDll");
            }
            IntPtr h = LoadLibrary(dllName);
            if (h == IntPtr.Zero)
            {
                Exception e = new Win32Exception();
                throw new DllNotFoundException("Unable to load library: " + dllName + " from " + tempFolder, e);
            }
        }

    }
}

2
马克,这真的很酷。对于我的用途,我发现可以删除LoadDll()方法,并在ExtractEmbeddedDlls()末尾调用LoadLibrary()。这也使我可以删除PATH修改代码。
卡梅伦·2013年

9

我不知道这是可能的-我猜CLR需要在某个地方提取嵌入式本机DLL(Windows需要有一个文件供DLL加载,它不能从原始内存加载图像),以及在任何地方它正在尝试执行该过程没有权限。

SysInternals的Process Monitor之类的东西可能会给您一个提示,如果问题是创建DLL文件失败...

更新:


嗯...现在我已经能够阅读Suzanne Cook的文章(以前没有针对我的页面),请注意她不是在谈论将本机DLL作为资源嵌入到托管DLL中,而是作为链接资源-本机DLL在文件系统中仍需要是其自己的文件。

请参阅http://msdn.microsoft.com/en-us/library/xawyf94k.aspx,其中显示:

资源文件未添加到输出文件。这与/ resource选项不同,后者在输出文件中嵌入了资源文件。

这似乎是在向程序集添加元数据,这会导致本机DLL在逻辑上成为程序集的一部分(即使它实际上是一个单独的文件)。因此,将托管程序集放入GAC之类的事情将自动包含本机DLL等。


如何在Visual Studio中使用“ linkresource”选项?我找不到任何例子。
阿列克谢·苏博塔

9

您可以尝试Costura.Fody。文档说,它能够处理非托管文件。我只将其用于托管文件,它的工作原理很像:)


4

也可以将DLL复制到任何文件夹,然后将SetDllDirectory调用到该文件夹​​。然后,无需调用LoadLibrary。

[DllImport("kernel32.dll", CharSet = CharSet.Unicode, SetLastError = true)]
    [return: MarshalAs(UnmanagedType.Bool)]
    static extern bool SetDllDirectory(string lpPathName);

1
好主意,请注意,由于它可能会注入dll,因此可能会带来安全后果,因此在高安全性环境中应谨慎使用
yoel halb
By using our site, you acknowledge that you have read and understand our Cookie Policy and Privacy Policy.
Licensed under cc by-sa 3.0 with attribution required.