Magnus Mårtensson
Microsoft Regional Director, Azure MVP, CEO Loftysoft
Avirag Jain
Director & CTO R Systems
Mahesh Chand
Founder C# Corner, CEO Mindcracker
Chris Gali
CEO & Co-Founder Graphite
Subinder Khurana
Chief Architect StoryProcess, Founder NASSCOM DeepTech Club
Bryan Rishforth
Investor, Chairman Graphite
Bryn Everson
Director Biz Dev Graphite
Raj Tiwari
Digital Transformation Leader, Futurist and Visionary
Joseph Guadagno
Microsoft MVP, Lead Quicken Loans
Nikita Sachdev
Entrepreneur, Blockchain Enthusiast & Advisor, Social Media Influencer
Doug Wagner
COO & Founder Adapt Technical Group
Ritesh Modi
Architect, Senior Evangelist, Cloud Architect
Crystal Wenrick
Director Communications Mindcracker
Allen O’Neill
Microsoft MVP, Consulting Engineer/Architect
Praveen Kumar
CEO MCN Solutions
Chris Love
Founder Love2Dev, Microsoft MVP, Author
Sanjay Vyas
Microsoft Regional Director, Microsoft MVP, Founder & CEO SkillLabs Technologies
Veena Sarda
Deep Learning Consultant, Author
Sekhar Srinivasan
C# Corner MVP, Microsoft Certified Trainer, Pluralsight Author
Lalit Bansal
Founder & CEO - EIY SYS
Navdeep Garg
CEO Revinfotech
Prakash Tripathi
Tech Manager/Leader, Microsoft MVP, Blogger
Bhavna Jain
Breakthrough Consultant
Naveen Sharma
Enterprise Architect, Leadership Coach, Author
Vidya Vrat Agarwal
Principal Architect, Microsoft MVP, Author
Sheetal Agarwal
Founder Clownselors, Medical Clown, Trainer
Abhishek Kant
Founder GTM Catalyst
Vishnu Saran
Founder & CEO VoiceQube
Sandeep Soni
Founder & CEO Deccansoft, Microsoft Certified Trainer
Parveen Malik
AVP InfoSec & Vulnerability Management, Information Security Expert
Nitin Pandit
Microsoft MVP, Developer Evangelist, Author
Niloshima Srivastava
C# Corner MVP, Tech Architect, Trainer, Blogger
Bala Chirtsabesan
Senior Software Engineer at Microsoft, Author
Manoj Mittal
Sr. Technical Architect, C# Corner MVP, Author
Chandni Di
Co-Founder Voice of Slum
Vithal Wadje
Technical Lead, Microsoft MVP, Author
Shivam Ahuja
Founder SkillCircle, Business Mentor
Chervine Bhiwoo
Solution Architect, Microsoft MVP, Author
Saurabh Jain
Vice President Paytm, Founder Fun2Do Labs, Author
Vinay Solanki
Head IoT at Lenovo, Founder IoT-NCR
Anshu kumari
Founder Blockchainkids, Inventor, Trainer
Amit Singal
CEO Startup Buddy
Dev Pratap
Co-Founder & CEO Voice of Slum
Amey Vartak
Technology Consultant, Full Stack Developer, C# Corner MVP, Author
Viswanatha Swamy
Principal Software Engineer, C# Corner MVP, Author
Sanket Verma
Research Engineer @ Ballistics (Forensics) and Chair, PyData Delhi
Sourabh Somani
Lead Developer, Microsoft MVP, Author
Abhishek Mishra
Software Architect, C# Corner MVP, Author
Siddharth Vaghasia
Technical Consultant, C# Corner MVP, Blogger
Bassam Alugili
Senior Software Specialist, Database Expert
S Ravi Kumar
Solution Architect, C# Corner MVP, Author
Sundaram Subramanian
Full Stack Developer, C# Corner MVP, Speaker
Deepesh Somani
Solution Architect, Microsoft MVP, Author
Debasis Saha
Technical Project Manager, C# Corner MVP, Blogger, Author
Vipul Jain
Software Architect, C# Corner MVP, Author
Akshay Patel
Technical Architect, Microsoft Certified Trainer, C# Corner MVP, Author
Stephen Simon
RPA Developer, Evangelist, Author
Vivek Sharma
Founder Kingster636, AR/VR Specialist
Jeetendra Gund
Technical Lead, C# Corner MVP, Author
Sujal Beniwal
AI Enthusiast, Student
M Viknaraj
Microsoft MVP, Azure Architect, Author
Prasham Sabadra
Software Architect, C# Corner MVP, Trainer, Author
Aakash Maurya
Senior Developer, C# Corner MVP, Speaker
Ankit Sharma
Senior Software Engineer, C# Corner MVP, Author
Mangesh Gaherwar
Team Lead, C# Corner MVP, Author
Viral Jain
Technical Consultant, C# Corner MVP, Author
Bhasker Das
Solution Architect, Evangelist
Manish Dwivedi
Associate Project Manager
Ck Nitin
Programmer, Author
Rohit Gupta
Technical Trainer, Author
Manish Tewatia
Full-stack Marketer, UX Designer
Bhavya Gaur
Technical Illustrator
Rohit Tomar
SEO/SMO Expert
Web Track
Cloud & Data Track
Dev Track
Registration & Breakfast
Future of Desktop Apps with JS (ElectronJs)
Nitin Pandit
Building Serverless Microservices Using Microsoft Azure
Vithal Wadje
Innovating RPA: A Robot for Every Person
Stephen Simon
Managing Cloud Storage Accounts using Logic Apps
Viknaraj Manogararajah
Data visualization using Python
Sekhar Srinivasan
Going Cross platform with AR Foundation
Vivek Sharma
Keynote
Managing your Azure dependencies in ASP.NET Core apps using VS
Bala Chirtsabesan
Securing Applications on Intelligent Azure
Abhishek Mishra
Getting started with Blazor the Framework of Future
S Ravi Kumar
Lunch
Build Progressive Web Apps using Angular 9
Debasis Saha
Build and deploy to any platform using Azure DevOps
Chervine Bhiwoo
Deep Dive in Azure Service Bus
Akshay Patel
Build a Native Mobile Application using React Native and JavaScript
Joseph Guadagno
Making sense of Web Job, Web Job SDK and Functions in Azure
Prakash Tripathi
CloudFront Distribution in AWS
Viral Jain
Tea Break
Introduction to PowerBI
Aakash Maurya
Build Advanced SPFx solutions with React and Graph API
Siddharth Vaghasia
Build Business Intelligence Analyst (BIA) Skills
Sundaram Subramanian
Deep dive of Power Platform – AI BUILDER
Prasham Sabadra
Panel 1
What's new in SharePoint development
Vipul Jain
Build a SSO (Single Sign On) based Native JavaScript application with Microsoft Identity within 10 minutes
Manoj Mittal
Panel 2
Applications and working of AI
Veena Sarda
Deploying serverless API's with .Net core 3.0 on AWS & Azure
Amey Vartak
Panel 3
Blockchain with .NET Core (Ark)
Anshu Kumari
Closing Note & Prize Distribution
Dev Track
Cloud Track
Architecture Track
Emerging Tech Track
Registration & Breakfast
Creating Full-Stack Web Apps Using Server-Side Blazor
Ankit Sharma
Real time face recognition with MS Cognitive Services
Niloshima Srivastava
Building Scalable APIs with GraphQL
Jeetendra Gund
Future of development with AI and Blockchain
Navdeep Garg
Debugging Tips and Tricks with Visual Studio 2019
Joseph Guadagno
Azure Containers
Abhishek Kant
Enterprise Architecture
Naveen Sharma
Bot Framework - learn it fast and look like a boss!
Allen O’Neill
Keynote
.Net Core & C# 8 Performance
David McCarter
Working with Azure kubernetes services
Ritesh Modi
Becoming an Architect
Vidyavrat Agarwal
Why Techies Need to Learn Product Management
Saurabh Jain
Lunch
Build a rules engine in .Net Core
Sanjay Vyas
Building CI and CD Pipeline using Azure DevOps
Sandeep Soni
Entity Framework Core - Tips and Tricks, Performance Optimization, and Tuning
Bassam Alugili
Hacking your way into Data Science
Sanket Verma
Speed up your .Net Core Website
Sourabh Somani
Azure
Magnus Mårtensson
Demystifying Open Distro for Elasticsearch
Suman Debnath
Future of Data
Shivam Ahuja
Tea Break
gRPC with C# and .Net Core
Mangesh Gaherwar
Panel 1
Essentials of Cloud security
Parveen Malik
Power platform and Dynamics 365
Deepesh Somani
Microservices - the gRPC Way
Viswanatha Swamy
Panel 2
Reserved
Reserved
Closing Note & Prize Distribution
Building a Scheduling Service with Quartz.NET in C#
A scheduling service coordinates work that should happen at a particular time or repeat on a reliable timetable. Examples include sending invoices, refreshing search indexes, importing partner data, generating reports and removing expired records. In a C# application, Quartz.NET provides a mature job scheduler with triggers, calendars, persistence, retry controls and clustering support.
The library is especially useful when a simple Timer is no longer sufficient. An Australian business may need a report to run at 9:00 am in Sydney, a data export to execute after an overnight batch, or a customer notification to respect local time and daylight-saving changes. A well-designed service separates scheduling decisions from the business operation itself, making the result easier to test, monitor and operate.
Why scheduling belongs in application architecture
A scheduled task has two distinct responsibilities. The first is deciding when work should run; the second is performing the work. Quartz.NET manages the first responsibility through jobs and triggers, while application services, repositories and API clients handle the second. This separation prevents timing code from becoming mixed with payment processing, reporting or data access.
A job should generally be small and focused. It can load the required records, call a domain service and record a result, but it should avoid containing complex business rules that cannot be reused elsewhere. A job that sends overdue account notices, for example, can call an OverdueNoticeService rather than directly constructing every query and email message.
Quartz.NET also gives the application a consistent way to express scheduling policies. A trigger can run once, repeat at fixed intervals, follow a cron expression or use a calendar that excludes selected dates. This is more expressive than a process that checks the clock every minute and hopes it remains running.
For organisations operating across Australia, time zones need early attention. Sydney, Melbourne, Canberra, Hobart and Brisbane commonly use Australian Eastern time, while Perth uses Australian Western time. New South Wales, Victoria, Tasmania and the Australian Capital Territory observe daylight saving; Queensland does not. A schedule stored only as “9:00” without a zone can therefore run at the wrong local time for part of the year.
Set up Quartz.NET in a .NET service
Quartz.NET can run inside an ASP.NET Core application, a worker service or a dedicated process. A worker service is often preferable when scheduled work should be independently deployed and scaled. An ASP.NET Core application can still host Quartz when the scheduled tasks belong closely to the web application and its dependency injection container.
Install the integration package that matches the application’s .NET and Quartz.NET versions. A typical registration in a modern worker or web application looks like this:
builder.Services.AddQuartz(options =>
{
options.UseMicrosoftDependencyInjectionJobFactory();
});
builder.Services.AddQuartzHostedService(options =>
{
options.WaitForJobsToComplete = true;
});
The hosted service starts the scheduler with the application and stops it during graceful shutdown. WaitForJobsToComplete helps prevent an in-progress operation from being abandoned immediately when a container, virtual machine or App Service instance is recycled.
A job can receive normal dependency-injection services through its constructor:
public sealed class RefreshCatalogueJob : IJob
{
private readonly ICatalogueService catalogue;
public RefreshCatalogueJob(ICatalogueService catalogue)
{
this.catalogue = catalogue;
}
public async Task Execute(IJobExecutionContext context)
{
await catalogue.RefreshAsync(context.CancellationToken);
}
}
The job should honour cancellation where possible. Database calls, HTTP requests and file operations should have suitable timeouts, since a scheduler cannot make a slow external system respond. Configuration such as endpoint URLs, batch sizes and feature flags belongs in options or environment variables rather than hard-coded job classes.
Define jobs, triggers and execution rules
Quartz.NET uses a job detail to describe the work and a trigger to describe when it should run. The job detail identifies the implementation, while the trigger contains the schedule, identity, start time, end time and misfire behaviour. Keeping these concepts separate lets several triggers invoke the same job with different parameters.
For a recurring task, a cron trigger provides a readable schedule:
var jobKey = new JobKey("catalogue-refresh");
options.AddJob<RefreshCatalogueJob>(job => job
.WithIdentity(jobKey));
options.AddTrigger(trigger => trigger
.ForJob(jobKey)
.WithIdentity("catalogue-refresh-every-night")
.WithCronSchedule("0 0 2 * * ?", cron => cron
.InTimeZone(TimeZoneInfo.FindSystemTimeZoneById(
"Australia/Sydney"))));
Quartz cron expressions include a seconds field, so the expression above represents 2:00:00 am each day. Always verify expressions with tests or a trusted expression tool. A small difference between “every five minutes” and “at five minutes past each hour” can create a significant operational problem.
A trigger should have a stable identity. If the application creates a random trigger name during every startup, it can produce duplicate schedules or make later administration difficult. Stable names also make it easier to inspect schedules through an administrative endpoint or the Quartz dashboard tools available in the surrounding ecosystem.
Use [DisallowConcurrentExecution] when two instances of the same job must not overlap:
[DisallowConcurrentExecution]
public sealed class ReconcilePaymentsJob : IJob
{
// Implementation omitted
}
This attribute protects a job key from concurrent execution within Quartz’s scheduling model. It does not replace database constraints or distributed locking around business data. If a reconciliation task updates shared records, those updates should remain transactionally safe even if a deployment or infrastructure failure occurs.
Persist schedules and handle missed work
An in-memory scheduler is suitable for development, demonstrations and disposable tasks. Its schedule disappears when the process stops, and any trigger that should have fired during downtime is handled only according to the in-memory scheduler’s current state. Production workloads usually require a persistent job store.
Quartz.NET can store jobs, triggers, calendars and execution information in a relational database. SQL Server is a natural fit for many Microsoft-based applications, while PostgreSQL and other supported databases may suit a cloud-native deployment. The database schema must be installed correctly, and the scheduler’s connection should use a dedicated account with only the required permissions.
Persistence becomes important when an Azure App Service, container or virtual machine is restarted. A durable store allows the scheduler to recover its definitions rather than relying on application startup code to recreate everything. It also provides a foundation for clustered operation, where multiple application instances share scheduling responsibility.
Misfire instructions define what happens when a trigger should have fired while the scheduler was unavailable. A missed hourly report might run once immediately after recovery, while a high-frequency polling task might skip old occurrences and continue with the next interval. The correct choice depends on business meaning. Replaying every missed notification could annoy customers; skipping every missed financial calculation could produce incorrect records.
Timezone data also needs deliberate handling. Store timestamps in UTC for events and audit records, but retain the intended IANA or Windows time-zone identifier for recurring local schedules. For customer-facing systems, “9:00 am in Melbourne” is a business rule, not merely a UTC offset. Daylight-saving transitions can create an invalid local time or an ambiguous time, so test schedules around October and April as well as ordinary dates.
Run scheduled work safely at scale
A scheduler is part of the production platform, so it needs the same operational controls as an API. Log the job key, trigger key, scheduled fire time, actual start time, duration, outcome and correlation identifier. Avoid writing customer data or access tokens into logs. Structured logging makes it easier to find failed runs in Azure Monitor, Application Insights or another observability platform.
Failures should be classified rather than blindly retried. A temporary network timeout may deserve a retry with backoff, while an invalid customer record may require quarantine and human review. Quartz.NET supports trigger-level retry patterns through rescheduling, but business operations should also be idempotent. If a process sends an invoice and then loses its database connection, the retry must not create a second invoice or duplicate payment.
Long-running work can block a scheduler’s thread pool and delay unrelated jobs. Break large workloads into pages or queue messages, then let Quartz.NET initiate the process rather than handling millions of records in one execution. For high-volume workloads, a common architecture is a small Quartz job that publishes work to Azure Service Bus, Amazon SQS or another queue, with separate consumers processing the items.
Clustering requires coordination between the scheduler and its persistent store. Configure one scheduler instance per application node, use compatible cluster settings and verify that database locks behave correctly under load. A three-node service in Sydney, Melbourne and Brisbane does not automatically provide fault tolerance if all nodes depend on one unavailable database or if each node accidentally runs an independent in-memory schedule.
Security matters for administrative scheduling features. If users can create or edit triggers, validate allowed intervals, restrict cron expressions and record who changed each schedule. Australian organisations may also need to consider the Privacy Act 1988 and the Australian Privacy Principles when job data includes personal information. Keep personal details out of job payloads where possible, limit retention and apply access controls to logs and scheduler tables.
Compare scheduling approaches for the workload
Quartz.NET is not the right answer for every delayed operation. A lightweight BackgroundService can handle a single internal loop, while a queue may be better for durable, high-volume processing. Hangfire is another .NET option that provides a database-backed dashboard and a different programming model. The choice should reflect delivery guarantees, operational complexity and the need for calendar-based scheduling.
| Approach | Suitable use | Strengths | Limitations |
|---|---|---|---|
| Quartz.NET | Cron schedules, calendars and multiple job types | Rich triggers, time zones, persistence and clustering | Requires careful configuration and operational monitoring |
BackgroundService with a timer |
One or two simple recurring tasks | Minimal dependencies and easy to understand | Weak recovery, limited administration and no built-in durable schedule |
| Queue-based worker | Large or bursty workloads | Durable delivery, horizontal scaling and back pressure | Needs a separate scheduling or delayed-message strategy |
| Hangfire | Background jobs with a database-backed dashboard | Familiar .NET API, retries and operational visibility | Different storage model and less focus on advanced calendar rules |
| Cloud scheduler | Managed HTTP or message triggers | Less infrastructure to maintain | Provider-specific features, costs and integration constraints |
Deployment recommendations
- Use stable job and trigger identities so deployments do not create duplicates.
- Persist production schedules in a supported relational job store.
- Store recurring local schedules with an explicit Australian time-zone identifier.
- Make database updates, notifications and external calls idempotent before enabling retries.
- Expose health, failure and duration metrics without exposing personal information.
A sensible delivery path begins with one small job in a worker service, followed by an integration test against the selected database. Test startup, graceful shutdown, a failed execution, a misfire, daylight-saving transitions and two application instances running together. Once those cases behave predictably, Quartz.NET can provide a dependable foundation for reports, synchronisation, notifications and other time-driven processes in C# applications.
1, CBD, Maharaj Surajmal Road, Near Yamuna Sports Complex, Delhi, 110032
GENERAL QUERIES
Manish Tewatia
manish@csharpcon.com
+91-9718-431-042
TICKET QUERIES
Atul Gupta
conference@csharpcon.com
+91-9910-125-804