ASP.net WebForms portal for data storage (VB only)

I'm looking for a freelancer to create a new application/portal using ASP.NET WebForms VB ONLY within a timeline of 6/10 days (test included). Informations are sufficient to provide an estimate (times and costs). No C#, no third party controls, no compiled objects. Using free objects/sources freely available on the internet is really appreciated (and reduces testing and development time). ----- General info ----- The new portal/application must allows (after login with standard user/pass method) users to: - define the location (is a form within 7/8 fields about location (city, addreess, zip code, ...) with a Maps picture of the address) - store and retrieve file (on local server, no cloud/GDrive/...) via browser - create and manage a gantt (it is a stand-alone function: If the user want to define/print a gantt because he's responsible of a task, he can defines task name, task description, start date, .... and he can use the gantt created, without use MS Project or other) Browsers in use are Firefox and Chrome. The new portal/application will work under IIS 10 (Windows). ----- Develop environment and test ----- If you need online free service for ASP pages, could you use - [login to view URL] - [login to view URL] ----- Process info ----- One Admin only (using his own admin console). User registration not needed: users will be invited and they receive user/pass to access. Users side, he can: - file upload (using drag & drop too) to server repository. Every type of file (.jpg, .xls, .doc, .dwg, ...); - file and directory browse (server repository) [something like "File explorer" of windows]; - download a file/directory Full details after project assignment. It will be really appreciated if each file will show its own icon (so, if I upload a word file, the icon will be the classic blue W) Application layout (icons, colors, template, ...) will be provided using a free template. If you have some advice or templates that you already have experience with, let's evaluate together whether we can use it. Application layout must be approved before starting coding. Logo image will be place on login form and inside the application. About application purpose..... the portal will be used to define an "environment" and upload file for each "category" of this environment . On each category, the user IF ALLOWED can upload files (photos or documenst) and describe what upload is (a couple of textboxes: title and description) If not allowed, he cannot see the content. LOG of activities done by each user is needed (a DB table with: who, date, time, what) ----- Roles ----- Some users can do everything, some can only upload (and read) to certain "category". The structure of the tree (obviously) is not fixed. It changes according to the customer's needs. Currently, 5 types of users have been defined. ----- System and database ----- File uploaded must be written into Windows filesystem (probably database use however it is necessary). "MS Access" DB is preferable (or you can use what you prefer BUT you have to export in .mdb the database file for our test). Access 97/2000. Application will be tested and used into an Intranet. The application will work into an intranet (no internet) and will be designed for publishing files and sharing files to other users inside the same LAN. ----- Costs and quality ----- Please pay attention on application performances. Pay attention to the budget limit. No upfront. No payment before successful completion of all tests. Source-code required for test Unnecessary images, files, libraries, ... must be removed. The source code is required to have a good level of comments, to allow bug-fixing, code maintenance and possibly future evolution. Bonuses are provided at the end of the project for compliance with the timing and quality of the software. Please, no ask «me what is your budget for this project?» Details, clarifications, use cases and test results will be shared after the project has started. ----- Timing ----- Proposals from programmers who do several activities in parallel will not be accepted: the quality of work could be low. Start as soon as possible - daily update is requested (showing progress), to avoid time loss and misunderstandings about requirements. Without daily update with project progress, project will be un-assigned.