Answer Posted / niloy roy

There is a lot of mythology surrounding ActiveX Data
Objects (ADO) and XML. ADO has supported XML since version
2.1. In general, this is a good thing, especially for
developers looking for better ways to reach out to the four
million programmers who use Visual Basic and who also
worship at the altar of the disconnected recordset.
However, simply supporting XML in your application is not
good enough because ADO uses a very stylized XML-based
vocabulary to perform its magic. The way ADO uses XML
allows ADO to interoperate with applications written in
programming languages such as Java, Perl, or Python and on
platforms such as Unix, Linux, and Apache. Yes, the
developer who uses Visual Basic can deal with arbitrary XML
using any number of XML parsers. However, morphing your XML
into the vocabulary of ADO makes it a no-brainer for any
typical application-focused programmer to access your
information with Visual Basic.

What is execute reader in ado.net?

965

---

Does dapper use ado.net?

1019

---

How to create data relations?

1001

---

What is aggregating data ?

963

---

What is an orm, and why would you use one instead of plain old ado.net?

1052

---

What is concurrency? How will you avoid concurrency when dealing with dataset? (One user deleted one row after that another user through his dataset was trying to update same row. What will happen? How will you avoid the problem?)

1004

---

What is a non query?

933

---

What is difference between ado and other data object?

914

---

What are dcl commands?

1009

---

Do you use stored procedure in ado.net?

1028

---

How to identify the controls which can be used for binding data?

1000

---

Which object of ado contains datarow datacolumn collection?

966

---

Can we connect two dataadapters to same data source using single connection at same time?

989

---

Is it possible to edit data in Repeater control?

966

---

What is the difference between Datareader and Dataset?

1083

---