In simple terms, before we write a line of code, we start each sprint planning session by outlining a blog post describing what our next release will be.
We developers spend lot of our time reading code. We read code so that we know how to change it to implement a new feature, fix a bug, etc. It is much better to work in a code base where code is easy to read and understand.
One thing that can make code readable is good naming. Giving variables, classes, and methods good names makes code easier to read.
Keeping up with JavaScript frameworks can be a challenge. There are a lot of them, and seemingly another one every month. How do you know which ones might be right for your project? What are their strengths and weaknesses? How do you get started?
.NET Core 2.1-Preview2 comprises:
- .NET Core Runtime 2.1.0-preview2-26406-04
- .NET Core SDK 2.1.300-preview2-008530
| | SDK Installer | SDK Binaries | Runtime Installer | Runtime Binaries |
|---|---|---|---|---|
| Windows | 32-bit / 64-bit | 32-bit / 64-bit | 32-bit / 64-bit | 32-bit / 64-bit |
| macOS | 64-bit | 64-bit | 64-bit | 64-bit |
| Linux * | See installations steps below | 64-bit | - | 64-bit |
This updated of the SDK includes the previously released .NET Core 2.0.3 Runtime.
| | SDK Installer | SDK Binaries | Runtime Installer | Runtime Binaries |
|---|---|---|---|---|
| Windows | 32-bit / 64-bit | 32-bit / 64-bit | 32-bit / 64-bit | 32-bit / 64-bit |
| macOS | 64-bit | 64-bit | 64-bit | 64-bit |
| Linux * | See installations steps below | 64-bit | - | 64-bit |
- .NET Core SDK 2.0.2
- .NET Core Runtime 2.0.0 (previously released)
| | SDK Installer | SDK Binaries | Runtime Installer | Runtime Binaries |
|---|---|---|---|---|
| Windows | 32-bit / 64-bit | 32-bit / 64-bit | 32-bit / 64-bit | 32-bit / 64-bit |
| macOS | 64-bit | 64-bit | 64-bit | 64-bit |
| Linux * | - | 64-bit | - | 64-bit |
| Ubuntu | See installations steps below | 64-bit | See installation steps below | 64-bit |
- .NET Core 3.1.7 and .NET Core SDK ( Download | Release Notes )
- .NET Core 2.1.21 and .NET Core SDK ( Download | Release Notes )
4x runtime performance enhancement on our NotifyPropertyChanged aspect.
Improved reliability and scope of our deadlock detection policy.
Dynamic advices: see IAdviceProvider, IntroduceInterface, ImportLocation, ImportMethod, IntroduceMethod.
Aspect Repository and Late Validation.
OnInstanceConstructed advice.
Faster advice state lookup: see DeclarationIdentifier.
This page describes how to use the Microsoft.CodeAnalysis.Metrics package to perform source code analysis of .NET assemblies from a console application. Visual Studio users can perform source code analysis by clicking the "Analyze" dropdown menu and selecting "Calculate Code Metrics", but I sought to automate this process so I can generate custom code analysis reports from console applications as part of my CI pipeline.
In this post, I want to compare “DNTFrameworkCore” with “ABP Framework”.
ABP is one of most popular and well documented frameworks with high level abstraction that I learned a lot from it. It has many other features that I don’t list them in this post, because, DNTFrameworkCore has not them actually. Behind of ABP, there is a team. It has 123 contributors in GitHub. Also, all of features have related unit-tests.
In other side, DNTFrameworkCore is lightweight with low level abstraction. It is personal open-source project without any contributor and has unit-tests for small part.
I wrote this post to prove that thinking behind of DNTFrameworkCore completely different from ABP (at least in most sections)
