The good news is that you don't need all of the files you have seen in the lib folder.
What you see in our demos is just the full collection of granular files that one can use. For example, if you only want to use a numeric textbox, there isn't much sense in carrying the scripts for, let's say, the scheduler. This granular approach requires maintenance on part of the developer and to follow what resources you need to include (see here for more details on this approach). The availability of those files is a feature that allows developers fine-grained control, because some people want it.
The easy way to go, however, only requires a few files:
- jQuery - the basic "framework"
- kendo.all.min.js - that's the file containing just about all scripts for all cases so you can instantiate all widgets with it
- kendo.aspnetmvc.js - that's the file that adds some helpers related to translating the razor syntax into the jQuery syntax
- the common styles and a theme with its surrounding assets (images, fonts, more details are available in a link you will find below)
- the Kendo.Mvc.dll assembly.
The way to get the assembly is through the NuGet package that will add the reference for you. To add the client resources, see the last article in the bullet list below.
You can read more about including the various assets in the following articles, and I recommend you review them so you can better understand how the widgets work and what you need:
Get quickly onboarded and successful
with your Telerik and/or Kendo UI products with the Virtual Classroom free technical training, available to all active customers. Learn More.