Right-click the solution, point to Add, and then click New Solution Folder. Rename the folder Solution.
Select the new solution folder.
Right-click the new solution folder, point to Add, click New Item, and then select XML File in the dialog box. Rename the XML file to Manifest.xml. Click Add.
Specifying the DeploymentTarget attribute indicates that you want your DLL to be installed to the global assembly cache when the solution is deployed.
Note:
You can add the Wss.xsd schema to the schemas for this blank XML file. This will provide you with IntelliSense and validation while you are editing the Manifest.xml file.
It is important to point out that both the Feature.xml and the Workflow.xml files must be put into a folder inside the solution package file. You do this by separating the source file and the destination with a space and then specifying a folder directory for the destination."VS 2008 Expense Report WF Alpha\feature.xml" ExpenseFeature\feature.xml"VS 2008 Expense Report WF Alpha\workflow.xml" ExpenseFeature\workflow.xml
Note:
It is also important that you add your Custom Task form to this solution package."VS 2008 Expense Report WF Alpha\ExpenseReportApprovalForm.xsn" ExpenseFeature\ExpenseReportApprovalForm.xsn
Creating the Solution Package
You are now ready to create the solution package. You need the Makecab.exe tool to create the solution package. If you do not have it on your computer, you can find it here: Microsoft Cabinet Software Development Kit.
To create the solution package
Open a command prompt, and navigate to the solution directory.
Run the following command to build the Solution.ddf file:
makecab /f Solution.ddf
You now have a solution package in your solution directory.
Figure 1. Solution Package .wsp File
Deploying the Solution Package
Now that you have a solution package, you have to deploy it. You must have the Stsadm.exe tool to deploy the solution package.
To deploy the solution package
Open a command prompt and navigate to the directory that contains the Stsadm.exe tool.
Run the following command to add your solution to a SharePoint server.
Now that your solution has been added to the SharePoint server, you must deploy that solution. Although you can deploy the solution using the SharePoint Server user interface (UI), you will use the command line in this scenario.
Your workflow has now been successfully deployed and activated on your SharePoint server. You can now navigate to your SharePoint site and add this workflow to a Document Library.
Figure 2. Installed Workflow
Creating a solution package enables you to deploy your Feature to other servers. This is useful when you have a development server and one or more production servers. Creating the solution package requires that you use the Stsadm.exe and the Makecab.exe utilities. For links to more information about these utilities, see the "Explore It" section.