Oct 02, 2017 - 10:09 AM
It is an issue related to the VS 2017. We have also posted this issue on the MSDN, and a Microsoft person said that there is breaking change from their side, and another wrong practice related to versioning. But we are still struggling to reproduce this issue at our end. Once it would be reproduced we can apply the solution by removing the wrong assemblies from GAC, or any other solution if we finds a better one.
And the current fix or workaround for this issue is that you shall disable the VS 2017 libraries of the SmartWord4TFS and load any other that you have like VS 2015 or VS 2013 or VS 2012 and then proceed.
In this regard I am mentioning here a link in which this whole scenario has been explained that how can you do this and then you can proceed with the SmartWord4TFS.
After this if the issue still persist then I have to do a brief GoToMeeting session with you where I shall investigate this issue and try to resolve it too.
Thanks and Regards,