Structure of MVC.NET

Question

Can anyone explain Architecture of the Web Apps in .Net different frameworks

Page life cycle and Structure and events

Difference of Classic ASP Vs. ASP.NET vs. MVC.NET vs. MVC.NET Core Vs. WebAps in blazers

Jaish Mathews · Answer

Before delving into the differences between MVC.NET and MVC.NET Core  it is important to first understand the distinction between .NET Framework and .NET Core . These foundational differences directly influence how the two MVC versions operate. Yes there are differences in the page life cycle between MVC.NET (based on the .NET Framework) and MVC.NET Core (part of .NET Core). These differences arise due to architectural changes and design philosophies between the two frameworks. Page Life Cycle Comparison Aspect MVC.NET MVC.NET Core Request Processing Tightly integrated with the System.Web pipeline (ASP.NET). Uses the ASP.NET Page Life Cycle which includes stages like BeginRequest  AuthenticateRequest  AuthorizeRequest  etc. Built on ASP.NET Core Middleware pipeline . A modular approach using Startup.cs and middleware for request handling. Handler Invocation Relies on the ControllerFactory to create controllers and invoke actions. Uses Routing Middleware to map requests to controllers and actions. Events Events like Application_Start  Session_Start  and Application_End are available in Global.asax for lifecycle management. Eliminates Global.asax . Lifecycle events are handled in Startup.cs via ConfigureServices and Configure . HTTP Modules & Handlers Uses HTTP Modules and Handlers for customizing the pipeline. Replaced with Middleware for greater flexibility and composability. Session State Managed by the System.Web pipeline with options for InProc StateServer or SQL Server. Session is optional and configured explicitly via middleware. Filters Supports Action Filters  Authorization Filters  Result Filters  and Exception Filters through attributes. Similar filter types are available but enhanced with dependency injection and extensibility. Dependency Injection Requires third-party libraries for DI integration. Built-in dependency injection system simplifies controller lifecycle and dependency resolution. Action Execution Lifecycle involves Controller.Execute  followed by action filters model binding and result execution. Streamlined execution pipeline with middleware-driven execution and enhanced extensibility. View Rendering Tightly coupled to the Razor View Engine. Razor View Engine remains but it is decoupled and can work alongside other templating engines. Key Differences Middleware Over System.Web Pipeline : MVC.NET Core replaces the rigid System.Web pipeline with a middleware-based approach making the life cycle more flexible and modular. Developers can control and customize the request pipeline through middleware components. No Global.asax : MVC.NET Core removes Global.asax . Instead application startup and configuration are managed in Startup.cs with methods like ConfigureServices and Configure . Session and State Management : Session management in MVC.NET is part of the page lifecycle. In MVC.NET Core  session must be explicitly enabled as middleware and is not tied to the default pipeline. Routing : MVC.NET uses RouteConfig to configure routes in Global.asax . MVC.NET Core integrates routing as part of the middleware pipeline managed in Startup.cs . Event Model : MVC.NET relies heavily on event-driven programming. MVC.NET Core uses the middleware model which is simpler and more aligned with modern practices. Summary While both frameworks process requests and generate responses MVC.NET Core introduces a streamlined middleware-driven lifecycle that is more modern and modular than the traditional System.Web -based lifecycle in MVC.NET . This leads to better performance flexibility and control over how requests are handled and processed.

Sangeetha S · Answer

1.Structure of MVC.NET Architecture MVC (Model-View-Controller) is a design pattern used in .NET applications to separate concerns: Model : Represents the data and business logic. It handles data retrieval storage and validation. View : The user interface that displays the data. Views are typically .cshtml files in ASP.NET MVC. Controller : Manages the flow of the application. It handles user input interacts with the model and selects the view to render. 2. Architecture of Web Apps in .NET Frameworks .NET offers several frameworks for building web applications: ASP.NET Web Forms : Event-driven model with a page lifecycle. Suitable for rapid application development. ASP.NET MVC : Follows the MVC pattern providing better separation of concerns and testability. ASP.NET Core : A cross-platform modular framework that combines the best of ASP.NET MVC and Web API. Blazor : Allows building interactive web UIs using C# instead of JavaScript. It can run on the server or client-side (WebAssembly). 3. Page Lifecycle in ASP.NET Web Forms The ASP.NET Web Forms page lifecycle involves several stages: Page Request : A request is made for a page. Start : The page is initialized. Initialization : Controls on the page are initialized. Load : Page and controls load data. Postback Event Handling : Events are handled if it’s a postback. Rendering : The page is rendered into HTML. Unload : Cleanup activities occur. Comparison of Classic ASP ASP.NET MVC.NET MVC.NET Core and Blazor: Classic ASP Type: Server-side scripting Language: VBScript or JScript Architecture: Monolithic Features: Simple lightweight but limited in functionality and scalability. Use Case: Suitable for small simple web applications. ASP.NET Type: Web framework Language: C# or VB.NET Architecture: Web Forms model (Event-driven) Features: Rich server controls state management and event-driven programming. Use Case: Good for enterprise-level applications but can be heavy. MVC.NET (ASP.NET MVC) Type: Framework for building web applications Language: C# Architecture: MVC (Model-View-Controller) Features: Separation of concerns testability and cleaner code organization. Use Case: Ideal for applications requiring more control over HTML and URLs. MVC.NET Core Type: Cross-platform web framework Language: C# Architecture: MVC (also supports Razor Pages) Features: Lightweight high performance cross-platform and modular. Use Case: Best for modern web applications and services especially cloud-based. Blazor Type: Framework for building interactive web UIs Language: C# Architecture: Can run on the server (Blazor Server) or client-side (Blazor WebAssembly) Features: Allows C# to be used for both client and server-side code rich UI components. Use Case: Great for building SPAs (Single Page Applications) with a modern approach. Summary Classic ASP: Basic older technology. ASP.NET: More powerful suitable for large applications. MVC.NET: Focuses on structure and testability. MVC.NET Core: Modern cross-platform and high-performance. Blazor: Combines C# for both client and server great for interactive apps.

Kiran Kumar · Answer

I think it is fine I get in list format you mentioned page events only in ASP.NET Web form can I get the same format for other types of apps Classic ASP I think not event based but others should have some pattern of event execution right can I get it

Kiran Kumar · Answer

Hi Sasi It was a good explanation But in that I need a few clarifications Architecture - MVC.NET Vs MVC.NET Core MVC.NET also has same middleware that has the models right so what is the exact difference State Management - MVC.NET Vs MVC.NET Core You mentioned no viewstate if no state management there should be alternative state management right can you tell me what it is Also you mentioned overall differences But can you find me what are the page events differences if it isn't matching each one in separate detail list of events or any diagrams I can get an idea of it

sasikala s · Answer

Difference of Classic ASP Vs ASP.NET vs MVC.NET vs MVC.NET Core Vs WebAps in blazor Feature Classic ASP ASP.NET MVC.NET MVC.NET Core Blazor Architecture Procedural Web Forms MVC MVC with Middleware Component-based Page Life Cycle Simple Complex MVC pattern Similar to MVC Component lifecycle Language VBScript C# or VB.NET C# C# C# State Management Session Cookies ViewState Session No ViewState No ViewState State management with components Performance Moderate Good Better than Web Forms High performance High performance Cross-Platform No No No Yes Yes Development Model Less structured Event-driven Structured Modular Component-driven Use Cases Simple web apps Enterprise apps Web apps with complex UIs Modern web apps Single-page applications Each of these technologies has its strengths and is suitable for different types of applications. Classic ASP is less common today while ASP.NET MVC and Core are widely used for modern web applications. Blazor offers a fresh approach with C# for client-side development.