Not Monitored
Tag not monitored by Microsoft.
39,334 questions
Debugger Extension - Unable to load source in VS2022
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(144, 30%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
Sajith
11
Reputation points
We are trying to update a debugger extension to VS2022. Debugger works fine in VS2019.
But after updating to VS2022, when execution breaks at a breakpoint, we don't get a call to IVsProject3.OpenItem to open the file.
So this results in showing 'Frame not in module' error.
IDebugStackFrame2 methods - GetDocContext and GetCodeContext get called on the debugger side and these are processed correctly,
document moniker is passed correctly.
But after this, we get a call to IVsProject3.OpenItem in VS2019 and not in VS2022.
Is there a new requirement for debugger extension in VS2022, any new interface that needs to be implemented?
Because IVsProject3.OpenItem is not getting called to open the source file, is there anything that additionally needs to be implemented or handled in the
Project, Debugger or Language Service?
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(249.60000000000002, 10%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAX%3C/text%3E%3C/svg%3E)
Anna Xiu-MSFT 29,096 Reputation points Microsoft Vendor2022-03-28T10:16:44.267+00:00 Hi, the latest version of VS2022 is version 17.1.2. Can you try it again in latest Visual Studio 2022?
-
Sajith 11 Reputation points
2022-03-29T17:47:11.243+00:00 Hi Anna,
I have updated VS2022 to 17.1.2, but the issue exists there also.More info on the issue-
We are creating the document window using - IVsUIShell.CreateDocumentWindow
There is no error on opening the window first time.
If the document window is open and then click on a frame in the callstack window, this gives 'Frame not in module' error even though, we have correctly
passed the moniker name from IDebugStackFrame2 methods and the document is already open in VS IDE.If we again close the already opened document and then try to navigate to source from call stack window, it works fine.
Once we return the stack frame from IDebugStackFrame2 what is the sequence of calls expected in VS2022 ?
This works fine in VS2019.
When debugging the major difference or issue found in VS2022 is IVsTextLines.CreateLineMarker never gets called
and IVsProject3.OpenItem does not get called if the document is already open.Thanks,
Sajith
Sign in to comment
Sign in to answer