You have VFP logic that should run as a command, from a script or from an agent.
Your VFP code, turned into a Windows command.
You write the commands as methods of a VFP class and FoxForge builds them into an .exe with its help, typed options, exit codes and JSON output for scripts and agents. It ships by copying a folder: no Visual FoxPro to install, nothing to register and no administrator rights.
- Scripts
- AI agents
- Machines without Visual FoxPro installed
- VFP developers, from the IDE
No credit card. Verify your email and you get 30 days of a full license (not a cut-down build) for FoxServer, FoxCore, FoxBridge, FoxAgent, FoxCli and FoxCli MCP, installer included, in your portal. One per person and product; after 30 days it expires.
Features
One method, one command
Every public method of the class is a command. Its parameters are the options, and the type comes from the AS. A comment block on top gives it a description, aliases and default values.
The help writes itself
Each command's help, the validation of the line and the usage errors come from the method signature, so they never drift apart. They are answered without starting VFP.
For scripts and for agents
Output as JSON, table or text, depending on the console. The describe command dumps the whole schema as JSON Schema: an AI agent discovers your CLI without reading anything else.
Ships by copying
The .exe activates your VFP DLL through a manifest, without registration. Nine files in a folder, with the VFP runtime inside: no installer and no administrator.
From the VFP IDE
FoxForge creates the project, builds with Ctrl+F7 and brings a test bench to run a command from the source, with the VFP debugger in front of you.
No dialogs
A VFP error goes to stderr with file and line, and the process ends with its code. Ctrl+C is handled without leaving a write half done.
How it works
- 1Create the project
In FoxForge, New project > Console application (CLI). It lays out your command class, the FoxCli base class and the runtime.
- 2Write your commands
One method per command, in plain VFP. Your code does not parse arguments or know there is a console: it gets the values already converted.
- 3Build and ship
Ctrl+F7 leaves the .exe, its manifest and its documentation in Markdown. To ship it, copy the folder or the zip that pack.ps1 puts together.
Pricing
The programmer is licensed, not the CLI. One-time payment with 12 months of new versions, then 25 € a year if you want to keep getting them. The CLIs you build are yours to hand out, free and without limit: the runtime costs nothing.
FoxCli + FoxCli MCP, both together
If you are going to use your CLIs from an agent as well, take both for 20 % less than separately. It is one purchase and two licenses, with the four downloads in My licenses. The tiers are the same, and the 1-seat tier binds both licenses to the same machine. What FoxCli MCP is.
No patron discount: the bundle already is the discount.
Frequently asked questions
Do I pay for every CLI I hand out?
What happens if I build without a license?
What does the license do, then?
What does the machine that runs it need?
And to program?
What happens when maintenance ends?
Is there a CLI built with FoxCli I can try?
Got VFP logic that should be a command?
Try it for 30 days with the full license, or without a license and without a date: your CLIs work the same.
Buy now