This article is an overview of the Kendo UI Sales Hub sample project. The Kendo UI Music Store includes two sub-projects: the Home and the Order Sales Hub page.
Figure 1. A screenshot of the Kendo UI Sales Hub Home page
The Sales Hub project is an Order Management System that demonstrates the usage of Telerik UI for ASP.NET MVC in an enterprise environment.
The goal of this sample project to is show how to use a subset of Kendo UI widgets using Telerik UI for ASP.NET MVC as well as to show how to easily implement server-side filtering for DataSource requests, using the server-side components that Telerik UI for ASP.NET MVC provides.
This sample is not feature-complete and is only meant to be used as a reference for how to use Telerik UI for ASP.NET MVC.
To view the demo of the Kendo UI Sales Hub sample project, refer to demos.telerik.com/kendo-ui/saleshub.
Start by getting the source for the SalesHub from GitHub.
This sample project is compatible with Microsoft Visual Studio 2012, and requires MVC 4, NuGet, Telerik UI for ASP.NET MVC, and SQLExpress to run.
Due to licensing restrictions, the sample project does not include the dll for the Telerik UI for ASP.NET MVC.
If you have a license for Telerik UI for ASP.NET MVC, use the Telerik Control Panel to download and install the extensions. If you do not have a license yet, download and install the free trial for the extensions.
Once you download and install the extensions, copy
\wrappers\aspnetmvc\Binaries\Mvc3\Kendo.Mvc.dll from the installation directory of Telerik UI for ASP.NET MVC to the
The standard installation directory for the extensions is
C:\Program Files (x86)\Progress\UI for ASP.NET MVC <version>. For versions prior to R3 2017, the default installation folder is
C:\Program Files (x86)\Telerik\UI for ASP.NET MVC <version>.
Once you copy
Kendo.Mvc.dll to the correct location, you should be able to build and run the application.
The first time the application launches, it creates and seeds its database. Seeding the database may take a few minutes to complete.
Figure 2. The Solution Explorer structure
There are three main projects in the Kendo UI Sales Hub sample application, as listed below.
SalesHub.ClientThis is a standard MVC project which uses the default MVC project structure with one exception. The data services, which are MVC controllers that return JSON results, are in their own namespace—
SalesHub.Client.Api—so as to avoid confusion about which controllers return Views and which return JSON.
SalesHub.DataThis project contains the Entity Framework repositories for data models.
SalesHub.CoreThis project contains the data models and the repository interfaces used by
The other chapters of the tutorial on the Kendo UI Music Store sample project are located at: