08-24-04 11:59 PM
The nature of xsd.exe is different and as such it cannot be used to replace
BizTalk Server compiled schema artifacts. If compiling a large schema is a
problem, please contact PSS and ask them to fix this.
Xsd.exe in fact does nothing more then creating a class from a given
schema... you can use this class inside an expression shape or your custom
.NET components, but it would certainly not replace the schema like BizTalk
Server is implementing this.
Best regards!
Christof
--
Christof [Microsoft BizTalk Server MVP]
"Isaac Ferreira" <gpostcov@hotmail.com> wrote in message
news:fd37e1fa.0408240135.2da39120@posting.google.com...
> Question:
>
> I am having major problems compiling a large sized XSD schema.
>
> I have tried many differenct cofigurations but nothing will compile
> the files. I posted this problem on another thread, but I wonder if
> there was a way to work around this by using XSD.EXE to compile the
> large schema into a .CS (C#) file and then add it to the project...
>
> Can BizTalk handled a compiled .CS file instead of the XSD file?
>
> I have literally spent 3 days on this problem, as BizTalk is very much
> based on schemas/document definitions I would imagine this part of the
> application would be stable, but it is not, and the setup of included
> schemas is too easy to get wrong. I am importing an industry standard
> XSD file and it will try to compile it for hours! This should not be
> so frustrating.
>
> Thanks!
>
> Isaac Ferreira
> Application Architect
> BizTalk Developer
[ Post a follow-up to this message ]
| 
