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

No Remote list visible/ no sign out #1455

Closed
remberg opened this Issue Feb 2, 2018 · 9 comments

Comments

Projects
None yet
4 participants
@remberg

remberg commented Feb 2, 2018

hi,
i have just installed the latest update. Unfortunately, the logout is no longer available and no remote repos are visible anymore. (latest Extension 2.4.0.1202, Visual Studio 2017 preview)

@grokys

This comment has been minimized.

Contributor

grokys commented Feb 2, 2018

Hi @remberg

Thanks for letting us know: could you share a screenshot of what you're seeing?

@grokys grokys added the bug label Feb 2, 2018

@drewkht

This comment has been minimized.

drewkht commented Feb 2, 2018

Hi, I'm also seeing this issue this morning after upgrading to the newest version. Hopefully these screenshots were what you were looking for. I'm using VS 2017 Community v15.5.6 with ReSharper Ultimate installed.
team explorer pane
github login pane
team explorer pane - expanded
team explorer pane - repo home

@grokys

This comment has been minimized.

Contributor

grokys commented Feb 2, 2018

Thanks for the screenshots @drewkht. This looks to me like MEF getting confused, could you first get a copy of your MEF cache and then try resetting the MEF cache?

There are two ways to do this:

  • The easiest way is to install this extension: https://github.com/madskristensen/ClearComponentCache (use the the nightly build from here)
    • You can then use "Tools -> Show MEF Errors" to show the MEF log. Copy this and paste it here.
    • Then select "Tools -> Clear MEF Component Cache". Visual studio will restart, and if I'm correct all should be well
  • If you don't want to install another extension:
    • Close VS
    • Go to C:\Users\[Username]\AppData\Local\Microsoft\VisualStudio\15.0_???????? (the ???????? will be a set of letters and numbers
    • Send us the Microsoft.VisualStudio.Default.err file
    • Then delete that directory and restart VS. Again, hopefully the problem will be fixed
@drewkht

This comment has been minimized.

drewkht commented Feb 2, 2018

Hi @grokys,

I followed your instructions, starting with installing the add-on. After installing and restarting VS I didn't have an option under Tools called "Show MEF Errors", although I did have the "Clear MEF Component Cache" option.

Here's the .err file you mentioned that was located inside the ComponentModelCache folder at the filepath you provided. This is from before I used the Clear MEF Component Cache option.
Microsoft.VisualStudio.Default.err.zip

It looks like you were correct about the cause of the issue, as clearing the MEF cache and restarting VS appears to have resolved it in my case. Functionality of the GitHub extension looks to be back to normal.

Thanks!

@grokys

This comment has been minimized.

Contributor

grokys commented Feb 2, 2018

Thanks for getting back to us @drewkht, glad that fixed your problem.

@AArnott @Michael-Eng it looks like we may have another installer problem - clearing the MEF cache seems to resolve it. Could the installer not be doing this properly? #1454 may be related but we have no confirmation as yet.

@grokys grokys added the installer label Feb 2, 2018

@remberg

This comment has been minimized.

remberg commented Feb 2, 2018

I didn't have an option under Tools called "Show MEF Errors".
I used the "Clear MEF Component Cache" and it works now. Thx for help

@jcansdale

This comment has been minimized.

Contributor

jcansdale commented Feb 2, 2018

@remberg, @drewkht,

Could you try this new installer (open the .vsix file):
https://ci.appveyor.com/project/github-windows/visualstudio/build/2.4.1.1219/artifacts

It includes a workaround for this issue. Please let us know if this version works as expected!

@jcansdale

This comment has been minimized.

Contributor

jcansdale commented Feb 2, 2018

@remberg, @drewkht,

Note, you might need to open the .vsix from the .zip. I was getting a network error when tried downloading the .vsix directly. It worked fine from the .zip. 😕

image

@remberg

This comment has been minimized.

remberg commented Feb 2, 2018

Ok i installed the .vsix and it works. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment