Create a simple page to upload/view files using .NET Core Web API and Angular -- 3
Budget: $30 – $250 USD
UI/UX NOT NEEDED IN THE PROJECT & HANDING OVER MANDATORY
Using .NET Core Web API and Angular (latest) create a simple page to upload/view files. The page is split into two parts: upload area and view area.
Upload area - single for all files. File size and file types that can be uploaded to the server must be configurable. Validation for invalid data should present.
View area consists of tables - one table per permitted file type. Each table must reflect: file name, file size, upload date. Keep in mind that the number of files can be unlimited.
Add at least two unit tests for the back-end and two unit tests for the front-end. Tests must have positive and negative scenarios. Default tests added by angular cli will be ignored during the task evaluation.
API and UI must have layered architecture, code must follow common style guides and development principles
The page should be as generic/reusable as possible
Feel free to choose any storage for uploaded files (it can be DB/File System/etc.) The only requirement here - storage must be persistent during runtime
Implement File download/preview.
* project should not contain code that is not related to the task
** all external references must be excluded from the package with the project (please do NOT include Node Modules).
FAQs
1.Page should be as generic/reusable as possible - what does it mean exactly?
Make sure everything is componetised and coded in a proper and correct way. Not sure all coded on one screen
2.What types of downloadable files must the application support?
It can support any files, you can make up which files it supports. It only needs to show the metadata of the files not view them
3.User that uploaded file-Does it mean that the application should also support the simplest security (user registration/login)?
No need to do user login, the page does not need security
4.Are there any restrictions as for .Net version to be used? Should it necessarily be .Net Core? Could I use "standard" MVC solution for security?
Standard MVC is fine, no need to use .net Core
5.Do I understand right that application does not have to expose file content, but only file metadata listed above?
Correct, only needs to show meta data, no need to show file content
The project must done during 6 hours.
Using .NET Core Web API and Angular (latest) create a simple page to upload/view files. The page is split into two parts: upload area and view area.
Upload area - single for all files. File size and file types that can be uploaded to the server must be configurable. Validation for invalid data should present.
View area consists of tables - one table per permitted file type. Each table must reflect: file name, file size, upload date. Keep in mind that the number of files can be unlimited.
Add at least two unit tests for the back-end and two unit tests for the front-end. Tests must have positive and negative scenarios. Default tests added by angular cli will be ignored during the task evaluation.
API and UI must have layered architecture, code must follow common style guides and development principles
The page should be as generic/reusable as possible
Feel free to choose any storage for uploaded files (it can be DB/File System/etc.) The only requirement here - storage must be persistent during runtime
Implement File download/preview.
* project should not contain code that is not related to the task
** all external references must be excluded from the package with the project (please do NOT include Node Modules).
FAQs
1.Page should be as generic/reusable as possible - what does it mean exactly?
Make sure everything is componetised and coded in a proper and correct way. Not sure all coded on one screen
2.What types of downloadable files must the application support?
It can support any files, you can make up which files it supports. It only needs to show the metadata of the files not view them
3.User that uploaded file-Does it mean that the application should also support the simplest security (user registration/login)?
No need to do user login, the page does not need security
4.Are there any restrictions as for .Net version to be used? Should it necessarily be .Net Core? Could I use "standard" MVC solution for security?
Standard MVC is fine, no need to use .net Core
5.Do I understand right that application does not have to expose file content, but only file metadata listed above?
Correct, only needs to show meta data, no need to show file content
The project must done during 6 hours.