Even More Resources for SharePoint Developers

Kemp first shared a lengthy list of SharePoint developer resources at http://blogs.msdn.com/b/vssharepointtoolsblog/archive/2010/08/12/resources-for-visual-studio-tools-for-sharepoint-developers.aspx. In addition to these, there are articles and videos that are published in the Technical Articles and Visual How Tos nodes. In addition to the documentation, technical articles, and visual how-tos, you can also read Book Excerpts and Quick Notes. Here is a…

0

Check out the new SharePoint in Pictures blog

There is a new blog called SharePoint in Pictures that illustrates the platform and architecture of SharePoint Foundation 2010 and SharePoint Server 2010.  The blog is to be updated on a weekly basis with new diagrams, so feel free to check it out and leave feedback about what you’d like to see in the near…

0

Resources for Visual Studio Tools for SharePoint Developers

Nearly all of the tools for SharePoint development included in Visual Studio 2010 are new, so learning about them and finding help and information can be a challenge. To help you in this quest, I’ve compiled a list of links to helpful resources, including product documentation, web sites, forums, and blogs. As new resources become available,…

1

Walkthrough of creating association between Sharepoint BDC entities using Visual Studio 2010

Up till now, we have published two blogs in this series about SharePoint 2010 external list, Walkthrough of creating a SharePoint 2010 external list using Visual Studio 2010 Beta and Walkthrough of enabling CRUD for SharePoint 2010 external lists using Visual Studio 2010. Now you are able to create external list and add basic CRUD…

3

Deploy your BDC model to a specific BCS Service using Visual Studio 2010

When deploying a BDC model in Visual Studio 2010, some people may see this error message “… There is no default Business Data Connectivity Service Proxy available for the given SPServiceContext…” or similar ones. This probably means the SiteUrl feature property is not appropriately set. SiteUrl is a SharePoint feature property that determines where a…

0

Using Deployment Step events to add functionality to Deployment Configuration

With the help of the extensibility features in the SharePoint tools in Visual Studio, you can add functionality to deployment configurations by subscribing to the DeploymentStepStarted and DeploymentStepCompleted events. To learn more about deployment configurations and deployment steps in SharePoint projects, refer to the MSDN article here. In this blog post I will show you…

0

Extending the SharePoint Tools in Visual Studio: An Overview

Since you’re reading this blog, you’re probably aware that Visual Studio 2010 includes an all-new set of tools for creating SharePoint solutions for Microsoft SharePoint Foundation 2010 and Microsoft SharePoint Server 2010. These tools include a set of project and item templates for developing various types of solutions, integrated Feature and packaging support (with designers), and…

0

Deploying documents with content types and associating content types with libraries (Part III)

Part III: Using Feature Event Receiver to create a library and associate a content typeIn previous post we showed how to use ContentTypeBinding to bind the content type to an existing document library. In this post, we will learn how to achieve similar results but using the feature event receiver. In this post we will…

0

The Visual Studio 2010 SharePoint Power Tools are now available!

The Visual Studio team that brought you the SharePoint developer tools in Visual Studio 2010 is happy to announce we have created a set of power tools that make developing SharePoint 2010 sandboxed solutions even easier.  Below is the list of features included in the current release of the power tools.   Sandboxed-compatible Visual Web…

6

Deploying documents with content types and associating content types with libraries (Part II)

Using ContentTypeBinding to associate content types with lists In previous post we showed how to deploy a document and associate it with a content type. Even though the deploying and associating the document with content types was fairly easy we still had to manually associate the content type with desired document library. In this post…

0