New to site?


Lost password? (X)

Already have an account?


(X)

Presents

#CSHARPCON20

The C# Corner Annual Conference 2020 is a three-day annual event for software professionals and developers.

3
DAYS
72
SPEAKERS
65
SESSIONS

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

8am-9am

Registration & Breakfast

9am-10am

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

10am-11am

Managing Cloud Storage Accounts using Logic Apps

Viknaraj Manogararajah

Data visualization using Python

Sekhar Srinivasan

Going Cross platform with AR Foundation

Vivek Sharma

11am-12pm

Keynote

12pm-1pm

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

1pm-2pm

Lunch

2pm-2:45pm

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

2:45pm-3:45pm

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

3:45pm-4pm

Tea Break

4pm-4:30pm

Introduction to PowerBI

Aakash Maurya

Build Advanced SPFx solutions with React and Graph API

Siddharth Vaghasia

Build Business Intelligence Analyst (BIA) Skills

Sundaram Subramanian

4:30pm-5pm

Deep dive of Power Platform – AI BUILDER

Prasham Sabadra

Panel 1

What's new in SharePoint development

Vipul Jain

5pm-5:30pm

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

5:30pm-6pm

Deploying serverless API's with .Net core 3.0 on AWS & Azure

Amey Vartak

Panel 3

Blockchain with .NET Core (Ark)

Anshu Kumari

6pm-6:30pm

Closing Note & Prize Distribution

Dev Track

Cloud Track

Architecture Track

Emerging Tech Track

8am-9am

Registration & Breakfast

9am-10am

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

10am-11am

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

11am-12:30pm

Keynote

12:30pm-1:30pm

.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

1:30pm-2:30pm

Lunch

2:30pm-3:30pm

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

3:30-4:15pm

Speed up your .Net Core Website

Sourabh Somani

Azure

Magnus Mårtensson

Demystifying Open Distro for Elasticsearch

Suman Debnath

Future of Data

Shivam Ahuja

4:15pm-4:30pm

Tea Break

4:30pm-5:15pm

gRPC with C# and .Net Core

Mangesh Gaherwar

Panel 1

Essentials of Cloud security

Parveen Malik

Power platform and Dynamics 365

Deepesh Somani

5:15pm-6pm

Microservices - the gRPC Way

Viswanatha Swamy

Panel 2

Reserved

Reserved

6pm-6:30pm

Closing Note & Prize Distribution

Creating a versioned REST API with Swagger and OpenAPI in ASP.NET Core

At C# Corner Annual Conference 2020, building an API provides a useful lens on how .NET teams turn business requirements into stable software contracts. Creating a versioned REST API with Swagger and OpenAPI in ASP.NET Core combines three concerns that are often separated: resource design, client compatibility and executable documentation. A clear contract lets developers work in parallel, gives testers a shared reference and allows consumers to integrate before the service reaches production.

The goal is to publish a deliberate interface that can evolve without surprising mobile apps, partner integrations or internal systems. OpenAPI supplies a machine-readable description of that interface, while Swagger provides tools for reading and exploring it. ASP.NET Core can derive the description from the same controllers, models and annotations used at runtime, reducing drift when a team adopts explicit versioning rather than maintaining a separate document by hand.

Define the contract before the implementation

Start with the resource and the consumer, not the URL template. A retailer might expose products, stock levels and orders as separate resources, with each operation given a stable operation identifier such as GetProduct or CreateOrder. These identifiers become part of the generated client surface and should change only when the meaning changes. Route names, HTTP verbs and payload schemas then describe how a caller reaches a resource without exposing database entities or ASP.NET Core internals.

Define request and response DTOs around business meaning. A product response can include a price in Australian dollars, an availability state and an updated timestamp, while accepting a smaller creation payload than the full resource returned later. Australian teams often work across Sydney, Melbourne and Brisbane, so timestamps should be stored in UTC and rendered with an explicit offset; daylight-saving changes affect the label, not the underlying instant.

Decide which changes are compatible before implementation. Adding an optional response field is usually safe, whereas removing a field, changing its type or making an optional request value mandatory can break generated clients. Treat those events as breaking changes and give each version a defined lifespan. This policy is particularly valuable for Australian SaaS products serving government, logistics and education customers whose own release calendars cannot always match the API team.

Connect OpenAPI generation to the build

OpenAPI and Swagger solve different jobs. OpenAPI is the specification for describing HTTP operations, schemas, parameters, responses and security requirements. Swagger is an ecosystem for tooling, including Swagger UI and code generators. ASP.NET Core commonly uses Swashbuckle to inspect the application’s API metadata, generate an OpenAPI document and serve it through endpoints such as /swagger/v1/swagger.json.

For the ASP.NET Core 3.1-era stack used around the 2020 conference, add Swashbuckle.AspNetCore, Microsoft.AspNetCore.Mvc.Versioning and Microsoft.AspNetCore.Mvc.Versioning.ApiExplorer. Register versioning before the API explorer and configure the response writers to include each supported version:

services.AddControllers();

services.AddApiVersioning(options =>
{
    options.DefaultApiVersion = new ApiVersion(1, 0);
    options.AssumeDefaultVersionWhenUnspecified = true;
    options.ReportApiVersions = true;
});

services.AddVersionedApiExplorer(options =>
{
    options.GroupNameFormat = "'v'VVV";
    options.SubstituteApiVersionInUrl = true;
});

services.AddSwaggerGen();

Configure middleware in every environment that needs documentation. In development, UseSwagger() exposes the generated document and UseSwaggerUI() provides a browser interface. In production, many teams protect the raw document or publish it only to an internal documentation portal. The OpenAPI file should still be generated during CI, even when the interactive UI is disabled.

Version routes without breaking clients

URL versioning is the most visible choice because the requested version is part of the resource path. Annotate a controller with both an API version and a version-aware route, then keep the route template identical across implementations:

[ApiController]
[ApiVersion("1.0")]
[Route("api/v{version:apiVersion}/[controller]")]
public class ProductsController : ControllerBase
{
    [HttpGet("{id}")]
    public ActionResult<ProductResponse> Get(int id) => Ok(/* ... */);
}

With versioned API explorer enabled, Swagger groups operations under the requested version instead of combining routes that differ only by the version segment. A client can load /swagger/v1/swagger.json, review the schemas and generate a request against the correct endpoint. The group name format controls how versions appear in the UI, while SubstituteApiVersionInUrl makes the generated request use the documented route.

Media-type versioning places the version in Accept, and header versioning uses a custom header such as X-Api-Version. Both keep the path stable, which helps clients that cache or route URLs aggressively. Header-based negotiation is explicit but adds client configuration; media-type negotiation follows HTTP content-negotiation rules but can be awkward for simple integrations. Whichever policy is selected, accept the advertised form and return a clear error for unsupported versions.

Do not support several version styles accidentally. Document one canonical approach, generate samples from it and test it in client contracts. A practical policy is URL versioning for public partner APIs because it is easy to inspect in logs and support tools, with a fixed default only when the absence of a version is genuinely unambiguous. The default must not conceal a request for an unknown version.

Protect compatibility and useful diagnostics

Validation and error responses belong in the contract. ASP.NET Core model validation can return ValidationProblemDetails automatically for [ApiController] controllers, and custom exceptions can be mapped to ProblemDetails with a stable type URI, status code, trace identifier and useful field errors. These details become OpenAPI response definitions when the relevant metadata is registered, so consumers see the same failure shape in Swagger and at runtime.

Compatibility testing should compare the generated OpenAPI documents for successive releases. A contract test can assert that existing operations, required parameters and response properties remain available. For deprecations, include a Deprecation or Sunset HTTP header and explain migration steps in the description. The identifier should not rely on an Australian phone number or local office hours; standard HTTP dates work consistently across the country’s UTC, Australian Eastern and Australian Central time zones.

The available version-negotiation styles suit different client behaviours:

Approach Example request Main advantage Main trade-off
URL segment GET /api/v1/products/42 Visible in logs and easy to call Version becomes part of the route
Media type Accept: application/json;v=1 Follows content negotiation More complex client headers
Custom header X-Api-Version: 1 Keeps resource URL unchanged Easy for clients to omit

Choose one style for a published interface and record it in the API governance policy. If an existing API already has traffic, retain its current convention to avoid a disruptive migration. Whichever option is used, make the selected version observable in response headers so support staff can diagnose mismatches without reconstructing intent from a request path.

Operate the API as a product

Treat generated documentation, security and testing as one delivery pipeline. Describe bearer authentication or OAuth scopes in OpenAPI so Swagger UI can prompt for a token, but never embed production credentials in source control. Generate clients in CI, compile a small consumer against them and publish the OpenAPI artifact alongside the deployed service. That gives Australian product teams in Melbourne and Brisbane a repeatable integration point even when squads release on different days.

Add telemetry for request version, operation identifier, status code and duration. These dimensions reveal whether a partner has adopted the new contract, which clients still call a retiring version and whether a schema change increased errors. Logs and metrics should use the operation identifier rather than a raw controller action name because the identifier remains stable across refactoring and maps directly to the published contract.

Finally, review the contract with local consumers rather than assuming that a global pattern fits every market. Australian organisations may invoice in AUD including GST, use ABNs in business records and expect dates to follow unambiguous day-month-year conventions. Those details belong in examples and schemas, while the API remains interoperable internationally. A versioned contract, generated OpenAPI description and disciplined compatibility checks give .NET teams a dependable foundation for growth at the C# Corner Annual Conference 2020 and beyond.

The Leela Ambience Convention Hotel

1, CBD, Maharaj Surajmal Road, Near Yamuna Sports Complex, Delhi, 110032

KNOW MORE

GENERAL QUERIES


Manish Tewatia

+91-9718-431-042

TICKET QUERIES


Atul Gupta

+91-9910-125-804