book

Pro ASP.NET SharePoint 2010 Solutions: Techniques for Building SharePoint Functionality into ASP.NET Applications

Name: Pro ASP.NET SharePoint 2010 Solutions: Techniques for Building SharePoint Functionality into ASP.NET Applications
Author: Dave Milner
ISBN: 9781430231110

by Dave Milner

December 2010

Intermediate to advanced

367 pages

8h 42m

English

Apress

Read now

Unlock full access

Copyright
About the Author
About the Technical Reviewer
Acknowledgments
Introduction
1. SharePoint as a Development Platform
1.1. SharePoint Features1.1.1. Extensibility1.1.1.1. Web Site Extensibility1.1.1.1.1. SPFarm1.1.1.1.2. SPWebApplication and SPSite1.1.1.1.3. SPSite and SPWeb1.1.1.2. Development Extensibility1.1.2. Document Management1.1.3. Authentication and Authorization1.1.3.1. Authentication1.1.3.2. Authorization1.1.4. Microsoft Office Integration1.1.5. SharePoint Designer 20101.1.6. SharePoint Workspace1.1.7. Visual Studio 2010 Integration1.2. Common Approach to Application Development in SharePoint1.2.1. Intranet Scenario1.2.2. Publishing Site Scenario1.3. Sandboxed Solutions1.4. Advanced Approaches to Application Development1.5. Summary
2. Visual Studio 2010–Advancing the SharePoint Development Environment
2.1. Anatomy of a Visual Studio 2010 SharePoint Project2.1.1. Empty SharePoint Project2.1.1.1. Feature2.1.1.2. Package2.1.2. Visual Web Part2.1.2.1. SharePoint Customization Wizard2.1.2.1.1. Deploy As a Farm Solution2.1.2.1.2. Deploy As a Sandboxed Solution2.1.2.2. Examining the Visual Web Part Solution2.1.2.2.1. Elements.xml2.1.2.2.2. VisualWebPart1.cs2.1.2.2.3. VisualWebPart1.webpart2.1.2.2.4. VisualWebPart1UserControl.ascx2.1.2.2.5. VisualWebPart1UserControl.ascx.cs2.2. Wrapping ASP.NET Development2.3. Coding the Sample Visual Web Part2.4. Deploying a Solution2.4.1. Examining the Deployment Process2.4.2. Deploying to a Test or Production Environment2.5. Using Features2.5.1. Feature.Template.xml2.5.2. Feature1.feature and Feature1 Nodes2.6. Package Designer2.7. Packaging Explorer2.8. SharePoint Project Templates2.8.1. Sequential Workflow2.8.2. State Machine Workflow2.8.3. Business Data Connectivity Model2.8.4. Event Receiver2.8.5. List Definition2.8.6. ContentType2.8.7. Module2.8.8. Site Definitions2.8.9. Import Reusable Workflow2.8.10. Import SharePoint Solution Package2.9. Other Visual Studio Templates and Features2.10. Team Development2.10.1. Development2.10.2. Test2.10.3. Production2.11. Summary
3. SharePoint, IIS, and the .NET Framework
3.1. SharePoint 2010 in IIS 7 Manager3.1.1. IIS and .NET Fundamentals3.1.1.1. HTTP.sys Protocol Listener3.1.1.2. WWW and WAS Services3.1.1.3. ISAPI Filters3.1.1.4. IISReset.exe3.1.1.5. Modules3.1.2. SharePoint 2010 File System Folders Under IIS3.1.3. SharePoint 2010 Virtual Directories3.2. SharePoint 2010 and the .NET Framework3.2.1. WSS web.config File3.2.1.1. Assemblies3.2.1.2. MergedActions3.2.1.3. Modules3.2.1.4. SafeControls3.2.2. Code Access Security3.2.2.1. Custom Trust Level Configurations3.2.2.2. Strong Name Signing Assemblies3.2.3. Sandboxed Solutions3.2.3.1. Site Collection Administrator Deployed3.2.3.2. Security3.3. Summary
4. SharePoint Architecture–File System, Database, and the Provider Pattern
4.1. SharePoint 2010 and the File System4.1.1. SharePoint Root4.1.1.1. ADMISAPI4.1.1.1.1. Bin4.1.1.2. CONFIG4.1.1.2.1. Data4.1.1.2.2. HCCab4.1.1.2.3. Help4.1.1.3. ISAPI4.1.1.4. LOGS4.1.1.4.1. Policy4.1.1.4.2. Resources4.1.1.5. TEMPLATE4.1.1.5.1. UserCode4.1.1.5.2. WebClients4.1.1.5.3. WebServices4.1.2. Program Files\Microsoft Office Server4.1.2.1.4.1.2.1.1. Bin4.1.2.1.2. Config4.1.2.1.3. Data4.1.2.1.4. Logs4.1.2.1.5. MUI4.1.2.1.6. Service4.1.2.1.7. Sql4.1.2.1.8. Synchronization Service4.1.2.1.9. Tools4.1.2.1.10. TransformApps4.1.2.1.11. WebClients4.1.2.1.12. WebServices4.1.3. WSS Folders4.2. SharePoint 2010 Databases4.2.1.4.2.1.1.4.2.1.1.1. Virtual machine "a" contains the following pre-configured software:4.2.1.1.2. Virtual machine "b" contains the following pre-configured software:4.2.1.1.3. AdventureWorksDW4.2.1.1.4. Application_Registry_Service_DB4.2.1.1.5. BDC_Service_DB4.2.1.1.6. Contoso_Inventory, Contoso_Retail_DW, and Customers4.2.1.1.7. FAST Databases4.2.1.1.8. Managed Metadata Service Database4.2.1.1.9. PerformancePoint Service Application database4.2.1.1.10. ReportServer, ReportServerTempDB4.2.1.1.11. Search Service Databases4.2.1.1.12. Secure_Store_Service_DB4.2.1.1.13. SharePoint_AdminContent4.2.1.1.14. SharePoint_Config4.2.1.1.15. StateService4.2.1.1.16. SupplyChainSQL4.2.1.1.17. User Profile Service Application_ProfileDB4.2.1.1.18. User Profile Service Application_SocialDB4.2.1.1.19. User Profile Service Application_SyncDB4.2.1.1.20. WebAnalyticsServiceApplication_ReportingDB, WebAnalyticsServiceApplication_StagingDB4.2.1.1.21. WordAutomationServices4.2.1.1.22. WSS_Content Databases4.2.1.1.23. WSS_Logging4.3. SharePoint 2010 and the Virtual Path Provider Pattern4.3.1. Object-Oriented Architecture4.3.1.1. The Open/Closed Principle4.3.1.2. Liskov Substitution Principle4.3.1.3. Dependency Inversion Principle4.3.1.4. Single Responsibility Principle4.3.1.5. Interface Segregation Principle4.3.2. The Provider Pattern4.3.3. The Virtual Path Provider4.4. Summary
5. Web Parts and Master Pages
5.1. Web Parts5.1.1. Building a Visual Web Part5.1.1.1. Adding Code5.1.1.2. Examining How SharePoint Loads User Controls5.1.1.3. Examining the Configuration Files5.1.1.4. Using Strongly Named Assemblies5.1.1.5. Deploying the Visual Web Part5.1.1.6. Using the Developer Dashboard5.1.2. Building a Standard SharePoint Web Part5.1.2.1. Adding a Web Part to the Project5.1.2.2. Adding Code5.1.2.3. Deploying the Web Part5.1.3. Building a Silverlight Web Part5.1.3.1. Adding Code5.1.3.2. Deploying the Silverlight Web Part5.1.4. Accessing External Database Content in a Web Part5.1.4.1. Storing the Connection String in an XML File5.1.4.2. Storing the Connection String in a Hidden List5.1.4.3. Storing the Connection String in the web.config File5.1.5. Web Parts Summary5.2. Master Pages5.2.1. Understanding Where Master Pages are Used5.2.2. V4.master5.2.3. Master Page Content5.3. Summary

6. The Client Object Model
6.1. Introducing the Client Object Model6.1.1. .NET-Managed and Silverlight-Based Clients6.1.2. ECMAScript/JavaScript Clients6.1.3. Taking Advantage of the Client Object Model6.2. Client Object Model Components6.2.1. .NET Components6.2.2. Silverlight Components6.3. Client Object Model API Support6.4. Data Retrieval and Interaction6.4.1. LoadQuery and Load6.4.1.1. Query Syntax Example—LoadQuery6.4.1.2. Method Syntax Example—Load6.4.1.3. Updating Items Through the Client Object Model6.4.1.4. Creating Items Through the Client Object Model6.4.1.5. Deleting Items Through the Client Object Model6.5. Client Object Model—The Big Three6.5.1. Client Object Model Reading List Data via ASP.NET6.5.2. Client Object Model Writing List Data via ASP.NET6.5.3. Client Object Model Reading List Data via Silverlight—From a Web Part6.5.4. Client Object Model Writing List Data via Silverlight6.5.5. Debugging Silverlight in SharePoint 20106.5.6. Client Object Model—Reading List Data via ECMAScript/JavaScript6.6. Summary
7. Business Connectivity Services
7.1. What are Business Connectivity Services?7.1.1. What are Business Connectivity Services?7.1.1.1. External Content Types7.1.1.2. External Lists7.1.1.3. External Data Columns7.1.1.4. Setting Up BCS7.1.2. BCS Solutions with SharePoint Designer7.1.2.1. Open SharePoint 2010 Site7.1.2.2. Define New External Content Type7.1.2.2.1. Discover Data Sources7.1.2.2.2. Data Source Credentials and Identity7.1.2.3. Create Operations7.1.2.4. Create External Lists and Forms7.1.2.5. Export BDC Model for Visual Studio 20107.1.2.6. Import BDC Model with Central Administration7.1.3. BCS Solutions with Visual Studio 20107.1.3.1. Create Events Database and Table7.1.3.2. New SharePoint BDC Model Project7.1.3.3. Create Events Code and EventsService Code7.1.3.4. Finish BDC Model and Deploy to SharePoint7.1.4. BCS Architecture7.1.4.1. External Data Store7.1.4.2. BCS Connectors7.1.4.3. Business Connectivity7.1.4.4. Secure Store Service7.1.5. Summary
8. Touch Points–Integrating SharePoint 2010 and ASP.NET
8.1. Integration Factors8.2. Example Business Scenarios8.2.1. Corporate Internet and Service Portals8.2.2. Existing ASP.NET Product8.2.3. New Blended Solution8.2.4. Expanding Your Corporate Portal8.2.5. Talking to SharePoint8.3. Organizational Factors8.3.1. Organizational Examples8.3.2. SharePoint-Centric Organizations8.4. Touch Points8.5. Low Touch Point8.5.1. Pros8.5.2. Cons8.6. Branding SharePoint Solutions8.6.1. Branding Possibilities, Features, and Tools8.6.1.1. Low-Effort Branding8.6.1.2. Medium-Effort Branding8.6.1.3. High-Effort Branding8.6.2. SharePoint Server 2010 Publishing Features8.6.3. Working With a Brand8.6.4. Branding the ASP.NET Application8.6.5. Branding in SharePoint Designer Example8.6.6. Deploying Branded Solutions8.7. Publishing Layouts8.8. Customizing SharePoint 2010 Navigation8.8.1. Customizing Navigation Through the User Interface8.8.2. Adding Links Through the Object Model8.8.3. Navigation Custom Data Sources8.9. Summary
9. Medium Touch Point Solutions
9.1. Medium Touch Points9.1.1. Pros9.1.2. Cons9.2. Medium Touch Point Examples9.2.1. SharePoint and The Cloud9.2.2. SharePoint 2010 and Windows Azure MarketPlace9.2.3. PowerPivot and Azure9.2.4. Accessing Azure DataMarket Feeds Through .NET9.2.5. Integrating External Feeds Through .NET WCF Services and jQuery9.2.5.1. Setting Up and Migrating Data to a SQL Azure Database9.2.5.2. Developing an ASP.NET Application with SQL Azure, WCF, and jQuery9.2.6. Consuming an oData Feed with jQuery in SharePoint 20109.3. Summary
10. High Touch Point Solutions
10.1. Pros10.1.1.10.1.1.1. Pros10.1.2. Tenets and Constraints for High Touch Point Solutions10.1.3. High Touch Point Blended Solution Example10.1.3.1. New ASP.NET Web Site Example10.1.3.1.1. Add Web Forms Customers and Orders10.1.3.1.2. Add ASP.NET Code10.1.3.2. Modifying Our ASP.NET Web Site for SharePoint 2010 Integration10.1.3.2.1. Create Master Page10.1.3.2.2. Reference Master Page on Application Pages10.1.3.2.3. Modify web.config10.1.3.3. Deploy to SharePoint 2010 Layouts Directory10.1.4. Migrating An Existing ASP.NET Application10.1.4.1. Client Side Libraries10.1.4.2. Third-Party Libraries10.1.4.3. Silverlight10.1.5. Load Testing Your Blended Solution10.2. Summary and Conclusion

Content preview from Pro ASP.NET SharePoint 2010 Solutions: Techniques for Building SharePoint Functionality into ASP.NET Applications

Chapter 6. The Client Object Model

It doesn't matter where you are coming from. All that matters is where you are going.

—Brian Tracy

In the previous chapter, we built our functional technical knowledge in SharePoint 2010 development by showing how we can connect to external systems directly from within SharePoint. This technique will become helpful in our blended solution chapters later in the book.

In this chapter, we will examine connectivity from the other perspective: connecting to SharePoint 2010 data from outside the SharePoint application. The SharePoint 2010 methods that enable this are known as the client object model.

Introducing the Client Object Model

The client object model consists primarily of two separate technologies:

A model for connecting ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

Read now

Unlock full access

More than 5,000 organizations count on O’Reilly

O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.

Julian F.

Head of Cybersecurity

I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.

Addison B.

Field Engineer

I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.

Amir M.

Data Platform Tech Lead

I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.

Mark W.

Embedded Software Engineer

Microsoft SharePoint 2013: Designing and Architecting Solutions

Publisher Resources

ISBN: 9781430231110Purchase book

Cloud Computing

Data Engineering

Data Science

AI & ML

Programming Languages

Software Architecture

IT/Ops

Security

Design

Business

Soft Skills

Pro ASP.NET SharePoint 2010 Solutions: Techniques for Building SharePoint Functionality into ASP.NET Applications

by Dave Milner

Chapter 6. The Client Object Model

Introducing the Client Object Model

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.