Skip to main content

Microsoft's Visual FoxPro Roadmap

Well, the road map is up and it says ......

"The primary goal of Sedna is to expand on the ability of Visual FoxPro-based solutions to better integrate with other Microsoft products and technologies."

Hmmm....what that mean? Well it certainly states what it does NOT mean:

"Microsoft does not plan to merge Visual FoxPro into Visual Studio .NET, nor are there plans to create a new Visual FoxPro .NET programming language."

The one I wish they would do is bring back the ability to debug FoxPro in Visual Studio but I think debugging COM components is something that every developer wants an easier way to do, and because of the very nature of COM, it's very difficult to do.

But the real focus is noted in Ken's June letter, where he effectively says they are working less on specific language or engine features and more to ensure FoxPro apps will run well in 5+ years. In short, maintenance mode.

Which is GREAT news for developers who are tired of constantly having to upgrade to the latest version, but NOT SO GREAT for those of us who are looking for more features to be put into the core engine. Developers should be fairly happy that while development has not STOPPED on newer tools for use within FoxPro, they should be able to work with a single version for a period of longer than two years. New features and tools will be made available - and they will WORK with the current version, not requiring endless upgrades.

However, if you look at many of the features to be found on the Wiki's Version 10 Wish List, you can be sure that some of these requests will find their way into the xBase apps or C libraries that will make up much of Sedna.

I'm sure some will take this "map" to mean all kinds of horrid things but the fact is that Visual FoxPro is a very functional language and database tool. I just finished a discussion with a client where we were talking about roadmaps. As a statement of what the Fox team is doing or will be doing for the next x months, the roadmap is good. As a true roadmap, one that shows where FoxPro is heading, this one is sorely lacking and open to many different interpretations. Granted, Microsoft has to be careful of not setting off too many on the everything is dead trail as they did with the VB 6 community - but something a little more would have been appreciated.

As it stands now, FoxPro developers should take great comfort knowing that VFP is supported in its current form by Microsoft until 2014, a full nine years away. By that time, DotNet could be replaced by yet another acronym (how quickly did it take MS to move from ActiveX -> COM -> DNA -> DotNet). Maybe in 9 years time, it will translate itself into another one of Microsoft's OpenSource projects.

On a slightly different note - if you're working with VFP and DotNet, Kevin McNeish's book DotNet for VFP Developers is available for download. That's good news for many people who need to switch back and forth.

Visual FoxPro: Microsoft Visual FoxPro Roadmap


Macrosoft said…
Nice information about microsoft visual foxpro roadmap.

Visual FoxPro to .Net

Popular posts from this blog

FoxInCloud Stats

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

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.

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 …

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…