Bug with ExtensionService selecting highest-possible-framework version of extensions

[ChrisMaddock]

From nunit/teamcity-event-listener#75.

The TeamCity extension has two versions, one which targets .NET 2.0, and one which targets .NET Standard 2.0. The intended engine behaviour is that it should chose the extension targeting the highest possible framework version.

So in this case, when running the console in .NET 4.6.2 or higher, the .NET Standard 2.0 extension should be selected. What I think actually happens is that the engine simply compares "2.0" to "2.0" to chose the highest framework.

In this case, we somehow need to make it aware that .NET Standard 2.0 is "higher" that .NET Framework 2.0. This needs thinking about in terms of how we create the target "hierarchy", so it doesn't become a maintenance burden.

[CharliePoole]

@NikolayPianikov
What's the status of this in your view? Do we still need to do something for the 4.0 console or have you changed the extension?

[NikolayPianikov]

@CharliePoole actually we have no any complaints about it from our customers, so I suppose this ticket could be closed

[CharliePoole]

Thanks @NikolayPianikov I'll close this. Let me know if you see any problems come up as the 4.0 development progresses.