Dynamic Data is the smack bang answer to CRUDding, with UI being dynamically generated and could be twicked up to a point. It is definitely a replacement for Access like systems, but on the down side when finally things start getting more refined and defined it stops being the choice.
So if your friends legacy app is nothing more that massaging data in databases and will not need much more control than some elementary validation of input data then it is definitely the choice. But if they are looking at something for longterm that they will need to twick and control to the n'th degree, then http://www.asp.net/mvc or even http://www.asp.net/web-forms will be better suited. Of course they can leverage all 3 for different aspects, picking the underlying programming model depending on the specific needs of each part of the system. If they are not sure how far they are going to take their app, then yes Dynamic Data would get them started but as soon as they start receiving specicialised business rules, then they MUST bite the bullet and jump into MVC or WebForms ( MVC preferred ). Regards On 17 August 2011 08:24, Clint Colefax <[email protected]> wrote: > Hi All,**** > > ** ** > > A friend of mine is asking me questions about ASP.NET Dynamic Data**** > > ** ** > > http://www.asp.net/dynamicdata**** > > ** ** > > With me not being in the web UI space much, I’d never heard of it before. > Any opinions on it’s worth? He’s building a large enterprise system, that is > to replace his companies legacy system (they are about to go through a > massive growth spurt, and have recognized their current system, which they > inherited in a “buy out” situation, is just not going to cut it). I’m trying > to convince him to architect the system properly with a nice layed approach, > but this Dynamic Data seems to want to reference the entity framework > context directly, which to my understanding will make it impossible to put a > service layer in place, so use concepts like repository implementations, > etc, etc.**** > > ** ** > > To be it sounds like something he should pass over, but it’s shiny and new > to him, which has taken his attention, even tho all he seems to be able to > tell me is how it won’t work.**** > > ** ** > > Should he persist with this, or is there a better direction he should take > now.**** > > ** ** > > Any advice greatly appreciated.**** > > Thanks**** > > ** ** > > ** ** > > [image: Clint_C]**** > > ** ** >
<<image001.jpg>>
