Corrected A.E.DynamicProxy - no longer supports TransparentProxy interception.

Author: tillig

docs/advanced/interceptors.rst

@@ -85,18 +85,7 @@ Under the covers, ``EnableInterfaceInterceptors()`` creates an interface proxy t
 Both techniques can be used in conjunction with the assembly scanning support, so you can configure batches of components using the same methods.
 
 **Special case: WCF proxy and remoting objects**
-While WCF proxy objects *look* like interfaces, the ``EnableInterfaceInterceptors()`` mechanism won't work because, behind the scenes, .NET is actually using a ``System.Runtime.Remoting.TransparentProxy`` object that behaves like the interface. If you want interception on a WCF proxy, you need to use the ``InterceptTransparentProxy()`` method.
-
-.. sourcecode:: csharp
-
-    var cb = new ContainerBuilder();
-    cb.RegisterType<TestServiceInterceptor>();
-    cb.Register(c => CreateChannelFactory()).SingleInstance();
-    cb
-      .Register(c => c.Resolve<ChannelFactory<ITestService>>().CreateChannel())
-      .InterceptTransparentProxy(typeof(IClientChannel))
-      .InterceptedBy(typeof(TestServiceInterceptor))
-      .UseWcfSafeRelease();
+While WCF proxy objects *look* like interfaces, the ``EnableInterfaceInterceptors()`` mechanism won't work because, behind the scenes, the .NET desktop framework is actually using a ``System.Runtime.Remoting.TransparentProxy`` object that behaves like the interface. As of v6.0.0 of ``Autofac.Extras.DynamicProxy`` the ability to intercept ``TransparentProxy`` objects was removed in an effort to improve cross-platform support.
 
 .. _associate_interceptors:
 
@@ -186,7 +175,7 @@ To enable proxying via interfaces, the component must provide its services throu
 WCF Proxies
 -----------
 
-As mentioned earlier, WCF proxies and other remoting types are special cases and can't use standard interface or class interception. You must use ``InterceptTransparentProxy()`` on those types.
+As mentioned earlier, WCF proxies and other remoting types are special cases and can't use standard interface or class interception.
 
 Class Interceptors and UsingConstructor
 ---------------------------------------
@@ -223,4 +212,4 @@ One, you can remove your direct Castle.Core reference. The transitive references
 
 Two, if you can't remove your direct reference or removing it doesn't work... all of the direct dependencies you have will need to update to version 4.2.0 or higher of Castle.Core. You'll have to file issues with those projects; it's not something Autofac can fix for you.
 
-`For reference, here's the Castle.Core issue discussing this challenge. <https://github.com/castleproject/Core/issues/288>`_
+`For reference, here's the Castle.Core issue discussing this challenge. <https://github.com/castleproject/Core/issues/288>`_