Expecto
MSBuild
Our great sponsors
Expecto | MSBuild | |
---|---|---|
2 | 19 | |
654 | 5,132 | |
- | 0.9% | |
6.6 | 6.9 | |
11 days ago | 4 days ago | |
F# | C# | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Expecto
-
Resources to learn the F# ecosystem
Unit testing: I personally use FsUnit, specifically FsUnit.Xunit. There's some other libraries like Expecto and Hedgehog (property testing), but I haven't found a reason to use them. I recently started experimenting a little with Hedgehog. FsUnit integrates well into Visual Studio, since it sits nicely on top of NUnit and xUnit, and it's done everything I've needed so far.
-
Das.Test - an opinionated unit testing library written in F# for F#
Beside, did you try Expecto? https://github.com/haf/expecto
MSBuild
-
Sharing Saturday #459
I did get confirmation that the actual kill has been postponed to .Net 9.0 rather than .Net 8.0 . However, that PR is factually wrong regarding when System.Runtime.Serialization use became opt-in -- I had to counter-adjust Rogue Survivor Revived to opt into using System.Runtime.Serialization for .Net 7.0, last November i.e. Nov 2022.
-
Did anyone figure out a way to compile .NET Core with WPF on Linux?
Like this https://github.com/dotnet/msbuild/blob/d0060335c1fb2f0523b1cf4656c464c5c4316783/src/Framework/NativeMethods.cs
- Why does Microsoft still insist on using XML for configuration files like `.csproj`, etc.?
-
[Copilot has] been a massive productivity improvement to our senior devs, and I got so used to it that it's an annoyance when Copilot doesn't respond.
Here is a taste of what to expect: https://github.com/dotnet/msbuild
-
Resources to learn the F# ecosystem
The main thing they do is to list projects so that you can open a solution and see a set of projects, or build a solution and build everything there. They also give a lot of customization and fortunately it's rare that you need to know anything about that. It does feel somewhat unnecessary since you should be able to open a project with its dependencies. Hopefully solution files are going to be cleaned up: https://github.com/dotnet/msbuild/issues/1730
-
Build to order? Checking MSBuild for the second time
Since the previous check, the project has grown a lot. Our analyzer has become more advanced, too. This only makes this task more interesting! Despite the high quality of the MSBuild product and the well-known name of its creator, we again managed to find some issues in MSBuild's source code. The project is almost entirely written in C#. You can see it on GitHub. We took the code from this commit.
- Gauging broader interest in a .sln file generator based on a new DSL?
-
New format for solution (.sln) files
relevant github issue: https://github.com/dotnet/msbuild/issues/1730
-
How can I compile a C# program with a different version of glibc?
msbuild is the "make" system, but for .Net. Those .csproj files are just makefiles by another name. Also, msbuild is not Windows-only. The readme specifically states that it can run on Unix (and Unix-like) systems that support .Net Core.
-
The most interesting C# / .NET blogs and websites
You can't do without source files when you want to better understand what is happening "under the hood" of a particular system. For example, do you want to improve your understanding of how types from the standard library work? The source code of .NET Framework and .NET will help you to do that. Do you want to dig deeper into the compiler? No problem - here is the Roslyn's source code at your service. Do you need to look inside the build system? Here you go - the MSBuild code is also open-source. By the way, if you are interested in build processes, you may also find MSBuild Structured Log Viewer useful. It's a tool that allows you to work with MSBuild build logs in a convenient format.
What are some alternatives?
xUnit - xUnit.net is a free, open source, community-focused unit testing tool for .NET.
Cake - :cake: Cake (C# Make) is a cross platform build automation system.
FsCheck - Random Testing for .NET
NUKE - 🏗 The AKEless Build System for C#/.NET
NFluent - Smooth your .NET TDD experience with NFluent! NFluent is an ergonomic assertion library which aims to fluent your .NET TDD experience (based on simple Check.That() assertion statements). NFluent aims your tests to be fluent to write (with a super-duper-happy 'dot' auto-completion experience), fluent to read (i.e. as close as possible to plain English expression), but also fluent to troubleshoot, in a less-error-prone way comparing to the classical .NET test frameworks. NFluent is also directly inspired by the awesome Java FEST Fluent assertion/reflection library (http://fest.easytesting.org/)
Roslyn - The Roslyn .NET compiler provides C# and Visual Basic languages with rich code analysis APIs.
NUnit - NUnit Framework
Psake - A build automation tool written in PowerShell
Fine Code Coverage - Visualize unit test code coverage easily for free in Visual Studio Community Edition (and other editions too)
FAKE - FAKE - F# Make
Canopy - f# web automation and testing library, built on top of Selenium (friendly to c# also)
CS Make - Sake Build