指定“使用自定义 Web 服务器”的远程限定符

发布于 2024-09-05 11:54:19 字数 545 浏览 4 评论 0原文

有谁知道在尝试自动连接到 MSVSMON 时如何设置 Visual Studio 使用的远程调试监视器限定符?

给出这个问题的背景:

在我们的开发 Web 服务器上,我们运行 IIS 和一个名为“Stephen.Edmonds@UK06695”的 MSVSMON 会话。

在我的开发计算机上,我安装了 Visual Studio 2008,其中“使用自定义 Web 服务器”指向开发 Web 服务器。当我在 Visual Studio 中“开始调试”时,它会按照您的预期正确连接到开发 Web 服务器。

在同事的机器上,我们有相同的设置(尽管出于明显的原因,他以不同的用户身份登录)。当他尝试在 Visual Studio 中对同一项目“开始调试”时,它无法连接到 Web 服务器,因为它正在寻找名为 His.Name@UK06695 的 MSVSMON 会话。

如果限定符设置为“stephen.edmonds@UK06695”,则尝试从两台计算机手动附加工作,因此我可以合理地确定这不是防火墙或权限的问题。

那么,有谁知道如何指定通过“启动调试会话”自动连接时要使用的限定符?

Does anyone know how you set the remote debug monitor qualifier used by Visual Studio when attempting to connect to MSVSMON automatically?

To give the context of this question:

On our development web server, we have IIS running and an MSVSMON session as 'Stephen.Edmonds@UK06695'.

On my development machine, I have Visual Studio 2008 setup with "Use Custom Web Server" pointed at the development web server. When I "start debugging" in Visual Studio, it connects correctly to the development web server as you would expect.

On a colleagues machine, we have the same setup (although for obvious reasons he is logged in as a different user). When he tries "start debugging" in Visual Studio on the same project, it fails to connect to the web server because it's looking for an MSVSMON session called His.Name@UK06695.

Attempts to manually attach work from both machines provided that the qualifier is set to 'stephen.edmonds@UK06695', so I can be reasonably sure that it is not a problem with either firewalls or permissions.

So, does anyone know how to specify the qualifier to be used when automatically connecting via "start debug session"?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

ぃ双果 2024-09-12 11:54:19

我相信远程调试以两种方式之一工作:

  1. 在启动会话的用户的上下文中。这就是我认为您目前所拥有的,也是只有您可以自动附加到该流程的原因。
  2. 作为服务,以用户身份运行,其帐户必须具有“作为服务登录”的权限并具有网络访问权限。

由于您想使用多个帐户进行远程调试,我建议使用远程调试器配置向导将其更改为作为服务运行。我还将检查您的远程调试权限,以确保您的同事帐户设置为允许调试。

I believe that Remote Debugging works in one of two ways:

  1. In the context of the user who started the session. Which is what I think you have at the moment and is the reason only you can automatically attach to the process.
  2. As a service, running as a user whose account must have the privilege to 'Log on as a service' and have network access rights.

Since you want to remotely debug using multiple accounts I would suggest using the Remote Debugger Configuration Wizard to change it to run as a service. I will also check your permissions for Remote Debugging to ensure that your colleagues account is set to Allow debugging.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文