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.
Delegate Controls allow you to provide users with pluggable functionality which they can use to extend their existing solution without modifying the existing code. Unfortunately once enabled it’s difficult to track which Delegate Controls are used where on your site. Find out how to check which Delegate Controls are activated on your site using PowerShell.
Using the new Visual Studio 2010 SharePoint Developer Tools you can package your SharePoint components into WSPs with just a few mouse clicks. And although it allows you to get productive and focus on the real work, this process has some limitations like not copying dependent assemblies to the output directory.