Learning Search-driven Application Development with SharePoint 2013 is a fast-paced, practical, hands-on guide to the world of enterprise search in SharePoint 2013. With step-by-step tutorials and real-world-based exercises, this book will give you a head start in creating fresh and exciting search-driven applications using SharePoint 2013's new search engine. The book covers a wide range of topics such as Query Rules, Result Types and Display Templates, Working with the new client APIs, and Business Connectivity Services.
Chapter 1, Getting Started With SharePoint 2013 Search, gives you a taste of the new features SharePoint 2013 search brings to the table and then dives deep into the architecture that holds this system together.
Chapter 2, Using the Out of the Box Search Components, shows you how to use query rules and result sources and get a taste of building a simple search-driven application. SharePoint 2013 provides a rich out of the box experience for developing search-driven applications.
Chapter 3, Using the New CSOM and RESTful APIs, explains how to work with these new APIs and build a SharePoint hosted search-driven app using the new App developing approach. SharePoint 2013 changes the way we developers extend the platform by providing a whole new set of client-based APIs.
Chapter 4, Customizing the Look, focuses on creating display templates that define how a search result will render, and result types that define which display template a result should have. SharePoint 2013 opens up a whole new way to design our search results.
Chapter 5, Extending Beyond SharePoint, introduces how to create an external indexing connector and understand how to work with external data. In a real-world environment, not all the information we wish to search for is hosted within SharePoint. Business Connectivity Services (or BCS for short) enables us to extend beyond the realms of SharePoint and index data from external systems.
To run the examples shown in this book you will need a SharePoint 2013 server with Visual Studio 2012 installed.
If you don't have access to a full SharePoint 2013 server, Office 365's SharePoint Online and Visual Studio 2012 can also be used to run most of the examples in this book.
In this book, you will find a number of styles of text that distinguish between different kinds of information. Here are some examples of these styles, and an explanation of their meaning.
Code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles are shown as follows: "We can include other contexts through the use of the
A block of code is set as follows:
[default] exten => s,1,Dial(Zap/1|30) exten => s,2,Voicemail(u100) exten => s,102,Voicemail(b100) exten => i,1,Voicemail(s0)
When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:
exten => s,1,Dial(Zap/1|30)
exten => s,2,Voicemail(u100)
exten => s,102,Voicemail(b100)
exten => i,1,Voicemail(s0)
Any command-line input or output is written as follows:
# cp /usr/src/asterisk-addons/configs/cdr_mysql.conf.sample /etc/asterisk/cdr_mysql.conf
New terms and important words are shown in bold. Words that you see on the screen, in menus or dialog boxes for example, appear in the text like this: "clicking the Next button moves you to the next screen".
Feedback from our readers is always welcome. Let us know what you think about this book—what you liked or may have disliked. Reader feedback is important for us to develop titles that you really get the most out of.
To send us general feedback, simply send an e-mail to
<[email protected]>, and mention the book title via the subject of your message.
If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, see our author guide on www.packtpub.com/authors.
Now that you are the proud owner of a Packt book, we have a number of things to help you to get the most from your purchase.
You can download the example code files for all Packt books you have purchased from your account at http://www.packtpub.com. If you purchased this book elsewhere, you can visit http://www.packtpub.com/support and register to have the files e-mailed directly to you.
Although we have taken every care to ensure the accuracy of our content, mistakes do happen. If you find a mistake in one of our books—maybe a mistake in the text or the code—we would be grateful if you would report this to us. By doing so, you can save other readers from frustration and help us improve subsequent versions of this book. If you find any errata, please report them by visiting http://www.packtpub.com/submit-errata, selecting your book, clicking on the errata submission form link, and entering the details of your errata. Once your errata are verified, your submission will be accepted and the errata will be uploaded on our website, or added to any list of existing errata, under the Errata section of that title. Any existing errata can be viewed by selecting your title from http://www.packtpub.com/support.
Piracy of copyright material on the Internet is an ongoing problem across all media. At Packt, we take the protection of our copyright and licenses very seriously. If you come across any illegal copies of our works, in any form, on the Internet, please provide us with the location address or website name immediately so that we can pursue a remedy.
Please contact us at
<[email protected]> with a link to the suspected pirated material.
We appreciate your help in protecting our authors, and our ability to bring you valuable content.
You can contact us at
<[email protected]> if you are having a problem with any aspect of the book, and we will do our best to address it.