Jan 262015

Reticle with ComponentModelCache Folder

Several times in the past few months, I have experienced an error loading a solution in Visual Studio 2013 that goes something like:

“The ‘<packagename>’ package did not load correctly.”

Every time that I have had this error, the solution has been to go to the “C:\Users\<user>\AppData\Local\Microsoft\VisualStudio\12.0 folder and delete the ComponentModelCache folder.

I suspect that the contents of the cache folder get corrupted and/or out of sync when the OS shuts down unexpectedly while Visual Studio 2013 is up.  It’s annoying, but deleting the ComponentModelCache forces Visual Studio to load without the cache and fixes the problem every time.

  2 Responses to “ComponentModelCache – The Root of All Solution Loading Evil”

  1. This is super annoying. It happens somewhat frequently to me as well. No reboots or system hangs. Just VS decides to puke on the cache. Really frustrating to have to close 5 instances because one decided to crap out.

    Deleting this folder doesn’t feel like an actual fix. I have actually thought about changing my shortcut to a script that will delete the folder prior launch… but then it makes things take longer to load while it rebuilds the cache. I don’t like this solution either.

  2. Four *YEARS* later, VS 2017 is still crashing for this same reason.
    Gee, thank MS!

 Leave a Reply



You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>