When deploying custom SPOneTimeSchedule job definitions sometimes the timer service (OWSTIMER.EXE) just sorta sits there. Your job definition is created, but isn't executed. It will most likely eventually run, but I have better things to do than sit around wait for it. Setting the time for the job in the past seems to move things along faster. // Create new job CustomJob MyJob = new CustomJob(Constants.JOB_NAME, webApp, properties.Definition.DisplayName); MyJob.Title = Constants.JOB_TITLE; // Set up the job to run once MyJob.Schedule = new SPOneTimeSchedule(DateTime.Now.AddHours(-4)); MyJob.Update();

About a year ago I've started to focus on two technologies to develop websites with. Dot Net Nuke and SharePoint. Both products are .Net based and Microsoft backed. At the end of this post are links to articles that do a good job comparing the two frameworks. Needless to say, as frameworks, these products vary greatly in the way you can accomplish your goals. Nevertheless, having the common thread of .Net makes them similiar in so many ways. I'm excited to continue to explore (and amazed at) some of the powerful tools that each product provides out of the box.  As...