Displaying System Interfaces in ClassView

The VC++ ClassView pane of the project window displays a view of your project classes. If your project is an ATL project, then ClassView will also display your interfaces that a class supports when the class node is opened in ClassView. ClassView scans your class header file for COM_INTERFACE_ENTRY macros to determine what interfaces a class supports. By default, only interfaces that appear in your IDL file are displayed in the ClassView.

You can extend this feature to include any system interfaces that you implement in your class, such as IStorage, IStream etc. This can be acieved in two simple steps:

  1. Ensure that your class declaration includes COM_INTERFACE_ENTRY macros for the system interfaces you implement (it should do already)
  2. Open the system IDL file (in the main Include directory of your VC++ installation) that contains the interface you want ClassView to recognise and include it in your project

All system interfaces that are defined all IDL files that are included in your project will appear in the ClassView window.

NOTE: By default, adding an IDL file to your project excludes it from the project build so this method does not affect the build of your project in any way



Comments

  • There are no comments yet. Be the first to comment!

Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • Learn How A Global Entertainment Company Saw a 448% ROI Every business today uses software to manage systems, deliver products, and empower employees to do their jobs. But software inevitably breaks, and when it does, businesses lose money -- in the form of dissatisfied customers, missed SLAs or lost productivity. PagerDuty, an operations performance platform, solves this problem by helping operations engineers and developers more effectively manage and resolve incidents across a company's global operations. …

  • Today's agile organizations pose operations teams with a tremendous challenge: to deploy new releases to production immediately after development and testing is completed. To ensure that applications are deployed successfully, an automatic and transparent process is required. We refer to this process as Zero Touch Deployment™. This white paper reviews two approaches to Zero Touch Deployment--a script-based solution and a release automation platform. The article discusses how each can solve the key …

Most Popular Programming Stories

More for Developers

RSS Feeds