PerrypheralFramework.CS
1.4.0
See the version list below for details.
dotnet add package PerrypheralFramework.CS --version 1.4.0
NuGet\Install-Package PerrypheralFramework.CS -Version 1.4.0
<PackageReference Include="PerrypheralFramework.CS" Version="1.4.0" />
paket add PerrypheralFramework.CS --version 1.4.0
#r "nuget: PerrypheralFramework.CS, 1.4.0"
// Install PerrypheralFramework.CS as a Cake Addin #addin nuget:?package=PerrypheralFramework.CS&version=1.4.0 // Install PerrypheralFramework.CS as a Cake Tool #tool nuget:?package=PerrypheralFramework.CS&version=1.4.0
Facilitatates IoC, Event Aggregation, and provides tools for Meta Developers, such as Reflection Extension Methods and Attribute Interpretation Services.
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET Framework | net45 is compatible. net451 was computed. net452 was computed. net46 was computed. net461 was computed. net462 was computed. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
This package has no dependencies.
NuGet packages (1)
Showing the top 1 NuGet packages that depend on PerrypheralFramework.CS:
Package | Downloads |
---|---|
PerrypheralFramework.WPF
Facilitates Development of WPF Applications using Markup Extensions and MVVM Utility Classes. |
GitHub repositories
This package is not used by any popular GitHub repositories.
Collection Injection (for both Dictionary<K,V> and List<T> annotated properties) is now supported.
Be sure to check out the Mvvm-IoC section in the Wiki for the how to and examples.
PerrypheralGC
Memory leaks cleaned - weak reference model applied.
EventAggregator
1) A slight change in subscription admissibility
Any instance can subscribe any of it's instance methods for the same message type as many times as required, per Token value.
This means that for class C, method M and token T there can exist only one entry in the Listener Queue of some message.
The null token (or using no token) counts as a token as well, for that manner.
2) A Slight change in the semantics of Unsubscribe
It is quite possible that the same thread which is handling a publishing of a message is removing a subscribed method from the same message's queue.
This can cause missed deliveries in some instances.
To remedy this, semantic unsubscription has been introduced.
Meaning that while the unsubscribed handler will effectively no longer be invoked, it is still present in the queue until Clean has been called on that queue's instance.
3) Adding a semantically removed subscriber
This will semantically subscribe the instance, meaning that from that point onwards it will once more receive messages.
3)Clean
will immediately return if a message is being published on the same method stack as the clean request.