Step-By-Step Example
2006 Volume 1 for CLR 1.x or for CLR 2.0
2006 Volume 2 for CLR 1.x or for CLR 2.0
2006 Volume 3 for CLR 1.x or for CLR 2.0
There are two steps necessary for deploying an ASP.NET application that utilizes elements from NetAdvantage 2006 Volume 1, Volume 2, or Volume 3:
Step 1: Deploy the correct assemblies necessary to the production server
Step 2: Deploy the correct JavaScript, form, style, and image files to the production server.
Step 1: How to deploy the correct assemblies
Starting with NetAdvantage 2004 Volume 2, the Infragistics assemblies are installed into the Global Assembly Cache (GAC). When in development, all of the references to the Infragistics assemblies have their copy local property set to false except the Shared assembly. Therefore when you deploy your application to a production server, you have to drill down into your development machine and copy all of the necessary assemblies to the production server.
The Infragistics assemblies are located at the following path on your development machine's hard disk, assuming the installation is made to the default destination folder:
For NetAdvantage 2006 Volume 1 for CLR 1.x: C:\Program Files\Infragistics\NetAdvantage 2006 Volume 1 CLR 1.x\ASP.NET\Bin
For NetAdvantage 2006 Volume 1 for CLR 2.0: C:\Program Files\Infragistics\NetAdvantage 2006 Volume 1 CLR 2.0\ASP.NET\Bin
For NetAdvantage 2006 Volume 2 for CLR 1.x: C:\Program Files\Infragistics\NetAdvantage 2006 Volume 2 CLR 1.x\ASP.NET\Bin
For NetAdvantage 2006 Volume 2 for CLR 2.0: C:\Program Files\Infragistics\NetAdvantage 2006 Volume 2 CLR 2.0\ASP.NET\Bin
For NetAdvantage 2006 Volume 3 for CLR 1.x: C:\Program Files\Infragistics\NetAdvantage 2006 Volume 3 CLR 1.x\ASP.NET\Bin
For NetAdvantage 2006 Volume 3 for CLR 2.0: C:\Program Files\Infragistics\NetAdvantage 2006 Volume 3 CLR 2.0\ASP.NET\Bin
Copy the necessary assemblies from this directory and paste them into the bin directory of your application on the production server. DO NOT copy them into the bin directory of your application on the development machine, as you will start to get errors once you start to modify that application again.
Note: Placing the necessary assemblies in the bin directory of your application is assuming that the developer doesn’t have permissions to place the assemblies in the GAC. If you have permissions to place assemblies in the GAC, then place the Infragistics assemblies in the GAC of the production server. Doing this will ensure that all of your applications on the server are using the same versions of the assemblies.
Step 2: How to deploy the correct JavaScript, form, style, and image files
By default, Infragistics web controls look for a virtual directory called "ig_common", which points to the physical path of the JavaScript, form, style, and image files. On the development machine, the physical path of these files are:
For 2006 Volume 1 for CLR 1.x:
Scripts:
C:\Inetpub\wwwroot\aspnet_client\Infragistics\20061\Scripts
Images:
C:\Inetpub\wwwroot\aspnet_client\Infragistics\Images
Forms: (used by WebSchedule)
C:\Inetpub\wwwroot\aspnet_client\Infragistics\20061\Forms
Styles: (used by WebSchedule)
C:\Inetpub\wwwroot\aspnet_client\Infragistics\20061\Styles
For 2006 Volume 1 for CLR 2.0, replace "20061" above with "20061clr20".
For 2006 Volume 2 for CLR 1.x:
Scripts:
C:\Inetpub\wwwroot\aspnet_client\Infragistics\20062\Scripts
Images:
C:\Inetpub\wwwroot\aspnet_client\Infragistics\Images
Forms: (used by WebSchedule)
C:\Inetpub\wwwroot\aspnet_client\Infragistics\20062\Forms
Styles: (used by WebSchedule)
C:\Inetpub\wwwroot\aspnet_client\Infragistics\20062\Styles
For 2006 Volume 2 for CLR 2.0, replace "20062" above with "20062clr20".
For 2006 Volume 3 for CLR 1.x:
Scripts:
C:\Inetpub\wwwroot\aspnet_client\Infragistics\20063\Scripts
Images:
C:\Inetpub\wwwroot\aspnet_client\Infragistics\Images
Forms: (used by WebSchedule)
C:\Inetpub\wwwroot\aspnet_client\Infragistics\20063\Forms
Styles: (used by WebSchedule)
C:\Inetpub\wwwroot\aspnet_client\Infragistics\20063\Styles
For 2006 Volume 3 for CLR 2.0, replace "20063" above with "20063clr20".
On the production server create a parent folder, and place the '20061' ('20061clr20', '20062', '20062clr20', '20063', or '20063clr20') and 'Images' folders into that folder. Now create the ig_common virtual directory and point that to the parent folder that you created. For example if you create a folder named 'infragistics' on the production server (anywhere on the disk), place the '20061' ('20061clr20', '20062', '20062clr20', '20063', or '20063clr20') and 'Images' folders under the 'infragistics' folder and then create the ig_common virtual directory and point it to that 'infragistics' folder.
Starting in NetAdvantage 2004 Volume 3, there is an alternative to using the ig_common virtual directory on the production server for the JavaScript, image, style, and forms files. You can specify the location of the javaScriptDirectory, imageDirectory, cssDirectory, and formsDirectory for the entire application in the web.config file. If you want to take this approach you can use the following Knowledge Base article.
In NetAdvantage for CLR 2.0, the JavaScript files and some images are included with the .NET assemblies as embedded resources. As such, it is no longer necessary to deploy the JavaScript files to the production server. If only default images are used, you may not need to deploy the image files, but if you use presets or non-default images, you must deploy the image files. If you are using WebSchedule, you must deploy the forms and styles files.
|