problem converting xsd from 1.0 to 2.0

[Les Caudle]

I've inherited a .NET 1.0 app that I'm converting to 2.0.

It contains a number of .xsd files (.xsd, .xsx, .cs) which get converted to
(.xsd, .xsx, .xss, .xsc, .cs, .Designer.cs).

The problem is that after VS 2005 converts these files, they will no longer
compile.. There are numerous classes with the partial keyword left off, and many
duplicate classes between the .cs and the Designer.cs.

I'm slowly converting the project, and am dragging the (.xsd, .xsx, .cs) files
into the Solution Explorer.

There are so many that it would take a week full time to try to massage them by
hand.

How can I get these files to convert properly, so that they will compile?

 

[Guest]

Hi,
I tried a similar scenario and it was working properly, kindly check the
following link, this may help you:

http://msdn2.microsoft.com/en-us/library/aa479567.aspx

Regards,
Husam Al-A'araj

 

[Les Caudle]

Husam - that solution won't work for me.

I'm unable to convert the existing solution. It is running 'live' on an
existing server - to be replaced by my conversion when I get that working.

So, I already have a .NET 2.0 solution, with about 1/2 of the files from the old
solution working.

I drag them in one by one.

The aspx pages convert ok, with a bit of massaging.

But the XSD files do not. For some reason, they are getting converted into
multiple files with the .Designer.cs - instead of just importing directly.

Partial classes are only created in one file, not in the others, and there are
multiple duplcate classes (that were not there before).

Anyone else with an idea?

Thanks, Les Caudle