Hi Kevin,

You could consider both options (sorta) at the same time. Have you taken a look at the VFP Toolkit for .NET? Here's the lini:

http://www.gotdotnet.com/team/vfp/

This would be a way to leverage your VFP knowledge if you wish to rewrite the logic in C# (or VB .NET for that matter)....essentially, it allows you to use functions with VFP syntax in .NET.

>I have a question about managed code in a .NET environment.
>
>We have a large amount of VFP business logic code, and are trying to weigh the pros and cons of re-architecting the code to run as a COM object(s) in a .NET application - or whether to rewrite the code in C#.
>
>My preference is to keep the code in VFP - however, I'm getting resistance from some colleagues that since it would be 'outside' the CLR, the code would be unmanaged (compared to it running in C#).
>
>Any thoughts on this?
>Thanks,
>Kevin