SharePoint 2010: Custom Timer Job Caching Old Code

I’m new to SharePoint 2010 development, and while I was working on a Custom Timer Job, every time I made a change to my code I noticed that those changes were not being applied… the “old” code was still being used. So, after doing some research (and losing a lot of hair), the way to fix this behavior is to change your Assembly and File version numbers:

SP2010 Assembly Iformation

That’s all that needs to be done to ensure that your most recent changes are deployed… otherwise, you’ll lose a lot of hair, like I did.

One thought on “SharePoint 2010: Custom Timer Job Caching Old Code

Comments are closed.