Krzysztof, Fabian It looks like the problem is when creating interfaces proxies while specifying additional interfaces that include generic methods. I created a unit test to demonstrate the problem. It is checked in on DP2 trunk with the Ignore attribute.
http://svn.castleproject.org:8080/svn/castle/trunk/Tools/Castle.DynamicProxy2/Castle.DynamicProxy.Tests/GenericMethodsProxyTestCase.cs I am currently trying to resolve this defect in the WCF integration facility http://support.castleproject.org/projects/DYNPROXY/issues/view/DYNPROXY-ISSUE-80 Thanks for your help, Craig I also have defects when creating class proxies that call self generic methods. This is happening when using MS MVC Controllers that have generic methods, but that is something totally different and I'll create more broken tests for that too. On Sat, Jan 10, 2009 at 2:33 AM, Fabian Schmied <[email protected]>wrote: > > > Does anyone have any idea the extent of change to DP2 to support proxying > > generic methods? Got a few defects from that. > > This is actually implemented. There are, however, a few bugs in the > .NET 2.0 CLR (before SP2, at least), which make this really hard to > get right. There are a few workarounds in there (eg. tokens of generic > methods aren't cached, there is this ominous > IInvocation.GetConcreteMethod API, etx), but in principle, it should > work. > > What exactly are the defects you have? > > Fabian > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
