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
Build a DI container with Microsoft.Extensions.DependencyInjection
Dependency injection is one of those C# topics that appears briefly in a conference demo and then shapes every production application. A container centralises object creation, exposes services through contracts and removes graph-building details from business classes. That matters across the C# Corner Annual Conference 2020 programme, where cloud, data and DevOps sessions share an interest in maintainable application foundations.
Microsoft.Extensions.DependencyInjection provides the standard building blocks for this work through service collections, service descriptors and service providers. The result works with ASP.NET Core, worker services, Azure applications and desktop tools. Understanding how that container creates, tracks and disposes of objects gives developers control over dependencies without introducing a separate framework or obscuring the familiar .NET injection model.
Designing registrations around application boundaries
A useful container starts with interfaces that reflect genuine application boundaries, rather than with a collection of arbitrary abstractions. A payment service might depend on IPaymentGateway, while order processing depends on IOrderRepository and IClock. These contracts describe capabilities the application needs and leave implementation details such as SQL, HTTP or system time outside the feature code.
Registration belongs in a dedicated composition root, usually the application entry point. The IServiceCollection supplied to the host receives each dependency as a ServiceDescriptor, which records the service type, implementation and lifetime. Generic extension methods make the intent clear: AddSingleton<IClock, SystemClock>() registers a system clock, AddScoped<IOrderRepository, SqlOrderRepository>() creates a repository for each scope, and AddTransient<IEmailComposer, EmailComposer>() creates a composer whenever it is requested.
Large applications can divide these registrations into focused extension methods such as AddBilling, AddPersistence and AddMessaging. Each method owns a feature’s bindings, while the composition root decides which modules to include and which configuration values to supply. This arrangement keeps dependency declarations close to their related code without scattering object creation throughout controllers, background workers or event handlers.
Configuring lifetimes and resolving services
Once registration is complete, the collection builds an IServiceProvider. Application code normally receives that provider through constructor injection and resolves a required service with GetRequiredService<T>(). The provider then constructs the requested object and recursively supplies its registered dependencies. This automatic graph construction replaces explicit new calls and keeps construction knowledge in one place.
Lifetime selection determines how long each instance survives. A singleton is created once by the root provider and remains available until that provider is disposed. A scoped service receives one instance within each scope, which commonly represents an HTTP request or an explicit unit of work. A transient service is created on every resolution. These semantics are central to thread safety, database context management and isolation of request-specific state.
Options provide another useful registration pattern. Binding configuration through Configure<TOptions> allows strongly typed settings to participate in normal dependency injection. IOptions<T> is generally singleton-backed, IOptionsSnapshot<T> is scoped and IOptionsSnapshot<T> is scoped, while IOptionsMonitor<T> supports singleton-backed change notifications. Newer .NET versions also support keyed services, allowing multiple registrations of the same contract through APIs such as AddKeyedSingleton and GetRequiredKeyedService. Keyed registration is valuable when an application genuinely needs several implementations, provided the target framework and package versions support it.
Managing scopes, validation and disposal
Scopes are particularly important when services hold temporary state. An Entity Framework Core DbContext, a unit-of-work coordinator or a request-specific cache should normally be scoped rather than singleton. Code can create a scope through IServiceScopeFactory, resolve the required services inside it and dispose the scope when the operation ends. ASP.NET Core creates request scopes automatically, while console applications and workers need to establish equivalent boundaries.
A long-lived singleton that captures a scoped dependency can retain that dependency for the entire application lifetime. It may also hold data belonging to an earlier request. Built-in scope validation can identify these lifetime mismatches, and ValidateOnBuild can expose missing or invalid registrations during startup. Enabling both checks in development turns a vague runtime failure into a precise registration error before business traffic reaches the affected path.
Disposal follows ownership rules. The service provider disposes singleton instances that it created, and disposing a child scope releases its scoped instances. Implementations of IDisposable and IAsyncDisposable receive appropriate cleanup. Objects returned by a custom factory are not automatically disposed by the container, so factory code must make that ownership decision explicit. This distinction prevents leaked database connections, background workers and unmanaged resources in long-running Australian production systems.
Adapting the design for Australian teams
Australian deployments add constraints that are easy to miss in a generic sample. Teams in Sydney, Melbourne and Brisbane often support customers across the country, and a Perth operations desk can begin its day several hours before Sydney. Daylight-saving changes in the eastern states also shift the windows in which scheduled jobs, support handovers and background workers run. Time-based singleton services therefore need predictable behaviour rather than hidden local-time assumptions.
For organisations handling personal information, the Australian Privacy Act and customer security policies can shape where data and logs are stored. Microsoft.Extensions.DependencyInjection does not select a cloud region, but the composition root must respect those decisions. Azure Australia East and Australia Southeast provide Australian deployment options, while hybrid designs can keep sensitive workloads in approved locations. Long-lived singletons still require care so they do not retain region-specific clients or personal information beyond the intended boundary.
Procurement adds another local layer: Australian GST and customs treatment can affect imported developer tooling and commercial components, so finance teams may need to classify an overseas purchase rather than treating it like a local subscription. In field environments with unreliable connectivity, the companion guide to EF Core and SQLite shows how local persistence can sit behind repository contracts. The container can still supply the repository, serialisers and logging services without embedding storage decisions in every feature.
Strengthening the composition root
The composition root is the place where configuration, concrete implementations and lifetimes meet. In an ASP.NET Core application it is normally Program.cs; in a worker it may be the host-building method. Keeping those decisions together makes the dependency graph reviewable and allows tests to replace selected registrations without changing production code. Service-locator patterns should remain limited to genuine framework boundaries because widespread use hides dependencies and weakens constructor-level validation.
Lifetime and ownership patterns
- Register immutable, thread-safe policy objects as singletons and avoid sharing mutable request state.
- Use scoped registrations for database contexts, units of work and per-operation caches.
- Treat factory-produced instances as caller-owned unless the factory explicitly transfers disposal.
- Prefer constructor injection, using property injection only where a framework requires optional collaboration.
Reliability checks
- Build the provider in one composition root and enable startup validation there.
- Create a scope around each logical unit of work and resolve scoped services only inside it.
- Test disposal of the root provider, child scopes and background workers.
- Include service names, scope identifiers and operation IDs in structured diagnostics.
Used this way, Microsoft.Extensions.DependencyInjection becomes more than an object factory. It becomes a documented map of application responsibilities, with explicit boundaries for creation, state and cleanup. That map gives small prototypes the flexibility to evolve and large systems the consistency required for dependable cloud, desktop and automation workloads.
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