Deployment Guide


Deploying Ignite UI for jQuery applications requires that you account for the three types of resources that make up a control: JavaScript, CSS and images. Each of these resources may be managed differently depending on how you have your application configured.

Files and Locations

As you prepare to build or deploy your application, it’s a good idea to begin by reviewing the different JavaScript Files in Ignite UI for jQuery. Once familiar with the different types of files used by Ignite UI for jQuery, then refer to Using JavaScript Resources in Ignite UI for jQuery to learn how to reference control resources (including details on localized resources). We have specific topics that cover manually adding files to a page as well as automatically referencing files with the Ignite UI for jQuery script loader. You have the option of requesting files from your servers or via the Infragistics Content Delivery Network (CDN).


If you choose to localize your application you have the option to customize the localization settings, which may have an impact on your deployment procedure.

Using Ignite UI for MVC

You have the option of working with Ignite UI for jQuery controls directly in JavaScript or by using the Ignite UI for MVC. If you use the helper methods then you want to learn how adding controls to an MVC project can affect your deployment.

Styling and Theming

Adding themes to your application requires that you deploy the style and image files to the appropriate place on the server. The Styling and Theming in Ignite UI for jQuery topic includes details on how the files should be organized.

Supporting Old Browsers

Sometimes your application is required to run in some old contexts. Make sure to read Using Ignite UI for jQuery in Browsers Without HTML5 or CSS3 Support to mitigate any issues working with old browsers.

Upgrading Ignite UI for jQuery

If your deployment includes an upgrade in Ignite UI for jQuery, then the Upgrading Projects to the Latest Ignite UI for jQuery Version topic includes the details to help you make a smooth transition.

View on GitHub