对于每一个或中继器-哪个更好?

I'm building a website in ASP.Net, using MVC, and need to list a set of results. Both of the following work as I want them to but I'm wondering which is faster, cleaner and/or better - or if another option entirely would be more appropriate?

我正在用ASP建立一个网站。Net，使用MVC，需要列出一组结果。以下两项工作都是我想让他们做的，但我想知道哪个更快、更干净和/或更好——或者另一个选择是否更合适?

Note: ViewData.Model is of type IEnumerable<Thing> and I need to display more attributes than Name - I've cropped the code for this example.

注意:显示数据。Model的类型是IEnumerable ，我需要显示比Name更多的属性——我已经为这个例子裁剪了代码。

---

<% foreach (var thing in ViewData.Model)
   { %>
   <p><%= thing.Name %></p>
<% }; %>

---

<% rptThings.DataSource = ViewData.Model;
   rptThings.DataBind(); %>
<asp:Repeater ID="rptThings" runat="server">
    <ItemTemplate>
    <p><%# DataBinder.Eval(Container.DataItem, "Name") %></p>
    </ItemTemplate>
</asp:Repeater>

---

5 个解决方案

#1

foreach is definitely faster, if you don't specifically screw up something. Repeater is cleaner of course, and more neatly separates UI and logic. Sometimes you need more conditions (other than different look even and odd rows) to render your stuff properly which makes foreach the only choice.

如果你没有特别搞砸某件事，那么foreach肯定会更快。中继器当然更简洁，并且更简洁地分离UI和逻辑。有时您需要更多的条件(除了不同的外观和奇数行)，以便正确地呈现您的东西，这使得foreach是惟一的选择。

I personally prefer Repeater for normal situations and foreach for more complex ones.

我个人更喜欢在正常情况下使用中继器，并为更复杂的情况而选择。

EDIT: I was talking about plain ASP.NET with WebControls. For MVC and even pages that are mostly generated by code, I agree that foreach is more straightforward and cleaner.

编辑:我说的是简单的ASP。与WebControls净。对于MVC，甚至是大部分由代码生成的页面，我同意foreach更加简单明了。

#2

foreach is the way to go for ASP.NET MVC. Why? i personally avoid any legacy asp:xxx controls .. because they could possibly have the bloat that exists with the webforms model. Secondly, what about all the event delegates you have to wire up? you're starting to mix and match architectures, IMO, so this could seriously lead to real spagetti code with crazy maintenence and support issues. (IMO: DataBinder.Eval == very evil :( :( :( )

对于每一个人来说都是ASP。净MVC。为什么?我个人避免任何遗留的asp:xxx控件。因为他们可能会有webforms模型存在的膨胀。第二，你需要连接的所有事件委托是什么?您开始混合和匹配架构，在我看来，这可能会导致真正的spagetti代码的维护和支持问题。(国际海事组织:DataBinder。非常邪恶的)(:)

The only asp:xxx control i use is the mastpage / content control(because there are no alternatives to it).

我使用的唯一的asp:xxx控件是mastpage / content控件(因为没有替代的方法)。

Lastly, doing foreach in asp.net mvc is NOT spagetti code, as many people believe. I know i did when i first saw the initial mvc demo's. If anything, it actually makes the UI so much more cleaner than before, imo .. so much more maintainable. IMO, spagetti code is when u have lots of <% .. %> doing business logic and ui logic and (gag) db access. Remember, that's what peeps did in the wild west of asp.net classic :P

最后，在asp.net mvc中执行foreach并不是spagetti代码，很多人都这么认为。当我第一次看到mvc演示时，我就知道是这样的。如果有的话，它实际上使UI比以前更简洁了，在我看来。更易于维护。在我看来，spagetti代码是当你有很多<% .. .执行业务逻辑和ui逻辑和(gag) db访问的%>。请记住，这是peeps在asp.net classic:P的狂野西部所做的

Summary

Stick with foreach and avoid using any webform controls - it's simple, very efficient and very possible to do.

坚持使用foreach并避免使用任何webform控件——它很简单，非常有效，而且很可能实现。

#3

I use the extension method repeater from Phil Haack. Best of both worlds. http://haacked.com/archive/2008/05/03/code-based-repeater-for-asp.net-mvc.aspx

我使用了菲尔。哈克的扩展方法。两全其美。http://haacked.com/archive/2008/05/03/code-based-repeater-for-asp.net-mvc.aspx

#4

<p each="var item in ViewData.Model">${item.Name}</p>

Mmm, tasty Spark.

嗯,美味的火花。

#5

Here's another option. I have not used this myself, but looks interesting.

这是另一种选择。我自己没有使用过这个，但是看起来很有趣。