Willy's Reflections - Visual Studio ALM Rangers

| Willy-Peter Schaub | Visual Studio ALM Rangers | In search of IT simplicity, quality and tranquility |

If you have problems with TFS or Visual Studio flush the user cache … or not?

If you have problems with TFS or Visual Studio flush the user cache … or not?

Rate This
  • Comments 13

Updated 2010-09-22 ... changes in blue italic.

BUT … before you go down this “drastic” route, please get a cup of coffee and think about pressing the Enter key.

WHY … The side effects are that your personal environment resets to default and many, if not all, the Visual Studio extension  have to be re-installed. The worst side effect, unless you are Swiss and keep everything documented to the nth degree, is that the Team Foundation Server and Collection configuration evaporates during the user data reset.

With many problems, such as the infamous Red X issue, the common resolution is often to flush the local cache by completing the following steps:

  1. Delete the contents from the following folders
    • C:\Users\<<Your Alias>>\AppData\Local\Microsoft\Team Foundation
    • C:\Users\<<Your Alias>>\AppData\Local\Microsoft\VisualStudio
    • C:\Users\<<Your Alias>>\AppData\Local\Microsoft\VSCommon
  2. Go to the Visual Studio IDE folder in command prompt and Run the following command "devenv /resetuserdata" from the Visual Studio IDE folder.
    • Typical location for 62 bit: C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE
    • Typical location for 32 bit: C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE

While this feature has its place, it needs to be used with some pre-Enter-Key thought and planning, and anyone recommending this to anyone should also highlight the side effects … or face a VERY unhappy customer.

To minimise the potential loss of your personal environment, you should consider creating a backup of your environment using the Export Settings wizard, and the Import Settings wizard to restore the settings if and when needed.

… loaned from book “Software Engineers on their way to Pluto”, symbolizing the possible side effects :)

  • I read this as time for the Rangers to dig through the API, call some friends for some undocumented info and build a tool which gives you two options:

    1) Clean cache & keep settings

    2) Reset everything

  • From a Ranger to Ranger ... yes :)

  • Thanks a lot! This saved me a lot of time.

  • Thank to you, I think I saved lots of days spending how to reconfigure my solution to another TFS while old one was completely removed.

  • Worked like a charm :)

  • Just when I was about to give up..thanks:)

  • Worked for me. Thanks Willy.

  • Thanks! Helped me solve this following error which was probably caused by cached areas:

    "An error occured while running the selected "Available Work Items" query: TF51011: The specified area path does not exist. The error is caused by 'My project\General'"

  • It breaks me whole Visual Studio.

  • Just a thought (silly as it may be) Put the disclaimer above the command.

    For someone going step by step quickly through, I had already run the command before I got to the disclaimer.

    I didn't have anything important set up, but someone else might.

  • Good point ... done!

  • Whew! Thanks! Got it!

  • The cache pattern is supposed to make things quicker but is does not. It makes things much less reliable and makes me spend most of my time finding which broken cache to empty. Can all software engineers please stop attempting to implement caches.

Page 1 of 1 (13 items)
Leave a Comment
  • Please add 5 and 5 and type the answer here:
  • Post