I was recently approached to build a small application (data management app) for a long time customer of my firm. Since we began discussing this new project, I have been spending every spare minute learning as much as I can of the new technologies that is (or soon will be available) at my finger tips with Visual Studio 2005, and how some of these new technologies could be implemented into this new project. But I find myself being forced to consider a tool that I have relied on for such similar projects for many years…being Visual FoxPro. It is so tempting to push forward and build the application with these new tools but my “rational” side keeps pulling me back to the reality of the situation. I have years of experience with Visual FoxPro (as well as Visual Studio) and this experience tells me that Visual Fox will build the application they require with no limitations, in less time and therefore at a cost savings to the customer. Yet my addiction to new technologies fed by the ‘Microsoft Marketing Machine’ makes me eager to build an application (production app) using these new technologies.
In fairness to my customer (and my desire to retain this customer), I am proceeding with the tool that my “gut instinct” tells me is the best for this particular app (Visual FoxPro) but it is so tempting to move forward with some of these newly introduced technologies.
<As a footnote, the Visual Studio Data team just released Visual FoxPro 9.0 to beta – both MSDN Subscriber and public beta – so either way, this new application will harness some new technologies>