Pages






Sunday, February 13, 2011

Version Correspondence - Visual Studio vs. EntLib vs. Platform SDK

    Versions of .NET Framework and Visual Studio are paired. Visual Studio versions can co-exist on the same machine.

    .NET Framework version Visual Studio version Launch OS Support Features EntLib Platform
    SDK
    XML
    v1.0.3705 2002 - - - - - -
    v1.1.4322 2003 - XP (IE 6.00), 2000 (IE 5.01) Not shipped with Vista. 1.1 June 2005 - -
    v2.0.50727 2005 Nov. 2005 - - 2.0 Jan. 2006
    3.1 May 2007
    5.0 -
    v3.0 2008 May 2008 Shipped with Vista, download for XP SP1 (IE 7),
    Server 2003
    WCF, WF, WPF, LINQ to SQL, Silverlight 4.0 May 2008 6.0 (WinFX) -
    v3.5 (30729) SP1 2008 SP1 x64 & IA64 Oct 2008 download for XP SP2,
    Vista,
    Server 2003 SP1
    SQL Server 2008 support. Dependency injection (DI IoC pattern)/interception/cross-cutting mechanism in the Unity Application Block. 4.1 Oct 2008 6.1 -
    v3.5 update - - - KB958481 - - -
    v4.0 2010 Beta1 2009 Windows 7 Parallel processing 5.0? - -

    LINQ (Language-Integrated Query) language extensions in C# and VB (introduced in 2008) enable access to in-memory and XML structures as well as databases using syntax like SQL, but as program commands, not as embedded SQL strings. This LINQ is good because crashing at run-time, errors in database names and datatypes are referenced as strongly typed objects which appear as intellisense and can be caught at compile-time.

    WF (Windows Workflow Foundation) for asynchronous/manual processing of sequential or state-machine flows,

    WPF (Windows Presentation Foundation), defined by .baml (Binary XAML) files and displayed by Silverlight/Mac Moonlight player competing with Adobe Flashanother page on this site


Go to Top of this page.
Previous topic this page
Next topic this page

Set screen The Cathedral and the Bazaar

Eric S. Raymond used this phrase to explain the difference between Microsoft's preferenced for a closed Cathedral approach versus open-source approaches by Java vendors.

For large organizations, Microsoft's cathedral provides more stability and control because of the closed, incremental approach. More importantly, Microsoft's approach yields a larger base of capable developers and users. A focused set of users raises the economic threshold for when investors are willing to invest in subsidiary products and services such as training products.

Because of its diversity, developer attention is fragmented in the open source world, which makes it difficult to find and keep good people. In order to keep up with the fast pace of technological change, developers need to jump to the next hottest thing (even before making the current technology truely usable).

This may change as the popularity of Google Apps grows and concentrates developer attention.

Microsoft's ".NET" (dot net) strategy and ".NET Framework" technical architecture is Microsoft's answer to Java and CORBA.

A Sharp Java Killer?

Microsoft had first said J++ is no longer one of the languages in the Visual Studio.NET suite of many languages. Early on, Microsot provided a Java User Migration Path (JUMP) to the C# language (pronounced "see sharp"). However, Java is now a supported language as J#.

Microsoft counters Java's “Write once, Run anywhere” premise with “Write many languages, Run on one Micosoft platform”.

Set screen CLR (Common Language Runtime)

Microsoft rewrote the Java runtime into Microsoft's own Intermediate Language (MSIL) called OptIL, associated compilers: one for each of the "20" existing programming source languages, and a run-time compiler to create machine code executable native to each hardware platform.

Much like the Java RunTime engine, a Common Language Runtime (CLR) execution engine (EE) "assembles" and "manages" OptIL code and provides services such as memory management, cross language integration, exception handling, code access security, and automatic lifetime control of objects.

Microsoft OptIL vs. Java IDL Compiler

Microsoft 's replacement for IDL (Interface Definition Language) is to have self-describing objects. The new OptIL compilers supply metadata for the .NET Framework to locate and unwind stack frames, and include information required for debugging and garbage collection, as well as security attributes, marshaling data, extended class and member definitions, version binding, and other information required by the runtime.

.NET applications, components, and controls are built using Microsoft's .NET Framework class library. Existing "unmanaged" COM applications will use a COM callable wrapper (CCW) to access system functionality managed by CLS-compliant library of classes, interfaces, and value types.

.NET applications code written using this contract of cooperation is called "managed" code.


SOURCE:http://www.wilsonmar.com/msdotnet.htm

0 comments: