RAD Studio (Common)
|
ProjectWeb Deploy Options
Configures a finished ActiveX control or ActiveForm for deployment to a Windows Web server.
Use this page to specify file locations, a URL, and CAB file compression and version information.
Item |
Description |
Target Dir |
Specifies the location of the ActiveX library file as a path on the Web server. This can be a standard path name or a UNC path. Click the Browse button to navigate to a desired directory, for example, C:\INETPUB\wwwroot. |
Target URL |
Specifies the URL for the ActiveX library file. See your Web server documentation for information on how it specifies URLs, for example, http://mymachine.borland.com/. |
HTML Dir |
Specifies the location where the HTML file that contains a reference to the ActiveX control should be generated. This can be a standard path name or a UNC path. Click the Browse button to navigate to the desired directory, for example, C:\INETPUB\wwwroot. |
Use CAB file compression |
Compresses the ActiveX library and all required packages and additional files that do not specify otherwise. Cabinet compression stores files in a file library, which can decrease download time by up to 70 percent. |
Include file version number |
Includes the version information specified on the VersionInfo page of the Project Options dialog box. |
Auto increment release number |
Automatically increments the project’s release number every time you choose ProjectWeb Deploy. This updates the value on the VersionInfo page of the Project Options dialog box. |
Deploy required packages |
Deploys all packages listed on the Packages page along with the project. |
Deploy additional files |
Deploys all files listed on the Additional Files page along with the project. |
Use this page to indicate which packages must be deployed with your project and how they should be deployed. Each package can specify its own options, overriding the defaults on the Project page. Packages that ship with this product are code signed with the CodeGear signature.
Item |
Description |
Packages used by this project |
Lists the packages that are required by your ActiveX library project. Select a package in this list to modify its options. |
Compress in a separate CAB |
Creates a separate .cab file for the package. |
Compress in project CAB |
Includes the package in the project .cab file. |
Use file VersionInfo |
If the package includes a VersionInfo resource, the version information in that resource is added to the .inf file for the project. |
Target URL |
Specifies the URL for the package file. If this is blank, the Web browser assumes the file already exists on the client machine. If the client does not have the package, the download of the ActiveX library fails. |
Target directory |
Specifies the directory where the package should be written on the server. This can be a standard path name or a UNC path. If this is blank, it indicates that the file already exists and should not be overwritten. |
Use this page to indicate files other than packages that must be deployed with your project and how they should be deployed. You can use this page to add files or to specify the options for any file, overriding the defaults on the Project page.
Item |
Description |
Files associated with project |
Lists the files (other than packages) that are required by your ActiveX library project. You can add files to the list by clicking the Add button. You can remove the selected file by clicking the Remove button. Select a file to modify its options. |
Compress in a separate CAB |
Creates a separate .cab file for the package. |
Compress in project CAB |
Includes the package in the project .cab file. |
Use file VersionInfo |
If the package includes a VersionInfo resource, the version information in that resource is added to the .inf file for the project. |
Target URL |
Specifies the URL for the package file. If this is blank, the Web browser assumes the file already exists on the client machine. If the client does not have the package, the download of the ActiveX library fails. |
Target directory |
Specifies the directory where the package should be written on the server. This can be a standard path name or a UNC path. If this is blank, it indicates that the file already exists and should not be overwritten. |
Copyright(C) 2009 Embarcadero Technologies, Inc. All Rights Reserved.
|
What do you think about this topic? Send feedback!
|