something better than xsd.exe for databinding

[Peted]

Hi
using winforms c# vs2008

im using xsd.exe to create a databinding class from an exisiting xsd
schema.

My problem is that it uses arrays for complex types in the xsd schema,
and i have to maually change them to arraylists or other collection
types to be able to use them the way i want to .

Is there a "free" tool that does a better job in databinding than
xsd.exe, or a way to force xsd.exe to use collections instead of
arrays.

Im using liquid xml studio community edition to create the xsd files,
and im sure there was from them also a free comunity edition
databinder wizard they no longer make available. Unfortunatly i cannot
find this older edition anyware for download.

Can anyone help, or provide advice on a better tool to use than
xsd.exe

thanks in advance

Peted.

 

[Pavel Minaev]

Hi
using winforms c# vs2008

im using xsd.exe to create a databinding class from an exisiting xsd
schema.

My problem is that it uses arrays for complex types in the xsd schema,
and i have to maually change them to arraylists or other collection
types to be able to use them the way i want to .

Is there a "free" tool that does a better job in databinding than
xsd.exe, or a way to force xsd.exe to use collections instead of
arrays.

First of all, the term "databinding class" doesn't make sense; and
neither does xsd.exe have anything to do with databinding as such.
It's just a tool to generate XmlSerializer-compliant class definitions
from XML Schema, no less, no more. You use it if you want to parse and/
or write XML of a specific structure in a convenient way.

On the other hand, you can data-bind to instance of any class, not
necessarily only ones generated using xsd.exe. Usually, you'd just
want to implement INotifyPropertyChange though, and use something like
BindingList<T> (if you use WinForms) or ObservableCollection<T> (if
you use WPF) for all your collections to enable change notifications
throughout.

Im using liquid xml studio community edition to create the xsd files,
and im sure there was from them also a free comunity edition
databinder wizard they no longer make available. Unfortunatly i cannot
find this older edition anyware for download.

Okay... please expand on that here. Are you _manually_ creating
those .xsd files just so that you can turn them into classes using
xsd.exe?

If that is correct, then you're definitely doing things wrong. Just
write classes normally, as described earlier.