I have a Silverlight Project which passes data using the Data Contract to a WCF service. The WCF method then invokes a BAL class which again has the same properties. Is there any way to avoid this duplication of properties ?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a Silverlight Project which passes data using the Data Contract to a WCF service. The WCF method then invokes a BAL class which again has the same properties. Is there any way to avoid this duplication of properties ?
Chak,
Depending on your situation this might work for you. You can share items between projects in Visual Studio. When adding a new item (C# class in your case), simply add the item as a linked item. By doing this, the class will only exist in one location. I wrote a blog post about this a couple months ago.
I hope this helps!
http://www.pagebrooks.com/archive/2008/10/11/sharing-code-between-.net-and-silverlight-platforms.aspx