Hi,
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 :
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
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?
Thanks and sorry for my poor English