Edit this page

Getting Started on Linux

This article demonstrates how to configure an ASP.NET Core project that enables you to use Telerik UI for ASP.NET Core on Linux.


The following steps are tested on Ubuntu 14.04 and 16.04. and on MacOS X El Capitan 10.11.6.



To configure an ASP.NET Core project that enables you to use Telerik UI for ASP.NET Core on Linux:

  1. Create an ASP.NET Core web site.
  2. Add the Kendo UI NuGet package.

Create ASP.NET Core Web Sites


If you are configuring an existing project, skip this step.

Below are listed the steps for you to follow when creating an ASP.NET Core web site. To scaffold an empty ASP.NET application, the examples use Yeoman.

  1. Install Node.js v.4.x.

        curl -sL https://deb.nodesource.com/setup_4.x | sudo -E bash -
        sudo apt-get install -y nodejs
  2. Check if the Node.js version is the desired one.

        kendo@kendo-docker:~$ nodejs -v
  3. Install the Yeoman and an aspnet generator.

        sudo npm install -g yo generator-aspnet
  4. By using the Terminal, navigate to the folder where you want to create the project folder.

        kendo@kendo-docker:~$ mkdir Projects
        kendo@kendo-docker:~$ cd Projects/
  5. Run yo aspnet. The following example demonstrates a result that is similar to the response you are expected to receive.

        kendo@kendo-docker:~/Projects$ yo aspnet
            |       |    .--------------------------.
            |--(o)--|    |      Welcome to the      |
           `---------´   |   marvellous ASP.NET 5   |
            ( _´U`_ )    |        generator!        |
            /___A___\    '--------------------------'
             |  ~  |
         ´   `  |° ´ Y `
        ? What type of application do you want to create?
          Empty Application
          Console Application
          Web Application
        ❯ Web Application Basic [without Membership and Authorization]
          Web API Application
          Nancy ASP.NET Application
          Class Library
          Unit test project
  6. Select the Web Application Basic option by using the keyboard Arrow keys and press Enter. Type the name of the new application. Note that you can skip this step and use the default name by pressing Enter. After you set the name, the generator creates the desired folder and the selected application. When finished, the scaffolded project should be ready.


    Yeoman gets improved in time and the steps above might change. For more information, refer to the Yeoman resources.

  7. Navigate to the created folder and run dotnet restore.


    For up-to-date commands, refer to the guide on getting started with .NET Core.

    As a result, the NuGet packages are downloaded. The following example demonstrates a result that is similar to the end of the response you are expected to receive.

        Restore complete, 10070ms elapsed
  8. Start the application by running dotnet run. The following example demonstrates the response you are expected to receive.

        Hosting environment: Production
        Now listening on: http://localhost:5000
        Application started. Press Ctrl+C to shut down.
  9. Use your favorite browser to navigate to the above location and make sure the application is working in the way shown below. After you check the application in the browser, stop the server.

    Figure 1. The web application in the browser

    Web application in browser

Add the Telerik.UI.for.AspNet.Core NuGet Package

  1. Open the project.json file by using a text editor, add the Telerik.UI.for.AspNet.Core dependency, and replace productVersion with an actual Telerik UI for ASP.NET Core version—for example, 2016.3.914.

        "dependencies": {
            "Telerik.UI.for.AspNet.Core": "productVersion"
  2. Add the private Telerik NuGet feed.

    NuGet Sources Add -Name "telerik.com" -Source "https://nuget.telerik.com/nuget" -UserName "your telerik.com login email" -Password "your telerik.com password" -StorePasswordInClearText


    Store the password in clear text because the .NET Core tooling does not support encryption.

  3. Restore the packages by running dotnet restore.

    • Troubleshooting

      You might get an error similar to error: Unable to resolve 'Telerik.UI.for.AspNet.Core (>= 2017.1.118)' for '.NETCoreApp,Version=v1.1'. It is caused by problems in the tooling. For more information, refer to the GitHub issues in Nuget/Home and in dotnet/core).

    • Workarounds

      When you use NuGet to add a private feed, NuGet Sources Add writes in the ~/.config/NuGet/NuGet.Config file. However, when you run dotnet restore, the ~/.nuget/NuGet/NuGet.Config file is used to read packageSources and packageSourceCredentials.

      Until this issue in the tooling gets fixed, you can either:

      • Copy your telerik.com credentials manually from ~/.config/NuGet/NuGet.Config to ~/.nuget/NuGet/NuGet.Config, or
      • Create a NuGet.Config file in the project folder with the contents from ~/.config/NuGet/NuGet.Config.
      <?xml version="1.0" encoding="utf-8"?>
          <add key="nuget.org" value="https://api.nuget.org/v3/index.json" protocolVersion="3" />
          <add key="telerik.com" value="https://nuget.telerik.com/nuget" />
            <add key="Username" value="your.telerik.com@email.login" />
            <add key="ClearTextPassword" value="your.telerik.com.password.in.clear.text" />
  4. Open Startup.cs by using a text editor (IDE) and update it in the way demonstrated in the following examples.

    Locate the ConfigureServices method and add a call to services.AddKendo at the end.

        using Newtonsoft.Json.Serialization;
        public void ConfigureServices(IServiceCollection services)
            // Maintain property names during serialization. See:
            // https://github.com/aspnet/Announcements/issues/194
                .AddJsonOptions(options => options.SerializerSettings.ContractResolver = new DefaultContractResolver());
            // Add Kendo UI services to the services container

    Locate the Configure method and add a call to app.UseKendo at the end.

        public void Configure(IApplicationBuilder app, IHostingEnvironment env, ILoggerFactory loggerFactory)
            // Configure Kendo UI
  5. Import the Kendo.Mvc.UI namespace in ~/Views/_ViewImports.cshtml through @using Kendo.Mvc.UI.

  6. Copy the Kendo UI client-side resources.

    • Manual installation—To manually install the resources, copy the js and styles folders from the telerik.ui.for.aspnetmvc archive to wwwroot\lib\kendo-ui.

      Figure 2. Kendo UI resources

      Kendo UI resources

    • Bower package installation—For more information on how to achieve this, refer to the Kendo UI Professional Bower package installation.

  7. Register the Kendo UI styles and scripts in ~/Views/Shared/Layout.cshtml.

        <link rel="stylesheet" href="~/lib/kendo-ui/styles/kendo.common-bootstrap.min.css" />
        <link rel="stylesheet" href="~/lib/kendo-ui/styles/kendo.bootstrap.min.css" />
        <link rel="stylesheet" href="~/lib/kendo-ui/styles/kendo.dataviz.bootstrap.min.css" />
        <script src="~/lib/kendo-ui/js/kendo.all.min.js"></script>
        <script src="~/lib/kendo-ui/js/kendo.aspnetmvc.min.js"></script>
        @RenderSection("scripts", required: false)
  8. Use a Kendo UI widget by adding the snippet from the following example to ~/Views/Home/Index.cshtml.

        <h2>Kendo UI DatePicker</h2>
        @section scripts {
  9. Navigate to the project folder by using the Terminal and run it using the dotnet run command. Now that all is done, you can see the sample page.

    Figure 3. The end result—a sample page

    Sample page

See Also