TimerJobs Deployment
Today I wanted to upgrade an existing custom TimerJob. After a stsadm -o upgradesolution everything seemed to be ok. But when the TimerJob was started it did not perform the way it should - in fact it used the wrong code/wrong logic - the same logic as before the upgrade. After some unsuccessful stsadm -o upgradesolution(s) later I almost gave up. But then I found a comment of a blog-post about custom TimerJobs. Finally the solution - actually it was quite obvious. If one deploys a new TimerJob it's always a good idea to restart the OWSTIMER service so that new assemblies are used.
