Check out the new book Using Visual FoxPro.NET by Menachem Bazian listed on Amazon. IMHO, there's going to be a lot of interop between .NET and COM/COM+ over the next several years simply because .NET won't have everything right away and will be slow or non-operational in many other areas. .NET (as has been stated before) is an attempt to make web programming and web services easier and better suited to VB and VC'rs. VFP has been there and done that - it's much easier to do these types of web things in VFP...

>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)?
>
>Granted, I still need to do my research on all the .NET stuff (and probably quickly from the sounds of things), but I just would like to know if this guy is just blowing smoke so that a project goes "his way".
>
>
>Thanks,
>
>- Brian