This will store the credentials in the Windows Credential Store, after which Visual Studio will happily pick them up. Mind all of the escapes needed to make paths work in the global git config.Īn alternative that doesn't require config changesĪnother option is to install the latest version of Git for Windows (which already ships with the Git credential Manager for Windows 1.18.4) and perform the initial clone and authentication from the command line. Helper = C:\\\\Program\\ Files\\\\Git\\\\mingw64\\\\libexec\\\\git-core\\\\git-credential-manager.exeĮnsure the path points to where the latest Git Credential Manager can be found on your system. Update your global git config to point to a specific implementation of the Git credential Manager: c:\>git config -global -edit Install the latest version of GCMW-1.xx.x.exe in your system and/or update to the latest version of Git for Windows which should include GCM.But on a machine without Visual Studio, that dll is not present. ![]() It happens that .dll, the file that contains the MSBuild tasks needed when creating a VSIX file, references it. ![]() The trick is, until Visual Studio actually ships with Git credential Manager for Windows 1.18.4 or newer (it should after Visual Studio 2019 preview 4.0 or newer), to configure the specific installation location of the Git credential manager in your Git Global Config: How is that a file from Visual Studio is required by the NuGet package that provides the Visual Studio SDK. ![]() ![]() This is preferred over overwriting the files in the Visual Studio installation as this may break future updates and can cause hard to debug issues in the future. After chatting with Chad Boles (who maintains Team Explorer in Visual Studio), we worked out another option.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |