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

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

Attending Southwest Fox 2019 could change your life - Find out how

Southwest Fox is coming up in October and as I do every year, I spoke with the organizers Rick , Doug and Tamar on the FoxShow. Deadlines for Southwest Fox: Super-saver price (before July 1): $695 Early-bird price (before August 1): $770 Regular price (August 1 and later): $820 This year, I took a different approach with separate shows for each organizer but the main message is still the same : July 1st is their Go/No-Go date. Conferences don't talk about this very often. I don't think developers really question if Apple will hold their WWDC in June or Microsoft will hold their Build conference - but that's because those conferences are vendor-led. Southwest Fox is a community-driven conference - it's not driven by a company with an agenda. Listen to the interviews and you can hear how important each of the organizers feel the live connection between speakers and among attendees.

Virtual FoxFest - A New Way to Conference

If you haven't been keeping up with the news around the Fox community, the Southwest Fox conference has gone digital now showing up as  Virtual FoxFest .  At $49, it's a steal and a great way to learn some new ideas and get inspired. While the reasoning for this change is fairly obvious with the year of COVID - for me, this is something that has been a long time coming. I appreciate many people's needs for a physical conference but the world is very large and it's difficult to get people from around the world into a single physical location. I recently attended a single-track conference via YouTube (a Quasar conference). YouTube's Live stream provided a very handy way to watch, rewind and communicate with people online. While Tamar, Doug and Rick are still making decisions related to the streaming platform, there are lots of great options available. I'm really looking forward to it. The FoxPro community has also really felt its international roots