I gave Rod a summary of my interop product, ActiveVFP, and he is free to investigate the details of it, as anyone else is since it's free and Open Source. That's the extent of it and there are no apologies to be made.
As for your projects, it would have helped if you had given a little more of an appraisal of each of the conversions. Like "the main vfp prg had 10,000 lines of vfp code but we converted it to c# in 3 days - it was a piece of cake" or some level of detail to give "most" people here the confidence you're telling it like it is. But I won't nitpik anymore...
>Claude,
>
>First...
>
>Summer 2003 - converted financial application from VFP to .NET/Crystal and SQL Server
>Early 2004 - converted job costing/invoicing application from VFP to .NET/Crystal and MSDE
>Mid 2004 - Converted large document production system from VFP to .NET/Crystal and SQL Server
>Late 2004 - Early 2005 - converted financial statement application from VFP to .NET/Crystal and SQL Server
>
>I'm currently working on a second document production system from VFP to .NET, and a check-writing module from VFP to .NET.
>
>This works both ways: I'll post details of my conversion projects, and you can follow-up on Rod Paddock's request (Message #1004571) to provide an outline on Interop experiences.
>
>Hopefully it'll be more than the answer you gave him (Message #1004599).
>
>“That sounds good! My experience is very narrow - only ASP.NET to VFP mtdll and the C# is just a stub. Right now in my interop product, ActiveVFP, there are about 10 lines of c# and pretty much everything is on the vfp side. This is working very well. Where appropriate and where VFP is lacking, the "vision" is to add more functionality on the C#(or vb.net) side. The negatives I've heard are that more round trips from C# to VFP will slow down performance, but, with the good perf numbers I've seen I don't know if this is relevant or not.”
>
>Inquiring minds want to know!