Type Reuse problem in WCF
-
Hi everyone, I have some very strange problem! I have my own WSHttpBinding-based webservice and it worked always fine. Furhtermore I have a client consuming it; since I have created some special classes I used "reuse types" there, so my referenced assembly and the original classes can be used within the original namespaces. So far so good! Since I always only updated the service reference I missed the point where my service got problems with reusing types. :( Whenever I add the service to a new client, code generation fails when I mark "reuse types"! My old client breaks if I re-configer it. As long as I only update it, it's ok, but that's certainly no solution, because there seems to be some problem with my service! Any hints for me where to search for the problem? Best regards, Roland
-
Hi everyone, I have some very strange problem! I have my own WSHttpBinding-based webservice and it worked always fine. Furhtermore I have a client consuming it; since I have created some special classes I used "reuse types" there, so my referenced assembly and the original classes can be used within the original namespaces. So far so good! Since I always only updated the service reference I missed the point where my service got problems with reusing types. :( Whenever I add the service to a new client, code generation fails when I mark "reuse types"! My old client breaks if I re-configer it. As long as I only update it, it's ok, but that's certainly no solution, because there seems to be some problem with my service! Any hints for me where to search for the problem? Best regards, Roland
I battled with this for a while myself. Basically, Some object in your domain object dll itself references something that isn't directly available to the client. When this scenario happens proxy objects are generated for everything not just the object that the client doesn't have a static reference to ... Make sense?
Jammer My Blog | Article(s)