Has anybody else found this the most annoying thing about .Net 2003, the NCB file becomes so flaming corrupt that none of the method calls are there for you to use when you dereference a pointer....
This is so annoying!!!!! I've tried deleting the NCB file and opening the solution again, but to no avail, I'd understand if there were errors in my source code, but this is ridiculous, or does this mean I rely on it too much!!!! At least its not as bad as Borland, as it junters a long loading the table up of the methods associated with a class!!!
Well I kinda got it working, but its in certain sections of the code that it don't like. Then some times it just doesn't work, according to the documentation it can sometimes become corrupt... Not a bad compiler though...
I could never get createDevice to show but I've pretty much remembered that off by heart now!!!
It stops working for me every time i use a core::aabbox in a method, after this, all lines in this method don't work with Intellisence. Commention out the line with the aabbox temporarily helps a lot. I have not figured out yet what VS doesn't like about the box, but if anybody has an idea..
I've been able to use aabbox, I think it must be a random thing, or your bad coding style Niko...
I think it might be something to do with cleaning your solution every now and then, and totally rebuilding the application. This is how I got it kinda working the other day, and numerous tries at deleting the .NCB...
Not a bad compiler though...
