Here is an interesting news from this article at MSDN.
Earlier this summer we emerged from shipping Windows XP Service Pack 2 and reviewed our "Longhorn" plans and all the feedback we've gotten since PDC. There was a lot of feedback to go through. The core feedback that came up time and again was "get the 'Longhorn' advances into the hands of customers sooner rather than later" and "make WinFX available on previous versions of Windows."
There are three core things that stand out for me in our plans:
- We are focusing on delivering "Longhorn" in 2006 and making appropriate tradeoffs, including reducing interdependencies in the OS to make this schedule.
- We plan to make the "Avalon" and "Indigo" pillars of WinFX available for Windows XP and Windows Server 2003.
- In order to deliver the "Longhorn" innovations to customers as quickly as possible, we now intend to deliver WinFS after the initial availability of the "Longhorn" client. We continue to be committed to WinFS. It is expected to beta when the "Longhorn" client is broadly available.
These are good changes that will enable Microsoft to deliver a compelling "Longhorn" release in 2006 and to increase our investments in managed code, the .NET Framework, and WinFX. In particular, because we now plan to deliver "Avalon" and "Indigo" to Windows XP and Windows Server 2003, we will greatly increase the reach of these two technologies and will make them even more compelling as developer technologies.
So what does this all mean to you? For those of you who were experimenting with WinFS on "Longhorn," it means that you'll be able to build on WinFS Beta 1 when "Longhorn" ships. For those of you who've been using other parts of WinFX such as "Avalon" and "Indigo," it means you'll be able to run them on Windows XP and Windows Server 2003. For everyone, it means "keep writing managed code on the .NET Framework today."
There are three core things that stand out for me in our plans:
- We are focusing on delivering "Longhorn" in 2006 and making appropriate tradeoffs, including reducing interdependencies in the OS to make this schedule.
- We plan to make the "Avalon" and "Indigo" pillars of WinFX available for Windows XP and Windows Server 2003.
- In order to deliver the "Longhorn" innovations to customers as quickly as possible, we now intend to deliver WinFS after the initial availability of the "Longhorn" client. We continue to be committed to WinFS. It is expected to beta when the "Longhorn" client is broadly available.
These are good changes that will enable Microsoft to deliver a compelling "Longhorn" release in 2006 and to increase our investments in managed code, the .NET Framework, and WinFX. In particular, because we now plan to deliver "Avalon" and "Indigo" to Windows XP and Windows Server 2003, we will greatly increase the reach of these two technologies and will make them even more compelling as developer technologies.
So what does this all mean to you? For those of you who were experimenting with WinFS on "Longhorn," it means that you'll be able to build on WinFS Beta 1 when "Longhorn" ships. For those of you who've been using other parts of WinFX such as "Avalon" and "Indigo," it means you'll be able to run them on Windows XP and Windows Server 2003. For everyone, it means "keep writing managed code on the .NET Framework today."
Comment