>Actually it wasn't having VFP call another component, but have the C# component (that calls the VFP COM) do more of the work. From what I have observed, a C# class in ASP.NET that does a lot of work, doesn't try to hog the CPU like VFP does.

No it doesn't because the CLR handles the timeslicing of the threads. In addition C# code is likely to be much more granular than VFP code (ie. more code) which gives you more chance to give up timeslices with Thread.Sleep() for example, if you're sitting in a tight loop.