The Problem With Visual Studio .NET 2007

      No Comments on The Problem With Visual Studio .NET 2007

Yes, you read correctly. 2007! .NET 2005 isn’t even out yet and Microsoft is already doing a sell job on VS .NET 2007. (By then, they’ll have dropped the .NET part of the name.)

Microsoft is starting to talk about how 2007, will have better integration and a closer relationship with data. Here’s a quote from the article: The Father of C# on the Past, Present and Future of Programming from Microsoft-watch.com

I think our approach in C#, though, is going to be a little bit different. FoxPro is very tightly married to your data being data in a database. When I talk about data in this conversation, I mean data at large. It doesn’t necessarily have to come from a database. It may as well come from an XML document or just be something that you moved off a bunch of objects and now you want to do set and query operations on these graphs of objects. So in that sense, we’re sort of coming at it in different ways.

Huh? How many years has Visual Studio been out? They’re just now getting to making it easy to work with data? These quotes totally sound like a half assed effort to me. This goes to show that M$ isn’t serious about business solutions. I think the C++ crowd had too much sway with the Visual Studio .WHATEVER project. Too many bitheads in the kitchen.

I thought that .NYET was object oriented too?!?! “Something is rotten in the state of Denmark.” (Redmond). If .NET was so damn cool, how come more people aren’t able to overcome it’s data deficiencies? Why hasn’t someone subclassed a base class, create a property called “CONTROLSOURCE” (like VFP) and then make up some methods that reference back to some ADO.NET object? If that is hard to do in .NET or non-obvious, then perhaps .NET is fundamentally flawed. A little OO work should have been able to overcome .NET’s poor data handling.

And yet, true geniuses like Rick Strahl, Kevin McNeish and others seem to be stumped on how to make .NET work with data as easily as Visual Foxpro. I believe that they’ve tried. They aren’t excited about their own results.

Where does this leave us? Is it just me, or does it sound like .NET is stalling and they’re trying to keep it from falling on it’s face? Here we are, in the 21st century, decades into the IT movement, on the eve of a .NET 2005 release, talking about how great .NET 2007 will be. Have I missed something? Should I start drinking now?

Does it sound like I’m bitter about M$ not making more of an effort to continue an excellent product like VFP? They should have merged the Foxpro language and abilities into SQL Server and came up with a brand new/cool name for the language. They could have sold tons of upgrade licenses to this new capable product.

BTW, has anyone heard much buzz about writing .NET based stored procedures in SQL Server lately? No? Me neither.

Leave a Reply