|
Sponsored Links
Resources
.NET Research Library
Get .NET related white papers, case studies and webcasts
|
News
News
News
|
Messages: 8
Messages: 8
Messages: 8
Printer friendly
Printer friendly
Printer friendly
Post reply
Post reply
Post reply
XML
XML
XML
|
 |
Microsoft announces Longhorn will ship with cuts by 2006
Microsoft has announced that their next-generation operating system, code-named "Longhorn", will ship sometime in 2006, but without several of the features that were originally intended for it, such as WinFS (the next-generation filesystem).
In an announcement on Friday, Bill Gates said, "Getting Longhorn to customers in 2006 will provide important advances in performance, security and reliability, and will help accelerate the creation of exciting new applications by developers across the industry." Gates is well known to be taking direct interest in the Longhorn project, in his role as chief software architect for the company.
Meanwhile, the new presentation system (code-named Avalon) and the replacement for .NET Remoting, Enterprise Services, et al (code-named Indigo) are still slated to be part of the 2006 release. In fact, in the announcement, Microsoft has stated an intent to release Avalon and Indigo (together known as WinFX) for Windows Server 2003 and Windows XP, though no date was specified when that might occur.
Reaction was mixed over the weekend, with some predicting that this was just "business as usual" for any new product under development, others saying that this was actually a better move for the software giant than trying to wait the three years or so for the product--with all of its originally-slated features--to be ready. Still others, particularly those in the Linux camp, proclaimed all of Longhorn to be merely FUD and that this is just "business as usual" for Microsoft.
For more details on the announcement and reactions to it, read:
|
|
|
Message #136285
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Microsoft announces Longhorn will ship with cuts by 2006
I am trying to make a technology decision for a company to develop an internet portal and they would like to go with a Microsoft solution. Unfortunately, news releases like this make it a harder sell. SharePoint Portal seems to have been left for dead while everyone waits for Whidbey portal features. Indigo is the way to go but there is no clear roadmap for a distributed system. The Don Box TSS.Net interview seems to raise more FUD. Everything is in beta with lots a promises. I'd like to get some ammo. Any suggestions?
|
|
|
Message #136286
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Shift to J2EE
Andrew,
I will suggest, try selling J2EE to your client, at least the technology is mature and has been around for quite some years now. Moreover, you have several vendor options in J2EE world. MS as usual is confusing the customers and trying to sell what does not exist.
Vimal
|
|
|
Message #136338
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Microsoft announces Longhorn will ship with cuts by 2006
...SharePoint Portal seems to have been left for dead while everyone waits for Whidbey portal features... Dead? Tell me more - we're planning to make a big jump on the SPS bandwagon, should I be worried?
|
|
|
Message #136348
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
SharePoint is not dead...
I think you may have been misinformed about what "portal" features are being included in Whidbey. ASP.NET 2.0 will be including much of the interface functionality that was introduced in SharePoint's last release in the form of WebParts. WebParts will become a first-class citizen in ASP.NET projects and will not require a special reference to the SPS libraries.
But SharePoint Portal Server is still very much the central part of Microsoft's portal play. It includes a lot of functionality beyond the WebParts model and includes a powerful subscription, search and organizational feature-set that will serve your portal needs well. The only thing to be careful about with SharePoint is the licensing for making it an internet portal... the costs tend to go way up once you go from an intranet based portal to extranet and internet portals.
|
|
|
Message #136370
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
J2EE for web portal !!!
Vimal,
I would like to know what in J2EE is more mature than any web portal related infrastructure in .Net arena. I am tired of the argument of Java being more matured technology compared to .Net, please suggest me what the existing shortcomming of .net which are not being improved in ASP.Net 2.0 and immature parts of ASP.Net 2.0 if possible, compared to J2EE.
Speaking of Vendor locks, who can lock you down better than IBM ? Certainly not MSFT.
p.s: I have to refer to sun site to really confirm whether I have to call J2EE or J5EE.
thanx,
Sri.
|
|
|
Message #136375
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Microsoft announces Longhorn will ship with cuts by 2006
SharePoint Portal seems to have been left for dead while everyone waits for Whidbey portal features. Thats just MS marketing, they have a lot of markets and audiences to cover, just because you here more about any particular technology does not mean the others are dead.Indigo is the way to go but there is no clear roadmap for a distributed system. The Don Box TSS.Net interview seems to raise more FUD. Everything is in beta with lots a promises. I'd like to get some ammo. Any suggestions? Dox Box also has said that ASMX is the closes thing we have to the "truth", there is also guidance available as to which technology to use (DCOM, Remoting, ASMX) for whatever scenario you need a solution for.
|
|
|
Message #136676
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
What about ObjectSpaces?
So, WinFS is getting cut. What does that mean for ObjectSpaces?
Are we to ever get a Microsoft blessed ORM solution? :)
Or should we just jump on Hibernate.NET?
No wonder Luca had to move, and is now C# PM :)
|
|
|
Message #137406
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Changes in .NET
I had the same concerns. .NET changes dramatically and I am not we afford updating our codes and designs everyday to match those dramaticall changes. As an example changes in Win and Web forms will turn everything over. All controls and applications will be effected. Web services will also change so nothing will remain unchanged.
We will also need to pay a lot of money for training of our programmers while we have done this last year. All the programmers have had a .NET core training (Win, Web, XML) and I feel sorry for it. (as all of those trainings will go away and we will need to repeat them for every big change in .NET).
I wanted to know what is the strategy of your companies fo .NET (regarding changes happening to technologies)? Is it possible to match with those changes. Is it possible for enterprise and software companies to upgrade their code and designs everytime?
I do not want to start J2EE vs .NET rant again but recently we were looking for buying a banking application and 90% of proposals were using Oracle and J2EE. (out of 17 proposals with minimum price of $4m ). Now I see why companies develop their applications with a less changing tool. Because it is not possible to update a $Xm or $XXm application easily.
Regards,
Mac (programmernet.org)
|
|
|
| |
|
| 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)
|
|
