Skip to content

Commit fd88711

Browse files
authored
Fix usage
1 parent 01ba178 commit fd88711

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ For command line use, choose your preferred installation:
4747
- CI Builds are available at the NuGet feed https://ci.appveyor.com/nuget/xmlschemaclassgenerator-0f1t3r6ti475
4848

4949
```
50-
Usage: dotnet xscgen [OPTIONS]+ xsdFile...
50+
Usage: xscgen [OPTIONS]+ xsdFile...
5151
Generate C# classes from XML Schema files.
5252
Version 2.0.522.0
5353
xsdFiles may contain globs, e.g. "content\{schema,xsd}\**\*.xsd", and URLs.
@@ -185,15 +185,15 @@ var generator = new Generator
185185
Using the optional `|` syntax of the `-n` command line option you can map individual xsd files to C# namespaces. If you have several input files using the same XML namespace you can still generate an individual C# namespace for the types defined within a single xsd file. For example, if you have two input files `a.xsd` and `b.xsd` both of which have the same `targetNamespace` of `http://example.com/namespace` you can generate the C# namespaces `Example.NamespaceA` and `Example.NamespaceB`:
186186

187187
```
188-
dotnet-xscgen.exe -n "|a.xsd=Example.NamespaceA" -n "|b.xsd=Example.NamespaceB" a.xsd b.xsd
188+
xscgen -n "|a.xsd=Example.NamespaceA" -n "|b.xsd=Example.NamespaceB" a.xsd b.xsd
189189
```
190190

191191
#### Mapping empty XML namespaces
192192

193193
In order to provide a C# namespace name for an empty XML namespace you can specify it on the command line like this:
194194

195195
```
196-
XmlSchemaClassGenerator.Console.exe -n =Example example.xsd
196+
xscgen -n =Example example.xsd
197197
```
198198

199199
Note the space between `-n` and `=Example`.

0 commit comments

Comments
 (0)