Recently I showed you how you can import List Instances and their data to your SharePoint Project so that you can reuse test data during the development process. If however creating test Features is too much work for you and you are more of a PowerShell guy this article might be just the right thing for you. Find out how to provision List Instance data using PowerShell.
In my previous article I showed you how you can import List Instances and their data using the Mavention Import List Instance extension. In this article I will show you how to clean the imported List Instance by removing unnecessary fields.
When working with custom Lists you find yourself often redeploying the List and creating some test data to verify that everything is working correctly. Entering sample data may be fun to do once but becomes rather boring after a few times. Find out how to reuse your sample data in the development process using Mavention Import List Instance.
When building SharePoint Projects using TFS Build 2010 many of standard available Microsoft assemblies are copied to the drop folder. This not only clutters your drop folder but also takes a lot of space on your disk. Find out how to remove all assemblies other than yours when building SharePoint Projects using TFS Build 2010.
Visual Studio 2010 SharePoint Developer Tools make it extremely easy to separate your solution into logical units and yet package them in a single SharePoint Package (WSP). Although building dependent SharePoint projects using Visual Studio 2010 is straight forward, building using TFS Build 2010 produces slightly different output. Find out how to build dependent SharePoint projects using TFS Build 2010 the right way.