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.
Hello and Happy New Year all! While thinking about new project I decided to build my business layer as separate WCF services, that will be consumed by various clients. Data access is also handled by services. The first consumer is an ASP.NET MVC website and other clients will be created only in about a year or two. The question is do I really need WCF layer or it will be easy to rewrite this to only MVC and throw WCF away? Or keep things as is?
Even if you build an MVC application or a desktop one, you will always need a Data Access Layer or Business Layer (Which ever name you choose for your Data Handling Objects).
I would suggest you to create a separate Project Which handles the task for data maniplulations.
And then Expose it via WCF Service and utlize it with any application whether web or desktop via different end points.