13. What is the need of Copy Web Site?
Copy Web Site is a tool used to deploy the Web site by copying its content files. The Copy Web Site tool also checks whether or not the latest version of a file is present at the destination. If files of the most recent version are found at the destination, then the Copy Web Site tool does not superimpose the older version of files. The Copy Web Site deployment tool consists of the following main entities:
Project source – Specifies the source directory, which contains the contents and references of a Web site at development time. In simple words, you can say that the project source specifies the site that you currently have opened in Visual Studio 2010. The Copy Web Site tool picks all the files for deployment from this location.
Project destination – Specifies the destination folder where you have to deploy the application. This destination directory can be placed on remote computers or servers, which allow you to copy the Web site contents using the Front Page Server Extensions, FTP, or HTTP protocol implementations for content transfer.
Synchronizing two Web sites – Synchronizes two Web sites by copying each other’s files. Synchronization checks the files on the local and remote sites and ensures that all files on both sites are up to date.
14. What is the use of the Copy Project command?
The Copy Project command copies only the files required to run the project and pastes it on the target server. It does not deploy the complete project; therefore, IIS directory settings are not automatically configured.
15. Can Windows applications and the Web applications be deployed using the same template of Setup and Deployment project?
No. the Windows applications use the Setup Project template; whereas, the Web applications use the Web Setup Project template. After the deployment, their installation takes place in the similar way.
16. Explain the .NET Framework deployment features.
In a general context, .NET Framework includes the following deployment features:
No-impact applications – Provides application isolation and removes DLL conflicts.
Private components by default – Enables the components to deploy to the application directory and to be visible only to the containing application.
Side-by-side versioning – Enables you to select one of the multiple versions.
XCOPY deployment and replication – Refers to the self-descriptive application that is deployed without the need to store registry entries.
On-the-fly updates – Allows for the updating of the DLLs of the remote computers.
Integration with the Microsoft Windows Installer – Makes the features, such as advertising, publishing, repairing, and install-on-demand available during deployment of an application.
Enterprise deployment – Eases the task of software distribution.
Downloading and caching – Specifies that the downloads are kept smaller and the components are isolated for application use.
Partially trusted code – Enables code-based identification.