How is .NET Application Development different from Traditional Development?

.NET application development is different from the traditional development in the approach used for compilation and execution of the code.




The difference is clearly tabulated below:

Traditional Development
.NET Application Development
Your program will be compiled into an assembly language code that is very specific to the platform in which you are running your application. Using .NET Framework, your program will be compiled into an intermediate language representation called MSIL (Microsoft Intermediate Language).
Assembly language code will contain API calls specific to the current application platform. MSIL code will not contain any API calls specific to any platform.
This assembly language code is then converted into machine code. This MSIL code is then converted into machine code at runtime using CLR (Common Language Runtime).
Optimization is done by the compiler itself at compile time. Optimization is done at runtime by CLR.
The compiler is not static. It performs both compilation as well as optimization. The compiler used in this process is static meaning that it checks only for syntax and the necessary semantics.
Libraries used by your program are linked only after generating the machine code. Libraries used by your program are linked even before generating MSIL, but it is linked in an un-compiled form. This will be compiled by the compiler and it will be used by the CLR while executing the program.
Now the program is ready for execution by the operating system. The program will directly call APIs of the operating system. The program will not directly call APIs of the operating system. Instead CLR will act as a mediator. CLR will call API's of operating system and the result of execution will be returned to program.
No automatic memory management or garbage collection. Automatic memory management and garbage collection is done by CLR.
No object oriented principles are incorporated. .NET Framework Class Library provides object oriented libraries.

_______________________________________________________________________

Add to My Yahoo!


FREE Subscription

Subscribe to our mailing list and receive new articles
through email. Keep yourself updated with latest
developments in the industry.

Name:
Email:

Note : We never rent, trade, or sell my email lists to
anyone. We assure that your privacy is respected
and protected.

Visit .NET Programming Tutorial Homepage

______________________________________________________

Recommended Resource

| How do you implement Observer Design Pattern in .NET? | How do you pass data between different Tiers in .NET Architecture? | How is Classic ADO different from ADO.NET? | How is Dataadapter useful in ADO.NET? | How is Datareader different from Dataset in ADO.NET? | How is .NET Application Development different from Traditional Development? | How is HashTable different from ArrayList in .NET? | How is Inheritance achieved in C#? | How is new keyword different from override keyword during inheritance in .NET? | How is String class different from StringBuilder class in .NET? | Illustrate ADO.NET Architecture | Illustrate the importance of Server.Transfer and Response.Redirect in .NET? | Mention the different objects available in Dataset of ADO.NET | Mention the usage of Connection Object in ADO.NET | What are the commonly used methods of Dataadapter in ADO.NET? | What are the different Behavioral Design Patterns that can be used in .NET Architecture? | What are the different Creational Design Patterns that can be used in .NET Architecture? | What are the different Structural Design Patterns that can be used in .NET Architecture? | What are the methods provided by Command Objects in ADO.NET? | What is Internal Access Modifier in C#? |


| Privacy Policy for www.dotnet-guide.com | Disclosure | Contact |

Copyright - © 2004 - 2017 - All Rights Reserved.