Skip to main content

Evolution of .NET Frame work

          Microsoft .Net technology has a rapid development and great success over the years. This is one of the best development platforms and accepted by all levels of peoples. The features like interoperability, security, portability, simplicity and maintainability makes the .NET technology as great. The .Net framework created on the year 2002 and still the features added and various versions of framework released for advanced software development.

What is .Net Framework?

          The .NET Framework is an integral Windows component that supports building and running the next generation of applications and XML Web services. The .NET Framework is designed to fulfill the following objectives:
  • To provide a consistent object-oriented programming environment whether object code is stored and executed locally, executed locally but Internet-distributed, or executed remotely.
  • To provide a code-execution environment that minimizes software deployment and versioning conflicts.
  • To provide a code-execution environment that promotes safe execution of code, including code created by an unknown or semi-trusted third party.
  • To provide a code-execution environment that eliminates the performance problems of scripted or interpreted environments.
  • To make the developer experience consistent across widely varying types of applications, such as Windows-based applications and Web-based applications.
  • To build all communication on industry standards to ensure that code based on the .NET Framework can integrate with any other code.
Evolution of Framework
          
         The figure shows the step by step growth of framework with its feature.




Framework 1.0

      .NET framework scratch started from the version 1.0 and later it is updated as 1.1. The version 1.1 is consistent and available in Microsoft Visual Studio 2003.


Framework 2.0

        .NET framework 2.0 provide a significantly better and more productive environment for people who design and write Windows software. released on 2005 and it has the updates over the version 1.0.  Microsoft visual studio 2005 is the IDE for .Net framework 2.0. The Features are listed below.
  • Master Pages
  • Themes
  • Web Parts
  • Navigation Controls
  • Login Controls
  • Roles and Personalization
  • Data Access using XML
  • Internationalization
  • Automatic Compilation(WSDL and XSD)
  • Compiled Deployment and Source Protection

  • Generics and Generic Collections
  • Anonymous methods
  • Globalization
  • .NET Framework Remoting
  • Serialization
  • SMTP Support
  • Transactions
  • Web Services
  • Authenticated Streams (SSL)
  • COM Interop Services Enhancements
  • Debugger Edit and Continue Support
  • Distributed Computing
  • Manifest-Based Activation

Framework 3.0

          The Microsoft stated summary as Version 3.0 of the Microsoft .NET Framework provides a diverse set of technologies, each addressing a significant challenge in application development today.
The .NET Framework 3.0 (formerly known as WinFX) is the next step of progression. Applications built on this new version of the Framework can be created with Visual Studio 2005, making it feel familiar to most Windows developers. But the .NET Framework 3.0 is also an evolution, adding more to what version 2.0 of the Framework already provides. Scheduled to be released in late 2006, the .NET Framework 3.0 will be available for Windows Vista, Windows Server 2003, and Windows XP.
Features are
  • Windows Communication Foundation (WCF)
  • Windows Presentation Foundation (WPF)
  • Windows Workflow Foundation (WWF)
  • Windows Card space (WC)


Framework 3.5



           In Framework 3.5 some more features are added with the existing version 3.0 they are,

  • Linq for SQL, XML, Dataset, Object
  • Addin system
  • p2p base class
  • Active directory
  • ASP.NET Ajax
  • Anonymous types with static type inference
  • Paging support for ADO.NET
  • ADO.NET synchronization API to synchronize local caches and server side datastores
  • Asynchronous network I/O API
  • Support for HTTP pipelining and syndication feeds.
  • New System.CodeDom namespace.
 

Framework 4.0
 
           In .NET Framework 4.0 there are features added with the existing version 3.5
  • Updated CLR
  • Client Data Access
  • Client data controls
  •  Client templates
  • Client data context
  • Setting Meta keyword and Meta description:
  • Enableviewstage property for each control
  • Setting Client IDs
  • Web.config File Refactoring
  • Extensible Output Caching
  • Auto-Start Web Applications
  • Permanently Redirecting a Page
  • Shrinking Session State
  • Expanding the Range of Allowable URLs
  • Extensible Request Validation
  • Object Caching and Object Caching Extensibility
  • Extensible HTML, URL, and HTTP Header Encoding
  • Performance Monitoring for Individual Applications in a Single Worker Process
  • Multi-Targeting


Framework 4.5

          Asynchronously Reading and Writing HTTP Requests and Responses
Improvements to HttpRequest handling
Asynchronously flushing a response
Support for await and Task-Based Asynchronous Modules and Handlers

Comments

Popular posts from this blog

N-Tier Architecture Design Using MVC, Entity Framework and WCF

 

MVC or Web Forms

I.          I think both technologies can get a bit complicated after getting past any of the basics. Here are some brief opinions that I gathered while having to implement a project that must live in both MVC and WebForms hosts. WebForms Positives: The maturity of the product Lots of 3rd party support with regard to sophisticated controls There are ways to get around the legacy-feeling aspects of the framework (e.g., WebForms MVP ) WebForms Negatives: Page lifecycle issues can anger you to no end; there are a lot of moving parts to a sophisticated web application Using dependency injection is "difficult" to use/implement There is a lot in the framework that you can't control Need something like Reflector to dive into decompiled source when have questions that are not answered by documentation, web, experimentation. MVC Positives: Great separation of concerns and support of dependency injectio