Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
In a VS2010 package, I have a piece of code that calls FileCodeModel.CodeElements, when the caret position changes. Also I registered a handler in the CodeModelEvents bound to the document.
When the package monitors a C# project, it works OK. However, when monitoring a VB project, the FileCodeModel.CodeElements call fails with an COMException that corresponds to an E_FAIL error.
any ideas why the behavior is different?
The C# and VB.net code models are completely separate implementations that both have their associated quirks.
In VB.Net the caret position change is part of a larger set of events which can trigger the line commit logic in the IDE. I’m not really surprised that it throws in this particular event, especially if the buffer is dirty.
One way to possibly work around this is to wait util the idle event after the caret move and query
CodeElementsthere.