COM object that has been separated from its underlying RCW cannot be used, when opening project properties RRS feed

  • Question

  • Hello!

    We've been developing a VS extension for some time. Recently some of out clients have reported that they're unable to open 'project properties' when our extension is installed. I've done a google and found out that this is indeed a problem with conflicted extensions. See: 




    Also, I could see that some of the extension are fixed now by their respective developers (Eg: GhostDoc). 

    Appreciate if you could point out what is the mentioned 'conflict' here, and how to fix this with regards to our extension.

    Thank  you

    • Edited by Thusitha H Wednesday, January 17, 2018 9:40 AM
    Wednesday, January 17, 2018 9:40 AM

All replies

  • Hi Thusitha H,

    Based on your description and related link, it seems that your extension should add try catch to avoid throw exception to your extension.

    For more information, please refer to:



    Best regards,

    Zhanglong Wu

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Friday, January 19, 2018 7:19 AM
  • Hi Zhanglong Wu,

    Thanks for the reply.

    I found out the issue. There was an exception getting thrown in the extension. After fixing that, Project Properties got loaded without any error.

    However, I don't understand, why would something external like an extension, affect something internal like 'Project Properties'.



    Wednesday, January 24, 2018 10:04 AM