ADO and ADO.net

  • Thread starter Thread starter Danieltbt05
  • Start date Start date
D

Danieltbt05

Whats the differences of ADO and ADO.net ? Which one should i use if i
need to design application that using SQL server ? Thanks

Rgss
Daniel
 
Daniel,
Whats the differences of ADO and ADO.net ? Which one should i use if i
need to design application that using SQL server ? Thanks
Click to expand...

The differences are the same as between a car and a plane, however they are
both for transport.

However for your design is probably only important that ADO is mostly done
with pessimistic concurrency and ADONET in my opinion only is good posible
with optimistic concurrency.

I hope that this gives an idea.

Cor
 
Thanks. But which is suitable if i just need to design simple
application that connect to sql server for data manipulation only ?

Rgds
Daniel
 
You can't design a simple application without first selecting a language to
write it in. If you haven't yet selected a language and are asking for help
deciding, then that's an entirely different question.

ADO.NET is based on .NET technologies. If you're selecting a .NET language,
then its clear you should be using ADO.NET.

Robert
 
The issue is i have no idea which 1 is better in handling sql server. I
used to ADO but not sure ADO.net . Can VB handle ADO.net application ?


Rgds
Daniel
 
Daniel,

VB Net as any Net program language can easier handle ADONET than ADO.

Although you are able to handle Ado in VB.Net

I hope this helps,

Cor
 
Which version of VB? Again, if you're talking about VB.NET then its a
no-brainer that ADO.NET will be your choice.

If you're still working in VB6 or prior, (shudder) then ADO is your only
option.

Robert
 
There has been a lot of debate about this. Converting from VB6 to VB.NET is
a challenge. Yes, there is a conversion wizard that can migrate the simple,
obvious stuff but it often can't handle the subtle stuff. It does not
migrate the third-party controls or the user controls you customized to work
with your app (at least not very well). It does not even attempt to convert
the ADO code--it simply wraps it in a COM interop layer and hopes for the
best. This works ok for much of the ADO code, but there are a number of
things that don't work at all.

As I see it, it's like migrating your coal delivery business from a Toyota
1/4 ton to a 20 ton truck. There's a lot to learn and unlearn. Many folks
have opted to rethink the application instead of migrating--they often just
start from scratch leveraging what they know of the business and the current
application. The way that .NET works, the functionality exposed by the
Framework means that a lot more of your application will be done by making
Framework calls. This replaces things you used to hand-code in VB6 or could
not do at all due to the complexity or the "you can't get there from VB6"
issues.

Sure, simple applications will convert fairly easily... but will your
skills? We've heard from some that the learning curve for VB.NET (from VB6)
is quite shallow--it can take quite some time to get productive. It also
makes a difference about what other programming experience you have. If you
also know Java or C++ the learning curve sharpens up quite a bit as VB.NET
seems to flow more like one of these other OO languages. However, those
folks tend to migrate to C#--not VB.NET. Don't discount the time it takes to
get up to speed--unless VB6 is your fourth language.

hth

--
William (Bill) Vaughn
President and Founder Beta V Corporation
Redmond, WA
(425) 556-9205
Microsoft MVP, Author, Mentor
Microsoft MVP
 
Back
Top