SharePoint 2010 and VS2010: Post-Deployment Scripts

Context

You are developing a SharePoint 2010 application using Visual Studio 2010 on a Windows 2008 64-bit server. You want to run a post-deployment script (PowerShell for example) for debugging:

image

The Problem

When you add a script, for example: powershell $(ProjectDir)\PowerShellScript\MySuperPowerShellScript.ps1

You always get an error when running the script:

Error occurred in deployment step ‘Run Post-Deployment Command’: The command "powershell $(ProjectDir)\PowerShellScript\MySuperPowerShellScript.ps1" exited with error code: 1.

This error is due to the fact that VS2010 runs in 32-bit mode, as well as its post-deployment scripts, and the SharePoint 2010 APIs run in 64-bit mode. This creates errors when executing the script.

[Read More]

A Substitute for Red Gate's .Net Reflector

If you are like me, you have already used .Net Reflector to decompile some .Net classes. The product has been owned by Red Gate for a few years now, and they have kindly eliminated the free version to make it paid. I came across this article by Corey Roth where he mentions that even the latest version of Reflector contains a Time Bomb, meaning you would be forced to upgrade to the paid version starting June 1st.

[Read More]

Do you know Fritzing?

While looking at prototyping tools for my Fez Domino, I came across Fritzing, a software that allows you to easily diagram your electrical circuit! Here is a summary:

Fritzing Application

[Read More]