BUG: RPC debugging does not work until you perform a step-by-step debug (318717)
The information in this article applies to:
- Microsoft Visual Studio .NET (2003), Professional Edition
- Microsoft Visual Studio .NET (2003), Enterprise Architect Edition
- Microsoft Visual Studio .NET (2003), Enterprise Developer Edition
- Microsoft Visual Studio .NET (2003), Academic Edition
- Microsoft Visual Studio .NET (2002), Professional Edition
- Microsoft Visual Studio .NET (2002), Enterprise Architect Edition
- Microsoft Visual Studio .NET (2002), Enterprise Developer Edition
- Microsoft Visual Studio .NET (2002), Academic Edition
- Microsoft Visual C++ .NET (2003)
- Microsoft Visual C++ .NET (2002)
This article was previously published under Q318717 SYMPTOMS If you have not performed any debugging on your computer
with either Visual Studio .NET or the Visual C++ 6.0 Debugger, remote RPC
debugging does not work, even though you have turned on RPC Debugging in VS .NET. CAUSE Visual Studio .NET sets the registry key DebugObjectRPCEnabled, which permits RPC debugging on the computer. However, Visual
Studio .NET does not set the registry key when you click to select RPC Debugging. Visual Studio .NET sets the registry key the first time you
perform step-by-step debugging on your computer. RESOLUTION Run a debug session and do step-by-step debugging at least
one time before you use the RPC debugging on your computer. STATUSMicrosoft has confirmed that this is a bug in the Microsoft
products that are listed at the beginning of this article.
Modification Type: | Minor | Last Reviewed: | 1/25/2006 |
---|
Keywords: | kbvs2005doesnotapply kbvs2005swept kbtshoot kbvs2002sp1sweep kbBug kbDebug kbpending kbsetup KB318717 kbAudDeveloper |
---|
|