XSD vs Dingo
Files in foobar sample:
- Foobar.cs - foobar class
- foobar.csproj - VS.NET project file
- foobar.sln - solution for project
- Test - simple test class to load the sample data
- xml - directory containing the schema and sample data
If you don't want to go through all the steps, you can simply open foobar project, build and run the command. The output from the simple test should be similar to the example below.
- Open a DOS shell
- change to "Dingo/bin/" directory. Example: cd c:\Dingo\bin\
- copy foobar.xsd to the bin directory
- compile the schema with "dingo foobar.xsd" command
- copy the generated files to "Dingo/samples/foobar/" directory and replace the existing files. The files should be the same.
- open the foobar project
- open Test.cs class in VS.NET
- build the project
- open a second DOS shell
- change to "Dingo/samples/foobar/bin/" directory
- run the test with "foobar.exe" command
loaded the xml successfull
The foobar sample is from Sun's JWSDP 1.4 release. If anyone has a particularly complex schema and would me try it, feel free to post it to the forum or email it to me directly woolfel AT gmail.com. Most of the schemas I've come across from VS.NET are rather simple and generally should work.