Skip to content
This repository was archived by the owner on Jun 21, 2023. It is now read-only.
This repository was archived by the owner on Jun 21, 2023. It is now read-only.

VS2017 repository listing spams the log with NRE when registry key is not found #978

@shana

Description

@shana

Looks like our 2017 codepath for listing repositories from the registry is not handling things right if the key doesn't exist (even though it probably doesn't crash, it spams the log with exceptions).

Error loading the repository list from the registry 'System.NullReferenceException: Object reference not set to an instance of an object.
   at GitHub.TeamFoundation.RegistryHelper.PokeTheRegistryForRepositoryList() in Y:\jenkins\workspace\GitHub for Visual Studio speakeasy jenkinskeep\src\GitHub.TeamFoundation.15\RegistryHelper.cs:line 26
   at GitHub.Services.VSGitServices.GetKnownRepositories() in Y:\jenkins\workspace\GitHub for Visual Studio speakeasy jenkinskeep\src\GitHub.TeamFoundation.14\Services\VSGitServices.cs:line 118'

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions