Geeks With Blogs
Chris Breisch   .NET Data Practices
Search this Blog!

With the impending release of Data Access Application Block 3.1, I now turn my thoughts to 3.2.  What should be in it?  A couple thoughts spring immediately to mind.

  • Support for Visual Studio 2005.  The problem with this is that I think it requires a code split.  I don't think VS 2005 can be adequately supported without breaking support for Visual Studio 2003.
  • Re-working UpdateDataset.  This needs to be alot easier to use and to work a lot better.

What other ideas do you have?  What about helpers for other providers, such as DB2? What about other languages?  It's currently written in C# and VB.NET.  Should Managed C++ be added?  Should VB.NET be eliminated since it's unnecessary?

 

Posted on Thursday, June 10, 2004 8:51 AM Database Practices , Visual Studio , .NET Development | Back to top


Comments on this post: Wishlist for Data Access Application Block 3.2

# re: Wishlist for Data Access Application Block 3.2
Requesting Gravatar...
Ohh geez... Db2, and specifically idb2. i am having a hell of a time with datatype conversion and trying to wrap stored procedure calls with the blocks....
Left by Chameleon on Dec 01, 2004 6:09 PM

# re: Wishlist for Data Access Application Block 3.2
Requesting Gravatar...
The current data application block is tailored to SQL. A nice spin would be one for JET.
Left by ANDREWCW on Dec 25, 2004 11:28 AM

Your comment:
 (will show your gravatar)


Copyright © Chris J. Breisch | Powered by: GeeksWithBlogs.net