Hi, I use llblgen to generate a "ORM" project(llblgen is v2.6 and use adapter), and refers to "WCF" project. Now I want to use entities in "Web" project through "WCF" project, in other words "Web" project will not assemble the ORM.dll. In "Web" project I could'n defind the entity of "ORM" I try to resorve it by adding [DataContract] attribute on entity class. but occur an error: "Type "ORM.EntityClasses.UserEntity' cannot be IXmlSerializable and have DataContractAttribute attribute."

Now I have two questions: 1. Is it right of my way? 2. If yes, how to deal with the error? 3. How to auto generate the [DataContract] and [DataMember] attributes on entity class. 4. If not right, please tell me the way to resorve it?

Thanks!

It's not clear to me what you have tried and what you haven't.

But in general you should start by checking our WCF project example published in the download section of our website.

There we used a windows client which communictas to a WCF service to get its entities. This shouldn't be any different than using a Web Client.

Please make sure you read the ReadMe.txt file.

Hi Walaa, The point is that I don't want to refer the ORM project in Web client.

For example:

In your WCF demo, you refer the "SD.LLBLGen.Pro.Examples.WCF" in "SD.LLBLGen.Pro.Examples.WCF.Client". This is the problem. I just want to refer the "SD.LLBLGen.Pro.Examples.WCF" in "SD.LLBLGen.Pro.Examples.WCF.Service". And then I can use entity and entity collection via Service, I want to keep a clean Web client. The client doesn't need to refer the "SD.LLBLGen.Pro.Examples.WCF".

Thank you.

Hi Walter,

I think that's no possible, as WCF service return EntityClasses, your client have to know about how to handle them, so it's necessary to reference the assembly.

If you want to do that, IMHO, you should use DTO's.

OK. But now if I want to add DataContract attribute to generated entity class, how to not occur the error.

You can't do this, as EntityClasses are not premitiveTypes or known types to the .NET Framework. So you can't decorate it with the dataContract attribute and expects the framework to re-cnstruct these entities at client side.

So in your situation I'd say you should use a DTO. Please search the forums for DTO, and you'll find some templates, and ones which are specific to WCF usage.

DataContract's are also too rigid in most cases, you should use a servicecontract as described in the example.