Document.ActiveWindow does not return always the active window - by Carlos J. Quintero

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 781522 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 3/17/2013 8:45:56 AM
Access Restriction Public


When a toolwindow is active, calling DTE.ActiveDocument.ActiveWindow on a Form document doesn't return the active window of the document.
Sign in to post a comment.
Posted by Deon [MSFT] on 4/29/2014 at 12:29 PM
Thank you for reporting this issue. This issue has been fixed in Visual Studio 2013. You can install a trial version of Visual Studio 2013 with the fix from:
Posted by Carl [MSFT] on 6/25/2013 at 9:49 AM
Thanks for your feedback Carlos. You'll be happy to know that we have found the issue and will be including the fix in a coming release of Visual Studio.

Carl Brochu | Visual Studio Team
Posted by Radhika [MSFT] on 6/17/2013 at 10:36 AM

Thanks for the feedback. To help investigate this issue we'd like some more information. Do you have any VS Updates installed? Have you seen this repro consistently? What scenario are you trying to enable where this fails? Assuming this was working earlier, what was the last change made to your Visual Studio environment after which this stopped working?

Thanks for your help investigating this issue,

Radhika Tadinada
Program Manager
Visual Studio Platform
Posted by Carlos J. Quintero on 5/10/2013 at 12:51 PM
The problem still happens with Update2 of VS 2012 so keep the issue open in order to fix it.
Posted by Radhika [MSFT] on 5/10/2013 at 10:11 AM

Thanks for your feedback.  It's been a while since our last communication so as per 'Connect' guidelines we need to resolve and close this issue. Hopefully installing the latest VSUpdate will resolve the issue. Please reactivate or create a new Connect bug if the issue persists and we'd love to investigate it.

Apologies for any inconvenience this causes!

Radhika Tadinada
Program Manager
Visual Studio Platform
Posted by Carl [MSFT] on 5/2/2013 at 1:14 PM
Hi Carlos,

did you get a chance to try the latest VSUpdate2? We believe this scenario is improved in the latest Update available here:

Let us know if this helps
Carl Brochu | Visual Studio Team
Posted by Helen [MSFT] on 3/17/2013 at 11:42 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Helen [MSFT] on 3/17/2013 at 8:51 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(