将非托pipedllembedded托pipe的C＃dll
我有一个托pipe的C＃DLL，它使用了一个使用DLLImport的非托pipeC ++ DLL。 一切都很好。 不过，我想embedded我托pipe的DLL内的非托pipeDLL作为微软解释说：
http://msdn.microsoft.com/en-us/library/system.runtime.interopservices.dllimportattribute.dllimportattribute.aspx
所以我将非托pipedll文件添加到我的托pipedll项目中，将该属性设置为“Embedded Resource”并将DLLImport修改为如下所示：
[DllImport("Unmanaged Driver.dll, Wrapper Engine, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null", CallingConvention = CallingConvention.Winapi)] 其中“包装引擎”是我的托pipeDLL的程序集名称“非托pipe的Driver.dll”是非托pipe的DLL
当我跑步时，我得到：
访问被拒绝。 （从HRESULTexception：0x80070005（E_ACCESSDENIED））
我从MSDN和http://blogs.msdn.com/suzcook/看到这应该是可能的…
如果您在初始化期间将其自己解压缩到临时目录中，则可以将非托pipeDLL作为资源embedded，并在使用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);
这是我的解决scheme，这是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); } } } }
我不知道这是可能的 – 我猜测，CLR需要提取embedded式原生DLL的地方（Windows需要有一个文件的DLL来加载它 – 它不能从原始存储器加载图像），以及任何地方它正试图做这个过程没有权限。
像SysInternals 进程监视器可能会给你一个线索，如果问题是创buildDLL文件失败…
更新：
啊…现在我已经可以阅读Suzanne Cook的文章（该页面以前没有提供过），请注意，她并不是将本机DLL作为资源embedded到受pipeDLL中，而是作为链接资源 – 本地DLL仍然需要在文件系统中成为自己的文件。
请参阅http://msdn.microsoft.com/en-us/library/xawyf94k.aspx ，其中说：
资源文件不会添加到输出文件。 这与在输出文件中embedded资源文件的/ resource选项不同。
这似乎是将元数据添加到程序集，导致本机DLL在逻辑上成为程序集的一部分（即使它实际上是一个单独的文件）。 因此，将托pipe程序集放入GAC中会自动包含本地DLL等。
你可以试试Costura.Fody 。 文档说，它能够处理非托pipe文件。 我只用它来pipe理文件，它像一个魅力:)
也可以将DLL复制到任何文件夹，然后调用SetDllDirectory到该文件夹。 那么不需要调用LoadLibrary。
[DllImport("kernel32.dll", CharSet = CharSet.Unicode, SetLastError = true)] [return: MarshalAs(UnmanagedType.Bool)] static extern bool SetDllDirectory(string lpPathName);
