ASP.NET MVC Application
Budget: £250 – £750 GBP
I want to build an ASP.NET.Core application for Attendance Tracking.
Users will register themselves to the system.
I am not a pro developer but from the work I have done so far, I have listed my requirements in the below lines, these are like guidelines, open to suggestions if it is an upgrade.
I want to use ASP.NET.MVC pattern that is a requirement that won't change.
What I would like is to develop the site together, so that I will be involved in every step of the application.
The application itself will have mostly 3-4 pages for general users, not a complex application but I want to use good architecture and patterns to learn and to develop myself.
There will be an also admin panel but not very complicated, basically for very basic user management and editing drop-down item lists.
REQUIREMENTS:
ASP.NET 5 or 3.1. MVC
Front End not Razor pages, classical MVC (Using Controllers)
Server: MS SQL Server (not Express)
Admin Template can be used, I can purchase it
Bootstrap 4 (latest version for 4)
Jquery
Javascript functions: New functionality like Modules or Classes won't be used. Prototype inheritance can be used.
CSS: Standard CSS (SASS not required)
Good organization for Javascript and CSS files, probably into multiple files.
Modular N-Layer backend.
Entity Framework, migrations, Code First
Dropdown boxes must have typeahead functionality (like Jquery Select2)
Jquery DataTables with server-side Paging, ordering, filtering to be used
Backend Async/Await methods to be used. Front end updates to be with AJAX calls(which may include building partial views or view components)
Tag Helpers to be used
Extension methods to be used for clean coding like to organize ConfigureService methods in the startup class
ASP.NET Identity will be used, required user pages:
* Register (Check if a user is in the database before creating, send an email for login verification, etc. Username can be email)
* Login
* Forget Password (reset password by sending email to the user)
Admin operations for user accounts:
* Approve user Acces level (There will be levels of user access, probably 3)
* Edit users (can make them inactive, there will be no delete user)
* Admin pages, including adding editing elements from dropdown lists
Some architectural ideas nice to have :
- Generic Repository Pattern
- Dependency Injection
- Standard Naming conventions
- JWT Token Based Authentication and Claim Based Authorization
- Logging to Database
- Client and Server-side validation
- Use of AutoMapper
- DTO or ViewModel for data transfer
Users will register themselves to the system.
I am not a pro developer but from the work I have done so far, I have listed my requirements in the below lines, these are like guidelines, open to suggestions if it is an upgrade.
I want to use ASP.NET.MVC pattern that is a requirement that won't change.
What I would like is to develop the site together, so that I will be involved in every step of the application.
The application itself will have mostly 3-4 pages for general users, not a complex application but I want to use good architecture and patterns to learn and to develop myself.
There will be an also admin panel but not very complicated, basically for very basic user management and editing drop-down item lists.
REQUIREMENTS:
ASP.NET 5 or 3.1. MVC
Front End not Razor pages, classical MVC (Using Controllers)
Server: MS SQL Server (not Express)
Admin Template can be used, I can purchase it
Bootstrap 4 (latest version for 4)
Jquery
Javascript functions: New functionality like Modules or Classes won't be used. Prototype inheritance can be used.
CSS: Standard CSS (SASS not required)
Good organization for Javascript and CSS files, probably into multiple files.
Modular N-Layer backend.
Entity Framework, migrations, Code First
Dropdown boxes must have typeahead functionality (like Jquery Select2)
Jquery DataTables with server-side Paging, ordering, filtering to be used
Backend Async/Await methods to be used. Front end updates to be with AJAX calls(which may include building partial views or view components)
Tag Helpers to be used
Extension methods to be used for clean coding like to organize ConfigureService methods in the startup class
ASP.NET Identity will be used, required user pages:
* Register (Check if a user is in the database before creating, send an email for login verification, etc. Username can be email)
* Login
* Forget Password (reset password by sending email to the user)
Admin operations for user accounts:
* Approve user Acces level (There will be levels of user access, probably 3)
* Edit users (can make them inactive, there will be no delete user)
* Admin pages, including adding editing elements from dropdown lists
Some architectural ideas nice to have :
- Generic Repository Pattern
- Dependency Injection
- Standard Naming conventions
- JWT Token Based Authentication and Claim Based Authorization
- Logging to Database
- Client and Server-side validation
- Use of AutoMapper
- DTO or ViewModel for data transfer