Share via


How to: Debug COM Clients and Servers Using RPC Debugging

This topic applies to:

Edition

Visual Basic

C#

C++

Web Developer

Express

Topic does not apply Topic does not apply

Native only

Topic does not apply

Standard

Topic does not apply Topic does not apply

Native only

Topic does not apply

Pro and Team

Topic does not apply Topic does not apply

Native only

Topic does not apply

Table legend:

Topic applies

Applies

Topic does not apply

Does not apply

Topic applies but command hidden by default

Command or commands hidden by default.

You can use remote procedure call (RPC) debugging to debug COM client/server applications. You must enable RPC debugging to use it. With RPC debugging enabled, when you step into the server call from the client, the debugger attaches to the server and lets you debug its code. When the debugger is attached, you can use all debugger features with both the client and server processes.

To enable RPC debugging

  1. On the Tools menu, click Options.

  2. In the Options dialog box, click the Debugging folder.

  3. Click the Native page.

  4. Select the RPC debugging check box.

    Note

    To debug RPC calls, you must have Administrator or Power User privileges.

    Note

    RPC stepping into a remote server that runs Microsoft Windows Vista will work only if a native debugger is attached to the remote server. Otherwise, the RPC call will fail without an error message. Otherwise the RPC call will complete, but the step-into the RPC call will not work.

See Also

Concepts

COM Server and Container Debugging

Other Resources

Debugging in Visual Studio