For daily tasks, such as
- converting csv files to excel files;
- creation of excel files (the contents of which are created using financial methods);
- moving and copying of files;
- calculation of daily financial and risk analysis metrics; and
- (this list will grow over time and will become more complex..)
Is Quartz.Net more suitable when compared to the windows scheduler? (Note: I am looking for advantages/disadvantages)
Background
At present we currently have a number of Excel macro enabled workbooks that have been created to accomplish the above tasks. These at face value seem simple enough, however they each have their own set of complexities, which VBA (or should I say me) is just managing to achieve.
Since we are talking Excel, the obvious initial disadvantage for a switch to Quartz would be to convert all the VBA code to .Net (preferably C#, however VB.Net should be a quicker move, I think). However, these tasks could also be converted to simple console apps that could run on the windows scheduler as well. To date, the current setup of using the Windows Scheduler works well with the Excel Macros.
I have recently stumbled upon Quartz.Net and wondered if this may be a long term option. The other main driving force behind this is that the above list of daily tasks will be growing and the way I see it is that maintenance of the Windows scheduler may become a bit of an issue especially with regards to access rights and job monitoring.
In addition, a move from VBA to .Net is inevitable in any case, since the current setup allows for some users to tinker with VBA who then want to know what went wrong.
My initial direction of thought leads me to think, that Quartz is the better option (skimmed though the tutorial). However, when coupled with the time taken for the above conversions, and the learning curve involved with Quartz, will I be delivering and adding tangible value to the business?