�ݺ�ߣ

Editor's Notes

• #10: Provide a brief run-through of the SharePoint Server 2013 workloads: Portals and Collaboration. SharePoint provides many core capabilities, such as the ability to create sites, workspaces, libraries, and lists, which enable teams to work together effectively regardless of their physical location. Search. SharePoint provides a comprehensive and highly extensible search platform that enables users to find information from a variety of content sources across an organization. Enterprise Content Management. SharePoint provides a range of functionality to support business processes, such as workflow, records management, and tools for eDiscovery and compliance. Web Content Management. SharePoint provides comprehensive Content Management System (CMS) features that can be used to manage and maintain a corporate Web presence. Social and Communities. SharePoint provides functionality that enables users to connect with one another, share news and information, and build communities around common interests. Business Connectivity Services. SharePoint enables you to integrate data from external systems into solutions for SharePoint sites and Microsoft Office 2013 applications. Business Intelligence. SharePoint provides a range of capabilities for providing insight into business data, from built-in tools such as Excel Services and PerformancePoint Services to integration with SQL Server 2012 Analysis Services and SQL Server 2012 Reporting Services.
• #11: Briefly cover the commonly used development tools: Microsoft Visual Studio 2012. Visual Studio is an integrated development environment (IDE) that provides a range of productivity tools, debugging and deployment functionality, and integration with Team Foundation Server. Microsoft Office Tools for Visual Studio 2012. This plug-in for Visual Studio provides templates for SharePoint Server 2013, including Apps for SharePoint and Apps for Office as well as server-side custom components. Microsoft SharePoint Designer 2013. SharePoint Designer is a free desktop application that offers a range of capabilities for customizing sites and creating non-code-based custom components for SharePoint. For example, you can use SharePoint Designer to create workflows and build declarative Business Data Connectivity (BDC) models. Although SharePoint Designer began as a tool for power users, it is now central to many aspects of the SharePoint development process. Web Design Tools. SharePoint 2013 introduces new processes for designing and branding SharePoint sites and pages. These processes enable web designers to create SharePoint pages by using standard web technologies—HTML, CSS, and JavaScript—in standard web design applications. You can then use built-in SharePoint utilities to add the required SharePoint functionality to the designer's wireframe web pages.
• #12: Provide a high-level overview of the SharePoint app model (see the student handbook for details). Emphasize that there are two ways to publish and consume apps: Office Marketplace. This is a public gallery of apps for SharePoint, hosted by Microsoft. Organizations can purchase and download apps from the Office Marketplace. Developers can publish apps to the Office Marketplace. Corporate Catalog. This is a private, organization-specific gallery of apps for SharePoint. SharePoint administrators can create a corporate catalog for each web application in a SharePoint farm. Developers can publish apps to a corporate catalog to make them available for use within the organization. Talk briefly around the four client-side programming models. Provide a brief overview of the new design model and the new workflow model, both of which have been completely overhauled for SharePoint 2013. Finish by mentioning some of the other key enhancements in SharePoint 2013, such as new social functionality and the redesigned search service.
• #13: This topic is designed to provide students with a high-level overview of SharePoint and related technologies, rather than any kind of detailed logical architecture. Keep the topic brief. Use the slide to illustrate key changes from SharePoint 2010, most notably that Office Web Apps Server is now a separate product and workflow now runs on a separate platform. Note: the specified versions of ASP.NET (4.0) and the .NET Framework (4.5) may seem incongruous to developers who are less familiar with .NET. The MCSA prerequisites cover the distinction between the .NET Framework and ASP.NET.
• #14: Mention that SharePoint 2010 supported REST-based list operations through the listdata.svc service. This service remains for backwards compatibility, but the client.svc service supports a far more comprehensive set of operations through REST and OData. This topic is designed to provide a high-level overview of API choices. Avoid providing too much detail at this stage.
• #15: The aim of this lesson is to familiarize students with the various approaches to SharePoint development that are available to them, together with the advantages and disadvantages of each approach. At this stage, you are not teaching the students how to use each approach; instead, you are just equipping them to evaluate which approach is best suited to particular scenarios. Where necessary, emphasize that each approach is covered in more detail later in the course. Bear in mind that deployment models—features, apps, farm solutions, and sandboxed solutions—are covered in the next lesson. As such, avoid discussing packaging and deployment in any detail in this lesson.
• #16: Provide a brief overview of what you can do with declarative components. Focus on when and where you should use declarative components, rather than on providing any technical detail. Subsequent modules provide the technical detail.
• #17: This topic evaluates client-side coding as a broad approach to SharePoint development. Specific deployment and execution models, such as apps for SharePoint, are covered in the next lesson.
• #18: Provide a brief overview of how web parts work, and focus on when and where you should use them. Emphasize that apps for SharePoint are now the preferred approach, unless you specifically want to leverage the web part framework (for example to connect web parts). Subsequent modules provide the technical detail.
• #19: Describe briefly how custom application pages work – essentially they plug directly into the ASP.NET page rendering process. Focus on when and where you should consider using custom application pages.
• #20: Provide a conceptual overview of timer jobs, and talk about when and where you should consider using a timer job. Subsequent modules provide the technical detail.
• #21: Provide a brief overview of event receivers in SharePoint, including event receiver categories and the concepts of before events and after events. Talk about when and where you should consider using an event receiver. Subsequent modules provide the technical detail.
• #22: Briefly describe the concept of workflow as a tool for modeling and automating business processes. Talk about when and where you should consider creating a workflow. Subsequent modules provide the technical detail.
• #23: Remember that this is an introductory module, which aims to give students a high-level view of the SharePoint development landscape. Later modules provide far more detail on how to build Features, solutions, and apps, so avoid being drawn into providing "how-to" information. This lesson is designed solely to provide an overview of the execution and deployment models that are available.
• #24: Provide an overview of the SharePoint Feature framework. The student handbook includes an example of a Feature.xml file.
• #25: Provide an overview of farm solutions as a vehicle for packaging and managing the lifecycle of SharePoint components. Subsequent modules provide more technical detail.
• #26: Provide a brief overview of the sandboxed solution framework, focusing on the capabilities and constraints. Emphasize that sandboxed solutions are largely considered deprecated in favor of apps for SharePoint.
• #27: Provide a brief overview of how apps are packaged, deployed, and provisioned. In the student workbook, the third paragraph states: When a user installs an app, the app provisions its own subsite within the host web. This subsite is known as the app web. Technically speaking, the app web is only provisioned if the app needs to deploy resources to SharePoint. If the app is remote-hosted and does not contain any declarative components, an app web is not created. Adding this explanation to the student manual at this point in the course would cloud the issue; however, you may want to provide clarification if challenged.