Pertti,

I doubt that including VFP syntax/language into NET application code is a good idea. Until MS does not provide VFP integrating into NET package, VFP syntax/additions in the code will remain artificial and not readable for majority of NET programmers.

In any case, you may not need to do anything: in NET you may use ADO with VFP OLEDB provider. It allows you to call a lot of VFP functions, create VFP cursors, it supports many of the VFP native tools for data manipulations, arrays, etc. Even more, it allows you to Execute the entire foxpro.prg as is. Here is one of my exercises written in VB.NET:

........
cnnVFP = CreateObject("ADODB.Connection")
cnnVFP.Open("Provider=VFPOLEDB.1;Data Source=" + VFPDirectory + ";Collating Sequence=MACHINE")

*'format foxpro prg text, prepare the proper vfp EXECSCRIPT call, and call it via ADO Execute.

ofso = CreateObject("Scripting.FileSystemObject")
With ofso.OpenTextFile("vfpcode.prg")
           lctmpstr = .readall
           .close()
End With
ctmpstr = "EXECSCRIPT('" + lctmpstr + "', '" + VFPDirectory + "', '" + _
                    lctmp1 + "', '" + lctmp2 + "')"
lctmpstr = lctmpstr.Replace(Chr(13) + Chr(10), "' +CHR(13)+CHR(10)+'")

cnnVFP.Execute(lctmpstr)
.......

Just my 2 cents.