I have some 'base' schema definitions that are going to be in several
projects in the future.  The processing of resulting classes created
by XSD will be consistent across the new projects.

I have created a schema with these base definitions and common code to
process these elements.  I have managed to finally get include to work
so that the base schema is now included in the schema for a particular
application.  The base schema and common code is in a different
solution than the actual application.

<xs:schema id="BaseConfig"
    targetNamespace="http:/foo/Configuration"
    xmlns:jlc="http:/foo/Configuration"
    xmlns="http://foo/Configuration"
    elementFormDefault="qualified"
    xmlns:xs="http://www.w3.org/2001/XMLSchema" >
<xs:element name="IPInformation" type="IPConfiguration_Type" />
<xs:complexType name="IPConfiguration_Type">
 <xs:sequence>
   <xs:element name="ProtocolType" type="ProtocolType_Type" />
   <xs:element name="AddressFamilyType" type="AddressFamily_Type" />
  <xs:element name="AddressType" type="Address_Type" />
  <xs:element name="PortNumber" type="PortNumber_Type" />
</xs:sequence>
</xs:complexType>
.....  details omited
</schema>
   
<xs:schema id="ApplicationConfig"
        targetNamespace="foo/Configuration"
        xmlns:jlc="foo/Configuration"
        xmlns="foo/Configuration"
        elementFormDefault="qualified"
        xmlns:xs="http://www.w3.org/2001/XMLSchema" >
<xs:include schemaLocation="..\..\..\ConfigurationBase.xsd" />
<xs:element name="ApplicationConfiguration">
 <xs:complexType name="IPHostBase">
   <xs:complexContent>
     <xs:extension base="HostBase">
       <xs:sequence>
         <xs:element name="IPConfiguration"
type="jlc:IPConfiguration_Type"/>
       </xs:sequence>
     </xs:extension>
   </xs:complexContent>
</xs:complexType>
</xs:element>
.... details ommited
</schema>

Now the problem (which was immediately obvious) is that in the base
solution, the class generated by XSD for IPConfiguration_Type is not
the same class (from a .net C# point of view) as the class generated
by XSD in the application solution.

Since the code in the base solution is built against the classes from
the XSD of the base schema, they can not be called passing in the
objects that were created by deserializing the application
configuration in the application.

Is there a way to solve this problem or is there better way to do this
so that I can reuse the schema definition and the common code that
works with those classes?

Thanks

------------------------------
Roy Chastain
SOHO Technology Solutions, LLC