New features in ADO.NET

  • Thread starter Thread starter Tony
  • Start date Start date
T

Tony

I want to know how many differences is between ADO.NET in Visual Studio 2003
and ADO.NET in Visual Studio 2005. I work with asp.net aplications. Will my
applications work in VS2005?
I want to know, does VS 2005 (ado.net 2.0) have only NEW features or have
some differences. Will My database programs in VS 2003 work in 2005 or I
must to change many code?
 
I detail these differences in my book, but I think most people have not had
trouble migrating existing code to VS2005. HOWEVER, the development
paradigms and tools in VS2005 are very different in several respects when
compared to 2003. For example, the DataAdapter wizard has been deprecated
(hidden) and some of the (IMHO) useful development shortcuts were cut
(completely).

hth

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
 
no wonder it confused the CRAP out of me

I just don't see any benefit.

MARS does not allow us 'multiple active result sets' I can't have 2
datasets open on the same connection
I can't even keep a connection problem up; I just want to rub some
Visual Viagra over my .NET connections because they can't stay up.

in VB6 we had CHOICES.
in VB6 we had a complete offering.

Here we have a bunch of chimpanzees saying 'look at me, look at me, im
a signing chimpanzee'

ADO.net doesn't do HALF of what ADO classic does.

NO WONDER THEY INCLUDED A NEW VERSION OF ADO CLASSIC IN VISTA
 
no wonder it confused the CRAP out of me

I just don't see any benefit.

MARS does not allow us 'multiple active result sets' I can't have 2
datasets open on the same connection
I can't even keep a connection problem up; I just want to rub some
Visual Viagra over my .NET connections because they can't stay up.

in VB6 we had CHOICES.
in VB6 we had a complete offering.

Here we have a bunch of chimpanzees saying 'look at me, look at me, im
a signing chimpanzee'

ADO.net doesn't do HALF of what ADO classic does.

NO WONDER THEY INCLUDED A NEW VERSION OF ADO CLASSIC IN VISTA
Click to expand...

Please, feel free to return to VB6 and classic ADO then. Without
specific details of your problems, I'm chalking this rant up to you
becoming frustrated because the framework doesn't work the way you
feel it should instead of learning how to do things properly in .Net.
Technology doesn't stay the same, and sometimes there are paradigm
shifts, and that's what happened with ADO and ADO.Net. There are
plenty of people working with Ado.Net though and the seem to be
working just fine.
 
Andy said:
Please, feel free to return to VB6 and classic ADO then. Without
specific details of your problems, I'm chalking this rant up to you
becoming frustrated because the framework doesn't work the way you
feel it should instead of learning how to do things properly in .Net.
Technology doesn't stay the same, and sometimes there are paradigm
shifts, and that's what happened with ADO and ADO.Net. There are
plenty of people working with Ado.Net though and the seem to be
working just fine.
Click to expand...
He's just trolling. He uses several aliases.
Robin S.
 
Back
Top