The Essence of Microsoft's .NET Framework
page 7 of 12
by Saripalli Koti Reddy
Average Rating: 
Views (Total / Last 10 Days): 59197/ 174

Four Major Components of .NET Framework 3.0 [WinFx]

Windows Presentation Foundation [WPF]

WPF, formerly code named Avalon, is the graphical sub system feature of the Microsoft .NET Framework 3.0 [WinFx].

WPF provides a consistent programming model for building next generation user experiences with User Interface [UI], Media and Documents and provides a clear separation between the User Interface and the business logic [Code Behind] by relating itself to the Extensible Application Markup Language [XAML] to store all the UI related information, whereas, the business logic will be placed within the corresponding .xaml.cs file.

WPF enables developers and designers to create visually stunning user interfaces.

WPF addresses the communication gap between the Multimedia Designer and Developer by enabling the Designers to create their design in the form of XAML by using XAML Designers, such as Microsoft Expressions and Developers, to directly use that XAML file and then define the business logic for it.

WPF enables the Developers to create 2D or 3D graphics through declarative programming.

WPF applications can be deployed on the desktop or hosted in web browser.

Check out my future article "Hands on WPF" for many more features and in depth discussion on WPF.

Windows Communication Foundation [WCF]

WCF is one of the four major components introduced as part of .NET Framework 3.0 [WinFx]. WCF is formerly known as "Indigo."

Development of "Indigo" began in early 2001, even before the completion of the first version of the .NET Framework. At the time, it was thought that Indigo would be released alongside "Longhorn," then the codename for a version of Windows that would ship in 2003 or 2004. Indigo made its first public appearance at the 2003 Professional Developers Conference as one of the "pillars of Longhorn." As Longhorn's release was delayed, Indigo's release was delayed as well.

On January 18, 2006, Microsoft released a preview of the WinFX runtime components and a run-time license for Windows Communication Framework.[1] The components made available included the WinFX Runtime Components, WinFX SDK, and Visual Studio Extensions for Workflow, and Visual Studio "Orcas" CTP Development tools for WinFX. Server applications based on this technology could be used in production development environments with the acquisition of a free license.

Final sign-off on Windows Communication Foundation came on November 3, 2006, almost six years after its inception and the release came a few days later.[1]

WCF unifies Web Services, .NET Remoting, COM+ Enterprise Services and Message Queues into a single "Service Oriented Programming" model.

WCF = ASMX [with WSE] + .NET Remoting + COM+ Enterprise Services + MSMQ

WCF is designed in accordance with Service oriented architecture principles to support Distributed computing where services are consumed by consumers. Clients can consume multiple services and services can be consumed by multiple clients. Services typically have a WSDL interface which any WCF client can use to consume the service, irrespective of which platform the service is hosted on. WCF implements many advanced WS* web services standards such as WS-Addressing, WS-ReliableMessaging and WS-Security. While Microsoft is a board member of WS-I it is not clear how many WS-I profiles they are committing to support fully.

Check out my future article "Building First WCF Service…" for a hands-on demonstration of WCF.

Windows Workflow Foundation [WF]

Workflow is a set of activities that coordinates people and/or software to perform a result oriented business process.

Windows Workflow Foundation is useful for defining, executing, and managing workflows. Windows Workflow Foundation API provides Programming model, engine, and tools for building workflow enabled applications.

Extensible Object Modeling Language [XOML] based on XAML is used for declaring the structure of workflow, business logic for the workflow activities can be defined within the .Net aware programming languages (such as C# .NET, …) within the .xoml.cs file.

Check out my future article "Building First Workflow Enabled Windows Application" for a hands-on demonstration of WF.

Windows Card Space [WCS]

WCS, formerly called InfoCard, is a framework developed by Microsoft which securely stores digital identities of a person and provides a unified interface for choosing the identity for a particular transaction, such as logging in to a website.

WCS is a central part of Microsoft's effort to create an Identity Metasystem or a unified, secure and interoperable identity layer for the internet.

WCS allows users to create self-issued identities for themselves, which can contain one or more of around 15 fields of telephone-book quality identity information. Other transactions may require a managed identity issued by a trusted identity provider, such as a bank, employer or a governmental agency.

WCS is built on top of Web Services Protocol Stack, an open set of XML-based protocols, including WS-Security, WS-Trust, WS-Metadata Exchange and WS-SecurityPolicy. This means that any technology or platform which supports WS-* protocols can integrate with CardSpace.

View Entire Article

User Comments

Title: Inappropriate details   
Name: Ehtesham Siddiqui
Date: 2010-11-23 3:15:24 AM
Not satisfactory
Title: straight to the xact research   
Name: Yonela
Date: 2009-03-23 3:25:09 PM
It would be nice to get the necessary information when browsin, it would make life much easier.but thakyou very much for the as i know tyou are doin all you can to make searching simple
Title: important information at one place   
Name: pallavi
Date: 2009-03-22 8:27:23 AM
the article is very good.
From this we can have clear idea of .net framework details from 1.0 till 3.5
Title: Thank You   
Name: Koti Reddy. Saripalli
Date: 2009-01-10 8:07:39 AM

Thanks for all your comments, as there are no auto notifications within this site, you can also mail me your comments over or for immediate response.

Title: The Essence of Microsoft's .NET Framework   
Name: Jagannath
Date: 2009-01-06 4:43:34 AM
Excellent Presentation of Evolution of Indigo/WCF + Basics

(Attended your Session on Basics of DOTNET @ Synergy(Ravi Pola)
Title: The Essence of .net framework   
Name: Sridhar
Date: 2008-08-06 3:46:30 AM
"Every developer of Microsoft technologies has come across Win32 Application Programming Interface [API] and the Principle API of all the Microsoft windows operating systems. But in upcoming versions of Microsoft Operating Systems, such as Windows Vista, Win32 API will no longer be the principal API."

This is not true. The number of new Win32 APIs in Vista/Server 2008 indicate that contrary to what you are claiming, there is a lot of new work/innovation going on with respect to native code and programming models.

Also please refer any code that runs outside the CLR as "native" code. Unmanaged is not the right way to describe it as most languages ( have ways (better?) to handle their state, not to mention memory and resources.
Title: The Essence of Microsoft's .NET Framework   
Name: Venkat
Date: 2008-05-23 8:50:29 AM
Its really very good article and excellent prasentation
Title: .NET Framework 3.0 [WinFx] - Here It Goes…   
Name: Dileep
Date: 2007-12-12 6:31:00 AM
good information and presentation..
u r always great in ur presentations..

dileep (your student in .net ur fan always)
Title: ---   
Name: ---------
Date: 2007-02-16 2:11:20 PM
wonderful article content provided in sequential sorted order, expecting more articles on windows workflow foundation.

Community Advice: ASP | SQL | XML | Regular Expressions | Windows

©Copyright 1998-2024  |  Page Processed at 2024-05-28 10:07:19 PM  AspAlliance Recent Articles RSS Feed
About ASPAlliance | Newsgroups | Advertise | Authors | Email Lists | Feedback | Link To Us | Privacy | Search