Jeff stated, "VFP versus .NET". Most .NET shops use the Enterprise version. (Many have the MSDN universal subscription.) The standard edition of Visual C# "targets" (among other people) beginners and those looking to take a first dive into the product. I would never use the standard edition for a development project, so I certainly wouldn't utilize it for this.

Either that or you would allow the VFP developer to include a CASE tool, a web development tool and other productivity tools to match those you are awarding yourself in the premier version you chose.

Once again, Jeff stated VFP versus .NET. He did not say, "VFP plus this, plus this, plus this". You yourself found Jeff's terms very fair. An allowance for those tools is an admission/acknowledgement that .NET contains these things, and that VFP is lacking in those areas out of the box.

Asynchronous processing- with add-ons, no problem, as long as the developer judges that it is necessary. But you've blocked use of add-ons, and asynchronous processing is not always necessary.

Developers aren't always going to judge whether asynch processing is necessary. The application requirements drive that.


Kevin