Incoding Framework - Getting Started

After the installation, the client logic is added to the UI using IML.

UnitTests

During the installation of Incoding tests helpers, the project is added by the MSpecAssemblyContext.csis file, in which connection is customized to the test database.

Part 1: Installation

So, we proceed to the task of the disclaimer and start writing our application. The first phase of building the application is to create solution structure of a project and to add the projects to it. The project solution will be called Example and as was already mentioned in the introduction, will have three projects. We begin with the project that is responsible for business logic of the application - Domain.

Create class library Domain.

Figure 2: Library

Then we proceed to the front-end and create, install ASP.NET Web Application UI with links to the MVC packages as template, empty project.

Figure 3: Empty Project

Figure 4: MVC App

Finally, we added class library UnitTests responsible for unit testing.

Figure 5: Unit Testing

Note: Although UnitTests are not an obligatory part of the application, we recommend you to cover the code with tests as it will help to avoid numerous problems in future with various possible faults in the code due to test automation.

After having finished all the above activities, you will get the following solution.

1. Right-click the project and select Manage NuGet Packages… in the context menu
2. Search incoding
3. Select necessary package and install it

First install Incoding framework in Domain

Figure 7: Framework Domain

Figure 8: Structure MAp Graph

1. Incoding Meta Language
2. Incoding Meta Language Contrib (optional)

Figure 9: Incoding Meta

Figure 10: ExampleUI

Note: Make sure that the Copy Local property is set to true in the References -> System.Web.Mvc.dll

Now change the file Example.UI - Go to Views, Shared, then _Layout.cshtml so that it looks as in the following:

Then add the link to Bootstrapper.cs to the files Example.UI, go to App_Start, IncodingStart.cs and select Example.UI, then click Controllers and DispatcherController.cs.

Figure 11: Bootstrapper

Figure 12: Coding

Note: If you use MVC5, it’s necessary for framework to add the following code to Web.config file.

Now install Incoding tests helpers in UnitTests and add the link to Bootstrapper.cs in Example.UnitTests, MSpecAssemblyContext.cs.

Figure 13: Incoding Test



Figure 14: Output

1. Operations – command and query of the project.
2. Persistence – entities for DB mapping.
3. Specifications – where and order specifications for data cleaning when request is made.

Figure 15: Opretions

Figure 16: Example Unit Test

To begin this process, create DB with which you will work. Open SQL Managment Studio and create two DB: Example and Example_test.

In order to work with DB, you need to set up a connection. Add to the file Example.UI, then Web.config and Example.UnitTests, then app.config connection string to the BD.

Note: Example and Example_test databases must exist.

Part 3: CRUD

After the actions described above, we come to the most interesting part – code writing implementing the CRUD (create, read, update, delete) functionality of an application. To begin the process, create an entity class that will map to the DB. In our case, this is Human.cs that we add to the Example.Domain -> Persistences folder.

Human.cs

@Html.ForGroup()

@Html.ValidationMessageFor()