How crazyjson/taskmanager works
Project type and purpose
• From the README and file tree, this is a .NET-based Task Management Platform built on Quartz.NET.
• It provides a scheduler engine (Windows Service or Console Host), a web-based UI (ASP.NET MVC “TaskManagerWeb”), a set of reusable libraries (data access, utilities, messaging), and a collection of Quartz jobs (in Mysoft.Task).
• The system’s purpose is to let teams define, schedule, execute and monitor recurring jobs; send notifications on job outcomes; and view/edit configuration via a UI.
File structure
Top-level projects (logical modules):
• Dapper.SimpleCRUD – lightweight ORM helper.
• TaskManagerWeb – ASP.NET MVC front-end (Views, Scripts, CSS, Modules folder with Nancy modules).
• YwdSoft.ConsoleHosting – standalone console host for tasks (uses a local SQLite DB).
• YwdSoft.WindowService – Windows Service wrapper around the scheduler engine (batch scripts & installer).
• Ywdsoft.Task – core Quartz.NET integration: reads TaskConfig.xml, loads IJob implementations (TaskSet folder).
• Ywdsoft.Service & Ywdsoft.MessageTransmit – specialized service libraries (e.g. HTTP, messaging, RabbitMQ, email) that jobs may call.
• Ywdsoft.Model – domain entities (DB tables, RabbitMQ message classes).
• Ywdsoft.Utility – cross-cutting services: configuration manager, data-access (DapperHelper, DB XML), logging, Excel import, RabbitMQ client, Quartz helper, etc.
• Ywdsoft.XmlCommand – XML-based command tool for DB generation/maintenance.
You also see config files (app.config, packages.config) in each project showing dependencies (e.g., Quartz.NET, log4net, RabbitMQ.Client).
Reading the README for additional insights
• The architecture calls out six “projects” (engine, UI, Windows Service installer, utilities, data/model, messaging).
• Tasks are added by dropping a class into Mysoft.Task.TaskSet and updating TaskConfig.xml.
• Installation uses WSWinForm.exe or batch scripts to install the Windows Service.
• Three built-in jobs: IP proxy crawler, Express-progress checker (with email notifications), and message notifier (poll messages table every 3 minutes).
Final advice
• Every logical boundary: UI vs. engine vs. utilities vs. external services.
• Shared libraries under a “Shared Utilities” boundary.
• Don’t forget the installation tooling: WSWinForm.exe and batch scripts as a Deployment artifact.