>I disagree. Moving VFP out of the box will let it stand on its own and have its own marketing message. If it were part of VS, then it would have to carry the .Net marketing message. Be assured that the decision to move VFP out of the box was made after careful consideration and discussion with many Fox developers. It was also made by the Fox team...not someone in the hierarchy at MS.
>
>
Hi, Craig. You know, I love VFP and FPW 2.6a. However, I am also a contractor and I make a living by knowing and using the tools that companies currently have built their intranet/internet sites with. Right now I am using ASP, JavaScript, CSS, VBScript, VB DLL (building them), DHTML, T-SQL with SQL server. People around me are also using Java.
If you are building your own product, like me, you choose the tool that is appropriate. My toolbox has many tools in it, including VFP and FPW but those tools sit in my toolbox most of the time, while other tools get used heavily.
The decision to pull VFP out of Visual Studio is bad, not good. Many corporate sites use Visual Studio and now that VB has full inheritance, VFP is not even considered.
MS has been defocusing VFP for years. It personally dissappoints me because it is so powerful. However, I am a pragmatic person and the demand for FoxPro has dropped considerably. I know because my last contract using FoxPro was several years ago for Bank of America, Texas. That was the last time anyone looked for that skill. OTOH, last year someone was looking for VFP skills in Dallas TX around Stemmons Freeway but the hourly rate was low and then dissolved into a full-time position - a sign of the times for beloved FoxPro.
Removing VFP from Visual Studio - if VFP was in MS plans, it would have survived as inclusion into the product. If VFP developers did indeed request it to be removed then that was unwise at best.
I hope VFP survives but I suspect it will slowly fade away. It has for me.