ASP.Net动态数据或MVC2？ [英] ASP.Net Dynamic Data or MVC2?
问题描述
我一直在使用web表单，我想根据一些事实和其他好东西，我看到它切换到MVC模式。当我遇到最新的动态数据（过去被称为动态数据模板）时，我正在使用MVC审核。
如果我错了，相信后端MVC2& DD使用MVC模式，但DD支持服务器端控制，并且使用其最新的脚手架技术具有很多自动化。我们可以在几个小时内创建一个运行的网站，DD为我们处理大部分的网站。
MS人们日子是大规模灵活和可配置的。但是，当我继续寻找在线资源，我感到失望（与MVC中提供的解决方案相比）asp.net论坛的最近一篇文章打击了我 -
Re：为什么我不再使用动态数据
- 请阅读这个Microsoft！
http://forums.asp.net /t/1604037.aspx?PageIndex=2ums.asp.net/t/1604037.aspx?PageIndex=2
看起来像一个非MS的家伙已经做了更多的DD然后实际的团队！
他的网站有一些复杂的解决方案 - http://csharpbits.notaclue.net/ p>
因此，MVC2& DD实际上是两个不同的东西还是他们有多相似？此外，我认为DD的一个主要问题是它在运行时生成一切 - 与MVC相比，这不会使它变慢，性能意识更差。
下面，我附加了一些我在
中完成的
屏幕Web表单（我需要能够插入
这样的功能我的网络应用程序）。对于
示例，网格级联，优化
分页，头过滤器，冻结
网格头，批量编辑等...网格头，批量编辑等...
请分享您的经验，看看DD是否成熟，有足够的文档和解决方案，或者MVC是否更好？
一些屏幕：
纠正我，如果我错了，但我相信后端两个MVC2& DD使用MVC
是的，这是错误的。 DD是泥球模式。
所以，MVC2& DD实际上是两个
不同的东西或者他们是如何相似的
他们？
请分享您的经验是否明智的等待DD成熟并有足够的文档和解决方案或MVC是否更好？
这是非常本地化到你和你的项目。如果他们解决了个人项目的需要，我将使用不成熟的项目，但在工作中我愿意等待稳定性。
I've been working with web-forms and I want to switch to the MVC pattern based on some facts and other goodies that I see in it. I was going good with MVC review when I came across the latest Dynamic Data (which in past was called Dynamic Data Templates).
Correct me if I'm wrong but I believe in backend both MVC2 & DD use the MVC pattern but then DD supports server-side controls and has a lot of automation using its latest scaffolding technique. We can make a running website with-in a few hours and DD handles most of it for us.
MS people day it is 'massively' flexible and configurable. However, as I went on looking for online resources I was disappointed (compared to the solutions available in MVC) a recent post from the asp.net forum hit me hard -
Re: Why I won't be using Dynamic Data any more - please read this Microsoft!
http://forums.asp.net/t/1604037.aspx?PageIndex=2ums.asp.net/t/1604037.aspx?PageIndex=2
And it looks like a non-MS guy has done more in DD then the actual team! His website has some complex solutions - http://csharpbits.notaclue.net/
So, are MVC2 & DD actually two different things or how similar are they? Besides, a major concern I thought about DD is that it generates everything at runtime - doesn't that make it slow and less performance conscious compared to MVC?
Below, I've attached some of my screens which I've accomplished in Web-forms (I need to be able to plug such features in my web-app). For example, Grid-cascading, optimized pagination, header-filters, frozen grid-header, bulk edit, etc...grid-header, bulk edit, etc...
Please share your experience whether its wise to wait until DD matures and has enough documentation and solutions or is MVC anytime better?
Some Screens:
Correct me if I'm wrong but I believe in backend both MVC2 & DD use the MVC
Yeah, thats wrong. DD is "ball of mud" pattern.
So, are MVC2 & DD actually two different things or how similar are they?
They are completely separate, do almost nothing the same and only share a common language and framework.
Please share your experience whether its wise to wait until DD matures and has enough >documentation and solutions or is MVC anytime better?
This is very localized to you and your project. I will use immature projects if they solve a need for personal projects but at work I'm willing to wait for stability.
这篇关于ASP.Net动态数据或MVC2？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
