tag:blogger.com,1999:blog-891889700878195825.post9220414909596258307..comments2023-10-20T10:02:27.498+02:00Comments on Piotr Włodek's Tech Blog: Introduction to InterceptingCatalog – Part IPiotr Włodekhttp://www.blogger.com/profile/16128908255082039702noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-891889700878195825.post-15617366137672580792011-09-15T09:49:02.026+02:002011-09-15T09:49:02.026+02:00Hi. First thanks for very nice article. I have one...Hi. First thanks for very nice article. I have one question when i try to move your demo to asp.net mvc app i got an error:<br />"Cannot cast the underlying exported value of type 'MefContrib.Samples.Interception.Foo (ContractName="MefContrib.Samples.Interception.Foo")' to type 'MefContrib.Samples.Interception.Foo'."<br />I dont now why but its work at simple app and dont work at asp.net mvc app (sanja.melnichuckhttps://www.blogger.com/profile/14291684656068352073noreply@blogger.comtag:blogger.com,1999:blog-891889700878195825.post-45820295350355573272011-02-18T12:15:46.633+01:002011-02-18T12:15:46.633+01:00Hi, thank you for the InterceptingCatalog!
I hav...Hi, thank you for the InterceptingCatalog! <br /><br />I have made a small addition to it so that you can use Unity as a proxy so that EntLib's PIAB attributes/interceptors work with MEF just like it was Unity. <br />You can check it here: http://baud.cz/blog/unity-entlib-interceptors-in-mef and if possible, add it to MEFContrib.giushttps://www.blogger.com/profile/13115797130046454621noreply@blogger.comtag:blogger.com,1999:blog-891889700878195825.post-28246925264745815362010-12-18T14:09:16.535+01:002010-12-18T14:09:16.535+01:00You would have to implement your own Castle Dynami...You would have to implement your own Castle DynamicProxy interceptor which supports class interception. The one shipped with MefContrib is suitable for interface interception only.<br /><br />PiotrPiotr Włodekhttps://www.blogger.com/profile/16128908255082039702noreply@blogger.comtag:blogger.com,1999:blog-891889700878195825.post-44999269249865574592010-12-01T03:20:40.682+01:002010-12-01T03:20:40.682+01:00If you export Foo instead of IFoo, you will get an...If you export Foo instead of IFoo, you will get an "unable to cast" error.<br /><br />As with nearly all MEF error messages, this one is unhelpful...<br /><br />"Cannot cast the underlying exported value of type 'MefContrib.Samples.Interception.Foo (ContractName="MefContrib.Samples.Interception.Foo")' to type 'MefContrib.Samples.Interception.Foo'."Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-891889700878195825.post-89611595592561591142010-11-17T20:49:04.734+01:002010-11-17T20:49:04.734+01:00Many thanks. It's just this sort of explanatio...Many thanks. It's just this sort of explanation that is lacking in MefContrib. Would love to see more of them!Anonymousnoreply@blogger.com