Opinions Please..

[Lethal]

What .NET technology do you think would logically make sense to tackle next: ASP.NET, ADO.NET, or Web Services.

[PT Exorcist]

tackle? what does that mean?

[hellswraith]

They kind of all go hand in hand. If you are creating ASP.Net apps, you will most likely be using ADO.Net for accessing DB's. Web services will also be using ADO.Net to access DB's for the most part. Web services are more or less just objects that get serialized and past over http requests along with people accessing server objects and calling them like they would do a local object.

For me, I will be tackling ADO.Net first, then quickly moving to ASP.Net. The web services part will fall in place last.

[Lethal]

Yeah, I think I'm leaning towards ado.net. In order to create any 'real' business apps, ado.net seems to be the glue that ties everything together. Thanks Hellswraith

[DevGrp]

I also vote for ADO.NET. It will only be easier moving to ASP.NET next.

[Lethal]

Yeah, I guess I'll go buy a book tomorrow night. What I usually do is go to amazon.com and read the reviews of the books I'm interested in.

[kovan]

is it me or u need ASP.NET which uses ADO.NET which can spit out the results to Web Services(in most cases)
so u cant buy a building thats missing one or more pillars.. it will collapse..

[Scott Penner]

No,
I think ADO and WebServices are pretty well separate. ADO.net is very powerful in the desktop realm as well as behind the scenes of a web application. Also, you could develop web services and not know anything about HTML or user controls.

my 2 cents...