Class View bug - fyi

[lactaseman]

I have just started spending serious time in the new studio 2005
C++/CLI arena writing some code assembly that will attache to a much
larger C# caode base. In keeping with the highly used namespaces in
C#, I have been making sure I organise my interfaces and class into
correct namespaces.

....However, I have run into a situation where when I renamed a
namespace in the code, the "Class View" window would not release the
old namespace name nor recognise the new name.

To make a long story short, after searching for this issue in the
groups and trying a a number of different things including removing
files (and deleting) from the project, recompiling, etc., the only way
I found to resolve this was to:

1) Close studio
2) delete the debug folders
3) delete aps and ncb files
4) reopen the solution and let it rebuild the class view

Not sure which files actually had to be removed... not sure if I care.
I am already edgy about C++/CLI not supporting the Class Designer... I
know they had trouble integrating it into VC and they had to pick and
choose their battles, but hey! I have no interrest in flaming C#, but
to me, moving away from 2005's VC (which now rocks with the new
language mods) to C# would be a step down.

....sorry about the rant at the end.

Tony

[Carl Daniel [VC++ MVP]]

la********@gmail.com wrote:

I have just started spending serious time in the new studio 2005
C++/CLI arena writing some code assembly that will attache to a much
larger C# caode base. In keeping with the highly used namespaces in
C#, I have been making sure I organise my interfaces and class into
correct namespaces.

...However, I have run into a situation where when I renamed a
namespace in the code, the "Class View" window would not release the
old namespace name nor recognise the new name.

To make a long story short, after searching for this issue in the
groups and trying a a number of different things including removing
files (and deleting) from the project, recompiling, etc., the only way
I found to resolve this was to:

1) Close studio
2) delete the debug folders
3) delete aps and ncb files
4) reopen the solution and let it rebuild the class view

Not sure which files actually had to be removed... not sure if I care.
I am already edgy about C++/CLI not supporting the Class Designer... I
know they had trouble integrating it into VC and they had to pick and
choose their battles, but hey! I have no interrest in flaming C#, but
to me, moving away from 2005's VC (which now rocks with the new
language mods) to C# would be a step down.

...sorry about the rant at the end.

Please post a bug report at http://lab.msdn.microsoft.com/productfeedback
and post the URL to the bug report here so that others can valdiate and vote
on it.

Mostly likely, all you needed to do is delete the .ncb file. NCB stands for
"No Compile Browser" aka Class View and Intellisense.

Personally, I don't miss the class designer in C++. It's nice in C#, but
even there it's so limited that I'm constantly switching back & forther
between the diagram and the code - it'd be even worse in C++ since the class
designer has no ability to deal with separation of interface and
implementation, or any C++ language features that don't map directly to C#
(e.g. template, free functions).

What is absolutely wonderful in C# (especially in 2005) is having
Intellisense that's 99.99% accurate. Intellisense in VC++ 2005 has come a
long way, but it's not up to the level of C# or VB yet.

-cd

[William DePalo [MVP VC++]]

<la********@gmail.com> wrote in message
news:11**********************@i40g2000cwc.googlegr oups.com...

1) Close studio
2) delete the debug folders
3) delete aps and ncb files
4) reopen the solution and let it rebuild the class view

Not sure which files actually had to be removed... not sure if I care.

When Intellisense stops working correctly for me I often have luck closing
the solution and deleting the .ncb file.

Regards,
Will