The Essence of Microsoft's .NET Framework: ASP Alliance

Print Add To Favorites Email To Friend Rate This Article
The Essence of Microsoft's .NET Framework

page 8 of 12

by Saripalli Koti Reddy
Feedback

Average Rating:

Views (Total / Last 10 Days): 20121/ 208

Article Contents:

Supported Operating Systems for .NET Framework 3.0 [WinFx]

1. Longhorn (Windows code name)

2. Windows Server 2003 Service Pack1

3. Windows Vista

4. Windows XP - Service Pack2

Download .NET Framework 3.0 [WinFx]

You can download and start working with WinFx by clicking here.

Visual Studio - 2005 Extensions for WPF, WCF & WF

In order to make use of Visual Studio - 2005 for developing the WPF, WCF and WF applications we need to install a few extensions to the Visual Studio - 2005 explicitly.

You can download those extensions from the links mentioned below:

1) Microsoft Visual Studio 2005 CTP Extensions for .NET Framework 3.0 (WCF & WPF)

2) Microsoft Visual Studio 2005 Extensions for Windows WorkFlow Foundation

« (Page 7)

View Entire Article

(Page 9) »

Article Feedback

Comment:
Title:
Name:
Url:	( Optional )

Please add 6 and 3 and type the answer here:

User Comments

Title: The Essence of Microsoft's .NET Framework
Name: Jagannath
Date: 1/6/2009 4:43:34 AM
Comment:
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: 8/6/2008 3:46:30 AM
Comment:
"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 (non-.net) have ways (better?) to handle their state, not to mention memory and resources.

Title: The Essence of Microsoft's .NET Framework
Name: Venkat
Date: 5/23/2008 8:50:29 AM
Comment:
Its really very good article and excellent prasentation

Title: .NET Framework 3.0 [WinFx] - Here It Goes…
Name: Dileep
Date: 12/12/2007 6:31:00 AM
Comment:
good information and presentation..
u r always great in ur presentations..

dileep (your student in .net ur fan always)

Title: ---
Name: ---------
Date: 2/16/2007 2:11:20 PM
Comment:
wonderful article content provided in sequential sorted order, expecting more articles on windows workflow foundation.