Build a .Net Blazor Application with CRUD operations for an existing Azure SQL Database with 7 tables
Budget: $750 – $1,500 USD
This project needs a Senior .Net Developer to built a lightweight web based Application UI for an existing Azure SQL Server Database. It is basic and can be modeled against a default Blazor application template for "groups".
REQUIREMENTS:
0. Microsoft Azure hosting
1. A .Net Blazor application
- The application should have common functions such as a User Login, User Profile Setting, and Application Settings pages. It should support multiple users and allow 3 user designations: Read, Contribute, or Admin
- Admin console to control CRUD operations for an existing database with 7 tables - 4 are "primary" objects like 'people', 'buildings', 'groups', 'items', and the other 3 are for managing one-to-many relationships with limited detail.
- It should have a feature to upload data for the tables via csv files
- It should be able to read, display, and filter data from Stored procedures or Views; and export the results to a compressed csv file.
2. An API Service - this should be able to call 3-5 stored procedures and return results in REST format. If possible it should be built using one or more Azure Functions. It should accept multiple connections and manage access to the service in a secure way such as OAuth. There should be a screen in the admin console to display and manage these settings.
REQUIREMENTS:
0. Microsoft Azure hosting
1. A .Net Blazor application
- The application should have common functions such as a User Login, User Profile Setting, and Application Settings pages. It should support multiple users and allow 3 user designations: Read, Contribute, or Admin
- Admin console to control CRUD operations for an existing database with 7 tables - 4 are "primary" objects like 'people', 'buildings', 'groups', 'items', and the other 3 are for managing one-to-many relationships with limited detail.
- It should have a feature to upload data for the tables via csv files
- It should be able to read, display, and filter data from Stored procedures or Views; and export the results to a compressed csv file.
2. An API Service - this should be able to call 3-5 stored procedures and return results in REST format. If possible it should be built using one or more Azure Functions. It should accept multiple connections and manage access to the service in a secure way such as OAuth. There should be a screen in the admin console to display and manage these settings.