Visual Studio beats SQL Server in 2008 stakes
Microsoft's Visual Studio team has put the database division to shame. Days after Microsoft slipped out the news that the update to SQL Server will not be ready in time for next month's big-dog release event, Visual Studio 2008 has been released commercially - ahead of time.
Visual Studio 2008 is available for purchase under Microsoft's volume licensing programs, through retail channels, and is available for download via MSDN.
Inclusion on Microsoft's volume licensing list means that Visual Studio 2008 is now available to customers via Microsoft's Open, Select and Enterprise Agreement agreements.
This is the latest milestone for Visual Studio 2008, which was released to manufacturing and to MSDN subscribers, in line with expectations, last November.
VS '08 is the first version of Microsoft's tools suite and developer framework to fully utilize underlying architectural changes on the desktop that were introduced with Windows Vista.
One of the biggest new features is support for Microsoft's Language Integrated Query (LINQ) architecture. This simplifies programming with SQL objects, XML and relational data models in C# and Visual Basic.NET.
News of the Visual Studio 2008 availability coupled with the fact that SQL Server 2008 is now delayed will take much of the shine off Microsoft's big launch event in Los Angeles next month. As things stand, just one of Microsoft's three new products - Windows Server 2008 - will actually qualify for official launch status. In other words, it will not have been previously available as a finished and packaged product and it is actually ready for users.®
From the link you posted: "ADO.NET DataSets provide a great way to retrieve, manipulate, sort, and shape data, store it locally for offline use, and synchronize changes back into a central database."
If you exlcude the Schema info from the DataSet serialization, and enable IIS gzip compression then the performance will increase dramatically.
DataSets for disconnected data???
If you're using DataSets to serialize data from one component to another ... or even worse, from one machine to another, you're may be paying a SERIOUS overhead for the privelige.
While the paper that Ingo Rammer and I wrote on this subject was based on .NET FX 1.1, many of the principles remain the same. I'll try to find the cycles to convert the code to NETFX 3.5 and see what the results look like with today's technologies including WCF.
LINQ does rock...
MS simply has the best development tools period, which is aggravating, because they are the only thing keeping me from switching to unix after this Vista BS. LINQ is probably the biggest change to any programming language since C++.
I do also have to agree with Neural9. There are allot of problems with O/R mapping in general. I would still stay with DataSets for disconnected data, but in dropping support for .ToDataTable(), MS has crippled LINQ over DataSets severely. Personally, the problems I've been having are with massive amounts of queries being generated because of lazy loading grandchildren: