I asked Microsoft about using RDS. This is their response:
Unfortunately, RDS and Access have been deprecated because of their inability to ensure secure data connections. Even SOAP is deprecated in
favor of ADO.NET and other features. To encourage the adoption of these more secure features, you won't find much information about them on
Microsoft.com. I did however find which might be helpful to you.
If you are hosting your content on an ISP, though, you might want to check with the administrators, because they might disable RDS on their
servers in order to make them more secure.
If you want to use more secure options, you could try using ADO from ASP, with a SQL backend
(
If resources are available, thought, your most secure option would be to adopt ASP.NET and use ADO.NET within server controls. It's very fast
and easy to develop an ASP.NET page that displays data. There are many data binding options (SqlDataSource, AccessDataSource, XmlDataSource,
ObjectDataSource, SiteMapDataSource) and options for server controls that display that data (DataGrid, GridView, Table, etc). For more information, please see:
I'm sorry that this might not be what you want to hear. Due to this information, I will have to remove the topics in the IIS SDK that deal
with RDS and remote data binding, but it sounds like they weren't very helpful anyway.
Unfortunately, RDS and Access have been deprecated because of their inability to ensure secure data connections. Even SOAP is deprecated in
favor of ADO.NET and other features. To encourage the adoption of these more secure features, you won't find much information about them on
Microsoft.com. I did however find which might be helpful to you.
If you are hosting your content on an ISP, though, you might want to check with the administrators, because they might disable RDS on their
servers in order to make them more secure.
If you want to use more secure options, you could try using ADO from ASP, with a SQL backend
(
If resources are available, thought, your most secure option would be to adopt ASP.NET and use ADO.NET within server controls. It's very fast
and easy to develop an ASP.NET page that displays data. There are many data binding options (SqlDataSource, AccessDataSource, XmlDataSource,
ObjectDataSource, SiteMapDataSource) and options for server controls that display that data (DataGrid, GridView, Table, etc). For more information, please see:
I'm sorry that this might not be what you want to hear. Due to this information, I will have to remove the topics in the IIS SDK that deal
with RDS and remote data binding, but it sounds like they weren't very helpful anyway.