Just upgraded to Visual Studio 2017, and quickly realized that TeamCity 9.1.7 (the version we have installed presently) does not support VS 2017. I can compile a VS 2017 solution using the VS 2015 solution runner, so long as I don't make use of any C# 7.0 language constructs (which was kind of the point of updating, really).
Was told by our DevOps team that an upgrade to TeamCity 10 is not in the cards for a while, so that is not currently an option.
Given that you have to install Visual Studio on the build agent in order for it to even work, is there a way we can tell TeamCity (or, rather, have TeamCity tell the build agent) to compile a VS 2017 solution without requiring the VS 2017 sln runner? For example, the NUnit build step allows us to manually specify the location and arguments for a console runner; is there something similar for .NET code compilation, by any chance?