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
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.
- Verify if the Posting Acceptor is installed on the target server.
- 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.
- Create a folder to receive the Visual InterDev project. This folder must have the following attributes:
- Visible in IIS
- Marked as an application in IIS
- Granted Write access in IIS
- Granted Write access in NTFS
Prepare the Project Folder Permissions
To create a folder that contains the attributes listed earlier, follow these steps:
- In Microsoft Windows Explorer, create the folder to which you can deploy the Visual InterDev project.
- In Windows Explorer, right-click the newly created folder and then click Properties.
- 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.
- Open Internet Services Manager in one of the following ways:
- 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.
- In Windows 2000, click Start, click Programs, click Administrative Tools, and then click Internet Services Manager.
- In Internet Services Manager, right-click the target Web site, click New, and then click Virtual Directory.
- 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.
- In Internet Services Manager, right-click the virtual directory and then click Properties.
- 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.
Use Visual InterDev to Deploy Web Applications
- Open an existing Web project in Visual InterDev.
- 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://<destination Web server name>/<destination folder name>).
- If you want to add more destinations, repeat step 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.
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 <APPLET> and <OBJECT> 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.
REFERENCES
For more information, visit the following MSDN Web sites:
Solution Deployment Common Tasks
http://msdn.microsoft.com/library/devprods/vs6/vstudio/vstool1/veovrSolutionDeploymentCommonTasks.htm
Solution Deployment Reference
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vstool1/html/veovrsolutiondeployreference.asp
Publishing a Microsoft Access-Driven Web Site Using Visual InterDev
http://msdn.microsoft.com/library/techart/vi_acc.htm
For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base:
246757 HOWTO: Use Copy Web to Deploy a Web Application
205696 How to Install FrontPage 2000 Server Extensions for Internet Information Server
241724 HOWTO: Deploy Only Selected Files to a Remote Server with the Visual InterDev 6.0 Deployment Feature
220841 PRB: Error "Failed to Deploy a File (Xx.asp): You Do Not Have Write Access to Destination URL"
220843 PRB: Deployment or New Deployment Target Creation Brings Error
220839 PRB: Web Deployment Results in "Failed to Deploy" Error
238566 PRB: Visual InterDev Fails to Deploy Projects to Remote Server with Posting Acceptor 2.0
276211 INFO: Some Editions of Visual InterDev Omit Deployment Feature
Keywords: kbhowto kbhowtomaster kbwebserver kbserver kbdeployment KB219050
