Backward compatibility for ADO.NET ?

Hi,

I have a beta 2 release of VS 2005. I am trying to open a sample which is originally made in VS2003. It simply has a datagrid bound to a dataset. I can't open it. It seems the datasets made through wizards at design time are not converted by the conversion wizard properly, and the datasets are not recognized. What do I do ? Is theer any way to completely convert the .xsd files also, to ADO.NET 2.0 format ?

P.S : When I tried the same sample with all datasets, connectionstrings at runtime, it works fine. However it is now not feasible to change my huge porject at this stage.

Any help is greatly appreciated.

[657 byte] By [A.A.] at [2007-12-16]

«« Debugging Device Control Libraries
»» disappearing component

# 1

The Visual Studio team is focused on providing backwards compatibility with Visual Studio 2003 projects. I spoke to one of the members of the team and he recommended submitting a project and/or steps to reproduce the behavior via the Product Feedback site. Here's a link to the site:

http://lab.msdn.microsoft.com/productfeedback/

Click the link for "Report a Bug" and select "Visual Basic .NET" as the product.

This should help route the issue to the appropriate team members as quickly as possible.

David Sceppa

ADO.NET Program Manager

Microsoft

DavidSceppa at 2007-9-9 >