>>>>>>>Yupp, I always recommend to check the current capabilities of the package Rick offers.
>>>>>>>Up next is a tossup of buying from other (relatively) small vendor or look in Dotnet...
>>>>>>
>>>>>> or look in Dotnet...
>>>>>>
>>>>>>They're built into .NET.
>>>>>>This is probably a newbie question but can .NET code be easily run from VFP?
>>>>>
>>>>>Define easy.
>>>>>Check this years VirtualFoxFest. Rick Strahl had a great session about it. It's available to the VFP comunity.
>>>>>https://virtualfoxfest.com/Sessions.aspx
>>>>
>>>>Easy = I can understand it
>>>>Thank you, Lutz - I'll take a look
>>
>>
>>>
>>>Hi Bill,
>>>You can compile solutions in Dotnet as COM-compatible.
>>>I am certain you can understand it and find relevant project options.
>>>(Facepalms and forehead typing irrelevant)
>>>For easier *development* I'd look into Rick's Dotnet bridge if using Dotnet dlls often.
>>>Rick prefers slower Exe COM for his Web tools, marshalling cost should be ok in most apps
>>>"Chunky, not Chatty" is mantra for layered code and just view Dotnet as added layer.
>>>
>>>my 0.22€
>>>thomas
>>
>>Thomas. Thank you. I code a lot of .NET but haven't had the need to set a project up as COM yet.
>
>Better than going to C or C++ in vfp
>and
>the need to offer hooks from unmanaged code into Dotnet.
>
>COM was the first really workable cross -
>(CORBA was a monster, old Java C bindings a pest)
>integration into Dotnet without COM not easy (write a Roslyn offspring?)
>GraalVM promises more freedom/capabilities, but I have only read blurbs, no hands on.
>
>my 0.02€
>thomas

I've only done one COM app.
The client had a serial label printer on a PC and wanted other PC's to be able to use it.
At that time you couldn't share a serial printer. That might be different now.
So I wrote a VFP COM server app to run on the PC with the printer and some client apps on other PC's to call it.
The documentation in VFP was good and I got the thing to run and the labels kept coming.