In this article, I address several issues that I see quite frequently as issues on the GitHub repo. A lot of these issues stem from a misunderstanding of how Kendo UI works when used alongside of Angular. Most of them are minor, and just require you to use the correct constructs and objects when dealing with Kendo UI widgets. I know that these are common mistakes, because I make them myself all the time!

Most ASP.NET Developers rely on one or more control suites to augment their web applications. Many of these control suites are not only .NET specific, but favor the use of WebForms over the MVC framework that many web application developers are using for new applications. Kendo UI is a powerful cross platform suite of controls that is based on HTML, JavaScript and CSS. This makes the suite completely interoperable across all major web development frameworks, including ASP.NET. And with the MVC Server wrappers and extensions Kendo UI and ASP.NET MVC work even better together!

Software ecosystems are vital to a developer's success. It's hard to place a value on the benefit derived from being able to lean on other's experience, as well as easily find and digest content that's relevant to your project. Ecosystems don't just sprout up overnight though. It takes the right timing, the perfect conditions and lots of love and cultivation. Trying to actively create a new ecosystem around a product or platform is a lot like terraforming. Carl Sagan knows a thing or two about that.

A quick PSA from the Kendo UI team