Foxpro in Visual Studio 2005

Hot Topic

_screen.ContinuousScroll problem
Records Disappear
Strategies for Stoping non customers from using my software
RICHTEXT.RichtextCtrl
Call application from program and trace Menus and Programs within
FTP with VFP
Set talk, set deleted in forms
connecting to foxpro table from asp or php
Using SQL Pass Through to Access my Remote Data Source
How to create a distribute package in VFP8.0?

Visual FoxPro

Grids are readOnly. How do I put text in them?
sometimes no response to mouse clicks.
Parameter Query
Preview container toolbar doesn't respond
cannot generate an exec file
Combine records into 1 text box using ALLTRIM
UPDATE vs REPLACE record locking
How to determine total audio time track?
Oleboundcontrol
Coming from Excel to VFP9 and need help understanding math functions on cells

Foxpro in Visual Studio 2005

Hi  .

Why Microsoft dont develop Visual Foxpro .
and why Microsoft dont create Visual Foxpro in .NET Freamwork

ThankX. Skyline . Smile


Answer this question

Foxpro in Visual Studio 2005

  • California

    Why do you ask your first question is something of a mystery. All you have to do is a little search online or just look at MS site and you will see that Microsoft has been updating/developing Visual FoxPro regularly every 18 months or so for more than 10 years! The current version is 9.0, released in December 2004. There is a Service Pack 1 in Beta testing slated to be released around December 2005.

    New plans for the next version of VFP, code-named Sedna have been announced and there is a community project (SednaX) in GotDotNet currently under way.

    As for you second question it's an easy one. Answer: because I does not make much sense to make VFP work in the CLR.

    Visual FoxPro works very well with .NET through COM Interop. Can also create and consume XML and Web Services natively.

    What would be gained from compiling to the CLR Nothing. It would lose its identity. It would lose the XBase language as you would not be able to open tables natively (the USE command is not part of the CLR). It would break all previous code (non-compatibility). It would become just another .NET language with a similar syntax to VB.NET. What would be the point

    HTH

  • howgoodisthis

    I'm not sure what your first question means. VFP 9 shipped this year and a service pack is expected before the end of the year. They've announced their plans for Sedna, the next version as well.

    http://msdn.microsoft.com/vfoxpro/Roadmap/default.aspx

    Tamar

  • Ghastly

    In addition to what you have been told already, youy will notice that there are actually two other notable Microsoft products that are NOT in the .NET framework.
    Access
    SQL Server

    Like Visual FoxPro they are databases and since the .NET framework is not (yet) designed to incorporate data integration they are not in the framework either. It is reported that the NEXT release of the .NET framework will have some form of data integration and it has been hinted that this will be based, to some extent, on technologies implement in VFP - but this is all speculation so far...

  • Stankov

    Hi

    Just check Ken Levy's blog to find out the why. He writes it clearly.
    http://blogs.msdn.com/klevy/archive/2005/10/28/486582.aspx



  • Foxpro in Visual Studio 2005
Answer this question