WCF problem with custom types

Question

I have created two projects in the same solution. The first project has a class, lets call it "class A". The second project is a WCF service library. That WCF service is referencing a project from that same solution so it can use type "A" defined in the first solution.

Now, the problem is that when I reference that wcf service from the first project (normal C# project), in the object browser I see wcf service methods that have to return type "A", are returning just an "object" type! If I define a custom class as part of WCF project, it is recognized as return type.

How can I make project 1 (that defined type "A") use the WCF project and recognize his own types?

Your mixing up the words Solution and Project. You'll have to be more precise in this question. And describe the setup a little better too. Are the Types (assembly) shared between Client and Server? — Henk Holterman
– Henk Holterman, Commented Jul 4, 2011 at 18:12
One solution contains two projects - client app (client project) and server app (wcf project). WCF project has to use types defined in client project (part of same solution) and it's ok, but when those types have to be offered to client app (in the same solution, that defines types used bu wcf) those types are recognized as "object". Don't know how to describe it any better :) — guest86
– guest86, Commented Jul 4, 2011 at 18:16
Client app defines types exposed by the service? That smells. — Ladislav Mrnka
– Ladislav Mrnka, Commented Jul 4, 2011 at 18:31

Henk Holterman · Accepted Answer · 2011-07-04 18:29:17Z

1

You will probably have to mark your DataContracts with [KnownType].

And it is a (very) good idea to isolate those shared types in a separate assembly (Project).

answered Jul 4, 2011 at 18:29

Henk Holterman

276k33 gold badges353 silver badges540 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Sebastian Piu · Accepted Answer · 2011-07-05 10:41:22Z

0

If you are the only consumer of your services and is a .net application then it might be worth using the NetDataContractSerailizer this way you can pass shared type information and you don't need to mark your objects with [KnownType]

see here for better explanation http://www.pluralsight-training.net/community/blogs/aaron/archive/2006/04/21/22284.aspx

hth

answered Jul 5, 2011 at 10:41

Sebastian Piu

8,0581 gold badge35 silver badges51 bronze badges

1 Comment

guest86 Over a year ago

Problem with my code was that i was trying to communicate with WCF using interfaces (whole project 1 is using interfaces as function argument types and return types). Right now, i realized i can't use interfaces that way, but when when i use class from project 1 to communicate with wcf that class (in object browser) is described as "WCFProject class", not as class belonging to "Project1"!

Collectives™ on Stack Overflow

WCF problem with custom types

2 Answers 2

Comments

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related