I took a look at the source code, and it seems the problem is the API Schema definitions have moved from the same directory as the WSDL for 1.3.1 to an "xsd_schemas" subdirectory for 1.4.1.1. Perhaps a separate key for the API Schema definition directory should be added for use in SchemaGatherer.ProcessEnergisticsSchemas rather than WITSMLxxx_WSLD.
Last edit: Matt 2013-07-02
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It turns out that my analysis was incorrect. The AllDirectories option will make Directory.GetFiles search the subdirectories as well. I'm not sure why those classes weren't in the provided DevKit build, but they showed up when I generated the DevKit myself.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The DevKit seems to be missing classes for the 1.4.1 API Schema objects (e.g. capClient, capServer).
Last edit: Matt 2013-07-02
I took a look at the source code, and it seems the problem is the API Schema definitions have moved from the same directory as the WSDL for 1.3.1 to an "xsd_schemas" subdirectory for 1.4.1.1. Perhaps a separate key for the API Schema definition directory should be added for use in SchemaGatherer.ProcessEnergisticsSchemas rather than WITSMLxxx_WSLD.
Last edit: Matt 2013-07-02
It turns out that my analysis was incorrect. The AllDirectories option will make Directory.GetFiles search the subdirectories as well. I'm not sure why those classes weren't in the provided DevKit build, but they showed up when I generated the DevKit myself.