Sharepoint 2010 Tutorial : what's new in web parts

Sharepoint 2010 Tutorial : what's new in web parts

SharePoint 2010 Web Casts

http://wssv4faq.mindsharp.com/Lists/v4WebCasts/AllItems.aspx

"LINQ for SharePoint 2010 part 1 - Introduction (Serge Luca)
12/26/2009SharePoint Server 2010
LINQ for SharePoint 2010 part 2 - Adding objects (Serge Luca)
12/26/2009SharePoint Server 2010
LINQ for SharePoint 2010 part 3 - Retrieving objects (Serge Luca)
12/26/2009SharePoint Server 2010
LINQ for SharePoint 2010 part 4 - Removing objects (Serge Luca)
12/26/2009SharePoint Server 2010
LINQ for SharePoint 2010 part 5 - Managing concurrency (Serge Luca)"

Signer - The Easy Way To Strong Name Your Assembli

Signer - The Easy Way To Strong Name Your Assembli: "Sign your unsigned assemblies AFTER you have built them. You can sign a whole bunch of unsigned assemblies with one public key while your strong named references are also updated at once. This is achieved by decompiling your assemblies with ILDASM to MSIL code, parsing and the IL code and doing the necessary modifications. After that a new assembly is created with ILASM and voila: Strong named assemblies. It has been tested with major projects (e.g. Enterprise Library Jan 2006) to validate that this approach works reliable."

Share Point List Filter ~ Moss 2007 WCM ~ SharePoint reports ~ kwizcom.com

Share Point List Filter ~ Moss 2007 WCM ~ SharePoint reports ~ kwizcom.com: "SharePoint List Filter Plus"

SharePoint 2010 Developer

SharePoint 2010 Developer - Beta
Sharepoint 2010 Logo

 

SharePoint 2010 provides the business collaboration platform for developers to rapidly build solutions using familiar tools while leveraging a rich set of out of the box features. Visual Studio 2010 and SharePoint Designer 2010 make developers more productive and Visual Studio Team Foundation Server delivers support for application lifecycle management. Developers can integrate Line of Business data in SharePoint 2010 with read/write capability delivered by Business Connectivity Services. Sandboxed Solutions can be deployed to a shared hosting environment to limit the impact of unpredictable code to the other applications in use.
Audience Prerequisites

 

Basic understanding of Microsoft Office, SharePoint and using Microsoft Visual Studio.
SharePoint

 

* Windows Server 2008 R2
* SQL Server 2008 64-bit
* SharePoint Server 2010 Beta

 

Office

 

* Office 2010 Beta
* Visual Studio 2010 Beta 2
* Open XML SDK 2.0

 

Units in this course

 

1. * Getting Started with SharePoint 2010
2. * SharePoint 2010 Developer Roadmap
3. * Visual Studio 2010 Tools for SharePoint 2010
4. * UI Enhancements
5. * Lists and Schemas
6. * LINQ to SharePoint
7. * Client Object Model
8. * Workflow
9. * Services Architecture
10. * Accessing External Data
11. * Enterprise Content Management
12. * Extending Search
13. * PerformancePoint Services
14. * Sandboxed Solutions
15. * Sharepoint 2010 Security

 

 

Getting Started with SharePoint 2010

 

Welcome to the SharePoint 2010 learning center. SharePoint 2010 includes numerous new capabilities and features for professional developers. In this welcome video you will hear from some of the team members behind the training kit to understand what the kit is all about and what are plans are for the future of the SharePoint learning center on Channel 9.

 

* Presentation: SharePoint 2010 Developer Presentations
* Video: Getting Started with SharePoint 2010

 

SharePoint 2010 Developer Roadmap

 

SharePoint 2010 includes numerous new capabilities and features for professional developers most of which are highlighted in this unit. SharePoint 2010 makes developing those solutions easier, quicker, and more flexible. Much of the work that the developer had to do in the past with earlier versions of SharePoint has been replaced with simple configuration of the SharePoint 2010 platform, use of Visual Studio 2010 and SharePoint Designer 2010 or with calls to the SharePoint API.

 

* Video: Whats New in SharePoint 2010
* Video: SharePoint 2010 Development Primer
* Video: New Developer Tools for SharePoint 2010
* Video: SharePoint 2010 Integration with PowerShell
* Lab: SharePoint 2010 Developer Roadmap Lab

 

Visual Studio 2010 Tools for SharePoint 2010

 

This unit will provide you with an overview of SharePoint development with Visual Studio 2010. Specific topics covered will include an overview of the project and item templates, a walkthrough of the designers included, and areas of extensibility within Visual Studio 2010 that can enhance SharePoint development. Visual Studio 2010 includes support out of the box for the most common types of projects that you may want to build with SharePoint 2010 as well as new features for more easily defining features, solutions, and wizards to walk through the most common settings for each project type.

 

* Video: Introduction to VS2010 SharePoint Tools
* Video: SharePoint Tools Project Structure
* Video: Adding SPIs to a Project
* Lab: SharePoint Development with Visual Studio 2010 Lab

 

UI Enhancements

 

The look and feel of SharePoint has radically changed from earlier versions of the product. In addition to being more accessible to the user it allows for improved extension points and fewer workarounds. The new user interface components that you can extend and build applications which include the fluent UI ribbon and an extensible dialog system.

 

* Video: The SharePoint Fluent User Interface
* Video: Sites as Collections of Pages
* Video: Managing Data with SharePoint 2010
* Lab: SharePoint 2010 UI Advancements Lab

 

Lists and Schemas

 

In a typical system data is somewhat normalized – not all of the system's data exists in one large table or list. Instead data exists in sets of tables or lists which have one entry for each entity across multiple tables.

 

* Video: New and Improved Events
* Video: List Relationships and Joins
* Video: Large List Support
* Video: Field and List Item Validation
* Lab: Lists and Schema Lab

 

LINQ to SharePoint

 

LINQ is a new data access paradigm which allows users to express SQL like syntax against a variety of data sources. LINQ can improve performance by allowing the back end data source to decide the best way to solve the query. SharePoint now fully supports LINQ for querying lists so that you can query information from the platform in a more condensed, easier to understand format.

 

* Video: Accessing SharePoint List Data
* Lab: Linq to SharePoint Lab

 

Client Object Model

 

In SharePoint 2010 there are a number of object models that can be used by developers to access the server. The Client Object Model (Client OM) is a unified model which uses the same or similar programming concepts as the Server Object Model (Server OM). The Client OM can be accessed via web services, via a client (JavaScript) API, and via REST.

 

* Video: Overview of the Client Object Model
* Video: Silverlight Client Object Model
* Video: ECMAScript Client Object Model
* Lab: Client Object Model Lab

 

Workflow

 

In SharePoint 2010 you can associate workflows with a site so you need not associate a workflow instance with a specific item in a list. Site-level workflows are a powerful mechanism to create generic functionality using the power of Windows Workflow Foundation (WF).

 

* Video: Whats New in SharePoint 2010 Workflow
* Video: Designing Workflows with SPD
* Video: Developing Workflows with VS 2010
* Lab: Workflow Lab

 

Services Architecture

 

In this session we will discuss the new Service Architecture model for SharePoint 2010. In SharePoint 2010 the Service platform has been re-written with a new more scalable and flexable architecture.

 

* Video: Architectural and Logical Overview
* Video: Creating Custom Service Applications

 

Accessing External Data

 

In SharePoint 2010 Business Connectivity Services (BCS) enables integration with back end systems. Business Connectivity Services includes a set of presentation features, a connectivity framework and tooling within SPD and Visual Studio that enable developers and ITPros to connect to external data and services and to surface this data in SharePoint 2010 and Office 2010.This session will provide an overview of the BCS capabilities and usage in SharePoint 2010.

 

* Video: Business Connectivity Services (BCS) Primer
* Video: Creating BCS Applications
* Video: Creating .NET Assembly Connectors in Visual Studio 2010 support
* Lab: Business Conectivity Services (BCS) Lab

 

Enterprise Content Management

 

From a free form Wiki to a highly controled intranet or internet site, learn about all of the new Web Content Management features in SharePoint 2010. This session will cover enhancements to the core authoring UI, publishing infrastructure, the content query webpart, and content deployment.

 

* Video: ECM and Enterprise Metadata
* Video: Advanced Routing and Document Sets
* Video: In Place Records Management
* Lab: Enterprise Content Management Lab

 

Extending Search

 

This session will provide an overview of the enterprise search product line in SharePoint 2010. We've brought together the best of SharePoint Search and FAST ESP, resulting in the most complete enterprise search product line in the industry. In this session we'll talk about our overall strategy for enterprise search and delineate each of the key search products in SharePoint 2010.

 

* Video: The Connector Framework
* Video: Enhancing the Search User Interface
* Video: Creating Custom Ranking Models
* Lab: Extending SharePoint Search Lab

 

PerformancePoint Services

 

There has been considerable investment in the Business Intelligence capabilities of SharePoint 2010. From new product capabilities like balanced scorecards, interactive dashboards, and line of business integration to improvements in Excel rendered content with Excel Services, improved and new capabilities for Self-Service information access, and creation of BI assets. In this session, we will cover the major components and identify the new capabilities.

 

* Video: Business Intelligence (BI) Primer
* Video: Excel Services
* Video: Performance Point Services
* Lab: Developing BI Applications Lab

 

Sandboxed Solutions

 

SharePoint 2010 adds a new deployment model for SharePoint called Sandboxed Solutions. It is a controlled solution packaging format that offers SharePoint Server Farm owners a way to easily mitigate risk that custom code will cause issues for them. It does this by restricting the API's that can be called and governing resources that can be used. Because of this Sandboxed Solutions provide a solution package that can be easily deployed to a shared server environment. This talk will describe what Sandboxed Solutions are, it will demonstrate how to create them with Visual Studio 2010 and how to deploy and monitor them on SharePoint farms.

 

* Video: Introducing Sandboxed Solutions
* Video: Executing Code in the Sandbox
* Lab: Sandboxed Solutions lab

 

Sharepoint 2010 Security

 

SharePoint Server 2010 incorporates a new, more powerful and flexible authentication model that works with any corporate identity system, including Active Directory® directory services, LDAP-based directories, application-specific databases, and new user-centric identity models such as LiveID. This model uses claims-based authentication and a new product, code-named “Geneva.” Claims-based authentication is built around the concept of an identity and is based on standards — WS-Federation, WS-Trust — and protocols like the Security Assertion Markup Language (SAML).

 

* Video: Introduction to Claims based Security

FireFox open link in new tab.

Hold down the CTRL key and left clink on link.

Writing CAML Queries For Retrieving List Items from a SharePoint List

PostRankWidget: "Introduction
The Collaborative Application Markup Language (better known as CAML) is an XML-based query language that helps you querying, building and customizing Web sites based on Windows SharePoint Services. The XML elements define various aspects of a WSS site.
In this first series of articles I will explain in detail how to build and execute CAML queries to retrieve list items from a SharePoint list. List items can be retrieved in several different ways: using the SharePoint object model, using the SharePoint Lists web service or even by using Powershell. Use the SharePoint object model when your code runs on the server (like f.e. when you’re developing a web part or an application page). Use the SharePoint Web Services when your code doesn’t run on the server where SharePointis installed, for example when you develop office clients or windows applications. Powershell, at the other side, can be used by administrators when they quickly need to retrieve some information. In any way the CAML query is the same."

File (.htm, xml, .txt...etc) Content View Web Part

File (.htm, xml, .txt...etc) Content View Web Part: "Project Description
This web part is ment to read the file content from the file systems and displays them as it is, it works both on MOSS 2007 & SharePoint 2010(Beta).

So far I've tested with .xml, .html, .txt, .word

Note: If the file type is html then it renders the htlm file in the web part.


Steps (WSS V3 / MOSS 2007):

1) Download the VITCS.FCViewWebPart.wsp package / solution from the downloads tab
2) Add solution file (VITCS.FCViewWebPart.wsp) to the centeral admin site solution store using stsadm
3) Deploy solution (VITCS.FCViewWebPart) to the desired web applicaiton in the centeral admin site
4) Activate the feature (VITCS.FCViewWebPart) in the site collection - this will add the web part (VITCS.FCViewWebPart) to the web part gallery
5) Edit the page and add the web part (VITCS.FCViewWebPart)
6) Edit the web part properties and set the input file location and save."

CodePlex Information and Discussion - Upload Project

CodePlex Information and Discussion: "Using TortoiseSVN with CodePlex


If you do not already have TortoiseSVN installed, you can download it here: http://tortoisesvn.net/downloadsGo to the Source Control tab of the CodePlex project and make a note of the 'Subversion URL'
Open Windows Explorer
Create a new folder where you want to download the source code of the CodePlex project
Right click on the new folder and select 'SVN Checkout...'
In the 'URL of repository' field enter the Subversion URL. Example: https://svnbridge.svn.codeplex.com/svn
Click OK on the SVN Checkout screen to start downloading the source code files for the project.

If you have any trouble using TortoiseSVN with CodePlex you can contact support using our Contact Us form."

Chris O'Brien: Blending publishing/collaboration functionality in SharePoint

Chris O'Brien: Blending publishing/collaboration functionality in SharePoint: "Blending publishing/collaboration functionality in SharePoint

Most often when creating SharePoint solutions, the requirements often map fairly well to one of the out-of-the-box site definitions which can be used to create new sites. If we're creating heavily-branded internet/intranet sites (WCM sites), we'll probably start with the 'publishing site' template. If we are deploying SharePoint in a document management/collaboration scenario, we'll probably start with the 'team site' template, and so on. Where it gets interesting it when the project requirements effectively have a mix of this functionality. Characteristics of such a site might include:

* site has completely bespoke look and feel/navigation
* users will work with files stored in document libraries
* site templates or definitions are used to create several sites with the same content/functionality
* custom workflow is used to support a business process (other than standard content publishing), perhaps with InfoPath forms

Such requirements present a few challenges, and a current project of mine fits into this category. At a high level, one consideration is that site users will also use 'system' pages provided by SharePoint in many scenarios (e.g. working with document libraries/lists, workflow etc.) and this doesn't happen in most WCM sites. This can lead to situations where there is a disparity between the look and feel of the 'published view' of the website and the 'system' areas. I don't intend to provide answers to all the issues here, but I do want to discuss a few as some food for thought. I'll probably revisit this post at the end of the project and provide a better insight into the issues and solutions, but for now let's cover some high-level decisions:"

Deployment overview (SharePoint Server 2010)

Deployment overview (SharePoint Server 2010): "Deployment overview (SharePoint Server 2010)

Updated: 2009-11-12

[This article is pre-release documentation and is subject to change in future releases.]

This article provides information about deploying Microsoft SharePoint Server 2010. The goal of this article is to provide information that can help you and your teams make fundamental decisions about deploying Microsoft SharePoint Server-based solutions in your organization.

A SharePoint Server solution can vary in complexity and size, depending on your business requirements.

The ideas presented in this article apply equally to all businesses—at the end of the deployment process you and your team want to have a SharePoint Server-based solution up and running.

In this article:

* Concepts

* Farm topologies

* Applying the information technology lifecycle to SharePoint 2010 Products

* Deployment scenarios

* Deploying a pilot or production farm"

Client Script in ASP.NET Web Pages

Client Script in ASP.NET Web Pages: "Client Script in ASP.NET Web Pages

ASP.NET Web applications are not limited to server-based tools and languages. You can include ECMAScript (JavaScript or JScript) in your ASP.NET Web pages to create rich browser-based functionality. A wide range of features for client script support is available in ASP.NET.

One option is to create and add individual snippets of client script to ASP.NET Web pages to support browser behavior that you design for your application. This option is practical if you want to include only a few small pieces of JavaScript code or if you are working with JavaScript code that you already have. This option also helps keep the size of your ASP.NET Web pages to a minimum.

Alternatively, you can take advantage of the powerful AJAX features of ASP.NET. These AJAX features include a complete framework that supports the following:

*

Object-oriented programming in JavaScript.
*

Asynchronous postbacks.
*

Application Web services for authentication and profiles.
*

Server controls that manage client script with extended debugging and trace support.

Using ASP.NET AJAX features lets you take advantage of JavaScript functionality with less manual coding. It provides extended JavaScript functionality, and it provides a framework for creating client functionality that is integrated into ASP.NET.

This topic provides an overview of options for adding client script to ASP.NET Web pages. It contains the following sections:

*

Scenarios
*

Including Custom Client Script in ASP.NET Pages
*

Extending JavaScript with ASP.NET AJAX Features
*

ASP.NET Server Controls That Depend on Client Script
*

Adding Client Script Events to ASP.NET Server Controls
*

Referencing Server Controls in Client Script
*

Raising Client Click Events for Server Controls
*

Communicating Between Client Script and Server Code
*

Creating Client Script Components
*

Adding Client Functionality to Server Controls"

Chapter 3: Pages and Design (Part 1 of 2)

Chapter 3: Pages and Design (Part 1 of 2): "This article is an excerpt from Inside Microsoft Windows SharePoint Services 3.0 by Ted Pattison and Daniel Larson, from Microsoft Press (ISBN 9780735623200, copyright 2007 by Microsoft Press, all rights reserved). No part of these chapters may be reproduced, stored in a retrieval system, or transmitted in any form or by any means—electronic, electrostatic, mechanical, photocopying, recording, or otherwise—without the prior written permission of the publisher, except in the case of brief quotations embodied in critical articles or reviews.

Download the sample code that accompanies the book

* Understand the benefits and restrictions of safe mode processing.

* Learn how to design site pages with controls and Web Part zones.

* Learn how to customize the master page used by site pages.

* Learn how to customize the Windows SharePoint Services navigation infrastructure.

* Learn best practices for branding Windows SharePoint Services sites."

Auto-Implemented Properties (C# Programming Guide)

Auto-Implemented Properties (C# Programming Guide): "Auto-Implemented Properties (C# Programming Guide)

In C# 3.0 and later, auto-implemented properties make property-declaration more concise when no additional logic is required in the property accessors. They also enable client code to create objects When you declare a property as shown in the following example, the compiler creates a private, anonymous backing field can only be accessed through the property's get and set accessors."

SPView object Query property update does not work.

"I've updated the query property of the view as show in the code but the view does not work unless I select the view/ modify the view and hit the Ok button using the user interface.

bottom line: programmatic update of query does not work as expected."

private void UpdateViewV2()
    {
        SPSite site = SPContext.Current.Site;
        SPSecurity.RunWithElevatedPrivileges(delegate()
        {
            using (SPSite elevatedPrivilegesSiteColl = new SPSite(site.ID))
            {
                using (SPWeb oWebsite = elevatedPrivilegesSiteColl.RootWeb)
                {
                    oWebsite.AllowUnsafeUpdates = true;
                    SPList oList = oWebsite.Lists[this.listName];
                    SPView oView = oList.Views[this.viewName];
                    oView.Query = ""+
                                                "" + this.strStartDate + ""+
                                                "" + this.strEndDate + ""+
                                    "";
                    oView.Update();
                    oList.Update();
                    oWebsite.AllowUnsafeUpdates = false;
                    oWebsite.Update();
                }
            }
        });
        site.Close();
    }

ListViewWebPart with Custom Filtered view

ListViewWebPart with Custom Filtered view: "I have any event receiver on a list (Fund) that automatically creates a web part page for the specified Fund. On the web part page I have a ListViewWebPart that displays a document library. I would like this doc library to only display documents that are associated to this Fund. I have been trying to modify the filter by updating the Query of the SPView, but have not been able to get it to work. I have also tried to use the FilterString property from the ListViewWebPart but this has also been unsuccessful."

Custom toolbar of a SPView object on SPLite

SaurabhKV : Custom toolbar of a SPView object on SPLite: "Custom toolbar of a SPView object on SPLite
Currently I’m in an engagement where I have to show the custom toolbar on a list view.
I started my code to create a new SPView and attach the same one with SPList, I’m able to change query, title etc properties of view. But once I started to change ToolBarType I was fail as it is a readonly property.
So I went to use a unsupported way to achieve the same, here is my code."

SPView.Query Property (Microsoft.SharePoint)

SPView.Query Property (Microsoft.SharePoint): "SPView.Query Property (Microsoft.SharePoint)
Gets or sets a string that contains the query for the view."

Fix Runtime Errors in Internet Explorer

Fix Runtime Errors in Internet Explorer: "Because this type of error message does not apply to you, you can prevent it from appearing. To do this, follow these steps in Internet Explorer:
Click the Tools button , and then click Internet Options. Or, press ALT+T, and then press O.
In the Internet Options dialog box, click the Advanced tab.
Click to select the Disable script debugging (Internet Explorer) and Disable script debugging (Other) check boxes, and then click to clear the Display a notification about every script error check box."

Calendar Web Part for SharePoint that displays and gives details of events from an event list

Introduction
This is a calendar part which displays events from an existing event list (dates highlighted), and also provides details about an event on the click of the event date.

Background
To create this WebPart, I chose the ASP.NET Calendar control and has overridden its OndayRender method to give colors to the dates with events.
The SharePoint object model (Microsoft.sharepoint.dll) is then used to pull the event details, displayed on the click of the date.

There are two classes used:
A class to highlight the event dates and to give colors to the dates of the calendar (e.g., gray for weekends).
A WebPart to create and render the Calender control and to display the event details pulled from the event list, on click of the highlighted date."