The Wayback Machine - https://web.archive.org/web/20201215063258/https://github.com/github/VisualStudio/issues/2439
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error popup "package did not load correctly." #2439

Open
shlomoa opened this issue Oct 28, 2019 · 3 comments
Open

Error popup "package did not load correctly." #2439

shlomoa opened this issue Oct 28, 2019 · 3 comments

Comments

@shlomoa
Copy link

@shlomoa shlomoa commented Oct 28, 2019

Versions

  • GitHub Extension for Visual Studio version: ...
    2.10.8.8132
  • Visual Studio version: ...
    2019-preview

What happened

Steps to Reproduce

Steps to reproduce the behavior:

  1. open a solution with git connection
    my connection is to a git repository, not github
  2. The popup appears

Expected behavior

Screenshots

image

Logs

Additional context

@dysangelist-1
Copy link

@dysangelist-1 dysangelist-1 commented Jan 16, 2020

Same here on VS2019 16.4.3. Upgraded the extension from 2.10.8.8121 to 2.10.8.8132 (latest as of this writing), immediately started getting two of these errors as soon as I loaded a folder cloned from a Github repo. First one says that PullRequestStatusBarPackage did not load correctly, second one that GitHubPackage didn't. GitHub functionality is of course totally unavailable with the plugin having failed to load.

Reverting to 2.10.8.8121 instantly fixed the problem.

This might be a regression? It seems to be the same problem as described on #1810 and #1625.

Error descriptions from ActivityLog.xml:

SetSite failed for package [PullRequestStatusBarPackage]
Source: 'System.ComponentModel.Composition' 
Description: No exports were found that match the constraint: 
ContractName: GitHub.InlineReviews.Services.PullRequestStatusBarManager
RequiredTypeIdentity: GitHub.InlineReviews.Services.PullRequestStatusBarManager 
...
SetSite failed for package [GitHubPackage]
Source: 'System.ComponentModel.Composition' 
Description: No exports were found that match the constraint: 
ContractName: GitHub.Commands.IBlameLinkCommand
RequiredTypeIdentity: GitHub.Commands.IBlameLinkCommand 
@MakCom
Copy link

@MakCom MakCom commented Jan 31, 2020

Same here on VS2019 16.4.3. Upgraded the extension from 2.10.8.8121 to 2.10.8.8132 (latest as of this writing), immediately started getting two of these errors as soon as I loaded a folder cloned from a Github repo. First one says that PullRequestStatusBarPackage did not load correctly, second one that GitHubPackage didn't. GitHub functionality is of course totally unavailable with the plugin having failed to load.

Reverting to 2.10.8.8121 instantly fixed the problem.

This might be a regression? It seems to be the same problem as described on #1810 and #1625.

Error descriptions from ActivityLog.xml:

SetSite failed for package [PullRequestStatusBarPackage]
Source: 'System.ComponentModel.Composition' 
Description: No exports were found that match the constraint: 
ContractName: GitHub.InlineReviews.Services.PullRequestStatusBarManager
RequiredTypeIdentity: GitHub.InlineReviews.Services.PullRequestStatusBarManager 
...
SetSite failed for package [GitHubPackage]
Source: 'System.ComponentModel.Composition' 
Description: No exports were found that match the constraint: 
ContractName: GitHub.Commands.IBlameLinkCommand
RequiredTypeIdentity: GitHub.Commands.IBlameLinkCommand 

I’m experiencing exactly the same problem. We have even identical versions.
Only difference is that on reverting to version 2.10.8.8121 of the GitHub extension the problem didn’t go away.
P.S,
Workaround fix, which worked for me:
Close VS. Delete files in ComponentModelCache folder. They will be recreated when VS starts.
%localappdata%\Microsoft\VisualStudio\16_xxxx
e.g.
%localappdata%\Microsoft\VisualStudio\16.0_574bb467\ComponentModelCache

@robertjf
Copy link

@robertjf robertjf commented Feb 14, 2020

I've had the same problem, but instead of reverting versions, I tried @MakCom's suggestion of clearing the ComponentModelCache - this worked for me with the latest version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.