SharePoint
I am a fan of the Object Data Source control especially when binding objects to controls such as a GridView for ASP.NET web forms. Not a 'huge' fan, but a fan none the less. I find its ability to organize binding methods and events consistently makes it a decent option for binding, along with its ability to present the objects wired up in a strongly typed manner during configuration.
Using Caching on an Object Data Source and Making it Unique Per User
It is not always appropriate to enable custom buttons on the ribbon all the time. Sometimes one or multiple conditions have to be met to enable the button. As showed in one of my previous posts ‘ A better user experience with the dialog framework and notifications ‘ the attribute EnabledScript of the CommandUIHandler can be used to test when to enable or disable the button. The check in the example used in the previous post is quite simple and checks if one or more items are selected in the list. To perform other, less simplistic, checks, it is likely you have to use asynchronous calls when working with ECMA script.
Using async call to enable a custom ribbon button
SharePoint Bits Blog: Custom WCF Services in SharePoint 2010
SharePoint 2007 provided the capability to add custom ASMX web services. Web Services could be deployed to the LAYOUTS folder, or could be deployed to the ISAPI folder, and supported accessing site settings and list data under the SharePoint user context. Since SharePoint 2007 was built on the ASP.NET 2.0 model, it did not natively support web service enhancements that were introduced with Windows Communication Foundation (WCF) in .NET Framework 3.0 and 3.5 or the additional WCF-based service frameworks like ADO.NET Data Services (now WCF Data Services). For those familiar with writing custom ASMX services for 2007, there were some pitfalls. Since SharePoint requires dynamic service endpoints (the ability to call the web service using any site-relative virtual path under the /_vti_bin/ folder), you had to hand-tool a special ASPX page file to generate the WSDL that included script to generate the dynamic endpoint.
Summary: This chapter discusses Microsoft Silverlight features and tools, how to create a Silverlight Web Part, how to access SharePoint 2010 data by using the Client Object Model, and how to extend Microsoft Visual Studio to create Silverlight solutions. This article is an excerpt from Professional SharePoint Branding and User Interface Design by Randy Drisgill, John Ross, Jacob J. Sanford, and Paul Stubb, published by Wrox Press (ISBN 978-0-470-58463-7, copyright © 2010 by Wrox, 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. Contents
Chapter 14: Silverlight and SharePoint Integration (Professional SharePoint Branding and User Interface Design)
I have been doing a lot of “hobby” porting over the last couple months. By that I mean that I have done a lot of porting of projects (mostly to WP7, but in some cases I’m porting to Silverlight 4). I just recently decided that I really need to start releasing this stuff (on my blog at first but then later I will start submitting this stuff back to the original projects).
PowerCollections and C5 Collections for Silverlight4 - JayKimble.net
Introduced with SharePoint 2010, the Client Object Mode helps developers design client applications that access SharePoint content without installing code on the server. The Client Object Model can run directly on client machines without having been installed on the SharePoint server. An article on MSDN tells us that the SharePoint 2010 Client Object Model supports "three new client APIs for interacting with Sharepoint sites: from a .NET managed application, from a Microsoft Silverlight application, or from ECMAScript (JavaScript, JScript) that executes in the browser." In this post, we will explore and utilize the Silverlight Client Object Model. Challenge:
SharePoint 2010 Cookbook: Using the Silverlight Client Object Model in SharePoint 2010 to Create a Silverlight Web Part - SharePoint 2010
Blogs
I am in training this week with Andrew Connell (by far the best SharePoint training I have ever attended), learning about SharePoint development. As I get started with my deep dive into learning SharePoint, something that comes up a lot is the need to find the public key token of the current .NET assembly. He just showed a great shortcut. In Visual Studio, go to the Tools menu and choose External Tools.
Updated: January 22, 2013 Summary: Learn how to create forms-based authentication for claims-based web applications by using ASP.NET SQL membership and role providers. Applies to: Microsoft SharePoint Foundation 2010 | Microsoft SharePoint Server 2010
Claims Walkthrough: Creating Forms-Based Authentication for Claims-Based SharePoint 2010 Web Applications Using ASP.NET SQL Membership and Role Providers
Recently I needed to deploy a SharePoint document library as a feature, but with some documents already in it. In my case it was because of demo content, the customer wanted to do some training and needed a pre-filled document library. I can see this useful in other times however, such as including templates for documents, etc. The solution for this is not difficult, but since I could not find any instructions online for this I thought I'd write a post.
Deploying a Document Library including content using a Feature
Deploying Branding Solutions for SharePoint 2010 Sites Using Sandboxed Solutions
Summary: Learn how to create sandbox-compatible branding solutions by using custom master pages, CSS files, and images that can be deployed to Microsoft SharePoint 2010 farms. Applies to: Microsoft SharePoint Foundation 2010 | Microsoft SharePoint Server 2010 | Microsoft Visual Studio 2010 There is only one way to deploy a business solution that is developed for the preceding version of SharePoint Products and Technologies.