Home → Knowledge Base →

Little tool to make sure VS2012 Fsharp projects are build.

• Edit

halcwb

09 Dec, 2014 05:54 PM

Building VS2012 fsharp projects resulted in an 'MSB4057: The target “Build” does not exist in the project.' error. However, this could be resolved by editing the project xml file (see: http://nikosbaxevanis.com/blog/2013/10/04/how-to-configure-msbuild-to-locate-the-f-number-build-targets/).
For large solutions, with a lot of fsharp projects this is a pain in the .. Therefore, I have a little command line tool that will do this for all fsharp projects it can find starting from a supplied root factory, i.e. fixfsrpoj.exe "/PATH".
The project can be found on GitHub, called fixfsproj (https://github.com/halcwb/fixfsproj).

1. Support Staff 1 Posted by Feodor Fitsner on 09 Dec, 2014 06:15 PM

   

   That's great, thanks. I'm moving it to KB section.

   • Edit

2. 2 Posted by halcwb on 09 Dec, 2014 07:18 PM

   

   Only, it there is one big caveat, it now builds OK on appveyor, but not on my local machine. I can build the projects in VS, but, using the Fake build script, it fails on my own local machine! So, be careful, I am not done with this yet!!

   • Edit

3. 3 Posted by halcwb on 10 Dec, 2014 12:00 AM

   

   Actually, this is very frustrating, I tried everything. Either I can run the build script on my machine, but then it fails in appveyor, or, I get it to run on appveyor, but then I cannot run the script locally. The only solution I have is to switch all the fsproj files to a 'appveyor version' before build.

   • Edit

4. 4 Posted by halcwb on 10 Dec, 2014 07:12 AM

   

   Finally got it all together. I have a before_build script that triggers the fixfsproj tool. This only runs at appveyor, so I can use my regular setup and build on my local machine. This seems finally to work.

   • Edit

5. Support Staff 5 Posted by Feodor Fitsner on 10 Dec, 2014 06:25 PM

   

   Cool, thanks!

   • Edit

6. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:50 AM.