JVP,

You make an excellent point, but I'd like to clarify a little.

There are two things one might think about when discussing ".Net" - one is the .Net concept of having information in "the cloud" which is accessible via the Internet by many different clients. This is central to Microsoft's corporate goals. VFP plays well in this area.

The other is Visual Studio .NET which is a group of developer tools (C# and VB.Net included) which are specifically designed to be useful in creating applications that provide or consume the web services necessary to the .Net initiative. I believe you are saying that you see yourself useful in helping VFP developers expand their toolsets into this area.

As will continue to be true, it's a big world with plenty of work to be done. We'll each find the place where we fit best. Thanks for finding your niche and optimizing your talents in this way.



>This past week has caused me to do a lot of soul searching about VFP and the work that I will concentrate on over the next couple of years. If you asked me a year ago to develop an application that needed remote and web capability as well as interoperatbility with disparate devices, I would be left to wonder about all the pieces that would be required and further, how to make all those pieces fit and work together. Today, I see .Net has the workbench platform for developing those types of applications as well as apps that work in a LAN environment - the type of apps primarily developed with VFP/VB 6.
>
>VFP is what it is, a nice tool for developing windows-based database applications. At the same time, .Net is the future and will be a nice tool for developing windows-based database applications. There was one primary message conveyed during the summit - .Net is the future. Eventually, SQL Server and Office will be built on the CLR as well as Visual Studio.
>
>As for me, the choice is clear. I will conduct the same research and make the contributions that I did in introducing ADO to the VFP Community. My goal, to have resources available to the VFP developer who wants to migrate to .Net. For those that wish to stay in VFP, I wish them the best of luck and will leave it to others to continue the tradition of developing optimized tools and strategies for VFP. For those that wish to and/or need to transition to .Net, I want to help by providing resources from the VFP developers perspective that will make that transition much smoother.
>
>I am proud to be a VISUAL FOXPRO MVP! IMO, one of the most "valuable" things a VFP MVP can do is to help blaze a trail for the VFP developer who wishes to migrate to .Net.
>
>It's a brave new world! I am going to go grab the brass ring!
>
>Regards,