.NET规范-调用自定义程序集失败-COR PROFILER [英] .NET Instrumentation - Call to Custom Assembly Fails - COR PROFILER

查看:141
本文介绍了.NET规范-调用自定义程序集失败-COR PROFILER的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在尝试将.NET Instrumentation Profiler部署到Azure Web应用程序中.我正在使用COR_PROFILER_32和* _64和COR_PROFILING_ENABLED在Azure Web应用程序中启用我的探查器.

I am trying to deploy my .NET Instrumentation profiler into Azure web apps. Using COR_PROFILER_32 and *_64 and COR_PROFILING_ENABLED i am enabling my profiler in Azure web app. 

我的探查器会将代码插入所有模块,包括.NET Framework模块. (例如System.dll,System.Core.dll等),甚至在用户模块中也是如此.所检测的代码将调用在单独的程序集"CAssemblyHelper.dll"中定义的函数. 这是任何CPU"

My profiler will instrument codes into all the modules including .NET Framework modules. (such as System.dll , System.Core.dll.. etc.) and even in user modules too. The instrumented code will call functions that are defined in a separate assembly "CAssemblyHelper.dll" which is "Any CPU" built. 

这里的问题是,当调用我的检测代码时,会出现"FileNotFoundException".错误消息发生. 

The issue here is , when my instrumented code is getting called there is a "FileNotFoundException" happening with error message. 

涂黑的是我所引用的程序集名称CAssemblyHelper.dll.程序集没有任何依赖关系.我已经在网络配置文件中探查了dll的位置.

The blacked out is the assembly name CAssemblyHelper.dll that i am referring to. The assembly is not having any dependencies. I have probed the location of the dll in the web config file. 

 <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <probing privatePath="bin;PrivateFolder"/>
    </assemblyBinding>
  </runtime>

如何解决此错误..!我正在IMetaDataAssemblyEmit中使用DefineAssemblyRef来定义模块中的程序集.在普通的IIS服务器计算机上,CAssembly帮助程序将安装在GAC中,并且一切运行正常.尝试时 在Azure中,问题来了!! 

How to resolve this error..! I am using DefineAssemblyRef in IMetaDataAssemblyEmit to define the assembly in the Modules. In the normal IIS server machine , the CAssembly helper will be installed in GAC, and everything was working perfectly. While trying in Azure the problem comes.! 

推荐答案

Selva,通读完您的帖子后,听起来好像只有在以下情况下才会发生此问题: .net框架代码正在调用已检测的代码.结果,在DLL加载到GAC中时,为什么它在本地可行,这是有道理的.这个问题很难 因为这是自定义探查器,所以我们可以进行故障排除.

Selva, after reading through your post, it sounds like this issue is only happening when the .net framework code is calling into the instrumented code. As a result, it makes sense why this works locally as the DLL is loaded in GAC. This issue is difficult for us to troubleshoot since this is a custom profiler.

话虽如此,Azure Web Apps确实具有内置的探查器.我们拥有有关如何设置探查器以及如何执行基本任务的文档

With that being said, Azure Web Apps does have a built in profiler. We have documentation on how to setup the profiler and how to perform basic tasks in this article. If you are already aware of this built in profiler, we would like to know what additional instrumentation you need in order for you to consider using it.

我们期待您的答复.


这篇关于.NET规范-调用自定义程序集失败-COR PROFILER的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆