Thanks Sean.
I encountered the exact same problem and your solution fixed it!
For the record:
SQL 2017 Developer Edition.
Visual Studio 2013 Professional with Update 5.
I used TSqlLanguageService.msi from the SQL 2016 RTM (not the developer edition).