I’ve just posted a minor update of the Imtech Run PowerShell Script Deployment Step. There are two things I’ve changed in the v1.1.
One of the extensibility points of the new Visual Studio SharePoint development tools are the Deployment Steps: tasks that are executed during the Deployment Process in Visual Studio. The tools allow you not only to specify different Deployment Configurations using available Deployment Steps but also to create your own steps like for example executing a PowerShell script. While creating custom Deployment Steps isn’t difficult.aspx), it can get challenging when you want to make them support user definable parameters.
One of the new capabilities of the new Visual Studio SharePoint development tools is support for creating Site Definitions. Using the Site Definition SharePoint Project Template you can create and test Site Definition. In order to fully benefit of the new tools there are a couple of things you have to keep in mind.
In my previous article I wrote about extending the Visual Studio SharePoint development tools. Now it’s time for the first extension: Imtech Run PowerShell Script Deployment Step.
SharePoint 2010 ships with a great development story. Using the new Visual Studio SharePoint development tools you can create SharePoint solutions easier and faster. Visual Studio SharePoint development tools provide you out of the box with a great number of Project and Item Templates which allow you to create the most commonly used SharePoint artifacts. Using the new SharePoint Server Explorer you can explore all the different objects within your Site Collection and using the Validation Rules and Deployment Steps you can package your work into a WSP package and deploy it to your server with a single mouse click. Yet I think that the most exciting part about the new Visual Studio SharePoint development tools is the extensibility, because the possibilities are almost limitless.