The deployment method at the heart of these tutorials is based on the split project file approach described in Understanding the Project File, in which the build process is controlled by two project files-one containing build instructions that apply to every destination environment, and one containing environment-specific build and deployment settings. This tutorial series uses a sample solution-the Contact Manager solution-to represent a web application with a realistic level of complexity, including an ASP.NET MVC 3 application, a Windows Communication Foundation (WCF) service, and a database project. This topic forms part of a series of tutorials based around the enterprise deployment requirements of a fictional company named Fabrikam, Inc. This topic will show you how to run Windows PowerShell scripts both locally and remotely from a custom target in a Microsoft Build Engine (MSBuild) project file. Configure replication between SQL Server instances.Create user accounts with the appropriate permissions.Send emails inviting users to a newly provisioned web application.Generate a file system directory for uploads.Add a custom event source to the registry.There are lots of reasons why you might want to run a post-deployment Windows PowerShell script. You can run a script locally (in other words, on the build server) or remotely, like on a destination web server or database server. This topic describes how to run a Windows PowerShell script as part of a build and deployment process.
0 kommentar(er)
