Hi Rick..

I see VS .Net as being at the beginning of an evolutionary path. With respect to windows apps, do I think it abandoning VFP in favor or VS .Net for windows/desktop apps is warranted in the next 12 months? No. Do I think folks, for learning purposes give it a shot? Yes.

Having used VB for about 8 years, the form designer in VS .Net is light years ahead of VB 6. The fact that a full OO model has been implemented is enough to grab my attention. While a containership model does not exist ala VFP's, I think that is a minor speed bump. With respect to binding, the best way of handling that may be yet to be determined. Still, there is a lot to be excited about. The integration with the OS, ability to build windows services, etc. There is usually a marked difference between how the inventor envisions a tool being implemented and how the tool will be implemented.

As far as the languages are concerned, I am backing off my stance that VB .Net would be a better alternative. Looking at the language spec, I think C# does look appealing. After all, looking at a simple variable declaration, which would you prefer:


int a = 10;

or

Dim a as Integer = 10

I think I'll take the first one. Class definitons look cleaner and the phrasing seems more cleaner and natural as well.

As far as SQL-Server is concerned, you will definitely be able to take assembelies and implement them in SQL Server. With respect to office, I think it will have to implement the CLR to some degree. What the actual degree is, I don't know. What is going to replace VBA? I think it will be VSA.

I do agree that most likely, the emphasis has not been on windows-based applications. I think that is going to be a rich area for defining and formulating optimized techniques.

We shall see....