DOCSLIB.ORG

Benefits of Sharepoint 2010 As a Product Platform

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Benefits of Sharepoint 2010 As a Product Platform Benefits of SharePoint 2010 as a Product Platform For Independent Software Vendors and Enterprises Date published: November 2010 Authors: Owen Allen – Principal, SharePoint Directions Eric Bowden – Senior Consultant, ThreeWill Kirk Liemohn – Principal Software Engineer, ThreeWill Danny Ryan – Principal, ThreeWill Tommy Ryan – Principal, ThreeWill Pete Skelly – Principal Consultant, ThreeWill John Underwood - Technical Evangelist, ThreeWill Contributors: Geoffrey Edge – Senior Technology Specialist, Microsoft Corporation Kirk Evans – Developer and Platform Evangelism for Communications Sector, Microsoft Corporation Chris Mitchell – Technology Architect for Microsoft Technology Center, Microsoft Corporation Reviewers: Bill Arconati – Product Marketing Manager, Atlassian Software Systems Tony Clark – Director, Enterprise Architecture, Cox Enterprises Geoffrey Edge – Senior Technology Specialist, Microsoft Corporation Bo George – Senior Application Developer, Aflac Murray Gordon – ISV Architect Evangelist, Microsoft Corporation Adam P. Morgan - Enterprise Sales, Digital Marketing Platform Group, Microsoft Corporation Aaron Rafus – Technology Evangelist, McKesson Corporation William Rogers – Chief Workplace Architect, CorasWorks Corporation Scott Schemmel - VP, Global Information Technology at PGi Brendon Schwartz – Senior Platform Engineer, JackBe Corporation Cole Shiflett – Solutions Architect, Equifax Dr. Todd Stephens – Senior Technical Architect, AT&T Matt Waltz – Chief Technology Officer, NextDocs Michael Wilson – Solution Specialist for Office and SharePoint, Microsoft Corporation Summary During the 2009 SharePoint Conference, Christian Finn, Director of SharePoint Products for Microsoft, commented that given current trends, building products on the SharePoint Platform is the “new black.” To make his case, he cited the momentum of the SharePoint platform along with significant announcements from companies building integration with SharePoint into their products and services. This white paper, designed for Independent Software Vendors, software architects, CIOs, and other enterprise technology leaders picks up this discussion by addressing the perceived limitations that may cause development companies to discount SharePoint as a development platform when drawing up a technology roadmap – and illustrating the value of leveraging SharePoint as a Web Application Development Platform for those organizations. Contents Why This White Paper ..............................................................3 Perceived Barrier 3 - Lack of Integration with External or Relational Data ........21 SharePoint Background ...........................................................4 Perceived Barrier 4 - Audience for this Paper............................................................6 Application Lifecycle Management (ALM) and Code Isolation. .................................................................................21 Making the Case for SharePoint .............................................7 Is Perception Reality? ....................................................................22 Does SharePoint Fit .........................................................................7 Misconceptions of SharePoint as an Making the Case ...............................................................................8 Application Platform ..............................................................23 Leveraging the Platform ............................................................8 Misconception 1 - Understand Your Value Proposition ......................................8 A SharePoint Dependency Means Closed Architecture .......................................................................23 SharePoint Platform Strategies ..............................................9 Misconception 2 - Connect ................................................................................................9 SharePoint Applications Are Too Restrictive ........................23 Extend .................................................................................................11 Misconception 3 - SharePoint Is Only a Document Repository..........................24 Build On .............................................................................................12 Misconception 4 - Platform Capabilities ..............................................................13 SharePoint Cannot Be Used to Run Line of Business Applications ..............................................................25 Infrastructure ...................................................................................13 Community Support and Tooling ........................................26 ASP.NET HTTP Pipeline ................................................................. 13 Community .......................................................................................26 Application Security ....................................................................... 14 Visual Studio ....................................................................................26 Service Applications ....................................................................... 14 Debugging ........................................................................................26 Packaging and Deployment ....................................................... 14 SharePoint Designer ......................................................................27 Office 365 & SharePoint Online ................................................ 14 Third Party Tools .............................................................................27 Content Management ..................................................................15 Office 365 & SharePoint Online Resources ...........................27 External Data ..................................................................................... 15 Next Steps .................................................................................28 Business Intelligence ...................................................................... 16 Feature Mapping ............................................................................28 Search .................................................................................................. 16 Market Analysis ...............................................................................28 Workflow ............................................................................................ 17 Bake Off .............................................................................................28 Data Model User Interface .......................................................... 17 Pilot Project ......................................................................................28 And More... ........................................................................................ 17 Consult with Others .......................................................................28 User Interface ...................................................................................18 ISV Ecosystem Map ........................................................................29 Platform Capabilities Summary ................................................19 Key Resources ..................................................................................30 Barriers to Adoption as a Development Platform ............20 References .........................................................................................30 Perceived Barrier 1 - Unique Developer Skill Set .........................................................20 Glossary of Terms ...........................................................................31 Perceived Barrier 2 - Footnotes ..........................................................................................34 Closed or Restrictive Platform Services ..................................20 2 3 Why This White Paper As with any evolving product, there are false ceilings set due to people’s experiences with previous versions. The initial core features/capabilities for SharePoint were targeted to provide out-of-the-box features that made the product easy to use and administer for team sites and portals. The product was extensible from the beginning, but it was not architected for the mainstream developer. This focus has changed over the years and there are very compelling reasons that product companies should consider SharePoint in their technology roadmaps. The ability to leverage the rich features of SharePoint technologies is reason enough to consider SharePoint as a web development platform. Another key reason to consider either building on top of SharePoint or having a connection strategy with SharePoint is market opportunities that come from being associated with this popular platform (over 100 million licenses of SharePoint have been sold). The purpose of this white paper is to address the perceived limitations that typically cause product companies to discount SharePoint when determining a technology roadmap for their products. This white paper will dive into some of the features of the platform, including how a company could build a better product faster and take advantage of the rapid adoption and increased market interest in SharePoint as a platform. Also described in this paper are the Connect, Extend, and Build On strategies and the advantages of each approach. 3 SharePoint Background SharePoint is now in its fourth version. It has matured over the past decade since its first versions
Load more

Recommended publications
  • A Response to Developing the Future
    A Response to DevelopingDeveloping tthehe FFutureuture Matthew Bishop Senior Director, Developer Platform Evangelism (DPE) Microsoft Ltd. Meeting the Challenges to Develop The Future Defining a New UK Knowledge Economy The paper, Developing the Future, addresses six aspects of the UK software development industry and identifies five key challenges. With a call to action that asks the Government, Academia and Industry to consider how they can work together to ensure that the UK software economy remains at the forefront of innovation. In this response to the challenges identified, Microsoft demonstrates that it is committed to a shared vision for software innovation that is having a dramatic impact on the workplace and society. Microsoft plays an important role in advancing technology in novel and innovative ways. Our business is founded on a visionary approach to solving real-world problems. From investment in research and development through to creating a strong partner community, we are driving success that has a quantifiable benefit to the UK economy. I invite you to read how Microsoft is rising to the five challenges identified in Developing the Future and to examine in detail how our vision will help develop the future of the new knowledge economy in the UK. Developing the Future THE UK SOFTWARE DEVELOPMENT INDUSTRY MICROSOFT MEETING THE CHALLENGES CONTENTS Innovation and Leadership - Vital to Global Success 4 Responding to: How can the UK meet the opportunities and challenges for globalisation? We Need Tomorrow’s Professionals - Today
    [Show full text]
  • The Role of an Architect
    Learn the discipline, pursue the art, and contribute ideas at www.ArchitectureJournal.net Resources you can build on. Journal 15 The Role of an Architect We Don’t Need No Architects! Becoming an Architect in a System Integrator Architecture Journal Profi le: Paul Priess The Open Group’s Architect Certifi cation Programs The Need for an Architectural Body of Knowledge A Study of Architect Roles by IASA Sweden The Softer Side of the Architect An A-Z Guide to Being an Architect ® Contents TM Journal 15 Foreword 1 by Simon Guest We Don’t Need No Architects 2 by Joseph Hofstader What does an architect do? What should an architect do? Join Joseph Hofstader as he examines the role of an architect. Becoming an Architect in a System Integrator 7 by Amit Unde In this article, Amit Unde explores the skills that aspiring architects need in a leading System Integrator. Architecture Journal Profi le: Paul Preiss 10 We chat with Paul Preiss, founder of a nonprofi t group called IASA (International Association of Software Architects). The Open Group’s Architect Certifi cation Programs 13 by Leonard Fehskens Join Leonard Fehskens as he outlines one of the industry’s architect certifi cation programs, Open Group’s ITAC (IT Architect Certifi cation). The Need for an Architectural Body of Knowledge 17 by Miha Kralj Miha Kralj covers an Architectural Body of Knowledge, an effort led by the Microsoft Certifi ed Architect community. A Study of Architect Roles by IASA Sweden 22 by Daniel Akenine Discover a perspective of architect roles through a recent study conducted by the local IASA chapter in Sweden.
    [Show full text]
  • What Is ASP.NET?
    Welcome to the ASP.NET QuickStart Tutorial Getting Started Introduction The ASP.NET QuickStart is a series of ASP.NET samples and What is ASP.NET? supporting commentary designed to quickly acquaint Language Support developers with the syntax, architecture, and power of the ASP.NET Web programming framework. The QuickStart ASP.NET Web Forms samples are designed to be short, easy-to-understand Introducing Web Forms illustrations of ASP.NET features. By the time you have Working with Server Controls completed the QuickStart tutorial, you will be familiar with: Applying Styles to Controls Server Control Form Validation ● ASP.NET Syntax. While some of the ASP.NET Web Forms User Controls syntax elements will be familiar to veteran ASP developers, several are unique to the new Data Binding Server Controls framework. The QuickStart samples cover each Server-Side Data Access element in detail. Data Access and Customization ● ASP.NET Architecture and Features. The Working with Business Objects QuickStart introduces the features of ASP.NET that Authoring Custom Controls enable developers to build interactive, world-class Web Forms Controls Reference applications with much less time and effort than ever before. Web Forms Syntax Reference ● Best Practices. The QuickStart samples demonstrate the best ways to exercise the power of ASP.NET Web Services ASP.NET while avoiding potential pitfalls along the Introducing Web Services way. Writing a Simple Web Service Web Service Type Marshalling What Level of Expertise Is Assumed in the Using Data in Web Services QuickStart? Using Objects and Intrinsics If you have never developed Web pages before, the The WebService Behavior QuickStart is not for you.
    [Show full text]
  • Exam Ref 70-482: Advanced Windows Store App Development Using HTML5 and Javascript
    Exam Ref 70-482: Advanced Windows Store App Development Using HTML5 and JavaScript Roberto Brunetti Vanni Boncinelli Copyright © 2013 by Roberto Brunetti and Vanni Boncinelli All rights reserved. No part of the contents of this book may be reproduced or transmitted in any form or by any means without the written permission of the publisher. ISBN: 978-0-7356-7680-0 1 2 3 4 5 6 7 8 9 QG 8 7 6 5 4 3 Printed and bound in the United States of America. Microsoft Press books are available through booksellers and distributors worldwide. If you need support related to this book, email Microsoft Press Book Support at [email protected]. Please tell us what you think of this book at http://www.microsoft.com/learning/booksurvey. Microsoft and the trademarks listed at http://www.microsoft.com/about/legal/ en/us/IntellectualProperty/Trademarks/EN-US.aspx are trademarks of the Microsoft group of companies. All other marks are property of their respec- tive owners. The example companies, organizations, products, domain names, email ad- dresses, logos, people, places, and events depicted herein are fictitious. No association with any real company, organization, product, domain name, email address, logo, person, place, or event is intended or should be inferred. This book expresses the author’s views and opinions. The information con- tained in this book is provided without any express, statutory, or implied warranties. Neither the authors, Microsoft Corporation, nor its resellers, or distributors will be held liable for any damages caused or alleged to be caused either directly or indirectly by this book.
    [Show full text]
  • ASP.NET 4 and Visual Studio 2010 Web Development Overview
    ASP.NET 4 and Visual Studio 2010 Web Development Overview This document provides an overview of many of the new features for ASP.NET that are included in the.NET Framework 4 and in Visual Studio 2010. Contents Core Services .....................................................................................................................................3 Web.config File Refactoring ...................................................................................................................... 3 Extensible Output Caching ........................................................................................................................ 3 Auto-Start Web Applications .................................................................................................................... 5 Permanently Redirecting a Page ............................................................................................................... 7 Shrinking Session State ............................................................................................................................. 7 Expanding the Range of Allowable URLs ................................................................................................... 8 Extensible Request Validation .................................................................................................................. 8 Object Caching and Object Caching Extensibility ...................................................................................... 9 Extensible HTML, URL, and HTTP Header
    [Show full text]
  • Contents Contents
    Contents Contents ........................................................................................................................................................ 1 1 Introduction ............................................................................................................................................... 4 Samples and Examples .............................................................................................................................. 4 2 Prerequisites .............................................................................................................................................. 4 3 Architecture ............................................................................................................................................... 4 Direct to On-Prem ..................................................................................................................................... 4 Azure Cloud ............................................................................................................................................... 5 Service On-Prem ....................................................................................................................................... 6 4 Why Choose the Microsoft Technology Stack? ......................................................................................... 7 Rapid Application Development ............................................................................................................... 7 C# .........................................................................................................................................................
    [Show full text]
  • Microsoft CRM – Typical Customizations
    Microsoft CRM – Typical Customizations by Andrew Karasev Microsoft CRM was designed to be easily customizable. Microsoft CRM Software Development Kit (MS CRM SDK) which you can download from Microsoft website contains descriptions of the objects or classes, exposed for customization. It has sample code in C# and partially in VB.Net. In Visual Studio.Net you can analyze all the classes, used by Microsoft developers to create MS CRM - you will discover that most of them are not documented in MS CRM SDK. Microsoft will not support your customization if you use undocumented class or do direct SQL access to CRM database. Let us describe you - programmer, software developer typical cases of MS CRM Customizations. 1. Integration with SQL Server application. If you have legacy system on MS SQL Server - let's say you are transportation company and have in-house developed cargo tracking database. Now in MS CRM you want lookup the shipments for the customer (or account in CRM). This is SDK programming and calling SQL stored proc to retrieve cargo info. Instead of SQL Server you can have other database (ORACLE, MS Access, PervasiveSQL to name a few) - you can access multiple Database platforms via ADO.Net connection from your .Net application, which is easily integrated into MS CRM Account screen. 2. Email capturing in MS CRM. You have customer with email [email protected]. Now you want all the emails that you receive from customer.com domain to be attached to Bill who is account in CRM. This is more difficult customization - you have to create MS CRM SDK web service, that one will be creating email activity and call it from COM+ application - Microsoft Exchange event handler (ONSYNCSAVE database event sink).
    [Show full text]
  • Moving Applications to the Cloud, 2Nd Edition Patterns & Practices
    Moving Applications to the Cloud, nd 2 Edition patterns & practices Summary: This book demonstrates how you can adapt an existing, on-premises ASP.NET application to one that operates in the cloud. The book is intended for any architect, developer, or information technology (IT) professional who designs, builds, or operates applications and services that are appropriate for the cloud. Although applications do not need to be based on the Microsoft Windows operating system to work in Windows Azure, this book is written for people who work with Windows-based systems. You should be familiar with the Microsoft .NET Framework, Microsoft Visual Studio, ASP.NET, and Microsoft Visual C#. Category: Guide Applies to: Windows Azure SDK for .NET (includes the Visual Studio Tools for Windows Azure), Windows Azure SQL Database, Microsoft SQL Server or SQL Server Express 2008, Windows Identity Foundation, Enterprise Library 5, WatiN 2.0, Microsoft Anti-Cross Site Scripting Library V4, Microsoft .NET Framework version 4.0, Microsoft Visual Studio 2010 Source: MSDN Library(patterns & practices) (link to source content) E-book publication date:June 2012 Copyright © 2012 by Microsoft Corporation All rights reserved. No part of the contents of this book may be reproduced or transmitted in any form or by any means without the written permission of the publisher. Microsoft and the trademarks listed at http://www.microsoft.com/about/legal/en/us/IntellectualProperty/Trademarks/EN-US.aspx are trademarks of the Microsoft group of companies. All other marks are property of their respective owners. The example companies, organizations, products, domain names, email addresses, logos, people, places, and events depicted herein are fictitious.
    [Show full text]
  • Special Characters A
    Index Special Characters AddAttributesToRender method, overriding, & (ampersand) character, QueryString 681, 691, 724, 777 encryption, 635 AddBezier method, 793 & operator, 499 AddBeziers method, 793 * (asterisk) character, XPath expression, 476 AddClosedCurve method, 793 * wildcard operator, 500, 505 AddCurve method, 793 @ (at sign) character, XPath expression, 477 AddEllipse method, 793 | (pipe) character, XPath expression, 477 AddLine method, 793 < > (brackets) characters, XPath expression, AddLines method, 793 477 AddNew method, 315 = (equal sign) character, QueryString AddParsedSubObject method, 706, 749 encryption, 635 AddPath method, 793 : (colon) character, namespace prefix, xmlns, AddPie method, 793 458 AddPolygon method, 793 . (dot) character, XPath expression, 477 AddRectangle method, 793 / (forward slash) character, XPath expression, AddRectangles method, 793 477 AddString method, 793 . (period) character, XPath expression, 477 AddStyleAttribute method, 674 \ in Path, 503 Administrator enumeration, ? wildcard operator, 500, 505 WindowsBuiltInRole, 592 ADO vs. ADO.NET, 276–78 A ADO.NET, 407–24, 426, 428, 431, 433–44, Abandon session state settings, 248 446–51 abstract encryption classes, 624 advanced grids, 433–41, 443 AcceptChanges, DataSet Version-Tracking, overview, 433 313, 334–36 parent/child view, 433–36 access, anonymous, 589, 596, 617 parent/child view in single table, access control lists (ACLs), 608 440–41, 443 AccessKey property, 149 parent/child/detail view, 437–38 account tokens, 596–97 summaries in DataGrid, 438–40
    [Show full text]
  • Tornadoproxyhandlers Documentation
    tornadoproxyhandlersDocumentation Release 0.0.5 Tim Paine Oct 15, 2020 Contents 1 Install 3 2 Overview 5 3 Use 7 4 API Documentation 9 Python Module Index 11 Index 13 i ii tornadoproxyhandlersDocumentation; Release0:0:5 Tornado proxy handlers for HTTP requests and web sockets Build Status Coverage License PyPI Docs Contents 1 tornadoproxyhandlersDocumentation; Release0:0:5 2 Contents CHAPTER 1 Install pip install tornado-proxy-handlers or from source python setup.py install 3 tornadoproxyhandlersDocumentation; Release0:0:5 4 Chapter 1. Install CHAPTER 2 Overview This project contains 2 proxy handlers: • HTTP Handler • Websocket Handler The websocket handler requires the http handler for 599 protocol switching. 5 tornadoproxyhandlersDocumentation; Release0:0:5 6 Chapter 2. Overview CHAPTER 3 Use These are designed to be embedded in a tornado server that needs to proxy. They can also be run as a standalone proxy server via the tornado-proxy command. 7 tornadoproxyhandlersDocumentation; Release0:0:5 8 Chapter 3. Use CHAPTER 4 API Documentation class tornado_proxy_handlers.handlers.ProxyHandler(application: tor- nado.web.Application, request: tor- nado.httputil.HTTPServerRequest, **kwargs) Bases: tornado.web.RequestHandler get(url=None) Get the login page initialize(proxy_url=’/’, **kwargs) class tornado_proxy_handlers.handlers.ProxyWSHandler(application: tor- nado.web.Application, request: tor- nado.httputil.HTTPServerRequest, **kwargs) Bases: tornado.websocket.WebSocketHandler initialize(proxy_url=’/’, **kwargs) on_close() Invoked when the WebSocket is closed. If the connection was closed cleanly and a status code or reason phrase was supplied, these values will be available as the attributes self.close_code and self.close_reason. Changed in version 4.0: Added close_code and close_reason attributes. on_message(message) Handle incoming messages on the WebSocket This method must be overridden.
    [Show full text]
  • Installation Guide for Microsoft SQL Server With
    Informatica® Multidomain MDM 10.4 Installation Guide for Microsoft SQL Server with Oracle WebLogic Informatica Multidomain MDM Installation Guide for Microsoft SQL Server with Oracle WebLogic 10.4 July 2020 © Copyright Informatica LLC 2001, 2020 This software and documentation are provided only under a separate license agreement containing restrictions on use and disclosure. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica LLC. U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation is subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License. Informatica, the Informatica logo, and ActiveVOS are trademarks or registered trademarks of Informatica LLC in the United States and many jurisdictions throughout the world. A current list of Informatica trademarks is available on the web at https://www.informatica.com/trademarks.html. Other company and product names may be trade names or trademarks of their respective owners. Portions of this software and/or documentation are subject to copyright held by third parties. Required third party notices are included with the product. The information in this documentation is subject to change without notice.
    [Show full text]
  • The Long Tail / Chris Anderson
    THE LONG TAIL Why the Future of Business Is Selling Less of More Enter CHRIS ANDERSON To Anne CONTENTS Acknowledgments v Introduction 1 1. The Long Tail 15 2. The Rise and Fall of the Hit 27 3. A Short History of the Long Tail 41 4. The Three Forces of the Long Tail 52 5. The New Producers 58 6. The New Markets 85 7. The New Tastemakers 98 8. Long Tail Economics 125 9. The Short Head 147 iv | CONTENTS 10. The Paradise of Choice 168 11. Niche Culture 177 12. The Infinite Screen 192 13. Beyond Entertainment 201 14. Long Tail Rules 217 15. The Long Tail of Marketing 225 Coda: Tomorrow’s Tail 247 Epilogue 249 Notes on Sources and Further Reading 255 Index 259 About the Author Praise Credits Cover Copyright ACKNOWLEDGMENTS This book has benefited from the help and collaboration of literally thousands of people, thanks to the relatively open process of having it start as a widely read article and continue in public as a blog of work in progress. The result is that there are many people to thank, both here and in the chapter notes at the end of the book. First, the person other than me who worked the hardest, my wife, Anne. No project like this could be done without a strong partner. Anne was all that and more. Her constant support and understanding made this possible, and the price was significant, from all the Sundays taking care of the kids while I worked at Starbucks to the lost evenings, absent vacations, nights out not taken, and other costs of an all-consuming project.
    [Show full text]