-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Making TeamExplorerServiceHolder testable #1292
Conversation
When running this I get:
|
The problem is that This causes the following warning.
These warnings can be difficult to track down and it isn't at all clear what the issue is whether it's serious or not. |
052f25f
to
171e52a
Compare
This should be working now, MEF crashes are fixed. Also, this branch is now loading the following DLLs up front when starting VS in Team Explorer Home: Note that |
171e52a
to
25119fc
Compare
25119fc
to
84df182
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved, with one nit.
ActiveRepositoriesChanged?.Invoke(); | ||
} | ||
|
||
public IEnumerable<ILocalRepositoryModel> ActiveRepositories => gitService?.ActiveRepositories.Select(x => IGitRepositoryInfoExtensions.ToModel(x)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IGitRepositoryInfoExtensions.ToModel
is an extension method so why not just say x.ToModel()
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed the nit so 👍
This makes TeamExplorerServiceHolder testable by moving/abstracting all the dependent VS types.
This also reverts the change to have GitHub.TeamFoundation.15 reference Shell.15 - we rely on types from Shell.14 in GitHub.Exports and other areas (Shell.14 is available in VS 2017), namely UIContextChangedEventArgs.