VS Data is one team (by yag)

John Koziol - one of the testers on my team - posted an entry in which he began to discuss some of the things he's learning as he dives in VB.NET. We've gotten a number of responses - which are of two forms:

  1. You're just trying to force VB on us Fox folks - how dare you? And why VB instead of C#?
  2. This is great! My value is in what I know and in creating systems. The more I learn, the more valuable I am.

I just wanted to respond to those who posted things along the first line. First, the easy part - why VB? Because John is a tester on VS. VB.NET is used by our testing frameworks. So, our testers tend to develop in VB when they write their automation.

Now - why did John write it? Because he enjoys blogging about what he's doing, and that's what he's doing right now. VS Data is one team - it's not two teams, one VS and one Fox. VFP9 shipped with tools that allow you to access and manipulate SQL Server databases. They work like the ones that ship in VS. Amazingly, some of the work on that was done with the help of folks who write VS code. John's now tasked with getting the VFP automation frameworks into the same standard tools as the rest of VS. This allows us to allocate test resources more easily between the products.

I've personally used Fox since version 1.21 for DOS. I've also used Fortran, C, VB, Powerbuilder and other languages. My personal value to this team, to Microsoft, and to our customers is in my understanding of data access across languages. That allows me to work with others to create the best data capabilities across all of our products. That's what I'm working on. That's what my team is working on. I'm sorry if some people feel that language has to become how they see their own selves (and I'm talking to VFP, VB, and C# folks here). People have to realize that, at the end of the day, bad applications can be written in any language. Good applications can be written in any language. The differentiator is the analysis that the developer or team does and their use of the tool.

I was at VSLive/SQLLive etc., this week. I saw a lot of Fox people there - attending, speaking and even running booths. I've seen VB and C++ developers at Fox conferences. Seems to me that's a good thing.

One more thing. If you have MSDN, you have both VS and Fox. No matter which you use - it pays to check out the other - they each have awesome capabilities, which we're dedicated to providing in both.

Comments (5)

  1. I’m a die-hard Fox developer but I agree that the people who think that we can’t talk about any other language are missing out on learning a thing or two. Besides, I enjoy hearing about cool new features in Visual Studio that we Fox programmers have had for years.

  2. yag,

    There is somewhat of a language war going on in relation to .NET. Last night I was involved in a discussion with an MS MVP lead and an MS Regional Director regarding the new Enterprise Library. They were bemoaning the fact that it’s written in C# and not VB.NET. They don’t want to deploy an additional assembly to get those features. On the other hand, we also pointed out that Office automation is easier in VB.NET than C#.

  3. Vern says:

    Yag, I understand what you are saying but people at Microsoft are under the ILLUSION that all programmers have the time to learn new languages AND attain the neccessary skill level to produce the good applications you are talking about. I have seen too many programmers who know a little of this and a little of that – these people are worthless.

    Granted, there are some who can master multiple languages. However, they represent a MINUTE percentage of programmers who are currently employed.

    You guys at Microsoft are in lala land.

  4. BR says:

    Since you’re language neutral, I’m sure you would approve of people checking out Java and Python as well.

  5. John Koziol says:

    We’re language neutral, but not vendor neutral *g*.

Skip to main content