hints on using vim for larger projects

run ctags with --extra=+f
so you'll have additional feature of searching files across entire project, with tab completion on filenames, etc (e.g. using :tag command)
the only disadvantage here is that last editing position of the file, opened with :tag, will not be preserved.
in general, that's what you'd get using alt+shift+O from visual studio with visual assist x addon.

you should definitely install taglist plugin. i don't find myself using it very frequently, but _sometimes_ it is very helpful.
it is bound to F3 key here.

if you need to use different IDE's with their proprietary project files - usually you can write a wrapper (calling devenv.com, or whatever), and use single Makefile, and :mak vim command.
most of our team uses visual studio + codewarrior + radix, in order to build and run on 4 different platforms, while i'm using single instance of vim running in xterm for all of this. i can build the app for any platform, for either debug or release mode, run it, and interrupt it when i'd like to. everything on hotkeys. of course, the only way it's possible on windows is using cygwin.
the only times when i need to run visual studio or radix is when i need a debugger, and that's quite rare case for me.

i use following hotkeys:
F9 - build (as simple as :mak) for current platform/buildtype (e.g. PC/debug, or XBOX/release)
F5 - run pc debug build
F6 - run wii debug build
S-F6 - stop wii executable (we don't need such a hotkey for pc, because we can use C-c for this)
... and so on ...

platform/buildtype is selectable in a Makefile itself (i only need to change no more than a single line or 2 usually)
of course, YOU can configure it with environment variables, or magic spells.

usually you'll be working in different source trees during even a single day.
e.g. main project and tools for it can be stored in a separate source control repositories, etc
so you'll need a mechanism of setting an 'execution' scripts and 'stopping' scripts on a per-project or a per-directory basis.
i do it using simple shell scripts, called .exec1, .stop1, .exec2, .stop2, ... etc, placed in the directory they were supposed to run from.
then i bind 'em to vim hotkeys:
nmap :!sh .exec1
nmap :!sh .stop1
nmap :!sh .exec2
nmap :!sh .stop2

of course, everything is easier, if build tools are built on something like Jamfiles, instead of just using native proprietary formats, like vcproj.

... hope to continue writing on the topic ...