Releases: pamidur/aspect-injector
Releases · pamidur/aspect-injector
2.2.8
- Fixed regression where putting string into or out of string array caused issues
- Now forced all aspects to be public
2.2.7
It took us quite a while to fix these severe issues:
Scope.PerInstance
now works correctly even for complex generics-involved hierarchy of classes from many assemblies #99
- Fixed generic types resolution for bases classes. Overall refactored call references creation and generics resolution #97
2.2.6
Fixed (I hope) execution on pure netcore 3.0+ environments such as docker containers #118.
2.2.5
- fixed #114
- added version to AI output
2.2.2
- fixed compatibility with VS Live Tests #105
- added ability disable Aspect Injector with
$(AspectInjectorEnabled) = true
in *.*proj file
2.2.1
New features release!
- you can inject around constructors now!
[Injection]
attribute has new propagation control feature via Injection.Propagation
and Injection.PropagationFilter
properties. Where you can setup propagation strategy and regex filter respectively.
- Compiler generated members (e.g. named and anonymous methods) are skipped by default. Use
[Injection( ... , Propagation = PropagateTo.Everything)]
2.1.1
Regression bugfix release:
- fixed #70 and generally added tests to check that there is no platform dependent references added to target assemblies. This ensures that only netstandard references can be added to targets.
1.0.2
Bugfix release for v1 (Legacy):
2.1.0
In this release doesn't have a lot of changes, however where moving to separating il processing into another library. Thus version is bumped to 2.1.0.
Also:
- fixed issue #90 , so now we support aspnetcore 3
- fixed transitive build, you can only reference AspectInjector once in library where you have aspects and the just reference only your library (only vs2019).
2.0.6
Fixed:
- #85 Correctly treating generic constraints