Releases: autofac/Autofac.Wcf
Releases · autofac/Autofac.Wcf
Release list
v8.0.0
Breaking Changes
- Minimum framework requirement is now .NET Framework 4.8.1. The target framework was raised from
net472tonet481; consumers on earlier framework versions must upgrade. - Updated the Autofac dependency from 8.0.0 to 9.3.1. This is a major-version bump of the core dependency and may require consumers to update their own Autofac reference.
Other Changes
- Fixed singleton hosting of intercepted WCF services (#31). Registering a service as
SingleInstance()together with interception (EnableInterfaceInterceptors) previously crashed at host construction because WCF rejected the Castle proxy type. The resolved singleton is now wrapped in aDispatchProxyso WCF can host it while interception continues to run. Clean, non-proxied instances are still hosted directly. - Added a dependency on
System.Reflection.DispatchProxy4.8.1 (BCL only; no Castle dependency is introduced into the core package).
v7.0.0
v6.1.0
What's Changed
- #28: Missing service registrations will now throw
InvalidOperationExceptioninstead ofNullReferenceException. (Thanks @JarkoDubbeldam! #29) - Package now includes README and symbols are published in .snupkg format to NuGet.
Full Changelog: v6.0.0...v6.1.0
v6.0.0
This is a compatibility release for Autofac 6.0
Breaking change: Starting with Autofac 6.0, we now only target netstandard2.0 and netstandard2.1; we have removed the explicit target for net461.
This package therefore now targets net472, instead of net461.
v5.0.0
This release is an update for compatibility with Autofac 5.0.0 and requires that new version. Autofac 5.0.0 does have some breaking changes - see the Autofac release notes for more information.
- Minimum .NET Framework updated to .NET 4.6.1
- Support for registering modules that will be added on a per-instance-context basis.