32/64位体系结构的Profiler加载路径（COR_PROFILER_PATH变量） [英] Profiler load path for 32/64-bit architectures (COR_PROFILER_PATH variable)
问题描述
根据此页面（https://msdn.microsoft.com/en-us/library/ee471451(v=vs） .100）.aspx）自.NET v4起，框架支持使用COR_PROFILER_PATH环境变量选择探查器DLL位置。这非常方便，但不幸的是
这种方法在启动x86 / x64进程混合时不起作用，因为需要两个不同的分析器DLL（每个体系结构一个）。
Hi,
According to this page (https://msdn.microsoft.com/en-us/library/ee471451(v=vs.100).aspx) since .NET v4 the framework supports selection of the profiler DLL location using COR_PROFILER_PATH environment variable. This is really convinient, but unfortunately
this approach does not work when a mix of x86/x64 processes is being started, since two two different profiler DLLs are required (one per architecture).
查看.NET Core的源代码，我看到它似乎支持每个架构COR_PROFILER_PATH_32 / COR_PROFILER_PATH_64的单独变量。但是，我在任何地方都找不到这些官方文档。 .NET Framework
是否也支持这些？如果是，可以正式记录吗？如果没有，开发人员可以考虑添加此功能吗？
b
祝你好运，
Vasili
Looking into the source code of .NET Core, I see that it seems to support separate variables per architecture COR_PROFILER_PATH_32 / COR_PROFILER_PATH_64. However, I found no official documentation for these anywhere. Are these supported by .NET Framework
as well? If yes, can it be officially documented? If not, can the developers consider adding this feature?
Best regards,
Vasili
推荐答案
您好Vasili Galka（SL），
Hi Vasili Galka (SL),
感谢您在此发帖。
根据我的搜索，.net support COR_PROFILER_PATH_32 / COR_PROFILER_PATH_64。它位于GitHub文档中。它显示了配置运行时行为的两种主要方法。
Based on my search, .net support COR_PROFILER_PATH_32 / COR_PROFILER_PATH_64. It is in the GitHub document. It shows two primary ways to configure runtime behavior.
COR_PROFILER_PATH_32 / COR_PROFILER_PATH_64在 分析API / ETW配置旋钮中声明。有关更多详细信息，请参阅GitHub文档。
The COR_PROFILER_PATH_32 / COR_PROFILER_PATH_64 declare in Profiling API / ETW Configuration Knobs. For more details, please refer to the GitHub document.
https://github.com/dotnet/coreclr/blob/master/Documentation/project-docs/clr-configuration-knobs.md
最诚挚的问候，
Wendy
这篇关于32/64位体系结构的Profiler加载路径（COR_PROFILER_PATH变量）的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
