Home/ Questions/Q 469313
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T23:46:12+00:00

I wanted to ask the SO community about this problem in my project. I

  • 0

I wanted to ask the SO community about this problem in my project. I have a Silverlight App Project in SL 3.0, which at the moment has a classic design with a business layer and a data layer in Linq2SQL. The problem is that the Data model can be in different version with some little changes in between.

I have 2 solutions but neither of them seemed good :

  1. Get rid of the Linq and put old stored procedures :

    • the good point if the data model changes i just have to change the stored procedures
    • the bad part is that my linq with dynamic filters would give me 30 stored procedures to change

  2. Build one data layer for each version

    • the good point is that the model stays clean with unit test for non regression
    • the bad part is that I have to develop for each new version of the model

Is there a good pattern to watch for data layer accessibility?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I would suggest option 2, but make sure that both implementations implement the same interface. Have the type of data layer be stored in a configuration file and loaded at runtime by a factory class.

    • 0