ASMX to Indigo
Good news is that your old ASMX code will continue to work. Same with MSMQ. No imperative that you must move to Indigo. Save code, run faster, smoother, better management tools – great reasons to change, however.
“First generation Web services are legacy“ – sounds weird, doesn’t it?
Enterprise Services to Indigo
Enhanced the transaction support, setting Tx and security semantics on a per method basis.
WSE to Indigo
Interoperate with WSE? Yes. Even better, because 4 lines of code became 1 attribute, for example.
System.Messaging to Indigo
Change to namespace System.ServiceModel, but then Indigo does the messaging for you. Your business logic will be the same, but the reading/writing code with be done in Indigo
Remoting to Indigo
They were used only when you know you are going to control both ends of the conversation. You can force server upgrades, or client upgrades, for example. Eric doesn’t expect most people to move from Remoting to Indigo, because it was for a different pupose, perhaps. Any custom adapters or formatters, would have to upgraded manually. Support for the serializable attribute, but that’s about it. So, there will be prescriptive guidance support, but that’s about it.
BizTalk Server 2004
Can connect multiple services built with Indigo. The need for BizTalk won’t go away. It will be the orchestrator for everything. The protocols will updated thought. There is a WSE adapter now. When Indigo ships, there will be an Indigo adapter (BizTalk Server 2006). BizTalk Server vNext will be built natively on Indigo stack.
SQL Server 2005 (Service Broker)
Queues for the database, for hanging queries and resultsets. The service broker is a slightly different protocol. This implementation will be based on Indigo in 2006 (service pack?). SQL Server version vNext will use Indigo transports for WS-* interoperability.
Windows Server System
Web service protocols everywhere. Classic protocols as well. Increasilngly the identity, etc. will be done with Web services. The roadmap will move to have a consistent Web service API down the road. Model and build in Visual Studio and monitor with Indigo tools. Great foundation to reduce complexity and reduce the number of paradigms.
Doubled the number of partners since last year. 225 premier and alliance partners with nearly 20,000 affiliates.
Critical Dates and Getting Started
- Avalon CTP was in November
- Indigo CTP and Avalon CTP 2 in March (brings them together and will include a version of VS2005)
- Broadly available on MSDN
- Will take some of the biggest samples (PAG) and publish on Indigo