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.
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.
A couple of weeks ago Chris O’Brien – fellow MVP wrote an article on the research of the SharePoint BLOB cache he has done. During that research he has experienced some issues with some of the files not being cached properly on the client causing the browser to request the file every single time. As I’m working with Web Content Management solutions on SharePoint a lot, it definitely took my attention.
Back in October last year I started working with programmatically provisioning Web Part instances. The challenging part was that the assemblies containing the Web Parts’ code were located in the bin directory of the target Web Application. The custom STSADM command I was using for that purpose wasn’t able to resolve the Web Part type. Back then I have found a way to deal with it which I though was a working solution. Unfortunately: just last week I have stumbled upon the same situation: again.
Recently I have found that you could actually provision Publishing Pages using the declarative markup of Features. Right after that discovery I have found that you could benefit of that functionality in quite a few scenario’s, like provisioning test content wrapped in Features. The biggest downside against provisioning Publishing Pages would be having to generate the XML manually. To simplify the process I have decided to create a tool which would export the existing Publishing Pages to Feature XML. Guess what: the tool is ready now and you can take a test drive.