This link suggests another alternative … using a path character in specifying the input schemas resets the generated file name. So if you use the following you will be able to control your output file name. xsd.exe schema1.xsd schema2.xsd .\schema3.xsd Will force xsd.exe to generate the schema3.cs file. Note: It’s a hack but up to … Read more
This behavior is by design: The xs:integer type is specified as a number with no upper or lower bound on its size. For this reason, neither XML serialization nor validation map it to the System.Int32 type. Instead, XML serialization maps the xs:integer to a string while validation maps it to the Decimal type that is … Read more
Once you have the SDK installed * (either Manually, or with Visual Studio), you’ll find it in the following directories: SDK 8 and later There is an an additional FX version subdirectory: %programfiles(x86)%\Microsoft SDKs\Windows\{ver}\bin\{FXVer} Tools Where {ver} is the SDK version (e.g. v8.1A) and {FXVer} is the applicable .Net Framework version, e.g. NETFX 4.0v e.g. … Read more
You can check out Xsd2Code for a VS addin that does this interactively. The author is also working on a VS2010 version, as far as I know. alt text http://i3.codeplex.com/Project/Download/FileDownload.aspx?ProjectName=Xsd2Code&DownloadId=41336
You can successfully integrate xsd.exe into the Visual Studio IDE like this: Go into Tools, External Tools and click the Add button: 2010 2015 / 2017 Title: Create Schema From Class Command (per framework): 4.0 C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin\NETFX 4.0 Tools\x64\xsd.exe 4.5.1 C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\bin\NETFX 4.5.1 Tools\x64\xsd.exe 4.6.* C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.6.* Tools\x64\xsd.exe … Read more