>>Hi all,
>>
>>I have a question which is prompted from something that another non-VFP developer said during a meeting today. Note that he is pushing to have everything re-engineered with .NET...
>>
>>He made a statement saying that "COM and COM+ will be obsolete technologies within 1-2 years".
>>
>>Since Microsoft is pushing all (ok, not all, but much) of it's focus to .NET, and (according to the other developer) .NET does something different than COM/COM+, what is the replacement for COM+?
>>
>>Is his statement even true? If so, what is one to do to prepare for the "demise" of COM? If we are not to use COM, what do we use? Do those of us who use VFP have to wait for ".NET support" (whatever the hell that means)?
>
>More...
>
>From the DOTNET discussion board, Don Box says (and he should know *g*), "I assume that COM (as I understand it IUnknown+API) will still be heavily
>used in layers of the Windows Platform beneath .Net, if not inside the VM
>itself. So I shouldn't throw away my copy of Essential COM just yet. (The
>very thought of it! ;-) )"


OOhh.. good quote.. Thanks Nancy

*Hastily adding this to my PPT for DevCon*