Skip to main content

DotNet vs. FoxPro for Features

One of my clients is in an interesting situation where they are looking to move their main development platform to DotNet but in doing so, they are having to look at the key feature set of their current FoxPro application. DotNet advocates are actually pushing back from doing the same kind of things in the new version that are currently in the FoxPro application (not many IT people like the idea of allowing users to write dynamic code that can be compiled on the fly).

I was hoping to find a place on the Wiki where it compared feature for feature between tools like Visual Studio and VFP.

Anyone know of one? Since they are both MS tools, it's likely going to be hard to find one. The VFP Conversion site has a variety of resources but many of the valuable ones are links to Advisor articles. There should be some matrix somewhere.

The link I did find was this one comparing how much code it took to write a Wiki in C# and found Bob Archer's comment to be all to true.
"Many times the FIRST question our sales people are asked is "What language is it written in?" like this is some indicator of quality"

As long as sales people ask this question, they are implying some measurement of quality which is funny because the last time I checked, most "product" sales people couldn't tell you WHY a particular language was better or worse than another, except that it was marketed better.

I did find an interesting discussion on Disconnected Data Sets for VFP and DotNet but what I'm really looking for is something that compares one feature to another, kind of like this

This will be something I think I'll bring up in the second part of the interview with Bill Sanders from the efGroup on the FoxShow which will be posted sometime this week.

Comments

Asad said…
but i like foxpro, :)
Macrosoft said…
Microsoft stopped foxpro support. We should migrate foxpro to .net migration.

Visual FoxPro to .Net
FoxPro to .Net
Visual FoxPro Migration
FoxPro Migration

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...