for years, dynamic data linq2sql served cool , easy tool create administration projects it's getting more , more problematic maintain these projects after 5 years, because asp addons lifecycle perspective it's deadend.
does faced similar decision, move next?
i fell trap @ previous job lot of projects "quick , dirty" , became mainline applications. suggestion describe problem management , when next change comes down line, allocate time translate of core orm entity framework.
since have db in place, can use edmx files, use generated classes model, or create 1 on top.
be sure explain management putting in time create better core pay dividends later on maintenance become easier, since no longer working around dynamic data's shortcomings.
Comments
Post a Comment