ASP.NET
  Home arrow ASP.NET arrow Page 4 - The Evolution Of Microsoft: .NET Explained
Dev Articles Forums 
ADO.NET  
Apache  
ASP  
ASP.NET  
C#  
C++  
ColdFusion  
COM/COM+  
Delphi-Kylix  
Design Usability  
Development Cycles  
DHTML  
Embedded Tools  
Flash  
Graphic Design  
HTML  
IIS  
Interviews  
Java  
JavaScript  
MySQL  
Oracle  
Photoshop  
PHP  
Reviews  
Ruby-on-Rails  
SQL  
SQL Server  
Style Sheets  
VB.Net  
Visual Basic  
Web Authoring  
Web Services  
Web Standards  
XML  
Mobile Linux 
App Generation ROI 
IBM® developerWorks 
Weekly Newsletter
 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid 
Request Media Kit
Contact Us 
Site Map 
Privacy Policy 
Support 
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
ASP.NET

The Evolution Of Microsoft: .NET Explained
By: James Yang
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 3 stars3 stars3 stars3 stars3 stars / 21
    2001-12-23

    Table of Contents:
  • The Evolution Of Microsoft: .NET Explained
  • What is .NET?
  • Understanding .NET
  • The .NET framework (contd.)
  • The .NET framework(contd.)
  • Web Services
  • Conclusion

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      Del.ici.ous Digg
      Blink Simpy
      Google Spurl
      Y! MyWeb Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article
     
     
    ADVERTISEMENT


    The Evolution Of Microsoft: .NET Explained - The .NET framework (contd.)


    (Page 4 of 7 )

    .NET framework base classes

    The .NET framework base classes are a collection of built-in functions, objects, properties and methods that can be utilised by any .NET compatible language. ADO.NET resides in this part of the .NET architecture, and provides developers with functions, objects, properties and methods to access, view and manipulate databases. The tools that we require as developers to work with XML are also included in these base classes.

    The Common Language Runtime

    The Common Language Runtime (CLR) is the heart of the .NET framework, and is responsible for the execution and management of .NET Applications, as well as the compilation of .NET applications into native code. The CLR is the environment under which .NET applications are ran.

    The CLR offers developers many useful and important features and benefits: Simpler Rapid Application Development (RAD), memory management, scalability and common approach programming/cross language integration.

    Simpler Rapid Application Development

    The concept of rapid application development is not a new one. Because the .NET framework base classes provide developers with pre-written, built-in functionality, and the ability to reuse source code that already exists, the amount of code that a developer needs to write to create an application is reduced by a significant amount.

    Memory Management

    Memory management is one of the most important features provided by the CLR. It works behind the scenes, and gives developers more of an opportunity to concentrate on building their application, rather than worrying about the nitty-gritty aspects of memory management. When the CLR allocates memory to variables and objects declared within an application, its garbage collection (GC) mechanism makes sure that whenever a value is assigned NULL, or goes out of scope, that its memory is freed, and can be allocated to another variable or object right away. This significantly reduces the amount of memory wasted by applications.

    Scalability

    Increased scalability is a direct result from the issues I have already discussed above, including rapid application development and memory management. Rapid application development allows you to spend more time tweaking and improving your applications performance, while the built-in memory management features of the CLR improves the in-memory performance and number of resources available to your application at any given time.

    Cross-Language Integration

    This feature is probably the most talked about when developers are discussing .NET. It is a radical and very significant change from the traditional concepts, because it brings all of the .NET languages up-to-par with each other. For example, although C++ is generally considered and accepted as being more powerful that Visual Basic, .NET has discarded this idea. All .NET applications are compiled into Intermediate Language (IL). The Intermediate Language equalises the power, complexity and optimisation across all of the .NET languages before they are compiled into native machine code.

    For a programming language to be considered “.NET compatible”, its source code must be able to be compiled into Intermediate Language.

    More ASP.NET Articles
    More By James Yang


     

    ASP.NET ARTICLES

    - How Caching Means More Ca-ching, Part 2
    - How Caching Means More Ca-ching, Part 1
    - Reading a Delimited File Using ASP.Net and V...
    - What is .Net and Where is ASP.NET?
    - An Object Driven Interface with .Net
    - Create Your Own Guestbook In ASP.NET
    - HTTP File Download Without User Interaction ...
    - Dynamically Using Methods in ASP.NET
    - Changing the Page Size Interactively in a Da...
    - XML Serialization in ASP.NET
    - Using Objects in ASP.NET: Part 1/2
    - IE Web Controls in VB.NET
    - Class Frameworks in VB .NET
    - Cryptographic Objects in C#: Part 1
    - Sample Chapter: Pure ASP.Net







    © 2003-2009 by Developer Shed. All rights reserved. DS Cluster 1 Hosted by Hostway
    For more Enterprise Application Development news, visit eWeek