tag:support.appharbor.com,2010-11-23:/discussions/problems/91270-no-luck-building-f-since-vs-2017-upgradeAppHarbor: Discussion 2017-07-22T20:12:11Ztag:support.appharbor.com,2010-11-23:Comment/428868782017-07-05T04:21:48Z2017-07-05T04:21:48ZNo Luck building F# since VS 2017 Upgrade<div><p>Hi,</p>
<p>This may well be related to a recent build server update, although it's interesting that this doesn't seem to be a general issue -- another customer did write about a similar issue just yesterday though. I noticed <a href="https://stackoverflow.com/questions/42679193/install-f-4-1-sdk-on-build-server/43919448#43919448">this suggested solution</a> which actually may be desirable in either case - particularly with regards to referencing NuGet package so you can depend entirely on the targets file there rather than the build server setup.</p>
<p>That said, the build servers have just been updated with the most recent VS 2017 build tools, and also includes the F# 4.1 compiler mentioned in the Stack Overflow answer I linked to above. The updated build tools also includes fixes related to F# project structure, so can you perhaps try and push your application again as this may already work without any modifications to your project(s)?</p>
<p>Best,<br>
Rune</p></div>runetag:support.appharbor.com,2010-11-23:Comment/428868782017-07-21T08:14:53Z2017-07-21T08:14:53ZNo Luck building F# since VS 2017 Upgrade<div><p>Just want to report back, the linked Stackoverflow answer helped me set up the build correctly.</p></div>rowinginmotiontag:support.appharbor.com,2010-11-23:Comment/428868782017-07-22T20:12:08Z2017-07-22T20:12:08ZNo Luck building F# since VS 2017 Upgrade<div><p>Ok great, thanks for the heads up!</p>
<p>Best,<br>
Rune</p></div>rune