|
Sponsored Links
Resources
.NET Research Library
Get .NET related white papers, case studies and webcasts
|
News
News
News
|
Messages: 10
Messages: 10
Messages: 10
Printer friendly
Printer friendly
Printer friendly
Post reply
Post reply
Post reply
XML
XML
XML
|
 |
Microsoft to Release Longhorn Beta 1 in June
Microsoft Director John Montgomery has said that there will be a public beta of Longhorn available in June of 2005 with the final release scheduled for the second half of next year. Having removed the three major features of Longhorn; WinFS, Avalon, and Indigo the new operating system will contain reliability and management features.
Editor's Note: Shortly after nixing plans to release ObjectSpaces in the Whidbey timeframe by grouping that team with the WinFS team, Microsoft announced that WinFS will not ship with Longhorn. They have since announced that in order to meet the dates mentioned above they will remove Avalon and Indigo, veritably gutting the product of the features that created such a buzz at PDC 2003. They're not being very forthcoming with what features are left in Longhorn, which many are beginning to dub "ShortHorn".
Would it be better for Microsoft to go back on the commitment to release Longhorn next year and include the features they've currently cut out or is the date the most important feature? What do you think?
***UPDATE***Editor: I'm reposting this with a link to comments from Robert Scoble that I think clear up the whys and hows of Longhorn. Perhaps most important is his statement that we didn't see everything at PDC and that they still have a few tricks up their sleeves for Longhorn. Read his comments here.
|
|
|
Message #156125
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Unfounded affirmations
As long as I know (and I also searched the web to make sure), Avalon and Indigo are STILL part of Longhorn, the buzz about them is that they are going to be released with backwards compatibility with Win XP and Win 2k3.
Can either of you (the author or the editor) point me to the official press releases saying that Avalon and Indigo are being cut off from Longhorn?
|
|
|
Message #156137
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Didn't know that
I didn't know Avalon AND Indigo have been cut from longhorn... That's shocking news...
I prefer to wait and see those features developed than have an strict ship date with a huge Disapointment OS with (apparently) nothing new.
|
|
|
Message #156145
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Avalon and Indigo in Longhorn
Avalon and Indigo are being "back-ported" to Windows XP which is a fancy way of saying that they are being made into separate products that will be installable on both Windows XP and Longhorn. Therefore, while the features will still be available on Longhorn, they are not part of that actual product. So, discounting those and with the removal of WinFS, there isn't much left.
What I find interesting is the concept that releasing a product, without the premiere features that everybody is so excited about, but on time is somehow better than waiting for the features to be ready. For example, in the gaming world there was buzz for years about the next version of Duke Nuke 'Em and Half-Life 2. The word from their creators was always "When it's ready". Which paradigm is better overall?
|
|
|
Message #156150
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
in order words
I can think of a couple of ways of interpreting the news.
1. the next release of windows won't coincide with the completion of indigo and avalon. therefore MS has to separate the two. Which isn't a bad thing really, if I can use indigo and avalon with XP without having to upgrade I'm all for it. It's more flexible and less risky.
2. MS feels some odd need to have new OS version at regular intervals and decides it's not worth rushing indigo and avalon to get it out in time for the next OS.
3. MS doesn't feel there's enough reason for users to upgrade, therefore separating indigo, objectspaces and avalon from the next OS release lets them stand on their own. which is positive for me.
I don't see much value in a new OS release, since corporate networks should have better security by now. If the release is mainly about improving security, I'm not sure that is enough motivation to upgrade. I'm totally bias here, but I'd rather MS focus on middleware and not so much on adding new doodads for the OS.
|
|
|
Message #156159
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Avalon and Indigo for XP! Come on
Avalon and Indigo is what we are waiting for. Couldn't care less about the rest.
|
|
|
Message #156257
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Avalon and Indigo for XP! Come on
Avalon and Indigo is what we are waiting for. Couldn't care less about the rest.
Possibly for the first time ever I am in total agreement with you. The planets must have aligned.
|
|
|
Message #156278
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Is Longhorn rush due to Software Assurance licensing?
2. MS feels some odd need to have new OS version at regular intervals and decides it's not worth rushing indigo and avalon to get it out in time for the next OS.
I believe the rush to get Longhorn out is due to the whole Software Assurance license scheme. Microsoft has to put out regular updates to justify the cost of these licenses.
Since the break-even point for SA is 3.5 years, if Microsoft doesn't release a new version in that time frame, then Software Assurance ends up costing more than just buying the full license outright.
See this blog post for more details.
http://www.microsoftmonitor.com/archives/002236.html
Kiliman
|
|
|
Message #156475
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Option Pack
Avalon and Indigo are being "back-ported" to Windows XP which is a fancy way of saying that they are being made into separate products that will be installable on both Windows XP and Longhorn. Therefore, while the features will still be available on Longhorn, they are not part of that actual product.
I just knew they'd get back to the "NT Option Pack 4" model sooner or later....
|
|
|
Message #158120
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Avalon and Indigo
There are a few issues with Avalon.
First of all, in order for Avalon to be a desirable feature, there have to be applications that use it. If it is supported only on a new version of windows that most large commercial entities (Microsoft's primary market) generally upgrade well after release, then there will be few applications targetting it. If it's a redistributable, then it becomes far more likely to be supported if it is a useful features, because Application developers can support the older version of Windows as well.
The second thing here is to look at it from a security standpoint. Microsoft has been being slammed for installing dozens of services that aren't really necessary but that contain security holes. Microsoft has been slammed for its default security settings. By making Avalon a separate entity from the operating system, it becomes possible to allow users to decide if they need Avalon or not. A file server, for example, doesn't benefit alot from Avalon.
If they would make similar moves with DirectX (which is rarely needed for business applications), Index server, and other things that aren't really part of the core operating system, then they could probably prevent a lot of security problems.
|
|
|
| |
|
| New content on TheServerSide.NETNew content on TheServerSide.NETNew content on TheServerSide.NET |
|
|
Language "mashups" will become more prominent, and developers will become polyglots, one programmer suggests.
SearchWinDevelopment.com offers an introduction to the language, performance, testing and data management improvements in VS 2008.
VBCode.com code snippets cover all aspects of application development, from data binding to security to the user interface.
Get up to date on XAML best practices with a variety of articles, tutorials and webcasts. [SearchWinDevelopment.com]
One team's experience with the VSTS DB edition suggests that it can improve workflow for dev teams. It also enhanced Agile efforts.
(June 24, Article)
Microsoft has begun to include DSL tools in the VSTS kit. A new book by Steve Cook and other VSTS team members helps set the stage.
(June 24, Article)
Cartoon: Be it ever so humble there is no place like your home after you get a Microsoft Home Server .
(June 18, Cartoon)
Microsoft's Thom Robbins says new technology to highlight in NET 3.5 includes AJAX, LINQ for both C# and VB, as well as tooling enhancements intended to ease the task of building WPF, WF and WCF apps.
(June 29, Podcast)
Venkat Subramaniam discusses AJAX bottlenecks, the tenets of Agile development and more. He spoke at the Ajax Experience.
(June 25, Tech Talk)
In the second of a two-part series, Michele Leroux Bustamente discusses design decisions related to the claims-based security model. Read the story and walk through the process for creating a set of claims-based utilities to encapsulate claims authorization at the service tier.
(May 24, Article)
Understanding why the Entity Framework exists and learning where it can fit into your projects can get you prepared for the eventual release early next year.
(May 10, Article)
Resource: This learning guide gives you quick access to useful links on Windows Communication Foundation security information.
(April 24, Article)
TSS.NET's Jack Vaughan spoke recently spoke with Microsoft's Brad Abrams to find out what he is seeing in the field and what the chefs in Redmond are cooking. Along the way he discusses patterns of AJAX frameworks.
(April 11, Article)
In a two-part series, Michele Leroux Bustamente explains how claims-based security is supported by WCF, and how you can implement a claims-based security model for your services.
(March 29, Article)
Windows Workflow Foundation is a new technology that many developers will need to get their heads around. In a brief excerpt adapted from Programming Windows Workflow Foundation: Practical WF Techniques and Examples using XAML and C#, K.Scott Allen considers aspects of workflow definition.
(March 22, Chapter Excerpt)
|
|
