OleDbDataAdapter, OleDbCommand, etc. in VS2005...

[johnb41]

Are objects like OleDbDataAdapter, OleDbCommand, etc not supported in
VS2005/.net framework 2.0?

I'm trying to learn the new techniques for 2.0, but I'm having a hard
time. I need to get something done quick, so i'm trying to do it the
VS2003 way. But my code isn't recognizing the familiar ADO.NET
objects.

Can anyone help?

Thanks!
John

 

[Cor Ligthert [MVP]]

John,

Are objects like OleDbDataAdapter, OleDbCommand, etc not supported in
VS2005/.net framework 2.0?

Of course it is, can you explain something more, do you use the designer or
is it your code. The designer and serverexplorer part has changed by the way
and I am AFAIK not the only one who doesn't like it.

If it is your code, can you than show it, and if it is the designer can you
explain something more.

Cor

 

[johnb41]

Hmmm... i must have been really tired when i tried it before. I could
have sworn the intellisense was not popping up when i did:

dim adapter as new System.Data.OleDb.xxxxxxx (intellisense should
have filled in the xxxxx, but nothing was happening.)

But it works now!

While I have your attention, I might as well ask a related question:

From video tutorials i've watched, (learnvisualstudio.net) it seems

that there are a bunch of new objects and methods to get data from a
datastore: TableAdapter, BindingSource, BindingAdapter, etc. The
videos don't mention anything about the normal oledbdataadapter,
oledbcommand, etc. (or it's sql counterpart).

Does this mean that the "classic" way of doing things is discouraged in
favor of doing it with these new objects? Should I continue to do it
the way I know, or should I start learning the new alternative
techniques?

Thanks!
John

 

[Cor Ligthert [MVP]]

John,

I am not yet so far in those as well, however in my opinion are most of
those things to get easier results by using the designers

Although that Microsoft is maybe a big company, they cannot change the way
the builder of a database creates the provider (beside if they are that
themself for by instance the SQLClient).

They changed however the way that the strongly typed dataset is working, the
connection and handling is beside the string which is in the config file is
in the strongly typed dataset class itself now and not any more in the form
or the component.

For the rest I have not seen really things that don't work from the
WindowsForm, however they have repeared bugs that were not even known in
2003 and if you have used those, than you can have problems.

There is in top of the designer a Data Tab to select your connections.

However as far as I know now.

Cor

 

[johnb41]

Thanks Cor, your reply help alot!!

John