次の方法で共有

WinFX is now .Net 3.0? a new Framework? huh?

  • [アーティクル]

WinFX is now .Net 3.0? a new Framework? huh?

 

Man! go on vacation for a couple of days and the whole world changes. Ever notice things are moving along just fine and then one day you take a couple of days off (literally), and you come back open your email and read and tatttaaaaaa! The worlds has changed.

First there was .Net Framework 1.0, then 1.1, so we call them 1.X now J

Then we had .Net Framework 2.0 COOL! (yah well I thought okay with Visual Studio 2005, we need a new framework).

 

Okay, then came WinFX pretty cool stuff, why else would I call myself XAMLChick?

So I was doing fine knowing I need .Net Framework 2.0 and WinFX to get WPF, WCF, WF and InfoCard to work. WELLLLL….. Now we have Framework 3.0. Forget about having to get .Net framework 2.0 and WinFX now you can have it in a bundle. Framework 3.0 includes both. So far we had been following the Visual Studio releases (or that is what I thought) with our .Net Framework numbering, but now we are following OS (operating system) releases? It would make sense. I thought since we had .Net Framework 1.1 with Visual Studio 2003 that we would have .Net Framework 2.5 with WinFX, oh well I like 3, plus it keeps things consistent. Okay enough about my thoughts on the matter, here is the scoop!

 

On Friday June 9th via Soma’s blog an announcement was made, that Microsoft publicly disclosed that WinFX is now officially re-brand the .NET Framework 3.0. The primary goal in Microsoft’s communications plan is articulate the rationale for the change and reduce any confusion within the developer community.

WinFX is now .Net 3.0? a new Framework? huh?

 

Man! go on vacation for a couple of days and the whole world changes. Ever notice things are moving along just fine and then one day you take a couple of days off (literally), and you come back open your email and read and tatttaaaaaa! The worlds has changed.

First there was .Net Framework 1.0, then 1.1, so we call them 1.X now J

Then we had .Net Framework 2.0 COOL! (yah well I thought okay with Visual Studio 2005, we need a new framework).

 

Okay, then came WinFX pretty cool stuff, why else would I call myself XAMLChick?

So I was doing fine knowing I need .Net Framework 2.0 and WinFX to get WPF, WCF, WF and InfoCard to work. WELLLLL….. Now we have Framework 3.0. Forget about having to get .Net framework 2.0 and WinFX now you can have it in a bundle. Framework 3.0 includes both. So far we had been following the Visual Studio releases (or that is what I thought) with our .Net Framework numbering, but now we are following OS (operating system) releases? It would make sense. I thought since we had .Net Framework 1.1 with Visual Studio 2003 that we would have .Net Framework 2.5 with WinFX, oh well I like 3, plus it keeps things consistent. Okay enough about my thoughts on the matter, here is the scoop!

 

On Friday June 9th via Soma’s blog an announcement was made, that Microsoft publicly disclosed that WinFX is now officially re-brand the .NET Framework 3.0. The primary goal in Microsoft’s communications plan is articulate the rationale for the change and reduce any confusion within the developer community.

This is purely a marketing decision on Microsoft’s part. There is absolutely no technical elements which were altered in what was referred to as WinFX and what is now the .NET Framework 3.0 as a result of this branding change. In addition, Microsoft is using this opportunity to announce the official name the technology formerly codenamed “InfoCard” as Windows CardSpace (WCS).  All WinFX components will ship as part of the .NET Framework 3.0 including Windows Presentation Foundation (WPF), Windows Communication Foundation (WCF), Windows Workflow Foundation (WF), and Windows CardSpace. There are no changes to Windows Vista as a result of this branding change and the .NET Framework 3.0.

Several spokespeople will be onsite at TechEd 2006 in Boston (keynote starting tomorrow June 11th).

All WinFX components will now be included within the .NET Framework 3.0.  There is no change to the ship schedule of Windows Vista or the .NET Framework 3.0 and the .NET Framework 3.0 will still ship in certain versions of Windows Vista.  Prashant Sridharan will be the spokesperson for the re-branding announcement.

You can find articles about this on eWeek and The Channel Insider

 

 

This is purely a marketing decision on Microsoft’s part. There is absolutely no technical elements which were altered in what was referred to as WinFX and what is now the .NET Framework 3.0 as a result of this branding change. In addition, Microsoft is using this opportunity to announce the official name the technology formerly codenamed “InfoCard” as Windows CardSpace (WCS).  All WinFX components will ship as part of the .NET Framework 3.0 including Windows Presentation Foundation (WPF), Windows Communication Foundation (WCF), Windows Workflow Foundation (WF), and Windows CardSpace. There are no changes to Windows Vista as a result of this branding change and the .NET Framework 3.0.

Several spokespeople will be onsite at TechEd 2006 in Boston (keynote starting tomorrow June 11th).

All WinFX components will now be included within the .NET Framework 3.0.  There is no change to the ship schedule of Windows Vista or the .NET Framework 3.0 and the .NET Framework 3.0 will still ship in certain versions of Windows Vista.  Prashant Sridharan will be the spokesperson for the re-branding announcement.

You can find articles about this on eWeek and The Channel Insider

 

 

WinFXtoNet3.bmp

Comments