C# Build the Contact Manager App For this project, you will build a multi$-$page, data driven app The Home page title is "Conctact Manager" has $5$ colunms: first name, last name, phone #$,$ email and category. When the user clicks on the name, $($first and last names$)$ it links to the Edit page, if your Details page is not working, please just go to the Edit page.

The Add and Edit pages $($both use the same view$)$ final version these pages has first name text box, last name text box, phone text box, email textbox $,$ category textbox and organizaiton textbox in rows with add and cancel buttons on the bottom of contact page and lastly a delete contact page with text $"$Do you really want to delete $+$ contacts first and lastname.

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 $($Family$,$ Friend, Work$).$

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 Category fields are required.

o The Organization field is optional.

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 the

Details page for that contact.

The model classes for contacts should use primary key that is generated by the database.

The Contact class should 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 model classes. Include

seed data for the contacts.

Use the default route with an additional route segment that allows an optional slug at the

end of a URL.