Corrupt extension cache and missing MEF exports #1859
Comments
|
I came here from #1810. I did not have a file or folder called Looks like this fixes the problem. Let me know if you'd like me to test anything else. Thanks! |
|
I had to reboot my computer for something unrelated, after the reboot I'm getting the popup again. |
|
same here reboot restored the bad behaviour |
|
Thanks for letting us know @vaindil and @apobekiaris. We're going to have to look into this issue more to understand what is going wrong. |
|
@vaindil @apobekiaris Can I get some extra information from you to try and diagnose this problem?
I can't reproduce this issue locally so I'm trying to eliminate any variables I can. |
|
@dgriffen Here's the output from doing Help > About Visual Studio > Copy Info. I believe I originally installed the GitHub extension from the marketplace, but I'm not certain of that. |
|
Microsoft Visual Studio Enterprise 2017 Installed Version: Enterprise Architecture Diagrams and Analysis Tools 00369-60000-00001-AA601 Visual C++ 2017 00369-60000-00001-AA601 ASP.NET and Web Tools 2017 15.8.05067.0 ASP.NET Core Razor Language Services 15.8.31590 ASP.NET Web Frameworks and Tools 2017 5.2.60618.0 Azure App Service Tools v3.0.0 15.8.05023.0 BusinessObjectEditor 1.0 C# Tools 2.9.0-beta8-63208-01 Clear MEF Component Cache 1.4 Common Azure Tools 1.10 ConvertToDevExtremeCommand Extension 1.0 DevExpress.DeploymentTool 1.0 DevExpress.ExpressApp.Design.DynamicPackage 1.0 DevExpress.ExpressApp.DesignPackage 1.0 DevExpress.Win.LayoutAssistant Extension 1.0 DevExpress.XtraReports.RepxPackage 10.0 DevExtreme.Design 17.1.7 GitHub.VisualStudio 2.5.5.3618 JavaScript Language Service 2.0 JavaScript Project System 2.0 JetBrains ReSharper Ultimate 2018.1.4 Build 112.0.20180731.142027 JustDecompilePackage2017 Extension 1.0 Merq 1.1.38 (5b3c069) Microsoft Azure Tools 2.9 Microsoft Continuous Delivery Tools for Visual Studio 0.4 Microsoft JVM Debugger 1.0 Microsoft Library Manager 1.0 Microsoft MI-Based Debugger 1.0 Microsoft Visual C++ Wizards 1.0 Microsoft Visual Studio Tools for Containers 1.1 Microsoft Visual Studio VC Package 1.0 MLGen Package Extension 1.0 Mono Debugging for Visual Studio 4.11.7-pre (8955b2a) NuGet Package Manager 4.6.0 ProjectServicesPackage Extension 1.0 ResourcePackage Extension 1.0 ResourcePackage Extension 1.0 SQL Server Data Tools 15.1.61808.07020 TestDriven.Net 4.1-Alpha TypeScript Tools 15.8.20801.2001 Visual Basic Tools 2.9.0-beta8-63208-01 Visual F# Tools 10.2 for F# 4.5 15.8.0.0. Commit Hash: c55dd2c3d618eb93a8d16e503947342b1fa93556. Visual Studio Code Debug Adapter Host Package 1.0 Visual Studio Tools for CMake 1.0 Visual Studio Tools for Containers 1.0 Visual Studio Tools for Universal Windows Apps 15.0.28010.00 VisualStudio.Mac 1.0 VSPackage Extension 1.0 Xamarin 4.11.0.732 (d15-8@33e83e124) Xamarin Designer 4.14.218 (79f535bdd) Xamarin Templates 1.1.113 (e1d02a7) Xamarin.Android SDK 9.0.0.18 (HEAD/3d8a28f1a) Xamarin.iOS and Xamarin.Mac SDK 11.14.0.13 (373c313) XtraReports package 1.0 |
|
i think I got mine from previous github issue |
|
I have updated my VS yesterday to 15.8.0 had no issues. Using option to revert to previous version (2.5.2.2500) helped and extension was fixed. |
Don't specify a target Visual Studio version for the GitHub.TeamFoundation.15 MEF assembly. Specifying a TargetVersion was causing it to sometimes incorrectly be excluded when installed on some Visual Studio 2017 versions. We can leave TargetVersion on the GitHub.TeamFoundation.14 MEF assembly because this attribute isn't supported on Visual Studio 2015 and we do want it excluded on Visual Studio 2017. This is a workaround for #1859.
Don't specify a target Visual Studio version for the GitHub.TeamFoundation.15 MEF assembly. Specifying a TargetVersion was causing it to sometimes incorrectly be excluded when installed on some Visual Studio 2017 versions. We can leave TargetVersion on the GitHub.TeamFoundation.14 MEF assembly because this attribute isn't supported on Visual Studio 2015 and we do want it excluded on Visual Studio 2017. This is a workaround for #1859.
|
@vaindil, @apobekiaris, @milanc thanks for the reports everyone! I'm back from holiday and have a new PR (#1875) with a fix. This time I'm pretty optimistic that we understand what's going on and the fix will resolve the issue. You can find the .vsix here: We're getting very close to a new release, so any reports, positive or negative would be much appreciated. If you could comment on the PR itself (#1875) that would be great! |
|
That task invokes devenv directly so it will use the correct version of VS. My guess is that the task had an issue running /updateConfiguration so the next time VS launched it had to rebuild its cache. |
|
Not sure if this is the right forum for the same issue as i see it as closed but it doesnt look to be so. Nor that i could get to see a solution discussed. so, i have the VS 2017 on Windows 7. I recently updated the Github extension for VS from marketplace with the current VS version. Info below: Installed Version: Enterprise Microsoft Visual Studio Tools for Applications 2017 00369-90253-49770-AA943 Application Insights Tools for Visual Studio Package 8.13.10627.1 ASP.NET and Web Tools 2017 15.8.05085.0 ASP.NET Core Razor Language Services 15.8.31590 ASP.NET Web Frameworks and Tools 2012 4.0.30625.0 ASP.NET Web Frameworks and Tools 2017 5.2.60618.0 Azure App Service Tools v3.0.0 15.8.05023.0 Azure Data Lake Node 1.0 Azure Data Lake Tools for Visual Studio 2.3.3000.2 Azure Functions and Web Jobs Tools 15.8.05023.0 Azure Stream Analytics Tools for Visual Studio 2.3.3000.2 C# Tools 2.9.0-beta8-63208-01 Common Azure Tools 1.10 GitHub.VisualStudio 2.5.6.4958 JavaScript Language Service 2.0 JetBrains ReSharper Ultimate 2018.2.3 Build 182.0.20180912.70621 Microsoft Azure HDInsight Azure Node 2.3.3000.2 Microsoft Azure Hive Query Language Service 2.3.3000.2 Microsoft Azure Stream Analytics Language Service 2.3.3000.2 Microsoft Azure Stream Analytics Node 1.0 Microsoft Azure Tools 2.9 Microsoft Continuous Delivery Tools for Visual Studio 0.4 Microsoft JVM Debugger 1.0 Microsoft Library Manager 1.0 Microsoft MI-Based Debugger 1.0 Microsoft Visual Studio Tools for Containers 1.1 NuGet Package Manager 4.6.0 Project 1.0 ProjectServicesPackage Extension 1.0 Redgate ReadyRoll 1.17.18155.10346 Visit https://www.red-gate.com/readyroll for more information. Copyright (C) 2011 Red Gate Software Ltd. All rights reserved. This software contains components from Component Owl. ReadyRoll contains code from the following open source software: NuGet https://www.nuget.org/ This product contains icons from http://www.visualpharm.com distributed under a free backlink license. For license details or other notices relating to the above software, please see NOTICE.TXT and EULA.rtf in the ReadyRoll application folder. Redgate SQL Prompt 9.3.0.6627 ResourcePackage Extension 1.0 ResourcePackage Extension 1.0 Snapshot Debugging Extension 1.0 SQL Server Analysis Services 14.0.1016.285 SQL Server Data Tools 15.1.61808.07020 SQL Server Integration Services SQL Server Reporting Services 14.0.1016.285 SsmsVsIntegration 1.0 ToolWindowHostedEditor 1.0 TypeScript Tools 15.8.20822.2001 Visual Basic Tools 2.9.0-beta8-63208-01 Visual F# Tools 10.2 for F# 4.5 15.8.0.0. Commit Hash: 55a3dc3231c95c77f81ee53f7d29152029da7408. Visual Studio Code Debug Adapter Host Package 1.0 Visual Studio Tools for Containers 1.0
|
Well this revert helped. I just did that, reverting to previous version of the GitHub extension and NO RESTART of OS/Machine but just the VS, solved it. I opened 3 VS instances and solutions back to back, and nothing popped up so far! thanks to this post, it helped. |
|
Firstable, you need to be sure have the last Microsoft .NET Framework version, in my case, I had the 4.6 version and I have downloaded and updated the .NET Framework 4.8.03761 Developer Pack, from the official site: https://dotnet.microsoft.com/download/dotnet-framework/net48 Once I restarted my PC, to continue fixing that, I solved this problem by clearing Visual Studio Component Model Cache. Just delete or rename this folder: %LocalAppData%\Microsoft\VisualStudio\11.0\ComponentModelCache %LocalAppData%\Microsoft\VPDExpress\11.0\ComponentModelCache |
We have been seeing many issues that involve missing MEF components, for example:
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.
The text was updated successfully, but these errors were encountered: