{"id":950,"date":"2010-02-14T16:56:07","date_gmt":"2010-02-14T16:56:07","guid":{"rendered":"http:\/\/www.navision-blog.de\/2010\/02\/14\/fake-f-make-0-29-released-ready-for-f-february-2010-ctp-and-net-4-0-rc\/"},"modified":"2010-02-14T17:46:40","modified_gmt":"2010-02-14T17:46:40","slug":"fake-f-make-0-29-released-ready-for-f-february-2010-ctp-and-net-4-0-rc","status":"publish","type":"post","link":"http:\/\/www.navision-blog.de\/blog\/2010\/02\/14\/fake-f-make-0-29-released-ready-for-f-february-2010-ctp-and-net-4-0-rc\/","title":{"rendered":"“FAKE – F# Make” 0.29 released – Ready for F# February 2010 CTP and .NET 4.0 RC"},"content":{"rendered":"

Last week I released version 0.29 of my build automation tool \u201cFAKE \u2013 F# Make\u201d. The new version comes along with a couple of changes which I will now describe.<\/p>\n

F# February 2010 CTP and .NET 4.0 RC<\/h5>\n

\u201cFAKE \u2013 F# Make\u201d should be completely compatible with both, the F# February 2010 CTP<\/a> and the F# version which is included in Visual Studio 2010 RC<\/a>.<\/p>\n

FAKE self build and binaries on teamcity.codebetter.com<\/h5>\n

Since \u201cFAKE \u2013 F# Make\u201d is a build automation tool, it was always used for it\u2019s own build process. Now this build process could be moved to an open CI server at teamcity.codebetter.com<\/a>. If you login as a guest you can download the latest \u201cFAKE \u2013 F# Make\u201d binaries from there.<\/p>\n

FAKE on build servers without F#<\/h5>\n

With the new F# CTP there is no longer a need for installing F# on the build agents. In fact FAKE itself was built on build agents which don\u2019t have a F# installation. <\/p>\n

If you want to create such build scripts you have to do the following:<\/p>\n

    \n
  1. Download the standalone zip file of the F# CTP<\/a> <\/li>\n
  2. Put the bin subfolder into your project tree <\/li>\n
  3. Modify the FSIPath value in the FAKE.exe.config file to match your FSharp bin folder\n
      \n
    1. If you copy the contents the F# bin folder into .\/tools\/FSharp\/ it should just work. <\/li>\n<\/ol>\n<\/li>\n<\/ol>\n

      If you have F# projects you also need to modify your .fsproj files like this:<\/p>\n

      <PropertyGroup>
         \u2026.
        <FscToolPath>..\\..\\..\\tools\\FSharp\\<\/FscToolPath>
      <\/PropertyGroup>
      \u2026
      <Import Project="..\\..\\..\\tools\\FSharp\\Microsoft.FSharp.Targets" \/><\/p>\n

      This modifications should take care that MSBuild will use the F# compiler from your tools paths.<\/p>\n

      Generate your documentations with \u201cdocu\u201d<\/h5>\n
      \n

      \u201cWhat’s a docu?<\/strong> A documentation generator for .Net that isn’t complicated, awkward, or difficult to use. Given an assembly and the XML that’s generated by Visual Studio, docu can produce an entire website of documentation with a single command.\u201d [docu Homepage<\/a>]<\/p>\n<\/blockquote>\n

      \u201cFAKE \u2013 F# Make\u201d 0.29 is bundled with this new documentation tool which can easily convert your xml-Documentation into some nice html pages. You can use the tool with the new Docu task like this:<\/p>\n

      \n

      Target? GenerateDocumentation <-<\/p>\n

          fun<\/span> _ -><\/span><\/p>\n

              Docu (fun<\/span> p -><\/span><\/p>\n

                  {p with<\/span><\/p>\n

                     ToolPath = @".\\tools\\FAKE\\docu.exe"<\/span><\/p>\n

                     TemplatesPath = @".\\tools\\FAKE\\templates"<\/span><\/p>\n

                     OutputPath = docDir })<\/p>\n

                  (buildDir + "MyAssembly.dll"<\/span>)<\/p>\n<\/p><\/div>\n

      You will also need the docu templates, which you can download from the product homepage. I\u2019m planning to bundle some basic templates with the next version of FAKE.<\/p>\n

      What\u2019s next?<\/h5>\n

      At the moment I\u2019m working on ILMerge<\/a> task for FAKE. I hope to release this with the next version. There are also some open issues with the Mono support but since teamcity.codebetter.com is getting a mono build agent I hope to make some progress here too.<\/p>\n

      If you have any questions or ideas for new features please contact me.<\/p>\n","protected":false},"excerpt":{"rendered":"

      Last week I released version 0.29 of my build automation tool \u201cFAKE \u2013 F# Make\u201d. The new version comes along with a couple of changes which I will now describe. F# February 2010 CTP and .NET 4.0 RC \u201cFAKE \u2013 F# Make\u201d should be completely compatible with both, the F# February 2010 CTP and the […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[23,448,546],"tags":[492,664,545],"_links":{"self":[{"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/posts\/950"}],"collection":[{"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/comments?post=950"}],"version-history":[{"count":5,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/posts\/950\/revisions"}],"predecessor-version":[{"id":955,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/posts\/950\/revisions\/955"}],"wp:attachment":[{"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/media?parent=950"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/categories?post=950"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/tags?post=950"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}