ClassView, Object Browser problems
-
Is anyone else having this problem with VS.NET IDE? I can't navigate my source code using Class View or the object Browser.
- In VS.NET, create a new project. Choose Win32 Project. Call it Foo.
- In the ClassView pane, double-click on "InitInstance". The editor window will open Foo.cpp and highlight the word "InitInstance" on the first line of the definition of InitInstance. So far so good.
- In the editor window, type <Ctrl+Home> to move the caret to the top of the buffer.
- Now double-click on any function or variable name in Class View. The caret in the editor window remains at the top of the buffer rather than moving to the definition of the symbol you chose in Class View.
- The same sort of problem occurs if you right-click on a function in ClassView and select "Go to definition" or "Go to declaration".
- If you enable Browse information and build the project, the same behaviour occurs for Go to definition or Go to declaration in the browser window.
- Using the combo boxes on top of the editor window, you can navigate properly (choosing a function name does cause the editor to highlight the function definition and move the caret to the correct place.
- Closing the IDE, deleting foo.ncb, and reopening the IDE does not resolve this problem.
- Rebooting does not resolve this problem.
This reproduces 100% on my machine, at least for yesterday and today. Can others reproduce this behaviour? It doesn't seem to appear in the VS.NET bug list at http://support.microsoft.com/common/canned.aspx?r=d&H=Documented%20Bugs%20in%20Visual%20Studio%20.NET&LL=kbvsnetsearch&Sz=kbbug%20and%20not%20kbnetfssd[^], so I have submitted it (Thanks, Nick, for getting the bug-report page fixed). Can't I just get upset without having to think about what I'm really upset about? Six Feet Under
-
Is anyone else having this problem with VS.NET IDE? I can't navigate my source code using Class View or the object Browser.
- In VS.NET, create a new project. Choose Win32 Project. Call it Foo.
- In the ClassView pane, double-click on "InitInstance". The editor window will open Foo.cpp and highlight the word "InitInstance" on the first line of the definition of InitInstance. So far so good.
- In the editor window, type <Ctrl+Home> to move the caret to the top of the buffer.
- Now double-click on any function or variable name in Class View. The caret in the editor window remains at the top of the buffer rather than moving to the definition of the symbol you chose in Class View.
- The same sort of problem occurs if you right-click on a function in ClassView and select "Go to definition" or "Go to declaration".
- If you enable Browse information and build the project, the same behaviour occurs for Go to definition or Go to declaration in the browser window.
- Using the combo boxes on top of the editor window, you can navigate properly (choosing a function name does cause the editor to highlight the function definition and move the caret to the correct place.
- Closing the IDE, deleting foo.ncb, and reopening the IDE does not resolve this problem.
- Rebooting does not resolve this problem.
This reproduces 100% on my machine, at least for yesterday and today. Can others reproduce this behaviour? It doesn't seem to appear in the VS.NET bug list at http://support.microsoft.com/common/canned.aspx?r=d&H=Documented%20Bugs%20in%20Visual%20Studio%20.NET&LL=kbvsnetsearch&Sz=kbbug%20and%20not%20kbnetfssd[^], so I have submitted it (Thanks, Nick, for getting the bug-report page fixed). Can't I just get upset without having to think about what I'm really upset about? Six Feet Under
Jonathan -- I tried and can't reproduce this using your steps (1-4) in either VC++ 2002 or 2003. On my machine the behavior is "correct". Anyone else? Nick This posting is provided “AS IS” with no warranties, and confers no rights. You assume all risk for your use. © 2002 Microsoft Corporation. All rights reserved.
-
Jonathan -- I tried and can't reproduce this using your steps (1-4) in either VC++ 2002 or 2003. On my machine the behavior is "correct". Anyone else? Nick This posting is provided “AS IS” with no warranties, and confers no rights. You assume all risk for your use. © 2002 Microsoft Corporation. All rights reserved.
Thanks. I just have the one machine, so it's hard to tell what's universal and what's a quirk of my machine. I guess it's time to uninstall/reinstall and see if the problem goes away. Why couldn't Science, in the long run, serve As well as one's uncleared lunch-table or Mme X en Culottes de Matador? James Merrill
-
Is anyone else having this problem with VS.NET IDE? I can't navigate my source code using Class View or the object Browser.
- In VS.NET, create a new project. Choose Win32 Project. Call it Foo.
- In the ClassView pane, double-click on "InitInstance". The editor window will open Foo.cpp and highlight the word "InitInstance" on the first line of the definition of InitInstance. So far so good.
- In the editor window, type <Ctrl+Home> to move the caret to the top of the buffer.
- Now double-click on any function or variable name in Class View. The caret in the editor window remains at the top of the buffer rather than moving to the definition of the symbol you chose in Class View.
- The same sort of problem occurs if you right-click on a function in ClassView and select "Go to definition" or "Go to declaration".
- If you enable Browse information and build the project, the same behaviour occurs for Go to definition or Go to declaration in the browser window.
- Using the combo boxes on top of the editor window, you can navigate properly (choosing a function name does cause the editor to highlight the function definition and move the caret to the correct place.
- Closing the IDE, deleting foo.ncb, and reopening the IDE does not resolve this problem.
- Rebooting does not resolve this problem.
This reproduces 100% on my machine, at least for yesterday and today. Can others reproduce this behaviour? It doesn't seem to appear in the VS.NET bug list at http://support.microsoft.com/common/canned.aspx?r=d&H=Documented%20Bugs%20in%20Visual%20Studio%20.NET&LL=kbvsnetsearch&Sz=kbbug%20and%20not%20kbnetfssd[^], so I have submitted it (Thanks, Nick, for getting the bug-report page fixed). Can't I just get upset without having to think about what I'm really upset about? Six Feet Under
-
Thanks. I just have the one machine, so it's hard to tell what's universal and what's a quirk of my machine. I guess it's time to uninstall/reinstall and see if the problem goes away. Why couldn't Science, in the long run, serve As well as one's uncleared lunch-table or Mme X en Culottes de Matador? James Merrill
Spent 3 hours(!) running "Repair installation" and still I see the same thing. I guess it's just one of those mysteries that I'll have to live with. If anyone has any thoughts about how to diagnose and resolve a problem like this, I would be grateful to hear about it, but my guess is that it's just an obscure bug in VS.NET. Fortunately it only slows me down but does not stop me from getting work done.