.NEXT (dotNext) is a set of powerful libaries aimed to improve development productivity and extend .NET API with unique features. Some of these features are planned in future releases of .NET platform but already implemented in the library:
| Proposal | Implementation |
|---|---|
| Static Delegates | Value Delegates |
| Operators for IntPtr and UIntPtr | Extension methods for arithmetic, bitwise and comparison operations |
| Enum API | Documentation |
| Check if an instance of T is a default(T) | IsDefault() method |
| Concept Types | Documentation |
Expression Trees covering additional language constructs, i.e. foreach, await, patterns, multi-line lambda expressions |
Metaprogramming |
| Async Locks | Documentation |
| High-performance general purpose Write-Ahead Log | Persistent Log |
| Memory-mapped file as Memory<byte> | MemoryMappedFileExtensions |
| Memory-mapped file as ReadOnlySequence<byte> | ReadOnlySequenceAccessor |
Quick overview of additional features:
- Attachment of user data to arbitrary objects
- Automatic generation of Equals/GetHashCode for arbitrary type at runtime which is much better that Visual Studio compile-time helper for generating these methods
- Extended set of atomic operations. Inspired by AtomicInteger and friends from Java
- Fast Reflection
- Fast conversion of bytes to hexadecimal representation and vice versa using
ToHexandFromHexmethods from Span static class ManualResetEvent,ReaderWriterLockSlimand other synchronization primitives now have their asynchronous versions- Powerful concurrent ObjectPool
- Atomic memory access operations for arbitrary value types including enums
- PipeExtensions provides high-level I/O operations for pipelines such as string encoding and decoding
- Fully-featured Raft implementation
All these things are implemented in 100% managed code on top of existing .NET Standard stack without modifications of Roslyn compiler or CoreFX libraries.
Documentation for older versions:
Release Date: 06-14-2020
- More ways to create
MemoryOwner<T> - Removed copying of synchronization context when creating continuation for
Futureobject - Introduced APM helper methods in
AsyncDelegateclass
- Improved performance of
FileBufferingWriter FileBufferingWriternow contains correctly implementedBeginWriteandEndWritemethodsFileBufferingWriterables to return written content as ReadOnlySequence<byte>- Introduced
BufferWriterclass with extension methods for IBufferWriter<byte> aimed to encoding strings, primitive and blittable types - Support of
ulong,uintandushortdata types available for encoding/decoding inSequenceBinaryReaderandPipeExtensionsclasses - Ability to access memory-mapped file content via ReadOnlySequence<byte>
- Introduced null-coalescing assignment expression
- Updated dependencies
- Introduced null-coalescing assignment expression
- Updated dependencies
- Fixed race-condition caused by
AsyncTrigger.Signalmethod AsyncLocknow implements IAsyncDisposable interfaceAsyncExclusiveLock,AsyncReaderWriterLockandAsyncSharedLocknow have support of graceful shutdown implemented via IAsyncDisposable interface
- Optimized performance of methods in
MemoryMappedFileExtensionsclass - Updated dependencies
- Fixed behavior of
PersistentState.DisposeAsyncso it suppress finalization correctly
DotNext.AspNetCore.Cluster 2.6.0
- Respect shutdown timeout inherited from parent host in Hosted Mode
- Updated dependencies
DotNext.Augmentation.Fody 2.1.0
- Removed usage of obsolete methods from
Fody - Updated
Fodyversion
Changelog for previous versions located here.
- The libraries are versioned according with Semantic Versioning 2.0.
- Version 0.x and 1.x relies on .NET Standard 2.0
- Version 2.x relies on .NET Standard 2.1
| Version | .NET compatibility | Support Level |
|---|---|---|
| 0.x | .NET Standard 2.0 | Not Supported |
| 1.x | .NET Standard 2.0 | Maintenance |
| 2.x | .NET Standard 2.1 | Active Development |
Maintenance support level means that new releases will contain bug fixes only.
DotNext.AspNetCore.Cluster of version 1.x is no longer supported because of ASP.NET Core 2.2 end-of-life.
DotNext.Net.Cluster of version 1.x is no longer supported due to few reasons:
- Underlying implementation for ASP.NET Core is no longer supported
- Raft implementation is incomplete
Philosophy of development process:
- All libraries in .NEXT family based on .NET Standard to be available for wide range of .NET implementations: Mono, Xamarin, .NET Core
- Compatibility with AOT compiler should be checked for every release
- Minimize set of dependencies
- Rely on .NET Standard specification
- Provide high-quality documentation
- Stay cross-platform
- Provide benchmarks