Chapter 10 ready for a review
devonlazarus
However, a humble suggestion: I think readers would be better served
with discussion of best practices in rendering dropdown lists,
checkbox lists, and radio lists in "create" and "edit" scenarios.
Neither of these three are what I would consider straight-forward out-
of-the-box, and authoritative content is hard to come by. You have
hinted in your own blog about writing up how you guys do this.
Seriously, it has to be the number one question I get when rendering
forms for input. Again, just my .02. (Plus, although I have my own way
for doing this, I'd really like to see what you guys consider a best
practice.)
Regards,
-devon
Grammatical edits follow:
Page 1:
"We can use web controls that do not take advantage of ViewState, but
that renders most web controls built for WebForms mostly useless."
Avoiding the use of "most" followed by "mostly," could be:
"...but that renders most web controls built for WebForms almost
useless."
Page 2:
"Each means of addressing duplication in our views has its sweet spot,
while there is some overlap between some."
could be:
"... while there is some amount of overlap between them."
"In Chatper 3, we examined using the new templates feature to
standardize on displaying and editing data across our entire
application."
1. Chapter is misspelled
2. "... to standardize displaying and editing..." note the removal of
the word "on"
In this same paragraph you touch on best practices for Templates and
Partials, but ignore Master Pages, Child Actions, and HtmlHelper
Extensions. Quick one-sentence overviews for the remaining three would
be a great addition.
"Originally added as part of ASP.NET 2.0, master pages allowed
developers to create master layouts of common pages."
could be:
"... master pages allow ..."
"Master pages are best applied when more than one view share common
content."
could be:
"... when multiple views share common content."
Page 4:
"The RenderPartial metohd takes a partial name..."
should be:
"The RenderPartial method..."
Page 8:
"... we can define a new base view page to hold our new helper
object. Our new base view page class is shown in listing 10.9."
and
"Listing 10.9: Our shim base view page class"
"view page" should be the actual name of the class here, I think.
(ViewPage) Actually there are several references in this paragraph
that might need this treatment.
On Jan 24, 7:07 pm, Jimmy Bogard <jimmy.bog...@gmail.com> wrote:
> Chapter 10 (Advanced view techniques) is ready for a review.
>
> Thanks everyone!
>
> MVC2iA_CH_10.docx
> 314KViewDownload