Debugger extensibility: how to set editor to read-only in debug mode?

Unanswered Debugger extensibility: how to set editor to read-only in debug mode?

  • Wednesday, August 01, 2012 2:07 PM
     
     

    Hi,

    we created a custom debug engine and now want to set the editor windows to read-only because we do not want to support edit-and-continue.

    What is the easiest way to achieve this?

    What we did is: we manually set the editor windows to read-only. We tried two different ways: either by calling method SetStateFlags of IVsTextLines or by calling FindAndLockDocument of IVsRunningDocumentTable. Both work, but have an ugly side effect: when the file is already open in the editor in debug mode and you double-click on the file name in the solution/project explorer, you get a popup saying "The document ... is already open. Do you want to close it?".

    So: how can we get rid of this popup or is there another way to set editor windows to read-only during debugging that does not have this side-effect?

    By the way: the editor windows stay editable for both J. Davis' sample engine (http://archive.msdn.microsoft.com/debugenginesample) as well as for IronPythonTools.

    Thanks and best regards,

    Bernhard

All Replies

  • Thursday, August 02, 2012 8:09 AM
    Moderator
     
     

    Hi Bernhard,

    Thank you for posting in the MSDN Forum.
     
    I will involve some experts into this issue to see whether they can help you out. There might be some time delay, appreciate for your patience.
     
    Thank you for your understanding and support.
     
    Best regards,


    Ego [MSFT]
    MSDN Community Support | Feedback to us