Deploying a Web Application that Uses NetAdvantage for ASP.NET Controls....

Deploying a Web Application that Uses NetAdvantage for ASP.NET Controls

1. 需要创建一个ig_common 的虚拟目录,将你的开发机上的 asp.net 20073CLR20 文件夹和 Image copy 里你的拟目录下。

2. 在程序发布的文件夹内的Bin 里一定要包含全 infragistics .dll

3. 如果用到了webschedule ,那个就要在webschedule 的目创建一个bin文件夹,Bin里面加上一个包含所有infragistics .dll

看具休的档说明

Deploying a Web Application that Uses NetAdvantage for ASP.NET Controls

Before You Begin

Deploying Web applications that use one or more NetAdvantage for ASP.NET controls/components is very similar to deploying any other assembly. The NetAdvantage for ASP.NET controls' assemblies are installed in the Global Assembly Cache (GAC) by default. However, the NetAdvantage 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 NetAdvantage for ASP.NET control assemblies.

What You Will Accomplish

In this walkthrough, you will learn how to deploy NetAdvantage for ASP.NET controls/components to a Web server that hosts your Web application.

Follow these Steps

1. Locate and deploy the correct assemblies.

a. Navigate to the following folder where the NetAdvantage for ASP.NET assemblies are installed by default: C:\Program Files\Infragistics\NetAdvantage for .NET 2007 Vol. 3 CLR 2.0\ASP.NET\bin.

b. 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 NetAdvantage ASP.NET controls/components require the Infragistics2.WebUI.Shared.v7.3 assembly for deployment. For more information on which assemblies need to be deployed for which control, see Deployment Overview.

2. 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 NetAdvantage 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 NetAdvantage for ASP.NET product is installed by default: C:\Program Files\Infragistics\NetAdvantage for .NET 2007 Vol. 3 CLR 2.0\ASP.NET\):

· If you used the WebSchedule™ control in your application, locate the following directory

C:\Inetpub\wwwroot\aspnet_client\Infragistics\20073CLR20\Forms

· If you modified JavaScript files (not recommended), locate the following directory:

C:\Inetpub\wwwroot\aspnet_client\Infragistics\20073CLR20\Scripts

Note: In .NET Framework 2.0, the NetAdvantage for ASP.NET controls' JavaScript files and some images are included in each control's assembly (e.g., Infragistics2.WebUI.UltraWebGrid.7.3) as embedded resources. Therefore, unless you modified the JavaScript files, it's not necessary to deploy the JavaScript files found in the Scripts directory to the production server.

· 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\Infragistics\20073CLR20\Styles

Note: If you are using the WebSchedule, you must deploy Forms and Style directories. In addition, certain presets (e.g., Aero, Aqua presets) also require you to deploy the Style directory.

· 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

3. Deploy the Forms, Scripts, Styles, and Images directories that you located in step 2, as necessary.

. On the production server, create a parent directory.

a. Place the "20073CLR20" and "Images" directories in the parent folder that you created in step 3a.

b. 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 20073CLR20 and "Images" directories under the "Infragistics" directory. Then create the ig_common virtual directory and point to that "Infragistics" folder.

-到些为止我发现我在使用webschedule 的仍然有问题,包下面的错误:

Server Error in '/ig_common/20071CLR20/Forms/WebSchedule' Application.

--------------------------------------------------------------------------------

Configuration Error

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: Could not load file or assembly 'Infragistics2.WebUI.Shared.v7.1, Version=7.1.20071.40, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb' or one of its dependencies. The system cannot find the file specified.

Source Error:

Line 15: <add assembly="System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089" />

Line 16: <add assembly="System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A" />

Line 17: <add assembly="Infragistics2.WebUI.Shared.v7.1, Version=7.1.20071.40, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb" />

Line 18: <add assembly="Infragistics2.WebUI.UltraWebTab.v7.1, Version=7.1.20071.40, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb" />

Line 19: <add assembly="Infragistics2.WebUI.WebDateChooser.v7.1, Version=7.1.20071.40, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb" />

Source File: C:\Inetpub\wwwroot\aspnet_client\infragistics\20071clr20\forms\webschedule\web.config Line: 17

Assembly Load Trace: The following information can be helpful to determine why the assembly 'Infragistics2.WebUI.Shared.v7.1, Version=7.1.20071.40, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb' could not be loaded.

WRN: Assembly binding logging is turned OFF.

To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.

Note: There is some performance penalty associated with assembly bind failure logging.

To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

WRN: Assembly binding logging is turned OFF.

通常的意思在虚拟主机的根目录下的bin文件夹中找不到所需的Assembly文件(或称.dl文件)

于是我加上了最面的第3条,问题解决。

阅读更多
想对作者说点什么? 我来说一句

没有更多推荐了,返回首页