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 created a modular application where each module only communicates through the other one with strong interfaces. Recently I found that we failed to separate the modules completely because there is a shared set of objects underneath that each of the modules access.
What is the best way to separate this layer out? The data objects represents that that is displayed on the screen for a new record.
Looks like I’m in a same boat as you. If you have ORM(EF for example) and some kind of business object framework (RIA Services, DevForce) than you pretty much “locked” into having 1 assembly on each end (client/server)
If you want to go ahead and break this down I think it will cause more problems then it’s worth. You will have issues joining entities from different modules, you will have repeating entities in different data modules, etc. If you already have ORM layer broken down – then by all means keep it same on client.
I would create just one data project (it’s not even module in Prism) and reference it from all modules. In my case I reference it from main project and set “CopyLocal=true” just so MEF knows about those entities and I reference it from other modules and set “CopyLocal=false”.