Shivprasad Koirala Pdf — .net Interview Questions By

It is not perfect. It is not always up-to-date. But it is honest, clear, and practical. For every developer who has nervously waited in a corporate lobby, clutching a printout of those yellowed pages, it represents one thing: .

For over a decade, this document has been passed around like a sacred scroll: uploaded to SlideShare, shared on Google Drive, attached in forum replies, and downloaded from forgotten corners of the internet. If you have ever prepared for a .NET interview in India, the Middle East, or anywhere with a strong outsourcing IT culture, you have almost certainly encountered it. But what makes this PDF so enduring? Why do hiring managers still ask questions straight out of its pages? And who is Shivprasad Koirala? Shivprasad Koirala started as a typical .NET developer in the early 2000s, working on enterprise applications. But he noticed a painful gap: freshers and even mid-level developers struggled with conceptual, architectural, and internals-based questions during interviews. Most could write a for loop or use a GridView , but ask them “What is the difference between a thread and a process?” or “How does garbage collection work in .NET?” — and they would freeze. .net interview questions by shivprasad koirala pdf

The PDF became an overnight success in developer communities — especially in India, where certification-driven rote learning was common, but deep conceptual understanding was rare. The PDF bridged that gap. “It’s not about memorizing answers,” Koirala once wrote in an introduction. “It’s about understanding the ‘why’ behind the ‘what’.” The PDF, typically spanning 150–250 pages depending on the version, is not a textbook. It is a compendium of frequently asked interview questions across key .NET domains. The structure is brutally practical: Core Sections (Typical Contents) | Domain | Example Questions | |--------|------------------| | C# Fundamentals | Difference between abstract class and interface ; sealed classes; partial classes; boxing vs unboxing | | Object-Oriented Programming | Is C# purely OOP? Real-world polymorphism example; composition vs inheritance | | ASP.NET (Web Forms & MVC) | ViewState vs Session; page lifecycle; difference between Response.Redirect and Server.Transfer | | SQL Server | Primary vs clustered index; triggers vs stored procedures; difference between DELETE , TRUNCATE , DROP | | ADO.NET | Connected vs disconnected architecture; DataSet vs DataReader | | Multithreading | Thread vs ThreadPool vs Task; lock vs Monitor; deadlock avoidance | | Design Patterns | Singleton, Factory, Repository – with .NET-specific examples | | Web Services / WCF | SOAP vs REST; BasicHttpBinding vs WsHttpBinding | | MVC | ViewBag vs ViewData vs TempData; routing; filters | | General .NET | CLR, CTS, CLS, JIT, Garbage Collection generations | It is not perfect