Using Ignite UI and ASP.NET MVC

Craig Shoemaker / Tuesday, March 24, 2015

Accompanying the 15.1 release we are focusing in on an aspect of Ignite UI that is specifically tailored to the ASP.NET MVC developer. In light of this effort, I wanted to share a few ideas for you to keep in mind as you begin to Ignite UI in ASP.NET MVC.

Helper Syntax in a JavaScript World

Although Ignite UI is a HTML5 and JavaScript-based jQuery UI control suite, you can interface with each control exclusively through its MVC Helper. These helpers are great if you feel more comfortable working in Razor and C# rather than JavaScript.

Beyond ASP.NET MVC Ignite UI is built to work with any web server platform. This means that as you read through the help documentation or samples, most of the guidance shows code in JavaScript. This is done on purpose in order to demonstrate how the controls work on any platform, but you can always “translate” any of the JavaScript code to the MVC Helper syntax - and this video can help you with that process.

Are Helpers Required?

You are not required to use the MVC Helpers if you want to use Ignite UI with ASP.NET MVC and there are many different approaches you can take to build your applications. Ultimately Ignite UI is a collection of jQuery UI controls and Ignite UI MVC simply focuses on the ASP.NET MVC helpers available for each control.

While the helpers are available you out-of-the-box, they are by no means required when using ASP.NET MVC. You could opt to use a straight jQuery approach, exclusively use the MVC helpers or decide to mix approaches depending on the needs of your application. In the end, the very same functionality is available from Ignite UI regardless of if you decide to use the MVC helpers or not.

More Info

For more information on building ASP.NET MVC applications with Ignite UI, make sure to read Developing ASP.NET MVC Applications with igGrid.