>Hi, Bonnie
>
>Re typed datasets: depends who you ask. Some people think they're due for replacement by lightweight POCO and focus on improved databinding, NULL handling and scalability.
>
>Lots of apps use typed datasets so that's an obvious employee opportunity, but employers are looking at next choices too. IMHO opportunities often are best if you're in at the start of the next wave that employers may be contemplating. As the person asking the question is from a VFP background, a cynic may observe that there is less point moving from VFP to another technology choice that people are looking away from. ;-) The other issue is that because so much is new, somebody starting using VS2010 features today does not have the experience disadvantage compared to (say) competing for a typed dataset maintenance position. Which is why in 2010 I'd be looking at POCO and the other VS2010 improvements. JMHO.

2010 has an ADO.NET Poco generator in online templates...(I just discovered this last week reading Julie's blog - I've been playing with VS2010 but not using it yet):
http://thedatafarm.com/blog/data-access/entity-framework-poco-template-for-net-3-5/
(their pure C# classes)