Release 2.3.4

• 65e58d0 Fixed issue causing async response interceptors not being invoked

Release 2.3.3

d09abae Fixed issue where stack traces from handler exceptions were not preserved

Release 2.3.2

Throws exception if an interceptor cannot be resolved, solving #26

Release 2.3.1

Appeaser 2.3.1

Stabilized version

Appeaser.Microsoft.DependencyInjection 1.2.0

Multitargeting netstandard2.1 and netstandard2.0 for better compatability with core 3.X projects

Appeaser.Microsoft.ApplicationInsights 0.3.0

Multitargeting netstandard2.1 and netstandard2.0 for better compatability with core 3.X projects

Appeaser.Microsoft.ApplicationInsights.AspNetCore 0.3.0

Multitargeting netstandard2.1 and netstandard2.0 for better compatability with core 3.X projects

Appeaser 2.3.1-rc.1

Small internal change, 2893045 , to how async interceptors are executed in order to work around diagnostic activity, see #25.

Appeaser.Microsoft.DependencyInjection 1.1.1

Replaced internal Typescanning with a ATypeScanner as of #24

Appeaser 2.3.0

#22 Adding netstandard 2.0 as according to recommendation.

Appeaser.Microsoft.DependencyInjection 1.1.0

#22 Adding support for configuration via IOptions (when using microsoft dependencyinjection). For an example of how you would use this, read this blog post

Appeaser.Microsoft.DependencyInjection 1.0.4

Fixed a bug causing multiple handlers of same type in the same class to not be registered correctly

Appeaser.Microsoft.DependencyInjection 1.0.0

First release of Appeaser.MicrosoftDependencyInjection which enables plugging into Asp.Net Core's dependency injection like this:

services.AddAppeaser();

... and can also be customized by providing config and/or extra assemblies to resolve handlers from (if no assemblies are provided, the calling assembly will be added by default).