Vighnesh Bendre - MS technologies

Setting up Continuous Integration for the code in a project is a common procedure followed in projects. The Continuous Integration (CI) becomes more important in development projects using Agile methodology or for geographically distributed teams. You can create build definitions in Team Foundation Server (TFS) 2010 to build your codebase. But the important question is – how do you setup CI for SharePoint projects? Because by TFS 2010 build agent will not be able to compile SharePoint code. This is because SharePoint code refers to the SharePoint assemblies. And these SharePoint assemblies are not available in the server where the TFS is configured. You could ask why don’t we just install SharePoint 2010 on the same server as TFS 2010. Installing SharePoint 2010 on TFS 2010 server is not recommended for performance reasons obviously. So, the easiest way to successfully compiling SharePoint 2010 code on TFS 2010 server is to copy the SharePoint 2010 assemblies on the build server. ...

There are many situations when you want to migrate data from SharePoint 2007 (MOSS) to SharePoint 2010. Microsoft has provided lot of material on upgrade or migrate to SharePoint 2010. This is the best starting point. I also have written about the steps to upgrade or migrate TFS 2008 team portals to TFS 2010 team portals. Basically I have considered upgrading and migrating from SharePoint 2007 to SharePoint 2010. You can find the blog post here ... But a situation may also arise where you are required to migrate only certain lists or libraries. In this blog post we will see how you can migrate only certain lists or libraries. The approach for migrating SharePoint 2007 lists and libraries is to save them as list templates with content and migrate them to SharePoint 2010 site. But unfortunately SharePoint 2007 list templates (version 3) are not supported in SharePoint 2010. For this reason, we have to convert SharePoint 2007 list templates to be SharePoint 2010 compatible. Fo...

      1.1 Introduction Microsoft SharePoint Foundation 2010 has been designed for scale and performance and as such requires new hardware and software requirements. There are 3 major steps while upgrading. 1. Plan and Prepare 2. Perform a database attach upgrade 3. Verify upgrade 1.2 Plan and Prepare   Before we run any process to upgrade from Windows SharePoint Services 3.0 to Microsoft SharePoint Foundation 2010, we have to determine which upgrade approach to take. In our scenario, Database Attach Upgrade seems to be appropriate approach to follow. We can upgrade the content for the environment on a separate farm. The result is that you do not upgrade any of the services or farm settings. You can upgrade the databases in any order and upgrade several databases at the same time. While each database is being upgraded, the content in that database is not available to users. 1.2.1 Upgrade Approach A database attach upgrade enables you to move to...