Top 19 F# .NET Projects
-
Check out https://fsprojects.github.io/Paket/ and https://fake.build/ and https://docs.microsoft.com/en-us/dotnet/fsharp/get-started/get-started-vscode for playing with F#.
-
Giraffe is a library that sits atop ASP.NET Core and allows developers to build web applications in a functional style; dotnet new giraffe is literally my starting point when I begin a new web application project. (Rather than write three more sentences filled with effusive praise, I’ll just leave it at that; it’s great.) It also provides a view engine (that builds upon Suave‘s “experimental” view engine) which uses an F# DSL to define HTML in a strongly-typed way. It has been incredibly efficient for a while, but with .NET’s work over the past two releases at improving performance, and Giraffe’s adoption of those techniques, it is lightning fast.
-
-
Suave.IO
Suave is a simple web development F# library providing a lightweight web server and a set of combinators to manipulate route flow and task composition.
Giraffe is a library that sits atop ASP.NET Core and allows developers to build web applications in a functional style; dotnet new giraffe is literally my starting point when I begin a new web application project. (Rather than write three more sentences filled with effusive praise, I’ll just leave it at that; it’s great.) It also provides a view engine (that builds upon Suave‘s “experimental” view engine) which uses an F# DSL to define HTML in a strongly-typed way. It has been incredibly efficient for a while, but with .NET’s work over the past two releases at improving performance, and Giraffe’s adoption of those techniques, it is lightning fast.
-
-
Yes. You can use TensorFlow.NET or DiffSharp.
-
equinox
.NET Event Sourcing library with CosmosDB, EventStoreDB, SqlStreamStore and integration test backends. Focused at stream level; see https://github.com/jet/propulsion for cross-stream projections/subscriptions/reactions
F# works really well with event-driven architectures. Event sourcing and MVU/Elmish both work well with immutable data (you can't change an event after it's happened!). Discriminated unions are fantastic, and F# event sourcing/MVU libraries make liberal usage of them. Elmish is a frontend agnostic MVU library that has WPF/Javascript/WebAssembly implementations. On the event sourcing side there's Akka (though this is more actor model) and Equinox whose maintainer is incredibly friendly.
-
MiniScaffold
F# Template for creating and publishing libraries targeting .NET 5.0 `net5.0` or console apps .NET 5.0 `net5.0`.
-
Scout APM
Scout APM: A developer's best friend. Try free for 14-days. Scout APM uses tracing logic that ties bottlenecks to source code so you know the exact line of code causing performance issues and can get back to building a great product faster.
-
You can look at the csharp tests for examples https://github.com/plotly/Plotly.NET/tree/dev/tests/Plotly.NET.Tests.CSharp
-
Project mention: How would you handle this compiler error? Trying to emulate the onion approach to code architecture. | reddit.com/r/fsharp | 2021-04-05
https://github.com/lfr/FSharp.Domain.Validation is one project that aims to simplify this sort of validate-and-build pattern.
-
FSharp.Control.FusionTasks
F# Async workflow <--> .NET Task/ValueTask easy seamless interoperability library.
- 🌱 Github release
-
I know the open-source Armitage project, but I'm not quite sure what you mean, since it is a different project. I said that I'm in the same position because neither all my projects are closed source too (https://github.com/enkomio/Sojobo, https://github.com/enkomio/sacara, https://github.com/enkomio/anathema, https://github.com/enkomio/shed, https://github.com/enkomio/s4tanic0d3). The main difference that I see is that Armitage had much more visibility. Don't get me wrong, I'm not discrediting Armitage, it is a nice project that was able to fulfill an existing gap with a perfect time-to-market. So, if I understood correctly, even if we both released open source projects without any hidden malicious intent, I don't deserve trust because I didn't release a project with a good visibility, am I correct?
-
They are slightly different and depending on your background one might feel more confortable than the other Feel free to choose the one you like the best, in my case I will continue the rest of the post with the Expression based one given that we already have some expression based code from Dapper.FSharp. Previously we added some authors, let'ts try to add Posts to those authors with Donald.
-
Project mention: Perfect F# React Dev Setup in F# Fable with VS Code, Formatting/Linting | dev.to | 2021-09-08
Dealing with both package manager can be a burden, so please install femto, a very easy-to-use & magic dotnet CLI tool:
-
Perla
A cross-platform tool for unbundled front-end development that doesn't depend on Node or requires you to install a complex toolchain
I keep working on Perla :) https://github.com/AngelMunoz/Perla
-
FsLibLog
FsLibLog is a single file you can copy paste or add through Paket Github dependencies to provide your F# library with a logging abstraction. This is a port of the C# LibLog.
-
> Every time I tried to write something quickly, I often had to choose between a heavily functional programming oriented frameworks or extremely tedious ASP.NET Core.
I had the exact same sentiment last year. made https://wiz.run/
I hated going through all the microsoft dotnet docs. Wanted something like this: https://wiz.run/api/
-
Mondocks
An alternative way to interact with MongoDB databases from F# that allows you to use mongo-idiomatic constructs
Mondocks - MongoDB DSL for the MongoDB .NET Driver
-
During the hacktoberfest, we open source Diffract. It is a .NET library that displays a readable diff between two objects. It is particularly useful for unit testing complex objects. The library is written in F# but works with both F# and C#. Here is an example from the readme with union where the case is different:
-
Symbolica.Extensions.Configuration.FSharp
Provides a safe API for binding the dotnet IConfiguration to types in F#.
One area where this was frequently biting us was the binding of configuration data using the Microsoft.Extensions.Configuration library. Due to this and other problems that we'll go into below, we created a safer alternative for configuration binding for F# projects called Symbolica.Extensions.Configuration.FSharp and open-sourced it on GitHub.
F# .NET related posts
Index
What are some of the best open-source .NET projects in F#? This list will help you:
| Project | Stars | |
|---|---|---|
| 1 | Paket | 1,786 |
| 2 | Giraffe | 1,698 |
| 3 | Suave.IO | 1,224 |
| 4 | Avalonia.FuncUI | 423 |
| 5 | DiffSharp | 416 |
| 6 | equinox | 326 |
| 7 | MiniScaffold | 221 |
| 8 | Plotly.NET | 219 |
| 9 | FSharp.Domain.Validation | 144 |
| 10 | FSharp.Control.FusionTasks | 140 |
| 11 | Sojobo | 125 |
| 12 | Donald | 109 |
| 13 | Femto | 104 |
| 14 | Perla | 46 |
| 15 | FsLibLog | 43 |
| 16 | wiz | 32 |
| 17 | Mondocks | 31 |
| 18 | Diffract | 12 |
| 19 | Symbolica.Extensions.Configuration.FSharp | 10 |
Are you hiring? Post a new remote job listing for free.
