WCF Integration facility enables integration with Windows Communication Foundation. It makes services and WCF proxies available as services in your application, lets you use non-default constructor and inject dependencies into your services, adds ability to easily set up your services with extensions, call services asynchronously without needing to use code generation and much more.
WCF Integration Facility lives in Castle.Facilities.WcfIntegration.dll file distributed as part of Windsor binary package.
If you're using Nuget, you'll have to download it separately using the following command:
Install-Package Castle.WcfIntegrationFacility
After adding reference to the facility, You can add it to the container:
using Castle.Facilities.WcfIntegration;
Container.AddFacility<WcfFacility>();Some of the functionality exposed by the facility on the client side of WCF application.
ℹ️ Notice that the documentation is still being created and the list is incomplete.
- Windsor replaces standard WCF client side remoting proxy with its own Dynamic Proxy. This lets you add interceptors to it like to any other Windsor component.
- Ability to perform asynchronous calls without need to code-generate client-side proxy
- Transparently recycle the channel when it gets closed/faulted
Some of the functionality exposed by the facility on the service side of WCF application.
Some of the functionality exposed by the facility on both - client and service side of WCF application.