CODEWITHSUNDEEP
tfsvisual-studio-2017vsix
Eduardo Elias Saléh
Eduardo Elias Saléh

Reputation: 859

My VSIX extension is not showing on VS2017 (Was on 2015)

I have a VSIX extension (https://github.com/eduelias/AssociateRecentWorkItems) that worked really well on my VS2015 but, as I built/run it on VS2017 (yeah, I've put the prerequisites on the .csproj properties), it is not appearing at 2017's TFS Pending Changes tab.

I've tried updating MIcrosoft.TeamfoundationServer.Controls to the 2017 version but still no success.

As I try to debug it, it seems that VS2017 isn't loading the extension at all. (Breakpoints aren't not been loaded)

Any help is welcome. Thanks!

Upvotes: 0

Views: 915

Answers (2)

Eduardo Elias Saléh
Eduardo Elias Saléh

Reputation: 859

Looking through the log, I was able to find that some of my references were asking for Microsoft.TeamFoundation.Client Version=14.0.0, in fact, It was the Microsoft.TeamFoundation.VersionControl version=12.0 that were looking for it.

To solve it, I've made a 'binding redirect' like this:

[assembly: ProvideBindingRedirection(AssemblyName = "Microsoft.TeamFoundation.Client", NewVersion = "15.0.0.0", OldVersionLowerBound = "12.0.0.0", OldVersionUpperBound = "14.0.0.0")]

It started appearing at the Exp instance and I was able to debug it.

Note that I strongly advise against doing such kind of workaround but, in my case, it was the only way I could make it load my extension so I could debug it.

Upvotes: 1

PatrickLu-MSFT
PatrickLu-MSFT

Reputation: 51133

Give a try with another new extension on VS2017(from marketplace) in your side. If this could also not installed successfully and you are using VS2017 RC.

You may encountered this issue--Unable to install extensions after updating VS2017 RC

Either update to latest VS version or use Stefan Z Camilleri 's workaround in above link.

If only your old extension could not be installed, since

Huge changes have been made by Microsoft on the installation, so previous approaches of detecting VS won't work any more. For example, to detect VS installation folder, now a few extra tools or scripts are required, https://github.com/Microsoft/vswhere

So guides such as How to: Migrate Extensibility Projects to Visual Studio 2017 are critical and you can follow the tips.

You could also refer more details in this similar question Visual Studio 2017 is not detected by extensions for installation

Upvotes: 1

Related Questions