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

Login failed in case of wrong NewtonSoft.JSON version #36

Closed
Banzai292 opened this issue Dec 11, 2018 · 3 comments
Closed

Login failed in case of wrong NewtonSoft.JSON version #36

Banzai292 opened this issue Dec 11, 2018 · 3 comments
Assignees
Labels

Comments

@Banzai292
Copy link

Installed product versions

  • Visual Studio: 2017 CE (15.9.3)
  • This extension: [GitLab.Extension 1.0.165]
  • GitLab self hosted (11.5.3)

Description

Can't login with Team Explorer->Connect, because extension try loading "NewtonSoft.JSON 11.0.0.0", what's very old, and failed.
The Installation (%AppData%\Microsoft\VisualStudio\15xxx\Extensions\somethingcryptic) comes with Version 12.0.1.22727.

Steps to recreate

  1. Go to "Team Explorer" in VS
  2. Click "Connect" on GitLab
  3. Enter address, username and password (doesnt matter, until its not empty)
  4. Set "GitLab ApiV4 Oauth2" (or something else, doesnt matter)
  5. UNCHECK Two Factor.... (doesnt matter, if checked or not)
  6. Click Login -> Error Message

Current behavior

No connection to self hosted GitLab server.

Expected behavior

Connect to self hosted GitLab server and pull, create etc. repository

It's only functional on cloned repos by hand. Open such project in vs and commit, push, etc. works with self hosted GitLab.

@Banzai292 Banzai292 changed the title Login faiuled in case of wrong NewtonSoft.JSON version Login failed in case of wrong NewtonSoft.JSON version Dec 11, 2018
@maikebing maikebing self-assigned this Dec 11, 2018
@maikebing maikebing added the bug label Dec 11, 2018
@maikebing
Copy link
Owner

@Banzai292
Copy link
Author

Banzai292 commented Dec 12, 2018

Thank you for your quick response.
Version seems fine, because it failes with another error!

After fiddle around with self-signed certificates, windows trust store, gitconfig and many googleing, git on git-bash works fine with local and remote repos (clone, pull, fetch etc), but the gitlab.extensions gives me a "does not trust SLL/TLS" message.

You can close this issue so far, because the "NewtonSoft"-problem does not pop up anymore.

BTW: The link "register now" results in "System can't find file' error bar in VS. Don't know the current or actual behavior of this functionality.... I doesn't need it.

@maikebing
Copy link
Owner

@Banzai292 OK !

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

No branches or pull requests

2 participants