What structure do you work with? I have some pointers if you are working with .Net 4.0, like me.
If you have access to your computer where you can install the services, I would use a new and improved Workflow service for this situation. What is nice about them is that Workflows can persist for several minutes, hours, days, weeks, months, etc., Lying โinactive,โ until the delay time periods are over.
If it is an IIS machine (and if you want to use this route), then it is relatively simple to build it directly as a project / solution "Workflow Service" in VS 2010. From there you will be presented by the designer and several workflow actions on the toolbar.
Add flowchart activity to put your email actions inside. The flowchart is ideal because it can initialize everything you need, and the flow of decisions can redirect backward in the direction (in contrast to the activity of an always moving sequence). What you need to do with your logic is up to you because your question does not contain many details.
Now, if you are using .Net 3.5, I would think about refraining from creating Workflow, since you need to migrate when switching to 4.0 (WF 3.5 is NOT compatible with 4.0). When the administrator accesses the computer, you can install the Windows service, which contains a timer, to light up the code every 30 days (or, nevertheless, determined) as necessary.
jlafay
source share