Extension starting issue
See original GitHub issueHi, I install specnetide extension. When Visual Studio 2017 starts, this error message appears
The ‘SpectNetPackage’ package did not load correctly. The problem may have been caused by a configuration change or by the installation of another extension. You can get more information by examining the file ‘C:\Users\User\AppData\Roaming\Microsoft\VisualStudio\15.0_460adfb2\ActivityLog.xml’.
Corresponding lines from ActivityLog.xml:
190 | Begin package load [SpectNetPackage] | {1B214806-BC31-49BD-BE5D-79AC4A189F3C} | VisualStudio | 2018/10/04 21:18:17.869 | ||
---|---|---|---|---|---|---|
191 | ERROR | SetSite failed for package [SpectNetPackage]Source: ‘mscorlib’ Description: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information. System.Reflection.ReflectionTypeLoadException: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information. at System.Reflection.RuntimeModule.GetTypes(RuntimeModule module) at System.Reflection.RuntimeModule.GetTypes() at System.Reflection.Assembly.GetTypes() at Spect.Net.VsPackage.Vsx.VsxPackage.ScanTypes(Func2 condition, Action 1 action) in C:\Users\dotne\Source\Repos\spectnetide\VsIntegration\Spect.Net.VsPackage\Vsx\VsxPackage.cs:line 197 at Spect.Net.VsPackage.Vsx.VsxPackage.<InitializeAsync>d__13.MoveNext() in C:\Users\dotne\Source\Repos\spectnetide\VsIntegration\Spect.Net.VsPackage\Vsx\VsxPackage.cs:line 87 — End of stack trace from previous location where exception was thrown — at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.VisualStudio.Shell.AsyncPackage.<>c__DisplayClass17_0.<<Microsoft-VisualStudio-Shell-Interop-IAsyncLoadablePackageInitialize-Initialize>b__1>d.MoveNext() — End of stack trace from previous location where exception was thrown — at Microsoft.VisualStudio.Services.VsTask.RethrowException(AggregateException e) at Microsoft.VisualStudio.Services.VsTask.InternalGetResult(Boolean ignoreUIThreadCheck) at Microsoft.VisualStudio.Services.VsTask.GetResult() |
{1B214806-BC31-49BD-BE5D-79AC4A189F3C} | 80131602 | VisualStudio | 2018/10/04 21:18:18.009 |
192 | ERROR | End package load [SpectNetPackage] | {1B214806-BC31-49BD-BE5D-79AC4A189F3C} | 80131602 | VisualStudio | 2018/10/04 21:18:18.025 |
193 | Entering function CVsPackageInfo::HrInstantiatePackage |
Issue Analytics
- State:
- Created 5 years ago
- Comments:21 (13 by maintainers)
Top Results From Across the Web
How to Fix Chrome Extensions Not Loading or Crashing
1. Restart Chrome. Whenever you're troubleshooting an issue on your laptop or PC, you should start by trying this quick fix. However, simply ......
Read more >Fix problems with apps, extensions, or themes - Chrome ...
If you're having problems with your apps, extensions, and themes, try these steps. If you can't install an app You can no longer...
Read more >Top 7 Ways to Fix Google Chrome Failed to Load Extension
This is one of the basic steps to fix the extension loading issue on Google Chrome. Close the Chrome browser. Use Task Manager...
Read more >Chrome Extension is Not Working - Copper Help Center
Below you will find some common fixes for any issues you may be experiencing with the Copper Chrome Extension for Gmail. Option 1:...
Read more >Troubleshoot extensions, themes and hardware ...
Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems · Start Firefox in Troubleshoot Mode · Turn off hardware ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Unfortunately, it is s totally different mechanism – though syntactically similar to the one you suggest. I did some experiments, and it seems that the mechanism seems to round up versions with minor tags (15.1-15.9 seems to be 16.0)
I was unable to find a solution for this issue, so I close it. I March I’ll be in Redmond, and try to discuss the issue personally with the VSX team.