blocks|key|1461708|text|您可以向应用程序的.config文件中添加probing+path，但只有当探测路径包含在应用程序的基目录中时，它才会起作用。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1461709|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/823z9h8w.aspx^0|L|C|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

You can add a <a href="http://msdn.microsoft.com/en-us/library/823z9h8w.aspx" rel="noreferrer">probing path</a> to your application's .config file, but it will only work if the probing path is a contained within your application's base directory.

blocks|key|1461756|text|听起来您可以使用AppDomain.AssemblyResolve事件并手动加载DLL目录中的依赖项。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1461757|编辑(来自评论)：|1461758|AppDomain+currentDomain+=+AppDomain.CurrentDomain;
currentDomain.AssemblyResolve+%2B=+new+ResolveEventHandler(LoadFromSameFolder);

static+Assembly+LoadFromSameFolder(object+sender,+ResolveEventArgs+args)
{
++++string+folderPath+=+Path.GetDirectoryName(Assembly.GetExecutingAssembly().Location);
++++string+assemblyPath+=+Path.Combine(folderPath,+new+AssemblyName(args.Name).Name+%2B+".dll");
++++if+(!File.Exists(assemblyPath))+return+null;
++++Assembly+assembly+=+Assembly.LoadFrom(assemblyPath);
++++return+assembly;
}|code-block|syntax|javascript|1461759|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Sounds like you could use the AppDomain.AssemblyResolve event and manually load the dependencies from your DLL directory.

Edit (from the comment):

<pre><code>AppDomain currentDomain = AppDomain.CurrentDomain;
currentDomain.AssemblyResolve += new ResolveEventHandler(LoadFromSameFolder);

static Assembly LoadFromSameFolder(object sender, ResolveEventArgs args)
{
 string folderPath = Path.GetDirectoryName(Assembly.GetExecutingAssembly().Location);
 string assemblyPath = Path.Combine(folderPath, new AssemblyName(args.Name).Name + ".dll");
 if (!File.Exists(assemblyPath)) return null;
 Assembly assembly = Assembly.LoadFrom(assemblyPath);
 return assembly;
}
</code></pre>

blocks|key|1461818|text|查看AppDomain.AppendPrivatePath+(已弃用)或AppDomainSetup.PrivateBinPath|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1461819|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

look into AppDomain.AppendPrivatePath (deprecated) or AppDomainSetup.PrivateBinPath

blocks|key|1461842|text|最好的解释from+MS+itself|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1461843|AppDomain+currentDomain+=+AppDomain.CurrentDomain;
currentDomain.AssemblyResolve+%2B=+new+ResolveEventHandler(MyResolveEventHandler);

private+Assembly+MyResolveEventHandler(object+sender,+ResolveEventArgs+args)
{
++++//This+handler+is+called+only+when+the+common+language+runtime+tries+to+bind+to+the+assembly+and+fails.

++++//Retrieve+the+list+of+referenced+assemblies+in+an+array+of+AssemblyName.
++++Assembly+MyAssembly,+objExecutingAssembly;
++++string+strTempAssmbPath+=+"";

++++objExecutingAssembly+=+Assembly.GetExecutingAssembly();
++++AssemblyName[]+arrReferencedAssmbNames+=+objExecutingAssembly.GetReferencedAssemblies();

++++//Loop+through+the+array+of+referenced+assembly+names.
++++foreach(AssemblyName+strAssmbName+in+arrReferencedAssmbNames)
++++{
++++++++//Check+for+the+assembly+names+that+have+raised+the+"AssemblyResolve"+event.
++++++++if(strAssmbName.FullName.Substring(0,+strAssmbName.FullName.IndexOf(","))+==+args.Name.Substring(0,+args.Name.IndexOf(",")))
++++++++{
++++++++++++//Build+the+path+of+the+assembly+from+where+it+has+to+be+loaded.++++++++++++++++
++++++++++++strTempAssmbPath+=+"C:\\Myassemblies\\"+%2B+args.Name.Substring(0,args.Name.IndexOf(","))%2B".dll";
++++++++++++break;
++++++++}

++++}

++++//Load+the+assembly+from+the+specified+path.++++++++++++++++++++
++++MyAssembly+=+Assembly.LoadFrom(strTempAssmbPath);+++++++++++++++++++

++++//Return+the+loaded+assembly.
++++return+MyAssembly;++++++++++
}|code-block|syntax|javascript|1461844|entityMap|0|LINK|mutability|MUTABLE|url|http://support.microsoft.com/kb/837908^0|5|E|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

The best explanation <a href="http://support.microsoft.com/kb/837908">from MS itself</a>:

<pre><code>AppDomain currentDomain = AppDomain.CurrentDomain;
currentDomain.AssemblyResolve += new ResolveEventHandler(MyResolveEventHandler);

private Assembly MyResolveEventHandler(object sender, ResolveEventArgs args)
{
 //This handler is called only when the common language runtime tries to bind to the assembly and fails.

 //Retrieve the list of referenced assemblies in an array of AssemblyName.
 Assembly MyAssembly, objExecutingAssembly;
 string strTempAssmbPath = "";

 objExecutingAssembly = Assembly.GetExecutingAssembly();
 AssemblyName[] arrReferencedAssmbNames = objExecutingAssembly.GetReferencedAssemblies();

 //Loop through the array of referenced assembly names.
 foreach(AssemblyName strAssmbName in arrReferencedAssmbNames)
 {
 //Check for the assembly names that have raised the "AssemblyResolve" event.
 if(strAssmbName.FullName.Substring(0, strAssmbName.FullName.IndexOf(",")) == args.Name.Substring(0, args.Name.IndexOf(",")))
 {
 //Build the path of the assembly from where it has to be loaded. 
 strTempAssmbPath = "C:\\Myassemblies\\" + args.Name.Substring(0,args.Name.IndexOf(","))+".dll";
 break;
 }

 }

 //Load the assembly from the specified path. 
 MyAssembly = Assembly.LoadFrom(strTempAssmbPath); 

 //Return the loaded assembly.
 return MyAssembly; 
}
</code></pre>

blocks|key|1247241|text|Framework+4的更新|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1247242|由于Framework4也会为资源引发AssemblyResolve事件，因此这个处理程序实际上工作得更好。它基于本地化的概念，即本地化位于APP子目录中(一个用于本地化的子目录，带有文化的名称，例如C:\MyApp\it对于意大利语)，里面有资源文件。如果本地化是国家/地区，即it-IT或pt-BR，则处理程序也可以工作。在这种情况下，MSDN可能会多次调用处理程序:回退链中的每个区域性调用一次。这意味着如果我们为"it-IT“资源文件返回null，框架将引发请求"it”的事件。|1247243|事件挂钩|1247244|++++++++AppDomain+currentDomain+=+AppDomain.CurrentDomain;
++++++++currentDomain.AssemblyResolve+%2B=+new+ResolveEventHandler(currentDomain_AssemblyResolve);|code-block|syntax|javascript|1247245|事件处理程序|1247246|++++Assembly+currentDomain_AssemblyResolve(object+sender,+ResolveEventArgs+args)
++++{
++++++++//This+handler+is+called+only+when+the+common+language+runtime+tries+to+bind+to+the+assembly+and+fails.

++++++++Assembly+executingAssembly+=+Assembly.GetExecutingAssembly();

++++++++string+applicationDirectory+=+Path.GetDirectoryName(executingAssembly.Location);

++++++++string[]+fields+=+args.Name.Split(',');
++++++++string+assemblyName+=+fields[0];
++++++++string+assemblyCulture;
++++++++if+(fields.Length+<+2)
++++++++++++assemblyCulture+=+null;
++++++++else
++++++++++++assemblyCulture+=+fields[2].Substring(fields[2].IndexOf('=')+%2B+1);


++++++++string+assemblyFileName+=+assemblyName+%2B+".dll";
++++++++string+assemblyPath;

++++++++if+(assemblyName.EndsWith(".resources"))
++++++++{
++++++++++++//+Specific+resources+are+located+in+app+subdirectories
++++++++++++string+resourceDirectory+=+Path.Combine(applicationDirectory,+assemblyCulture);

++++++++++++assemblyPath+=+Path.Combine(resourceDirectory,+assemblyFileName);
++++++++}
++++++++else
++++++++{
++++++++++++assemblyPath+=+Path.Combine(applicationDirectory,+assemblyFileName);
++++++++}



++++++++if+(File.Exists(assemblyPath))
++++++++{
++++++++++++//Load+the+assembly+from+the+specified+path.++++++++++++++++++++
++++++++++++Assembly+loadingAssembly+=+Assembly.LoadFrom(assemblyPath);

++++++++++++//Return+the+loaded+assembly.
++++++++++++return+loadingAssembly;
++++++++}
++++++++else
++++++++{
++++++++++++return+null;
++++++++}

++++}|1247247|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|T|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|V|8|@]|9|@]|A|$I|J]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

Update for Framework 4

Since Framework 4 raise the AssemblyResolve event also for resources actually this handler works better. It's based on the concept that localizations are in app subdirectories (one for localization with the name of the culture i.e. C:\MyApp\it for Italian)
Inside there are resources file.
The handler works also if the localization is country-region i.e. it-IT or pt-BR. In this case the handler "might be called multiple times: once for each culture in the fallback chain" [from MSDN]. This means that if we return null for "it-IT" resource file the framework raises the event asking for "it".

Event hook

<pre><code> AppDomain currentDomain = AppDomain.CurrentDomain;
 currentDomain.AssemblyResolve += new ResolveEventHandler(currentDomain_AssemblyResolve);
</code></pre>

Event handler

<pre><code> Assembly currentDomain_AssemblyResolve(object sender, ResolveEventArgs args)
 {
 //This handler is called only when the common language runtime tries to bind to the assembly and fails.

 Assembly executingAssembly = Assembly.GetExecutingAssembly();

 string applicationDirectory = Path.GetDirectoryName(executingAssembly.Location);

 string[] fields = args.Name.Split(',');
 string assemblyName = fields[0];
 string assemblyCulture;
 if (fields.Length &lt; 2)
 assemblyCulture = null;
 else
 assemblyCulture = fields[2].Substring(fields[2].IndexOf('=') + 1);


 string assemblyFileName = assemblyName + ".dll";
 string assemblyPath;

 if (assemblyName.EndsWith(".resources"))
 {
 // Specific resources are located in app subdirectories
 string resourceDirectory = Path.Combine(applicationDirectory, assemblyCulture);

 assemblyPath = Path.Combine(resourceDirectory, assemblyFileName);
 }
 else
 {
 assemblyPath = Path.Combine(applicationDirectory, assemblyFileName);
 }



 if (File.Exists(assemblyPath))
 {
 //Load the assembly from the specified path. 
 Assembly loadingAssembly = Assembly.LoadFrom(assemblyPath);

 //Return the loaded assembly.
 return loadingAssembly;
 }
 else
 {
 return null;
 }

 }
</code></pre>

blocks|key|1247266|text|对于C%2B%2B/CLI用户，以下是@Mattias+S的答案(适用于我)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1247267|using+namespace+System;
using+namespace+System::IO;
using+namespace+System::Reflection;

static+Assembly+%5ELoadFromSameFolder(Object+%5Esender,+ResolveEventArgs+%5Eargs)
{
++++String+%5EfolderPath+=+Path::GetDirectoryName(Assembly::GetExecutingAssembly()->Location);
++++String+%5EassemblyPath+=+Path::Combine(folderPath,+(gcnew+AssemblyName(args->Name))->Name+%2B+".dll");
++++if+(File::Exists(assemblyPath)+==+false)+return+nullptr;
++++Assembly+%5Eassembly+=+Assembly::LoadFrom(assemblyPath);
++++return+assembly;
}

//+put+this+somewhere+you+know+it+will+run+(early,+when+the+DLL+gets+loaded)
System::AppDomain+%5EcurrentDomain+=+AppDomain::CurrentDomain;
currentDomain->AssemblyResolve+%2B=+gcnew+ResolveEventHandler(LoadFromSameFolder);|code-block|syntax|javascript|1247268|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

For C++/CLI users, here is @Mattias S' answer (which works for me):

<pre><code>using namespace System;
using namespace System::IO;
using namespace System::Reflection;

static Assembly ^LoadFromSameFolder(Object ^sender, ResolveEventArgs ^args)
{
 String ^folderPath = Path::GetDirectoryName(Assembly::GetExecutingAssembly()-&gt;Location);
 String ^assemblyPath = Path::Combine(folderPath, (gcnew AssemblyName(args-&gt;Name))-&gt;Name + ".dll");
 if (File::Exists(assemblyPath) == false) return nullptr;
 Assembly ^assembly = Assembly::LoadFrom(assemblyPath);
 return assembly;
}

// put this somewhere you know it will run (early, when the DLL gets loaded)
System::AppDomain ^currentDomain = AppDomain::CurrentDomain;
currentDomain-&gt;AssemblyResolve += gcnew ResolveEventHandler(LoadFromSameFolder);
</code></pre>

blocks|key|1247347|text|我从another+(marked+duplicate)+question来到这里，是为了向App.Config文件添加探测标记。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1247348|我想对此添加一个附注-+Visual+studio已经生成了一个App.config文件，但是将探测标记添加到预先生成的运行时标记并不起作用！您需要一个单独的运行时标记，其中包含探测标记。简而言之，您的App.Config应该如下所示：|1247349|<?xml+version="1.0"+encoding="utf-8"?>
<configuration>
++++<startup>+
++++++++<supportedRuntime+version="v4.0"+sku=".NETFramework,Version=v4.7.2"+/>
++++</startup>
++<runtime>
++++<assemblyBinding+xmlns="urn:schemas-microsoft-com:asm.v1">
++++++<dependentAssembly>
++++++++<assemblyIdentity+name="System.Text.Encoding.CodePages"+publicKeyToken="b03f5f7f11d50a3a"+culture="neutral"+/>
++++++++<bindingRedirect+oldVersion="0.0.0.0-4.1.1.0"+newVersion="4.1.1.0"+/>
++++++</dependentAssembly>
++++</assemblyBinding>
++</runtime>

++
++<runtime>
++++<assemblyBinding+xmlns="urn:schemas-microsoft-com:asm.v1">
++++++<probing+privatePath="lib"+/>
++++</assemblyBinding>
++</runtime>
</configuration>|code-block|syntax|javascript|1247350|这花了一些时间才弄清楚，所以我把它贴在这里。也归功于The+PrettyBin+NuGet+Package。它是一个自动移动dlls的包。我喜欢一种更手动的方法，所以我没有使用它。|1247351|还有-这里是一个构建后脚本，它将所有.dll/.xml/.pdb复制到/Lib。这会使/debug+(或/release)文件夹变得整洁，这正是我认为人们想要实现的目标。|1247352|::+Moves+files+to+a+subdirectory,+to+unclutter+the+application+folder
::+Note+that+the+new+subdirectory+should+be+probed+so+the+dlls+can+be+found.
SET+path=$(TargetDir)\lib
if+not+exist+"%25path%25"+mkdir+"%25path%25"
del+/S+/Q+"%25path%25"
move+/Y+$(TargetDir)*.dll+"%25path%25"
move+/Y+$(TargetDir)*.xml+"%25path%25"
move+/Y+$(TargetDir)*.pdb+"%25path%25"|1247353|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/2445556/c-sharp-putting-the-required-dlls-somewhere-other-than-the-root-of-the-output|1|https://github.com/slmjy/PrettyBin/^0|2|Z|0|0|0|0|Q|R|1|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@$A|11|B|12|1|13]]|C|$]]|$1|D|3|E|5|6|7|14|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|15|8|@]|9|@]|C|$I|J]]|$1|K|3|L|5|6|7|16|8|@]|9|@$A|17|B|18|1|19]]|C|$]]|$1|M|3|N|5|6|7|1A|8|@]|9|@]|C|$]]|$1|O|3|P|5|H|7|1B|8|@]|9|@]|C|$I|J]]|$1|Q|3|-4|5|6|7|1C|8|@]|9|@]|C|$]]]|R|$S|$5|T|U|V|C|$W|X]]|Y|$5|T|U|V|C|$W|Z]]]]

I came here from <a href="https://stackoverflow.com/questions/2445556/c-sharp-putting-the-required-dlls-somewhere-other-than-the-root-of-the-output">another (marked duplicate) question</a> about adding the probing tag to the App.Config file.

I want to add a sidenote to this - Visual studio had already generated an App.config file, however adding the probing tag to the pregenerated runtime tag did not work! you need a seperate runtime tag with the probing tag included. In short, your App.Config should look like this:

<pre><code>&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;configuration&gt;
 &lt;startup&gt; 
 &lt;supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.7.2" /&gt;
 &lt;/startup&gt;
 &lt;runtime&gt;
 &lt;assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"&gt;
 &lt;dependentAssembly&gt;
 &lt;assemblyIdentity name="System.Text.Encoding.CodePages" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" /&gt;
 &lt;bindingRedirect oldVersion="0.0.0.0-4.1.1.0" newVersion="4.1.1.0" /&gt;
 &lt;/dependentAssembly&gt;
 &lt;/assemblyBinding&gt;
 &lt;/runtime&gt;

 &lt;!-- Discover assemblies in /lib --&gt;
 &lt;runtime&gt;
 &lt;assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"&gt;
 &lt;probing privatePath="lib" /&gt;
 &lt;/assemblyBinding&gt;
 &lt;/runtime&gt;
&lt;/configuration&gt;
</code></pre>

This took some time to figure out so I am posting it here. Also credits to <a href="https://github.com/slmjy/PrettyBin/" rel="noreferrer">The PrettyBin NuGet Package</a>. It is a package that moves the dlls automatically. I liked a more manual approach so I did not use it.

Also - here is a post build script that copies all .dll/.xml/.pdb to /Lib. This unclutters the /debug (or /release) folder, what I think people try to achieve.

<pre><code>:: Moves files to a subdirectory, to unclutter the application folder
:: Note that the new subdirectory should be probed so the dlls can be found.
SET path=$(TargetDir)\lib
if not exist "%path%" mkdir "%path%"
del /S /Q "%path%"
move /Y $(TargetDir)*.dll "%path%"
move /Y $(TargetDir)*.xml "%path%"
move /Y $(TargetDir)*.pdb "%path%"
</code></pre>

My DLLs are loaded by a third-party application, which we can not customize. My assemblies have to be located in their own folder. I can not put them into GAC (my application has a requirement to be deployed using XCOPY).
When the root DLL tries to load resource or type from another DLL (in the same folder), the loading fails (FileNotFound).
Is it possible to add the folder where my DLLs are located to the assembly search path programmatically (from the root DLL)? I am not allowed to change the configuration files of the application.

How to add folder to assembly search path at runtime in .NET?

我的DLL是由第三方应用程序加载的，我们无法对其进行自定义。我的程序集必须位于它们自己的文件夹中。我不能将它们放入GAC (我的应用程序需要使用XCOPY进行部署)。当根DLL尝试从另一个DLL (在同一文件夹中)加载资源或类型时，加载失败(FileNotFound)。是否可以通过编程方式(从根DLL)将DLL所在的文...

问在.NET中如何在运行时将文件夹添加到程序集搜索路径？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在.NET中如何在运行时将文件夹添加到程序集搜索路径？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在.NET中如何在运行时将文件夹添加到程序集搜索路径？
EN