What's that IIS Process ID again?
Sunday, August 18, 2013
This one came up during a recent sprint of coding in which I was debugging a SharePoint 2013 farm solution (I know - apps are the way to go now!) with Visual Studio 2012. Let me say, since first starting development in MOSS 2007, this is a totally different and much smoother experience. I switched back-and-forth between using Visual Studio’s “Play” button - also known as “Start Debugging” - and a more traditional Build, Deploy, Attach to Process method.
VirtualBox and Multiple Monitors
Thursday, July 26, 2012
As a SharePoint consultant, I really enjoy having a local copy of a full SharePoint server on my laptop. As I am patiently waiting for Windows 8 to release with Client Hyper-V, I’m continuing to use Oracle’s VirtualBox software to host my SharePoint development environments.
Extracting Zip Files using PowerShell
Tuesday, July 17, 2012
To help troubleshoot some SharePoint issues, I had a need to analyze some log files that were contained in multiple zip files; one log file per zip file. Since there were several hundred zip files to extract, I figured PowerShell could help! There are several posts I found with example scripts for how to perform this operation. I took pieces from many posts, added some COM object clean-up code, and wrapped this in a function. I hope it helps you in your scripting activities!
Latest Code Not Working Quite Right?
Tuesday, July 3, 2012
This post reviews a common situation in SharePoint development where stale code persists in a .NET process causing unexpected results.
Adding a PowerShell Snap-in
Tuesday, May 29, 2012
A typical scenario when developing PowerShell scripts for SharePoint is to need the use of the SharePoint PowerShell snap-in. This snap-in provides all of the great SharePoint cmdlets that have quickly become critical to any SharePoint developer or administrator’s toolkit.
Some scripts may assume that the script will be executed within the SharePoint 2010 Management Shell - which is simply a standard PowerShell window with some extras: including the SharePoint PowerShell snap-in. However, what if an unsuspecting or unexperienced administrator executes the SharePoint script in a standard PowerShell instance?