Skip to main content

Journey from ASP.NET Framework to .NET Core

Initial development with ASP.NET framework

Initially, projects were developed using ASP.NET Framework, which provided various options for user interfaces.

  • Windows forms (WinForms): For desktop applications with rich UI controls.
  • Windows presentation foundation (WPF): For desktop applications with advanced graphics and multimedia support.
  • ASP.NET web forms: For web applications with a component-based UI model and event-driven programming.

Transition to ASP.NET MVC

  • As web development evolved, ASP.NET MVC (Model-View-Controller) emerged as a popular framework for building web applications using the ASP.NET Framework. ASP.NET MVC introduced a more structured approach to web development, separating concerns into models, views, and controllers.
  • ASP.NET MVC allowed developers to create web applications with cleaner code architecture, better testability, and improved control over HTML markup.

Introduction of .NET Core

  • With the advent of .NET Core, Microsoft introduced ASP.NET Core, a cross-platform, high-performance framework for building modern web applications and services.
  • ASP.NET Core MVC is the web framework included in ASP.NET Core, providing similar functionality to ASP.NET MVC but with enhancements and optimizations for performance, scalability, and cross-platform development.

Integration of AngularJS and Angular

  • While ASP.NET Framework and ASP.NET Core MVC provide server-side rendering of UI components, it's common to integrate client-side frameworks like AngularJS (for older projects) or Angular (for newer projects) to build interactive, dynamic user interfaces.
  • In the ASP.NET Framework, AngularJS can be integrated with server-side code to create single-page applications (SPAs) and enhance the user experience.
  • In ASP.NET Core, Angular is often preferred for its modern features, performance, and ecosystem support. ASP.NET Core provides seamless integration with Angular for building SPAs or using Angular components within server-rendered views

.Net Framework and .Net Core Version
 

S.No.ReleaseRelease Date
1.NET Framework 1.013-Feb-02
2.NET Framework 1.124-Apr-03
3.NET Framework 2.007-Nov-05
4.NET Framework 3.006-Nov-06
5.NET Framework 3.519-Nov-07
6.NET Framework 4.012-Apr-10
7.NET Framework 4.515-Aug-12
8.NET Framework 4.5.117-Oct-13
9.NET Framework 4.5.205-May-14
10.NET Framework 4.620-Jul-15
11.NET Framework 4.6.130-Nov-15
12.NET Core 1.027-Jun-16
13.NET Core 1.116-Nov-16
14.NET Core 2.014-Aug-17
15.NET Core 2.130-May-18
16.NET Core 2.204-Dec-18
17.NET Core 3.023-Sep-19
18.NET Core 3.103-Dec-19
19.NET 510-Nov-20
20.NET 608-Nov-21
21.NET 708-Nov-22
22.NET 814-Nov-23
23.NET 92024
24.NET 102025

Comments

Post a Comment

Popular posts from this blog

How to write Unit Tests in .net

Unit tests are automated tests that verify the behavior code like methods and functions. Writing unit tests is crucial to clean coding, as they help ensure your code works as intended and catches bugs early in the development process. I can share some tips for writing effective unit tests: Write tests for all public methods Every public method in your code should have a corresponding unit test. This helps ensure that your code behaves correctly and catches any unexpected behavior early. public class Calculator { public int Add(int a, int b) { return a + b; } } [TestClass] public class CalculatorTests { [TestMethod] public void Add_ShouldReturnCorrectSum() { // Arrange Calculator calculator = new Calculator(); int a = 1; int b = 2; // Act int result = calculator.Add(a, b); // Assert Assert.AreEqual(3, result); } } Test boundary conditions  Make sure to test boundary conditions, such a...
Post a Comment
Read more

What to choose between .NET Core and .NET?

 .NET Framework is a better choice if you: you don't have enough time time to learn new technology. Need a stable environment to work in. Have nearer release schedules. you are already working on an existing app and extending its functionality. If already have an existing team with .NET expertise and building production-ready software. Do not want to deal with continuous upgrades and changes. Building Windows client applications using Windows Forms or WPF .NET Core is a better choice if you: IF you wanted to deploy your app on Windows, Linux, and Mac operating systems. Are not afraid of learning new things. Are not afraid of breaking and fixing things since .NET Core is not fully matured yet. When you are learning .NET. work on open source.
Post a Comment
Read more