0
FAKE (F# MAKE) &
AUTOMATION
@sergey_tihon
2014
DO YOU HAVE A BUILD SCRIPT
ON YOUR PROJECT?
WHAT DO YOU USE FOR
BUILD AUTOMATION?
DID YOU WRITE BUILD
SCRIPTS?
MSBuildRAKE
MAKE
Build Tools Roundup For .NET Systems
http://lostechies.com/derickbailey/2010/05/10/build-tools-for-net-sy...
FAKE - F# MAKE -
HTTP://FSHARP.GITHUB.IO/FAKE/
Steffen
Forkmann
@sforkmann
F# and Dynamics NAV developer,
blogger and some...
GETTING STARTED WITH
FAKE
HTTP://FSHARP.GITHUB.IO/FAKE/GETTINGSTARTED.HTML
EVERYTHING IS ON NUGET
HELLO WORLD SAMPLE
CLEANING THE LAST BUILD
OUTPUT
COMPILING THE APPLICATION
FILESETS
COMPILING TEST PROJECTS
UNITTESTS
ADDING FXCOP
GENERATE ASSEMBLYINFO FILES
CREATING NUGET PACKAGE
AWESOME DOCUMENTATION
http://fsharp.github.io/FAKE/apidocs/
WHO USE FAKE?
• Octokit by GitHub
• msu solutions GmbH
• E.On Global Commodities UK
• Akka.net
• Portable.Licensing
• Feat...
BUILDING GREAT OPEN-SOURCE
LIBRARIES
HTTP://TOMASP.NET/BLOG/20
13/GREAT-OPEN-SOURCE/
Tomas Petricek
@tomaspetricek
MVP, F#...
EVERY GOOD OPEN-SOURCE LIBRARY NEEDS TO
HAVE:
1. UNIT TESTS - at least for non-trivial parts of code and to prevent
regres...
FAKE CAN HELP YOU WITH:
1. UNIT TESTS - at least for non-trivial parts of code and to prevent
regressions
2. RANDOM TESTIN...
FOR THOSE WHO INTERESTED IN CORRECTNESS
1. UNIT TESTS - at least for non-trivial parts of code and to prevent
regressions
...
FSharp.ProjectScaffo
ld
Demo
HTTPS://github.com/fsprojects/FSharp.ProjectScaf
fold
QUESTIONS?
THANK YOU!
Ask me @sergey_tihon
Ask FAKE @fsharpMake
Ask about #FSharp
Upcoming SlideShare
Loading in...5
×

FAKE (F# Make) & Automation

994

Published on

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
994
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
4
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Transcript of "FAKE (F# Make) & Automation"

  1. 1. FAKE (F# MAKE) & AUTOMATION @sergey_tihon 2014
  2. 2. DO YOU HAVE A BUILD SCRIPT ON YOUR PROJECT?
  3. 3. WHAT DO YOU USE FOR BUILD AUTOMATION?
  4. 4. DID YOU WRITE BUILD SCRIPTS?
  5. 5. MSBuildRAKE MAKE Build Tools Roundup For .NET Systems http://lostechies.com/derickbailey/2010/05/10/build-tools-for-net-systems-it-s-no-longer-a-question-of-features/
  6. 6. FAKE - F# MAKE - HTTP://FSHARP.GITHUB.IO/FAKE/ Steffen Forkmann @sforkmann F# and Dynamics NAV developer, blogger and sometimes speaker. Creator of FAKE - F# Make and NaturalSpec. MVP for F#.
  7. 7. GETTING STARTED WITH FAKE HTTP://FSHARP.GITHUB.IO/FAKE/GETTINGSTARTED.HTML
  8. 8. EVERYTHING IS ON NUGET
  9. 9. HELLO WORLD SAMPLE
  10. 10. CLEANING THE LAST BUILD OUTPUT
  11. 11. COMPILING THE APPLICATION
  12. 12. FILESETS
  13. 13. COMPILING TEST PROJECTS
  14. 14. UNITTESTS
  15. 15. ADDING FXCOP
  16. 16. GENERATE ASSEMBLYINFO FILES
  17. 17. CREATING NUGET PACKAGE
  18. 18. AWESOME DOCUMENTATION http://fsharp.github.io/FAKE/apidocs/
  19. 19. WHO USE FAKE? • Octokit by GitHub • msu solutions GmbH • E.On Global Commodities UK • Akka.net • Portable.Licensing • FeatureSwitcher • Machine.Fakes • Enticify • SolrNet • Carbonite • FSharp.Compiler.Service • Visual F# Power Tools • Deedle by BlueMountainCapital • fsharpx • FSharp.Data • FSharp.Charting • NuGetPlus • FsPickler http://fsharp.github.io/FAKE/users.html
  20. 20. BUILDING GREAT OPEN-SOURCE LIBRARIES HTTP://TOMASP.NET/BLOG/20 13/GREAT-OPEN-SOURCE/ Tomas Petricek @tomaspetricek MVP, F# enthusiast, book author and a PhD student at the University of Cambridge.
  21. 21. EVERY GOOD OPEN-SOURCE LIBRARY NEEDS TO HAVE: 1. UNIT TESTS - at least for non-trivial parts of code and to prevent regressions 2. RANDOM TESTING - for tricky parts of code, it is useful and helps checking unexpected cases 3. NUGET PACKAGE - or other up-to-date and easy to use release 4. DOCUMENTATION - for public API, at least when the API is not super simple 5. TUTORIALS & WALKTHROUGHS - showing how to call the API in a larger-scale scenarios 6. AUTOMATION - when releasing a new version, all of the above should happen with "one click" and documentation with tutorials must be up-to-date and correct.
  22. 22. FAKE CAN HELP YOU WITH: 1. UNIT TESTS - at least for non-trivial parts of code and to prevent regressions 2. RANDOM TESTING - for tricky parts of code, it is useful and helps checking unexpected cases 3. NUGET PACKAGE - or other up-to-date and easy to use release 4. DOCUMENTATION - for public API, at least when the API is not super simple 5. TUTORIALS & WALKTHROUGHS - showing how to call the API in a larger-scale scenarios 6. AUTOMATION - when releasing a new version, all of the above should happen with "one click" and documentation with tutorials must be up-to-date and correct.
  23. 23. FOR THOSE WHO INTERESTED IN CORRECTNESS 1. UNIT TESTS - at least for non-trivial parts of code and to prevent regressions 2. RANDOM TESTING - for tricky parts of code, it is useful and helps checking unexpected cases 3. NUGET PACKAGE - or other up-to-date and easy to use release 4. DOCUMENTATION - for public API, at least when the API is not super simple 5. TUTORIALS & WALKTHROUGHS - showing how to call the API in a larger-scale scenarios 6. AUTOMATION - when releasing a new version, all of the above should happen with "one click" and documentation with tutorials must be up-to-date and correct. http://www.meetup.com/fsharpminsk/events/1817675 52/
  24. 24. FSharp.ProjectScaffo ld Demo HTTPS://github.com/fsprojects/FSharp.ProjectScaf fold
  25. 25. QUESTIONS? THANK YOU! Ask me @sergey_tihon Ask FAKE @fsharpMake Ask about #FSharp
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×