This post originated from an RSS feed registered with .NET Buzz
by Sam Gentile.
Original Post: Longhorn Changes
Feed Title: Sam Gentile's Blog
Feed URL: http://samgentile.com/blog/Rss.aspx
Feed Description: .NET and Software Development from an experienced perspective - .NET/CLR, Rotor, Interop, MC+/C++, COM+, ES, Mac OS X, Extreme Programming and More!
I was briefed today by Robert Scoble today on the changes for Longhorn in advance of the official announcement. These changes were necessary for Microsoft to ship Longhorn Client in 2006 broadly. The extremely good news is that Microsoft is making elements of the WinFX programming model early for Windows XP and Win2K3 Server, namely Avalon and Indigo. I'm not so enamored of Avalon although I can see possible client desktop innovations useful to people like us, but I am really enamored of one managed interface to all distributed .NET communication (i.e. Indigo) on these platforms. Indigo is a very important technology.IThe bad news is that WinFS will not make it into Longhorn. I view WinFS as the strategic and most important technology pillar of the former Longhorn triad. Synchronization is a vital technology. Thank goodness, we have a solution for that today.
Previous Topic
