Deploying Web applications that use one or more Ultimate UI for ASP.NET controls/components is very similar to deploying any other assembly. The Ultimate UI for ASP.NET controls' assemblies are installed in the Global Assembly Cache (GAC) by default. However, the Ultimate UI for ASP.NET controls use other folders that you should be aware to ensure successful deployment. In .NET Framework 2.0, it’s relatively simple to deploy the Ultimate UI for ASP.NET control assemblies.
In this walkthrough, you will learn how to deploy Ultimate UI for ASP.NET controls/components to a Web server that hosts your Web application.
Locate and deploy the correct assemblies.
Navigate to the following folder where the Ultimate UI for ASP.NET assemblies are installed by default:
C:\Program Files (x86)\Infragistics\2023.1\ASP.NET\ASP.NET\bin.
..
Copy the necessary assemblies from this directory and paste them into your Web application’s bin directory on the production server. Alternatively, you can place the Infragistics assemblies into the production server’s GAC, assuming you have the proper permissions.
At minimum, all Ultimate UI for ASP.NET controls/components require the Infragistics4.WebUI.Shared.v23.1 assembly for deployment. For more information on which assemblies need to be deployed for which control, see Deployment Overview.
In certain cases, you may need to deploy the Forms, Scripts, Styles, and Images directories (see the list below for the scenarios). By default, the Ultimate UI for ASP.NET controls/components look for a virtual directory called ig_common
, which points to the physical path of the Forms, Scripts, Styles, and Images directories. (Alternatively, you can locate these directories in the following folder where the Ultimate UI for ASP.NET product is installed by default: C:\Program Files (x86)\Infragistics\2023.1\ASP.NET\ASP.NET\):
If you used the WebSchedule™ control in your application, locate the following directory
C:\Inetpub\wwwroot\aspnet_client\Infragistics23.1CLR4\Forms
** If you modified JavaScript files (not recommended), locate the following directory:
C:\Inetpub\wwwroot\aspnet_client\Infragistics23.1CLR4\Scripts
If you used the WebSchedule control in your application, or you applied presets (i.e., Aero, Aqua, Default, ElectricBlue, Onyx, Royale, XpBlue, XpOlive, or XpSilver), located the following directory:
C:\Inetpub\wwwroot\aspnet_client\Infragistics23.1CLR4\Styles
If you are using your own custom images in your application, as opposed to Infragistics' predefined images, locate the following directory:
C:\Inetpub\wwwroot\aspnet_client\Infragistics\Images
Deploy the Forms, Scripts, Styles, and Images directories that you located in step 2, as necessary.
On the production server, create a parent directory.
Place the "23.1CLR4" and "Images" directories in the parent folder that you created in step 3a.
Create the ig_common
virtual directory and point to the parent folder that you created. For example, if you create a parent folder named "Infragistics" anywhere on the production server, place the 23.1CLR4 and "Images" directories under the "Infragistics" directory. Then create the ig_common
virtual directory and point to that "Infragistics" folder.