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, :)
Unknown 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

Well, that explains CodePlex...

In a move that will be sure to anger open source (or rather anti-paid software, anti-Microsoft open source)  zealots, Microsoft is planning to buy GitHub.

A year ago, I mused about why Microsoft would shut down CodePlex and how the world needs competing source code repositories to be strong. I'm not the only one per this Slashdot article :
"...people have warned about GitHub becoming as large as it did as problematic because it concentrates too much of the power to make or break the open source world in a single entity, moreso because there were valid questions about GitHubs financial viability...." - Jacques Mattheij

I will be interested in seeing this play out - whether developers jump ship or not. Have all the efforts Microsoft has made in pushing towards open source be seen as genuine or will all the zealots jump ship or maybe even attack?

Microsoft's comment about why they shut down CodePlex referred to how spammers were using CodePlex. Well, GitHub has its own …

FoxInCloud Stats

FoxInCloud sent this link a while back about their statistics regarding visits to their site:

http://foxincloud.com/blog/2017/12/27/VFP-community-lessons-from-foxincloud-site.html



What's interesting here is the breakdown of people. Yes, I think it's understandable that the Fox community is getting older.

Another factor is the growth of the mobile and web environments taking over development. These environments really do push people towards the newer non-SQL or free SQL/hosted environments but more towards hosted storage options like Amazon and Google. A tool like FoxInCloud that helps MOVE existing applications to the cloud inherently competes with those environments.

But FoxInCloud also allows developers to extend their application further by giving them a starting point using Javascript and the basic CSS (such as Bootstrap). If you're not rebuilding your application from scratch, it's certainly a great step forward.

The World of Updates Today

I just received an update for Office 365. It certainly includes some cool features - including starting in one environment and picking it up in another environment. In recent years, I've certainly enjoined the use of Continuity on a Mac and in fact, I feel spoiled being able to start a message in one environment (even Google) and then finish it off on another.  This has become some pervasive when we were reviewing our most recent backlog at a client site, a similar feature was added to the current workload.

But with web applications, the trend is to reduce the amount of software on a client machine. I used to have automatic backup for all of my machines (thanks Carbonite!) but these days, many of my machines don't need anything beyond the core OS and some basic applications. Certainly that's the feeling with Chromebooks and even the lightweight aspect of many iOS apps. The functionality is mostly in the cloud.

When you upgrade your system, you expect it to a big update. So…