解析来自另一个文件夹的程序集引用
我正在开发一个应用程序,该应用程序引用并使用来自某个供应商的一些第三方程序集;在开发框中,我的源树中的引用文件夹中有这 3 个程序集,我可以引用它们并构建应用程序,应用程序构建但不会运行,因为未安装整个服务器应用程序,但这很好。
在我想要复制此自定义应用程序并运行我引用的所有程序集的服务器上,这些程序集位于类似以下的文件夹中:
D:\ProgramFiles\VendorName\ProductName\Support\API\Bin64
如果我在该文件夹中复制我的小可执行文件并运行它,它会完美运行,但如果我将 .exe 放入像我想要的更合适的文件夹:
D:\ProgramFiles\MyCompanyName\MyProduct\bin\...
它不起作用,因为它无法解析这些程序集。
我知道我可以在 app.config 中使用探测来指定我的 exe 必须在哪些文件夹中查找引用,但在我的情况下,程序集不在子文件夹中,更多的是在完全不同的位置中。
我不想复制我的应用程序文件夹中的所有供应商程序集,并且我不能仅将我引用的 3 个程序集放在那里,因为它们还加载其他程序集,除非我拥有所有这些程序集(很多...),否则它不会工作。
我没有做任何特殊的事情,没有创建应用程序域,也没有通过反射加载程序集,只是希望 CLR 解析应用程序启动或执行时需要的引用。
谢谢。
编辑:这里是最终的工作代码
static System.Reflection.Assembly currentDomain_AssemblyResolve(object sender, ResolveEventArgs args)
{
Logger logger = new Logger();
try
{
string RMSAssemblyFolder = ConfigurationManager.AppSettings["RMSAssemblyFolder"];
Assembly MyAssembly = null;
string strTempAssmbPath = string.Empty;
Assembly objExecutingAssemblies = Assembly.GetExecutingAssembly();
AssemblyName[] arrReferencedAssmbNames = objExecutingAssemblies.GetReferencedAssemblies();
AssemblyName myAssemblyName = Array.Find<AssemblyName>(arrReferencedAssmbNames, a => a.Name == args.Name);
if (myAssemblyName != null)
{
MyAssembly = Assembly.LoadFrom(myAssemblyName.CodeBase);
}
else
{
strTempAssmbPath = Path.Combine(RMSAssemblyFolder, args.Name.Substring(0, args.Name.IndexOf(",")) + ".dll");
if (!string.IsNullOrEmpty(strTempAssmbPath))
{
if (File.Exists(strTempAssmbPath))
{
logger.Information("Assembly to load: {0} - File was found in: {1}", args.Name, strTempAssmbPath);
// Loads the assembly from the specified path.
MyAssembly = Assembly.LoadFrom(strTempAssmbPath);
}
}
}
// Returns the loaded assembly.
return MyAssembly;
}
catch (Exception exc)
{
logger.Error(exc);
return null;
}
}
I am developing an application which references and uses some third party assemblies from a certain Vendor; in development box I have these 3 assemblies in a reference folder in my source tree and I can reference them and build the application, application builds but does not run because the whole server application is not installed, but this is fine.
On the server where I want to copy this custom application and run all assemblies I am referencing are in folder something like:
D:\ProgramFiles\VendorName\ProductName\Support\API\Bin64
and if I copy my small executable in that folder and run it, it works perfectly, but if I put my .exe in a more appropriate folder like I want:
D:\ProgramFiles\MyCompanyName\MyProduct\bin\...
it does not work because it cannot resolve those assemblies.
I know I can use probing in app.config to specify in which folders my exe has to look for references but imy case the assemblies are not in a subfolder, more in a completely different location.
I don't want to copy all vendor assemblies in my app folder and I cannot put there only the 3 ones I am referencing because they are also loading other assemblies and unless I have all of them (many...), it does not work.
I am not doing anything special, not creating app domains and not loading assemblies via reflection, just want the CLR to resolve the references as they are needed on application start or execution.
Thanks.
Edit: here the final working code
static System.Reflection.Assembly currentDomain_AssemblyResolve(object sender, ResolveEventArgs args)
{
Logger logger = new Logger();
try
{
string RMSAssemblyFolder = ConfigurationManager.AppSettings["RMSAssemblyFolder"];
Assembly MyAssembly = null;
string strTempAssmbPath = string.Empty;
Assembly objExecutingAssemblies = Assembly.GetExecutingAssembly();
AssemblyName[] arrReferencedAssmbNames = objExecutingAssemblies.GetReferencedAssemblies();
AssemblyName myAssemblyName = Array.Find<AssemblyName>(arrReferencedAssmbNames, a => a.Name == args.Name);
if (myAssemblyName != null)
{
MyAssembly = Assembly.LoadFrom(myAssemblyName.CodeBase);
}
else
{
strTempAssmbPath = Path.Combine(RMSAssemblyFolder, args.Name.Substring(0, args.Name.IndexOf(",")) + ".dll");
if (!string.IsNullOrEmpty(strTempAssmbPath))
{
if (File.Exists(strTempAssmbPath))
{
logger.Information("Assembly to load: {0} - File was found in: {1}", args.Name, strTempAssmbPath);
// Loads the assembly from the specified path.
MyAssembly = Assembly.LoadFrom(strTempAssmbPath);
}
}
}
// Returns the loaded assembly.
return MyAssembly;
}
catch (Exception exc)
{
logger.Error(exc);
return null;
}
}
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
您应该首先找到安装这些 dll 的文件夹,然后使用
AppDomain。 AssemblyResolve
挂钩程序集解析并尝试从此文件夹加载请求的程序集。它看起来像这样(未经测试,您需要检查 args.Name 到底包含什么,可能包含版本和强名称以及类型名称):
You should first find the folder where theses dlls are installed then use
AppDomain.AssemblyResolve
to hook assembly resolution and try to load the requested assemblies from this folder.It will look something like this (not tested, and you need to check what
args.Name
contain exactly, could contain the version and the strong name along with type name) :使用 SN.exe :SN - T VendorAssembly.dll,这将返回一个十六进制数字,即公钥令牌,然后从 app.config 引用该程序集。要获取版本,请右键单击您的供应商程序集并将其用作 codeBase 版本值,即您提到的 href=path。
Use SN.exe : SN -T VendorAssembly.dll, this will return a hex number that is the public key token, then, reference the assembly from app.config. To get the version right click your vendor assembly and use that for the codeBase version value, the href=path you mentioned.