In the history of programming. Net, no other tool having a climb and fall so fast as noisy as the Dataset. Used as a emblematic item at the early .Net versions, was abused commercially as the solution to all problems of programmers to access and manipulate database. Big mistake, the obvious gap between the development team which created a powerful and versatile object, and the final link with the client (whether msdn or technet) which basically is the visible face to the community of developers and purely commercial court has completely clueless about the skills and dangers of its use. This component is the living example of such a great idea is misleading and manipulated in order to achieve sales, and their way of promotion is an easy way to badly stop the product.
Clearly, not all the fault of the seller, but many times the speed of the market and the decisions on the fly without knowing either the products they mistakenly used the tools. The big problem here is that he blamed the bad component of the publishing being generated or its poor implementation practice, and as the customer is always right, just goes to Microsoft for leaving out the playing field in this component with each new version of Visual Studio, and worse, the solutions are in place as Linq and Entity Data Model not only away from the road, but their benefits are not enough to cover or replace the possibilities offered by DataSet. I will comment on details of usage or best practices in use, and its comparison to highlight the major differences. I just hope to claim their profits before they disappear completely.
(tiny)
.gif)
