Author: ncage | Posted on: 7/6/2008 6:46:24 PM | Views : 968

Hi everyone how is it going? What is best practices to pass data between tiers and still keep things loosly coupled. I also want something that will serialize across service boundaries. I have pondered this question for awhile and here are some things ive came up with:1) Linq To SQL / Entity Framework is too hard at this point to be effective in a N-Tiered architecture. To keep everything working smoothly you either have to tightly couple everything or write a lot of code to get around the fact that your going to be disconnecting from the datacontext. I will wait for version 2 :).2) You can pass around Data Entities (POCO Objects). You essentially create an array of poco objects and pass that between tiers. I liked this approach.3) Dataset - Two types of datasets were under consideration...typed and untyped. I didn't like the untyped approach but thought the typed approach was maybe an option. Go to the complete details ...