COM: "Add Connection Point" does not generate Fire_* methods (VS2010)

Question

I'm currently attempting to implement a COM component with event support using connection points.
I've followed the general instructions given in
http://msdn.microsoft.com/en-us/library/9h7xedd1%28VS.80%29.aspx and
http://msdn.microsoft.com/en-us/magazine/cc163361.aspx .
Meaning I added a method description to the IDL file, generated the underlying type library by doing a compile on the IDL-file, and performed the "Add Connection Point" on the class in class view.
Following this procedure works like a charm for new projects - connection points are created without problems. However, on the project I've been working on for a while the necessary Fire_* methods are not created. The CProxy_* class is created, but it's
empty except for the class declaration (no methods)).
I've been looking around the net a bit and I noticed I'm not the only one having this problem. So I was wondering does anyone know what could cause this, is it a bug and, if so, is there a way to solve this?
update:
Similar problem 1
Similar problem 2

Answer 1

Hello,
For
the IDE wizard issue, please consider the following lists of items that we can try.
1. Have we applied the latest service pack? If not, apply the service pack.
2. If we reboot the operating system to safe mode, do we have the problem? This can help to isolate whether any other applications are interfering
with Visual Studio. Note that some features (like IIS) are not available under safe mode. Please check whether this can apply or not. In addition to safe mode, we can also suggest “clean boot”:
http://support.microsoft.com/kb/310353.
3. If we create a new user account, do we have the problem? This can help to isolate user profile corruption related causes.
4. If we disable Add-ns (e.g. “Tools” | “Add-in Manager”) and run “devenv.exe /safemode”, do we still have
the problem? This can eliminate the possibility that third party Add-ins are causing problems.
5. If we create a new project, do we have the problem? Sometimes corrupted project settings can cause problems. These are project specific.
6. If the problem remains, we can use Visual Studio Setup Wizard (via Control Panel) to repair Visual Studio. It can restore the Visual Studio
Installation into its original state.
Cheers
Yi Feng Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.