Showing posts with label SharePoint 2010 Transition. Show all posts
Showing posts with label SharePoint 2010 Transition. Show all posts
5

My Favourite SharePoint 2010 Enhancements (for developer) part 1

There are a number of platform and tool enhancements for SharePoint 2010.

I picked out a few favourites which I briefly explain below:
  • LINQ to SharePoint (Language Integrated Query)
  • Data Platform Improvements
  • List Enhancements
  • Business Connectivity Services
  • Silverlight Integration
  • Managed Client Object Model
  • Sandbox Solutions
  • Visual Studio 2010 for SharePoint
  • WSP Changes
  • Developer Dashboard
  • Dialog Framework
  • SharePoint Designer 2010
  • Visio Services
  • InfoPath (changes)
  • Windows PowerShell
LINQ to SharePoint (Language Integrated Query)
LINQ is a feature of the programming languages C# and Microsoft Visual Basic .NET. Compilers are included with Visual Studio.
LINQ adds a SQL-like syntax and vocabulary to each of the languages, which can be used to query data sources. But unlike other languages and query syntaxes which vary from one type of data source to another, LINQ can be used to query, in principle, any data source whatsoever. For this reason, developers may find that it is the only query syntax that they ever need to know.
The LINQ to SharePoint Provider is defined in the Microsoft.SharePoint.Linq namespace. It translates LINQ queries into Collaborative Application Markup Language (CAML) queries. more details here...


Data Platform Improvements
The data platform improvements include: List Relationships, Unique Column Constraints, Data Validation, Column Formula Validation, etc
more details here...

List Enhancements
The list enhancements in SP2010 include: Bulk Operations, New capacity limits(more details here..), XSLT Views (more details here..)

Business Connectivity Services (BCS)
BCS is a set of services and features that provide a way to connect SharePoint solutions to sources of external data and to define external content types that are based on the external data. External content types resemble content types and allow the presentation of and interaction with external data in SharePoint lists (known as external lists), Web Parts, Microsoft Outlook 2010, Microsoft SharePoint Workspace 2010, and Microsoft Word 2010 clients. External systems that Microsoft Business Connectivity Services can connect to include SQL Server databases, SAP applications, Web services (including Windows Communication Foundation Web services), custom applications, and Web sites based on SharePoint. more details here...

Silverlight Integration
In Windows SharePoint Services 3.0, you could host a Microsoft Silverlight application in a Web Part. Microsoft SharePoint Foundation 2010 goes beyond by providing a built-in, extensible, Silverlight Web Part specifically designed to host Silverlight applications. Closely related to the new Web Part is Silverlight Cross-Domain Data Access (Silverlight CDA) that enables secure, cross-domain, integration between Silverlight applications and SharePoint Foundation deployments, and Silverlight CDA can be used by non-Silverlight external applications as well. more details here...

Managed Client Object Model
The SharePoint Foundation 2010 managed client object model lets you write client-side code to work with all the common objects in SharePoint sites. Through the object model, you can add and remove lists, add, update, and delete list items, change documents in document libraries, create sites, manage permissions of items, and add and remove Web Parts from a page.
With the SharePoint Foundation 2010 managed client object model, you can design client applications that access SharePoint content without installing code on the server that runs Microsoft SharePoint Foundation 2010. For example, you can build new categories of applications that include writing applications that are based on the Microsoft .NET Framework, rich interactive Web Parts, Microsoft Silverlight applications, and ECMAScript (JavaScript, JScript) applications that run client-side in a SharePoint Web Part.
more details here...

Sandbox Solutions
You can deploy a Microsoft SharePoint Foundation 2010 solution directly onto your SharePoint Foundation farm, or you can deploy the solution into a sandbox. A sandbox is a restricted execution environment that enables programs to access only certain resources, and that keeps problems that occur in the sandbox from affecting the rest of the server environment.
Solutions that you deploy into a sandbox, cannot use certain computer and network resources, and cannot access content outside the site collection they are deployed in.
more details here... and here.

Visual Studio 2010 for SharePoint
A number of areas for SharePoint developers in Visual Studio 2010 are worth mentioning. First, you get SharePoint project templates in the box, so you can start right away on solution development. Second, tooling has standardized on the Windows SharePoint Package (WSP) packaging standard, so when you import or deploy a solution to SharePoint, Visual Studio treats it as a solution package. Third, some great deployment and packaging features, such as solution retraction and custom deployment configurations, ship with the SharePoint tools in Visual Studio 2010. And last, the new SharePoint Explorer provides a view into native and custom artifacts (for example, lists and workflows) that exist on your SharePoint server.

WSP Changes
SharePoint 2010 improves the WSP format so that it is supported across all tools, allowing you to export your site through the browser, SharePoint Designer, and Visual Studio. This means that you can quickly upgrade or downgrade your solutions between the tools.
SharePoint Online, the Microsoft - hosted version of SharePoint, supports this format so that you can move solutions to the cloud without having to rework the package.

Developer Dashboard
The developer dashboard is a new feature in SharePoint 2010 that is design to provide additional performance and tracing information that can be used to debug and troubleshoot issues with page rendering time. The dashboard is turned off by default, but can be enabled via the object model or stsadm (and PowerShell too, I just haven’t put together the script for it yet). When the dashboard is turned on you will find information about the controls, queries and execution time that occur as part of the page rendering process; this information appears at the bottom of the page.

Dialog Framework
SharePoint 2010 has a new framework for showing dialogs to the end-user. The dialogs allow people to work with some data without losing focus on the page they were working on to get things done. Closing the dialog will often cause AJAX based refreshes to give a sense of stateful-ness.
The dialog is of course extensible through JavaScript code. You can either show a separate page, or use a DOM element on the source page and show that. You can then determine when the dialog closes and what happens when it has closed.
more details here...

SharePoint Designer 2010
There have been a large number of changes to SharePoint Designer.
For a nice overview go to this post

Visio Services
Visio Services in Microsoft SharePoint Server 2010 is a service application that lets users share and view Microsoft Visio Web drawings. The service also enables data-connected Microsoft Visio 2010 Web drawings to be refreshed and updated from various data sources.
Visio Web drawings (*.vdw files) can be rendered by Visio Services and viewed in a Web browser. This lets users view Visio documents without having Visio or the Visio Viewer installed on their local computer. Basic exploration and navigation of these rendered Web drawings are supported within the Visio Web Access Web Part. Page designers can configure the user interface and functionality of the Web Part.
Visio Services can also refresh the data and recalculate the visuals of a Visio Web drawing hosted on a Microsoft SharePoint Server 2010 site. This enables published Web drawings to refresh connections to various data sources and to update affected data graphics and text fields. more details here...

InfoPath 2010 (changes)
InfoPath 2010 comes with a large number of enhancements which includes:
Easy customization of list forms with InfoPath, an InfoPath Form Web Part, Forms with code-behind can be deployed using sandbox solutions, creating a site template will produce a WSP package which includes the InfoPath forms, Forms Services forms now support WCAG 2.0 standard, InfoPath forms can be made available offline using SharePoint Workspace 2010, Forms Services also support FireFox and Safari.
more details here... and here.

PowerShell for SharePoint 2010
Windows PowerShell is a command-line scripting tool that provides an administrator full access to applicable application programming interfaces (APIs), along with the ability to unlock the capability to interact directly with SharePoint 2010 Products to manipulate Web applications, site collections, sites, lists and much more. In addition, the administrator has the ability to script cmdlets (pronounced "command-lets"), which makes for an improved experience from past product versions.  more details here... and here

Other enhancements (not covered in this post):
Access Services
Central Administration (Redesigned)
Digital Asset Management
Enterprise Search
Excel Services
Health Monitoring
Managed Metadata
PerformancePoint Services
Enhanced Records Management
Changes to Social Computing (previous called Collaboration)
Upgrade

Enjoy !!

2

Transition to SP2010: Impact on developer part1

Solution Architects (and developers) need to be aware of a few changes between SharePoint 2007 and SharePoint 2010.
Keep this in mind when upgrading SharePoint 2007 or WSS 3.0 web parts or custom code to SharePoint 2010.


WSS 3.0 to SharePoint Foundation 2010:
Deprecated features (will eventually be removed):

  • Stsadm command-line tool: The Stsadm command-line tool will be superseded by Windows PowerShell 2.0.
Features and functionality no longer available in SharePoint Foundation 2010:
  • 32-bit operating systems: SharePoint Foundation 2010 requires a 64-bit operating system.
  • Side-by-side installation: The ability to perform side-by-side installation of Windows SharePoint Services 3.0 and SharePoint Foundation 2010 on the same server is being removed.
  • Gradual upgrade: Support for the gradual upgrade feature is being removed as part of the removal of Side-by-side installation.
  • Web discussions:Web discussions enable users to add comments about documents and pages without modifying their actual content. SharePoint Foundation 2010 does not support Web discussions.
  • SQL Server 2000 data sources: SQL Server 2000 does not fully support many of the newer data features available in SharePoint Foundation 2010 and have been removed.
  • ODBC data sources: Newer and more versatile database connection options have replaced the functionality of ODBC.
  • Version 3 themes: The functionality provided in the version 3 themes is not available in the newly designed version 4 themes.The new version architecture is not compatible with the architecture of version 3 themes.
  • Web bot software agents: Search crawlers and indexers are examples of Web bots. Developers can no longer use Web bot entry points and users cannot add Web bots to SharePoint Foundation 2010 sites. (Use Web Parts instead of Web bots.)
  • E-mail enabled groups and Microsoft SharePoint Directory Management service (DMS): The Microsoft SharePoint Directory Management service (DMS) connects SharePoint sites to an organization's user directory to provide enhanced e-mail features. If a SharePoint farm is using DMS, users cannot enable SharePoint groups to use e-mail.The type of authentication used in DMS is being replaced with claims authentication.)
  • Permissions for sub-webs: In SharePoint Foundation 2010, if you want to give different permissions to a sub-web, you must assign a separate permission level to the sub-web. Site collections that are upgraded from Windows SharePoint Services 3.0 and have these unique permission level structures will continue to work. However, the user interface in SharePoint Foundation 2010 does not have a way to edit an inherited permission level at the sub-web scope, so you cannot change them or create new permission level definitions of this type.
  • Internationalized domain names: removed.
MOSS 2007 to SharePoint Server 2010:

Deprecated features (will eventually be removed):
  • Stsadm command-line tool
  • Site Directory feature:This functionality will be replaced by the social features of the User Profile service.
  • Scorecard export to Reporting Services.
  • Business Data Catalog: Replaced with Business Data Connectivity service.
Features and functionality no longer available in SharePoint Server 2010:
  • All features and functionality removed for SharePoint Foundation 2010 applies to SharePoint Server as well as the items listed below.
  • Office Web Components: The PivotChart, PivotTable, and Trend Chart report types are no longer available as options in the SharePoint Dashboard Designer.
  • Web discussions: Now use the Note Board feature.
  • Storage Management page: The Storage Management (storman.aspx) page is now removed from the Central Administration Web site.
  • Shared Services Provider (SSP): Service applications replace this functionality.
  • Site directory template: replaced by Enterprise Content Management (ECM) solutions.
  • News portal template:replaced by Enterprise Content Management (ECM) solutions.
  • Collaboration portal template: replaced by Enterprise Content Management (ECM) solutions.
Object Model:
There are also a number of Obsolete types and methods.
They will continue to work in your custom code and solutions, but they will generate compiler warnings, and you should update your code to use the new types.

The following site (http://code.msdn.microsoft.com/sps2010deprecated) contains 3 text files:

SPS2010NewlyDeprecated.txt lists the types and methods that have been made obsolete in Microsoft SharePoint Server 2010 since the release of Microsoft Office SharePoint Server 2007.
SPS2010Deprecated.txt lists all of the types and methods that are obsolete in Microsoft SharePoint Server 2010.
OfficeSharePointServer2007Deprecated.txt lists all of the types and methods that are obsolete in Microsoft Office SharePoint Server 2007.