MSDN Magazine - March 2008 - (Page 36)

Figure 4 Deploying an Assembly with SolutionConfig.xml 24F91DED-8BA7-4633-8BA0-4C9B2A4387D7 HelloWorld True True itself and any assemblies that should be deployed inside the solution package. Therefore, STSDEV has been designed to generate an XML metadata file named SolutionConfig.xml and to read the contents of this file any time it regenerates manifest.xml and SolutionPackage.ddf. The most basic version of a SolutionConfig.xml file looks like the following: 24F91DED-8BA7-4633-8BA0-4C9B2A4387D7 HelloWorld True False As you can see, the SolutionConfig.xml file tracks the GUID with the solution ID, the solution name, and a Boolean value named ResetWebServer that is used add the instruction in manifest.xml that controls whether WSS will run IISRESET on each front-end Web server after the output solution package has been deployed, upgraded, Figure 5 Custom Build Targets or retracted. Target Description SolutionConfig.xml also contains an DebugBuild After building the debug version of the project’s output assembly DLL, this element named AssemblyDeployment command refreshes the solution’s deployment files and then builds the output that is read by the RefreshDeploymentsolution package .wsp file using MAKECAB.EXE. Files command. This is used to add DebugInstall This command installs the solution package .wsp file into the solution package configuration about one or more of store of the local farm using the STSADM –addsolution operation. the assemblies that need to be deployed DebugDeploy This command deploys the solution package in the farm using the STSADM in the output solution package along –deploysolution operation. with the required assembly configuDebugUpgrade This command upgrades the solution package using the STSADM ration information. –upgradesolution operation. For example, if you created the HelDebugQuickCopy This command performs a simply copy command to copy the contents of the loWorld project by selecting Empty solution’s RootFiles folder into the WSS RootFiles directory of the local Web server. Solution (C# assembly), then the iniDebugRetract This command retracts the solution package from the farm using the STSADM –retractsolution operation. tial state of the SolutionConfig.xml DebugDelete This command deletes the solution package .wsp file from the solution package file would look like the one shown in store of the local farm using the STSADM –deletesolution operation. Figure 4. The binary file and metadata ReleaseBuild After building the release version of the project’s output assembly DLL, this information would then be added into command refreshes the solution’s deployment files and then builds the output manifest.xml and SolutionPackage.ddf solution package .wsp file using MAKECAB.EXE. for assembly deployment. Figure 6 Microsoft.SharePoint.targets HelloWorld.wsp HelloWorld.wsp Creating Custom Build Targets with MSBuild Instead of using batch files, STSDEV leverages the capabilities of MSBuild to create custom build targets that can be integrated into Visual Studio solutions. In particular, STSDEV creates a file named Microsoft.SharePoint.targets in the DeploymentFiles folder that contains custom build targets. This makes it possible to create each new solution with a complete set of commands commonly used in SharePoint development. Figure 5 provides a list of the custom build targets generated for each new project. Note that the use of custom build targets brings up security issues. Visual Studio warns you whenever you open a project or solution with custom build targets to protect developers against unexpected attacks. Therefore, when you open a project created with the STSDEV utility for the first time, you should expect to see the security warning. This is a good time for me to drill into the contents of the Microsoft.SharePoint.targets file. If you open this file, you should see 36 msdnmagazine Office Space

Table of Contents Feed for the Digital Edition of MSDN Magazine - March 2008

MSDN Magazine - March 2008 Contents Toolbox CLR Inside Out Data Points Advanced Basics Office Space Introducing ASP.NET MVC Loosen Up CI Server Performance Office Development Test Run Security Briefs Extreme ASP.NET Foundations .NET Matters {End Bracket}

MSDN Magazine - March 2008

For optimal viewing of this digital publication, please enable JavaScript and then refresh the page. If you would like to try to load the digital publication without using Flash Player detection, please click here.