Microsoft SharePoint Power User Cookbook Download PDF, Microsoft SharePoint Power User Cookbook Full Collection, Read Best Book Online . caite.info Online Source Download and Free Ebook PDF Manual Reference. Microsoft-sharepointpower-user-cookbook-colquhoun-adrian. We present Microsoft Sharepoint Power User Cookbook Colquhoun document imaging solutions comparison chart nuance power pdf pdf solution.
|Language:||English, Spanish, Japanese|
|ePub File Size:||27.47 MB|
|PDF File Size:||14.14 MB|
|Distribution:||Free* [*Regsitration Required]|
A book and eBook containing over 70 advanced recipes for expert End Users to unlock and apply the value of Microsoft SharePoint Popular ebook that must definitely be read right now is Microsoft Sharepoint. Power User Cookbook Colquhoun Adrian Ebook PDF I am sure you will. Microsoft SharePoint Development Cookbook Over 45 recipes to take you from caite.info, you can use this to access PacktLib today and view nine Suggested are the Visual Studio SharePoint Power Tools, especially if .
To explore Features from the physical implementation perspective, we need to examine the SharePoint installation folder. For now, let us get this tool installed into your virtual environment. This is a good time to actually take a snapshot of your virtual machine or back it up , as this can be a good a starting point if in the future you have to set up another separate development machine. Along the way, we are introduced to the workflow form types—Association, Initiation, and Task Edit. Now carry out the following: The Edit page is shown in the following screenshot:
What do I get with a Packt subscription? What do I get with an eBook? What do I get with a Video? Frequently bought together. Learn more Add to cart. Paperback pages. Book Description The power of Microsoft SharePoint as the Enterprise collaboration platform is ever-growing; due to the wide range of capabilities it offers, SharePoint can help transform your business so you can quickly respond to the changes and challenges that you face.
Table of Contents Chapter 1: Getting Started—SharePoint Essentials. Tagging a SharePoint page so I can find it again later. Reviewing the tags and notes other users have posted on a SharePoint page. Checking another user's permissions in a SharePoint site.
Chapter 2: Adding a slide to a presentation from a SharePoint slide library.
Creating a SharePoint contact list and connecting it to Outlook Chapter 3: Creating a term set using the managed metadata service. Chapter 4: Creating an alert on a document to be notified when it is updated. Requiring users to check out a document before they can edit it. Use content types to store different types of document in the same document library. Chapter 5: Using web analytics to see which are the most popular pages on your site.
Chapter 6: Where's My Stuff? Saving a search as an alert and being notified when the results change. Using search analytics to see what people are searching for. Chapter 7: Creating a chart using the PerformancePoint Dashboard Designer. Building a PerformancePoint business intelligence dashboard. Chapter 8: Creating a holiday request InfoPath form and publishing it to a form library. Using the Collect Feedback workflow toreceive feedback on a Microsoft Word document.
Creating a list workflow using SharePoint Designer Using Microsoft Visio to model a SharePoint workflow. What You Will Learn Quickly move through some essential SharePoint End User tasks before moving on to more advanced functionality Take a deep dive into SharePoint document management Learn from a comprehensive treatment of SharePoint workflows Understand who is listening to your information with SharePoint Web Analytics tools Create and publish InfoPath forms to front-end your business processes Discover the SharePoint security trimmed user interface from a practical business perspective Understand SharePoint search and how to find things more easily Turn data into information using SharePoint's powerful business intelligence tools Unlock the true business value of SharePoint with HR, CRM, and PM composite application examples Understand how to apply your SharePoint knowledge to "Think SharePoint" rather than simply grasping basic SharePoint concepts.
Authors Adrian Colquhoun. He has been building enterprise software applications for more than 13 years and has been working with SharePoint since His multiple roles as business owner, Consultant, Developer, Trainer, and SharePoint End User give him a unique insight to pass on as an author. Read More. Read More Reviews. Recommended for You. Microsoft SharePoint Developer's Compendium: Expert Cookbook.
As a new user, these step-by-step tutorial guides will give you all the practical skills necessary to become competent and efficient. Beginner's Guide. Friendly, informal tutorials that provide a practical introduction using examples, activities, and challenges. Fast paced, concentrated introductions showing the quickest way to put the tool to work in the real world.
A collection of practical self-contained recipes that all users of the technology will find useful for building more powerful and reliable systems. Guides you through the most common types of project you'll encounter, giving you end-to-end guidance on how to build your specific solution quickly and reliably.
Give this a try and see if it works as equally well as a paid version of VMware. With your selected virtualization technology in hand, head to the next section to install and configure Windows Server R2, which is the base operating system required for an installation of SharePoint Server In this recipe, we will configure the components of Windows Server necessary in order to get ready to install SQL Server and SharePoint This book does not cover actually installing the base operating system.
The specific instructions to do so will be dependent upon the virtualization software selected as per the Selecting your virtual environment recipe. Generally, it will be provided as an ISO image the file extension will be. This means that when you elect to create a new virtual machine, you will normally be prompted for the ISO image, and the installation of the operating system should proceed in a familiar and relatively automated fashion.
So for this recipe, ready means that you have your virtualization software up and running, the Windows Server R2 base operating system is installed, and you are able to log in as the Administrator and that you are effectively logging in for the first time.
How to do it Log in as the Administrator. You will be prompted to change the password the first time—I suggest choosing a very commonly used Microsoft password—Password1. However, feel free to select a password of your choice, but use it consistently throughout this chapter.
The Initial configuration tasks screen will come up automatically. On this screen: Activate windows using your day trial key or using your MSDN key. Select Provide computer name and domain. Change the computer name to a simpler one of your choice. Leave the Member of option as Workgroup. The computer will require a reboot. In the Update this server section, choose Download and install updates.
Click on the Change settings link and select the option Never check for updates and click OK. Click the Check for updates link. The important updates will be selected. Click on Install Updates. Now is a good time for a coffee break! You will need to reboot the server when the updates complete. In the Customize this server section, click on Add Features. Choose Add Required Features when prompted to do so.
Reboot the server when prompted to do so. If the Initial configuration tasks screen appears now, or in the future, you may now select the checkbox for Do not show this window at logon. We will continue configuration from the Server Manager, which should be displayed on your screen. If not, launch the Server Manager using the icon on the taskbar. Click on Configure Remote Desktop if you have a preference for accessing your virtual machine using Remote Desktop RDP instead of using the virtual machine's console software.
Click on the Windows Firewall Properties link. Set both options to Off and click OK. From the Server Manager, expand the Configuration node and then expand Local Users and Groups node, and then click on the Users folder. Right-click on the Administrator account and select Properties. Select the option for Password never expires and click OK. From the Server Manager, click the Roles node. Click the Add Roles link. Click Next, again click on Next, and then click Install.
Now, carry out the following steps: This is completely internal to your development server and does not have to be real. For book purposes, I am using theopenhighway. Then click Next: Select Yes on the Static IP assignment screen.
Click Yes on the Dns Delegation Warning screen. Click Next. Otherwise reboot the server after the installation completes. You will now configure a user account that will run the application pools for the SharePoint web applications in IIS. From the Server Manager, expand the Roles node. Click on the Users folder.
Now carry out the following: Deselect the option for User must change password at next logon and select the option for Password never expires. Click Next and then click Finish. A loopback check is a security feature to mitigate against reflection attacks, introduced in Windows Server SP1.
You will likely encounter connection issues with your local websites and it is therefore universally recommended that you disable the loopback check on a development server. This is done from the registry editor: The Windows Shutdown Event Tracker is simply annoying on a development machine. To turn this feature off, click the Start button, select Run…, enter gpedit.
Select the Disabled option and click OK, as shown in the following screenshot: The content that you plan to manage in SharePoint, including web content and documents, literally is stored within and served from SQL Server databases. The SharePoint architecture itself relies on information stored in SQL Server databases, such as configuration and the many service applications. Getting ready I do not recommend SQL Server Express for your development environment, although this is a possible, free, and valid choice for the installation of SharePoint In my personal experience, I have valued the full power and flexibility of the full version of SQL Server as well as not having to live with the constraints and limitations of SQL Express.
Besides, there is another little reason too! If you download your SQL Server from the Microsoft site as a trial, extract the software it is a self-extracting EXE on your local machine, and then share the folder with your virtual machine. Finallly, run the Setup. Carry out the following steps to complete this recipe: You will be presented with the SQL Server Installation Center; on the left side of the screen, select Installation, as shown in the following screenshot: For the choices presented on the Installation screen, select New installation or add features to an existing installation.
The Setup Support Rules shown in the following screenshot will run to identify any possible problems that might occur when installing SQL Server. All rules should pass. Click OK to continue: On the first screen, you can select an evaluation or use your product key from, for example, MSDN and then click Next. Accept the terms in the license, but do not check the Send feature usage data to Microsoft checkbox, and click Next. On the Setup Support Files screen, click Install.
All tests will pass except for a warning that you can safely ignore the one noting we are installing on a domain controller , and click Next, as shown in the following screenshot: On the Feature Selection, as shown in the following screenshot, carry out the following tasks: On the Installation Rules screen, click Next On the Instance Configuration screen, click Next.
On the Disk Space Requirements screen, click Next On the Server Configuration screen: On the Database Configuration Engine screen: On the Analysis Services Configuration screen: On the Reporting Services Configuration screen, select the option to Install but do not configure the report server. Now, click Next. On the Error Reporting Screen, click Next. On the Installation Configuration Rules screen, click Next. On the Ready to Install screen, click Install.
Your patience will be rewarded with the Complete screen! Finally, click Close. The Complete screen is shown in the following screenshot: Click the check names button and then click OK.
Installing and configuring SharePoint Server We are ready to get to the main event of the chapter! In this recipe, we deal with the installation and configuration of SharePoint itself. Getting ready Download SharePoint Server from your MSDN subscription, or type in sharepoint server trial download into your favorite search engine to download the day trial from the Microsoft site.
There are a few pre-requisites that need to be in place before the actual installation of SharePoint So, let us prepare a few ingredients for our recipe in advance. From Internet Explorer in the virtual machine: Use your favorite search engine to find ado. Look for the Download Details link, which should be the first result on the Microsoft site. Look for the x64 version and download it from the Microsoft site to the desktop of the virtual machine.
Now, launch the installation. Click Yes when prompted with Do you want to install the following Windows software update? It is now time for our second coffee break. Click Close after the Installation Complete screen appears. We are nearly there!
We are going to get into the SharePoint setup in order to install the required pre-requisites. If you downloaded it from Microsoft as a trial, download it to your virtual machine settings and sharing a folder from the host machine.
Double-click the EXE file to launch the installation. Ensure your virtual machine has internet connectivity test by using Internet Explorer to navigate to http: Run Splash. Installing the SharePoint pre-requisites: Click on the Install Software Prerequisites link. Once you click on this link, you will see the following screen: It is now time for our third coffee break. Watch for any prompts to reboot the server. On the Installation Complete screen, click Finish. Now, let's get to the main recipe for which you have patiently been waiting for!
Here is your recipe to install SharePoint From the virtual machine CD Drive, run Splash. Click on the Install SharePoint Server link. On the Read the Microsoft Software License Terms screen, select the checkbox I accept the terms of this agreement and click on Continue.
On the Choose a file location screen, click Install Now. The Installation Progress screen will show the proceeding of the installation. Fourth coffee break? You might want to consider switching to decaf.
This is a good time to actually take a snapshot of your virtual machine or back it up , as this can be a good a starting point if in the future you have to set up another separate development machine. Click Yes to the warning regarding services that may need to be restarted. On the Connect to a Server Farm screen, choose the option to Create a new server farm and click Next.
On the Specify Farm Security Settings screen, choose a passphrase of Password1 or the same as you have used for the Administrator account and click Next. On the Configure SharePoint Central Admin Web Application Page, select the checkbox Specify port number and enter the value or a different port number of your preference.
You are probably sick of coffee by now. Please take the time to check your e-mail, voice messages, Facebook, Twitter, and Linked In. On the Configuration Successful screen, click Finish. Internet Explorer will open and navigate to the adminconfigintro. On the How do you want to configure your SharePoint farm? You are almost there! Reward yourself with a quick online match in your favorite game on your favorite console while you wait for the configuration to complete.
The wizard will have created a web application using the machine name, in my case, http: You now get to create your very first Site Collection. Choose a title based on your company name in my case, The Open Highway , choose the Team Site template and click OK, as shown in the following screenshot: Your hard and patient work is rewarded with the This completes the Farm Configuration Wizard screen!
Breathe deeply. Refresh the browser. There is your Team Site.
The following screenshot shows my Team Site: You have successfully installed and configured SharePoint Server and are ready for our next step — to install Microsoft Office and your development tools. There's more If you are prompted with the following screen with the Install Microsoft Silverlight link, then click on the link and take the opportunity now to install it! The user interface of SharePoint relies on Silverlight in many cases: Installing Microsoft Office Professional SharePoint is tightly integrated with, and was specifically designed to exploit, Microsoft Office So Office is a key tool for you to leverage in your SharePoint solutions, such as Word, Excel, and so on.
Together with Visio and SharePoint Designer, these applications will be an important part of your development toolkit. Getting ready Download Microsoft Office Professional Plus from your MSDN subscription, or type in Microsoft office professional plus trial download into your favorite search engine to download the day trial from the Microsoft site. Wherever the software comes from, it will be presented as an EXE file. Make the file available to your virtual machine, for example, by going to your virtual machine settings and sharing a folder from the host machine.
Or you could choose to download the software directly to your VM environment. Here is the recipe to install Microsoft Office Professional Plus On the first screen, enter your product key either MSDN or trial key.
Accept the terms of the license agreement and click Continue. On the Choose the installation you want screen, click Customize. You can always install these later if you wish to experiment with these applications with SharePoint. Finally, click Install Now. Click Close when the installation completes. We want to take a moment to initialize Office. From the Windows Start menu, launch Microsoft Word.
Take the opportunity to activate Office if this has not been automatically done already. On the File tab in the ribbon, select Options. On the Word Options screen, select Trust Center on the left-hand side.
Click the Trust Center Settings button. On the Trust Center screen, select Protected View on the left-hand side, as shown in the following screenshot. Deselect the first three checkboxes and click OK twice: Close Microsoft Word. You have installed Microsoft Office Professional Plus Installing Visio Premium Here we will install Visio , and later in this book, we will exploit the key new capability to design SharePoint workflows.
Getting ready Download Visio Premium from your MSDN subscription, or type in visio premium trial download into your favorite search engine to download the trial from the Microsoft site. If you downloaded from Microsoft as a trial, make the file available to your virtual machine, for example, by going to your virtual machine settings, and sharing a folder from the host machine.
In this case, run VisioSingleImage. Here is the simple recipe to install Visio On the Choose the installation you want screen, click Install Now.
You have installed Visio Premium This is a powerful tool to create no-code solutions for SharePoint, but it is also a critical tool for the developer to exploit all of SharePoint's out-of-the-box capabilities before turning to code solutions in Visual Studio. Type sharepoint designer download into your favorite search engine to download the software. Make the file available to your virtual machine, for example, by going to your virtual machine settings, and sharing a folder from the host machine.
Otherwise, you could choose to download the software directly to your virtual machine environment. Here is the simple recipe to install SharePoint Designer You have installed SharePoint Designer Installing Visual Studio Visual Studio is, believe it or not, the very first version of Visual Studio to incorporate a complete set of SharePoint development tools—ones that we of the SharePoint development world have been longing for for many years.
You might overhear our excitement by murmuring "Wow! For those ASP. To which we might reply "But you don't understand!!! Anyway, I digress, this could be the subject of another whole chapter about what we used to have to deal with, which would add absolutely no value whatsoever to your task at hand today.
Suffice to say, Visual Studio is your primary SharePoint customization platform that you will discover as we go through the book. For now, let us get this tool installed into your virtual environment. Note that there is an option on the start page of Visual Studio to register the software and extend this trial for a further 60 days.
Run Autorun. Here is the recipe for installing Visual Studio Under the Help Improve Setup section, de-select Yes, send information about my setup experiences to Microsoft Corporation.
Click the Next button when it is available. Click I have read and accept the license terms and click Next. Under Select features to install, select the Custom option and click Next. Finally, click Install. It's probably been long enough now, so have another coffee break and enjoy! Click Finish when the installation completes and restart the server when prompted. When rebooted, you can exit the wizard. You have successfully installed Visual Studio How it works You may now realize the point which we are at.
I will put forward to you that by my experience, the most effective development platform for the SharePoint developer is a standalone virtual machine, where Visual Studio is installed within a full server-based installation of SharePoint Only time will tell whether you agree with me!
Start up Visual Studio and select your preferred environment settings I choose the settings for Visual C developer. Note the startup screen has the option of Extending Visual Studio for an additional 60 days , in case you are using a trial version. Installing recommended developer tools While Visual Studio certainly contains an excellent set of tools for the SharePoint developer, both Microsoft and the community at large are constantly providing you with further excellent sample code, utilities, and productivity aids.
In this section, I recommend three key tools that you should have, and will direct you to a location where you can find more! Here is the recipe for installing key SharePoint developer tools: Highly recommended is the SharePoint Guidance available at http: Highly recommended is the Community Kit for SharePoint.
It is a set of best practices, templates, Web Parts, tools, and source code that enables practically anyone to create a community website based on SharePoint technology for practically any group of people with a common interest.
It is available from http: Highly recommended is the SharePoint Manager tool. It is from http: You have successfully installed the key tools every SharePoint developer should have at hand. There are far too many excellent tools contributed by the community to be mentioned here, and more being created all the time. Some will be useful to accelerate some very specific development task. The primary source is CodePlex at http: Search the site for SharePoint , or more generally, SharePoint as some tools support both the current and older versions of SharePoint.
Setting up your first web application You are ready to start developing on SharePoint ! Well almost. I am going to strongly recommend a development approach for you. I ask for a moment of patience as I explain. The site collection in turn lives within a Web Application in IIS and that web application will have an associated content database literally, a SQL Server database that has been created to hold the content within the site collections of that web application.
You may also know this as the SharePoint containment hierarchy. Let's say that project is a new collaboration Intranet for the company The Open Highway. I want to host that on the URL http: So I'd like to create that very web application locally, including mimicking the URL I ultimately want to use.
That way, when I actually want to deploy my application, I'll be quite certain that it should operate perfectly well in the target environment. But why do I say your first web application? Did SharePoint not create for itself the first content database, web application, and site collection with a Team Site at its root?
Why, yes it did, located at a URL that is your machine name. In my case, that would have been http: And the clarification is that SharePoint created that. The key word here is your first web application. Use Windows Explorer to navigate to the directory C: Right-click on the Hosts file and select Open.
Copy and paste the three lines referring to the local intranet. Remove the hash marks from lines two and three and then replace the local host with your URL. The result will look as follows: Here is the recipe to create a new web application: From this screen, click on Manage Web Applications and the following screen will be displayed: In the ribbon, click on the New button. Fill in the screen similarly to the following screenshot. Choose your own name for the web application.
Scroll down the window. As shown in the following screenshot, in the Application Pool section, select the Use existing application pool and select the one that begins with SharePoint — In the Database Name and Authentication sections, change that unusably ugly GUID at the end of the database name to something meaningful. Scroll down to the bottom of the window. Leave all the remaining settings at their default and click OK. Please wait while your changes are processed.
Truer words have never been spoken. Please wait patiently until you see the Application Created screen. Click on the Create Site Collection link, as shown in the following screenshot: Scroll to the bottom of the window, enter the Administrator account as the Primary Site Administrator, and press OK, as shown in the following screenshot: You will be rewarded with the Top Level Site Successfully Created screen, as shown in the following screenshot: Don't forget!
If you get the dreaded Error screen, it is just a time out.
Refresh the browser and you will see your site. You will be prompted to log in. We will fix this in a moment. In the meantime, enter the Administrator and the password you chose in my case, Password1. There are a couple of small helpful clean up notes, but otherwise you are ready to code! Using the Tools menu drop-down, select Internet Options. Click on the Security tab and click on the Local Intranet icon, as shown in the following screenshot: Then click Close and click OK thrice: The advantage?
No more prompts to login! There are many other "out-of-the-box" SharePoint lists you can create such as Announcements, Contacts, Events calendar , Tasks, and more! Lists are where we store our data in SharePoint.
SharePoint Development with Visual Studio You should strive to use the out-of-the-box lists wherever possible. Next you should look to leverage an out-of-the-box list by "inheriting" from it and then customizing your own columns.
If you wish, you may also create your own custom list from scratch. A list is composed of columns — collectively they form the schema for the list. In SharePoint terms, the schema is called a Content Type, and the individual columns within the schema are called Site Columns.
If you have relational database expertise such as with Microsoft SQL Server , the concepts introduced here will be familiar to you. Site Columns are equivalent to data types. Running the script will create a physical table instance as determined by the schema. The proper creation, deployment, and management of SharePoint lists and schema is an important focus of the professional SharePoint developer. I cannot think of a better example to introduce all of the basics in such a way that you will be returning to this chapter again and again for guidance!
We will be using the awesome Visual Studio SharePoint tools to create a custom document library for Proposals. The "Proposal" will be implemented with a Content Type and Site Columns , and inherit from the out-of-the-box "document", and attached to the document library.
We will also be exploring the practical use of more advanced techniques: This forms one of the most common "professional" patterns for a SharePoint developer! Create Site Columns 2. Create Content Types 3. Create SharePoint list and attach Content Types 4. Provision with Feature Receivers and Feature Staplers 5. Control list events with Item Event Receivers This chapter will walk through the components of this pattern.
Ensure the correct web application is selected. Leave all other options at their default values. Scroll to the bottom and click on Ok. Bookmark the site to your favorites. I will refer to this site as the Chapter 2 URL in this chapter, for later purposes of creating Visual Studio projects. For example, in my case, this URL is: Choose the type Contacts, enter name as MyContacts and click on Create.
After the creation of the MyContacts list, you should automatically be navigated to the new list. From the ribbon, choose the Items tab from List Tools. Select the New Item drop-down. Specifically, note that you are creating a "new contact". I added last name "Munster", first name "Eddy" yes, from the 60's television show.
Click on the Save button: Now we are going to use the Contacts list as an example for demonstrating all the SharePoint components Microsoft used in putting this type of list together. First we look behind the scenes of the MyContacts list: Navigate to the MyContacts list by clicking the link in Quick Launch left-hand navigation.
In the ribbon, you will see List Tools.
Click on the List tab. Click on List Settings in the ribbon. Let us enable a "behind the scenes" view! Click on Advanced Settings. Click on Yes to Allow management of content types. Scroll down and click on OK to save this setting: If you scroll down, you will now see a Content Types section has become visible.
Note that the Content Type — Contact is assigned to the list: These site columns are part of the Contact content type. The columns in the MyContacts list were created as a result of the schema defined in the Contact Content Type.
From the Site Actions menu, choose Site Settings. Note the Galleries section: Click on Site content types and note the rather extensive selection available. You will see Contact under the List section: Click on Contact and it will take you to the details screen. From the Galleries section, click on Site Columns. A very long list appears but I would encourage you to review and become familiar with it — you should always consider using an existing Site Column instead of "duplicating" something very similar for your own use.
If we wish to follow "best practice" when creating our own Proposals document library, then it should be similarly backed by a Proposal Content Type that contains some out-of-the-box Site Columns and custom Site Columns. As an exercise, repeat this recipe again, but this time try using the Shared Documents library in the Chapter 2 site. Features and Solutions If you have professionally developed any type of application, then you must have had the requirement to "deploy" it.
For example, if you are developing a Windows desktop application, you may have been asked to create a setup. Or perhaps you have experience with using MSI windows installer files. Regardless, when it is time to hand off your application to others you must "package" it for deployment. NET web application, so SharePoint understands special installer files called Solutions creative name, right?
SharePoint solution files have the extension. The great news is that Visual Studio will automatically "package" your SharePoint customizations in WSP format — ready for you to deploy it to the world of SharePoint! I will explain the term "Feature" in more detail in one moment, but your goal throughout the remainder of this chapter will be to: Package these two Features into a SharePoint Solution file.
We will be proceeding to create the example, but at various points in the chapter, you will see the There's more section that will take you behind the scenes on what is happening with our Features and Solution. Here, we will explore how Microsoft implemented the Contacts Content Type and list schema.
To explore Features from the SharePoint site perspective, go to the Chapter 2 site: From the Site Actions menu, select Site Settings. Here, you can see that Microsoft itself has created a number of Features for SharePoint. The Activate and Deactivate buttons are simply a means of being able to turn the features on or off. Team Collaboration Lists is a feature that enables your ability to create all of the out-of-the-box lists, including a Contact list: Go ahead and click on the Deactivate button for the Team Collaboration Lists feature.
You may accept the warning that will pop up! Nothing "bad" will happen. Now go to Site Actions More Options. You will find all of the out-of-the-box lists gone — you cannot select them to create them.
Announcements, Contacts, Document Library, and so on. Go back to Site Actions Site Settings. Verify using Site Actions More Options that the list choices have returned.
To explore Features from the physical implementation perspective, we need to examine the SharePoint installation folder. This is also referred to as the SharePoint Root folder. Open windows explorer and navigate to: Go to the Template sub-folder.
Then underneath to the Features folder. From one perspective, SharePoint is a composition of a long list of Features — customizations and extensions that Microsoft has created for the product. Find the TeamCollab folder and navigate to it.
Inside you will find a Feature. One of the purposes of this file is to describe the feature with a title, description, and icon. In this case, it displays the title Team Collaboration Lists and description Provides team collaboration capabilities…". Navigate back up to the Features folder. Towards the top, go to the ContactsList sub-folder. Explore and you will find a feature. We have explored Features from these two perspectives because, as a SharePoint developer, it will be your role to create new Features that get deployed to the SharePoint servers and will appear in the Feature list alongside the Microsoft provided ones!
In our case, building up a SharePoint Solution as described in the introduction to this section. First, please look at the rather extensive set of Site Columns you get "out-of-the-box" and please feel free to reuse them instead of duplicating something similar. In our case, we will be defining a document library to hold our proposals.
We are going to define the following additional Site Columns that we require: Number ff Proposal Client: Single line of text ff Proposal Type: Choice field For simplicity of the example, the client is a single line of text. This could have been another long list the client list and we could then define a "lookup" to be able to choose the client for example, from a drop-down menu for the proposal. Getting ready We will create the Visual Studio project that we will be working with in this chapter: Open Visual Studio From the File menu, select New Project.
We will be taking advantage of some of these in the future chapters, such as the Visual Web Part in the next chapter: Provide a name such as ProposalSiteColumns.
Take a moment to view all of the available project items. There is not one specifically for Site Columns, but shortly we will be taking advantage of the items for Content Type and for List Definition. Click on Add: You will see that a Feature was added called Feature1!
We will review this in more detail later. For now, right-click on the node that says Feature1 and select Rename. Change the name to ProposalLibrary. Change the Title to something more meaningful — such as Proposal Library — as well as the Description. It is professional to add an icon image to your Feature.
Target an image size around 32 x 32, although this is not strict for dimension. Typically, you may choose a company logo or such. To add the image to your Feature: Right-click on your project and choose Add SharePoint Images mapped folder. Click on the SPProposalLibrary folder that was created.
Right-click on the folder and select Add Existing Item. Navigate to the location for your image. Double-click on the ProposalLibrary Feature to expose the properties window. Locate the Image URL property and type in the path and image relative to the images folder.
Get ready to generate GUIDs! The following screen will appear. Select the Registry Format. Go ahead and "copy" a GUID now. Ok, this is not the most exciting development you will do in your lifetime, as you will simply be hand typing some XML: Enter the following XML. You can type in these very GUIDs, or you can generate your own in place of the ones provided: Wait until you see the Deploy Succeeded message in the bottom left-hand corner of Visual Studio.
Let us go and verify that our Feature had been deployed and our Site Columns are defined. Navigate to the Chapter 2 site. Select Site Actions Site Settings. Notice that the Proposal Library is there and is activated: Select the Site columns link in the Galleries section.
Scroll down and you will see our three custom Site Columns in the Packt Publishing section: You have created your first real Feature with Visual Studio SharePoint developer tools; created some Site Columns, deployed them to the sample site, and activated the Feature. Here is some further information and explanation regarding Site Columns and the meaning of the Elements. More Site Column types While these are not all the possible types of columns you can create as Site Columns, here are some of the most common ones: In this case, instructions for creating several "Field" elements, also known as Site Columns.
As we examine more SharePoint items, you will see different types of instructions. There can be one or more Elements. Note that Elements. However, the name can be one of your choice, and possibly more helpful such as ProposalSiteColumns. Packaging SharePoint Solutions Regardless of the type of Visual Studio Solution you develop — a regular web application or even a Windows application — eventually you will need to "package" it for the purpose of deploying it to another server or client computer.
Such packaging is varied and may be a Cabinet. CAB file, a Microsoft Installer. MSI file, or a setup. Some summary points about SharePoint Solution files: We are going to explore the Packaging Designer: Double-click on the Package node in your Visual Studio project. You can see literally in visual representation that the Proposal Library Feature is contained in our package — as well as the graphics files we deployed to SharePoint's Images directory: It is almost the dictionary definition of a manifest — primarily a list of files contained in the package and their respective deployment location relative to the SharePoint Root folder.
You can view the actual WSP file in the Bin folder of your project. Expand the Bin folder, and then expand the Debug sub-folder. Right-click on the SPProposalLibrary. Right-click on the Debug folder and select Paste. Your Solution should look as follows: We can see the files contained inside: So there is your behind the scenes look at how the SharePoint Solution package is created and what is "inside the box".
Here is some further explanation on what is going on behind the scenes with SharePoint Solutions and Solution deployment. How did my Feature get deployed and activated? When you right-clicked on your Visual Studio project and selected Deploy Solution — you kicked off the Solution deployment lifecycle!
Let us presume now that your Features are deployed. You make some changes and use Deploy Solution again. Then, it adds the new solution WSP file and "installs" it. Next, the Visual Studio Solution deployment is kind enough to automatically activate the Feature for us, although technically that is an extra step.
Go ahead and use Deploy Solution again.
Then look at your output window to see the following: SPProposalLibrary, Configuration: Default Run Pre-Deployment Command: Skipping deployment step because a pre-deployment command is not specified. Retract Solution: Retracting solution 'spproposallibrary.
Deleting solution 'spproposallibrary. Add Solution: Adding solution 'SPProposalLibrary. Deploying solution 'SPProposalLibrary. Activate Features: Activating feature 'ProposalLibrary' Run Post-Deployment Command: Skipping deployment step because a post-deployment command is not specified.
But what are "Deleting Solution" and "Adding Solution" actually doing? You can physically see all of the WSP files on the server and the current status of solution deployment from Central Administration. Click on the SPProposalLibrary. You will see the following information: Creating new Content Types Now we are ready to create the schema for our Proposal Library — through a Content Type that will inherit from Document and extend it with our custom Proposal site columns.
The Content Type can also have associated a Microsoft Word template file, so that as you create a "New Proposal", Microsoft Word will come up and launch with a Proposal document template, instead of simply a blank document. Getting ready Launch Microsoft Word and create a simple document to serve as your Proposal template. Save the file as ProposalTemplate.
We must first actually take a copy of our ProposalTemplate.
A file copy operation in SharePoint is accomplished via the "Module" provisioning instruction. You will see an example of this instruction as follows: Select Module from the presented list, provide a name such as ProposalTemplate and click on the Add button. Navigate to the location of the ProposalTemplate.
In the ProposalTemplate section, you will see a sample. Right-click on sample. Edit the Elements. The URL is the destination folder in the content database. Your Elements. Next we will implement a Proposal Content Type that features the Site Columns created in the last recipe, and attaches the Word Proposal template: Select Content Type from the presented list, provide a name such as Proposal and click on the Add button. A dialog will come up. Choose Document from the drop-down in response to the question What base content type should this content type inherit from?
In the Elements. Change the Description attribute to something such as Create a new proposal from a template. Add the XMLDocuments node exactly as shown in the following example. This node will add standard New, Edit, and Display forms to the document library. Now, let us deploy the Solution and observe the results: Note that the Proposal Library is there and is activated same Feature as with the Site Columns recipe: Select the Site content types link in the Galleries section.
Scroll down and you will see our three custom site columns in the Packt Publishing section: Click on the Proposal Content Type, and note the Columns section includes the Site Columns we defined in a previous recipe: You have enhanced our Feature with Visual Studio SharePoint developer tools, created a Content Type SharePoint schema , deployed this to the sample site, and activated the Feature.
Creating document libraries with Content Types Now we are going to create an actual document library with the Proposal Content Type attached. Enter Proposal Document Library in response to the question What is the display name of the list definition?. Choose Proposal in the drop-down in response to the question What content type would you like to use for your list definition?. Ensure the checkbox is enabled for Add a list instance for this list definition, and click on the Finish button.
Expand this node to expose the Elements.