Category Archive for: Deployment

ClickOnce is a deployment technology that allows applications to be self-updating. Applications are published to a file share, Web site, or media such as a CD. Once published, ClickOnce apps can be automatically updated with minimal user input. ClickOnce also solves the security permission problem. Normally, to install an application the user would need Administrative rights. With ClickOnce…

Xcopy deployment can be easy to use, but there are times when the lack of functionality becomes an issue. To overcome this shortcoming, Visual Studio 2008 has six installer project types. Four of these options are based on the Windows Installer technology. The following table lists the project types. Setup and Web Setup Projects are very similar.…

If deployment is part of an application’s original design considerations, deployment can be as simple as copying a set of files to the target computer. For a Web application, it can be a simple menu choice in Visual Studio 2008. This section discusses these simple deployment scenarios . To see how the various deployment options are…

When an application is developed using .NET,there is a dependency on the .NET runtime. This may seem rather obvious, but sometimes the obvious can be overlooked. If the application does not use any .NET3.0 features, then dotnetfx. exe (netfx64. exe for 64 bit OS) will be the only runtime installation required. If .NET 3.0 features are used, then…

It is instructive to look at the runtime requirements of a .NET-based application. The CLR does have certain requirements on the target platform before any managed application can execute. The first requirement that must be met is the operating system. Currently, the following operating systems can run .NET-based applications: Windows 98 Windows 98 Second Edition (SE) Windows…

This section provides an overview of the deployment. options that are available to .NET developers. Most of these options are discussed in greater detail later in this chapter. Xcopy The xcopy utility enables you to copy an assembly or group of assemblies to an application folder, cutting down on your development time. Because assemblies are self-discovering (that…

Often, deployment is an afterthought in the development process that can lead to nasty, if not costly, surprises, To avoid grief in deployment scenarios, the deployment process should be planned out during the initial design stage. Any special deployment considerations – such as server capacity, desktop security, or where assemblies will be loaded from – should be built…

The development process does not end when the source code is compiled and testing is complete. At that stage, the job of getting the application into the user’s hands begins. Whether it’s an ASP.NET application, a smart client application, or an application built using the Compact Framework, the software must be deployed to a target environment. The .NET…