rune on 05 Jul, 2017 04:21 AM
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 this suggested solution 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.
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)?