Web Portal, ASP.Net MVC / C# / SQL Server / DevExpress / JQuery
To an already existing ASP.Net MVC C# solution, add a search query screen, results/grid screen, and edit form for a single table (Dealer). Create an Entity Framework class library for an already existing database. Create a "skeleton" unit test project.
This is a very small test of using Elance on what will hopefully become a bigger project. The biggest problem here is that the work must be done IMMEDIATELY. As in basically one day.
The detailed information below is copied from a document in a Google Drive folder at http://bit.ly/1NMxuuv
The folder contains two .bak files for the necessary databases, as well as the existing solution source code (LabPortal.7z)
It is better to read the document there, as it includes screenshots and formatting.
Document contents are posted below:
Microsoft Visual Studio 2013 - C#
Microsoft SQL Server 2014
ASP.Net MVC 5.2
Entity Framework 6.1
Restore the databases DODBStage and CallCenterTools.
Build the solution LabPortal
Modify web.config as necessary to connect to the databases you have restored
Verify that you can run the website and login using userid=test and password=test123
Task 1: Create a separate Entity Framework project (Class Library)
In other words, create a new project of type Class Library.
Then, to that project, add an ADO.Net Entity Data Model
Name the model and class "DODBStage"
Add this project to the LabPortal.sln
Entities should be created for all tables and views (if any) in the DODBStage database.
It is not necessary to generate entities for stored procedures or functions
Task 2: Create a skeleton Unit Test project and add it to the LabPortal solution.
Create 3 unit tests related to the dealer search functionality. Up to you as to what they should be. What the tests are is not really important - more important is that the Unit Test project exist and that it have a few simple tests.
Task 3: Implement Dealer Search functionality (database table is "Dealer")
Search function should use LINQ to query the database and return results.
Search should use a query screen similar to the below:
Results should be displayed in tabular format using a DevExpress grid (not shown here).
Choosing a result from the grid should open an edit form similar to the below. EDIT FUNCTIONALITY IS NOT REQUIRED! You are simply required to DISPLAY the results. Edit will be required at a later stage, but not now.
Also, it is not necessary to implement the child table that is headed "Dealer Override Shipping Accounts". Ignore that for now.
Whenever necessary, use your best guess at how to implement questionable functionality. When in doubt, generally just best to leave a function out.
I need a proof of concept IMMEDIATELY, as in by noon USA Eastern Standard Time (New York). So speed is more important than full functionality.