visual studio 2015 - Updated VS2012 to VS2015 on Buiild server. Now "No TFS assemblies were found on the system" when connecting to VCS (TFS) root -

we have teamcity on it's own (internal) build server, , tfs on internal build server. working hunky dory until...

i've removed vs2012 build server , installed vs2015 on there, dev team have upgraded (most have been using 6 months).

teamcity cannot connect tfs , following when testing connection vcs root:

error - no tfs assemblies found on system. please make sure have microsoft team explorer 8.0, 9.0, 10.0 or 11.0 installed

i've seen various posts stating team explorer required, so...

• have installed (seemed use vs2013 shell) , have connected tfs within there.
• i've connected tfs within vs2015.
• have rebooted server

what need resolve error? tfs assemblies looking for?

nb full text of error received when testing connection

test connection failed in v6 :: ci - build v6. tfs failed. exitcode: -1 stdout: tfs native verifier v7.1 copyright (c) 2006-2012 jetbrains s.r.o. running under .net framework 4.0.30319.42000 error - no tfs assemblies found on system. please make sure have microsoft team explorer 8.0, 9.0, 10.0 or 11.0 installed  command: c:\teamcity\webapps\root\web-inf\plugins\.unpacked\tfs\bin\tfs-native.exe @@c:\teamcity\bin\..\temp\tc-tfs-20-3556_30\command.params, in file: {http://[mytfsserver:8080/tfs/defaultcollection/, /user:***** /hash:s, c:\teamcity\temp\tc-tfs-20-3556_29.result, connectiontest, $/v6/} 

ok, moment i've got round installing team explorer visual studio 2012. build still failing , @ least build able start, original issue - i.e. teamcity can connect the vcs root.

this isn't optimal solution we've supposedly moved on vs2012, i'm , running.

vs2015 natively supported in teamcity 9 long term solution (which may have sooner planned) upgrade tc latest version - we're on 7.1.3...

update: ok, had backed up, decided dirty workaround didn't cut mustard, removed team explorer vs2012, , updated teamcity 9, in longer term plan anyway. works natively without smelly workaround. argue should have been done start, initial plan wasn't upgrade @ once, play safe.