带 WCF 的 CLR Profiler 不适用于特定服务
我需要分析 WCF 服务，但收到消息“等待服务启动公共语言运行时”，它仅发生在该特定服务上；当我尝试使用其他 WCF 服务时，它工作正常。我想知道是否应该在 wcf 中配置某些内容以允许该配置文件。两个服务都使用相同的帐户（admin）运行，并且两个服务的.net框架版本都是3.5。也许，我应该在配置文件中设置一些东西？我不知道为什么只有在这个服务中 clr 探查器不起作用。操作系统是windows 2003 server。
我真的很感激每一个答案。
提前致谢。
I need to profile a WCF service, but I get the message "Waiting for service to start common language runtime", it only occurs with this particular service; when I tried with other WCF services, it works fine. I was wondering if I should configure something in the wcf to allow the profile. Both services run with the same account(admin) and the .net framework version of both service is 3.5. Perhaps, I should set something in the config file? I don't know why only in this service the clr profiler doesn't work. The operating system is windows 2003 server.
I'll really appreciate every answer.
Thanks in advance.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
您可以将服务作为 .exe 运行并在那里对其进行分析吗？
Can you run the services as .exes and profile them there.
探查器不应该真正干扰服务，无论您在配置文件中放入什么，探查器都应该工作。
由于探查器几乎会挂钩 CLR 中的每个方法调用，因此您可能会看到在标准执行期间通常不会看到的各种并发问题；那么您的服务是否使用线程或者在启动过程中做了一些特殊的事情？
当然，CLR 分析器也可能存在一些错误，因此尝试使用另一个分析器也可能会得到您想要的东西 - 有几个免费选项。
The profiler should not really interfere with the service and no matter what you put in the config file, the profiler should work.
Since the profiler hooks just about every method call in the CLR, you might see various sorts of concurrency issues that you would not normally see during standard execution; so does your service utilize threading or is it doing something special during startup?
Of course the CLR profiler might also have some bugs in it, so trying with another profiler might also get you what you want - there are several free options out there.