I want to know, if support for extending Team Explorer in "newer" Studios was changed significantly or not. I want to add a new section to the "Pending Changes" page in Team Explorer 2017.
Based on the informations here I implemented a base class for this stuff:
public class TeamExplorerBaseSection : TeamExplorerBase, ITeamExplorerSection { ... }
and then derived from it:
[TeamExplorerSection(SectionId, TeamExplorerPageIds.PendingChanges, 900)]
public class MyNewSectionSection : TeamExplorerBaseSection
{
public const string SectionId = "8AAE3BBE-E5FE-4D9E-9244-EA86F67B8512";
}
This worked in VS 2013 without any problem. When I hit F5 at least the Experimental Version of VS 2017 will not show any new section in the desired page.
What made me suspicios is that you can find nearly every needed component via NuGet from Microsoft now. As you can see here Microsoft had support for Team Explorer via NuGet too but for some reason decided to stop it at VS 2013. Another clue is that the official VSIX-docu will say nothing on this kind of extension.
Does this mean that one should not extend Team Explorer anymore?
The solution in my case was to remove a NuGet package named Microsoft.TeamFoundation.All from my references. This package is outdated which I've not noticed.
The package situation for VSIX is somewhat annoying to me. I ended up building my own NuGet package containing the packages I need for VS 2015, VS 2017 and so on. This way I'm not depending in searching and referencing on the local machine which can break everything because we're working as a team using VSTS.