Highlights and Juicy Tidbits:
First Indigo bits will be delivered in a March 2005 CTP. Avalon and Indigo will be released together.
Steve Swartz (has blank blog) said that they settled on using Client/Service terminology rather than Service/Service, or Client/Server
Indigo does a great job of interoperation with WSDL, MSMQ, and COM+, allowing you to migrate one tier at a time. I especially like the easy change for clients. You only need to replace CreateInstance with GetObject and a Moniker that describes the Indigo service. Very nice.
WS-Discovery will not be supported by Indigo. Apparently that will be device support in Longhorn.
There will be Five SKUs for VS Team System. Team Server, Team Architect, Team Developer, Team Test, Team Suite. The Universal License will cover ONE of the user licenses and you can buy Suite “for a small fee”
Versant has jumped into the .NET Object Relational Mapping business with Versant Open Access.NET. Being pretty much cleaned out by the ObjectSpaces vaporware, the market should be ripe for them.
Sybase has release DataWindow.NET, Windows Forms and WebForms control that acts exactly like the PowerBuilder 10 Data Window so PowerBuilder developers will feel at home. PowerBuilder 11 applications can be compiled as .NET applications, even Web Applications. Finally PowerBuilder 12 will be a .NET language, like Delphi.NET is now. I see the future of PowerBuilder and it is .NET!
I especially liked Rich Turner's presentation on how to do SO on .NET today. Good job. I hope to have him present it when we have our EBC in Redmond in May.
Indigo Day was a long one for me. They only have the Exhibition floor open over lunch time. I had to skip lunch yesterday.