Hi Parag,

Currently, we are looking into this problem. We will update you as soon as
we get anything out.

Thanks for your understanding!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Parag,

I have consulted this issue with our corresponding develop team members,
their opinion is as follows:

There may be misunderstanding, it sounds as if you are implementing the
IVsCodeDefView interface, which should only be implemented by the Code Def
Win service.

The Code Def Win is available as a service which implements IVsCodeDefView.
VSCore implements this service (and interface).  The service can be
obtained using QueryService(SID_SVsCodeDefView).  Those who want to push
context to the Code Def Win need to implement a context object, which
implements IVsCodeDefViewContext, and hand it to the service using
IVsCodeDefView::SetContext(pIVsCodeDefViewContext).  They push context in
this manner whenever it changes, for example on selection or insertion
point change in the editor.

If the Code Def Win UI (tool window) is visible, every idle it checks
whether there is a new context pushed to the service.  If so, it picks up
the latest context and presents it.  If you are pushing context as
described above and the context is not changing, it is possible that
something is starving the Code Def Win UI of idle processing time.

Wish it helps!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.