xsd(1)

💖 xsd(1) — bestie's guide to Mono's schema/class-file generator 💖

ok so like. this is xsd, the Mono utility that generates schemas or class files. yes it shares a name with that one XML Schema thing, no they are not the same, we move. 🎀

✨ SYNOPSIS ✨

xsd <schema.xsd> /classes [options]

xsd <schema.xsd> /dataset [options]

xsd <assembly>.dll|<assembly>.exe [options]

xsd <instance.xml> [<instance.xml> ...] [options]

🌸 DESCRIPTION 🌸

so xsd is a tool that's intended to complement the XML serialization support of Mono. it's giving sidekick energy but honestly it's the main character of this whole situation. here's what it can do for you:

• Generate serializable classes — from a given XML schema, it generates a class you can use to read and write xml documents that conform to that schema (that's the /classes option, periodt 💅).
• Generate typed datasets — from a given XML schema, it generates a typed DataSet class you can use to read and write xml documents that conform to that schema (that's the /dataset option, iconic).
• Generate XML schemas — from a given assembly and an optional type name, it generates an XML schema you can use to validate the xml documents you can get by serializing objects of that type. if you don't provide a type, xsd generates a schema for all types in the assembly. okay and this part is important bestie: when you specify the assembly name, do not include the file extension (.dll or .exe). xsd will look for the assembly using the standard assembly loading rules. no cap. 🦋
• Infer XML schemas — from a given set of XML documents, it infers the XML schema you can use to validate those documents. it's literally reading the vibes of your XML and writing them down. 🔥

⭐ OPTIONS ⭐

the following options are available:

• /element:name, /e:name — specifies the name of the XML schema element for which a class or a dataset has to be generated. tell it which element, bestie, it can't read your mind.
• /namespace:name, /n:name — specifies the namespace of the XML schema element for which a class or a dataset has to be generated.
• /language:name, /l:name — specifies the programming language to use for the generated code. the only supported languages are CS (C#) and VB (Visual Basic.NET). so sorry to everyone else, that's the whole guest list. 😭
• /generator:type,assembly, /g:type,assembly — tells xsd.exe to use a custom CodeDomProvider to generate code. the type name must be the full name. assembly name is a local file name that's going to be loaded. the specified Type must have the default constructor. no default constructor, no party. 🙈
• /outputdir:path, /o:path — specifies the directory where to generate the code or schemas. put your little files somewhere cute. 💖
• /type:name, /t:name — specifies the full name of the type (including namespace) for which to generate the XML schema. full name, including namespace, don't skip the namespace part. 👑
• /help, /h — show usage help. the classic. always here for you. ✨

🫶 AUTHORS 🫶

these legends built it:

• Lluis Sanchez Gual (lluis@ximian.com)
• Atsushi Enomoto (atsushi@ximian.com)

🌈 LICENSE 🌈

xsd is released under the terms of the GNU GPL. slay. legally. ⚖️💖

🧚 SEE ALSO 🧚

• disco(1)
• soapsuds(1)
• mono(1)
• mcs(1)
• wsdl(1)

go read those too, they're in the group chat. 💅

ok that's the whole page bestie, you ate that. this has been xsd(1) from the Mono manual — that's the one and only, the header up top and the footer down here both say xsd(1) and honestly? consistent queen. 🎀✨💜