Before we test our updates, let's make one more change to our Controller.

When processing a post request for

my add entry form, if we have a valid entry data model instance,

we need to save the entry and display the entry's list page back to the user.

Remember how the ModelState contained a collection of the request

form field values.

And for each of those values,

a collection of errors, given that the model state object is tracking all of

the form field value errors, it's able to tell us if our model is in a valid state.

We just need to add an if statement to check if the ModelStates

is valid property, is true.

If the model state is valid, we can save the entry data model instance

by calling the repositories at entry method.

And then we can display the entries list page

instead of redisplaying the AddEntry page.

We'll save doing that for the next video.

Let's move our breakpoint up to the beginning of the method and

press F5 to start our app.

The first thing that catches my eye is the date field value.

Now that we're using our entry data model and we've defaulted its date property

to today, we're getting both a date and a time.

This is happening because MVC calls the to string method on the date time value,

to get the textual representation of that value

when rendering the input elements value attribute.

The date time to string method returns a string containing both a date and a time.

We can customize the formatting of the value by using a different text box for

method overload.

The fifth overload accepts a format parameter,

which allows us to provide a string for the value format.

Behind the scenes, MVC is calling the string format method

with our provided format and the date field value.

Let's look at an example.

Var formattedDate = String.Format and

our format string and our value

model.Date and a semicolon.

If you haven't seen a format string before, it can look a little odd at first.

The format string is simply a string that contains one or more format items.

Format items are defined using a set of curly braces surrounding a number

that represents the index of the object whose string value will be inserted.

We're only working with one value here.

Our model date value.

So we'll use 0 for the index.

Then we can follow the index with a colon and a date time format.

I can never seem to remember the date time format strings that are available to use.

Let's open a new tab and search for

c#, standard, date, format, strings.

The first result is the page that we're looking for, the standard date and

time format strings page on MSDN.

If we scroll down a bit,

we can see that there are a variety of standard format strings available.

A lowercase d that will give us a short date pattern, and

an upper case D that will give us a long date pattern, and so on.

You can see an example of the output here on the right.

I want a short date pattern, so I'm going to go with the lower case D.

You can also create custom date and time format strings.

See the teachers notes for more information.

Let's add our format to the text box for method call.

Curly braces with 0 for the index followed by a colon and

a lowercase d, for our short date pattern.

Then let's remove our temporary example.

Press Ctrl + S to save the View and

refresh the page to see how this affects our date value.

Great!

That remove the time portion just like we wanted.

Lets change the activity value to 1 duration to 23 and

Notes to this is my note and save the form.

Here we are at our break point.

If we expand the entry parameter in the locals window,

we can see that all of our values have flowed correctly to our data model.

We can also hover over the ModelState.IsValid property

to see that is currently true which is what we'd expect.

Press F10 twice to move down to the repositories AddEntry method call.

I'll press F10 one more time to execute the method call.

Now we're at the end of our IF block.

In a bit we will work on displaying our entries list page but

for now we're just going to see your AddEntry page again.

Press F5 to continue.

This time let's remove the duration field value and save the form.

We're at our break point again.

The ModelState.IsValid property is false, which is what we want it to be,

given that we didn't supply a duration field value.

Press F5 to continue, and we're back on our form.

Ideally there'd be a validation message here,

letting us know that we need to supply a duration field value.

We'll implement that later in this course.

Go ahead and stop the app.

If you're using GitHub, let's commit our changes.

Enter a commit message of,

Updated the "AddEntry" controller and

view to use the Entry data model and click the commit all button.

Let's wrap up this section by updating our Add action method

to display the entries list page after successfully adding an entry.