Visual Studio：如何启动开发服务器而不打开浏览器窗口或看到警告？
Visual Studio 2010 Professional
因此，我希望能够“开始调试 (F5)”或“开始但不调试 (Ctrl + F5)”，而无需 a) 打开浏览器窗口或 b) 收到错误消息在 Visual Studio 中，
我尝试了以下操作：
将“开始操作”设置为“不打开页面。等待来自外部应用程序的请求”
这对于调试非常有用，但是如果我在没有调试的情况下启动，我每次都会收到此错误消息：
将“启动操作”设置为外部程序没有做任何事情。这非常适合在不进行调试的情况下启动，但是如果我尝试进行调试，则调试器会立即启动并停止。
我什至不明白 VS 的错误消息。我是“不调试就开始”……当然没有什么可调试的！别再烦我了！
提前致谢！
Visual Studio 2010 Professional
So I want to be able to "Start Debugging (F5)" or "Start Without Debugging (Ctrl + F5)" without a) Opening a browser window or b) Getting an error message from Visual Studio
I tried the following:
Setting "Start Action" to "Don't open a page. Wait for a request from an external application"
This works great for debugging, however if I start without debugging I get this error message every time:
Setting "Start Action" to an external program that doesn't do anything. This works great for starting without debugging, however if I try and debug then the debugger starts and stops immediately.
I don't even understand that VS error message. I'm "Starting Without Debugging"... of course there's nothing to debug! Stop bothering me!
Thanks in advance!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我可以提供一个工作流程，仅在您首次启动开发会话时打开浏览器窗口。我知道您永远不想打开浏览器窗口。如果这是工作流程偏好，那么我发现下面的解决方案对我自己来说已经足够了。
我将开始操作保留为“当前页面”。启动开发会话时，我使用“启动而不调试”来启动 ASP.NET 开发服务器和 Web 浏览器。我关闭了 Web 浏览器，但开发服务器仍保持运行并继续处理应用程序的请求。
如果未附加调试器，并且我进行了代码更改，则我使用“构建解决方案 (F6)”进行重建，并且开发服务器使用新构建的二进制文件。视图的更改会自动检测并重新编译。
为了调试，我使用 Debug ->附加到进程（对我来说是 CTRL + ALT + P）并根据端口找到正确运行的 WebDev.WebServer40.EXE 进程。
只要解决方案在 Visual Studio 中保持打开状态，开发服务器就会保持运行。
I can provide a workflow that only opens a browser window when you first start a development session. I know you don't want to open a browser window ever. If this is a workflow preference, then I have found the solution below good-enough for myself.
I keep the start action as 'Current Page'. When starting a development session, I use 'Start Without Debugging' to start the ASP.NET Development Server, and a web browser. I close the web browser, but the Development Server remains running and continues to server requests for your application.
If the debugger is not attached, and I make a code change, the I use 'Build Solution (F6)' to rebuild, and the Development Server uses the newly built binaries. Changes to views are automatically detected and re-compiled.
To debug, I use Debug -> Attach to Process (CTRL + ALT + P for me) and find the correct running WebDev.WebServer40.EXE process based on the port.
The Development Server remains running as long as the solution remains open in Visual Studio.