I watched this webcast recently, and I got the sense that a lot of the "cool stuff" from ASP.NET MVC is getting pulled back into the ASP.NET framework.
我最近看了这个网络直播，我感觉很多来自ASP的“很酷的东西”。NET MVC正在被拉回到ASP中。净框架。
At the moment I'm setting the ground-work for a project at my company using ASP.NET MVC, but after watching this, I'm beginning to wonder if that's the right choice, and whether it would behoove me to wait for ASP.NET 4.0.
目前，我正在为我的公司使用ASP的一个项目设置基础工作。NET MVC，但是看了这个之后，我开始怀疑这是否是正确的选择，我是否应该等待ASP。NET 4.0。
I realize ASP.NET MVC 2.0 is getting close to an actual release.
我意识到ASP。NET MVC 2.0正在接近实际的发行版。
If High-Testability, loose coupling, and having Full control of our HTML are top priorities, which should I choose, ASP.NET 4.0 or ASP.NET MVC?
如果高可测试性、松耦合和完全控制HTML是最重要的，我应该选择ASP。NET 4.0或ASP。净MVC吗?
5 个解决方案
#1
23
Well your question doesn't really make sense to me.
你的问题对我来说没什么意义。
You're asking whether or not to go with ASP.Net MVC or ASP.Net 4.0 - do you mean WebForms?
你在问是否要使用ASP。净MVC或ASP。Net 4.0 -你是指WebForms吗?
MVC 2.0 will be shipped in the box with VS 2010 and as such same time as .Net 4.0 AND ASP.Net 4.0 - also ASP.Net MVC is a part of ASP.Net.
MVC 2.0将会在vs2010的盒子里，与。net 4.0和ASP同时发布。Net 4.0 -也是ASP。Net MVC是ASP.Net的一部分。
If you wish to use the .Net 4.0 runtime and all the features of ASP.Net 4.0 - what's wrong with doing it WITH MVC?
如果您希望使用。net 4.0运行时和ASP的所有特性。Net 4.0 -用MVC做有什么问题?
Also, I'd suggest building onto the MVC 1.0 now and structure your app in a such way that you can easily migrate to and embrace the new features in MVC 2.0 as you already know how most of these will work that shouldn't be too much of an issue. Or if your release is after the release of ASP.Net MVC 2.0, simply start using it now - unless that poses other issues.
另外，我建议您现在就构建MVC 1.0，并以一种您可以轻松迁移到MVC 2.0中的新特性的方式来构建您的应用程序，因为您已经知道这些新特性将如何工作，这应该不是什么大问题。或者你的发布是在ASP发布之后。Net MVC 2.0，现在就开始使用它——除非这会带来其他问题。
#2
7
If your application will be released after the March release date, then it's a no brainier. Go with ASP.Net 4.0.
如果你的应用程序在3月发布日期之后发布，那么它就不是一个聪明的人了。ASP。Net 4.0。
If it's not, then it not quite as clear. My current company is facing the same issue. Do we go with .Net 4.0 or not. For us, our solution is hosted internally, so we don't have the problem of releasing a product on a unreleased platform. Our biggest concern is the changes from beta2 to RTM.
如果不是，那就没那么清楚了。我现在的公司也面临着同样的问题。我们要不要用。net 4.0呢?对于我们来说，我们的解决方案是在内部托管的，所以我们没有在未发布的平台上发布产品的问题。我们最关心的是从beta2到RTM的变化。
As a developer I'm always wanting to move to the newest platform. A company has to consider it's clients and the risk to move to a new platform. Most of the time caution is more prudent then being the first to jump.
作为一名开发人员，我一直都想搬到最新的平台。一个公司必须考虑到它的客户和转移到一个新平台的风险。大多数时候，谨慎要比第一个跳下去更谨慎。
ASP.MVC 1.0 is supported and released. It's a great web framework. If you are not looking for specific features in ASP.MVC 2. Then use ASP.NET MVC 1.
ASP。支持并发布了MVC 1.0。这是一个很棒的web框架。如果您没有在ASP中寻找特定的特性。MVC 2。然后使用ASP。净MVC 1。
#3
6
If your criteria include this:
如果你的标准包括以下内容:
We are aiming for high testability, loose coupling, and "controlled HTML" -- to me that meant ASP.NET MVC.
我们的目标是高可测试性、松散耦合和“受控HTML”——对我来说，这意味着ASP。净MVC。
Then ASP.NET MVC is a must. Even with ASP.NET 4.0, you can't get around the fact that ASP.NET is hard to test for without a lot of extra leg work that just isn't there for MVC.
然后ASP。NET MVC是必须的。即使ASP。NET 4.0，你无法回避ASP这个事实。NET很难进行测试，因为它没有太多MVC所没有的额外工作。
I use ASP.NET in my 'day job', but at night time I'm ASP.NET MVC all the way. ASP.NET 4.0 still hangs on to the legacy "Code-Behind" and the View/Controller coupling that goes on with ASP.NET Controls. These are things that make it much harder to test, and are 'tightly coupled' by definition.
我使用ASP。在我的“白天工作”，但在晚上我是ASP。NET MVC。ASP。NET 4.0仍然依赖于遗留的“代码隐藏”和与ASP进行的视图/控制器耦合。网络控制。这些东西使测试变得更加困难，并且根据定义它们是“紧密结合”的。
#4
3
Go with whichever makes the most business sense. We always feel like waiting for the next best thing...but if we did we'd never get anything accomplished.
选择最具商业价值的。我们总想等待下一个最好的东西……但如果我们这样做了，我们就永远不会有任何成就。
#5
1
Choosing a presentation pattern for a new or enterprise web development on the Microsoft platform is a daunting task, in my opinion there are only three; View Model, Model-View-Presenter (MVP) or ASP.NET MVC (a Model2 derivative).
在Microsoft平台上为新的或企业web开发选择表示模式是一项艰巨的任务，在我看来只有三个;查看模型，模型-视图-演示者(MVP)或ASP。NET MVC(一个Model2衍生版本)。
You can read the full article here ASP.NET MVC Patterns
你可以在这里阅读全文ASP。净MVC模式
#1
23
Well your question doesn't really make sense to me.
你的问题对我来说没什么意义。
You're asking whether or not to go with ASP.Net MVC or ASP.Net 4.0 - do you mean WebForms?
你在问是否要使用ASP。净MVC或ASP。Net 4.0 -你是指WebForms吗?
MVC 2.0 will be shipped in the box with VS 2010 and as such same time as .Net 4.0 AND ASP.Net 4.0 - also ASP.Net MVC is a part of ASP.Net.
MVC 2.0将会在vs2010的盒子里，与。net 4.0和ASP同时发布。Net 4.0 -也是ASP。Net MVC是ASP.Net的一部分。
If you wish to use the .Net 4.0 runtime and all the features of ASP.Net 4.0 - what's wrong with doing it WITH MVC?
如果您希望使用。net 4.0运行时和ASP的所有特性。Net 4.0 -用MVC做有什么问题?
Also, I'd suggest building onto the MVC 1.0 now and structure your app in a such way that you can easily migrate to and embrace the new features in MVC 2.0 as you already know how most of these will work that shouldn't be too much of an issue. Or if your release is after the release of ASP.Net MVC 2.0, simply start using it now - unless that poses other issues.
另外，我建议您现在就构建MVC 1.0，并以一种您可以轻松迁移到MVC 2.0中的新特性的方式来构建您的应用程序，因为您已经知道这些新特性将如何工作，这应该不是什么大问题。或者你的发布是在ASP发布之后。Net MVC 2.0，现在就开始使用它——除非这会带来其他问题。
#2
7
If your application will be released after the March release date, then it's a no brainier. Go with ASP.Net 4.0.
如果你的应用程序在3月发布日期之后发布，那么它就不是一个聪明的人了。ASP。Net 4.0。
If it's not, then it not quite as clear. My current company is facing the same issue. Do we go with .Net 4.0 or not. For us, our solution is hosted internally, so we don't have the problem of releasing a product on a unreleased platform. Our biggest concern is the changes from beta2 to RTM.
如果不是，那就没那么清楚了。我现在的公司也面临着同样的问题。我们要不要用。net 4.0呢?对于我们来说，我们的解决方案是在内部托管的，所以我们没有在未发布的平台上发布产品的问题。我们最关心的是从beta2到RTM的变化。
As a developer I'm always wanting to move to the newest platform. A company has to consider it's clients and the risk to move to a new platform. Most of the time caution is more prudent then being the first to jump.
作为一名开发人员，我一直都想搬到最新的平台。一个公司必须考虑到它的客户和转移到一个新平台的风险。大多数时候，谨慎要比第一个跳下去更谨慎。
ASP.MVC 1.0 is supported and released. It's a great web framework. If you are not looking for specific features in ASP.MVC 2. Then use ASP.NET MVC 1.
ASP。支持并发布了MVC 1.0。这是一个很棒的web框架。如果您没有在ASP中寻找特定的特性。MVC 2。然后使用ASP。净MVC 1。
#3
6
If your criteria include this:
如果你的标准包括以下内容:
We are aiming for high testability, loose coupling, and "controlled HTML" -- to me that meant ASP.NET MVC.
我们的目标是高可测试性、松散耦合和“受控HTML”——对我来说，这意味着ASP。净MVC。
Then ASP.NET MVC is a must. Even with ASP.NET 4.0, you can't get around the fact that ASP.NET is hard to test for without a lot of extra leg work that just isn't there for MVC.
然后ASP。NET MVC是必须的。即使ASP。NET 4.0，你无法回避ASP这个事实。NET很难进行测试，因为它没有太多MVC所没有的额外工作。
I use ASP.NET in my 'day job', but at night time I'm ASP.NET MVC all the way. ASP.NET 4.0 still hangs on to the legacy "Code-Behind" and the View/Controller coupling that goes on with ASP.NET Controls. These are things that make it much harder to test, and are 'tightly coupled' by definition.
我使用ASP。在我的“白天工作”，但在晚上我是ASP。NET MVC。ASP。NET 4.0仍然依赖于遗留的“代码隐藏”和与ASP进行的视图/控制器耦合。网络控制。这些东西使测试变得更加困难，并且根据定义它们是“紧密结合”的。
#4
3
Go with whichever makes the most business sense. We always feel like waiting for the next best thing...but if we did we'd never get anything accomplished.
选择最具商业价值的。我们总想等待下一个最好的东西……但如果我们这样做了，我们就永远不会有任何成就。
#5
1
Choosing a presentation pattern for a new or enterprise web development on the Microsoft platform is a daunting task, in my opinion there are only three; View Model, Model-View-Presenter (MVP) or ASP.NET MVC (a Model2 derivative).
在Microsoft平台上为新的或企业web开发选择表示模式是一项艰巨的任务，在我看来只有三个;查看模型，模型-视图-演示者(MVP)或ASP。NET MVC(一个Model2衍生版本)。
You can read the full article here ASP.NET MVC Patterns
你可以在这里阅读全文ASP。净MVC模式