Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
VFP in a .NET World a from FoxPro Advisor October 2001
Message
From
11/10/2001 21:28:24
 
 
To
11/10/2001 09:10:18
Alexandre Palma
Harms Software, Inc.
Alverca, Portugal
General information
Forum:
Visual FoxPro
Category:
Visual FoxPro and .NET
Miscellaneous
Thread ID:
00566897
Message ID:
00567367
Views:
10
>While .NET is geared primarily for distributed, Web-based applications, VFP will continue to be geared toward robust client-server applications." since everybody now is saying that client-server is dead and in my experience this is true now all the applications are being developed as n-tier applications, then all new developers shouldn't use VFP unless they are designing desktop applications and don't have any plans that those applications should run in a n-tier environment.
>Then also if this is true then why the heck does Microsoft put all this new features in VFP if we are to development old types of client-server application or desktop applications then Why do we need to create web services and why do we need XML?

I read this article by Jenny Brown in FoxPro Advisor magazine, and I have to say I completely disagree with your summary and comments about what what written. To start, Jenny is a VFP developer, one who has taken the time to also develop in VS .NET beta 2, so she has the proper perspective in commenting on VFP and .NET.

Nowhere in the article does it say client-server applications are dead, and nowhere in the article does it imply that VFP doesn't fit will in .NET.
XML Web services is about creating distributed applications, and VFP 7.0 allows developers to venture into this new technology while still supporting all the great 1 to n tier development strategies as before.

I suggest you review the comments that Steve Ballmer recently made about VFP 7.0 and how it relates to .NET at http://msdn.microsoft.com/vfoxpro/prodinfo/ballmer.asp

Everyone who reads Jenny's article in FoxPro Advisor magazine should take it seriously and consider it an extremely well written article, and it states the right information about VFP and .NET. Just take a look at the summary sentence in the article:

"What's important to realize is that even though Visual FoxPro isn't part of Visual Studio.NET, it can still play an important role in a .NET solution—that is, if you choose to incorporate it into a .NET solution."

The above statement is completely accurate and is an excellent summary. Those interested in using VFP7 along with VS .NET should consider upgrading to the new MSDN Professional subscription level that includes VFP7, VS .NET, VS6, and all the Windows operating systems and SDKs. A good complement to this FoxPro Advisor article on VFP and .NET is the Web Services whitepaper for VFP at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/fox7help/html/fogrfWebServicesInVisualFoxPro.asp
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform