Chapter 1 - NerdDinner - Errors

sakshamgautam · October 8th, 2009, 07:48 AM

Yes AbrarP, you're right. I think it should be:

Code:

ModelState.AddRuleViolations(dinner.GetRuleViolations());

because in previous page, we created an extension method

Code:

public static void AddRuleViolations(this ModelStateDictionary modelState, ...)

.

Hope this helps!
S.

AbrarP · October 8th, 2009, 09:24 AM

This is what the book doesn't say (pg 70-71): The code for the controllerhelper class is all wrong...

Incorrect Code:

Code:

public static class ControllerHelpers {    
              public static void AddRuleViolations(this ModelStateDictionary                   
                          modelState,   IEnumerable<RuleViolation> errors) {        
                  foreach (RuleViolation issue in errors) {
                             modelState.AddModelError(issue.PropertyName,              
                                                                  issue.ErrorMessage);
                  }    
              } 
}

Correct Code:

Code:

public static class ModelStateHelpers {

        public static void AddModelErrors(this ModelStateDictionary modelState, IEnumerable<RuleViolation> errors) {

            foreach (RuleViolation issue in errors) {
                modelState.AddModelError(issue.PropertyName, issue.ErrorMessage);
            }
        }
    }

sakshamgautam · October 8th, 2009, 10:03 AM

You could either change the method definition or ignore the errata for page 71.

S.

Tharnid · February 8th, 2010, 08:56 PM

Where do you insert the PhoneValidator class? I am finding this follow though very frustrating to say the least :(

sakshamgautam · February 9th, 2010, 04:37 AM

@Tharnid: You can add PhoneValidator class to the Helpers folder inside NerdDinner project. That is where all helper classes should be.

If you have more problems, I suggest that you download the sample code for the book. You can get that from here.

Hope it helps.

StartupGuy · May 22nd, 2010, 09:34 AM

The book authoring/editing process is obviously broken. How hard can it be to copy/paste code from a working program into an authoring tool (i.e., Word, etc.?) This is about the fourth undocumented error I have plowed through while working through this tutorial, and--although there is some educational value in doing your debugging--it is highly irritating.

Anyway, in the introduction of the AJAX call, here is the broken content:

Code:

<%= Ajax.ActionLink( "RSVP for this event",
                             "Register", "RSVP"
                             new { id=Model.DinnerID },
                             new AjaxOptions { UpdateTargetId="rsvpmsg" }) %>

There should, of course, be a comma after the "RSVP" ... so it should look like this:

Code:

<%= Ajax.ActionLink( "RSVP for this event",
                             "Register", "RSVP,"
                             new { id=Model.DinnerID },
                             new AjaxOptions { UpdateTargetId="rsvpmsg" }) %>

I hope this saves at least a few others from debugging drool.

StartupGuy · May 22nd, 2010, 11:28 AM

Here is a lesson learned which could have been avoided with more explicit instructions, re: creating partial views when doing this refactoring.

For RSVP, the text reads:

Quote:

We can do this by right-clicking on the \Views\Dinners folder and then choosing the Add->View menu command. We’ll have it take a Dinner object as its strongly-typed ViewModel. We can then copy/paste the RSVP content from our Details.aspx view into it.

To be brutally-clear, this could read:

Quote:

We can do this by right-clicking on the \Views\Dinners folder and then choosing the Add->View menu command. We’ll have it take a Dinner object as its strongly-typed ViewModel, and be sure to click on the "Create a partial view (.ascx) option". We can then copy/paste the RSVP content from our Details.aspx view into it.

This is obviously a NEWB observation, but that .ascx nuance is vitally important to actually creating a partial view. Since we created our first partial view MANY pages ago, a more explicit reminder to select the "Create a partial view (.ascx)" option would have been very helpful.

If you (like me) do not click on the "Create a partial view (.ascx)" option in that Create View wizard, here is what you will see when you try to run the updated app and select a dinner event to view:

Quote:

MasterPage cannot be applied to this page because the control collection is read-only. If the page contains code blocks, make sure they are placed inside content controls (i.e. <asp:Content runat=server />)

The key here is the phrase "the control collection is read-only." If you then compare your "partial" pages (which were created as .aspx, not .ascx), you will see that your pages begin with:

Code:

<%@ Page Title="" Language="C#" MasterPageFile="~/Views/Shared/Site.Master" Inherits="System.Web.Mvc.ViewPage<NerdDinner.Models.Dinner>" %>

and that the RSVP and EditAndDeleteLinks pages in the NerdDinner 1.0.zip archive of "known-good" source code both begin with:

Code:

<%@ Control Language="C#" Inherits="System.Web.Mvc.ViewUserControl<NerdDinner.Models.Dinner>" %>

So kewl, let's just copy and paste the code from the "known-good" source code into our "partials," right?

Wrong, because our "partials" were not actually created as partials, this won't work, but the resulting error message does look less onerous:

Quote:

Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: The directive 'control' is unknown.

Source Error:

Line 1: <%@ Control Language="C#" Inherits="System.Web.Mvc.ViewUserControl<NerdDinne r.Models.Dinner>" %>

I finally completely removed my RSVP and EditAndDeleteLinks "partials," then looked more closely at the Create View wizard to notice the "Create a partial view (.ascx)" option when I recreated each of them.

I hope others benefit from my hard-learned lesson.

StartupGuy · May 22nd, 2010, 03:22 PM

Just spent the past 2+ hours trying to get Map positioning away from upper-left (in both FF 3.6.2 and IE8). MANY issues out there about this one.

The most current troubleshooting for this is at the CodePlex site for NerDinner: http://nerddinner.codeplex.com/

Your best bet for Map troubleshooting is to head over to the CodePlex site.

Warning: The NerdDinner project has advanced WAY beyond the scope of this tutorial, so it is very difficult to find solutions specific enough to this (first) generation of the code which do not also introduce new dependencies on later-generation additions to the project.

Good luck to all of us.