Hi,

I began developing my custom module using the app_code or dynamic compilation approach - i.e. my module was developed by placing user controls (and other content files in the DesktopModules/[ModuleName] folder, and by placing the code files (Controller & Info classes and DataProvider classes) in the App_Code/[ModuleName] folder.

I now have a requirement to develop a scheduled task to send out emails that my module is going to generate. I wish to use the DNN Scheduling Provider to achieve this but as far I'm aware, scheduled tasks need to be compiled into a DLL file. I was wondering what the best approach would be?

I developed a simple HelloWorld scheduled task inside its own Class Library project that I compiled into a DLL and to which I added a reference to the DotNetNuke.dll. The problem with this is that whilst I could access all the methods inside DotNetNuke I couldn't reference anything inside my custom module (e.g. any of the Info, DataProvider, SqlDataProvider classes that I may have use for). I'm keen to avoid duplicating stuff so should I simply rework my custom module so that the whole module is compiled (e.g. using the DotNetNuke Compiled Module template included with the Starter Kit) - then I could simply have the scheduled task as just another class in my module from which I could reference all the other classes in my module? It sounds like this may be the best approach as isn't this the way the forum module is developed (i.e. you have the GUI stuff and the scheduler all wrapped up in the one DLL)?

Any advice/tips would be gratefully received. I'm a bit tentative about starting off on a particular track only to discover that I would have been better of doing it a different way if only I knew a bit more starting off.

Thanks