SPWakeUp version 1.3.0 has been released. This version includes the ability to run on a non-SharePoint server to wake arbitrary URLs.

Use the ‘-NotASharePointServer’ command line parameter to specify that SPWakeUp should not check for the presence of SharePoint and should not attempt to evaluate a list of web …

SPWakeUp version 1.2.0 has been released. This version includes the ability to import a list of additional URLs to be woken from a file instead of providing a series of URLs to be included individually on the command line.

Use the ‘-IncludeFile:’ command line parameter to specify the full path to the file containing …

I’ve implemented something that I’ve wanted to for a long time on SPWakeUp: The ability to wake additional URLs.

Version 1.1.0 allows the use of the ‘-Include':’ command line parameter to specify additional URLs that will be woken once the detected site collections and subsites have been traversed.

Since I started working with on-premises SharePoint instances, one of the solutions that I’ve used to wake up (pre-compile) the site collections and sub-sites contained within the web applications hosted by the farm is SPWakeUp.

This was originally a solution hosted on CodePlex and provided binaries for SharePoint …

1. Use public on the main program class.In order for web jobs to initialise correctly the main class that contains the web jobs needs to be made public. Once this has been added the individual jobs can then be read and should be visible in the output when running locally.

The latest tools for windows Azure are located here:

http://www.microsoft.com/en-us/download/details.aspx?id=29988

This version is supported in both Visual Studio 2010 & 2012 and will run on Windows 7 & 8 Server 2008 & 2012

This is a follow on post from my introduction to Windows Azure Websites and shows you how you can synchronise your website in TFS with Windows Azure.

One of the biggest problems with the way you deploy applications to  Windows Azure is that minor changes (e.g .markup, content and styling) require a redeploy to publish …