Assignment $02-$ Fuli stack CRUD operations

Glilld the Contact Manager app

No sin

The thenery

Contret manager

beiste Centst I want step by step deatil and code for every page 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: The Firstname, Lastname, Phone, Email, and CategoryId fields are required. The Organization field is optional. Note: Since the CategoryId field is an int $($see domain model specifications below$),$ you can$$t use the Requprired 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. Use the default route with an additional route segment that allows an optional slug at the end of a URL. Make the app URLs lowercase with trailing slashes. Requirements and Delivery $$ Functionality: o Create $($C$)$: Create operation should successfully add new data to the database or data source. $$ Newly created data should be persistent and retrievable. o Read $($R$)$: $$ Read operation should retrieve existing data from the database or data source. $$ Retrieved data should be accurate and complete. o Update $($U$)$: $$ Update operation should modify existing data in the database or data source. $$ Updated data should reflect the changes made by the user and be stored correctly. o Delete $($D$)$: $$ Delete operation should remove existing data from the database or data source. $$ Deleted data should be permanently removed and not retrievable. $$ User Interface $($UI$)$: o Create $($C$)$: $$ User interface should provide a form or input fields for users to input data for creation. o Read $($R$)$: $$ User interface should display retrieved data in an organized and readable format. o Update $($U$)$: $$ User interface should provide options for users to edit existing data. o Delete $($D$)$: $$ User interface should include a mechanism for users to delete data. $$ Error Handling: o Create $($C$),$ Read $($R$),$ Update $($U$),$ Delete $($D$)$: $$ Proper error handling should be implemented for cases such as network errors, server errors, or invalid user input. $$ Users should be provided with clear error messages or feedback.