Problem with Class Viewer

  • Thread starter Thread starter Peteroid
  • Start date Start date
P

Peteroid

I changed the name of a method in the editor while looking at it in the
Class Viewer. Now the Class Viewer can't see the new name ans still sees the
old name. This is reflected in the bars at the top that let you editor-jump
to a particular method in your class. This tool also thinks the old name is
there and the new name isn't, and jumps to a wierd location in the source
when I click on it. Now anything below the point the old named method was is
also not being jumped to or recognized correctly.

I'm afraid my source is being corrupted somehow. It still compiles and runs
just fine. Breakpoints work. But for how long?

I've tried copying the source, creating a new header file, copy the contents
into blank header file, remove old header file, rename new one to old name.
It still compiles, but it still has name-confusion problem (it remembers).
I've tried cleaning and rebuilding. I've tried closing and opening the
project. I've even tried a hard re-boot of the computer. No problems except
name-confusion problem.

Like I said, this is not causing any problems (so far), but is scary. Is
this a known problem?

For context, I'm programming using MS VS C++.NET 2005 Express in /clr mode.

[==P==]
 
I was able to solve the problem by renaming the header file itself, and then
rebuilding. The various other files that used the old name now complained,
and I manually changed each one of their names to the new file name. When it
compiled the class viewer had the correct info.

Still this is obviously a bug. Is it known, or should I report it somehow?

[==P==]
 
I was able to solve the problem by renaming the header file itself,
and then rebuilding. The various other files that used the old name
now complained, and I manually changed each one of their names to the
new file name. When it compiled the class viewer had the correct info.

Still this is obviously a bug. Is it known, or should I report it
somehow?
Click to expand...

Yes, that would be a bug. Please report it at:
http://msdn.microsoft.com/productfeedback

Thanks,
 
Back
Top