Figure 11-23: Package Designer s Advanced view showing additional assemblies in VS .NET

Making QR Code in VS .NET Figure 11-23: Package Designer s Advanced view showing additional assemblies
Figure 11-23: Package Designer s Advanced view showing additional assemblies
Create Quick Response Code In Visual Studio .NET
Using Barcode encoder for VS .NET Control to generate, create QR Code image in .NET framework applications.
The SharePoint Project Structure in Visual Studio
QR Code Recognizer In VS .NET
Using Barcode decoder for .NET framework Control to read, scan read, scan image in Visual Studio .NET applications.
You can add additional assemblies to the package from the advanced view of the Package Designer If you click the Add button you are presented with two options: Add Existing Assembly and Add Assembly from Project Output The Add Existing Assembly dialog shown in Figure 11-24 allows you to add an existing assembly to the package
Bar Code Drawer In Visual Studio .NET
Using Barcode creator for VS .NET Control to generate, create barcode image in Visual Studio .NET applications.
Figure 11-24: Add Existing Assembly dialog
Recognize Bar Code In .NET
Using Barcode decoder for Visual Studio .NET Control to read, scan read, scan image in VS .NET applications.
From this dialog you can specify the desired assembly and where you want to deploy it You can also register safe controls and add class resources that are in the selected assembly The dialog for adding an assembly from the project output shown in Figure 11-25 is very similar to the previous dialog The only difference is that instead of having an option to browse to an existing assembly, you have the option to select a project from your current solution The output assembly of the selected project is then added to the package Just as with existing assemblies you can also specify the safe controls as well as class resources
QR-Code Maker In Visual C#
Using Barcode generation for .NET Control to generate, create QR Code image in .NET applications.
11: Packaging and Deployment
Denso QR Bar Code Drawer In Visual Studio .NET
Using Barcode printer for ASP.NET Control to generate, create QR Code 2d barcode image in ASP.NET applications.
Figure 11-25: Add Assembly from Project Output dialog
Making QR Code 2d Barcode In Visual Basic .NET
Using Barcode creation for VS .NET Control to generate, create Quick Response Code image in VS .NET applications.
Any changes made from this part of the designer are reflected in the package manifest file (Manifestxml) As in Feature Designer, the Package Designer gives you an option to fully control the package manifest without the designer If you click the Manifest tab the designer changes to the view shown in Figure 11-26 You have two options for updating the package manifest You can either enter the package manifest XML elements into the provided textbox and the XML you type is merged with the XML generated by the Package designer The other advanced option is to overwrite the generated package manifest by clicking the link: Overwrite generated XML and edit manifest in the XML editor If you decide to do this, you will be able to control the Manifestxml package manifest file directly and change it to your liking and requirements However, if you decide to go back and re-activate the Package designer, all the changes you made in the Manifestxml package manifest will get overwritten
Drawing Code39 In .NET Framework
Using Barcode generation for Visual Studio .NET Control to generate, create Code 39 image in .NET applications.
Configurable Deployment
Bar Code Maker In Visual Studio .NET
Using Barcode generation for .NET Control to generate, create barcode image in .NET applications.
Figure 11-26: Manifest view
ECC200 Generation In VS .NET
Using Barcode generator for VS .NET Control to generate, create Data Matrix 2d barcode image in Visual Studio .NET applications.
Configurable Deployment
Encoding EAN 13 In .NET Framework
Using Barcode maker for .NET Control to generate, create GTIN - 13 image in .NET applications.
Deployment of SharePoint projects from Visual Studio is done with the help of configurable deployment Configurable deployment lets you configure the way SharePoint projects are deployed and retracted from the server Visual Studio 2010 ships with two deployment configurations: default deployment and no activation deployment Before we explain what the difference is between these two we should look at the deployment configuration structure Figure 11-27 shows how deployment configuration is structured Each deployment configuration consists of two parts: deployment and retraction When a SharePoint project is deployed Visual Studio executes a series of deployment steps in a specific order Something similar happens when you retract the project Retraction steps are executed in a specific order Both parts (deployment and retraction) are built from steps Since
UPCE Generation In Visual Studio .NET
Using Barcode printer for Visual Studio .NET Control to generate, create UPC-E Supplement 2 image in Visual Studio .NET applications.
11: Packaging and Deployment
Code 128 Encoder In .NET
Using Barcode maker for ASP.NET Control to generate, create Code-128 image in ASP.NET applications.
Figure 11-27: Deployment configuration structure
Code 128 Code Set B Recognizer In Visual Studio .NET
Using Barcode reader for .NET Control to read, scan read, scan image in .NET applications.
deployment is configurable you can use zero, one, or multiple steps for both the deployment and retraction parts of the configuration You can also control the order in which steps are executed Let s start at the steps level and move up the hierarchy Visual Studio ships with a number of reusable deployment steps shown in Table 11-10 You can use these steps to build your own deployment configuration
Draw Bar Code In .NET
Using Barcode creator for ASP.NET Control to generate, create barcode image in ASP.NET applications.
TABLE 11-10: Deployment Steps
Printing EAN-13 Supplement 5 In Java
Using Barcode generator for Java Control to generate, create EAN-13 image in Java applications.
Step Run Pre-Deployment Command
Code 39 Creation In Java
Using Barcode printer for Java Control to generate, create USS Code 39 image in Java applications.
Description Specifies a command that gets called before the deployment of the SharePoint project starts; you can use MS-DOS or MSBuild commands Specifies a command that gets called after the SharePoint project is deployed; you can use MS-DOS or MSBuild commands When executed it will recycle the IIS application pool
Bar Code Creation In Visual Basic .NET
Using Barcode creation for .NET framework Control to generate, create bar code image in VS .NET applications.
Run Post-Deployment Command
Reading Bar Code In Java
Using Barcode reader for Java Control to read, scan read, scan image in Java applications.
Recycle IIS Application Pool Retract Solution Add Solution Activate Features
EAN 13 Scanner In .NET Framework
Using Barcode reader for .NET Control to read, scan read, scan image in .NET applications.
Retracts the SharePoint solution from the server Adds the SharePoint solution to the server Activates the features on the SharePoint server
Configurable Deployment
When you create any SharePoint project the active deployment configuration is set to the built-in deployment configuration Default Deployment The numbered list shows the steps and the order in which they are performed when the SharePoint project is deployed using the default deployment configuration: 1 Run Pre-Deployment Command 2 Recycle IIS Application Pool 3 Retract Solution 4 Add Solution 5 Activate Features 6 Run Post-Deployment Command The list of retraction steps in the default deployment configuration is much shorter and it looks like this: 1 Recycle IIS Application Pool 2 Retract Solution The built-in deployment configuration, No activation deployment, is very similar to the default deployment The only difference is that when using No activation deployment, the Activate Features step is not performed All the other steps and their order are identical If you have read the previous chapters you probably remember that we used No activation deployment when we were debugging feature event receivers As explained in 5, SharePoint Event Receivers, in order to debug the FeatureActivated event we had to deploy it without activating it We used the No activation deployment to deploy the feature event receiver and when we activated the feature from the SharePoint UI, the breakpoint in the FeatureActivated event was hit Switching between the default and no activation deployment configurations can be done in two places in the Visual Studio UI The most common place to change the active deployment configuration is in the Properties window If you click the project name in the Solution Explorer