I'm fairly new to .NET, so bear with me if this question is naive. But do
most developers use the VS data controls for connections, adapters, and
datasets, or do you write all that code manually?

And if you use the controls, how do you wrap your connection and adapter
code so that you can easily switch between SQL Server, OLE DB, and ODBC?

I've been writing the code manually, and I'm comfortable with that, but I'm
wondering whether I'd be more productive using the Visual data controls.

Thanks,
Steve Murphy

There is no easy one-line answer for this question. While many developers
use the wizards and the code they generated, others (more than half) find
this code to be too simplistic for their specific requirements. In cases
where you need to write a front-end that can access several data sources, we
usually suggest creating a separate data access layer (tier) that handles
DBMS-specific operations and expose this class to the application. This way
you can (in theory) "simply" substitute another layer to access other DBMS
backends. I discuss this in depth in my books.

hth

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
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.
__________________________________

"Steve Murphy" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> I'm fairly new to .NET, so bear with me if this question is naive. But do
> most developers use the VS data controls for connections, adapters, and
> datasets, or do you write all that code manually?
>
> And if you use the controls, how do you wrap your connection and adapter
> code so that you can easily switch between SQL Server, OLE DB, and ODBC?
>
> I've been writing the code manually, and I'm comfortable with that, but
> I'm
> wondering whether I'd be more productive using the Visual data controls.
>
> Thanks,
> Steve Murphy
>
>
>

this is a very big issue for me. Which book do you recomend for what you just
described.
thankd you
kes

"William (Bill) Vaughn" wrote:

> There is no easy one-line answer for this question. While many developers
> use the wizards and the code they generated, others (more than half) find
> this code to be too simplistic for their specific requirements. In cases
> where you need to write a front-end that can access several data sources, we
> usually suggest creating a separate data access layer (tier) that handles
> DBMS-specific operations and expose this class to the application. This way
> you can (in theory) "simply" substitute another layer to access other DBMS
> backends. I discuss this in depth in my books.
>
> hth
>
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> 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.
> __________________________________
>
> "Steve Murphy" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
> > I'm fairly new to .NET, so bear with me if this question is naive. But do
> > most developers use the VS data controls for connections, adapters, and
> > datasets, or do you write all that code manually?
> >
> > And if you use the controls, how do you wrap your connection and adapter
> > code so that you can easily switch between SQL Server, OLE DB, and ODBC?
> >
> > I've been writing the code manually, and I'm comfortable with that, but
> > I'm
> > wondering whether I'd be more productive using the Visual data controls.
> >
> > Thanks,
> > Steve Murphy
> >
> >
> >
>
>
>

> this is a very big issue for me. Which book do you recomend for what you
just
> described.
>
> > There is no easy one-line answer for this question. While many
developers
> > use the wizards and the code they generated, others (more than half)
find
> > this code to be too simplistic for their specific requirements. In cases
> > where you need to write a front-end that can access several data
sources, we
> > usually suggest creating a separate data access layer (tier) that
handles
> > DBMS-specific operations and expose this class to the application. This
way
> > you can (in theory) "simply" substitute another layer to access other
DBMS
> > backends. I discuss this in depth in my books.


I am also interested in your book. What is the title, and where is the best
place to get it?

Thanks,
Steve Murphy

See www.betav.com for details. Note there is a site there that looks up the
best price. http://www.bestwebbuys.com/books/sea...=1-893115-68-2

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
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.
__________________________________

"Steve Murphy" <(E-Mail Removed)> wrote in message
news:uat4st$(E-Mail Removed)...
>> this is a very big issue for me. Which book do you recomend for what you
> just
>> described.
>>
>> > There is no easy one-line answer for this question. While many
> developers
>> > use the wizards and the code they generated, others (more than half)
> find
>> > this code to be too simplistic for their specific requirements. In
>> > cases
>> > where you need to write a front-end that can access several data
> sources, we
>> > usually suggest creating a separate data access layer (tier) that
> handles
>> > DBMS-specific operations and expose this class to the application. This
> way
>> > you can (in theory) "simply" substitute another layer to access other
> DBMS
>> > backends. I discuss this in depth in my books.
>
>
> I am also interested in your book. What is the title, and where is the
> best
> place to get it?
>
> Thanks,
> Steve Murphy
>
>

"William (Bill) Vaughn" <(E-Mail Removed)> wrote:

> See www.betav.com for details. Note there is a site there that looks up
the
> best price. http://www.bestwebbuys.com/books/sea...=1-893115-68-2


Are the VB and C# books pretty much equivalent? Do they both cover layering
with the same depth?

Thanks,
Steve Murphy

The difference between the two books (if you ignore the language
differences) is in how ADO classic covered--it's not mentioned in the C#
book.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
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.
__________________________________

"Steve Murphy" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
>
> "William (Bill) Vaughn" <(E-Mail Removed)> wrote:
>
>> See www.betav.com for details. Note there is a site there that looks up
> the
>> best price.
>> http://www.bestwebbuys.com/books/sea...=1-893115-68-2
>
>
> Are the VB and C# books pretty much equivalent? Do they both cover
> layering
> with the same depth?
>
> Thanks,
> Steve Murphy
>
>