Dealing with legacy issues

Contoso has several applications that currently use ADO.NET to interact with the database. Each application used to run locally inside the corporate network. Now, there’s tremendous pressure to expose many of them to the outside world. You’re tasked with deciding whether ADO.NET should continue to be used or whether a move should be made to another technology. If a move away from ADO.NET is made, you need to decide which other technology should be used.

Should you continue building applications with ADO.NET?
Does using the EF provide any benefit toward the stated goal that ADO.NET doesn’t?
Would WCF Data Services provide any benefit toward the stated goal that ADO. NET doesn’t?