Visual Studio .NET 2003 Interesting Problem

[Adam Hartshorne]

Hi All,

I have an interesting problem with the aforementioned IDE. I am using an
external library, wildmagic to be precise. I was using version 2 of this
library and have just moved to version 3.

Ok so I changed the paths to point at version 3, and deleted all source,
header, lib and dll files for version 2.

To my surprise when I do the . the list of methods available is still
those of version 2, even though some of those methods are not available
in version 3. Initially I thought I had forgotten to change a path or
delete an instance of the version 2 library, however I can call methods
from the version 3 library that do not exist in version 2, and the
program compiles and run fine. Additionally if I try to call the version
2 methods which visual studio suggests exist with a particular class
that are not available in version 3 compilation errors occur.

Therefore I am 100% sure that I have the paths etc setup for version 3,
but for some weird reason visual studio seems to have a list of methods
from classes in version 2. Does visual studio buld some sort of weird
list that needs erasing or forcing to change?

Adam

[dirk]

Perhaps you should delete the .ncb file in your solution dir.

"Adam Hartshorne" <or********@yahoo.com> wrote in message
news:cu**********@wisteria.csv.warwick.ac.uk...

Hi All,

I have an interesting problem with the aforementioned IDE. I am using an
external library, wildmagic to be precise. I was using version 2 of this
library and have just moved to version 3.

Ok so I changed the paths to point at version 3, and deleted all source,
header, lib and dll files for version 2.

To my surprise when I do the . the list of methods available is still
those of version 2, even though some of those methods are not available
in version 3. Initially I thought I had forgotten to change a path or
delete an instance of the version 2 library, however I can call methods
from the version 3 library that do not exist in version 2, and the
program compiles and run fine. Additionally if I try to call the version
2 methods which visual studio suggests exist with a particular class
that are not available in version 3 compilation errors occur.

Therefore I am 100% sure that I have the paths etc setup for version 3,
but for some weird reason visual studio seems to have a list of methods
from classes in version 2. Does visual studio buld some sort of weird
list that needs erasing or forcing to change?

Adam

[SirMike]

dirk wrote:

Perhaps you should delete the .ncb file in your solution dir.

Or even all additional files created by VS in solution dir and try to
rebuild the project.

--
the code is my strength
SirMike

[Richard Cavell]

On 16/2/05 12:24 AM, Adam Hartshorne wrote:

Therefore I am 100% sure that I have the paths etc setup for version 3,
but for some weird reason visual studio seems to have a list of methods
from classes in version 2. Does visual studio buld some sort of weird
list that needs erasing or forcing to change?

Yes. Get rid of the .clw file. This class wizard view is something
your IDE does to be helpful. It's not the compiler that's doing that.