...as it will be NULL within a Timer Job or Workflow. I have some shared Data Access classes that use SPContext.Current.Web all over the place and now that I want to use them from within a Timer Job, I have to refactor them to take a SPWeb as a Parameter...
If it consumes electricity, chances are good that I worked with it or at least know about it. SysAdmin during the 90's, Blogger and professional Programmer since the mid-2000's. Professional C# (ASP.net MVC/Web API) and JavaScript (Browser and node.js) developer. In the past I also worked with Basic, Delphi. Java, and PHP. Did some Ruby and Go code as a hobby. 6502 Assembly is art.
I'm on Stack Overflow, @mstum on 
Twitter and mstum on 
GitHub.
Copyright © 2008-2015 Michael Stum - Theme by deniart
So are you going to create Fake SPContext.Current OR make the Timer Job execute in SharePoint's context?
Neither, since there is no Context, it runs side by side with SharePoint. I have to instantiate the SPSite or SPWeb that I want myself.