微软认为这是VS2008的一个bug，并且将在VS2010的Beta2中解决。。。
你如果非要调试，就用别的协议吧。。
以下摘自微软网站声明：http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=472536
If you expose a WCF web service via both WSDualHttpBinding and the newer Silverlight PollingDuplexBinding, and then make a simplex call to the web service over the WSDualHttpBinding while debugging the Visual Studio solution, Visual Studio will respond with the error message "Unable to automatically debug 'servicename'. The remote procedure could not be debugged. This usually indicates that debugging has not been enabled on the server. See help for more information."
你如果非要调试，就用别的协议吧。。
以下摘自微软网站声明：http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=472536
If you expose a WCF web service via both WSDualHttpBinding and the newer Silverlight PollingDuplexBinding, and then make a simplex call to the web service over the WSDualHttpBinding while debugging the Visual Studio solution, Visual Studio will respond with the error message "Unable to automatically debug 'servicename'. The remote procedure could not be debugged. This usually indicates that debugging has not been enabled on the server. See help for more information."
建议
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com/)
由 Microsoft 在 2009/7/6 1:35 发送I'd love to hear back on this, if only for suggestions on a workaround. My repro is pretty clear, so it shouldn't take someone in the know too long to figure out what's going wrong.
由 Ken Smith1 在 2009/7/14 4:12 发送Hi Ken,
Sorry that no one got back to you sooner, and thanks for reporting the issue.
First, because of your report, this issue should be resolved in Visual Studio 2010 beta 2. So if you get the chance, please give the beta a try when it releases later this year. Because of how the issue is fixed, installing the beta should actually fix both Visual Studio 2010 and Visual Studio 2008 if they are both installed on the same computer.
Aside from waiting for the fix, there are three work arounds that may help some customers, though they may not be an option for you:
1. As you already discovered, this is not an issue for the non-dual HTTP bindings. Though I am guessing that this workaround is not helpful for you.
-or-
2. If you used a protocol other than HTTP (ex: Net.TCP) this would not be an issue
-or-
3. If you used a binding that didn’t support one-way operations, this would not be an issue. So if you could build a custom binding that included what you needed without including one-way support, you could work around the issue.
Thanks,
Gregg Miskelly
Visual Studio Debugger Dev
Sorry that no one got back to you sooner, and thanks for reporting the issue.
First, because of your report, this issue should be resolved in Visual Studio 2010 beta 2. So if you get the chance, please give the beta a try when it releases later this year. Because of how the issue is fixed, installing the beta should actually fix both Visual Studio 2010 and Visual Studio 2008 if they are both installed on the same computer.
Aside from waiting for the fix, there are three work arounds that may help some customers, though they may not be an option for you:
1. As you already discovered, this is not an issue for the non-dual HTTP bindings. Though I am guessing that this workaround is not helpful for you.
-or-
2. If you used a protocol other than HTTP (ex: Net.TCP) this would not be an issue
-or-
3. If you used a binding that didn’t support one-way operations, this would not be an issue. So if you could build a custom binding that included what you needed without including one-way support, you could work around the issue.
Thanks,
Gregg Miskelly
Visual Studio Debugger Dev
由 Microsoft 在 2009/8/24 9:58 发送Thanks for the response. My workaround was to abandon IIS for hosting my service, and switch to the self-hosted variety, but I'll give the 2010 Beta 2 fix a try when it releases.
由 Ken Smith1 在 2009/8/27 16:33 发送 Product Language
English
Version
Visual Studio 2008 SP1
Operating System
Windows Vista
Operating System Language
English
Steps to Reproduce
(1) Create a web service which includes both duplex and standard simplex methods.
(2) Expose that web service via both the WSDualHttpBinding and the PollingDuplexBinding.
(3) Make a simplex (non-duplex) call to the web service over the WSDualHttpBinding.
(2) Expose that web service via both the WSDualHttpBinding and the PollingDuplexBinding.
(3) Make a simplex (non-duplex) call to the web service over the WSDualHttpBinding.
Actual Results
An error dialog box that says, "Unable to automatically debug 'servicename'."
Expected Results
The ability to debug the web service in question.
TAP Code (if applicable)