It's a known bug (I don't have the KB or connect link at hand). I
believe it is due to roaming profiles (i.e. it can be worked around by
not using roaming profiles). Why it wasn't fixed by the SP I don't
know.
I also am not sure if there is a good answer to get it to use the
existing settings that
--
I work on a few different machines (real and virtual) and the first time I use
Visual Studio 2008 on a machine, I get the whole "Visual Studio is starting for
the first time" thing, and have to choose what language I want to code in, and
all my settings are reset (including, annoyingly, intel
