So what do we do now? Jamie McAllister discussed this scenario in his post Alternatives to SharePoint Timer Jobs and he proposed a nice design to use Windows Scheduler as an alternative of Timer Jobs. ![]() Hold on, there is no timer job in Office 365. Let’s take it to another extent and just assume that we want to have our solution cloud ready so that if we want to move to Office 365 in future, that’s ready for it as well. Wait a second, did we just say deploy to farm? So, does it makes sense to have a new timer job running at farm level for a such a common, simple problem? ![]() NET code and deploying the timer job to your SharePoint farm. You can always do it by writing a SharePoint Timer Job using. Thus, the problem statement becomes “How to schedule upload of files to a SharePoint Library?”. ![]() One of the most common questions I see on various forums is on “How to upload files to SharePoint Library?” and to a larger extent, these questions are related to a scheduled upload of files.
0 Comments
Leave a Reply. |