Skip to main content

ASP.NET MVC Interview Questions Part 1


1) What is MVC generally?
M - Model  --> Contains Data and information on how to handle data (Business Logic)

 V - View --> Representation of data to the user (User Interface, Front End)

 C - Controller --> Sits between the Model and View, acts as interface between them, basically the controller takes the user request and provide the view with correct model data  
This is software developing pattern which implements Seperation of Concerns (SoC), which decouples all the three components to enable it for better parallel programming,

2) What are the Advantages of MVC pattern

 Easy and Fast Development of code
More meaningful URLs which provides the competetive edge over traditional URLs 
Change Friendly
Maintenance Friendly
Test Friendly (Test Driven Development is fully supported)
Easy to divide the application and respective teams such as Design Team, Developent Team, Database Team can collaboratively work


3) What is the current stable version of ASP.NET MVC (June 2018)

 The current version of ASP.NET MVC is 5.2.5

 4) What is ASP.NET Routing?  

 ASP.NET Routing is the concept of mapping the incoming request (URL) with the existing resources (may be pages but not always to the pages)

 Detailed Explanation Here



5) What is Global.asax file

The Global.asax file is called as the ASP.NET application file, which contains the events related to Application and Session level

The file will be positioned in the root level of the Web Application.

Detailed Explanation Here and Here


Labels:

Comments

Post a Comment

Popular posts from this blog

Using of global variables in C# - Drawbacks & Solutions

How using global variables can have implications on the design, maintainability, and test-ability of C# code: Harder to understand and reason about the code:       class Program     {         public static int globalCounter = 0;         static void Main()         {             globalCounter++;             Console.WriteLine(globalCounter);         }     }   In this example, the global variable globalCounter is accessible from anywhere in the program, including the Main method. It's not clear where the value of the globalCounter is updated, it could be updated in other methods or classes, making it harder to trace the flow of data and understand the source of bugs.   More prone to errors:       class Program     {         public static string globalString;         static void Main()         {             globalString = "Hello" ;             Method1();             Method2();         }         static void Method1()         {
Post a Comment
Read more

Task Parallel Library (TPL) and Akka.NET Alternatives

Task Parallel Library (TPL) and Akka.NET are among the most commonly used libraries for parallel and concurrent programming in the .NET ecosystem. However, there are also several other options available, depending on your specific needs: Parallel Language Integrated Query (PLINQ) is a parallel programming feature of .NET that provides an easy and efficient way to perform operations on collections in parallel. LINQ (Language Integrated Query) is a powerful feature in .NET that allows developers to work with data in a more declarative and language-integrated manner. While LINQ queries are inherently sequential, PLINQ extends LINQ by providing parallel versions of the query operators, allowing some queries to execute faster by utilizing multiple processors or cores on a machine. PLINQ is great when you are working with large collections where operations might be CPU-intensive or I/O-bound and could potentially be sped up by parallel execution. Here is a simple example of a PLI
Post a Comment
Read more

SOLID Principles with Real World examples in C#

  SOLID Principles with Real World examples in C#   SOLID principles are formed by using S Single Responsibility Principles (SRP) O Open Closed Principle (OCP) L Liskov’s Substitution Principle (LCP) I Interface Segregation Principle (ISP) D Dependency Inversion Principle (DIP)   S Single Responsibility Principles (SRP) There should never be more than one reason for a class to change, to be precise one class should have only one responsibility Single Responsibility Principles (SRP) Real world example, A perfect match for SRP is Microservices , a Microservice will not contain functionalities other than the one it is designated to do,  Example ·                   Order Processing Service, ·                   Shipment Management Service, ·                   User Authentication Service, ·                   Catalogue List Service       class OrderProcessor     {         public void Process(Order order)         {             // Check inven
Post a Comment
Read more