This is very short, look for the presentation for more details.

Com interop with indigo - both parties could use each other. One way will be to export a proxy and indigo will use it and expose a service.

Avoid or abstract existing extensibility points.

no asp.net application state support
no asp.net session support
no HttpContext when not under asp.net
indigo will not support wsdl extension

asmx and EnterpriseServices require only change of using namespace to System.ServiceModel.Compat and everything will compile.

A key feature in indigo is that it doesn't need a base class, everything is using

QC, LCQ, CRM is not migrated - indigo will have new model for this technology.
The Com+ Catalog will not be supported or needed by indigo.

WSE is the new model for adopters. MS will try to release as much code as it can about this

System.Messaging will not be implemented under indigo. Everything is around attributes.

Use object technology only inside your services

In 2 weeks there will be a document about migrating.

Cross process communication will be extremely fast in

indigo.

Avoid passing object references inside com+, don't use com+ instead use System.EnterpriseServices do not use msmq instead use System.Messaging.