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

Merry Christmas

Whether you celebrate now, have already celebrated your past holiday, are planning to, or not, I hope you find yourself surrounded by family and those you love during this holiday season and are able to remember fondly those who are not with you. We often find ourselves buried in work, or too distracted by other problems, to share and remember a few moments with those closest to us. So many of us are separated by huge distances, we often find it easier to focus on those who are out of arm's reach yet so easy to connect with online, instead of those who are right beside us. So do yourself a favour, put down the keyboard (stylus, mouse, etc) and spend that time. I know I will. Merry Christmas. Powered by ScribeFire .

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...

From Writing to AI: the pattern repeats itself

When I was ten years old, my dad bought a computer and, thanks to an advertising supplement in a Superman comic I read, it was a TRS-80. A month later, he dragged the entire family (my mom and brother were not the most enthusiastic) to a class at Radio Shack teaching how to use microcomputers. At the time, I understood why my mom wasn’t that excited: the computer was yet another gadget in the house. But today I find it fascinating. My mother went to Vassar in the 50s. She learned how to type — not a common skill at the time — but it opened doors. Her ability to communicate effectively led her to a career in adult education and later communications work with the CBC (Canadian Broadcasting Corporation). This isn’t a nostalgia post. Today, the ability to use artificial intelligence, be it through Copilot or simply writing the right prompt, is becoming a critical skill. But is it really that novel? In the 1500s and 1600s, the printing press gradually made reading accessible beyond cler...