>
>I was talking more about a methodology and migration path as opposed to some tool that in all liklihood - could not be built....
>< jvp >

Next questions could be:

Is there some reason to actually migrate VFP code to the .Net plattform? Or it is just better to make it interact wwith other components?


And, of course, and interesting debate could start with:
¿What are the possibilities that we -as a community- foresee for VFP to become a .Net language in the future?
¿What are the minimal additions the CLR/Framework classes needs to be able to handle VFP in a decent way?
¿What losses can we tolerate in our beloved environment for the sake of being inside the framework and achieve its promised ubiquity?

May be all this deserves more than a single thread, but I think we need to start asking us this questions, and maybe let MS know about our ideas.

Don't you?