>There is probably no one single answer for this, but...
>
>We're moving a VFP app (very thick layer of business logic currently tied to the UI) to .NET.
>
>Are there any clear advantages to taking blocks of VFP functions and moving them to VB.NET or C#, as opposed to keeping the VFP layer as a COM object?
>
>A related question is this: if an app has a particularly intensive business layer, does it make sense to identify which pieces might make more sense to reside on the client side? (Particularly user-validations that can fire so frequently that it might put a heavy burden on the server?)

I will be able to address this with you in more detail after this Friday evening when I talk about something new that helps do this, and it does not even require VFP to be running (not a COM wrapper). Not only will I discuss this in detail and demo it in the keynote, but it will be available for download then also, so stay tuned. Be sure to check out http://www.levelextreme.com/Conferences/EssentialFox/2002/ for up to date information about the conference. I will post a message here on the UT during the keynote so that I actually show the UT to people and share the same news items with folks on the UT while I'm talking to the audience at the conference. That allows those people who can't be at the conference do not miss out on the news and information announced. Sound cool? :)