Help me get my VS2008 "go To Definition" back!?
February 3, 2011 11:49 AM Subscribe
"Go To Definition" Greyed out in VS2008...help get it back?!
I make extensive use of the "Go To Definition" context menu tool in VS2008...and as of this morning it's greyed out. I've tried reseting settings, uninstall and reinstall, etc. Nothing seems to work...anyone know of a fix?
I make extensive use of the "Go To Definition" context menu tool in VS2008...and as of this morning it's greyed out. I've tried reseting settings, uninstall and reinstall, etc. Nothing seems to work...anyone know of a fix?
Go To Definition, IIRC uses a database that is supposed to be updated after every build. This is the .ncb file. Close visual studio, delete that file, reopen the project, rebuild.
posted by plinth at 11:59 AM on February 3, 2011
posted by plinth at 11:59 AM on February 3, 2011
Response by poster: I should add that I'm using Visual SourceSafe...
posted by gnomicPerfect at 12:16 PM on February 3, 2011
posted by gnomicPerfect at 12:16 PM on February 3, 2011
Every source file you open from the Solution Explorer? When this happens to me it is usually because the file isn't actually in the solution, it is a history version from TFS or something I opend in windows explorer that is just being displayed in VS.
posted by Ad hominem at 12:36 PM on February 3, 2011
posted by Ad hominem at 12:36 PM on February 3, 2011
Response by poster: I don't open from Solution explorer. I open from SourceSafe....
I'm really new to this job and to VS in general...I'm more of a LAMP/Python linux sort normally....
...the other programmer here opens her stuff from VSS and it works fine, so I'm not sure why this would be a problem...?
posted by gnomicPerfect at 1:08 PM on February 3, 2011
I'm really new to this job and to VS in general...I'm more of a LAMP/Python linux sort normally....
...the other programmer here opens her stuff from VSS and it works fine, so I'm not sure why this would be a problem...?
posted by gnomicPerfect at 1:08 PM on February 3, 2011
Best answer: Ok, when I open a random file from source control, it loads into visual studio but in a barebones text editor mode. Vs does not know what solution the file belongs to so it can't compile the data for "go to definition". If I open the .sln (solution) file from source control it will load all of the files from the solution into the solution explorer. Then when I open any files from that solution from sorce control( not by double clicking on solution explorer) it knows what solution that file belongs to and enables "go to definition"
tl;dr open the .sln file first.
posted by Ad hominem at 1:21 PM on February 3, 2011
tl;dr open the .sln file first.
posted by Ad hominem at 1:21 PM on February 3, 2011
Response by poster: thanks sorry to be such a n00b
posted by gnomicPerfect at 1:31 PM on February 3, 2011
posted by gnomicPerfect at 1:31 PM on February 3, 2011
Np sorry for the typos, I actually surf on my phone while I compile.
posted by Ad hominem at 1:36 PM on February 3, 2011
posted by Ad hominem at 1:36 PM on February 3, 2011
« Older How to deal with a relationship gone wrong at work... | Please Kindle my Blog Reading Newer »
This thread is closed to new comments.
posted by hjd at 11:58 AM on February 3, 2011