XSD.EXE Warning: cannot create classes...

December 19, 2005 · 1 min read

If you build services the way I do, you create the XSD and then generate the classes using xsd.exe (instead of the other way around). I like this approach because the service's consumers will need to generate classes too (and if you start with code, they will probably be able to tell).

Anyway, each time I run XSD.EXE -c for the first time, I usually get the same error:

Warning: cannot generate classes because no top-level elements with complex type were found.

Ideally, VS.NET 03/05 would generate these elements for us as we're designing our complex types, but luckily the fix is quite simple.

For example, here is a complex type that VS.NET might generate in the designer:

<xs:complexType name="SomeType">
    xs:sequence
      <xs:element name="SomeDate" type="xs:dateTime" />
      <xs:element name="SomeName" type="xs:string" />
    </xs:sequence>
</xs:complexType> 

What XSD.EXE -c needs is the following:

**<xs:element name="someRequest" type="SomeType" />
**<xs:complexType name="SomeType">
    xs:sequence
      <xs:element name="SomeDate" type="xs:dateTime" />
      <xs:element name="SomeName" type="xs:string" />
    </xs:sequence>
</xs:complexType>

This article is part of the GWB Archives. Original Author: Craig Hunt

New on Geeks with Blogs

  • We Won The One Award I Actually Care About

    Full Scale made the Inc. 5000 for the fifth year straight, the 12th listing across my three companies. Here is why the one award you cannot buy is worth stopping for.

  • Your Customers Build the Features Now

    I let a tool I liked sit dead for a year rather than build the features I wanted. An MCP server meant I never had to, and your customers can do the same to your product.

  • Get the Size of a Directory in Linux the Easy Way

    du -sh for the quick answer, ncdu for the cleanup, df for the disk itself: every command for checking directory size in Linux, plus why du and df never agree.

  • Vim Search and Replace: The Ultimate Guide

    One :%s command replaces every match in a file before a find dialog would even open. The Vim substitute patterns worth the muscle memory: flags, ranges, capture groups, and multi-file edits.