>>>HI
>>>
>>>in visual studio 2008 I am following through code by right clicking on a piece of code and selecting go to definition. This jumps me to where that procedure (or whatever I should call it) is written.
>>>Is there any way of jumping back fro that location. Like a back button on a browser.
>>>
>>>Barring that what would be the best way to follow through code in VS2008
>>
>>Look at Bookmarks (Edit/Bookmarks). The basic short cuts are straightforward. Ctrl-K,K to toggle, Ctrl-K+N : next, Ctrl-K+P :previous
>>(Disclaimer: I'm on VS2010 but AFAIR it was the same in 2008)
>
>Thanks Viv .
>
>I've given up on the moving site for now as it seemed to be eating time. Its one of those areas where I can't believe how hard it is to put my finger on the problem. .

I know how you feel! I just moved one project (not a main one - just one of its dependencies) and changed one namespace. The first compile came up with over 80 errors (Before you ask, No - there were none before :-} ) But the trick is to winnow through those errors and identify the real culprits that all the others flow from. I think I had to only make three actual changes before it all fell into place again. The compiler error messages can appear long and confusing but are actually pretty exact. Another trick is to build the projects individually starting with the 'low level' ones which have fewer dependencies - make sure they compile without error before moving on to projects that depend on them.

Of course if you follow the defaults when creating a solution then all related projects are automatically placed in sub-folders of the main folder and, because all those paths are relative, the whole thing can be transferred to a different folder, different drive or different machine without problems. But that strategy, which works great with, say, source control, is exactly what causes the problems when you aren't following the default layout...