blocks|key|2926406|text|好的，有很多方法可以回答这个问题，我相信其他许多人也会加入进来。我只想说，既然你的目标是改进和学习更多，而且你已经有2-3年的webform经验，这可能是一个学习MVC的好机会。然后，您将在这两个方面都有经验，并且可以对未来项目的最佳架构做出更明智的决策。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2926407|祝您学习愉快！|2926408|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Well, there are a number of ways to answer this question, and I'm sure many others will chime in. I'll just say that since your goal is to improve and learn more, and you already have 2-3 years of webform experience, this might be a good opportunity for you to learn MVC. Then you will have experience in both, and can make more informed decisions regarding the best architecture for future projects.

Happy learning!

blocks|key|610701|text|虽然没有人能确切地告诉你要做什么，但我管理的团队即将发布一个新的使用ASP+MVC的CMS+/+Job门户。MVC为我们提供了开箱即用的出色的可测试性和可扩展性，它可以快速地与nHibernate+/+windsor+(IOC)+/+nCache+/+jQuery等工具相结合-这确保您在internet上拥有丰富的资源，以帮助您加速开发和技能。您还可以采用诸如XHTML1.1Strict之类的标准，这对于ASP.Net+webforms来说几乎是不可能的，因为它是自动生成的|type|unstyled|depth|inlineStyleRanges|entityRanges|data|610702|1另一个优点是，您还可以摆脱可怕的ASP.Net视图状态。|610703|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Whilst nobody can tell you exactly what to do, the team I manage is about to release a new CMS / Job portal using ASP MVC. MVC gives us excellent testability and scalability out of the box and it can be quickly combined with tools such as nHibernate / windsor (IOC) / nCache / jQuery - this ensures that you have a wealth of resources on the internet to help accelerate your development and skill. You can also embrace standards such as XHTML 1.1 strict, which is almost impossible with ASP.Net webforms due to the auto generated HTML 

1 other advantage is that you also get away from the dreaded ASP.Net viewstate.

blocks|key|4393991|text|如果您想执行以下操作，请使用ASP.NET+MVC：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4393992|使用libraries|4393993|really或类似的语言学习web语言(HTML、CSS、JavaScript)|unordered-list-item|4393994|
|4393995|use+|4393996|4393997|+Driven+Development|4393998|4393999|have+a+clean+of+concerns|4394000|4394001|+jQuery+|offset|length|4394002|4394003|如果你没有时间或者意愿去学习正确使用MVC框架，那就坚持使用ASP.NET+WebForms。|4394004|entityMap|0|LINK|mutability|MUTABLE|url|http://jquery.com/^0|0|0|0|0|0|0|0|0|0|0|1|6|0|0|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|17|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|18|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|19|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|1A|8|@]|9|@]|A|$]]|$1|K|3|H|5|6|7|1B|8|@]|9|@]|A|$]]|$1|L|3|M|5|F|7|1C|8|@]|9|@]|A|$]]|$1|N|3|H|5|6|7|1D|8|@]|9|@]|A|$]]|$1|O|3|P|5|F|7|1E|8|@]|9|@]|A|$]]|$1|Q|3|H|5|6|7|1F|8|@]|9|@]|A|$]]|$1|R|3|S|5|F|7|1G|8|@]|9|@$T|1H|U|1I|1|1J]]|A|$]]|$1|V|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1L|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1M|8|@]|9|@]|A|$]]]|Z|$10|$5|11|12|13|A|$14|15]]]]

Use ASP.NET MVC if you want to:

<ul>
<li>learn the ASP.NET MVC framework</li>
<li>use <a href="http://jquery.com/" rel="nofollow noreferrer">jQuery</a> or similar libraries</li>
<li>really learn web-languages (HTML, CSS, JavaScript)</li>
<li>use Test Driven Development</li>
<li>have a clean separation of concerns</li>
</ul>

If you don't have the time or will to learn to use the ASP.NET MVC framework correctly, stick with ASP.NET WebForms.

blocks|key|4394219|text|我的答案几乎总是"ASP.NET+MVC“。灵活性和特性的数量以及可测试性和可维护性以及...远远超过了WebForms。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4394220|WebForms具有现有控件和文档的丰富生态系统的优势，并且对于某些类型的任务(复杂的、多形式的交互)来说非常强大，但我发现它的局限性经常会阻碍我的工作。你必须塑造自己去适应它。|4394221|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

My answer is almost always "ASP.NET MVC." The amount of flexibility and features and testability and maintainabilty and ... heavily outweigh WebForms.

WebForms has the advantages of a rich ecosystem of existing controls and documentation, and is really powerful for some kinds of tasks (complex, multi-form interactions), but I find its limitations get in the way far too often. You have to mold yourself to it.

blocks|key|4394035|text|这实际上取决于应用程序的最终目标是什么。正如Scott+Ewers所说，如果你的目标是学习，那么使用web将扩展你在ASP.NET空间的知识广度(因为你已经了解ASP.NET表单)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4394036|此外，如果这将是一个公共产品，您可以利用MVC的可测试性优势并运行自动化的单元测试。像关注点分离这样的关键思想也可以提高长期可伸缩性和可维护性。|4394037|您可能选择web表单的主要原因是，如果您正在快速构建工作公告板应用程序的原型。正如您所知道的，web表单允许您将组件拖放到画布上，以快速创建一些基本的数据输入功能。|4394038|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

It really depends on what the end goal of the application is. As Scott Ewers said, if your goal is to learn, then using ASP.NET MVC will expand your breadth of knowledge in the ASP.NET space (since you already know web forms).

Additionally, if this is going to be a public product, you can leverage the testability benefits of MVC and run automated unit tests. Key ideas like Separation of Concerns can also increase long-term scalability and maintainability.

The primary reason why you might choose web forms is if you are rapidly prototyping the job board application. As you know, web forms allows you to drag-and-drop components onto the canvas to quickly create some basic data entry functionality.

blocks|key|4394053|text|5月13日有一个关于这个主题的herding+code+podcast。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4394054|4394055|群组代码47:+Joe+Brinkman+on+Webforms+vs+ASP.NET+MVC。|blockquote|4394056|4394057|entityMap|0|LINK|mutability|MUTABLE|url|http://herdingcode.com/?p=183^0|F|K|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]|$1|E|3|F|5|G|7|V|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|W|8|@]|9|@]|C|$]]|$1|I|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

There is a <a href="http://herdingcode.com/?p=183" rel="nofollow noreferrer">herding code podcast</a> from May 13 on the subject.

<blockquote>
 Herding Code 47: Joe Brinkman on Webforms vs ASP.NET MVC.
</blockquote>

blocks|key|4394087|text|我也同意选择MVC的好处是可以让你扩展你的知识。这不是唯一的原因，如果我也可以选择的话，我刚刚完成了一个小的MVC项目(我的第一个)，让我告诉你MVC很棒！这是一个很棒的框架，我觉得它给了你更多的灵活性，同时还提供了开箱即用的工具来快速、轻松地创建web应用程序。这是我第一次使用VS2008+&+.NET+FW3.5&+LINQ，www.asp.net上的所有指南都帮助我快速前进(特别是一本提到here的MVC1.0书中的免费教程章节)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4394088|在此过程中，我也学到了JQuery，因为它与这些新技术有很大的集成。|4394089|但需要注意的是，这是一项新技术，版本2已经在酝酿之中，所以如果你的项目是长期的，请牢记这一点并制定相应的计划(对于我来说，作为一个小项目，我可能会在正式发布时尝试将我的项目升级到版本2)。然而，同时，拥有一个完全支持MS+(以及MSDN)的版本1对我来说是天赐之物……|4394090|祝好运!|4394091|entityMap|0|LINK|mutability|MUTABLE|url|http://weblogs.asp.net/scottgu/archive/2009/03/10/free-asp-net-mvc-ebook-tutorial.aspx^0|5J|4|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]]]

I also agree that choosing MVC would have the advantage of allowing you to expand your knowledge. That not being the only reason, given the choice as well I just finished a small MVC project (my first) and let me tell you MVC rocks! Its a great framework which I feel gives you more flexibility and at the same time out-of-the-box tools to create a web app quickly and painlessly. It was my first experience with VS2008 &amp; .NET FW 3.5 &amp; LINQ, and all the guides at www.asp.net helped me go forward quickly (especially the free tutorial chapter from an MVC 1.0 book mentioned <a href="http://weblogs.asp.net/scottgu/archive/2009/03/10/free-asp-net-mvc-ebook-tutorial.aspx" rel="nofollow noreferrer">here</a>).

I also got to learn JQuery along the way, as it is very much integrated into these new technologies.

One think to take note though is that this being a new tech, version 2 is already being cooked up, so if your project is for the long run, have that in mind and plan accordingly (in my case, being a small project, I'll probably try upgrading my project to version 2 when its officially released). Yet at the same time, having a fully MS (and thus MSDN) supported version 1 was a godsend for me... 

Good luck!

blocks|key|900008|text|我在Jquery，CSS，HTML，Javascript方面有很好的经验，但在TDD方面没有。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|900009|我让time..and愿意学习MVC，但不确定MVC是不是工作门户或类似网站的好选择。|900010|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I have good experience in Jquery, CSS, HTML, Javascript but not in TDD.

I have time..and willing to learn MVC but wasn't sure MVC is good choice for Job portal or similar site..

blocks|key|4394156|text|这可以被认为是一种无耻的自我宣传，但这是我关于如何在两者之间做出选择的小测验：http://sietch.net/ViewNewsItem.aspx?NewsItemID=101|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4394157|entityMap|0|LINK|mutability|MUTABLE|url|http://sietch.net/ViewNewsItem.aspx?NewsItemID=101^0|13|1E|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

This can be considered a shameless self-advertisement but here is my quiz on how to choose between the two:
<a href="http://sietch.net/ViewNewsItem.aspx?NewsItemID=101" rel="nofollow noreferrer">http://sietch.net/ViewNewsItem.aspx?NewsItemID=101</a>

blocks|key|4394304|text|最近，我的一个客户让我写一篇论文，或者简单地写一份清单，以帮助其他主要开发人员做出同样的决定。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4394305|我在我的博客上发布了前两个初稿。我诚然是支持mvc的，但我们已经收到了论文/清单，所以它可能会有所帮助。|4394306|http://eric.polerecky.com/archives/a-somewhat-less-biases-comparison-of-mvp-and-mvc/[http://eric.polerecky.com/archives/a-somewhat-less-biases-comparison-of-mvp-and-mvc/][1]|offset|length|4394307|我认为MVC最常被忽视的好处是约定；我真的在webforms项目中看到了任何约定，虽然在MVC项目中没有严格执行，但至少在那里是这样的。|4394308|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|4T|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@$F|T|G|U|1|V]]|A|$]]|$1|H|3|I|5|6|7|W|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|E]]]]

I was recently tasked by one of my clients to write a paper, or simply a checklist, that would help other lead developers make this same decision.

I posted the first 2 rough drafts on my blog. I am admittedly pro-mvc but the paper/checklist has been we received so it might be helpful.

<a href="http://eric.polerecky.com/archives/a-somewhat-less-biases-comparison-of-mvp-and-mvc/[http://eric.polerecky.com/archives/a-somewhat-less-biases-comparison-of-mvp-and-mvc/][1]" rel="nofollow noreferrer">http://eric.polerecky.com/archives/a-somewhat-less-biases-comparison-of-mvp-and-mvc/[http://eric.polerecky.com/archives/a-somewhat-less-biases-comparison-of-mvp-and-mvc/][1]</a>

I think the most often overlooked benefit of MVC is convention; I really see any convention in webforms projects and while not strictly enforced in MVC projects at least its there.

blocks|key|610748|text|我开始在webforms中开发我们当前的应用程序，mvc在开发开始时是不可用的。我选择了MVP模式，使用URL重写HTTP模块。目前，我正在研究在其中插入一些MVC，基本上是使用前端控制器而不是页面控制器。已经建立的MVP架构中的其他东西，在我的应用程序中，与没有WebForms的纯MVC方法相比，给了我更多的灵活性，我喜欢，尽管需要比MVC示例更多的代码(我从来没有在真实的项目中尝试过，看看它是否保持原样，就像在截屏视频中的那些示例一样)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|610749|我对MVC不喜欢的是在模板中混合控件代码--我认为循环、is之类的东西不应该出现在模板中。但几天前，我遇到了Spark+view+engine，它在这一领域看起来很有前途，尽管还没有接近java世界中的Tapestry5(一种基于组件的webGUI框架)。|610750|但是上面提到的将两者混合在一起的建议可能会对你探索MVC世界起作用，并且如果某些东西对你来说不起作用，你可能会有安全的退路。|610751|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

i started developing our current app in webforms, mvc wasn't available when development started.. i've chosen the MVP pattern, with URL rewrite HTTP module. currently i'm investigating plugging in some MVC into this, basically to use the front-controller instead of using page-controllers. the other things in already established MVP architecture with web forms in my app give me more flexibility than pure MVC approach without WebForms, which i like, although require a bit more code than MS MVC examples (never tried it for real project to see if it stays that way, like in those examples in screencasts).

what i don't like with MVC is mixing control code inside templates - i believe loops, ifs and stuff like that just shouldn't belong inside the template. but a couple days ago i've ran into Spark view engine that looks kind of promising in that segment, although not still close to the Tapestry 5 (a component-based webGUI framework) in the java world.

But the above mention suggestion to mix both might work for you to explore MVC world and have the safe ground to fallback to if something won't work for you might be ok for you.

I'm developing a website , job portal. I have 2-3 years of ASP.NET webform development experience, 
I want to create a professional job portal site (to improve and learn more) but trying to decide on best architecture. Any suggestions or advice will help...

Thanks

MVC or Webform Architecture for new site

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我正在开发一个网站，求职门户。我有2-3年的ASP.NET webform开发经验，我想创建一个专业的就业门户网站(以提高和学习更多)，但试图决定最好的架构。任何建议或建议都会有所帮助。谢谢

问用于新站点的MVC或Webform架构
EN

回答 11

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问用于新站点的MVC或Webform架构EN

回答 11

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问用于新站点的MVC或Webform架构
EN