Epiforge.Extensions.Components 4.1.1

.NET 6.0 This package targets .NET 6.0. The package is compatible with this framework or higher. 
dotnet add package Epiforge.Extensions.Components --version 4.1.1
                    


                    

                
NuGet\Install-Package Epiforge.Extensions.Components -Version 4.1.1
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="Epiforge.Extensions.Components" Version="4.1.1" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
<PackageVersion Include="Epiforge.Extensions.Components" Version="4.1.1" />
                    


                            Directory.Packages.props
                        

                    

                
<PackageReference Include="Epiforge.Extensions.Components" />
                    


                            Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package. 
paket add Epiforge.Extensions.Components --version 4.1.1
                    


                    

                
#r "nuget: Epiforge.Extensions.Components, 4.1.1"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
#:package Epiforge.Extensions.Components@4.1.1
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package. 
#addin nuget:?package=Epiforge.Extensions.Components&version=4.1.1
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=Epiforge.Extensions.Components&version=4.1.1
                    


                            Install as a Cake Tool

Property Change Notification

This library offers the PropertyChangeNotifier class, which you may inherit from to quickly get all the property utilities we're all tired of copying and pasting everywhere. Just call the protected OnPropertyChanged and OnPropertyChanging methods at the appropriate times from setters and compiler services will figure out what property you're in. Or, if all you need to do is set the value of a field, SetBackedProperty couldn't make it any easier or convenient to handle that as efficiently as possible. DynamicPropertyChangeNotifier is also available if your class needs to be dynamic.

Be sure to set the protected Logger property if you want the abstract class to log what's going on with property change notification.

Disposal

This library features base classes that handle things we've written a thousand times over, this time involving disposal. If you want to go with an implementation of the tried and true IDisposable, just inherit from SyncDisposable. Want a taste of the new IAsyncDisposable? Then, inherit from AsyncDisposable. Or, if you want to support both, there's Disposable. Additionally, if your object needs to be dynamic, you can use DynamicSyncDisposable, DynamicAsyncDisposable, or DynamicDisposable. And if your object has no unmanaged resources to release and no need to announce its disposal as a property change, there are PlainSyncDisposable, PlainAsyncDisposable, and PlainDisposable, which keep the disposal claim, the events, and the ability to override disposal, but are not property change notifiers and declare no finalizer, which makes them meaningfully smaller. Because they have no finalizer, nothing at all happens if disposal is neglected, so hold unmanaged resources in a SafeHandle or use one of the classes above; their synchronous method is DisposeCore, which takes no argument, because without a finalizer nothing could pass false. Each of these features abstract methods to actually do your disposal. On Disposable and DynamicDisposable, the asynchronous one, DisposeAsyncCore, is virtual and defaults to the synchronous Dispose(bool), so a type whose cleanup is entirely synchronous only writes it once. On AsyncDisposable and DynamicAsyncDisposable it stays abstract, because there is no synchronous path for it to delegate to. But all of the base classes feature:

  • proper implementation of the finalizer and use of GC.SuppressFinalize, save for the plain classes, which declare no finalizer
  • monitored access to disposal to ensure it can't happen twice
  • the ability to override or "cancel" disposal by returning false from the abstract methods (e.g. you're reference counting and only want to dispose when your counter reaches zero)
  • a protected ThrowIfDisposed method you can call to before doing anything that requires you haven't been disposed
  • an IsDisposed property the value of which is handled for you, along with its change notifications on all but the plain classes

This library provides the IDisposalStatus interface, which defines the IsDisposed property and all the base classes implement it. This library also provides the INotifyDisposing, INotifyDisposed, and INotifyDisposalOverridden interfaces, which add events that notify of these occurrences.

Be sure to set the protected Logger property if you want the abstract class to log what's going on with disposal; the plain classes do not log, which is part of what makes them smaller.

Reflection

This library has useful tools for when you can't be certain of some things at compile time, such as types, methods, etc. While .NET reflection is immensely powerful, prior to .NET 7, it's not very quick. To address this, this library offers the following extension methods which will emit IL, generate delegates, and cache them for expedited use of Reflection:

  • ConstructorInfo.FastInvoke: call a constructor only known at runtime quickly
  • MethodInfo.FastInvoke: call a method only known at runtime quickly
  • PropertyInfo.FastGetValue: get the value of a property only known at runtime quickly
  • PropertyInfo.FastSetValue: set the value of a property only known at runtime quickly
  • Type.FastDefault: get the default value of a type only known at runtime quickly
  • Type.GetImplementationEvents: searches for the events of a type, including interfaces and interface inheritance
  • Type.GetImplementationMethods: searches for the methods of a type, including interfaces and interface inheritance
  • Type.GetImplementationProperties: searches for the properties of a type, including interfaces and interface inheritance

Use of these methods in .NET 7 or later will simply call the built-in methods, as they are now optimized.

This library also offers FastComparer and FastEqualityComparer, which implement IComparer and IEqualityComaprer, respectively, but quickly use the methods of Comparer<>.Default and EqualityComaprer<>.Default, respectively, to do their work.

In addition (pun intended), this library offers GenericAddition, GenericSubtraction, GenericMultiplication, and GenericDivision, which will produce delegates that will perform the respective operations with values of supplied generic type arguments.

Exceptions

This library provides extension methods for dealing with exceptions:

  • GetFullDetails - creates a representation of an exception and all of its inner exceptions, including exception types, messages, and stack traces, and traversing multiple inner exceptions in the case of AggregateException and ReflectionTypeLoadException

Threading

This library provides classes for use in threading scenarios:

  • AsyncSynchronizationContext - A SynchronizationContext that uses the Task Parallel Library (TPL) to process callbacks asynchronously
Product Compatible and additional computed target framework versions.
.NET net6.0 is compatible.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 is compatible.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed.  net9.0 is compatible.  net9.0-android was computed.  net9.0-browser was computed.  net9.0-ios was computed.  net9.0-maccatalyst was computed.  net9.0-macos was computed.  net9.0-tvos was computed.  net9.0-windows was computed.  net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (4)

Showing the top 4 NuGet packages that depend on Epiforge.Extensions.Components:

Package Downloads
Epiforge.Extensions.Expressions

This package assists in operating with expressions.
Epiforge.Extensions.Collections

This package assists in operating with collections.
Epiforge.Extensions.Platforms.Windows

This package assists in Windows-platform specific operations.
Epiforge.Extensions.Frameworks.WPF

This package assists in developing WPF-based applications.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
4.1.1 0 8/30/2026
4.1.0 41 8/29/2026
4.0.0 164 8/27/2026
3.1.0 387 5/6/2026
3.0.0 280 4/14/2026
2.0.1 394 12/24/2025
2.0.0 709 4/17/2025
1.7.0 353 12/30/2023
1.6.0 313 12/28/2023
1.5.0 488 8/18/2023
1.4.0 1,067 8/11/2023
1.3.2 362 8/10/2023
1.3.1 266 8/10/2023
1.3.0 301 7/20/2023
1.2.0 315 7/3/2023
1.1.1 314 6/25/2023
1.1.0 498 5/29/2023
1.0.0 338 5/28/2023

FastEqualityComparer and FastComparer no longer reach the default comparer through reflection. Each comparison allocated a two-element argument array and boxed its result, costing sixty-four bytes and about fourteen nanoseconds; a comparison is now a virtual call and two unboxes, costing about four tenths of a nanosecond and nothing. The types and their members are unchanged, so consumers need do nothing to receive this.