Microsoft KB Archive/219050

= HOW TO: Deploy Web Applications with Visual InterDev 6.0 =

Article ID: 219050

Article Last Modified on 6/29/2004

-

APPLIES TO


 * Microsoft Visual InterDev 6.0 Standard Edition
 * Microsoft Internet Information Services 5.0
 * Microsoft Internet Information Server 4.0

-



This article was previously published under Q219050



IN THIS TASK
SUMMARY
 * Configure the Target Server
 * Prepare the Project Folder Permissions
 * Use Visual InterDev to Deploy Web Applications
 * Additional Features

REFERENCES



SUMMARY
This step-by-step article tells how to use the Visual InterDev Deploy Web features to periodically deploy and redeploy your application into production if Visual Interdev is not on your production Web server.

NOTE: See the "References" section for information about the Copy Web feature and in-depth information about the Deploy feature.

back to the top

Configure the Target Server
There are several steps that must be performed on the target Microsoft Internet Information Services (IIS) server before the destination computer can receive the Visual InterDev project that the Deploy feature sends it.
 * 1) Verify if the Posting Acceptor is installed on the target server.
 * 2) To install the Posting Acceptor 2.0, insert CD1 or CD2 of your Microsoft Visual InterDev or Microsoft Visual Studio setup discs in your CD-ROM or DVD-ROM drive and then run Pasetup.exe from the Deploy folder.
 * 3) Create a folder to receive the Visual InterDev project. This folder must have the following attributes:
 * 4) * Visible in IIS
 * 5) * Marked as an application in IIS
 * 6) * Granted Write access in IIS
 * 7) * Granted Write access in NTFS

back to the top

Prepare the Project Folder Permissions
To create a folder that contains the attributes listed earlier, follow these steps:
 * 1) In Microsoft Windows Explorer, create the folder to which you can deploy the Visual InterDev project.
 * 2) In Windows Explorer, right-click the newly created folder and then click Properties.
 * 3) On the Security tab, grant Write permissions to the account that you plan to use.

NOTE: If this folder is on a FAT volume, no Security tab appears, and this step is not required.
 * 1) Open Internet Services Manager in one of the following ways:
 * 2) * In Windows NT 4.0, click Start, click Programs, click Windows NT 4.0 Option Pack, click Microsoft Internet Information Server, and then click Internet Service Manager.
 * 3) * In Windows 2000, click Start, click Programs, click Administrative Tools, and then click Internet Services Manager.
 * 4) In Internet Services Manager, right-click the target Web site, click New, and then click Virtual Directory.
 * 5) Complete the wizard to create a new virtual directory that points to the target directory. This makes the Visual InterDev project folder visible in IIS and marks the Visual InterDev project folder as an application in IIS.
 * 6) In Internet Services Manager, right-click the virtual directory and then click Properties.
 * 7) On the Virtual Directory tab, in the Access Permissions section, click to select the Write access check box to grant Write permissions to IIS.

NOTE: NTFS and IIS Write permissions can present a significant security issue. To reduce this security threat, turn on these Write permissions just before deployment, and then turn off these Write permissions just after deployment.

back to the top

Use Visual InterDev to Deploy Web Applications

 * 1) Open an existing Web project in Visual InterDev.
 * 2) From the Project menu, click New Deployment Target, and then type the Uniform Resource Locator (URL) of the destination directory.

NOTE: The URL must be a fully-qualified URL to your target server (for example, http:/// ).
 * 1) If you want to add more destinations, repeat step 2.
 * 2) From the Project menu, in the Deploy submenu, select one of the destinations that you added in step 2.

This copies your project to the destination.

back to the top

Additional Features
 Update object tags:

In the Deployment Explorer window, right-click the entry for the deployment target, and then click Deployment Target Settings. The check box to modify deployed pages indicates whether Visual InterDev must examine your HTML pages for  and  tags during deployment. If you select this check box, these tags are updated to point to the new locations of these objects on the destination server. Add other files:

In the Deployment Explorer window, expand the deployment target, right-click Web content, controls, and applets, click Add Files, and then add any files that are not located in the project folder. When this project is deployed, these additional files are copied to the Web application folder on the target server. Server components:

A description of how you can use the Deploy feature to install server components, generally dynamic-link libraries (DLLs) on the remote server, is beyond the scope of this article. However, the following two items must occur when you place server components on a remote server:

 Most DLLs require other files called dependent files or dependencies. The Deploy feature in Visual InterDev does not copy these other files. If the remote server does not already have these files, install the server components separately with an installation or setup program. For Visual Basic DLLs, you can use the Visual Basic Package and Deployment Wizard to create a setup program. If the server component is already in use on the destination server, the actual file (such as Abc.dll) is locked and is in use by the IIS Admin Service on the destination server. The actual file cannot be replaced with a new copy while it is locked. To unlock the file, you must stop the IIS Admin Service on the destination server. You must then restart the IIS Admin Service for the Deploy feature to work because the Deploy feature uses this service as part of its mechanism to copy files to the destination server.</li></ul>

For detailed information about how to use the Deploy feature to install server components on the remote server, visit the "References" section.</li></ul>

back to the top

<div class="references_section">