Per the attached article, Visual FoxPro has reached its end-of-life, and will be released as open source
http://blogs.zdnet.com/microsoft/?p=361
I hadn't actually realized it wasn't already part of the dotnet, the latest version I touched was FoxPro 6. Then 8 and 9 were out so fast, I figured they were to catch up with .net 1.0/1 and .net 2.0, respectively. In fact, Visual FoxPro is still sitting out there in COM land. My prediction is that it will take the open source route, a movement there will build a DotNet interface, with FoxPro syntax, similar in paradigm to Fujitsu's COBOL.net or in that sense Microsoft's J#... it will not be a port of the language, rather layering another syntax on the dot net framework. which begs the question, was it the language features or syntax and semantics that was the strength?
I used to be hard pressed to see how FoxPro's tight data integration can be duplicated in dot net. Now with reading about LINQ, it seems like that is the direction of the entire dot net line.
Subscribe to:
Post Comments (Atom)
Labels
SQL Server
(15)
Project Management
(5)
Dot Net Framework
(4)
SSIS
(4)
Maxims
(3)
Virtual PC
(3)
WMI
(3)
ASP.net
(2)
Data Warehouse
(2)
Database
(2)
Development
(2)
InfoPath
(2)
Oracle
(2)
PMI
(2)
PowerShell
(2)
SQL Server Integration Services
(2)
Software
(2)
Source Code Control
(2)
web design
(2)
Active Directory
(1)
Business Analysis
(1)
C#
(1)
CSS
(1)
Career
(1)
Click-Once
(1)
Flash
(1)
FoxPro
(1)
HTML
(1)
IT Support
(1)
JavaScript
(1)
LAMP
(1)
MCP
(1)
MCTS
(1)
MOSS
(1)
Microsoft Access
(1)
Microsoft Money
(1)
ODBC
(1)
Office 2007
(1)
OneNote
(1)
Open Source
(1)
PMP
(1)
Reporting
(1)
SQL Server 2008 R2; SQL Server
(1)
SQL Server Express
(1)
SQL Server Reporting Services
(1)
SSRS
(1)
SharePoint
(1)
SharePoint Server
(1)
SkyDrive
(1)
T-SQL
(1)
UML
(1)
VB.net
(1)
VBScript
(1)
Visual Studio
(1)
WMI; PowerShell
(1)
Web
(1)
Word 2000
(1)
Word 2003
(1)
mashup
(1)
No comments:
Post a Comment