.NET Development

This course exists because Pakistani employers ask for it more than any other technology we do not teach: seven of the hundred we researched named it, including NETSOL and Autosoft Dynamics, whose core-banking work runs on it. Two honest things about that. First, .NET work in Pakistan concentrates in enterprise and banking software, which means larger, slower, older codebases than the startup work a Full-Stack or MERN graduate walks into; some people love that and some do not. Second, one employer's posting still names WCF, a Microsoft technology that has been superseded, you will meet legacy alongside modern here, which is the honest shape of enterprise work. All tooling is free: Visual Studio Community, .NET SDK and SQL Server Developer Edition cost nothing.

Apply for this course

Every employer naming .NET also named OOP. Interview reports say the same. This module is why.

• Types, references and value semantics hands on
  Classes vs structs, what a reference copy actually copies, null and nullable reference types.
• Encapsulation, inheritance, polymorphism, interfaces hands on
  Not as vocabulary for an interview, as the thing that makes a large codebase survivable.
• Collections, LINQ and iterators hands on
  Querying in-memory data. LINQ is the idiom you will read in every C# codebase you join.
• Exceptions and what to do with them hands on
  Catching what you can act on, letting the rest travel, and never swallowing an error silently.
• async and await hands on
  Where the thread actually goes. The single most misunderstood part of modern C#.
• Testing with xUnit hands on
  Writing a test before the fix. Employers name automated testing; most graduates cannot do it.

Named by NETSOL and Autosoft explicitly, and NETSOL's postings specify large databases.

• Schema design and normalisation hands on
  Keys, relationships, constraints. Getting this wrong is the most expensive mistake in the course.
• T-SQL beyond SELECT hands on
  Joins, grouping, subqueries, window functions. Reading somebody else's query.
• Stored procedures hands on
  Named by S&P Global too. Where enterprise logic often lives, whether or not you approve.
• Indexes and why a query got slow hands on
  Reading an execution plan. NETSOL's postings say large databases; this is what that means in practice.
• Transactions and concurrency hands on
  What happens when two people write at once. Banking software is built on the answer.
• Entity Framework Core hands on
  Mapping objects to tables, migrations, and spotting the N+1 query the ORM just wrote for you.

The centre of the course. Every .NET employer in the pipeline builds these.

• The request pipeline and middleware hands on
  What actually happens between a request arriving and your code running.
• Controllers, routing and model binding hands on
  Building a REST API that behaves the way a client expects.
• Dependency injection hands on
  Built into the framework, and the reason .NET codebases are testable. Lifetimes, and the bugs each one causes.
• Validation and error responses hands on
  Rejecting bad input at the edge, and returning a problem a caller can act on.
• Authentication and authorisation hands on
  JWT bearer tokens and role-based policies. Systems Limited's posting names JWT and OAuth.
• Configuration and secrets hands on
  appsettings, environments, user secrets. Nothing sensitive in the repository, ever.

Autosoft names jQuery, Bootstrap and AJAX; NETSOL names Angular and React. That mix is real and this module reflects it rather than the fashion.

• Razor Pages and server-rendered views hands on
  Still how a large share of Pakistani enterprise .NET applications are built.
• HTML, CSS and Bootstrap layout hands on
  Named directly by Autosoft. Building a usable form and table without a design system.
• JavaScript, jQuery and AJAX against your own API hands on
  jQuery is not fashionable and it is in the codebase you will join. Reading and maintaining it.
• Where a SPA fits
  Angular and React consuming an ASP.NET API. Enough to work with a front-end colleague, not to replace one.

A complete application, with the parts employers complain graduates skip.

• Layering an application hands on
  Separating API, business logic and data access so a change stays in one place.
• Logging and diagnosing production hands on
  Structured logs, correlation ids, and finding out what a user actually did.
• Publishing and hosting hands on
  Deploying to IIS and to a Linux container. Configuration per environment.
• Azure, at the level Confiz asks for hands on
  App Service, SQL Database and Blob Storage, the three you will actually meet.
• Legacy you will inherit
  Reading .NET Framework and WCF code without rewriting it. NETSOL's stack still names WCF; pretending otherwise would not survive your first week.

The habits every one of these employers assumes and few graduates arrive with.

• Git in a team hands on
  Branches, pull requests, reviewing somebody else's code and having yours reviewed.
• Reading a codebase you did not write hands on
  The actual first task in an enterprise job. Finding where a change belongs.
• Debugging in Visual Studio hands on
  Breakpoints, watches, call stacks. Faster than adding print statements, and most graduates never learn it.
• The technical interview these employers run hands on
  OOP, database design, SQL queries and data structures, exactly what candidate reports from NETSOL describe.

A layered business application with an API, a database and a front end

Build something a small business would use: stock and invoicing, admissions, a booking system. ASP.NET Core API over SQL Server with Entity Framework, a working front end, authentication with roles, validation at the edge, structured logging, and an xUnit test suite covering the business rules. Deployed and reachable. Marked on the layering and the tests as much as the features: employers in this sector hire people who can be trusted in a large codebase, and that is what those two things demonstrate.

A final assessment marked out of 100; the pass mark is 60, with 120 minutes to complete it.

• C#, OOP and async (25 marks)
• SQL Server, T-SQL and Entity Framework (25 marks)
• ASP.NET Core APIs, DI and auth (30 marks)
• Front end and integration (10 marks)
• Testing, logging and deployment (10 marks)

Students who pass the final assessment and have project work verified by their trainer receive a completion letter. It states attendance, the assessment result and the projects verified, and carries a code any employer can check at the verification page.

No verified NAVTTC alignment. No published lesson plan has been checked against this syllabus module by module, as the CEH mapping was. Map it before quoting it in a bid. This course is taught to BvLogic's own syllabus, published in full above.

Interested in this programme?

Apply now, or try the subject free first: there is no reason to pay before you know you like it.