vaindil
commented
6 years ago I came here from #1810. I did not have a file or folder called ComponentModelCache in the Extensions folder, so I assumed it was the folder one level up (at VisualStudio\15.0_xxxxx\ComponentModelCache). I renamed both that folder and the extensions.en-US.cache file, no error popup happened. I restarted VS just to check, and the popup still did not happen.
Looks like this fixes the problem. Let me know if you'd like me to test anything else. Thanks!
apobekiaris
meaghanlewis
ZoeyR
milanc
jcansdale
aravindk777
iSamuel51
We have been seeing many issues that involve missing MEF components, for example:
1826 GitHub Extension broken with VS 15.7.6
1810 SetSite failed for the package [GitHubPackage], VS 15.8 Preview 4/5
1812 Error On Project Load
Symptoms
These tend to manifest themselves as follows on the GitHub pane:
Or like this when opening a solution that's hosted on GitHub:
With an entry in the ActivityLog:
What's going on
Update from Daniel Griffen @dgriffen on Gitter.
This doesn't appear to be caused by a specific version of GitHub for Visual Studio or MEF component, but seems to be a
random corruption of the extension cachesee above.Simply clearing the MEF component cache or running
devenv.exe /updateConfigurationwon't repair the extension cache (which is usually what resolves missing MEF components).How to fix
Clearing the extension and MEF caches
The quickest way is to delete the following file and directory (where
15.0_xxxxxxxxcorresponds to a particular instance of Visual Studio):Deleting
extensions.en-US.cachecauses the extension cache to be recreated and deleting theComponentModelCachedirectory clears the MEF component cache.Reinstalling the extension
The alternative way is to uninstall and then re-install GitHub for Visual Studio.
This can be error prone when done manually because the
VSIX Installeroften appears behind other windows. It's easy to think the uninstall has completed when it hasn't even started. Perhaps we could provide a script for doing this?Automatic detection
Missing MEF components would be easy to detect during our package initialization. The
package did not load correctlydialog only appears because we don't handle an exception in our package initialization. At the very least we could point users to instructions on how to repair their extension cache.Automatic repair
It's easier to find the relevant cache files from inside an instance of Visual Studio that it is to find the correct instance-Guid and paths from an external script. It would be straightforward to detect suspected cache corruption and offer to perform an automatic repair.