xsd.exe fails to create common data types out of nested schemas


hi,

with contract first approach have xsd schemas core interface definitions. outsourced common data types (enumerations , length limited string types) in shared common.xsd file in turn <import>ed top level xsd schemas.

we tried generate .cs code files xsd.exe in scenario. generated code files repeatingly contain common data type definitions. leads several compiler errors. using different namespace delcarations each generated class not solve problem: shared character of our common data types lost after code generation xsd.exe!

it seems popular problem, because shared data types commonly used practice. solved problem already? how can deal this? suggestions?

hi, had similiar issue. main reason can't tell xsd.exe tool generate classes first schema , not supporting schemas, little manual cleanup in order.  because of how .net compiles everything, found following workflow helpful:

consider 3 files, common.xsd, obj1.xsd, , obj2.xsd.  obj1 , obj2 both refer common.xsd resolve data types.

create of .cs files using xsd.exe tool end common.cs, obj1.cs, , obj2.cs.

now, go obj1.cs , delete declarations types, enumerations, etc duplicated from the common.cs file.  same obj2.cs file.

finally, add 3 files project.  compiler accurately locate references.

we went 1 step further , added namespace xyz { } declaration within each of .cs files of objects within same namespace.

 

chris lively.



Archived Forums A-B  >  ASMX Web Services and XML Serialization



Comments

Post a Comment

Popular posts from this blog

Azure DocumentDB Owner resource does not exist

having same error microsoft.azure.documents.documentclientexception: message: {"errors":["owner resource not exist"]} , scenario. when deployed webapp azure , try document docdb throws error. docdb exists in azure , contains document looking for. weird local machine(running vs) works fine. i'm using same settings in azure , local. have , idea this. thanks Microsoft Azure  >  Azure Cosmos DB
Read more

job syspolicy_purge_history job fail in sqlserver 2008

Image
hello guys, when installed sqlserver,it automatically created 1 job name job syspolicy_purge_history. but failed @ step 1. the reason is: date                11/6/2010 2:00:00 am log                job history (syspolicy_purge_history) step id                1 server                mxosv-otsdb01 job name                syspolicy_purge_history step name                verify automation enabled. duration                00:00:00 sql severity                16 sql message id                34022 operator emailed                operator net sent                operator paged                retries attempted                0 message executed user: nt authority\system. policy automation turned off. [sqlstate 42000] (error 34022).  the step failed. have run statement: select msdb.dbo.fn_syspolicy_is_automation_enabled the returned valus 0. what can resolve it? or can delete job manually.   thanks in advance. if haven't things want,be
Read more

Trying to register with public marketplace error with 'Get-AzureStackStampInformation'

when trying register against public azure adfs azure stack error below. logs can found at: c:\maslogs\azurestack.azureregistration.2017-10-12.01-31-23.log  and  \\azs-ercs01\c$\maslogs error occurred checking stamp information: system.management.automation.remoteexception: term 'get-azurestackstampinformation' not recognized name of cmdlet, function, script file, or operable program. check spelling of name, or if path included, verify path correct , try again. @ c:\azurestack-tools-master\registration\registerwithazure.psm1:1106 char:5 +     throw "logs can found at: $global:azureregistrationlog  and  \ ... +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     + categoryinfo          : operationstopped: (logs can fou... , try again.:string) [], runtimeexception     + fullyqualifiederrorid : logs can found at: c:\maslogs\azurestack.azureregistration.2017-10-12.01-31-23.log  a    nd  \\azs-ercs01\c$\maslogs error occurred chec
Read more