Visual Studio and .NET Framework Home
EnvDTE.SelectionEvents.OnChange event does not fire when more than two nodes are already selected in the Solution Explorer of Visual Studio
Carlos J. Quintero
as Won't Fix
4/9/2007 5:00:32 AM
User(s) can reproduce this bug
The OnChange event of the EnvDTE.SelectionEvents class fires each time you select something different in the IDE. For example, if you multi-select a second file in the Solution Explorer, the event is fired. However, it does not fire when you multi-select a third item in the Solution Explorer.
Visual Studio 2005 (All Products and Editions) Service Pack 1
Windows XP Professional
Operating System Language
Steps to Reproduce
- Open the Macros IDE, go to the EnvironmentEvents file, select the SelectionEvents item in the combobox to the left and the OnChange event in the combobox to the right. This creates the event handler for that event. Add this code:
Public Sub SelectionEvents_OnChange() Handles SelectionEvents.OnChange
- Go back to the Visual Studio IDE and create a project.
- Expand the References node in the Solution Explorer.
- Select a reference in the Solution Explorer and notice that the SelectionEvents.OnChange event is fired (you see the message box).
- Multi-select (with the Ctrl key) a second reference and notice that the event is fired again. Now you have two items selected.
- Multi-select a third reference
The event is not fired this time.
The event should be fired
TAP Code (if applicable)
You can indicate your satisfaction with how Microsoft handled this issue by completing this quick
3 question survey
to post a comment.
Please enter a comment.
on 4/18/2007 at 12:35 PM
Thanks for reporting this issue. Unfortunately we will not have time to address this in the upcoming release of Visual Studio (codename "Orcas") but we are tracking this bug in an internal database to address in the following version.
The Visual Studio IDE Team
on 4/10/2007 at 2:45 AM
Thanks for your feedback. We have reproduced this bug on Visual Studio 2005 SP1, and we are sending this bug to the appropriate group within the VisualStudio Product Team for triage and resolution.
Visual Studio Product Team.
on 4/9/2007 at 6:03 AM
Thank you for your feedback. We are currently investigating. If this issue is urgent, please call support directly (see http://support.microsoft.com).
Visual Studio Product Team
to post a workaround.
Please enter a workaround.
© 2014 Microsoft