http://mogadanez.blogspot.com/2009/07/aspnet-mvc-speed-test.html

Thank you.

I couldn’t understand your first answer. For example, I have a Post.ascx and in which, I want to put “Edit” link if the Post’s creator is the current user.
Where from should I bring the CurrentUser?

For the second answer – Thanks, makes sense.

First question – RenderPartial on all accounts. If the data is completely orthogonal, RenderPartial.

Second question, for child partials, it’s mapped on the parent to be the child type.

So,

OrderDto contains a list of OrderLineDto, and I have a partial for both OrderDto and OrderLineDto. Make sense?

How do you pass another complex ViewData to a child partial?

Do you hold nested view data objects?

For example, a blog’s post list page:

PostListViewData contains IEnumerable or IEnumerable ?

The idea is to be able to have in Post.ascx more than a Post in some cases, and properties that aren’t in the Post domain object.
If IEnumerable is used, then is it OK to instantiate PostViewData on the List.aspx?

For example:
< %
foreach (Post p in Model.Posts) {
Html.RenderPartial("Post",new PostViewData { Post=p,SomeOtherThing=someOtherThing });
}
%>

Thanks! ]]> http://lostechies.com/jimmybogard/2009/06/19/the-filter-viewdata-anti-pattern/#comment-1612 E Fri, 10 Jul 2009 17:46:08 +0000 /blogs/jimmy_bogard/archive/2009/06/18/the-filter-viewdata-anti-pattern.aspx#comment-1612 Thank you for this article! I have a question: Where will you preserve "global" variables such as CurrentUser, UserScore, IsAdmin, CurrentTheme etc.? Do you include it in every ViewData class that you need it in? Or do you create a BaseViewData class and let all the ViewData classes inherit from? And if so, where do you fill these variables? In every action, action filter or on BaseController's OnActionExecuted? Thank you for this article!

I have a question:

Where will you preserve “global” variables such as CurrentUser, UserScore, IsAdmin, CurrentTheme etc.?

Do you include it in every ViewData class that you need it in?
Or do you create a BaseViewData class and let all the ViewData classes inherit from? And if so, where do you fill these variables? In every action, action filter or on BaseController’s OnActionExecuted?

Since I’m creating links based on controllers (strongly-typed Url.Action), for me it’s no big stretch. I understand those that are more route-centric it’s a bit of a compromise. At its base, RenderAction renders a route, and you’re not forced to use the controller/action based version.

I imagine it as something like the chain of responsibility pattern – multiple controllers get a “crack” at a request, shaped by a view (since this is how we ultimately determine what HTML gets down to the client).

I’m still with Mike “Sampy” Sampson on this, and not quite convinced by the IMG tag example. In the case of a browser making a request based on an IMG tag URL, it’s still executing the routing logic on the server. By putting a direct reference to the LoginController in your view, you’ve sort of “hardcoded” routing logic right in the view which doesn’t quite “feel” right. I think it’s closer than filtering, though.

Why can’t you pass down the “item” down to RenderPartial? We do this all the time, breaking our model into individual components rendered by strongly-typed views and partials.

i Have list with complex view.
with many and many variats.

very simlify

${item.Name}

so if i use renderPartial, i need create a BIG, COMPLEX, viewdata. and it is not reusable with one item view action