Installed product versions

• Visual Studio: 2019 preview
• This extension: 1.0.179

Description

Can't login in, it tell me that my password is wrong. But I am sure it's right, while the output window got an error with the hostinfo.json missing.

Steps to recreate

1. login

Current behavior

hostinfo.json missing

Expected behavior

Here's the details output:

[GitLab for Visual Studio  Handled Exception 03:38:00 PM] LoadHostVersionInfo: System.IO.FileNotFoundException: Could not find file 'C:\Users\{UserName}\hostinfo.json'.
File name: 'C:\Users\{UserName}\hostinfo.json'
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   at System.IO.StreamReader..ctor(String path, Encoding encoding, Boolean detectEncodingFromByteOrderMarks, Int32 bufferSize, Boolean checkHost)
   at System.IO.File.InternalReadAllText(String path, Encoding encoding, Boolean checkHost)
   at System.IO.File.ReadAllText(String path)
   at GitLab.VisualStudio.Services.Storage.LoadHostVersionInfo()
[GitLab for Visual Studio  Handled Exception 03:40:10 PM] Diagnostics mode caught and marked as handled the following DispatcherUnhandledException raised in Visual Studio: System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified
   at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
   at System.Diagnostics.Process.Start()
   at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
   at GitLab.VisualStudio.Services.ShellService.OpenUrl(String uri)
   at GitLab.TeamFoundation.ViewModels.PublishSectionViewModel.OnSignUp()
   at GitLab.VisualStudio.Shared.Helpers.Commands.DelegateCommand.<>c__DisplayClass5_0.<.ctor>b__0(Object o)
   at GitLab.VisualStudio.Shared.Helpers.Commands.DelegateCommand.Execute(Object parameter)
   at GitLab.VisualStudio.Shared.Helpers.Commands.DelegateCommand.System.Windows.Input.ICommand.Execute(Object parameter)
   at MS.Internal.Commands.CommandHelpers.CriticalExecuteCommandSource(ICommandSource commandSource, Boolean userInitiated)
   at System.Windows.Controls.Primitives.ButtonBase.OnClick()
   at System.Windows.Controls.Button.OnClick()
   at System.Windows.Controls.Primitives.ButtonBase.OnMouseLeftButtonUp(MouseButtonEventArgs e)
   at System.Windows.UIElement.OnMouseLeftButtonUpThunk(Object sender, MouseButtonEventArgs e)
   at System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(Delegate genericHandler, Object genericTarget)
   at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
   at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
   at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
   at System.Windows.UIElement.ReRaiseEventAs(DependencyObject sender, RoutedEventArgs args, RoutedEvent newEvent)
   at System.Windows.UIElement.OnMouseUpThunk(Object sender, MouseButtonEventArgs e)
   at System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(Delegate genericHandler, Object genericTarget)
   at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
   at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
   at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
   at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
   at System.Windows.UIElement.RaiseTrustedEvent(RoutedEventArgs args)
   at System.Windows.UIElement.RaiseEvent(RoutedEventArgs args, Boolean trusted)
   at System.Windows.Input.InputManager.ProcessStagingArea()
   at System.Windows.Input.InputManager.ProcessInput(InputEventArgs input)
   at System.Windows.Input.InputProviderSite.ReportInput(InputReport inputReport)
   at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawMouseActions actions, Int32 x, Int32 y, Int32 wheel)
   at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr hwnd, WindowMessage msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

Trying to install this on vscode and am getting the error of the extension/package.json not being found inside zip.

Patrick Becker
1 Star2 Star3 Star4 Star5 Star
2017/11/20
A great extension. A normal login does not work, tokens must be used. (This is not immediately clear and makes it difficult to get started)

Only the publishing of projects via VisualStudio fails. (BadRequest)

Visual Studio öffnen -> Zur Quellcodeverwaltung hinzufügen
Visual Studio öffnen -> GitLab -> Veröffentlichen (Error: BadRequest)

Create an empty project on GitLab and add it manually.
[Code]
git remote add origin https://gitlab.com//
git push -u origin master
[/Code]

Installed product versions

• Visual Studio 2017 Enterprise v15.9.4
• This extension: v1.0.166

Description

I cannot find any way in the Team Explorer window to create a connection my GitLab account. I have a local project in Git. On the Push tab of Team Eplorer there are options to publish to Azure DevOps, GitHub, and Remote Repository.

Steps to recreate

1. Create new project.
2. Add to Git control from the bottom right menu option.
3. Look everywhere possible in Team Explorer for a GitLab login.
4. Notice that according to another closed issue, the GitLab login button appears to be on the "Sync" tab of Team Explorer, but in the current version of Visual Studio, you CANNOT go to that tab. When you click on Sync, you are taken to the Push tab.

Current behavior

There is no possible way to create a GitLab login.

Expected behavior

Simple easy way to login to a GitLab account from Manage Connections tab of the Team Explorer window in Visual Studio.

Installed product versions

• Visual Studio: 2017 Enterprise edtion
• This extension: [example 1.1.21]

Description

I just download gitlab flow for VS 2017. I am trying to gitlab from git hub.

It does not look like I have an option to log in?

Steps to recreate

1. installed the plug in
2. opened a project that I moved and branched within gitlab using github desktop app.
   3.opened the project and getting this screenshot
   
   .

Current behavior

no option to log in or anything

Expected behavior

Explain what it should be doing after it's fixed.

Installed product versions

• Visual Studio: Visual Studio 2019 Enterprise Preview
• This extension: 1.0.182

Description

I can not connect to my gitlab server.
our https port is 7443 and ssh port is 7022.

Steps to recreate

1. install the plugin
   

2. Connect to GitLab
   
   

then I got the error:

3. when use email to login:
   

I got the error:

Current behavior

Expected behavior

how can i connect?

Hi @maikebing ,
on update to version 1.0.142 got error message:
Beginning to install extension to Microsoft Visual Studio Professional 2015...
Upgrading 'GitLab Extension for Visual Studio', version 1.0.0.122 to version 1.0.142.
Install Error : Microsoft.VisualStudio.ExtensionManager.MissingReferencesException: This extension cannot be installed because the following references are missing:

• Visual Studio MPF 15.0
  at Microsoft.VisualStudio.ExtensionManager.ExtensionManagerService.CheckForInstallBlockers(InstallableExtensionImpl extension, IInstalledExtensionList modifiedInstalledExtensionsList, Boolean isNestedExtension, Boolean& olderVersionInstalled)
  at Microsoft.VisualStudio.ExtensionManager.ExtensionManagerService.InstallInternal(InstallableExtensionImpl extension, Boolean perMachine, Boolean isNestedExtension, IDictionary2 extensionsInstalledSoFar, List1 extensionsUninstalledSoFar, IInstalledExtensionList modifiedInstalledExtensionsList, AsyncOperation asyncOp, UInt64 totalBytesToWrite, UInt64& totalBytesWritten, Boolean enforceCertificateCheckForUpgrade)
  at Microsoft.VisualStudio.ExtensionManager.ExtensionManagerService.BeginInstall(IInstallableExtension installableExtension, Boolean perMachine, AsyncOperation asyncOp, Boolean enforceCertificateCheckForUpgrade)
  at Microsoft.VisualStudio.ExtensionManager.ExtensionManagerService.InstallWorker(IInstallableExtension extension, Boolean perMachine, AsyncOperation asyncOp, Boolean enforceCertificateCheckForUpgrade)

Looks it is simmilar to : rionmonster/Glyphfriend#87

Thank you

Hi,

Modify default repo folder on Visual Studio.

Then try to duplicate or create new repo, default folder is always c:\users\mylogin\Source...

New folder never used.

Regards,

我在代码上，右键 -> Gitlab -> 提交，打开的URL一直都是 master 分支，但是当前的默认分支为develop，导致需要一直手动改Url

生成的URL

https://gitlab.XXXX.net/xxx/xxx/xxx/commits/master/src/xxx/xxx/xxxx.cs#L16

In the dialog "Connect to GitLab" (Connection Management) the password field is not accepting passwords shorter than 6 chars.

Why? A simple login form dont have to test the password complexity. ;)

Whether I check or uncheck "Private" it appears to still try to Publish as a Private repository.
GitLab CE

When trying to attach to a server without a domain extension such as http://my-gitserv/ on the login, it will flag it as an invalid URL.

I really like the GitLab extension, but there's one thing that's bothering me a bit: it doesn't do an automatic fetch to check if there might be updates floating around when you open up a project that has been connected to a repository.

Could that maybe added?

Installed product versions

• Visual Studio: 2017 v15.9.10 Professional and v15.9.9 Community Edition
• This extension: Git commit 5c6b62b

Description

I am not able to build the current master.
I want to find out why the extension doesn't work with the GitLab CE in our LAN.

Steps to recreate

1. Clone the repository from GitHub
2. Open in Visual Studio 2017.9.10
3. Run Build Solution.

Current behavior

I get this error building GitLab.VisualStudio.csproj (other projects within the solution build fine):

1>------ Build started: Project: GitLab.VisualStudio, Configuration: Debug Any CPU ------
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(2110,5): warning MSB3274: The primary reference "C:\Source\GitLab.VisualStudio\build\Debug\GitLab.TeamFoundation.16.dll" could not be resolved because it was built against the ".NETFramework,Version=v4.7.2" framework. This is a higher version than the currently targeted framework ".NETFramework,Version=v4.6.1".
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(2110,5): warning MSB3277: Found conflicts between different versions of "Microsoft.TeamFoundation.Git.Controls" that could not be resolved.  These reference conflicts are listed in the build log when log verbosity is set to detailed.
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(2110,5): warning MSB3277: Found conflicts between different versions of "Microsoft.VisualStudio.ComponentModelHost" that could not be resolved.  These reference conflicts are listed in the build log when log verbosity is set to detailed.
1>  GitLab.VisualStudio -> C:\Source\GitLab.VisualStudio\build\Debug\GitLab.VisualStudio.dll
1>C:\Source\GitLab.VisualStudio\packages\Microsoft.VSSDK.BuildTools.15.1.192\tools\VSSDK\Microsoft.VsSDK.targets(578,5): error MSB4057: The target "GenerateFileManifest" does not exist in the project.
========== Build: 0 succeeded, 1 failed, 5 up-to-date, 0 skipped ==========

Expected behavior

It builds without an error

Tried to solve this by

• Upgrade all the nuget packages. This fails because some most projects are still targeted to v4.6.1
• Retarget all the projects to v4.7.2. This fails because GitLab.VisualStudio.csproj becomes incompatible.

So far it's working very well with Visual Studio 2015 using our company GitLab server.

With VS 2017, weirdly, I am getting fatal: unable to access 'https://gitlab.mycompany.com/myname/test2.git/': SSL certificate problem: unable to get local issuer certificate.

作者你好：
我嘗試著用docker自己架了gitlab server
但是我輸入帳號密碼時總是出現錯誤@@(如附圖)
但是如果我使用git client是確定可以正常使用的。
請問是不是我哪裡沒有設定正確呢？

另外，請問是否有支援ssh key登入呢？
非常感謝^^

Installed product versions

• Visual Studio: 2017 community edition
• This extension: 1.0.167

Description

I'm getting a login error when connection from a new project. Exisiting projects still work and authenticate normally however creating a new project gives an error on login.

Steps to recreate

1. Start visual studio
2. In the team explorer trying to connect to my gitlab server
3. Or creating a new project an trying to connect to the gitlab server.

Current behavior

Throwing an error on login while login on exisiting projects still work.

I have been trying to log into GitLab through your extension, and have been getting no luck.
I have 2FA enabled on my account, I am not sure if that has any effect.
But when I enable 2FA on your extension, it says Error 401. When I don't enable it and use my password it gives me Error 401 again. And when I use a Personal Access Token without 2FA enabled it gives me this:

I'm using the gitlab plugin version 1.0.0.112 for Visual Studio 2017 and after getting the latest update i am no longer able to log into the account. Every login attempt will return a login failed message, is there any way to revert to old api functionality or to get a better error message related to the cause of the login failure. I am using a private gitlab repo

I can login to the GitLab web portal, create a repository and clone it in Visual Studio, but when I try to publish back to GitLab, I get a "401 Unauthorized". Tried all 4 authentication methods, never asked for a token.

I am using 1.0.0.122 of the GitLab extension.

目前的在VS里进行历史记录比较后的差异项，在团队资源管理器里呈现后，右键文件打开时，打开的是提交记录里的文件，没法打开当前项目里对应的实际文件，颇为不变，希望能加上一个打开当前文件的功能。

I have Win10 1709 (16299) I can't install the gitlab update. I get a lot of similiars errors like:
22.05.2018 09:30:52 - Skipping non-applicable package Microsoft.Windows.UniversalCRT.Msu.8: Die aktuelle Betriebssystemversion 10.0.16299.0 liegt nicht im unterstützten Versionsbereich "[6.2,6.3)".
22.05.2018 09:30:52 - Skipping non-applicable package Microsoft.Windows.UniversalCRT.Msu.81: Die aktuelle Betriebssystemversion 10.0.16299.0 liegt nicht im unterstützten Versionsbereich "[6.3,6.4)".
22.05.2018 09:30:52 - Skipping non-applicable package Microsoft.Windows.D3DCompiler.Msu.Win7: Die aktuelle Betriebssystemversion 10.0.16299.0 liegt nicht im unterstützten Versionsbereich "[6.1,6.2)".
liegt nicht im unterstützten Versionsbereich->Version is not supported

https://marketplace.visualstudio.com/items?itemName=MysticBoy.GitLabExtensionforVisualStudio#qna

Installed product versions

• Visual Studio: 2017 15.9.11
• This extension: 1.0.183

Description

At the moment the default clone path is hardcoded to the documents folder.
It would be nice, if we can configure the default path.

Steps to recreate

1. Open Clone Dialog

Current behavior

Path is hardcoded

Expected behavior

Config File / Configuration Menu to set default path

I do all to login. Create a Personal Access Tokens, but when i enter the data, I have the error Failed to login, 404 not found!
please i need to work thanks

it still wont let me log into gitlab after the update, tried email & username to https://gitlab.com and check 2 factor authentication, always comes back with "Failed to login"
been having to manually sync via git cmd

GitLab Server：https://gitlab.com/
Auth Type：GitLab ApiV4

I have GitLab server but the VS extension report random errors, after project creation on my server:
http://79.8.134.146:10080
The client extension create the project in the server but immediatly after report strange connection error to invalid local server:
http://localhost:10080/..
se attached image.
Same problem when I try to clone, the client extension show me the correct project (previous created) but when confirm unable to clone because return the same error (of creation)

I think was little problem on the code when reconnect to server replacing the IP with localhost

I wait for patch!! .. thanks in advance!!

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.
Error with latest release of the extension.

As the title says if that's possible update the Visual Studio Gallery plugin

Installed product versions

• Visual Studio: 2017 15.9.11
• This extension: 1.0.183

Description

The namespace in the project clone dialog is incomplete.

Steps to recreate

1. Create Project in Group & Project in Sub Group
2. Open Clone Dialog

Current behavior

Name of Group and Sub Group is missing.

Expected behavior

Name is displayed.

Hi.

When I try to open a project without .sln / .*proj file, The extension ask me to select a .sln / .*proj. As there are none, I can't use the extension.

Regards,

Dremor

Installed product versions

• Visual Studio: 2019 Community
• This extension: 1.0.189 (same issue 1.0.180)

Description

I'm getting the same error like here https://marketplace.visualstudio.com/items?itemName=MysticBoy.GitLabExtensionforVisualStudio&ssr=false#review-details

Still cannot get logged in, very disappointing. Error: "Failed to login Please check your username or password! V4_Oauth:Unexpected character encountered while parsing value: <. Path ", line 0, position 0."

auto discovery.

I also checked multiple times the URL, also tried several URLs, always getting the error above. I also checked my login data multiple times on the GitLab Login website. On the marketplace I also read many comments about connection problems.

Current behavior

see above.

Expected behavior

Would expect that it connects with GitLab without any errors.

Installed product versions

• Visual Studio: 2017 15.9.11
• This extension: 1.0.183

Description

An exception occours, if a solution is loaded and the create project button is pressed.

Steps to recreate

1. Load solution
2. Switch to Team Explorer and press Create

Current behavior

Exception is thrown:

[GitLab for Visual Studio  Handled Exception 04:17:33 ] Diagnostics mode caught and marked as handled the following DispatcherUnhandledException raised in Visual Studio: System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
   bei GitLab.VisualStudio.UI.ViewModels.CreateViewModel.LoadResources()
   bei GitLab.VisualStudio.UI.ViewModels.CreateViewModel..ctor(IDialog dialog, IGitService git, IMessenger messenger, IShellService shell, IStorage storage, IWebService web)
   bei GitLab.VisualStudio.Services.ViewFactory.GetView[T](ViewTypes type)
   bei GitLab.TeamFoundation.ViewModels.ConnectSectionViewModel.OnCreate()
   bei GitLab.VisualStudio.Shared.Helpers.Commands.DelegateCommand.<>c__DisplayClass5_0.<.ctor>b__0(Object o)
   bei GitLab.VisualStudio.Shared.Helpers.Commands.DelegateCommand.Execute(Object parameter)
   bei GitLab.VisualStudio.Shared.Helpers.Commands.DelegateCommand.System.Windows.Input.ICommand.Execute(Object parameter)
   bei MS.Internal.Commands.CommandHelpers.CriticalExecuteCommandSource(ICommandSource commandSource, Boolean userInitiated)
   bei System.Windows.Documents.Hyperlink.OnClick()
   bei System.Windows.Documents.Hyperlink.DispatchNavigation(Object sender)
   bei System.Windows.Documents.Hyperlink.DoUserInitiatedNavigation(Object sender)
   bei System.Windows.Documents.Hyperlink.OnMouseLeftButtonUp(Object sender, MouseButtonEventArgs e)
   bei System.Windows.Documents.Hyperlink.OnMouseLeftButtonUp(MouseButtonEventArgs e)
   bei System.Windows.UIElement.OnMouseLeftButtonUpThunk(Object sender, MouseButtonEventArgs e)
   bei System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(Delegate genericHandler, Object genericTarget)
   bei System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
   bei System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
   bei System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
   bei System.Windows.UIElement.ReRaiseEventAs(DependencyObject sender, RoutedEventArgs args, RoutedEvent newEvent)
   bei System.Windows.UIElement.OnMouseUpThunk(Object sender, MouseButtonEventArgs e)
   bei System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(Delegate genericHandler, Object genericTarget)
   bei System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
   bei System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
   bei System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
   bei System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
   bei System.Windows.ContentElement.RaiseTrustedEvent(RoutedEventArgs args)
   bei System.Windows.Input.InputManager.ProcessStagingArea()
   bei System.Windows.Input.InputManager.ProcessInput(InputEventArgs input)
   bei System.Windows.Input.InputProviderSite.ReportInput(InputReport inputReport)
   bei System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawMouseActions actions, Int32 x, Int32 y, Int32 wheel)
   bei System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr hwnd, WindowMessage msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   bei System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   bei MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   bei MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
   bei System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   bei System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

Expected behavior

Dialog opens. Project can be created.

Hi !

I've just installed the extension on a VS 2017 instance. On the "Team Explorer" tab I can see a section "Gitlab", but I have nothing actionable for connecting to my gitlab server (See screenshot).

How am I supposed to do for connecting Visual studio and my Gitlab server ?

When creating new repo even after choosing new location it remains default

Installed product versions

• Visual Studio: [2019 Professional]
• This extension: [Version | 1.0.189]

Description

I want to connect to the local gitlab server I sing in without any problem, but I can't see any branch, and of course, I couldn't clone my project and button clone is gray.

Installed product versions

• Visual Studio: 2017 Community
• This extension: 1.0.166

Description

Publish option offered for solution tracking remote repository.

Steps to recreate

1. Clone a repository from GitLab
2. Open cloned solution in Visual Studio
3. Open Team Explorer to the Sync Tab
4. Publish option is available even though publishing is not a viable option.

Current behavior

Publish option for solution tracking remote repository. Publish option is available even though publishing is not a viable option.

Expected behavior

If the solution is tracking a remote repository, the publish button should be hidden.

Installed product versions

• Visual Studio: 2019 Professional
• This extension: 1.0.182

Description

Cloning any GitLab repo generates the folowing error.

Git failed with fatal error. Repository {path} not found

Steps to recreate

Assume GitLabs VS extension is installed.

1. Open VS and click View>>Team Explorer
2. Click GitLab>>Clone
3. when the clone dialog appears, select any repo, leave the install path default, click "Clone"
4. VS "Output" windows displays the following...

Cloning into 'C:\Source'...
Remote: The project you were looking for could not be found.
Error encountered while cloning the remote repository: Git failed with a fatal error.
repository 'https://gitlab.com/{user}/myrepo.git/' not found

Current behavior

The behaviour does not happen in VS2017 for the same repos

Expected behavior

It should clone the repo for normal usage

I have noticed in the error message the the repo path always has a trailing forward slash when there shouldn't be one. Not sure if this is the problem.

For example, the path displayed appears as so: "https://gitlab.com/{user}/myrepo.git/"

If you cut-n-past this path into a browser you get a 404 error. Removing the trailing slash and the page displays (in any browser).

• I have tried un/re install of GIT both in the VS installer and manually.
• Tried using different "Path" parameter, same effect
• tried fresh VM with VS2019 installed, same effect
• fresh VM (W10E) with VS2017, GitLabs ext runs fine. Same repo using same target path, clones just fine.

GitLab does not login with LDAP credentials. Is there any chance to support this feature?

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.

I'm using the gitlab addin version 1.0.0.112 for Visual Studio 2017. When I try to publish to GitLab I get error 'The remote server returned an error (BadRequest)' On old projects that I have previously published to gitlab I can sync those without any problems. Only on a new project, publishing for the first time I get this error. Any ideas?

Excellent extension. Everything works for me on VS 2017 Community Edition using my personal GitLab server. A few interactions could be handled better, possibly better integration of some of the other features. Integrate auto GitLab repo on new project (this can get confusing). Maybe automate some git workflow handling? CI/CD build notifications?

This i what I am getting when logging

I have this error when I tried to connect:
"Failed to login
Unexpected character encountered while parsing value: <. Path '', line 0, position 0."

I write all the required fields ok.
This is the latest version installed from VS extensions menu.

Please help, I need to connect to gitlab. Thank you!!

Installed product versions

• Visual Studio: 2017 Professional
• This extension: lasted

Description

[GitLab for Visual Studio Handled Exception 11:14:20 PM] AddHostVersionInfo: System.ArgumentException: An item with the same key has already been added.
at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
at GitLab.VisualStudio.Services.Storage.AddHostVersionInfo(String host, ApiVersion apiVersion)

show error when login with extensions

Thanks

Win10. I received the following error attempting to use this Extension while on CorpNet behind a Proxy:

"Git failed with a fatal error.
unable to access 'https://gitlab.com/myproject': Could not resolve proxy: none"

I searched but couldn't find any documentation or setting for Proxy. It doesn't seem to be reading from the browser settings.

一旦我打开解决方案,这个插件界面就没有了. 2017正常工作