>>>Nope. COM will still be there.
>>
>>Not the way it's used today...
>>
>>Native .Net objects (IL code) are not COM objects and access to 'classic' COM objects is through an interoperability layer.
>>
>>This is Microsoft's way of phasing out 'legacy' COM apps <s>... Funny how quickly technology goes obsolete these days, huh?
>>
>>Obsolete is of course exaggerated, but COM components will definitely be less important in the .Net future.
>
>So i think my real question is:
>
>If I use COM Codebook, am I building obsolete applications?

In a literal sense. Maybe. In a real sense - probably not. I can't speak for Flash but I'm pretty sure they'll have something that'll map into .Net.

But as far as it goes any application you build today on the COM platform will not be directly move to the .Net platform. I want to refrain from calling it obsolete, because that's not true - anything you build today will continue to work, but it won't be part of the .Net platform without the interop layer.