In$.$Net $8\mathrm{.}0$ MCV $($NOT NET FRAMEWORK PLEASE!$)$ Build the Contact Manager app

For this project, you will build a multi$-$page, data driven app like the one that's shown below

Specifications

$$ When the app starts, it should display a list of contacts and a link to add a contact.

$$ If the user clicks the first or last name of a contact, the app should display the Detail page for that

contact.

$$ The Details page should include buttons that allow the user to edit or delete the contact. Before

deleting a contact, the app should display the Delete page to confirm the deletion.

$$ To reduce code duplication, the Add and Edit pages should both use the same view. This view should

include a drop$-$down for Category values.

$$ The Add and Edit pages should not include the Date Added field that$$s displayed by the Details page.

That field should only be set only by code when the user first adds a contact.

$$ If the user enters invalid data on the Add or Edit page, the app should display a summary of

validation errors above the form.

$$ Here are the requirements for valid data:

o The Firstname, Lastname, Phone, Email, and CategoryId fields are required.

o The Organization field is optional.

Note: Since the CategoryId field is an int $($see domain model specifications below$),$ you can$$t use

the Required validation attribute with it$.$ However, you can use the Range attribute to make sure

the value of CategoryId is greater than zero.

$$ If the user clicks the Cancel button on the Add page, the app should display the Home page.

$$ If the user clicks the Cancel button on the Edit page, the app should display to the Details page for

that contact.

$$ The domain model classes for contacts and categories should use primary keys that are generated by

the database.

$$ The Contact class should have a foreign key field that relates it to the Category class. It should also

have a read$-$only property that creates a slug of the contact$$s first and last name that can be added to

URLs to make them user friendly.

$$ Use EF Code First to create a database based on your domain model classes. Include seed data for the

categories and one or more contacts.

$$ Use a Razor layout to store the $,,$ and elements.

$$ Use Bootstrap to style the views. If necessary, use a custom CSS style sheet to override Bootstrap

classes.